This appendix describes how to remove Tivoli Storage
Manager Version 3 Release 7 and reinstall an earlier version of ADSM.
![]() | 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:
+--------------------------------------------------------------------------------+ |backup db type=full devclass=tapeclass | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |backup volumehistory filenames=volhist | |backup devconfig filenames=devices | +--------------------------------------------------------------------------------+
Here is the procedure for removing Tivoli Storage Manager Version 3.7 and reinstalling ADSM:
+--------------------------------------------------------------------------------+ |halt | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |dsmserv restore db | +--------------------------------------------------------------------------------+See TSM Administrator's Reference for details.
+--------------------------------------------------------------------------------+ |dsmserv | +--------------------------------------------------------------------------------+
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.