This document helps you make smart decisions when designing disaster recovery (DR) architectures and strategies. The document considers not just the criticality of individual solutions, but also the different components of a typical SAP system.
The document is part of a series about working with SAP on Google Cloud, which includes the following:
- High availability
- Migration strategies
- Backup strategies and solutions
- Disaster recovery strategies (this document)
A good disaster recovery strategy always begins with a business impact analysis that defines two key metrics:
- Recovery Time Objective (RTO): How long you can afford to have your business offline.
- Recovery Point Objective (RPO): How much data loss you can sustain before you run into compliance issues due to financial losses.
For both cases, you must determine the costs to your business while the system is offline or for data loss and re-creation.
Typically, the smaller your RTO and RPO values (that is, the faster your application must recover from an interruption), the more your application will cost to run. Because smaller RTO and RPO values often mean greater complexity, the associated administrative overhead also increases with lower RTO and RPO values.
To read the full white paper, click the button: