Quick Start


Migrating from a Previous Version of ADSM

You can install Tivoli Storage Manager Version 3.7 over previous versions of ADSM. Follow the instructions in this section to prevent loss of data from your system if you are migrating from a previous version.


Figure AB0CT107 not displayed.

Migration does not normally create new database, recovery log, and storage pool volumes if the dsmserv.dsk file is not in the /opt/IBMadsm-s/bin directory, the install creates the following volumes in the directory:

  • Database volume (db.dsm)

  • Recovery log volume (log.dsm)

  • Storage pool volumes (sbkup00.dsm, and sarch00.dsm,)
To use your existing database, recovery log, and storage pool volumes, ensure that a copy of the dsmserv.dsk file is in /opt/IBMadsm-s/bin and the file system is mounted before you do a migrate install.

 

To migrate to Tivoli Storage Manager Version 3.7 do the following:

  1. Back up the ADSM Version 3.1 database and the device configuration and volume history files. In the following example, the tape device class named TAPECLASS is used for database backups.

    Figure AB0CT124 not displayed.

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

    Note:This command retrieves database records into a database dump. This process does not access the recovery log. Transactions held in the log database are lost.

  2. Store the output volumes and the device configuration and volume history files in a safe location. You will need these volumes and files if you want to return to the previous version of the server.

  3. Stop the server if it is running by entering:

    Figure AB0CT124 not displayed.

    halt

  4. Remove any installed PTFs.

  5. Remove the previous version of the server software IBMadsm-s by entering:
    +--------------------------------------------------------------------------------+
    |/usr/sbin/pkgrm IBMadsm-s                                                       |
    +--------------------------------------------------------------------------------+

  6. Install the Tivoli Storage Manager Version 3.7 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.

    Note:Until the new version is installed and any required licenses are re-registered, clients will not be able to connect to the server.

  7. Start the server.

  8. Re-register your licenses. See Registering Licenses.

  9. This procedure replaces the TSM tape, optical and library device drivers (non-IBM). Therefore, you must 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 9a 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 DRIVE and UPDATE LIBRARY commands to make any device special file name changes.

  10. To use the administrative web interface:

  11. Tivoli Storage Manager is shipped with sample command scripts that can be loaded into the database and run from a TSM administrative client, administrative web interface, or server console. They can also be included in TSM 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 backup storage pools.

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

    +--------------------------------------------------------------------------------+
    |dsmserv runfile scripts.smp                                                     |
    +--------------------------------------------------------------------------------+
    Note:The sample scripts may have been loaded when ADSM Version 3.1 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.


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