1.
Check that the cluster application (transaction) has 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 (transaction).
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 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.
4.
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.
5.
On the primary node, perform a backup of the operating environment of the previous version of the AdvancedCopy Manager's
manager.
Refer to "
A.33 Capacity Necessary for Backup of Previous Version
" for information on the capacity required to perform a backup.
a.
Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
b.
Insert the DVD-ROM "ETERNUS SF SC/ACM Mediapack for Solaris (Manager Program) (2/2)" or "ETERNUS SF SC/ACM/Express
Mediapack for Linux 64bit (Manager Program) (2/2)" for this version into the DVD-ROM drive.
Refer to "DVD-ROM Contents" in the
ETERNUS SF Installation and Setup Guide
for this version for information on the DVD-
ROM structure and detailed contents.
c.
Mount the DVD-ROM.
Example:
# mount /mnt/dvd
d.
Implement backup of the previous version.
Execute the following command. For
backupDir
, specify the directory in which to store the backup data with an absolute
path. For
tmpDir
, specify a directory in which to temporarily place the files related to the performance management
function of Storage Cruiser with an absolute path. When the performance management function is not being used, it is
unnecessary to specify a directory for the
tmpDir
.
# /mnt/dvd/Manager_unix/vuptools/esfpreinst_cluster.sh backupDir [tmpDir] -primary
When the backup fails, after confirming the output error message and removing the cause of the failure, execute the
command again.
Point
-
Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory names.
- 152 -
