The process for upgrading the server from V5 to V7.1.1

Moving from Tivoli® Storage Manager V5 to V7.1.1 requires more preparation and planning than previous upgrades. Because of the database program that the server is using, an existing database must be moved into the new database structure by using the provided upgrade tools.

Except for the database extraction and insertion steps, the server upgrade process is similar to the disaster recovery process. Critical server files, such as the option and device configuration files, must be available, and storage pool devices must be made available to the upgraded server.

Windows operating systemsTip: The Tivoli Storage Manager Management Console, which is a Microsoft Management Console (MMC) snap-in, is no longer delivered with Tivoli Storage Manager. If you are configuring or upgrading a Tivoli Storage Manager server that is installed on a Microsoft Windows operating system, the preferred methods are to use the configuration and upgrade wizards. You can use the wizards to complete several server configuration tasks. However, you cannot use the wizards to extend the Active Directory schema so that clients can automatically discover servers.
The major steps in the upgrade process from V5 to V7.1.1 are as follows:
  1. Plan system hardware and software, and estimate the upgrade time.

    Use information about the Tivoli Storage Manager upgrade process together with operational requirements for your existing servers to decide how and when to perform the upgrade.

    Tip: If you are introducing new hardware or changes in the storage system infrastructure, plan the zoning for the storage area network (SAN). Allow time to create device statements and paths, and to check in tape volumes following the upgrade. For IBM® tape devices, no multipathing driver is available for tape drives that are distributed over more than one adapter. Use zoning and device definitions to balance the workload.
  2. Back up the Tivoli Storage Manager server database and configuration files. Ensure that at least one full database backup is available onsite.
    Tip: If you must restore the database after a failed upgrade, having an onsite backup database saves time.
  3. Install the server code. Installation tasks include the following:
    • Installing the new server code, which includes the server and its database manager program. Configure a user ID for the new server instance.
    • Installing the upgrade utilities package on the system where the existing V5 server is located.
  4. Upgrade the database. This task includes preparing the database, and then moving the database. Use the upgrade utilities or the upgrade wizard to complete these tasks.

    The upgrade utilities or upgrade wizard extracts data from an existing database and inserts the data into a new V7.1.1 database. Media or the network can be used for the data movement.

    As a database is moved into the new database structure, the validity of the data is checked against constraints that are enforced in the new database. The upgrade tools automatically correct some errors in the database. Other errors might require manual correction.

    If you use the wizard, you are guided to complete the upgrade steps in the correct order. If you are performing the upgrade manually by using utilities from a command line, follow the procedure carefully.

  5. Verify the upgrade by running basic operations and querying information about the system to confirm that all information transferred correctly.

To help you decide how to perform the upgrade process, review the information that compares upgrade methods, and the descriptions of upgrade scenarios.