Azure offers High availability, disaster recovery and backup solutions This enables your applications to meet business availability and recovery goals. We continue to build on our portfolio of resilient services by providing zonal capabilities for improved business continuity and disaster recovery Azure site recovery. Azure Site Recovery replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary site. If your primary site fails, failover to a secondary site and access apps from there. After the primary location runs again, you can failback. Azure Site Recovery helps ensure business continuity by keeping business applications and workloads running in the event of a failure.
With the zonal disaster recovery function, we enable the replication and orchestration of the failover of applications in Azure across Azure availability zones in a specific region. Zone-to-zone disaster recoveryOptions with Azure Site Recovery are on the way to being available inAll RegionsWithAzure availability zones(AZs). Availability zones, fault-isolated locations in an Azure region, provide redundant power, cooling and networking so that customers can run business-critical applications with higher availability and fault tolerance against data center failures. Azure Availability Zones will be available in every country where Microsoft Azure operates publicly by the end of 2021.
While availability zones are traditionally used by customers for high availability, they can also be used for disaster recovery under certain scenarios. The feature adds disaster recovery options for scenarios where data residency and local compliance may need to be maintained, reducing the complexity of configuring a DR strategy in a secondary region and improving the recovery point goal (RPO).
Adhering to local compliance and data residency
In order to meet the unique requirements of customers for compliance and data residency, Azure offers regions within regions that form a clear boundary for data residency and compliance. Zone-to-zone recovery can be used by customers who prefer to keep applications within a specific jurisdiction because their applications and data do not have cross-border boundaries. Azure offers a broad portfolio of more than 90 compliance offerings to support optimized compliance and protect data with the most comprehensive compliance coverage.
Reduce the complexity of DR in a secondary area, latency and RPO
Many Azure regions offer traditional disaster recovery with a specific region that is very separate from the other. Some customers who enable this type of DR will require the restoration of complex network infrastructure, increases in cost and operational complexity. Zone-to-zone disaster recovery reduces complexity as redundant network concepts are used in all availability zones to simplify configuration considerably.
Because Availability Zones are designed to support synchronous replication while optimizing physical separation to provide protection and isolation from localized faults, it also means data travels shorter distances from region to region compared to DR, so Customers may see lower latency and, consequently, lower RPO by using the DR zones.
“When Availability Zones were made available for Azure, we were in the process of moving our production workloads from local data centers to the cloud. At this point, we made the bold decision to distribute all of our IaaS instances across different zones in order to maximize the benefits of redundancy and minimize the impact of single data center failures on business applications. We looked at the recently announced zone-to-zone replication as an extension of our DR capability and rolled it out to production. The call was quite easy as we had a positive experience with ASR before and simply changed the data center we are replicating to. Some exercises for different applications have been performed with great success in non-productive environments. We were able to restore the protected VMs in about 10 minutes. Failover to the same region / VNet eliminates the need to create dedicated test networks, which significantly reduces management overhead. I really liked the fact that Azure did almost the entire failover process by providing a new VM, attaching the hard drives and even swapping the IP address so that other applications quickly reconnect to the “new” one. Establish instance. “- Patryk Wolski, Senior Manager – Infrastructure Manager at Accenture.
Architecture for zonal resilience and disaster recovery
In addition to providing the right features in the right regions, we also strive to provide guidance and best practices to help our customers and partners take advantage of these features. We recently got the Good architectural Azure framework– A set of guiding principles that can be used to improve the quality of a workload. In addition to cost optimization, operational excellence, performance efficiency and security, reliability is one of the five pillars of architectural excellence. If Azure is already running a workload and you want to assess your alignment with best practices in one or more of these areas, try the following: Azure Well-Architected Review.
We continue to hear from customers about the importance of a resilience strategy that supports a variety of scenarios. We maintain detailed instructions too Design reliable applicationsThis includes best practices for architecture design, monitoring application health, and responding to failures and disasters. We invite customers to learn more about using zone-to-zone recoverystrengthen their elasticity.