How Azure Site Recovery and Backup Can Help Your Business Continuity and Disaster Recovery (BCDR) Strategy.
Simplify your BCDR strategy with Azure
All businesses are in the risks to a critical business operation due to systems outages, and will always be, a concern for most organizations. As a result, IT disaster recovery planning is critical to help ease the likelihood of a system disruption, or reduce downtime when a disruption does happen.
Business continuity and disaster recovery (BCDR) strategy is required for a company to keep safe their data, apps and workloads running whenever a planned or an unplanned outages occur during the business hour.
What Azure Recovery Services can contribute to your BCDR strategy:
Site Recovery service: Site Recovery helps business to continue as usual by keeping business apps and workloads running during any outages. Site Recovery replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary location. When an outage occurs to your primary site, all your fail will be transfer over to a secondary location, and you can access apps from the secondary location.
Backup service: The Azure Backup service keeps your data safe and recoverable by backing it up to Azure.
Site Recovery can manage replication for:
Azure VMs replicating between Azure regions.
On-premises VMs, Azure Stack VMs and physical servers.
Site Recovery Provides the Following:
Simple BCDR solution
Using Site Recovery, user can set up and manage replication, failover, and failback from a single location in the Azure portal.
Azure VM replication
User set up disaster recovery of Azure VMs from a primary region to a secondary region.
On-premises VM replication
User replicate on-premises VMs and physical servers to Azure, or to a secondary on-premises datacenter. This process eliminates the cost and complexity of maintaining a secondary datacenter.
Replicate any workload running on supported Azure VMs, on-premises Hyper-V and VMware VMs, and Windows/Linux physical servers.
Site recovery orchestrates replication without intercepting application data. When you replicate to Azure, data is stored in Azure storage, with the resilience that provides. 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
User 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
User easily run disaster recovery drills, without affecting ongoing replication.
User run planned failovers for expected outages with zero-data loss, or unplanned failovers with minimal data loss (depending on replication frequency) for unexpected disasters. user easily fail back to their primary site when it's available again.
Customized recovery plans
Using recovery plans, user can customize and sequence the failover and recovery of multi-tier applications running on multiple VMs. User group machines together in a recovery plan, and optionally add scripts and manual actions. Recovery plans can be integrated with Azure automation runbooks.
Site Recovery integrates with other BCDR technologies. For example, user can use 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.
Azure automation integration
A rich Azure Automation library provides production-ready, application-specific scripts that can be downloaded and integrated with Site Recovery.
Site Recovery integrates with Azure for simple application network management, including reserving IP addresses, configuring load-balancers, and integrating Azure Traffic Manager for efficient network switchovers.
What can be replicate?
Replicate Azure VMs from one Azure region to another.
Replicate on-premises VMware VMs, Hyper-V VMs managed by System Center VMM, and physical servers to a secondary site.
Replicate on-premises VMware VMs, Hyper-V VMs, physical servers (Windows and Linux), Azure Stack VMs to Azure.
Review the replication requirements for Azure VM replication, on-premises VMware VMs and physical servers, and on-premises Hyper-V VMs.
You can replicate any workload running on a machine that's supported for replication.