The operational environment must be prepared prior to upgrading the Storage Cruiser's manager, as described below.
Back up the Storage Cruiser's manager operational environment using the following procedure:
Note
The iSCSI HBA information cannot be backed up. Save the current settings information into an appropriate file.
Refer to the iSCSI port property information in the resource view of the previous version of Storage Cruiser.
Performance management information is not backed up. If performance monitoring is being performed, take a note of current settings.
Refer to the following information on an earlier-version GUI client:
Settings for performance monitoring
Interval before obtaining performance information (in seconds)
Performance monitoring target (only for ETERNUS Disk storage system. Minimum LUN_V, Maximum LUN_V)
Settings for threshold monitoring (if threshold monitoring is performed)
Settings for the Threshold Monitoring time
Threshold Monitoring time (Start Time/Stop Time), Alarm Display time (Start Time/Stop Time), Alarm Display frequency
Settings for the Threshold Monitoring
Threshold Monitoring target, Threshold, Unit of the Threshold Monitoring time, Alarm allowable range, Alarm allowable time, Lower limit
Stop the Storage Cruiser's manager.
For Windows:
From the Services screen, stop the ETERNUS SF Storage Cruiser Manager.
For Solaris or Linux:
Execute the following command:
# /opt/FJSVssmgr/sbin/managerctl stop
See
Refer to the ETERNUS SF Storage Cruiser User's Guide for the relevant previous version for information on stopping the Storage Cruiser's manager.
Back up the operational environment for the previous version of Storage Cruiser's manager, referring to the following locations in the ETERNUS SF Storage Cruiser Operation Guide for this version.
For Windows:
Perform steps 4 to 10 of "Backup of Windows Manager". In step 4, perform "Upgrade from a previous version".
Note
The file or directory names of the copy source that are described in steps 5 to 10 of "Backup of Windows Manager" differ to those of the previous version.
The following table shows the relationship between the previous and current file and directory names.
Description in "Backup of Windows Manager" | Path names of the previous version |
|---|---|
$TMP_DIR\ESC\Manager\var\opt\FJSVssmgr\... | $TMP_DIR\Manager\var\opt\FJSVssmgr\... |
$ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\... | $ENV_DIR\Manager\etc\opt\FJSVssmgr\... |
$INS_DIR\ESC\Manager\opt\FJSVssmgr\... | $INS_DIR\Manager\opt\FJSVssmgr\... |
For Solaris or Linux:
Perform steps 4 to 10 in "Backup of Solaris OS Manager". In step 4, perform "Upgrade from a previous version".
AdvancedCopy Manager operational environment
When AdvancedCopy Manager is installed, backup the AdvancedCopy Manager operational environment.
Note
The following information cannot continue to be used.
User account for the GUI client
See
Refer to the following table to back up the operational environment.
Server type | OS | Reference |
|---|---|---|
Storage Management Server | Windows | |
Solaris, | ||
Storage Management Server which also serves as a Storage Server | Windows | Perform the steps in the following order: |
Solaris, | Perform the steps in the following order: |
AdvancedCopy Manager Copy Control Module operational environment
When AdvancedCopy Manager Copy Control Module is installed, backup the AdvancedCopy Manager Copy Control Module operational environment.
See
Refer to "A.6 Backing up the the environment setting files" for information on performing a backup.
License information
When AdvancedCopy Manager and/or AdvancedCopy Manager Copy Control Module are installed, backup the definition of the license information.
Back up the license management database of ETERNUS SF License Manager by executing the esflm backup command. Refer to the ETERNUS SF AdvancedCopy Manager Installation and Setup Guide for the previous version for information on the command.
Example of executing the command is shown below. The file specified for backupFileName will be created as a backup file.
> esflm backup backupFileName
Backup of license database was performed successfully |
Ensure that there is enough available disk space on the server where the upgrade will be performed.
The required disk space for the upgrade is calculated as the "Required disk space for the new version to be installed" minus the "Required disk space for the previous version".
The space required to install this version of the ETERNUS SF Manager.
Refer to "Operating environment of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on the required disk space.
The space required to install the previous version of the Storage Cruiser's manager.
Refer to the ETERNUS SF Storage Cruiser Installation Guide for the relevant previous version for information on the required disk space.
Check if any incompatible software for this version of the ETERNUS SF Manager is installed on the server where the upgrade will be 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 ETERNUS SF Installation and Setup Guide for this version for information on the incompatible software.
The Symfoware product is bundled with this product. If Symfoware is already installed on the server where the upgrade will be performed, check the Symfoware environment before starting the upgrade.
See
Refer to "Before installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for details.
A database is necessary for this version of Storage Cruiser.
The database size must be estimated before starting the upgrade.
See
Refer to "Before installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for details.
This version of the Storage Cruiser's manager requires registration of the repository access user.
Therefore, register the repository access user before starting the upgrade.
See
Refer to "Installation procedure" in the Software Release Guide for information on registering a user name and password.
Kernel parameter tuning must be performed in order to use this version of the Storage Cruiser's manager. Therefore, perform the necessary kernel parameter tuning before starting the upgrade.
See
Refer to "Before installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on tuning.
This version of the AdvancedCopy Manager's manager uses additional ports.
Therefore, ensure the new ports are available before starting the upgrade.
See
Refer to "Before installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on port numbers.
If AdvancedCopy Manager is installed, before starting the upgrade, the following preparation is necessary before uninstalling the previous version.
Cancel the configuration information for the Web Server (for using AdvancedCopy Manager Version 13.x on Windows Server 2003 only).
Cancel the Web Server configuration information as follows:
Log on to the system using Administrator privileges to uninstall AdvancedCopy Manager.
If you configured the Web Server during the previous installation, cancel the Web Server configuration information.
Execute the following command.
C:\> programDir\bin\alias -uRefer to "Web server setting and setting cancellation command (alias)" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for the relevant previous version for information on the command.
Stop the daemon (for Solaris or Linux).
Execute the following command to stop the daemon of AdvancedCopy Manager on the Management Server (Storage Management Server).
# /opt/swstorage/bin/stopacm
Execute the DB unsetup.
Refer to the following sections to perform the repository database unsetup of the previous version:
For Windows:
For Solaris or Linux:
Uninstall Symfoware.
Uninstall Symfoware if the Symfoware Server that was bundled with the previous version of AdvancedCopy Manager for Windows Server 2003 is being used.
From the Control Panel, use the Add or Remove Programs or Programs and Features function to uninstall Symfoware.
If you have installed both the Symfoware Server and the Symfoware Server Client, uninstall the Symfoware Server Client first.
For clustered systems
For clustered systems, execute cluster unsetup before uninstallation.
See
Refer to "Cluster environment deletion" in the ETERNUS SF Storage Cruiser Installation Guide for the relevant previous version for information on the cluster unsetup procedure.