x

• WebFOCUS configuration files store host names and TCP/IP ports. These would have to be mapped to an IP failover address so the WebFOCUS applications resume automatically once the Disaster Recovery (DR) system is online.
• Third-party software used by WebFOCUS must have an automatic failover strategy in the DRP. These include:
  • External storage
  • Database servers
  • Load balancers and proxy servers
  • Web servers and web server farms
  • Java Application Servers
  • Search engines

The following are WebFOCUS considerations when planning Disaster Recovery measures.

• WebFOCUS configurations contain machine host names, UDP, and TCP/IP ports. In the case of a catastrophic event, those host names must be known to facilitate IP reassignment for those hosts. WebFOCUS depends on a number of third-party software to run, so it is important to start those in the proper order. The software required is mapped to what customers are using. The following is all known third-party software, listed in the start-up priority order.
  • Database back-end systems used by the Reporting Server Data Adapters and WebFOCUS Repositories.
  • Reporting Servers
  • Java Application Servers
  • ReportCaster Distribution Server
  • Web servers
  • Load Balancer
• The Recovery Time Objective (RTO) for getting all applications back online in the event of a catastrophic event is clearly defined.
• The Recovery Point Objective (RPO), the frequency for taking snapshots of the system, is also clearly defined.
• WebFOCUS applications are backed up daily.
• Conduct a complete Disaster Recovery infrastructure drill yearly.
• Conduct a complete application drill twice a year and include in the yearly Disaster Recovery infrastructure drill.