Tivoli Header

Quick Start


Migrating to Tivoli Storage Manager Version 5.1

You can install Tivoli Storage Manager Version 5.1 over ADSM or an earlier version of Tivoli Storage Manager. This is called a "migrate install". A DSMSERV UPGRADEDB operation is automatically performed during a migrate install.

The default installation directories have changed with Tivoli Storage Manager Version 4 Release 1. If you have previously used Disaster Recovery Manager (DRM) with a version prior to 4.1, your disaster recovery plan file refers to path names that may no longer be valid. After you have installed Tivoli Storage Manager, you should back up your storage pools and database and create a new disaster recovery plan file. For the sequence and details of the procedure, see the Tivoli Disaster Recovery Manager chapter in the Administrator's Guide.


Attention

To return to ADSM or an earlier version of Tivoli Storage Manager, after a migrate install, you must have a full database backup of that original version and the install code for the server of that original version.
  • You cannot restore a prior version's backed up database onto the latest version of Tivoli Storage Manager server. For instance, you cannot restore a TSM 4.2 database onto Tivoli Storage Manager 5.1 server. For instructions on how to rollback to a prior version of Tivoli Storage Manager server see Appendix E, Removing the Tivoli Storage Manager Server.

Be aware of the results of returning to ADSM or an earlier version of Tivoli Storage Manager:

  • References to client files that were backed up, archived, or migrated to the Tivoli Storage Manager Version 5.1 server will be lost.
  • Some existing volumes may be overwritten or deleted during operation of the current version. If so, client files that were on those volumes and that were migrated, reclaimed, moved (MOVE DATA command), or deleted (DELETE VOLUME command) may no longer be accessible to the earlier version of ADSM or TSM.
  • Definitions, updates, and deletions of TSM objects performed on the current server version will be lost.

Before Performing a Migrate Install

This section describes some things you should consider before you perform a migrate install.

Performing a Migrate Install

  1. Stop the server if it is running by entering:
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |halt                                                                            |
    +--------------------------------------------------------------------------------+
  2. Remove any installed PTFs.
  3. Remove the previous version of the server software by entering:
    1. If you are migrating from versions 4.1 or later.
      +--------------------------------------------------------------------------------+
      |/usr/sbin/pkgrm TIVsmS                                                          |
      +--------------------------------------------------------------------------------+
    2. If you are migrating from versions prior to 4.1.
      +--------------------------------------------------------------------------------+
      |/usr/sbin/pkgrm IBMadsm -S                                                      |
      +--------------------------------------------------------------------------------+
  4. Install the Tivoli Storage Manager Version 5.1 server software:
    +--------------------------------------------------------------------------------+
    |/usr/sbin/pkgadd -d /cdrom/cdrom0                                               |
    +--------------------------------------------------------------------------------+

    This command gives you a list of packages to install. Select TIVsmS for the server package and TIVsmSlic for the license package and TIVsmSdev for the device driver package.

    Note:
    Until the new version is installed and any required licenses are re-registered, clients will not be able to connect to the server.
  5. Start the server by issuing the following command:
    +--------------------------------------------------------------------------------+
    |./dsmserv                                                                       |
    +--------------------------------------------------------------------------------+
    See Starting and Stopping the Server for more details.
  6. Re-register your licenses. See Registering Licenses.
  7. The previous procedure replaces the TSM tape, optical and library device drivers (non-IBM). You must now reconfigure the device drivers into the kernel, so that the device special file names are consistent.
    1. Note the existing device special file names. You may want to redirect them to a file.
      +--------------------------------------------------------------------------------+
      |ls -l /dev/rmt/*mt                (tape)                                        |
      |ls -l /dev/rmt/*lb | grep lb@     (library)                                     |
      |ls -l /dev/rmt/*op                (optical)                                     |
      +--------------------------------------------------------------------------------+
    2. Remove the device special files. The device drivers were removed from the kernel when the previous packages were removed.
      +--------------------------------------------------------------------------------+
      |rm /dev/rmt/xmt                                                                 |
      |rm /dev/rmt/xlb                                                                 |
      |rm /dev/rmt/xop                                                                 |
      |                                                                                |
      |   Where x is the appropriate number                                            |
      +--------------------------------------------------------------------------------+
    3. Reconfigure the device drivers:
      +--------------------------------------------------------------------------------+
      |add_drv mt                (tape)                                                |
      |add_drv lb                (library)                                             |
      |add_drv op                (optical)                                             |
      +--------------------------------------------------------------------------------+
    4. Compare the device special file names with the names noted in step 7a and note any differences.
      +--------------------------------------------------------------------------------+
      |ls -l /dev/rmt/*mt                (tape)                                        |
      |ls -l /dev/rmt/*lb | grep lb@     (library)                                     |
      |ls -l /dev/rmt/*op                (optical)                                     |
      +--------------------------------------------------------------------------------+
      After you start TSM, use the UPDATE PATH command to make any device special file name changes.
  8. Tivoli Storage Manager is shipped with sample command scripts that can be loaded into the database and run from an administrative client, administrative Web interface, or server console. They can also be included in administrative command schedules. The sample scripts, in scripts.smp, are primarily SELECT queries, but also include scripts that define volumes for and extend the database and recovery log and that back up storage pools.
    Note:
    The sample scripts may have been loaded when a previous version of ADSM or Tivoli Storage Manager was installed. Loading the sample scripts again at this point will overlay any existing scripts of the same name and any modifications made to those scripts will be lost.

    To load the sample scripts into the database, issue the following command:

    +--------------------------------------------------------------------------------+
    |dsmserv runfile /opt/tivoli/tsm/server/webimages/scripts.smp                    |
    +--------------------------------------------------------------------------------+
  9. To use the administrative Web interface:


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]