Applying a fix pack to Tivoli Storage Manager Version 6 for AIX in a clustered environment
In a clustered environment, apply a fix pack to Tivoli Storage Manager V6 running on an AIX operating system.
To install a fix pack or interim fix to the server, install the server 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 currently have V18.104.22.168 installed, you can go directly to the latest fix pack for V6.3 or later. You do not have to start with the V6.3.0 installation if a maintenance update is available.
Remember: 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 database. The preferred method is to use a snapshot backup, which provides a full database backup without interrupting 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. If you are using application level monitoring of the Tivoli Storage Manager server, from the primary node, suspend monitoring of the dsmserv application resource. To suspend monitoring, use the smitty IBM® PowerHA® menu.
6. Halt the Tivoli Storage Manager server.
7. Verify that the database manager is not running.
8. Mount all shared resources on the primary node. Verify that no other nodes have write access to these resources during the upgrade. If your environment includes multiple instances of Tivoli Storage Manager, shared resources for all instances must be accessible to the primary node during the upgrade.
9. Install the Tivoli Storage Manager V6 server on the primary node.
10. Start the Tivoli Storage Manager V6 server.
11. Halt the Tivoli Storage Manager V6 server. Go to the secondary node.
12. On the secondary node, install the Tivoli Storage Manager V6 server.
Translate this page: