Quick Start


Appendix F. Removing Tivoli Storage Manager Version 3.7 and Reinstalling ADSM

This appendix describes how to remove Tivoli Storage Manager Version 3 Release 7 and reinstall an earlier version of ADSM. It also discusses how to just remove Tivoli Storage Manager (see Removing Tivoli Storage Manager).


Figure AB0CT107 not displayed.

This procedure includes reloading the ADSM Version 3 Release 1 database. All references to client files that were backed up, archived, or migrated to the Tivoli Storage Manager Version 3.7 server will be lost. In addition, some existing volumes may be overwritten or deleted during the Tivoli Storage Manager Version 3.7 operation. 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.

Before you remove Tivoli Storage Manager Version 3.7 you must already have done the following:

  1. Do a full database backup. For example, if you have a tape device class named TAPECLASS, do a full backup by issuing the following command:
    +--------------------------------------------------------------------------------+
    |backup db type=full devclass=tapeclass                                          |
    +--------------------------------------------------------------------------------+

  2. Save a copy of the volume history and device configuration files that were defined in the server options file with the VOLHISTORY and DEVCONFIG options respectively. For example, to save the volume history in a file called VOLHIST and the device configuration in a file called DEVICES, enter:
    +--------------------------------------------------------------------------------+
    |backup volumehistory filenames=volhist                                          |
    |backup devconfig filenames=devices                                              |
    +--------------------------------------------------------------------------------+

Here is the procedure for removing Tivoli Storage Manager Version 3.7 and reinstalling ADSM:

  1. Stop the Tivoli Storage Manager Version 3.7 server if it is currently running, by entering the following command:
    +--------------------------------------------------------------------------------+
    |halt                                                                            |
    +--------------------------------------------------------------------------------+

  2. Delete the current device definitions.

  3. Remove the Version 3.7 server software. Enter the following:
    +--------------------------------------------------------------------------------+
    |/usr/sbin/pkgrm TIVsmS                                                          |
    +--------------------------------------------------------------------------------+
    Note:Also remove any other NLS Tivoli Storage Manager packages you may have installed (for example, TIVsmSjp).

  4. Reinstall the previous version of ADSM and the most recent maintenance.
    +--------------------------------------------------------------------------------+
    |/usr/sbin/pkgadd -d /cdrom/cdrom0/IBMadsm-s                                     |
    +--------------------------------------------------------------------------------+

  5. Define the Tivoli Storage Manager devices to the operating system.

  6. Reinitialize any database and recovery log volumes, other than those created during install, using the DSMSERV FORMAT utility. See Administrator's Reference for details.

  7. Reload the ADSM database using the DSMSERV RESTORE DB utility.
    +--------------------------------------------------------------------------------+
    |dsmserv restore db                                                              |
    +--------------------------------------------------------------------------------+
    See TSM Administrator's Reference for details.

  8. Start the server by entering the following command:
    +--------------------------------------------------------------------------------+
    |dsmserv                                                                         |
    +--------------------------------------------------------------------------------+

  9. 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.

  10. 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 ]