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.
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.
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 server where the work has been performed. After the server restarts, log on to the server using Administrator privileges and 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.
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.
If 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.
Execute the following batch to stop the services of ETERNUS SF Manager.
$INS_DIR\Common\bin\Stop_ESFservice.bat
$INS_DIR means the "Program Directory" specified at the ETERNUS SF Manager installation.
When using the ETERNUS VASA Provider, stop the Provider function.
With the Windows services screen, stop the ETERNUS Information Provider.
When using the ETERNUS SF SNMP Trap Service, 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.
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.
Point
If the upgrade was terminated abnormally, refer to "8.2.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows)" to recover the system to the normal state.
The tasks below need to be performed.
Information
About the notation in procedure
Directory Name | Explanation |
|---|---|
$INS_DIR | "Program Directory" specified at the ETERNUS SF Manager installation. |
$ENV_DIR | "Environment Directory" specified at the ETERNUS SF Manager installation. |
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.
If the SNMP Trap XML definition file is customized in the environment of the previous version, it is necessary to customize this version as well.
Save the SNMP Trap XML definition file that is stored in the following directory to an arbitrary location.
After that, refer to "SNMP Trap XML Definition File" in the Storage Cruiser Operation Guide and customize the SNMP Trap XML definition file. For the contents of the customization, refer to the SNMP Trap XML definition file which was saved to the arbitrary location.
Directory of the location of Customization Definition files |
|---|
$ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth |
If the polling service setting file is customized in the environment of the previous version, it is necessary to customize this version as well.
Save the polling service setting file that is stored in the following directory to an arbitrary location.
After that, refer to "Polling Service Setting File" in the Storage Cruiser Operation Guide and customize the Polling Service Setting file. For the contents of the customization, refer to the polling service setting file which was saved to the arbitrary location.
Customization Definition files |
|---|
$ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling\pollingService.xml |
If 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.
Execute the following batch to restart the services of ETERNUS SF Manager.
$INS_DIR\Common\bin\Start_ESFservice.bat
When ETERNUS VASA Provider was used in a previous version of ETERNUS SF system, upgrade it to the version corresponding to this version of ETERNUS SF system. After the upgrade, confirm that the Provider function is running.
If it is not running, start ETERNUS Information Provider from the Windows services screen.
However, if the following conditions are satisfied, reinstall (uninstall and install) ETERNUS VASA Provider:
The upgrade from Version 16.2 is performed, and
ETERNUS VASA Provider whose version corresponds to this version level is installed.
Note
The host name of the Management Server must be a name that can be specified as the FQDN name in ETERNUS VASA Provider. Because the ETERNUS VASA Provider that supports this version limits the available FQDN name, change the host name of the Management Server as required. For details about the available FQDN names for ETERNUS VASA Provider, refer to the ETERNUS VASA Provider manuals.
If the ETERNUS SF SNMP Trap Service was used with the previous version, 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 "5.1.3 Resuming Operation".