text: **Scenario 4: Both cache and storage manager, then expiration**
  The storage object is stored directly to both cache and the storage manager. After a short 
  period, the data is expired from cache. Then, after a much longer period, the data is expired 
  from the storage manager. Typically, this methodology is used under the following 
  circumstances: 
  
  (cid:2) The cache file system allows more efficient data retrieval. 
  (cid:2) The data needs to be kept for a longer period. 
  (cid:2) The hierarchical storage management (or other features) of the storage manager is 
  required. 
  
  The Cache data field determines whether Content Manager OnDemand stores data in cache 
  storage. If the storage set is a cache-only storage set, Yes is the only selection. If the storage 
  set is an archive manager-controlled storage set (OAM, Tivoli Storage Manager, or ASM), you 
  can optionally add storing the data in cache. 
  
  **Note:**Whether the data is stored in cache or in a storage manager, the main performance 
  differences are a result of the following items: 
  
  (cid:2) The hardware speed (and I/O channels and interfaces) on which the data is stored. 
  
  (cid:2) The location of the hardware device in relations to the object server. 
  
  If the hardware device connects over a TCP/IP link, that link can form a bottleneck, 
  depending on the link’s throughput and the required data retrieval rate. 