Preparing For Upgrade - Fujitsu ETERNUS SF Express V16.6 Migration Manual

-
Interval that obtains performance information (in seconds)
-
Performance monitoring target (only for ETERNUS Disk storage system. Minimum LUN_V, Maximum LUN_V)
-
VMware vCenter Server configuration information
If VMware vCenter Server was registered in the Storage Cruiser's manager of the previous version, record the configuration
information of the previous version with the following procedure:
1.
Log in to Web Console.
2.
On the global navigation tab, click Server.
3.
On the Category pane, click Correlation.
The items of the Category pane change into the items concerning the correlation management.
4.
On the Category pane, click End to End View (VMware).
The VMware End to End view list is displayed in the Main pane.
5.
Record the IP address and the port number of VMware vCenter Server that are displayed in the Main pane.
6.2.2.2

Preparing for Upgrade

Point
It is recommended that you back up the system before starting the upgrade. If a failure occurs during the upgrade, you cannot restore
the environment to the pre-installation status (rollback).
When returning back to the state before installation of the upgrade, recover (restore) the system from the backup.
1.
Check that the cluster application (transaction) is stopped on the secondary node.
Check whether the cluster application (transaction) to which ETERNUS SF Manager belongs has stopped.
If not stopped, stop the cluster application (transaction).
Refer to the relevant cluster software manuals for information on stopping it.
2.
Stop the cluster application (transaction) on the primary node.
Stop the cluster application (transaction) to which ETERNUS SF Manager belongs. Refer to the relevant cluster software manuals
for information on stopping it.
However, the shared disk for shared data of ETERNUS SF Manager must be mounted.
3.
If Managed Server transactions coexist in the clustered system, perform the following procedure:
a.
On the secondary node for a target transaction, check that the Managed Server transactions are stopped.
If not stopped, stop Managed Server transactions on the secondary node.
If multiple Managed Server transactions exist, perform this procedure on each secondary node for Managed Server
transactions.
Refer to the relevant cluster software manuals for information on stopping it.
b.
On the primary node for a target transaction, stop the Managed Server transaction.
Refer to the relevant cluster software manuals, stop Managed Server transactions.
However, the shared disk for shared data of Managed Server transactions must be mounted.
If multiple Managed Server transactions exist, perform this procedure on each primary node for Managed Server
transaction.
4.
Stop the local transactions on all the nodes, perform the following procedure:
Stop the communication daemon for the local transactions of the AdvancedCopy Manager's manager.
Refer to "Starting and Stopping Communication Daemon" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant
to the OS of the Management Server for this version for information on stopping the daemon.
- 64 -