Containers DR Managed Hot Standby
Describes the processes involved in recovering your environment with the Managed Hot Standby DR service for Containers.
With Sitecore Containers DR Managed Hot Standby, in the event of an outage, the Sitecore Managed Cloud disaster recovery service sets a process in action. When there is an outage in the primary region, traffic is redirected to a secondary production environment. The secondary environment is created during DR provisioning. Because the secondary environment is already available, the Recovery Time Objective (RTO) of this recovery option is shorter than DR Basic Cold Standby, but it is the more expensive option.
The following diagram shows the containers infrastructure before setting up DR Managed Hot Standby.
The following is a brief overview of the steps to set up Containers DR Managed Hot Standby:
Sitecore executes the setup after the customer initiates a service request. These operations are part of our GitOps where changes are first committed to the relevant customer’s repositories.
Provision the Control Resource Group and the relevant underlying resources and services that monitor DR states.
Provision the Secondary Resource Group, which is the secondary environment containing Sitecore resources.
Configure Azure FrontDoor.
Set up the geo-replication for SQL server, ACR, and the Storage account.
Update the Application Repository, specifically for recognizing the endpoint for SQL Geo-Replication.
The following diagram shows the containers infrastructure after performing the DR Managed Hot Standby.
Initiating a failover
Sitecore Managed Cloud Containers continuously checks the health of the primary region environment. If three out of five data centers report an issue, the monitoring component of our DR Solution signals a regional failure and performs a failover to the secondary region. Azure FrontDoor will serve the users with Sitecore from the secondary region.
The following diagram shows the containers infrastructure after performing DR Managed Hot Standby failover.
When Sitecore in the primary region has recovered from a disaster, the DR solution automatically performs a failback. After a failback, the primary environment resumes from its state before the failure and any new SQL Server data is replicated from the secondary region.