text: Basically, two redundancy techniques are available: 
  
  (cid:2) Passive redundancy: This redundancy is achieved by including enough excess capacity in 
  
  the design to accommodate a performance decline, such as two Content Manager 
  OnDemand servers (known as ARSSOCKD on z/OS and Multiplatforms) that access the 
  same system tables and archive. If one server fails, the other server is available to take on 
  the workload. 
  
  (cid:2) Active redundancy: This redundancy is used to achieve high availability with no 
  
  performance decline. In this case, at least double the required resources are allocated to 
  the Content Manager OnDemand system. For example, if the peak workload requires 1.5 
  Content Manager OnDemand servers, three Content Manager OnDemand servers are 
  configured to work in parallel. If one of the servers fails, the other two servers can take on 
  the full workload with no performance degradation. 
  
  Systems typically become unavailable because of the lack of one or more of the following 
  activities: 
  
  (cid:2) Change control procedures (a failure to implement the appropriate procedures from 
  installation verification through performance testing before you place the system into 
  production) 
  
  (cid:2) Monitoring of production system components (including total system workload, hardware, 
  and network issues) 
  
  (cid:2) Implementing high availability solutions (redundant systems and network connections) 
  
  (cid:2) A comprehensive backup (and restore) process that is tested on a routine basis 