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 Managed Server transactions
Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
Check that Managed Server transactions are stopped on the secondary node.
If not stopped, stop them on the secondary node. Refer to the relevant cluster software manuals for information on stopping it.
If multiple Managed Server transactions exist, perform this procedure on each secondary node for Managed Server transactions.
Stop the Managed Server transaction on the primary node.
Stop the Managed Server transactions by referring to the relevant cluster software manuals.
However, the shared disk for shared data of Managed Server transactions must be mounted.
If multiple Managed Server transactions exist, perform this procedure on each primary node for Managed Server transaction.
Execute the following command to stop the local transactions on all the nodes.
# /opt/swstorage/bin/stopacm
Perform a backup of the previous version with all of the nodes.
For recovery in case the upgrade fails, perform a backup of the operating environment of the previous version of the AdvancedCopy Manager's agent.
On the primary node and the secondary node, perform a backup of the previous version.
In cases when there are multiple Managed Server transactions, in each primary node of the Managed Server transactions, switch the shared disk for the shared data of the Managed Server transactions online.
Information
The capacity required for performing the backup is the total value of the following:
Fixed configuration directory and Modifying configuration directory of "For Solaris environments" or "For Linux environments" under "Required disk space for installation" in the Installation and Setup Guide
"For Solaris, Linux, HP-UX or AIX environments" under "Required disk space for operation" in the Installation and Setup Guide
In the case of a primary node operating a Managed Server transaction, add the following to the capacity required to perform the backup:
"Capacity of Shared Disk" in the Cluster Environment Setup Guide
The procedure is shown below:
Insert the DVD "ETERNUS SF SC/ACM/Express Mediapack (V16.9 or higher) Agent Program and Manual" of this version into the DVD drive.
Mount the DVD media.
Example for Solaris environments
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPointThe 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 dvdMountPointThe 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".
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.
When using the Solaris Agent
# dvdMountPoint/Agent_unix/AdvancedCopy_Manager/Solaris/esfacmapreinst.sh backupDir
When using the Red Hat Enterprise Linux 8 Agent
# dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel8_x64/esfacmapreinst.sh backupDir
When using the Red Hat Enterprise Linux 7 Agent
# dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel7_x86/esfacmapreinst.sh backupDir
When using the Red Hat Enterprise Linux 6 Agent
# dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel6_x86/esfacmapreinst.sh backupDir
When the backup fails, after confirming the output error message and removing the cause of the failure, re-execute the command.
Execute the following commands, and then eject the DVD media.
# cd /
# umount dvdMountPointOn the primary node and the secondary node, back up the AdvancedCopy Manager daemon start and stop script of the Managed Server transactions.
Note that if step 1 through step 3 have already been performed, perform from step 4.
Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
Insert the DVD "ETERNUS SF SC/ACM/Express Mediapack (V16.9 or higher) Agent Program and Manual" of this version into the DVD drive.
Mount the DVD media.
Example for Solaris environments
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPointThe 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 dvdMountPointThe 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".
Execute the following commands to install the AdvancedCopy Manager's agent.
# cd environmentDir
# ./swsetupThe environmentDir is as follows.
OS Type | Directory |
|---|---|
Solaris | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/Solaris |
Red Hat Enterprise Linux 8 (for Intel64) | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel8_x64 |
Red Hat Enterprise Linux 7 (for Intel64) | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel7_x86 |
Red Hat Enterprise Linux 6 (for Intel64) | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel6_x86 |
The installation information is displayed.
swsetup: Installer is preparing for installation... +-----------------------------------------------------------+ | ETERNUS SF AdvancedCopy Manager | | 16.9 | | Copyright FUJITSU LIMITED 2013-2021 | +-----------------------------------------------------------+ Welcome to Setup. This program will install "AdvancedCopy Manager" on your system.
A confirmation message is displayed before uninstalling the previous version. To uninstall the previous version and proceed with the new installation, enter "y". To cancel the installation, enter "q". Press Enter.
An old version is installed in this system. Do you want to upgrade? [y,q]:
If "y" was entered for step 6, the upgrade continues.
If the upgrade completes successfully, the following message is displayed.
swsetup: AdvancedCopy Manager was installed successfully.
Execute the following commands, and then eject the DVD media.
# cd /
# umount dvdMountPointWhen the tasks described above have been performed, the upgrade of the AdvancedCopy Manager's agent is complete.
When the upgrade of the primary node has been completed, refer to "7.4.2.4 Tasks to Be Performed After Upgrade (Primary Node)" and set up the AdvancedCopy Manager's agent of the primary node.
When the upgrade of the secondary node has been completed, refer to "7.4.2.7 Tasks to Be Performed After Upgrade (Secondary Node)" and set up the AdvancedCopy Manager's agent of the secondary node.
Point
If the upgrade was terminated abnormally, refer to "8.2.6 In Case of Problem During Upgrade of AdvancedCopy Manager's Agent (for Solaris, Linux)" to recover the system to the normal state.
Note that if step 1 through step 3 have already been performed, perform from step 4.
Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
Insert the DVD "ETERNUS SF SC/ACM/Express Mediapack (V16.9 or higher) Agent Program and Manual" of this version into the DVD drive.
Mount the DVD media.
Example for Solaris environments
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPointThe 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 dvdMountPointThe 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".
Execute the following commands for the silent installation to install the AdvancedCopy Manager's agent.
For installLogFile, specify the file in which to output installation log with an absolute path. It is optional to specify for installLogFile.
# environmentDir/acmagtsilentinstall.sh [-l installLogFile]
The environmentDir is as follows.
OS type | Directory |
|---|---|
Solaris | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/Solaris |
Red Hat Enterprise Linux 8 (for Intel64) | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel8_x64 |
Red Hat Enterprise Linux 7 (for Intel64) | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel7_x86 |
Red Hat Enterprise Linux 6 (for Intel64) | dvdMountPoint/Agent_unix/AdvancedCopy_Manager/rhel6_x86 |
Point
If nothing is specified for installLogFile, an install log file named "acmagtsilentinstall.log" is created in /var/tmp directory.
If there is any file of the same name as the specified install log file, it is overwritten.
It is required to specify an existing directory with write permission for the directory in which to store the install log file. If it has no write permission, no error message is output in the command prompt or screen and the process terminates with error.
Note
If an invalid option is specified, its corresponding error message is output in the install log file and the process exits. No error message is output in the command prompt or screen.
Do not execute multiplexly the command for silent installation. If it is multiplexly executed, the command executed after that terminates abnormally. At this time, an install log file is not created.
During an update, it is not possible to specify an installation parameter file for the command. In the case that a file has been specified, the command terminates in an error.
On completion of installation, a command prompt is displayed.
Execute the following commands, and then eject the DVD media.
# umount dvdMountPointCheck the return value from the silent installation command. If necessary, check the install log file. However, if the return value from the silent installation command is 3 or 9, an install log file is not created. For details, refer to "Return Values for Silent Installation (for AdvancedCopy Manager's Agent)" in the Installation and Setup Guide.
The installation result can be viewed in the install log file, too.
Open the install log file to see "ResultCode" in the ResponseResult section. In "ResultCode" is written the return value from the silent installation command.
Point
If the upgrade was terminated abnormally, refer to "8.2.6 In Case of Problem During Upgrade of AdvancedCopy Manager's Agent (for Solaris, Linux)" to recover the system to the normal state.
The tasks below need to be performed.
When the AdvancedCopy Manager's agent upgrade has been completed for the primary node, perform the following procedure.
If multiple Managed Server transactions exist, perform this procedure on each primary node for Managed Server transaction.
Edit the following environment setting files for Managed Server transaction on the shared disk for shared data:
<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=V16.x | Version=V16.9 |
Note
Do not change anything other than the version information.
Perform the upgrade for the secondary node.
The upgrade procedure is the same as that for the primary node. Refer to "7.4.2.2 Performing Upgrade (Primary Node)".
Point
If this secondary node acts as a primary node for other Managed Server transactions, it is upgraded as a primary node, so this procedure is not needed.
Perform the upgrade with silent installation for the secondary node.
The upgrade with silent installation procedure is the same as that for the primary node. Refer to "7.4.2.3 Upgrade with Silent Installation Tasks (Primary Node)".
Point
If this secondary node acts as a primary node for other Managed Server transactions, it is upgraded as a primary node, so this procedure is not needed.
No operation is required after upgrade at the secondary node.
Perform the following procedure:
Note that in these tasks, in addition to operations with the Managed Server, there are operations to execute from the Management Server and Web Console.
Start the Managed Server transactions on the primary node.
Refer to the relevant cluster software manuals to start the Managed Server transactions.
If multiple Managed Server transactions exist, perform this procedure for each Managed Server transaction.
Perform the following command to start the local transactions on all the nodes.
# /opt/swstorage/bin/startacm
To ensure data consistency, with the Management Server, execute the "stgxfwcmmodsrv" command to change the server information.
When executing the "stgxfwcmmodsrv" command, specify the Managed Server name for the -n option.
When the Management Server OS is Windows
$INS_DIR\ACM\bin\stgxfwcmmodsrv -n serverName$INS_DIR means the "Program Directory" specified at the ETERNUS SF Manager installation.
When the Management Server OS is Solaris or Linux
/opt/FJSVswstf/bin/stgxfwcmmodsrv -n serverNameIf multiple Managed Server transactions exist, perform this procedure for each Managed Server transaction.
In addition, if there is any node that is running local transactions, perform this procedure on the relevant node.
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 relevant to the OS of the Management Server for information on the command.
Perform the following operations with Web Console to reload the server information.
On the global navigation tab, click Server.
The registered server list is displayed in the Main pane.
On the Main pane, check the target server checkbox.
If the target server is a VM guest, check the checkbox of the VM host where the VM guest exists.
On the Action pane, click Reload Conf. under Server.
Point
Once normal operation has been confirmed after the upgrade of the AdvancedCopy Manager's agent, the backup data in the backup destination directory created in step 5-d of "7.4.2.1 Preparing for Upgrade" maybe deleted.