Tivoli Header

Quick Start


Managing the TSM Server

Using TSM Administrative Interfaces

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.

Starting the TSM Server

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:

  1. Expand the tree for the TSM server you are starting and expand Reports
  2. Click Service Information Icon Service Information.

    The Service Information view appears in the right pane.

  3. If the server status displays Stopped, right click service line and select Start.

Stopping the TSM Server

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:

Backing up the TSM Server Database and Database Recovery Log

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.

Removing the Tivoli Storage Manager Server

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.

Note:
You cannot restore a prior version's backed up database onto a newer version of the TSM server. For instance, you cannot restore a TSM 3.7 database onto TSM 4.2 server.

Be aware of the results of returning to ADSM or an earlier version of TSM:

Before Removing Tivoli Storage Manager

You must do 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                                              |
    +--------------------------------------------------------------------------------+
  3. Store the output volumes in a safe location.

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. Remove the current TSM server software.
  3. Reinstall the previous version of TSM and the most recent maintenance.
  4. Define the Tivoli Storage Manager devices to the operating system.
  5. Reinitialize any database and recovery log volumes, other than those created during install, using the DSMSERV FORMAT utility. See Administrator's Reference for details.
  6. Reload the TSM database using the DSMSERV RESTORE DB utility.
    +--------------------------------------------------------------------------------+
    |dsmserv restore db todate=07/04/2000                                            |
    +--------------------------------------------------------------------------------+

    See TSM Administrator's Reference for details.

  7. Start the server by entering the following command:
    +--------------------------------------------------------------------------------+
    |dsmserv                                                                         |
    +--------------------------------------------------------------------------------+
  8. 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.
  9. 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 ]