The following values are used in the description.
Directory Name | Explanation |
|---|---|
$INS_DIR | "Program Directory" specified at the ETERNUS SF Manager installation. |
Point
It is recommended that you back up the following resources 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.
System (the primary node and the secondary node)
Shared disk for shared data of Management Server transactions
Shared disk for shared data of Managed Server transactions
Log on to the server using Administrator privileges.
Insert the DVD "ETERNUS SF SC/ACM/Express Mediapack for Windows (V16.9 or higher) Manager Program (1/2)" of this version into the DVD drive.
On the secondary node, execute the following batch file and then confirm the output message.
dvdDrive:\Manager_windows\vuptools\esfccm_vlup_first.batIf the following message is output, the setting has been changed for the Upgrade Installation. To reflect the setting, restart the secondary node where the work has been performed. After the secondary node restarts, proceed to the next step.
[Info] Configuration check and change succeeded. You must restart your system before the installation.
If the following message is output, the Upgrade Installation can be performed with the existing setting. Proceed to the next step.
[Info] Configuration check succeeded.
On the primary node, execute the following batch file and then confirm the output message.
dvdDrive:\Manager_windows\vuptools\esfccm_vlup_first.batIf the following message is output, the setting has been changed for the Upgrade Installation. To reflect the setting, restart the primary node where the work has been performed. After the primary node restarts, proceed to the next step.
[Info] Configuration check and change succeeded. You must restart your system before the installation.
If the following message is output, the Upgrade Installation can be performed with the existing setting. Proceed to the next step.
[Info] Configuration check succeeded.
Ensure that there is enough available disk space (400 MB) on the server where the upgrade is performed on the secondary node.
In cases when upgrade installation is executed in a state where the capacity required for the upgrade is not available, the following message is displayed and the installation terminates in an error. Re-execute the upgrade after securing the capacity required for the installation.
Output message (when the drive letter of the destination of the installation is "C:"):
The available capacity of the specified disk (C:) is insufficient. Please execute it again after increasing the disk area.
Check that the services of ETERNUS SF Manager are stopped on the secondary node.
If not stopped, use the Failover Cluster Manager on the secondary node to stop the transactions of ETERNUS SF Manager.
When using the ETERNUS SF SNMP Trap Service, on the secondary node, stop the SNMP Trap function.
With the Windows services screen, stop the ETERNUS SF SNMP Trap Service.
Note
In an environment where other software using SNMP Traps such as Systemwalker Centric Manager and ServerView Resource Orchestrator coexists on a target server, if you stop the ETERNUS SF SNMP Trap Service, other software using SNMP Traps cannot perform the fault monitoring. Make sure that even if the fault monitoring cannot be performed, no problem is caused, and perform this step.
When using the ETERNUS VASA Provider, on the secondary node, confirm that the ETERNUS VASA Provider service has been stopped.
If not stopped, use the Failover Cluster Manager on the secondary node to stop the transactions of the ETERNUS VASA Provider.
Ensure that there is enough available disk space (400 MB) on the server where the upgrade is performed on the primary node.
In cases when upgrade installation is executed in a state where the capacity required for the upgrade is not available, the following message is displayed and the installation terminates in an error. Re-execute the upgrade after securing the capacity required for the installation.
Output message (when the drive letter of the destination of the installation is "C:"):
The available capacity of the specified disk (C:) is insufficient. Please execute it again after increasing the disk area.
On the primary node, stop the services of ETERNUS SF Manager.
Use the Failover Cluster Manager to stop the transactions of ETERNUS SF Manager.
However, the shared disk for shared data of ETERNUS SF Manager must be online.
When using the ETERNUS SF SNMP Trap Service, on the primary node, stop the SNMP Trap function.
With the Windows services screen, stop the ETERNUS SF SNMP Trap Service.
Note
In an environment where other software using SNMP Traps such as Systemwalker Centric Manager and ServerView Resource Orchestrator coexists on a target server, if you stop the ETERNUS SF SNMP Trap Service, other software using SNMP Traps cannot perform the fault monitoring. Make sure that even if the fault monitoring cannot be performed, no problem is caused, and perform this step.
When using the ETERNUS VASA Provider, stop the ETERNUS VASA Provider service on the primary node.
Use the Failover Cluster Manager to stop the transactions of the ETERNUS VASA Provider.
However, the shared disk for shared data of the ETERNUS Information Provider must be online.
If Managed Server transactions coexist in the clustered system, perform the following procedure:
On the secondary node for a target transaction, check that the Managed Server transactions are stopped.
If not stopped, use the Failover Cluster Manager to 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.
On the primary node for a target transaction, stop the Managed Server transaction.
Use the Failover Cluster Manager to stop Managed Server transactions.
However, the shared disk for shared data of Managed Server transactions must be online.
If multiple Managed Server transactions exist, perform this procedure on each primary node for Managed Server transaction.
In all of the nodes in which the Storage Cruiser's agent has been installed, stop the service of the Storage Cruiser's agent. Refer to "Starting and Stopping Agent" in the Storage Cruiser Operation Guide for information on how to stop the service.
Stop the local transactions on all the nodes, perform the following procedure.
With the Windows services screen, stop the AdvancedCopy Manager COM Service.
Performing the upgrade is as follows.
Save the environment setting files for AdvancedCopy Manager Copy Control Module (sys.properties).
The environment setting files for AdvancedCopy Manager Copy Control Module is as follows.
$INS_DIR\CCM\sys\sys.properties
Make a copy on any directory that is other than the directory which is the destination of the installation of AdvancedCopy Manager CCM.
The saved file is used in tasks after the upgrade.
Recover the original environment configurations file (sys.properties) of the AdvancedCopy Manager CCM.
Overwrite the original environment configurations file onto the file of the copying destination.
Original Environment Configurations File | Copying Destination File |
|---|---|
$INS_DIR\CCM\noncluster\sys\sys.properties | $INS_DIR\CCM\sys\sys.properties |
Save the general script for the AdvancedCopy Manager CCM.
In corresponding previous version of "Preparing General Scripts for AdvancedCopy Manager CCM" corresponding to each OS and nodes in the Cluster Environment Setup Guide, in cases when the general scripts have been stored under the bin directory of the program directory of the AdvancedCopy Manager CCM, make a copy on any directory that is other than the directory which is the destination of the installation of AdvancedCopy Manager CCM.
The saved file is used in tasks after the upgrade.
Refer to "C.3 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 16.x (for Windows)" to perform the upgrade.
Stop the following services and then change the settings for their startup type to "Manual".
ETERNUS SF Manager Apache Service
ETERNUS SF Manager Tomcat Service
ETERNUS SF Manager Postgres Service
ETERNUS SF Storage Cruiser Optimization Option
The shared disk for shared data of ETERNUS SF Manager must be offline.
Point
If the Upgrade Installation has ended in an error, refer to "8.2.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows)" and return the system to a normal state.
The shared disk for shared data of ETERNUS SF Manager must be online.
Perform the upgrade for the secondary node.
The upgrade procedure is the same as that for the primary node. Refer to "7.1.2.2 Performing Upgrade (Primary Node)".
Stop the following services and then change the settings for their startup type to "Manual".
ETERNUS SF Manager Apache Service
ETERNUS SF Manager Tomcat Service
ETERNUS SF Manager Postgres Service
ETERNUS SF Storage Cruiser Optimization Option
The shared disk for shared data of ETERNUS SF Manager must be offline.
The tasks below need to be performed on the primary node.
The shared disk for shared data of ETERNUS SF Manager must be online.
In the version level of this ETERNUS SF Manager, Symfoware is not used.
To upgrade from Version 16.1 or later, steps 1, 2, and 7 are not needed.
To upgrade from Version 16.0 or earlier, follow the procedures listed below to uninstall the Symfoware Server.
Confirm that other products are not utilizing the Symfoware. If Symfoware is in use by another product, refrain from uninstalling Symfoware.
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.
Restore the environment setting files for AdvancedCopy Manager Copy Control Module (sys.properties).
Overwrite the environment configurations file (sys.properties) saved in "7.1.2.2 Performing Upgrade (Primary 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
Restore the saved general scripts for the AdvancedCopy Manager CCM.
When general scripts are backed up in "7.1.2.2 Performing Upgrade (Primary Node)", restore the backed-up 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 Cluster Environment Setup Guide of the appropriate earlier version.
Edit the environment setting files for AdvancedCopy Manager on the shared disk for ETERNUS SF Manager shared data.
Edit the following files:
<Drive of shared disk for shared data of ETERNUS SF Manager>:\etc\opt\swstorage\clsetup.ini
<Drive of shared disk for shared data of ETERNUS SF Manager >:\etc\opt\swstorage\etc\swstg.ini
Change the version information within each file, as follows.
Descriptive Contents of Version Information | |
|---|---|
Before | After |
Version=V16.x | Version=V16.9 |
Note
Do not change anything other than the version information.
If Managed Server transactions coexist in the clustered system, edit the environment setting files for AdvancedCopy Manager on the shared disk for Managed Server transactions shared data.
On the primary node for target transactions, edit the following files:
<Drive of shared disk for shared data of Managed Server transactions>:\etc\opt\swstorage\clsetup.ini
<Drive of shared disk for shared data of Managed Server transactions>:\etc\opt\swstorage\etc\swstg.ini
Change the version information within each file, as follows.
Descriptive Contents of Version Information | |
|---|---|
Before | After |
Version=V16.x | Version=V16.9 |
Note
Do not change anything other than the version information.
The resource is deleted from the transactions belonging to the ETERNUS SF Manager.
Making use of failover cluster manager, the resources stated below are deleted from the transactions belonging to ETERNUS SF Manager. No measures are necessary where the resources do not exist.
Name of Resources
AdvancedCopy GUI Service
SymfoWARE RDB RDBSWSTF
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.
The tasks below need to be performed on the secondary node.
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.
Confirm that other products are not utilizing the Symfoware. If Symfoware is in use by another product, refrain from uninstalling Symfoware.
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.
Check that the services of ETERNUS SF Manager are stopped.
If not stopped, use the Failover Cluster Manager to stop the transactions of ETERNUS SF Manager.
Restore the environment setting files (sys.properties) for AdvancedCopy Manager Copy Control Module.
Overwrite the environment configurations file (sys.properties) saved in "7.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
Restore the saved general scripts for the AdvancedCopy Manager CCM.
When general scripts are backed up in "7.1.2.4 Tasks to Be Performed After Upgrade (Primary Node)", restore the backed-up 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 Cluster Environment Setup Guide of the appropriate earlier version.
After performing "7.1.2.4 Tasks to Be Performed After Upgrade (Primary Node)" and "7.1.2.5 Tasks to Be Performed After Upgrade (Secondary Node)", perform the following procedure:
Check that the services of ETERNUS SF Manager are started on the primary node.
If not started, use the Failover Cluster Manager to start the transactions of ETERNUS SF Manager.
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.
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.
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 Storage Cruiser Operation Guide for information on how to start the service.
Start the local transactions on all the nodes.
With the Windows services screen, start the AdvancedCopy Manager COM Service.
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.
Point
When ETERNUS SF Manager has been recovered to normal state by performing the task described in "8.2.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows)", to ensure data consistency, execute the "stgxfwcmmodsrv" command to perform the server information change processing.
Specify the Management Server name to the -n option and execute the "stgxfwcmmodsrv" command. Check Server column of the "stgxfwcmdispsrv" command execution result for the Management Server name specified to the -n option.
$INS_DIR\ACM\bin\stgxfwcmmodsrv -n ManagementServerNameRefer to "Command References" in the AdvancedCopy Manager Operation Guide (for Windows) for this version for information on the commands.
Subsequently, go to "7.1.3 Resuming Operation".