text: **File systems on UNIX**
  During the installation and setup of Content Manager OnDemand, one of the tasks is to 
  create the file systems that are required to contain the various Content Manager OnDemand 
  components. 
  
  For performance reasons, when the Content Manager OnDemand file systems are created, 
  the following components*must not*be on the same physical media: 
  
  (cid:2) Cache file system 
  (cid:2) Database file system 
  (cid:2) Primary logs file system 
  (cid:2) Secondary logs file system 
  (cid:2) Load/indexing file system 
  (cid:2) Content Manager OnDemand temporary space file system 
  
  **13.1.4 Storage management**
  
  Regardless of the platforms, storage management with Content Manager OnDemand can be 
  divided into two areas: cache storage that is managed by Content Manager OnDemand and 
  archive media that is managed by an external product, such as IBM Tivoli Storage Manager, 
  object access method (OAM), Virtual Storage Access Method (VSAM), or Archive Storage 
  Manager (ASM). 
  
  For effective storage management, one key performance feature of Content Manager 
  OnDemand is its ability to load data to archive media, while simultaneously retaining a 
  temporary cached copy of the most recent archived data on fast access media (such as the 
  hard disk drive (HDD)). Content Manager OnDemand handles the expiration and 
  management of this cached copy of the data. After a certain predefined period elapses, the 
  data is removed from cache. The only remaining copy is held on the much slower archive 
  media that is managed by either Tivoli Storage Manager, OAM, VSAM, or ASM, depending on 
  the platform. 