IBM Tivoli Storage Manager, Version 7.1

Scenario 3: Preparing for the upgrade

Prepare for the upgrade by checking requirements, preparing the space that is required, backing up the server, and modifying certain server settings.

About this task

Follow the preparation steps carefully to protect your server and its data.
Important: It is possible, after the upgrade to V7.1 is complete, that conditions might cause the need to temporarily revert to the previous version of the server. Successfully reverting to the previous version of the server is possible only if you have completed all preparation steps. To understand why it is important to complete all preparation steps, review the procedure for reverting an upgraded server to its previous version.
  1. Scenario 3: Checking the prerequisites for the upgrade
    Check your system against requirements for the server.
  2. Optional: Scenario 3: Preparing space for the upgrade process
    Determine the amount and type of space that is required for the upgrade process before beginning the process.
  3. Scenario 3: Modifying the server before the upgrade
    A command must be run on the server to prevent one type of problem during the upgrade process. Some modifications to typical server settings can be useful to prepare for the upgrade.
  4. Scenario 3: Disabling sessions
    In preparation for the upgrade, prevent activity on the server by disabling new sessions. Cancel any existing sessions.
  5. Scenario 3: Backing up storage pools and the server database
    Immediately before upgrading the server, back up primary storage pools to copy storage pools, and perform a full database backup.
  6. Scenario 3: Moving the NODELOCK file
    To ensure that licensing information is updated during the upgrade process, move the NODELOCK file from the server instance directory to another directory.
  7. Scenario 3: Backing up configuration information
    Before you install the new version, back up critical files and information for each server instance. Store the files in a safe place, on a different system from the system that is being upgraded or on offline media, such as a CD. The files are required after the installation of the new software version is complete. You also need these files if you must revert to the previous version after the upgrade.
  8. Scenario 3: Creating a summary of database contents
    Create a summary of the contents of the original database. After the upgrade, you can use the same commands to compare the results and to confirm that the database contents are intact.
  9. Scenario 3: Stopping the server before installing the upgrade
    Stop all server processes and unmount any tapes that are mounted. Then, stop the server.
Parent topic: Scenario 3: New system, media method
Related tasks:
Reverting from V7.1 to the previous V5 server version

Feedback