Azure Site Recovery helps protect the critical applications running in your datacenter with flexible recovery plans and low Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

Azure Site Recovery is part of Microsoft Azure cloud computing services.

As an organization, you need to adopt a business continuity and disaster recovery (BCDR) strategy that keeps your data safe, and your apps and workloads up and running, when planned and unplanned outages occur.

How Azure Site Recovery ensures business continuity

Azure Site Recovery helps ensure business continuity by keeping business apps and workloads running during outages. It replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary location. When an outage occurs at your primary site, you fail over to the secondary location, and access apps from there. After the primary location is running again, you can fail back to it.

What does Azure Site Recovery do?

Simple BCDR solution: Using Azure Site Recovery, you can set up and manage replication, failover, and failback from a single location in the Azure portal.

Azure VM replication: You can set up disaster recovery of Azure VMs from a primary region to a secondary region.

Workload replication: Replicate any workload running on supported Azure VMs, on-premises Hyper-V and VMware VMs, and Windows/Linux physical servers.

Data Resilience: Site recovery orchestrates replication without intercepting application data. When failover occurs, Azure VMs are created, based on the replicated data.

RTO and RPO targets: Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organizational limits. Site Recovery provides continuous replication for Azure VMs and VMware VMs, and replication frequency as low as 30 seconds for Hyper-V. You can reduce RTO further by integrating with Azure Traffic Manager.

Keep apps consistent over failover: You can replicate using recovery points with application-consistent snapshots. These snapshots capture disk data, all data in memory, and all transactions in process.

Testing without disruption: You can easily run disaster recovery drills, without affecting ongoing replication.

Flexible failovers: You can run planned failovers for expected outages with zero-data loss, or unplanned failovers with minimal data loss (depending on replication frequency) for unexpected disasters. So you can easily fail back to your primary site when it’s available again.

Customized recovery plans: Using recovery plans, can customize and sequence the failover and recovery of multi-tier applications running on multiple VMs. You group machines together in a recovery plan, and optionally add scripts and manual actions. Recovery plans can be integrated with Azure automation runbooks.

BCDR integration: Site Recovery integrates with other BCDR technologies. For example, you can use Azure Site Recovery to protect the SQL Server backend of corporate workloads, with native support for SQL Server AlwaysOn, to manage the failover of availability groups.

Network Integration: Site Recovery integrates with Azure for simple application network management. That includes reserving IP addresses, configuring load-balancers, and integrating Azure Traffic Manager for efficient network switchovers.

If you would like more information on Azure Site Recovery, contact PC Professional today.



Share this post with your friends and networks!