96 IBM Content Manager OnDemand Guide
5.2.4  Storage set definition
A storage set can contain one or more primary storage nodes. A primary storage node is 
used to manage reports and resources that are stored in an application group. A storage node 
is associated with a specific Content Manager OnDemand object server. When Tivoli Storage 
Manager is used for archive storage, each storage node that is associated with storage that is 
managed by Tivoli Storage Manager must be registered as a client node in a Tivoli Storage 
Manager policy domain. The Tivoli Storage Manager policy domain properties determine the 
type of storage devices that are used to maintain the archived data and the length of time that 
the data is maintained. 
Content Manager OnDemand systems can be set up to run as cache-only hard disk drive 
systems with no migration of the data or indexes, or with an archive system that uses Tivoli 
Storage Manager to maintain and manage the archive of Content Manager OnDemand 
documents and indexes over a predetermined period. 
When Content Manager OnDemand is installed and the system is initialized, a default 
cache-only storage set is created. Additional cache storage sets can be defined. Storage sets 
that are associated with Tivoli Storage Manager client nodes that are tied to specific 
management policies on the Tivoli Storage Manager servers are used for long-term archive 
storage.
Note: In Content Manager OnDemand, the date that is used to determine the Life of Data 
and Indexes is the date field index value, which is taken from the report that is being loaded 
and defined as the segment date. 
For Tivoli Storage Manager: 
/SM590000If RETINIT=CREATION, the date that is used for the retention period in Tivoli Storage 
Manager is the date that the report is first migrated to Tivoli Storage Manager. 
/SM590000If you are using RETINIT=EVENT, the RETMIN parameter specifies the minimum number of 
days that Tivoli Storage Manager stores an object.
The expiration type determines how the data is expired: 
/SM590000If the expiration type value for the application group is load, a command is issued from 
Content Manager OnDemand to Tivoli Storage Manager to delete data when the data is 
expired from Content Manager OnDemand. 
/SM590000If the expiration type is segment or document, a delete command is not issued from 
Content Manager OnDemand to Tivoli Storage Manager when Content Manager 
OnDemand expires the data and the data remains in Tivoli Storage Manager until the 
Tivoli Storage Manager retention period expires. This data is not accessible from 
Content Manager OnDemand because the indexes are expired in Content Manager 
OnDemand.
If Tivoli Storage Manager and Content Manager OnDemand are configured to use 
event-based archiving, Content Manager OnDemand sends a delete command to Tivoli 
Storage Manager when data is due to be expired. Tivoli Storage Manager then checks to 
see whether the data is allowed to be deleted based on its RETMIN parameter. The benefit 
of this approach is that Content Manager OnDemand is in total control of when deletions 
can take place instead of Tivoli Storage Manager deleting data independently.