Understanding business continuity and disaster recovery for IBM OpenPages
Disaster recoveryThe ability of a service or workload to recover from rare, major incidents and wide-scale failures, such as service disruption. This includes a physical disaster that affects an entire region, corruption of a database, or the loss of a service contributing to a workload. The impact exceeds the ability of the high availability design to handle it. involves a set of policies, tools, and procedures for returning a system, an application, or an entire data center to full operation after a catastrophic interruption. It includes procedures for copying and storing an installed system's essential data in a secure location, and for recovering that data to restore normalcy of operation.
Responsibilities
To find out more about responsibility ownership for using IBM Cloud® products between IBM and customer see Shared responsibilities for IBM Cloud products.
Disaster recovery strategy
IBM Cloud has business continuityThe capability of a business to withstand outages and to operate mission-critical services normally and without interruption in accordance with predefined service-level agreements. plans in place to provide for the recovery of services within hours if a disaster occurs. You are responsible for your data backup and associated recovery of your content.
IBM OpenPages provides mechanisms to protect your data and restore service functions. Business continuity plans are in place to achieve targeted recovery point objectiveIn disaster recovery planning, the time at which data is restored measured in time (seconds, minutes, hours) starting at the recovered instance and ending at the point of disaster. (RPO) and recovery time objectiveIn disaster recovery planning, the duration of time for a business process to be restored after a disaster. (RTO) for the service. The following table outlines the targets for IBM OpenPages.
| Disaster recovery objective | Target Value |
|---|---|
| RPO | Up to 24 hours |
| RTO | Up to 72 hours |
The service is restored to another region based on the following table. The application URL domain is updated in the event of a restore. When the service is restored at the target region, the new application URL is available in the console.
If you customized the hostname, the URL uses the updated region, along with the custom hostname.
| Primary region of the service | Target region to restore the service |
|---|---|
| AWS US East (Northern Virginia) | AWS US East (Ohio) |
| AWS Europe (Frankfurt) | AWS Europe (London) |