![]() |
![]() |
The X/Open API applications can make calls to either delete objects that were archived or deactivate objects that were backed up. The former is dependent on the node authorization that is given when a TSM administrator registered the node. Administrators can specify whether nodes can delete archive objects.
The BSADeleteObject call is used for deleting archive objects, and the BSAMarkObjectInactive call is used for deactivating backup objects.
When deleting an archive object, the object is marked in TSM storage for deletion when the system next performs its object expiration cycle. Once an archive object is deleted from the server, it cannot be retrieved.
When a backup object on the TSM server is deactivated, the object moves from an active state to an inactive state. These states have different retention policies associated with them that are based on the management class assigned.
A call to BSADeleteObject or to BSAMarkObjectInactive is always made within the bounds of a transaction. The flowcharts in Figure 25 show how a call to BSADeleteObject or BSAMarkObjectInactive is preceded by a call to BSABeginTxn and followed by a call to BSAEndTxn.
Figure 25. Flowcharts for Delete Archive (left) and Deactivate Backup (right) Operations