See
Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the
ETERNUS SF Installation and Setup Guide
for this
version for information on tuning.
5.
Check that the cluster application (transaction) has stopped.
If not stopped, stop the cluster application (transaction) to which ETERNUS SF Manager belongs.
Refer to the relevant cluster software manuals for information on stopping it (transaction).
10.2.2.6 Starting ETERNUS SF Manager
After performing "
10.2.2.4 Tasks to Be Performed After Upgrade (Primary Node)
10.1.2.5 Tasks to Be Performed After Upgrade
", perform the following procedure:
1.
Check that the cluster application (transaction) has started on the primary node.
If not started, start the cluster application (transaction) to which ETERNUS SF Manager belongs.
Refer to the relevant cluster software manuals for information on starting it.
2.
If Managed Server transactions coexist in a clustered system, start the Managed Server transactions on the primary node for the
target transactions.
Refer to the relevant cluster software manuals to start the Managed Server transactions.
If multiple Managed Server transactions exist, perform this procedure for each Managed Server transaction.
3.
Start the local transactions on all the nodes.
Start the communication daemon for local transactions of AdvancedCopy Manager's manager.
Refer to "Starting and Stopping Communication Daemon" in the
ETERNUS SF AdvancedCopy Manager Operation Guide
for the
operating system of the Management Server for this version for information on starting the daemon.
".
10.2.3 Resuming Operation
When the tasks described above have been performed, the upgrade of the AdvancedCopy Manager's manager is complete. Restart the
AdvancedCopy Manager operation.
Note
If operating Web Console from the same web browser as before the upgrade, delete the web browser's cache prior to operation.
10.3 Upgrading AdvancedCopy Manager's Agent (for Windows)
This section describes the upgrade procedure for the AdvancedCopy Manager's agent for Windows Server 2008 or later.
10.3.1 Upgrading on Non-clustered Systems
10.3.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.
Log on to the server using Administrator privileges.
- 215 -