Upgrading a Tivoli Storage Manager server from V5.5 to V6.1 or V6.2 in a Windows clustered environment

Product documentation


In a clustered environment running on a Windows operating system, you can upgrade a Tivoli Storage Manager server from V5.5 to V6.1 or V6.2. You must complete preparation tasks, such as backing up the database and key configuration files. Then, delete the V5.5 cluster resources, install the V6 server, and move the V5 data into the V6 database.


Tip: If you are upgrading the server to V6.2.5 or later, you can simplify the upgrade process by using a wizard. For instructions, see Upgrading the Tivoli Storage Manager server from V5.5 to V6.2.5 in a Windows clustered environment.

Before you begin
To prepare for the upgrade, complete the following steps:

2. Determine the upgrade method to use: network or media.
3. For the following steps, see the instructions in your selected upgrade scenario: From the primary node, complete the steps for your scenario from the "Preparing for the upgrade" section:
a. "Checking the prerequisites for the upgrade"
b. "Preparing space for the upgrade process"
c. "Modifying the server before the upgrade"
d. "Disabling sessions"

4. Back up the database. The preferred method is to use a snapshot backup, which provides a full database backup that does not interrupt scheduled 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.

5. 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.

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

backup volhistory filenames=

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 4. For example, issue the following 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.

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


Tip: Some steps in this procedure require you to run the Microsoft Management Console (MMC). The MMC initialization wizard formats and starts a Tivoli Storage Manager server. This process takes several minutes. If the server has not finished initializing, you might get the ANRU1203E error message. If you see this message, wait a few minutes for the server to initialize.

To upgrade the server to V6.1 or V6.2, complete the following steps:
1. Delete the V5.5 cluster resources:
    a. Ensure that the primary node owns the cluster resources.
    b. Use Windows Cluster Manager (Failover Cluster Manager for Windows Server 2008) to view the values of the TCP/IP address and network name resources in the group. Record these values. The cluster group includes Tivoli Storage Manager server resources and disk resources.
    c. Delete the Tivoli Storage Manager server and the network name. Only the shared disks and any shared tape resources remain in the cluster.

2. Install the upgrade package on the primary node:
3. Prepare the V5 server database for upgrade by issuing the DSMUPGRADE PREPAREDB command. Follow the instructions in Preparing the database of a V5 server for upgrade.

Repeat this step for each Tivoli Storage Manager instance.
4. If you are upgrading on the same system, delete the server instances from the MMC on each node in the cluster. Do not delete file or disk volumes, only the Service and Registry entries.
5. If you are upgrading on the same system, uninstall the V5.5 server. For details, see Uninstalling the V5 program on Microsoft® Windows® systems. Ensure that you uninstall the V5.5 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. Complete this step for each node in the cluster.
6. Remove the Tivoli Storage Manager server resource type from the cluster:
    a. Exit Microsoft Failover Cluster Manager.
    b. On one node in the cluster, on the command line, issue the following command:
    cluster resourcetype "TSM Server" /delete
7. On each node, delete the tsmsvrrsc DLL files from the Windows cluster directory:
For example, on a 64-bit system, delete the following files: TsmSrvRscExX64.dll and  
For example, on a 32-bit system, delete the following files: TsmSrvRscEx.dll and TsmSrvRsc.dll.

8. Edit the server options file, dsmserv.opt, to be used for the V6 server:
    a. Remove any options that are not supported for V6:
    b. Ensure that the server options file contains at least one VOLUMEHISTORY option and at least one DEVCONFIG option. A volume history file and a device configuration file are required when you restore the database.
    c. Check if the server options file includes the TXNGROUPMAX option. If the option is included and the value is less than 4096, consider increasing the value, or removing the option so that the server uses the new default value. The increased value can improve the performance for data movement operations such as storage pool migration and storage pool backup.
9. Install the V6 server on all nodes.

10. Prepare for upgrading the Tivoli Storage Manager server by creating the directories and the user ID for the V6 server instance. You must create the directories on shared disks that are accessible to the cluster. The user ID for the instance must be a domain ID. Complete this operation on only one node. 11. If you are using the media method, extract the data from the V5 server database.

Complete these steps from the instance directory.
12. Before you open the MMC to configure the server on the first node, ensure that the instance user ID can access the server options file, the device configuration file, and the volume history file.
Tip: For multiple instances, you must create the server instances in the same order as they were created originally. The MMC names the first server instance SERVER1, the second server instance SERVER2, and so on.
13. On the primary node, open the MMC and run the Initial Configuration Wizard.
Tip: If the “Initial Configuration Task List …” does not immediately open in the left pane, right-click the system under Tivoli Storage Manager and select Add a New TSM Server.

Proceed through the panels to configure the server. On the Server Service Logon Parameters panel, enter the domain user ID and password.

14. Remove the newly created database and load the previous database:
    a. Halt the Tivoli Storage Manager server. Review the services menu. If the server service is running, right-click the server and select Stop.
    b. Use the DSMSERV REMOVEDB utility to remove the newly created database.
    c. Empty the database, active log, mirror log, archive log, and archive failover log directories.
    d. Copy the updated dsmserv.opt file, the device configuration file, and the volume history file to the server instance directory.
    e. Issue the DSMSERV LOADFORMAT command from the instance directory. Specify the shared database and log directories.
15. Load the data into the database: Tip: For the network method, the DSMUPGRD EXTRACTDB command must specify the system IP address, not the cluster address.

16. Open the MMC and run the Cluster Configuration Wizard on the primary node. For each additional node in the cluster, move the resource group to the node and run the MMC cluster configuration wizard. When you finish running the wizard on the final node, the cluster configuration is complete.
17. Optional: To configure a new device, run the Device Configuration Wizard on the primary node.
18. After the server is upgraded, register licenses and verify that the upgrade is successful. The verification should include starting the server from the Failover Cluster Manager and backing up the database.
  • To verify that the server is configured for database backup, complete the following steps:
    a. Issue the db2set db2_vendor_ini command.
    b. Ensure that the DB2_VENDOR_INI value is set to the tsmdbmgr.env file.
  • If the server is not configured for database backup, follow the steps in your selected scenario to configure the system for database backup on Microsoft Windows.

19. Update the cluster to allow for failover and automatic starts.
20. Optional: Delete the disk storage pool volume that was created in the server instance directory by the V6 Initial Configuration Wizard.

Product Alias/Synonym


Document information

More support for:

Tivoli Storage Manager

Software version:

5.5, 6.1, 6.2, 6.2.2, 6.2.3, 6.2.4, 6.2.5

Operating system(s):


Reference #:


Modified date:


Translate my page

Content navigation