Understanding the disaster recovery plan and processes
Cloud disaster recovery and resilience management practices are focused on monitoring and identifying the risks for potential business disruption, averting those risks if possible, putting contingency plans into action if a disruption cannot be prevented, and recovering normal business activities once the outage is resolved. Semos Cloud architects resilient cloud solutions with two objectives in mind:- Continuing business operations from an alternate site (such as an availability zone or in-metro data center) in the event of a failure or major outage provided by the SAP BTP
- Efficiently recovering on-demand products at a secondary site on SAP Business Technology Platform (either in-metro or inter-region) following a disaster declaration
To address the first objective, a global cloud resilience strategy captures the various methods for providing resilience and failover during a disruptive incident. A variety of resilience methods serve to minimize the negative impact of unexpected outages; the exact mechanisms may vary according to the cloud solution. Together with our partner SAP, we establish, govern, and support disaster recovery at a secondary facility with its documented strategies. The disaster recovery plan directs the recovery of mission-critical cloud services at the data center. Plans are developed and implemented to maintain or restore operations and help ensure availability of information at the required level and within the required time scales following interruption to, or failure of, critical business processes.
Top management commitment as well as testing are two measures keeping business continuity procedures up-to-date and effective. With such a framework in place, we can take measures to recover our critical business processes, restore cloud services, and safeguard our reputation in the event of a disruptive incident.
The SAP Business Technology Platform's standard subscription fee also includes a Standard Disaster Recovery option. It is based on data restore from a backup site. The Recovery Point Objective (RPO) has no strict SLA but the objective is 24 hours. The Recovery Time Objective (RTO) is "best commercially reasonable effort" to restore service as soon as possible at time of disaster. โDisasterโ means an event of substantial extent causing significant disruption to the delivery of the SAP Business Technology Platform services and may include physical damage or destruction, to the SAP Data Center or Computing Environment.
If this article left your questions unanswered, please submit a Support Form, and we can clarify this topic.