5.
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.
6.
If Managed Server transactions coexist in a clustered system, perform the following.
a.
On the secondary node for the target transactions, check that the Managed Server transactions have stopped.
If not stopped, stop them on the secondary node.
If multiple Managed Server transactions exist, perform this procedure for each secondary node for Managed Server
transactions.
Refer to the relevant cluster software manuals for information on stopping the Managed Server transactions.
b.
On the primary node for the target transactions, stop the Managed Server transactions.
Refer to the relevant cluster software manuals to stop the 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 for each primary node for Managed Server
transactions.
7.
Stop the local transactions on all the nodes.
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.
8.
On the primary node and the secondary node, save the start and stop script of the Management Server transaction.
9.
In cases when Managed Server transactions coexist in the cluster system, move the AdvancedCopy Manager daemon start and
stop script of the Managed Server transactions to a backup location.
On the primary node and the secondary node, move the AdvancedCopy Manager daemon start and stop script of the Managed
Server transactions to a backup location.
10.2.2.2 Performing Upgrade (Primary Node)
1.
Refer to "
Version 16.x (for Solaris, Linux)
" and perform the Upgrade Installation.
2.
Unmount the shared disk for shared data of ETERNUS SF Manager.
Point
If the Upgrade Installation has ended in an error, after removing the cause of the failure of the Upgrade Installation, re-execute the
installation from the execution of the installation shell.
10.2.2.3 Performing Upgrade (Secondary Node)
1.
Mount the shared disk for shared data of ETERNUS SF Manager.
2.
Refer to "
Version 16.x (for Solaris, Linux)
" and perform the Upgrade Installation.
3.
Unmount the shared disk for shared data of ETERNUS SF Manager.
Point
If the Upgrade Installation has ended in an error, after removing the cause of the failure of the Upgrade Installation, re-execute the
installation from the execution of the installation shell.
- 211 -
