Upgrading Tivoli Storage Manager on AIX from V5 to V6 in a clustered environment

Product documentation


Abstract

To upgrade a Tivoli Storage Manager server from V5 or later to V6 or later in an AIX clustered environment, you must move all server instances to the primary node. Then, upgrade each V5 server database instance on the primary node to V6. On each secondary node, install the V6 server and complete configuration tasks.

Content


To upgrade a Tivoli Storage Manager server from V5 or later to V6 or later in a clustered environment on an AIX operating system, complete the following steps:

1. Move all Tivoli Storage Manager server instances to the primary node in the cluster.

Complete Steps 2 - 5 for every Tivoli Storage Manager server instance in this environment.

2. Back up the database. The preferred method is to use a snapshot backup, which provides a full database backup without interrupting scheduled database backups.

The device class that you specify must exist and have volumes that are available to it. For example, to perform a snapshot backup of your database to the TAPECLASS device class by using scratch volumes, enter the Tivoli Storage Manager administrative command:

    backup db type=dbsnapshot devclass=tapeclass

To use specific volumes instead of scratch volumes, specify the volume names in the command.

If the upgrade fails, and you must revert the server to the previous level, you will need the database backup and the configuration files that you save in the next steps. By using the database backup and the configuration files, you might be able to revert the server to the previous level. Consider making two copies of the database backup to protect the backup from media failures. Ensure that at least one full database backup is available onsite. If you must restore the database after a failed upgrade, having an onsite backup database saves time.

3. Back up device configuration information by using the Tivoli Storage Manager administrative command:
    backup devconfig filenames= file_name

    where file_name specifies the name of the file in which to store device configuration information.

4. Back up volume history information by using the Tivoli Storage Manager administrative command:

    backup volhistory filenames=
    file_name

    where file_name specifies the name of the file in which to store the volume history information.
Ensure that the volume history includes information about the database backup that you completed in Step 2. For example, issue the command:
    query volhistory type=dbbackup

Review the query output to verify that the timestamp for the database backup matches the actual time of the backup.

5. Save copies of the following files, which are in the server instance directory:
  • The server options file, typically named dsmserv.opt
  • dsmserv.dsk

The dsmserv.dsk file is not available in Tivoli Storage Manager V6.3 or later. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.

6.  Install the upgrade package on the primary node. For instructions, see Scenario 1: Installing the upgrade utilities on AIX systems.

7. Prepare the V5 server database for upgrade by issuing the DSMUPGRADE PREPAREDB command. For instructions, see Scenario 1: Preparing the database of a V5 server for upgrade.

Repeat this step for each Tivoli Storage Manager instance.

8. On the primary node, uninstall the V5 server, server license, and device driver. Do not remove the database, recovery log, or any other related files or directories, such as the server options file.
  • For a V5.4 or V5.5 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license.aix5.rte64
/usr/sbin/installp -ug tivoli.tsm.devices.aix5.rte
/usr/sbin/installp -ug tivoli.tsm.server.aix5.rte64
  • For a V5.3 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license
/usr/sbin/installp -ug tivoli.tsm.devices
/usr/sbin/installp -ug tivoli.tsm.server


9. On the primary node, upgrade each V5 server database instance to V6 by using the dsmupgdx upgrade wizard or by completing the manual procedure.

For instructions about running the wizard, see Upgrading the server by using the upgrade wizard.
For instructions about completing the manual procedure, see Upgrading the server manually by using utilities.

During this step, you define and format the V6 database instance, extract the data from the V5 server database, and load the data into the V6 database.

Repeat this step for each Tivoli Storage Manager instance.

10. Mount all shared resources on the secondary node. If your environment includes multiple instances of Tivoli Storage Manager, shared resources for all instances must be accessible to the secondary node.

11. On the secondary node, for each Tivoli Storage Manager instance, create an instance user ID that is identical to that on the primary node.

12. For each instance user ID, ensure that a home directory is created and that the user has permissions to write to it. For details, see Server naming best practices.

13. On the secondary node, uninstall the V5 server.
  • For a V5.4 or V5.5 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license.aix5.rte64
/usr/sbin/installp -ug tivoli.tsm.devices.aix5.rte
/usr/sbin/installp -ug tivoli.tsm.server.aix5.rte64
  • For a V5.3 server, issue the following commands:
/usr/sbin/installp -ug tivoli.tsm.license
/usr/sbin/installp -ug tivoli.tsm.devices
/usr/sbin/installp -ug tivoli.tsm.server



14. On the secondary node, install the V6 server: 15. To configure a server instance on the secondary node, select Method A for a shared DB2 instance or Method B for a separate DB2 instance.

Method A
To configure a server instance on a secondary node with a shared DB2 instance, complete the following steps:
a. On each node in the cluster, add the following text to the /opt/tivoli/tsm/server/bin/rc.dsmserv script:

DB2NODES_TEMP='/tmp/db2nodes.tmp'
DB2NODES=${homeDir}/sqllib/db2nodes.cfg
Current hostname
HOSTNAME=$(/bin/hostname)
hostname saved in db2nodes.cfg
DB2_HOST=$(cat $DB2NODES | cut -d ' ' -f 2)
if the are different update the file
if [[ "$HOSTNAME" != "$DB2_HOST" ]]
then
  echo "Updating hostname in db2nodes.cfg"
  sed -e s_${DB2_HOST}_${HOSTNAME}_g $DB2NODES > $DB2NODES_TEMP
  cp $DB2NODES_TEMP $DB2NODES
fi

Tip: If the text is not included in the script, you can include it before you issue the /opt/tivoli/tsm/server/bin/rc.dsmserv script.
b. Move all shared resources to the secondary node.
c. Update the variables in the /opt/tivoli/tsm/server/bin/startserver script by using the following values:
Description Variable Example
Set the INST_USER to the instance user ID. INST_USER INST_USER='tsmuser1'
Set the INST_DIR to the location of the Tivoli Storage Manager instance directory.
This directory includes the dsmserv.dbid and dsmserv.opt files.
INST_DIR INST_DIR='/home/tsmuser1/tsminst1'
Select one of the following startup options:

Option 1: Use instance $INST_USER, but run the server with the root user ID (-U).

Option 2: Use instance $INST_USER and run the server as $INST_USER (-u).
INST_OPTION Option 1:
INST_OPTION='-U $INST_USER'

Option 2:
INST_OPTION='-u $INST_USER'


Method B
To configure a server instance on a secondary node with a separate DB2 instance, complete the following steps.

Tip: You must create a DB2 instance on each secondary node if the DB2 instance directory, /home/tsminst1/sqllib, is not shared between the nodes in the PowerHA cluster.

You can configure the Tivoli Storage Manager server on a secondary node by using the dsmicfgx wizard or manually:
• To create a DB2 instance on a secondary node by using the dsmicfgx wizard, complete the following steps:
a. Run the dsmicfgx wizard.
b. From the Instance Directory panel, select the Check this if you are configuring the server instance on a secondary node of a high availability cluster check box.

• To manually create a DB2 instance on a secondary node, complete the following steps:
a. Move all shared resources to the secondary node.
b. Create a DB2 instance by issuing the following db2icrt command:
/opt/tivoli/tsm/db2/instance/db2icrt -s ese -u <instance_user> <instance_user>
where <instance_user> is the user that owns the DB2 instance on the primary node.
c. When the DB2 instance is created, log in with the instance user ID or by issuing the su command:
su - <instance_user>
d. As the instance user, issue the following commands:
db2start
db2 update dbm cfg using DFTDBPATH <shared_db_path>
db2 catalog db TSMDB1
dbset -i <instance_user> DB2CODEPAGE=819
db2stop
where <shared_db_path> is the shared database directory. The shared database directory is typically the server instance directory.
Tip: To determine the <shared_db_path> value, issue the following command on the primary node:
db2 get dbm cfg | grep DFTDBPATH
e. Update the variables in the /opt/tivoli/tsm/server/bin/startserver script by using the following values:

Description Variable Example
Set the INST_USER to the instance user ID. INST_USER INST_USER='tsmuser1'
Set the INST_DIR to the location of the Tivoli Storage Manager instance directory.
This directory includes the dsmserv.dbid and dsmserv.opt files.
INST_DIR INST_DIR='/home/tsmuser1/tsminst1'
Select one of the following startup options:

Option 1: Use the instance $INST_USER, but run the server with the root user ID (-U).

Option 2: Use instance $INST_USER and run the server as $INST_USER (-u).
INST_OPTION Option 1:
INST_OPTION='-U $INST_USER'

Option 2:
INST_OPTION='-u $INST_USER'


16. For any additional secondary nodes, repeat Steps 10 - 15. Then, move all resources to the primary node and start the server by issuing the following script:
/opt/tivoli/tsm/server/bin/startserver

17. To ensure that the data is successfully backed up, issue the BACKUP DB command.

Product Alias/Synonym

TSM

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager
Server

Software version:

All Supported Versions

Operating system(s):

AIX

Reference #:

7020691

Modified date:

2013-11-13

Translate my page

Machine Translation

Content navigation