When the operation divides shared disk for shared data use and the shared disk for repository use, the resources of the shared
disk for repository use are deleted.
10.1.2.5 Tasks to Be Performed After Upgrade (Secondary Node)
The tasks below need to be performed on the secondary node.
1.
In the version level of this ETERNUS SF Manager, Symfoware is not used.
To upgrade from Version 16.1 or later, the procedures listed below are not needed.
To upgrade from Version 16.0 or earlier, follow the procedures listed below to uninstall the Symfoware Server.
a.
Confirm that other products are not utilizing the Symfoware. If Symfoware is in use by another product, refrain from
uninstalling Symfoware.
b.
Uninstall Symfoware from the Add or Remove Programs or Programs and Features page.
If Symfoware Server and Symfoware Client are both installed, uninstall the Symfoware Client first.
2.
Check that the ETERNUS SF Manager services are stopped.
If not stopped, use the Failover Cluster Manager to stop the transactions of ETERNUS SF Manager.
3.
Restore the environment setting files (sys.properties) for AdvancedCopy Manager Copy Control Module.
Overwrite the environment configurations file (sys.properties) saved in "
10.1.2.3 Performing Upgrade (Secondary Node)
" onto
the following file after upgrade installation.
The environment setting files for AdvancedCopy Manager Copy Control Module is as follows.
$INS_DIR\CCM\sys\sys.properties
4.
Restore the saved general scripts for the AdvancedCopy Manager CCM.
When general scripts are backed up in "
10.1.2.4 Tasks to Be Performed After Upgrade (Primary Node)
general scripts to the directory stored in "Preparing General Scripts for AdvancedCopy Manager CCM", which corresponds to
respective operating systems and nodes described in the
ETERNUS SF Cluster Environment Setup Guide
of the appropriate earlier
version.
10.1.2.6 Starting ETERNUS SF Manager
After performing "
10.1.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 ETERNUS SF Manager services are started on the primary node.
If not started, use the Failover Cluster Manager to start the transactions of ETERNUS SF Manager.
2.
When using the ETERNUS VASA Provider, start the ETERNUS VASA Provider service on the primary node.
Use the Failover Cluster Manager to start the transactions of the ETERNUS VASA Provider.
3.
If Managed Server transactions coexist in a clustered system, start the Managed Server transactions in the primary node for a
target transaction.
Use the Failover Cluster Manager to start the Managed Server transactions.
If multiple Managed Server transactions exist, apply this procedure for each Managed Server transaction.
4.
In all of the nodes in which the Storage Cruiser's agent has been installed, start the service of the Storage Cruiser's agent. Refer
to "Starting and Stopping Agent" in the
ETERNUS SF Storage Cruiser Operation Guide
for information on how to start the service.
5.
Start the local transactions on all the nodes.
With the Windows services screen, start the AdvancedCopy Manager COM Service.
6.
If the ETERNUS SF SNMP Trap Service was used with the previous version, on all the nodes, start the ETERNUS SF SNMP Trap Service
with the Windows services screen.
- 207 -
