The following values are used in the description.
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. |
Point
It is recommended that you back up the system before starting the upgrade. If a failure occurs during the upgrade, you cannot restore the environment to the pre-installation status (rollback).
When returning back to the state before installation of the upgrade, recover (restore) 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.
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.
Check that the ETERNUS SF Manager services 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 VASA Provider or the ETERNUS Information Provider, on the secondary node, confirm that the ETERNUS Information Provider service has been stopped.
If not stopped, use the Failover Cluster Manager on the secondary node to stop the transactions of the ETERNUS Information Provider.
On the primary node, stop the ETERNUS SF Manager services.
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 VASA Provider or the ETERNUS Information Provider, stop the ETERNUS Information Provider service on the primary node.
Use the Failover Cluster Manager to stop the transactions of the ETERNUS Information 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.
Perform the following steps to stop the local transactions on all the nodes.
Select Control Panel > Administrative Tools > Services to open the Windows Services screen.
Select "AdvancedCopy Manager COM Service" and then click Stop.
On the primary node, perform a backup of the operating environment of the previous version of the AdvancedCopy Manager's manager.
Refer to "A.7 Capacity Necessary for Backup of Previous Version" for information on the capacity required to perform a backup.
Log on to the server using Administrator privileges.
If already logged on as the Administrator privileges, this step is unnecessary.
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 to perform a backup of the previous version.
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.
dvdDrive:\Manager_windows\vuptools\esfpreinst_cluster.bat backupDir [tmpDir] -primary
When the backup fails, after confirming the output error message and removing the cause of the failure, re-execute the batch file.
Point
Spaces and the characters " | : * ? / . < > , % & ^ = ! ; ( ) are not supported for directory names.
The number of characters in a directory name must be up to 220.
Move the files (tmpDir) related to the performance management function to the same logical drive as the drive on which the product of the previous version is installed. In the case of backup to a different logical drive, it may take time to perform backup and restore.
Eject the DVD media.
Checking for available disk space
Ensure that there is enough available disk space on the server where the upgrade is performed.
The required disk space for the upgrade is calculated as the "Required Disk Space for New Version" minus the "Required Disk Space for Previous Version".
The space required to install this version of the ETERNUS SF Manager.
Refer to "Operating Environment of ETERNUS SF Manager" in the Installation and Setup Guide for this version for information on the required disk space.
The space required to install the previous version of the ETERNUS SF Manager.
Refer to "Operating environment of ETERNUS SF Manager" in the Installation and Setup Guide for the previous version for information on the required disk space.
Uninstalling incompatible software
Check if any incompatible software for this version of the ETERNUS SF Manager is installed on the server where the upgrade is performed.
If incompatible software is found, refer to the relevant software manual and uninstall it before starting the upgrade.
See
Refer to "Operating Environment of ETERNUS SF Manager" in the Installation and Setup Guide for this version for information on the incompatible software.
Estimating the database size
A database is necessary for this version of AdvancedCopy Manager.
The database size must be estimated before starting the upgrade.
See
Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the Installation and Setup Guide for this version for details.
On the secondary node, perform a backup of the operating environment of the previous version of the AdvancedCopy Manager's manager.
The capacity required for performing this backup is 10 MB.
Log on to the server using Administrator privileges.
If already logged on as the Administrator privileges, this step is unnecessary.
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.
Mount the shared disk for shared data of ETERNUS SF Manager.
If it is mounted on the primary node, unmount it to mount on the secondary node.
Execute the following batch file to perform a backup of the previous version.
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.
dvdDrive:\Manager_windows\vuptools\esfpreinst_cluster.bat backupDir [tmpDir] -secondary
When the backup fails, after confirming the output error message and removing the cause of the failure, re-execute the batch file.
Point
Spaces and the characters " | : * ? / . < > , % & ^ = ! ; ( ) are not supported for directory names.
The number of characters in a directory name must be up to 220.
Move the files (tmpDir) related to the performance management function to the same logical drive as the drive on which the product of the previous version is installed. In the case of backup to a different logical drive, it may take time to perform backup and restore.
Unmount the shared disk for shared data of ETERNUS SF Manager.
If it is required for the work on the primary node, mount it on the primary node.
Eject the DVD media.
Checking for available disk space
Ensure that there is enough available disk space on the server where the upgrade is performed.
The required disk space for the upgrade is calculated as the "Required Disk Space for New Version" minus the "Required Disk Space for Previous Version".
The space required to install this version of the ETERNUS SF Manager.
Refer to "Operating Environment of ETERNUS SF Manager" in the Installation and Setup Guide for this version for information on the required disk space.
The space required to install the previous version of the ETERNUS SF Manager.
Refer to "Operating environment of ETERNUS SF Manager" in the Installation and Setup Guide for the previous version for information on the required disk space.
Uninstalling incompatible software
Check if any incompatible software for this version of the ETERNUS SF Manager is installed on the server where the upgrade is performed.
If incompatible software is found, refer to the relevant software manual and uninstall it before starting the upgrade.
See
Refer to "Operating Environment of ETERNUS SF Manager" in the Installation and Setup Guide for this version for information on the incompatible software.
Performing the cluster unsetup
Refer to "Uninstallation of ETERNUS SF Manager" in "Deletion of Cluster Environment for Management Server Transactions" in the Cluster Environment Setup Guide for the relevant previous version to delete the service resources, the cluster resources and unnecessary resources.
Note
Do not uninstall the ETERNUS SF Manager program.
Do not delete the ETERNUS SF Manager installation directory of each node.
In cases when Managed Server transactions coexist, do not release the configurations of these Managed Server transactions.
Refer to "C.1 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 15.x (for Windows)" to perform the upgrade.
Information
When the Upgrade Installation terminates in an error, perform recovery by following the steps outlined below.
Install the target version.
If the installation is successfully completed, continue from "6.1.2.3 Performing Upgrade (Secondary Node)".
Perform the upgrade for the secondary node.
The upgrade procedure is the same as that for the primary node. Refer to "6.1.2.2 Performing Upgrade (Primary Node)".
Information
When the Upgrade Installation terminates in an error, perform recovery by following the steps outlined below.
Install the target version.
If the installation is successfully completed, continue from the following tasks.
After upgrading on the primary node and the secondary node, perform the cluster setup. Refer to "Preparations for Customizing Management Server Transactions" and "Customization for Management Server Transaction" in the Cluster Environment Setup Guide of this version for information on the cluster setup.
The tasks below need to be performed 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.
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=V15.x | Version=V16.9 |
Note
Do not change anything other than the version information.
Restore the operation environment of the previous version of the AdvancedCopy Manager's manager.
Note that if step a and step b have already been performed, perform from step c.
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 to perform a restore of the previous version.
For backupDir, specify the directory in which the backup data is stored 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 backed up, it is unnecessary to specify a directory for the tmpDir.
dvdDrive:\Manager_windows\vuptools\esfpostinst_cluster.bat backupDir [tmpDir] -primary
When the restore fails, after confirming the output error message and removing the cause of the failure, re-execute the batch file.
Point
Spaces and the characters " | : * ? / . < > , % & ^ = ! ; ( ) are not supported for directory names.
The number of characters in a directory name must be up to 220.
Eject the DVD media.
Start the services of ETERNUS SF Manager.
Use the Failover Cluster Manager to start the transactions of ETERNUS SF Manager.
If Managed Server transactions coexist in a clustered system, change the server information of the Managed Server transactions.
To ensure data consistency, execute the "stgxfwcmmodsrv" command to change the server information.
When executing the "stgxfwcmmodsrv" command, specify the Managed Server name for the -n option.
$INS_DIR\ACM\bin\stgxfwcmmodsrv -n serverName
This operation should be performed on the primary node for Management Server transactions.
If multiple Managed Server transactions exist, perform this procedure for each Managed Server transaction.
Note
For changing the server information, start a new window for command execution, and then perform the procedure on the window.
See
Refer to "Command References" in the AdvancedCopy Manager Operation Guide (for Windows) for this version for information on the command.
Import the configuration information from the previous version by executing the "esfadm devconf import" command using Administrator permissions.
Check that the managed devices and servers can be accessed before executing the "esfadm devconf import" command.
$INS_DIR\Common\bin\esfadm devconf import -all
After executing the "esfadm devconf import" command, confirm that the IMPORT STATUS column displays "Complete" with "esfadm devconf importstatus" command.
In addition, confirm that "Complete" is displayed in STATUS column of the import status of the migration target resources. When "Failed" is displayed, the import of configuration information has failed. Refer to "9.2 What to Do When Error Occurs" to take the corrective action.
Note
When executing the "esfadm devconf import" command, if a managed device or server is not accessible, the "esfadm devconf import" command should be re-executed since the device configuration information is not imported.
Uninstalling Symfoware
In the version level of this ETERNUS SF Manager, Symfoware is not used.
Symfoware should only be installed in cases where it was used by ETERNUS SF Manager only.
The procedures to uninstall Symfoware are stated below.
Uninstall Symfoware from the Add or Remove Programs or Programs and Features page.
If both Symfoware Server and Symfoware Client are installed, uninstall Symfoware Client first.
Point
If the ETERNUS VASA Provider was being used with the previous version
It is necessary to reinstall a version of the ETERNUS VASA Provider that supports this version.
If the Fujitsu ETERNUS Storage Systems Monitoring Pack was being used with the previous version
It is necessary to reinstall a version of the Fujitsu ETERNUS Storage Systems Monitoring Pack that supports this version.
The tasks below need to be performed on the secondary node.
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 operation environment of the previous version of the AdvancedCopy Manager's manager.
Note that if step a and step b have already been performed, perform from step c.
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.
Mount the shared disk for shared data of ETERNUS SF Manager.
If it is mounted on the primary node, unmount it to mount on the secondary node.
Execute the following batch file to perform a restore of the previous version.
For backupDir, specify the directory in which the backup data is stored 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 backed up, it is unnecessary to specify a directory for the tmpDir.
dvdDrive:\Manager_windows\vuptools\esfpostinst_cluster.bat backupDir [tmpDir] -secondary
When the restore fails, after confirming the output error message and removing the cause of the failure, re-execute the batch file.
Point
Spaces and the characters " | : * ? / . < > , % & ^ = ! ; ( ) are not supported for directory names.
The number of characters in a directory name must be up to 220.
Unmount the shared disk for shared data of ETERNUS SF Manager.
If it is required for the work on the primary node, mount it on the primary node.
Eject the DVD media.
Uninstalling Symfoware
In the version level of this ETERNUS SF Manager, Symfoware is not used.
Symfoware should only be installed in cases where it was used by ETERNUS SF Manager only.
The procedures to uninstall Symfoware are stated below.
Uninstall Symfoware from the Add or Remove Programs or Programs and Features page.
If both Symfoware Server and Symfoware Client are installed, uninstall Symfoware Client first.
Point
If the ETERNUS VASA Provider was being used with the previous version
It is necessary to reinstall a version of the ETERNUS VASA Provider that supports this version.
If the Fujitsu ETERNUS Storage Systems Monitoring Pack was being used with the previous version
It is necessary to reinstall a version of the Fujitsu ETERNUS Storage Systems Monitoring Pack that supports this version.
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.
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.
Perform the following steps to start the local transactions on all the nodes.
Select Control Panel > Administrative Tools > Services to open the Windows Services screen.
Select "AdvancedCopy Manager COM Service" and then click Start.
Note
If operating Web Console from the same web browser as before the upgrade, delete the web browser's cache prior to operation.
Point
Once normal operation has been confirmed after the upgrade, the backup data in the backup destination directory created in step 8-c and step 12-d of "6.1.2.1 Preparing for Upgrade" maybe deleted.