text: 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. 
  
  **Important notes**: 
  
  (cid:2) Data retention protection is*permanent*. After it is turned on, it cannot be turned off. 
  (cid:2) Content Manager OnDemand does not support deletion on hold data. This feature 
  prevents held data from being deleted until the hold is released. 
  
  Tivoli Storage Manager supports two retention policies: 
  
  (cid:2) In*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. 
  
  (cid:2) In*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. 