Upgrading Storage Cruiser's Manager (For Solaris, Linux); Upgrading On Non-Clustered Systems; Preparing For Upgrade - Fujitsu ETERNUS SF Express V16.6 Migration Manual

See
Refer to "Reload ETERNUS Disk Storage System Configuration Information" in the ETERNUS SF Web Console Guide for this version
for information on reloading the configuration information.
3.
Upgrading Performance Management
When using the performance management function of NAS volume and NAS system after the upgrade, it is required to restart
the performance management function. To set Start of performance management, select "Yes" for Create Device Configuration
File.
Refer to "Displaying Performance Information of NAS Volume and NAS System" in the ETERNUS SF Storage Cruiser Operation Guide
for details.
Information
After upgrading to this version, when changing the SNMP communication protocol used for fault management from SNMPv1 to
SNMPv3, refer to "Changing SNMP Communication Protocol of Management Server" in the ETERNUS SF Storage Cruiser Operation Guide
for this version and configure your operational environment.
Note
Information related to the captured capacity and the captured logs before the upgrade is not displayed on the Dashboard. Refer to the
following screens:
-
Capacity information
-
Capacity Graph of Thin Provisioning Pool
-
Capacity Graph of Tier Pool
-
Logs information
-
Operation History
-
Events
-
Threshold Monitoring Alarms
-
Quota Management (NAS Management)

7.2 Upgrading Storage Cruiser's Manager (for Solaris, Linux)

7.2.1 Upgrading on Non-clustered Systems

7.2.1.1

Preparing for Upgrade

Point
It is recommended that you back up the system before starting the upgrade.
By preparing a backup, in cases when an error occurs during the upgrade, it is possible to return the system to its state prior to the
upgrade, simply by recovering (restoring) the system from the backup.
1.
Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
2.
Ensure that there is enough available disk space (650 MB in a Solaris environment, 200 MB in a Linux environment) on the server
where the upgrade is performed.
Note that in cases when upgrade installation is executed in a state where the capacity required for the upgrade is not available,
- 95 -