Tivoli Header

Tivoli Storage Manager Using the Application Program Interface


Deleting Objects from the Server

API applications can make calls to either delete objects that were archived or turn off objects that were backed up. Deleting archived objects is dependent on the node authorization that was given when the TSM administrator registered the node. Administrators can specify that nodes can delete archived objects. Use the dsmDeleteObj function call to delete archived objects and turn off backup objects.Using this delType will remove the backup object from the server. This is based on objID, deletes an object from the server database. Only an owner of an object can delete it.You can delete any version (active or inactive) of an object. The server reconciles the versions. If you delete an active version of an object, the first inactive version becomes active. If you delete an inactive version of an object, all older versions will advance. The node must be registered with backDel permission.

An archived object is marked for deletion in storage when the system performs its next object expiration cycle. Once you delete an archived object from the server, you cannot retrieve it.

When you inactivate a backup object at the server, 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 that is assigned.

Similar to the dsmSendObj call, a call to dsmDeleteObj is sent within the boundary of a transaction. The state diagram in Figure 12 displays how a call to dsmDeleteObj is preceded by a call to dsmBeginTxn and followed by a call to dsmEndTxn.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]