234 IBM Content Manager OnDemand Guide
Managing Tivoli Storage Manager storage
For each automated library, Tivoli Storage Manager tracks in its volume inventory for the 
library whether a volume has scratch or private status:
/SM590000A scratch volume is a labeled volume that is empty or contains no valid data, and it can be 
used to satisfy any request to mount a scratch volume. To support Content Manager 
OnDemand, you define scratch volumes to Tivoli Storage Manager. Tivoli Storage 
Manager uses scratch volumes as needed, and returns the volumes to scratch when they 
become empty (for example, when all data on the volume expires).
/SM590000A private volume is a volume that is in use or owned by an application, and it might contain 
valid data. Volumes that you define to Tivoli Storage Manager are private volumes. A 
private volume is used to satisfy only a request to mount that volume by name. When 
Tivoli Storage Manager uses a scratch volume, it changes the volume’s status to private. 
Tivoli Storage Manager tracks whether defined volumes were originally scratch volumes. 
Volumes that were originally scratch volumes return to scratch status when they become 
empty.
Secondary storage of storage volumes
For instructions that describe how to handle physical storage volumes and remove them from 
the library, see the documentation that is provided by the library manufacturer.
For instructions about documentation that you might need to complete when you remove 
storage volumes from a library and where to store them for safekeeping, see your 
organization’s media storage guide.
Protecting data with data retention protection 
To avoid the accidental erasure or overwriting of critical data, Content Manager OnDemand 
supports the Tivoli Storage Manager APIs that relate to data retention. Data retention 
protection prohibits the explicit deletion of documents until their specified retention criterion is 
met. Although documents can no longer be explicitly deleted, they can still expire.
Tivoli Storage Manager supports two retention policies:
/SM590000In creation-based retention, the policy becomes active when the data is stored (created) 
on the Tivoli Storage Manager server. This policy is the default retention policy method 
and it is used with normal backup/archive clients.
/SM590000In event-based retention, the policy becomes active when the client sends a retention 
event to the Tivoli Storage Manager server. The retention event can be sent to the server 
any time after the data is stored on the server. Until the retention event is received, the 
data is indefinitely stored on the Tivoli Storage Manager server. For Content Manager 
OnDemand, the retention event is the call to delete the data. A load, unload, application 
group delete, or expiration of data triggers the retention event. 
If you decide to use these policies in Tivoli Storage Manager, the Content Manager 
OnDemand scenarios that are described in the rest of this section are supported.
Important notes: 
/SM590000Data retention protection is permanent. After it is turned on, it cannot be turned off.
/SM590000Content Manager OnDemand does not support deletion on hold data. This feature 
prevents held data from being deleted until the hold is released.