Recovery Point Objectives and Recovery Time Objectives for DR 2.0
The time taken from the failure of your Production environment to the successful return to operations in the DR environment depends on you creating the request to initiate the failover process. Any time spent investigating a failure or event prior to failover will delay the point at which return to operations occurs. This topic describes the Recovery Point Objectives (RPOs) and Recovery Time Objectives (RTOs) involved in the failover process for DR 2.0.
Recovery Point Objective (RPO)
| Service type | Recovery Point Objective |
|---|---|
| Azure SQL Failover Groups | ~5 Seconds |
| Azure App Service plans backups and restore | 3 hours |
| Azure Redis Cache (recreated in the secondary region) | N/A |
| Sitecore configuration and automation | 3 hours |
| Solr as a Service using backup and restore | 3 hours |
Technology Recovery Time Objective (RTO)
| Service type | Technology Recovery Time Objective |
|---|---|
| Azure SQL failover groups | 10 minutes |
| Azure App service plans backups | 10 minutes |
| Azure Redis Cache * | 30 minutes |
| Sitecore configuration and automation | 10 minutes |
| Solr as a Service using backup and restore | 10 minutes |
* Azure Redis Cache Scale-up will take approximately 30 minutes. During this time, there might be intermittent access to the Azure Redis Cache service. Please refer to the Microsoft documentation on Azure Redis Scaling.
The Technology RTO values only account for the time it takes to restore the Sitecore platform. If manual steps involving the customer or partner are required, such as attempting to get in touch with authorized contacts for permission to failover or validation of customizations before going live, the effective RTO will be extended.
Platform and website Recovery Time Objective (RTO)
The RTO values listed below are subject to customer approval to initiate the DR failover process.
| Backup technology | Responsible owner | Technology Recovery Time Objective |
|---|---|---|
| Sitecore CM server access and service availability | Sitecore | 1 hour |
| Sitecore CD server access and service availability | Sitecore | 1 hour |
| Website access and availability | Customer/Partner | Customer-dependent activity which requires validation of custom application connection strings and third-party connectivity. |
The RTO does not cover a rebuild of the xDB index due to the significant time it can take for a large content database. If the analytics indexes are not rebuilt, this should only affect functionality that depends on lists, such as EXM, and it should not affect the runtime site.