Applying a fix pack to Tivoli Storage Manager Version 6 on a Windows operating system in a clustered environment

Product documentation


Abstract

To install a fix pack on a Tivoli Storage Manager V6 server running on a Windows operating system in a clustered environment, complete preparation tasks such as backing up the server database and key configuration files. Then, install the fix pack.

Content

Tip: To install a fix pack or interim fix to the server, install the Tivoli Storage Manager server component at the level on which you want to run it. You do not have to start the server installation at the base release level. For example, if you have V6.1.2.1 installed, you can go directly to the latest fix pack for V6.3. You do not have to start with the V6.3.0 installation if a maintenance update is available.

Before you upgrade the Tivoli Storage Manager server, ensure that you retain the Tivoli Storage Manager server base release installation media from the currently installed version. If you installed Tivoli Storage Manager from a DVD, ensure that the DVD is available. If you installed Tivoli Storage Manager from a downloaded package, ensure that the downloaded files are available. If the upgrade fails, and the server license module is uninstalled, the server base release installation media are required to reinstall the license.

1. Back up the server database, and note the location of the backup. The preferred method is to use a snapshot backup, which is a full database backup that does not interrupt any scheduled database backups. For example, issue the following command:
backup db type=dbsnapshot devclass=tapeclass

Important: 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.

2. Back up the device configuration information. Issue the following command:
backup devconfig filenames=file_name
where file_name specifies the name of the file in which to store device configuration information.

3. Back up the volume history information. Issue the following command:
backup volhistory filenames=file_name
where file_name specifies the name of the file in which to store the volume history information.

4. Save a copy of the server options file, typically named dsmserv.opt. The file is in the server instance directory.

5. Disable automatic failback. You must disable automatic failback so that no groups automatically fail back during the installation. The cluster service then restarts automatically.

    a. In the Failover Cluster Manager window, select Services and Applications and right-click the cluster group.
    b. Select Properties.
    c. On the Failover tab in the Properties window, select Prevent failback and click OK.
    d. If multiple groups exist, repeat steps 5a, 5b, and 5c to disable automatic failback.

6. Determine the first node on which to install the fix pack.

7. Move the cluster groups from the node where the fix pack will be installed.

8. Stop the cluster server node. In the Component Services window, right-click Cluster Service and click Stop.

9. Install the Tivoli Storage Manager fix pack on the first node. For details, see the appropriate information center: Tip: Tivoli Storage Manager is still running and available on another node. If the DB2 installation attempts to access an offline instance near the end of the installation, you might receive error message SQL5005C. This message does not indicate an installation failure.

10. Take the Tivoli Storage Manager server and the DB2 resources offline:
    a. In the Failover Cluster Manager window, in the left pane, select Services and Applications and then select the cluster group. The resources for the group are displayed in the right pane. In the Other Resources section, SERVER1 and the Tivoli Storage Manager server are displayed.
    b. In the Other Resources section, right-click the Tivoli Storage Manager Instance(x) Server, where x represents the instance number. Select Take this resource Offline. Repeat this step for SERVER1.

11. Restart the cluster service on the current node. In the Component Services window, right-click Cluster Service and click Start.

12. Move the cluster groups to the current node:
    a. In the Failover Cluster Manager window, click Services and Applications.
    b. Right-click the cluster group and select Move this service or application to another node. The Current Owner column changes to the current node.
    c. Optional: If multiple groups exist, move the other cluster groups to the current node, and repeat steps 12a and 12b.
13. Start the DB2 resources:
    a. In the Failover Cluster Manager window, in the left pane, select Services and Applications, and then select the cluster group.
    b. In the right pane, right-click SERVER1 and select Bring this service online. Repeat this step for each Tivoli Storage Manager Instance (x) Server, where x represents the instance number.
14. Stop the cluster service on the second node. In the Component Services window, right-click Cluster Service and click Stop.

15. Install the Tivoli Storage Manager fix pack on the second node. Tivoli Storage Manager is now running and available on the first node. If the DB2 installation attempts to access an offline instance before the installation is completed, you might receive error message SQL5005C. This message does not indicate an installation failure.

16. Restart the cluster service on the first node. From the Component Services window, right-click Cluster Service and click Start.

17. Move the cluster groups back to the nodes that you want to use:
    a. In the Failover Cluster Manager window, click Services and Applications.
    b. Right-click the group that you want to move and select Move this service or application to another node. The Current Owner column changes to the selected node.
    c. For any other nodes that must be moved to the owners that you want to use, repeat step 17b. This step reverts the Microsoft Cluster Server environment to its initial configuration.

18. Restart automatic failback processing:
    a. In the Failover Cluster Manager window, right-click the cluster group.
    b. Select Properties.
    c. On the Failover tab of the Cluster Group Properties window, select Allow failback, and click OK.

If the upgrade fails, and you must revert to a previous level, you will need the files that were saved at the start of the upgrade procedure. For general guidance about reverting to a previous version, see Reverting from V6.3 or later to a previous Version 6 server.

Product Alias/Synonym

TSM

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager
Server

Software version:

6.1, 6.2, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.3, 6.3.2, 6.3.3, 6.3.4

Operating system(s):

Windows

Reference #:

7020690

Modified date:

2012-10-15

Translate my page

Machine Translation

Content navigation