Tivoli Header

Quick Start


Rollback to previous version of TSM (or ADSM)



Attention

You cannot restore a prior version's backed up database onto a newer version of TSM server. For instance, you cannot restore a TSM 3.7 database onto TSM 4.2 server.
  1. Stop the current Tivoli Storage Manager server if it is currently running, by entering the following command:
    +--------------------------------------------------------------------------------+
    |halt                                                                            |
    +--------------------------------------------------------------------------------+
  2. Delete the current device definitions.
    1. To use SMIT, enter:
      +--------------------------------------------------------------------------------+
      |smit &                                                                          |
      +--------------------------------------------------------------------------------+
    2. Select Devices.

      Select your device from the device selection screen.


      A Closer Look

      You do not need to remove the non-TSM devices that Tivoli Storage Manager uses (3480, 3490, and 3590 drives, and 3494 and 3495 tape libraries).
    3. Select Remove for the device selected in the preceding step.

      Do not keep the configurations in the database, but record the device SCSI address so you can use them later to redefine the devices. On the SMIT screen (Keep definition in database) for defining devices, change the yes to no.

  3. Remove the current TSM server software. Enter the following:
    +--------------------------------------------------------------------------------+
    |/usr/sbin/installp -ug tivoli.tsm.license                                       |
    |/usr/sbin/installp -ug tivoli.tsm.devices                                       |
    |/usr/sbin/installp -ug tivoli.tsm.server                                        |
    +--------------------------------------------------------------------------------+
    Note:
    Also remove any other NLS Tivoli Storage Manager packages you may have installed (for example, tivoli.tsm.msg.Ja_JP.server).
  4. If you have the previous dsmserv.dsk, database, and recovery log, restore them to the directory that will be used for the reinstall.
  5. Reinstall the previous version of TSM and the most recent maintenance.
  6. Define the Tivoli Storage Manager devices to the operating system.
  7. Reinitialize any database and recovery log volumes, other than those created during install, using the DSMSERV FORMAT utility. See Administrator's Reference for details.
  8. Reload the TSM database using the DSMSERV RESTORE DB utility.
    +--------------------------------------------------------------------------------+
    |dsmserv restore db todate=07/04/2000                                            |
    +--------------------------------------------------------------------------------+

    See TSM Administrator's Reference for details.

  9. Start the server by entering the following command:
    +--------------------------------------------------------------------------------+
    |dsmserv                                                                         |
    +--------------------------------------------------------------------------------+
  10. Issue an AUDIT VOLUME FIX=YES command for each sequential storage pool volume that has a volume type of STGDELETE or STGREUSE to audit all disk storage pool volumes.
  11. Examine the saved volume history file from step 2.

    For every sequential volume specified in the volume history file with a volume type of STGREUSE or STGDELETE, execute the AUDIT VOLUME FIX=YES command to clean up invalid database references to the volume(s).

    If you cannot locate a volume that has a volume type of STGDELETE, use the DELETE VOLUME DISCARDDATA=YES command to remove references to the volume from the server database.


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