Tivoli Header

Quick Start


Migrating to Tivoli Storage Manager Version 5.1

You can install Tivoli Storage Manager Version 5.1 over a previous version or over ADSM. This is called a "migrate install".

Before Performing a Migrate Install

Attention: The following sections describe some things you must understand or do before beginning a migrate install. Follow the instructions here to prevent loss of data from your system if you are migrating from a previous version.

Directories and Files

The ADSM default installation directories have changed for Tivoli Storage Manager. If you have previously used Tivoli Disaster Recovery Manager to create a disaster recovery plan file, that 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.

During the migrate install, the following files are automatically copied to the location of the new server installation:

Attention: If your device configuration and volume history files are not named devconfig and volhist respectively, they will not be copied. Back up the files and save them in a temporary directory. You can later edit the new server options file to include the names of these files.

You should also save any existing runfile scripts in a temporary directory.

Device Support

The Tivoli Storage Manager device driver, called tsmscsi, and newly supported device classes are now available to replace the SCSI pass-through device driver, the HP-UX generic device drivers, and the GENERICTAPE device class.

For libraries that can use tsmscsi, you must migrate to the tsmscsi device driver. The SCSI pass-through device driver is no longer supported. For tape drives, tsmscsi is optional but recommended. However, tracing and error reporting is better with tsmscsi than with the standard HP-UX device driver, and tsmscsi supports additional device classes. These device classes let you specify format types for tapes, allow greater server control of SCSI devices, and enable new server functions.

Attention: Due to changes in the device support for version 5.1, the Precision Bus architecture for attaching SCSI tape devices on HP systems is no longer supported. This bus is SIO-based and is considered obsolete. In version 5.1, device support for buses based on SIO was replaced with support for buses based on WSIO. If your system uses buses based on SIO, do not install or migrate to Tivoli Storage Manager Version 5.1.

The HSC bus is still supported. To use the functions of version 5.1, you must migrate your hardware to current hardware that is based on WSIO, such as the PCI bus or the HSC bus. Questions about these bus architectures should be directed to Hewlett-Packard.

Using Existing Database, Recovery Log, and Storage Pool Volumes

A migrate install will not normally create a new database, recovery log, and storage pool volumes. However, if dsmserv.dsk is not in the /opt/adsmserv/bin or /opt/tivoli/tsm/server/bin directory, the install creates the following volumes in the /opt/tivoli/tsm/server/bin directory:

To use your existing database, recovery log, and storage pool volumes, ensure that a copy of the dsmserv.dsk file is in /opt/tivoli/tsm/server/bin or /opt/adsmserv/bin and that the filesystem is mounted before you do a migrate install. The dsmserv.dsk file points to the current location of the database and recovery log volumes. You must not move the database, recovery log, and storage pool volumes.

Returning to an Earlier Version of Tivoli Storage Manager

To return to ADSM or an earlier version of Tivoli Storage Manager, after a migrate install, you must have a full database backup from your original version and the server install code for your original version.

Be aware of the results of returning to ADSM or an earlier version of TSM:

If you decide to return to the previous version of ADSM or TSM, you must have a backup copy of your prior database, volume history, and device configuration files. In the following example, the tape device class named TAPECLASS is used for database backups.


Admin Command Line

+--------------------------------------------------------------------------------+
|backup db type=full devclass=tapeclass                                          |
|backup devconfig filenames=devconfig.jan99                                      |
|backup volhistory filenames=volhistory.jan99                                    |
+--------------------------------------------------------------------------------+

Attention: This process retrieves database records into a database dump. The recovery log is not accessed. Transactions held in the log database are lost if you return to a previous version.

Store the output volumes, device configuration, and volume history files in a safe location.

Performing a Migrate Install

  1. Stop the server if it is running by entering:
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |halt                                                                            |
    +--------------------------------------------------------------------------------+
  2. Remove the previous version server software by entering:
    +--------------------------------------------------------------------------------+
    | swremove ADSM                                                                  |
    +--------------------------------------------------------------------------------+
    Or
    +--------------------------------------------------------------------------------+
    | swremove TSM                                                                   |
    +--------------------------------------------------------------------------------+
  3. Install the Tivoli Storage Manager Version 5.1 server software (see Installing Tivoli Storage Manager).
    Note:
    Until the new version is installed and any required licenses are re-registered (step 9), clients will not be able to connect to the server.
  4. To upgrade your existing TSM database, issue the following command:
    +--------------------------------------------------------------------------------+
    |./dsmserv -upgradedb                                                            |
    +--------------------------------------------------------------------------------+
    Note:
    Issue this command only one time. Do not include the UPGRADEDB parameter in any automated programs that start your server.
  5. 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. If so, 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 scripts.smp                                                   |
    +--------------------------------------------------------------------------------+
  6. To use the administrative Web interface:
    1. Your browser must have Java(TM) 1.1.6 support. See System Requirements.
    2. The fileset TIVsmS.server_webadmin must first be installed. This subcomponent includes the dsmserv.idl file and all required image files. This fileset is installed with the server if the entire server program is installed ('swinstall TIVsm').
    3. Configure the HTTP communication method in your server options file (dsmserv.opt).
      +--------------------------------------------------------------------------------+
      |commmethod          http                                                        |
      |   httpport         1580                                                        |
      +--------------------------------------------------------------------------------+
    4. Issue this command to load the definition file:
      +--------------------------------------------------------------------------------+
      |./dsmserv runfile dsmserv.idl                                                   |
      +--------------------------------------------------------------------------------+
  7. Stop the server if it is running by entering:
    Admin Command Line
    +--------------------------------------------------------------------------------+
    |halt                                                                            |
    +--------------------------------------------------------------------------------+
  8. Start the server by issuing the following command:
    +--------------------------------------------------------------------------------+
    |./dsmserv                                                                       |
    +--------------------------------------------------------------------------------+
    See Starting and Stopping the Server for more details.
  9. Reregister your licenses. See Registering Licenses. TIVsmS.license fileset is required to register licenses. This fileset is installed when you install the TSM server package.
  10. For libraries that can use tsmscsi, you must migrate to the tsmscsi device driver. For tape drives, tsmscsi is optional but recommended. Follow the procedure in Configuring Devices to use the tsmscsi Device Driver.


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