This section describes how to upgrade a Tape Server that also operates as a Storage Server.
Implement steps 1 and 6 only if the Tape Server operates in a cluster.
9.4.2.1 Repository data backup
Save the repository data. Perform this step from the Storage Management Server.
9.4.2.2 Management information backup
Save the management information from the pre-update environment.
9.4.2.3 Tape management information backup
Save the tape management information from the pre-upgrade environment.
Delete the operating environment and uninstall the existing software product.
Install the new product and perform the environment setup.
9.4.2.6 Restore repository data
Restore the repository data that was backed up. Perform this step from the Storage Management Server.
9.4.2.7 Change server information
In order to guarantee data consistency, perform the server information change if necessary.
9.4.2.8 Restore management informationn
Restore the management information that was saved from the previous version.
9.4.2.9 Updating the version information
Update the tape server version information
9.4.2.10 Restore tape management information
Restore the tape management information that was saved from the previous version.
9.4.2.11 Set access path definitions
Set the definitions for the Tape Server access paths.
9.4.2.12 Customize the Tape Server
Recover the Tape Server environment configuration.
Note
If the configuration is changed at the time of the upgrade
If the server name, IP address, or port numbers of the Storage Management Server need to be changed during the upgrade, perform the above upgrade procedures, then perform the change tasks described in "Operating environment changes" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide".
Back up the repository data of the Storage Management Server.
For Windows edition
Use "DB backup" under DB setup to backup the data.
For Solaris and Linux editions
Use the stgdbbackup command to backup the data.
Refer to "Database backup" in the appropriate "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the procedure. Note that it is not an execution procedure of "Making a package backup of databases".
Back up the Storage Server management information.
Refer to "Backing up databases separately" under "Database maintenance" in the relevant operating system edition of the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the execution procedures.
Back up the tape server tape management information. The procedure is shown below.
Execute backup of the tape management information to the directory specified for the tape management information of the Tape Server. Refer to "Tape management information backup" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide Tape Backup Option" for details on the procedure.
Back up the tape manager-related definition files shown below.
/etc/opt/FJSVswstm/conf/devpath.conf
/etc/opt/FJSVswstm/conf/tsm.conf
/etc/opt/FJSVswstm/conf/tsmbkfile
/usr/bin/dsm.opt
/usr/bin/dsm.sys
Uninstall the Tape Server and the Storage Server. The procedure is as follows:
For non-cluster operation
Stop the Tape Server and Storage Server daemons. Refer to "Starting and stopping daemons" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option" for the execution procedure.
Uninstall the Tape Manager from the Tape Server. For procedures on Tape Manager uninstallation, refer to the appropriate sections of the following manuals.
AdvancedCopy Manager13.1 or later
Refer to "Uninstall" under "Tape Manager uninstallation" in the "ETERNUS SF AdvancedCopy Manager Installation Guide".
AdvancedCopy Manager13.0 or earlier
Refer to "Uninstall" under "Tape Manager Unsetup" in "Unsetup" of the "ETERNUS SF AdvancedCopy Manager Tape Backup Installation Guide".
Delete the manually created startup file.
# /usr/bin/rm -rf /opt/FJSVswstm/* /etc/opt/FJSVswst[mu]/* /var/opt/FJSVswst[mr]/* # /usr/bin/rm -rf /opt/FJSVswstm /etc/opt/FJSVswst[mu] /var/opt/FJSVswst[mr] # /usr/bin/rm -f /etc/init.d/initTSM /etc/rc0.d/K00tsmsv /etc/rc2.d/S99tsmsv |
Uninstall the agent of AdvancedCopy Manager from the Storage Server. For details, refer to the appropriate edition of the following manuals:
AdvancedCopy Manager13.1 or later
Refer to "Uninstall" under "Solaris/Linux/HP-UX/AIX" of "Agent Uninstallation" in the "ETERNUS SF AdvancedCopy Manager Installation Guide".
AdvancedCopy Manager13.0 or earlier
Refer to "Uninstall" under "Storage Server Unsetup" in "Unsetup" of the "ETERNUS SF AdvancedCopy Manager Installation Guide".
For cluster operation
If the Tape Server performs Tape Server tasks as cluster operations, cluster unsetup is required before performing uninstall.
Refer to "Tape Server task deletion" in the appropriate version edition of the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment" for the procedures for executing cluster unsetup.
Install the new version of AdvancedCopy Manager, and configure the operating environment. The procedure is as follows:
Installation
For non-cluster operation
Install the AdvancedCopy Manager Agent, which is mandatory software for the server to operate as a Storage Server. Refer to "Chapter 4 Installation of the Agent" for the installation procedure for AdvancedCopy Manager Agent.
Install the Tape Manager that is required for the server to operate as a Tape Server. Refer to "Chapter 7 Installation of Tape Manager" for the Tape Manager installation procedure.
For cluster operation
Refer to "Installing Tape Manager functions" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster operations" for the Tape Server and Storage Server installation procedures. Note that, when performing the "AdvancedCopy Manager installation" procedures under "Installing Tape Manager functions", the AdvancedCopy Manager Agent, which is mandatory software for a Storage Server, must be selected and installed.
Operating environment setup
For non-cluster operation
Refer to "Chapter 5 Customization of Storage Server" for the execution procedure.
For cluster operation
Refer to "Customizing Storage Management Server transactions and Storage Server transactions" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster operations" for the execution procedure.
Recover the backed up repository data of the Storage Management Server. Refer to "9.1.6 Restoring repository data" for the procedure.
In order to guarantee data consistency, use GUI client or stgxfwcmmodsrv (Server information change command) at a command prompt to change the server information.
Using GUI client
Select and right click the Storage server from the site view.
Select the [Modify] option from the context menu, the [Modify Storage Server] dialogue is displayed. Click the [OK] button without changing anything in the display.
For details on how to use the GUI client, refer to "Modify Storage Server Information" in the "ETERNUS SF AdvancedCopy Manager GUI Operator's Guide."
Using commands
Specify the name of the Storage Management Server in the -n option, and execute stgxfwcmmodsrv (Server information change command) at a command prompt.
Refer to "stgxfwcmmodsrv (Server information change command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for additional information.
Note
Changing the server information may fail due to the influence of the Java Plug-in cache. If changing the server information fails, use the following steps to clear the Java Plug-in cache at the GUI client, then re-execute the command. If the GUI client is running, clear the cache, then stop and restart the GUI client.
Select [Control Panel] then [Java Plug-in].
Select the [Cache] tab, then [Clear].
Recover the management information that was backed up for the Storage Server. Refer to "9.3.8 Restoring management information" for the execution procedure.
To update the Storage server version information use either the GUI client or stgxfwcmmodsrv (Server information change command). Make sure that cluster operations are not in use and that the repository data is restored in the replication management file.
Using GUI client
Select and right click the Storage server from the site view.
Select the [Modify] option from the context menu, the [Modify Storage Server] dialogue is displayed. Click the [OK] button without changing anything in the display.
For details on how to use the GUI client, refer to "Modify Storage Server Information" in the "ETERNUS SF AdvancedCopy Manager GUI Operator's Guide."
Using the command:
Execute stgxfwcmmodsrv (Server information change command) with the server name specified in the "-n" option.
For details on how to use the command, refer to "stgxfwcmmodsrv (Server information change command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide".
Note
An attempt to change server information may fail due to the effects of Java cache. If this is the case, follow the steps below to clear the cache (for the Java Plug-in) and then re-execute the command. If the GUI Client is running, clear the cache and then stop and re-start the GUI Client.
Select [Control Panel], then [Java Plug-in].
Select the [Cache] tab, then [Clear].
Restore the tape server tape management information. The procedure is shown below.
Note
In Cluster operation, the cluster setup must have been done before restoring the tape server tape management information.
Execute procedure 1 to 20 excluding procedure 11 and 19 refer to "Customizing Tape Server Transactions" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Make sure the following shared disks are mounted, then restore the tape management information.
The shared disk for AdvancedCopy Manager shared data
The shared disk for AdvancedCopy Manager repository
The shared disk for TSM
Restore the tape server tape management information. The procedure is shown below.
Recover the tape management information that was backed up for the Tape Server. Refer to "Restoring tape management information" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide Tape Backup Option" for the execution procedure.
Restore the backed up tape manager-related definition files shown below.
/etc/opt/FJSVswstm/conf/devpath.conf
/etc/opt/FJSVswstm/conf/tsm.conf
/etc/opt/FJSVswstm/conf/tsmbkfile
/usr/bin/dsm.opt
/usr/bin/dsm.sys
Updating TSM server daemon
Execute the following command to update the TSM server daemon information.
# TSMDB=<TSM database directory>; export TSMDB
# DSMSERV_DIR=/opt/tivoli/tsm/server/bin; export DSMSERV_DIR
# DSMSERV_CONFIG=$TSMDB/dsmserv.opt; export DSMSERV_CONFIG
# cd $TSMDB
# /opt/tivoli/tsm/server/bin/dsmserv UPGRADEDB
:
tsm: TAPESERVER1> halt
# /opt/tivoli/tsm/server/bin/dsmserv
:
tsm: TAPESERVER1> halt
|
After the command (dsmserv UPGRADEDB) execution, press the Enter key periodically (once per minute). When the prompt re-appears, the command is completed.
Then use the dsmserv command to check TSM server daemon started.
Set the definitions for the Tape Server access paths.
Note
This procedure is required only for an ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 operating environment.
If the conditions below apply, implement the "Access path recovery" procedures.
If the conditions below do not apply, implement the "Re-setting access path definitions" procedures.
The Tape Server operating system is not upgraded, and
GR multipath drivers will continue to be used after the upgrade.
Access path recovery
Execute tboactmplbext (Tape Server upgrade settings command).
# /opt/FJSVswstm/bin/tboactmplbext /etc/opt/FJSVmplb/conf/mplb_ext_active was created. # |
For cluster operation, execute the upgrade settings command on the active node that currently references shared volumes. This command does not need to be executed on the standby node.
Note
If the tboactmplbext command is executed by mistake
If the tboactmplbext command is executed in unsuitable conditions, the backup function may not operate correctly. In this case refer to "tboactmplbext (Tape Server upgrade settings command)" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option, to take the appropriate action.
Re-setting access path definitions
Re-create access paths and re-set the access path definitions.
Note
The following procedure is required only for the ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 access path.
If the access paths used before the upgrade meet the following conditions, only execute step 4 and subsequent steps:
A total of four access paths are set, two each from the disks of CM0 and CM1 disk array units, and
The access paths used before the upgrade will continue to be used.
Execution procedure
Recreate access path partitions
Refer to "Creating access path partitions" for the procedure.
Delete access path definition information
Delete the access path definition information that was used before the upgrade.
# rm -f /etc/opt/FJSVswstm/data/ctrl/.boxid_* # |
Reset the access path definition file
Refer to "Setting the access path definition file" for the procedure.
Inspect the definition file
Refer to "Definition file inspection" for the procedure.
ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 information collection.
Refer to "8.6.1.4 Collecting ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, and ETERNUS4000 information" for the procedure.
Recover the Tape Server environment settings.
For non-cluster operation
If the following conditions apply, execute from Step 3. If these conditions do not apply, execute from Step 1.
[Conditions]
If the ETERNUS disk storage systems and LUN configurations are not changed
[Execution procedure]
Inspect the definition file.
Refer to "8.6.1.3 Checking Definition Files" for the execution procedure.
Collect ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 information
Refer to "8.6.1.4 Collecting ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, and ETERNUS4000 information" for the execution procedure.
Note: This procedure is not required if ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 is not used.
Tape library driver settings
Refer to "8.7.1 Driver Configuration of Tape Library System" for the procedure.
Daemon automatic startup settings
Refer to "8.8 Configuring Automatic Activation of Daemons" for the execution procedure.
A pre-upgrade settings file for the TSM server daemon settings may exist. This procedure need not be executed if the file that is set by this procedure already exists.
TSM settings
TSM setting has to be same before upgraded. For details, refer to "8.9 TSM Configuration (the settings set after the daemon automatic start settings)".
For cluster operation
If the Tape Server performs Tape Server tasks as cluster operations, procedures for clusters are required.
Execute procedure 21 to 26, refer to "Customizing Tape Server Transactions" in the appropriate version of the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
The setting of procedure 24 "Set the TSM setting" has already been completed when restoring management information. Confirm that the setting is correct.
