6.2.2 Upgrading on Clustered Systems

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.

Check that the cluster application (transaction) has stopped on the secondary node.
Check whether the cluster application (transaction) to which ETERNUS SF Manager belongs has stopped.
If not stopped, stop the cluster application (transaction).
Refer to the relevant cluster software manuals for information on stopping it (transaction).
Stop the cluster application (transaction) on the primary node.
Stop the cluster application (transaction) to which ETERNUS SF Manager belongs.
Refer to the relevant cluster software manuals for information on stopping it.
However, the shared disk for shared data of ETERNUS SF Manager must be mounted.
If Managed Server transactions coexist in a clustered system, perform the following.
1. On the secondary node for the target transactions, check that the Managed Server transactions have stopped.
  If not stopped, stop them on the secondary node.
  If multiple Managed Server transactions exist, perform this procedure for each secondary node for Managed Server transactions.
  Refer to the relevant cluster software manuals for information on stopping the Managed Server transactions.
2. On the primary node for the target transactions, stop the Managed Server transactions.
  Refer to the relevant cluster software manuals to stop the Managed Server transactions.
  However, the shared disk for shared data of Managed Server transactions must be mounted.
  If multiple Managed Server transactions exist, perform this procedure for each primary node for Managed Server transactions.
Stop the local transactions on all the nodes.
Stop the communication daemon for the local transactions of the AdvancedCopy Manager's manager.
Refer to "Starting and Stopping Communication Daemon" in the AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for this version for information on stopping the daemon.
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.
1. Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
2. Insert the DVD "ETERNUS SF SC/ACM Mediapack for Solaris (V16.9 or higher) Manager Program (2/2)" or "ETERNUS SF SC/ACM/Express Mediapack for Linux 64bit (V16.9 or higher) Manager Program (2/2)" of this version into the DVD drive.
3. Mount the DVD media.
  - Example for Solaris environments
```
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/dsk/c0t4d0s0".
  - Example for Linux environments
```
# mount -t iso9660 -r /dev/cdrom dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/cdrom".
4. Execute the following command 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.
```
# dvdMountPoint/Manager_unix/vuptools/esfpreinst_cluster.sh backupDir [tmpDir] -primary
```
  When the backup fails, after confirming the output error message and removing the cause of the failure, re-execute the command.
  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 under /var/opt. In the case of backup to a different location from that under /var/opt, it may take time to perform backup and restore.
5. Change to a directory other than the DVD media.
  Example:
```
# cd
```
6. Unmount the DVD media.
```
# umount dvdMountPoint
```
7. 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".
Required Disk Space for New 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.
Required Disk Space for Previous Version
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
The Symfoware product is bundled with this product. If Symfoware is already installed on the server where the upgrade is performed, check the Symfoware environment 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.
Confirming the port number for the communication service
Therefore, ensure the new ports are available 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 information on port numbers.
Perform the kernel parameter tuning on the primary node.
Therefore, perform the necessary kernel parameter tuning 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 information on tuning.
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.
1. Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
2. Insert the DVD "ETERNUS SF SC/ACM Mediapack for Solaris (V16.9 or higher) Manager Program (2/2)" or "ETERNUS SF SC/ACM/Express Mediapack for Linux 64bit (V16.9 or higher) Manager Program (2/2)" of this version into the DVD drive.
3. Mount the DVD media.
  - Example for Solaris environments
```
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/dsk/c0t4d0s0".
  - Example for Linux environments
```
# mount -t iso9660 -r /dev/cdrom dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/cdrom".
4. 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.
5. Execute the following command 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 the 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.
```
# dvdMountPoint/Manager_unix/vuptools/esfpreinst_cluster.sh backupDir [tmpDir] -secondary
```
  When the backup fails, after confirming the output error message and removing the cause of the failure, re-execute the command.
  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 under /var/opt. In the case of backup to a different location from that under /var/opt, it may take time to perform backup and restore.
6. 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.
7. Change to a directory other than the DVD media.
  Example:
```
# cd
```
8. Unmount the DVD media.
```
# umount dvdMountPoint
```
9. 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".
Required Disk Space for New 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.
Required Disk Space for Previous Version
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.
Confirming the port number for the communication service
Therefore, ensure the new ports are available 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 information on port numbers.
Perform the kernel parameter tuning on the secondary node.
Therefore, perform the necessary kernel parameter tuning 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 information on tuning.
In cases when Managed Server transactions coexist in the cluster system, move the AdvancedCopy Manager daemon start and stop script of the Managed Server transactions to a backup location.
On the primary node and the secondary node, move the AdvancedCopy Manager daemon start and stop script of the Managed Server transactions to a backup location.
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 unnecessary resources.
Note
- Do not uninstall the ETERNUS SF Manager.
- In cases when Managed Server transactions coexist, do not release the configurations of these Managed Server transactions.

6.2.2.2 Performing Upgrade (Primary Node)

Refer to "C.2 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 15.x (for Solaris, Linux)" 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.2.2.3 Performing Upgrade (Secondary Node)".

6.2.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.2.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.

In cases when Managed Server transaction coexist in the cluster system, recover the AdvancedCopy Manager daemon start and stop script of the Managed Server transaction evacuated in step 16 of "6.2.2.1 Preparing for Upgrade". On the primary node and the secondary node, recover the AdvancedCopy Manager daemon start and stop script of the Managed Server transaction.

6.2.2.4 Tasks to Be Performed After Upgrade (Primary Node)

The tasks below need to be performed on the primary node.

Stop the cluster application (transaction) to which ETERNUS SF Manager belongs. Refer to the relevant cluster software manuals for information on stopping it.
However, the shared disk for shared data of ETERNUS SF Manager must be mounted.
If Managed Server transactions coexist in the clustered system, edit the environment setting files for AdvancedCopy Manager on the shared disk for shared data of Managed Server transactions, on the primary node for a target service.
On the primary node for target transactions, edit the following files:
- <Mount point of shared disk for shared data of Managed Server transaction>/etc/opt/swstorage/clsetup.ini
- <Mount point of shared disk for shared data of Managed Server transaction>/etc/opt/swstorage/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 through step c have already been performed, perform from step d.
1. Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
2. Insert the DVD "ETERNUS SF SC/ACM Mediapack for Solaris (V16.9 or higher) Manager Program (2/2)" or "ETERNUS SF SC/ACM/Express Mediapack for Linux 64bit (V16.9 or higher) Manager Program (2/2)" of this version into the DVD drive.
3. Mount the DVD media.
  - Example for Solaris environments
```
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/dsk/c0t4d0s0".
  - Example for Linux environments
```
# mount -t iso9660 -r /dev/cdrom dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/cdrom".
4. Execute the following command 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.
```
# dvdMountPoint/Manager_unix/vuptools/esfpostinst_cluster.sh backupDir [tmpDir] -primary
```
  When the restore fails, after confirming the output error message and removing the cause of the failure, re-execute the command.
  Point
  - Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory names.
  - The number of characters in a directory name must be up to 220.
5. Change to a directory other than the DVD media.
  Example:
```
# cd
```
6. Unmount the DVD media.
```
# umount dvdMountPoint
```
7. Eject the DVD media.
Start the cluster application (transaction) to which ETERNUS SF Manager belongs.
Refer to the relevant cluster software manuals for information.
In cases when Managed Server transactions coexist in the cluster system, change the server information of the Managed Server transactions.
To ensure data consistency, use the "stgxfwcmmodsrv" command to change the server information.
When executing the "stgxfwcmmodsrv" command, specify the Management Server name for the -n option.
```
# /opt/FJSVswstf/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 the operating system of the Management Server 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.
```
# /opt/FJSVesfcm/bin/esfadm devconf import -all
```
After executing the "esfadm devconf import" command, confirm that "Complete" is displayed in IMPORT STATUS column in the "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.
Symfoware should only be installed in cases where it was used by ETERNUS SF Manager only.
The procedures to uninstall Symfoware are stated below.
1. Start the uninstaller of Symfoware to delete the Symfoware package.
  Before deleting the package, confirm that none of the package functions used by any system other than ETERNUS SF Manager.
```
# /opt/symfoware/setup/symfo_remove
```
2. Confirmation message to uninstall Symfoware is displayed. To perform the uninstallation, enter "y". To cancel the process, enter "q".
  When "y" is entered, a message allowing to select the function to uninstall is shown. Input "all" or "number to delete" to select the function to uninstall.
  A message to re-confirm uninstallation appears. Enter "y" to perform the uninstallation and "q" when it is not required.
  Example of Uninstallation with the Specification "all"
```
Start checking the installation environment.
Check of installation environment is ended.

WARNING: There is a possibility that another product uses "Symfoware Server Enterprise Edition".

Continue the uninstallation?
y: Continue the uninstallation
q: End directly without uninstallation
[y,q]: y

Uninstallation of "Symfoware Server Enterprise Edition" begins.

Please select the functions to be uninstalled.
1: Base function (Server function, Client function)
Separate multiple selections with ",". (Example: 1, 2)
[all:All functions,1,q]: all

Selected functions
- Base function (Server function, Client function)

Start the uninstallation of the above functions?
y: Uninstallation begins
n: Select the functions again
q: End directly without uninstallation
[y,n,q]: y

Uninstallation begins.
```
3. The following message is displayed after the Symfoware uninstallation is completed normally.
```
Uninstallation of "Symfoware Server Enterprise Edition" is ended normally.
```
4. When FSUNiconv package is installed, delete it (only in Solaris environments).
  Delete after confirming that this package function is used only by ETERNUS SF Manager.
```
# pkgrm FSUNiconv
```

6.2.2.5 Tasks to Be Performed After Upgrade (Secondary Node)

Descriptive Contents of Version Information
Before	After
Version=V15.x	Version=V16.9

The tasks below need to be performed on the secondary node.

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).
Restore the operation environment of the previous version of the AdvancedCopy Manager's manager.
Note that if step a through step c have already been performed, perform from step d.
1. Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
2. Insert the DVD "ETERNUS SF SC/ACM Mediapack for Solaris (V16.9 or higher) Manager Program (2/2)" or "ETERNUS SF SC/ACM/Express Mediapack for Linux 64bit (V16.9 or higher) Manager Program (2/2)" of this version into the DVD drive.
3. Mount the DVD media.
  - Example for Solaris environments
```
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/dsk/c0t4d0s0".
  - Example for Linux environments
```
# mount -t iso9660 -r /dev/cdrom dvdMountPoint
```
    The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/cdrom".
4. 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.
5. Execute the following command 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.
```
# dvdMountPoint/Manager_unix/vuptools/esfpostinst_cluster.sh backupDir [tmpDir] -secondary
```
  When the restore fails, after confirming the output error message and removing the cause of the failure, re-execute the command.
  Point
  - Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory names.
  - The number of characters in a directory name must be up to 220.
6. 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.
7. Change to a directory other than the DVD media.
  Example:
```
# cd
```
8. Unmount the DVD media.
```
# umount dvdMountPoint
```
9. Eject the DVD media.
Symfoware should only be installed in cases where it was used by ETERNUS SF Manager only.
The procedures to uninstall Symfoware are stated below.
1. Start the uninstaller of Symfoware to delete the Symfoware package.
  Before deleting the package, confirm that none of the package functions used by any system other than ETERNUS SF Manager.
```
# /opt/symfoware/setup/symfo_remove
```
2. Confirmation message to uninstall Symfoware is displayed. To perform the uninstallation, enter "y". To cancel the process, enter "q".
  When "y" is entered, a message allowing to select the function to uninstall is shown. Input "all" or "number to delete" to select the function to uninstall.
  A message to re-confirm uninstallation appears. Enter "y" to perform the uninstallation and "q" when it is not required.
  Example of Uninstallation with the Specification "all"
```
Start checking the installation environment.
Check of installation environment is ended.

WARNING: There is a possibility that another product uses "Symfoware Server Enterprise Edition".

Continue the uninstallation?
y: Continue the uninstallation
q: End directly without uninstallation
[y,q]: y

Uninstallation of "Symfoware Server Enterprise Edition" begins.

Please select the functions to be uninstalled.
1: Base function (Server function, Client function)
Separate multiple selections with ",". (Example: 1, 2)
[all:All functions,1,q]: all

Selected functions
- Base function (Server function, Client function)

Start the uninstallation of the above functions?
y: Uninstallation begins
n: Select the functions again
q: End directly without uninstallation
[y,n,q]: y

Uninstallation begins.
```
3. The following message is displayed after the Symfoware uninstallation is completed normally.
```
Uninstallation of "Symfoware Server Enterprise Edition" is ended normally.
```
4. When FSUNiconv package is installed, delete it (only in Solaris environments).
  Delete after confirming that this package function is used only by ETERNUS SF Manager.
```
# pkgrm FSUNiconv
```