Chat now with support
Chat with Support

LiteSpeed for SQL Server 8.9.5 - Security and Compliance Guide

Back Up and Restore to TSM with LiteSpeed

To use LiteSpeed to back up and/or restore to TSM

Conduct a backup from the LiteSpeed UI Console, using the LiteSpeed command line utility or using LiteSpeed T-SQL commands in the normal manner, providing the TSM-required information using TSM specific arguments.

LiteSpeed needs some specific information for every backup data stream sent to the TSM server, including:

  • Location of the option file (Usually, C:\Program Files\Tivoli\TSM\baclient\dsm.opt.)

    NOTE: Tivoli Server uses the option file to start as a service with a set of default options to start the server. Some server options may affect backup/restore processes.

  • TSM object name specification, a three-part name used to uniquely identify the object within the TSM server namespace, for example, FS\HL\LL_xmlData. The three parts can be generally explained as:

    • File space—The name of the file system or disk drive where related data is located. The file system can hold a group of similar objects. All data sent to the TSM server needs to have a file space associated with it. IBM recommends that an application client should select a unique file space; it is recommended that LiteSpeed users follow this practice with a specific filespace reserved for LiteSpeed backups.
    • High level name—The location of the object within the TSM Server namespace (roughly synonymous to a directory path).
    • Low level name—The actual name given to the object. This name always needs to be unique.

    This name identifies the backup in TSM and may be unique. It is not possible to overwrite or append to an existing object. If backing up to the same tsm objects with init option, they are "versioned" by the TSM server. New backups become active, old ones become inactive and removed as specified by the TSM servers' retention policies. Using -I or @init=1 parameters will allow for non-unique TSM object names.

Depending on your TSM configuration, you may need to provide the following:

  • Client node that is accessing the TSM Server (Not needed, if you use the PASSWORDACCESS GENERATE option. The TSM API uses the system host name instead. BUT: If you are working from a different workstation, you can use the nodename option even if the passwordaccess option is set to generate)
  • Node owner password (Not needed, if you use the PASSWORDACCESS GENERATE option.)
  • Client node owner that is authorized to access the server (-M parameter in the command line)
  • Connection user name (generated in LiteSpeed script)
  • Connection password (generated in LiteSpeed script)

For more information, see IBM Spectrum Project (TSM) Examples. on how to perform LiteSpeed functions with the TSM. 

NOTE: For information about backing up or restoring to TSM using the LiteSpeed UI Console, please see the LiteSpeed User Guide.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating