![]() |
![]() |
For TSM server administrative interface overviews and access information, refer to TSM Interfaces. For detailed descriptions of TSM server administrative interfaces, refer to Appendix F, Using Administrative Interfaces.
You can start the Tivoli Storage Manager server in several ways. However, we recommend that you start it as a service. In this way, the server remains active when you log off the workstation. To start the server as a service, do the following from the TSM Console:
The Service Information view appears in the right pane.
You can stop the server without warning if required. To avoid losing administrative and client node connections, stop the server only after current sessions have been completed or canceled. For most tasks in this book, your server must be running. This procedure is explained here only if an unusual situation requires that you stop the server.
To stop the server, do one of the following:
The Service Information view appears in the right pane.
The Command Line view appears in the right pane.
The Command Prompt dialog appears.
If the TSM server database or the recovery log is unusable, the entire server is unavailable. If a database is lost and cannot be recovered, all of the data managed by that server is lost. If a storage pool volume is lost and cannot be recovered, the data on the volume is also lost.
With Tivoli Storage Manager you can define administrative schedules so that the database and storage pools are backed up regularly. If you should lose your database or storage pool volumes, you can use offline utilities provided by Tivoli Storage Manager to restore your server and data.
See the Administrator's Guide for details.
This section describes what you need to do before removing the current version of the TSM server, and tells you how to rollback to a previous version of TSM (or ADSM).
After removing the Tivoli Storage Manager device driver, the system will require a reboot.
To return to ADSM or an earlier version of TSM, 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:
You must do the following:
+--------------------------------------------------------------------------------+ |backup db type=full devclass=tapeclass | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |backup volumehistory filenames=volhist | |backup devconfig filenames=devices | +--------------------------------------------------------------------------------+
![]() | 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. |
+--------------------------------------------------------------------------------+ |halt | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |dsmserv restore db todate=07/04/2000 | +--------------------------------------------------------------------------------+
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.