Question & Answer
Question
Why are the Sybase backups that are stored using the Tivoli Storage Manager API not automatically expiring from the Server?
Cause
The Sybase Database and Log backups are saved to the Tivoli Storage Manager server as unique objects. Since the unique objects will remain in an active state, they will not be removed by any retention settings.
Answer
As noted in the Sybase Guide for Tivoli Storage Manager backups:
within the paragraph "Deleting backup objects from TSM", it is necessary to run the sp_deletesmobj procedure:
- Use the sp_deletesmobj stored procedure to delete some or all of the current server’s backup objects from TSM. See the Reference Manual: Procedures for complete syntax and usage information.
For this deletion to work as expected, it is necessary for the node definition to have the BackDelete parameter set to YES. The syntax for this can be found in the Tivoli Storage Manager documentation under the REGISTER NODE and UPDATE NODE commands.
[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Client","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Supported Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Product Synonym
TSM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21695297