To configure LiteSpeed to back up directly to TSM
Set up the machine from where you will run LiteSpeed so that it is a TSM backup-archive client node. This requires that you install the TSM backup-archive client and API files. For more information, see Install and Configure the Backup-Archive Client.
Register the TSM client node with the TSM server. For instructions, refer to IBM Tivoli Storage Manager Implementation guide available at www.redbooks.ibm.com.
You should now be able to conduct LiteSpeed backups and restores from the TSM client node.
Set up the client option file
If the TSM client API is installed with the default options then the options file (dsm.opt) is typically located in the C:\Program Files\Tivoli\TSM\baclient directory. At a minimum, the client option file must contain the following:
The client API needs the communication method and the IP address and TCP port of the TSM server to initiate a session. TCPSERVERADDRESS can use either the IP address or the computer name of the TSM server.
For general instructions on the client option file and information on additional options, refer to the IBM Tivoli Storage Manager Implementation guide and the IBM Tivoli API Documentation available at www.redbooks.ibm.com.
Tip: You can create a new options file for use with LiteSpeed and locate it anywhere you like.
Back Up and Restore to TSM with [[[Undefined variable Primary.product_Name]]]
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. Some server options may affect backup/restore processes.
- 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 identifies the backup in TSM. 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.
Depending on your TSM configuration, you may need to provide the following:
- Client node that is accessing the TSM Server
- Node owner password
For more information, see TSM Examples. on how to perform LiteSpeed functions with the TSM.
NOTE: For information about backing up or restoring using the LiteSpeed UI Console, please see the LiteSpeed User Guide.
Troubleshoot Backing Up and Restoring to TSM
LiteSpeed displays the return codes from the TSM API. If an error occurs, refer to the list of TSM API error codes for a description of the error, the system action occurring in the event of the error, and the appropriate response. The TSM API error codes are listed in the Tivoli Storage Manager Information Center.