Azure Site Recovery Usage Scenarios
Usage Scenarios for Azure Site Recovery - paraphrased from various online articles:
* Disaster recovery in the cloud—You can replicate workloads running on running on supported on-premises Hyper-V VMs, VMware VMs, and physical servers to Azure, rather than to a secondary site. This eliminates the cost and complexity of maintaining a secondary datacenter. ASR provides orchestrated disaster recovery as a service (DRaaS). When failover occurs, Azure VMs are created based on the replicated data. 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. You can easily fail back to your primary site when it's available again. Advanced network management in Site Recovery and Azure simplifies application network requirements, including reserving IP addresses, configuring load-balancers, and integrating Azure Traffic Manager for efficient network switchovers.
* Migrate on-premises AWS instances to Azure VMs, or to migrate Azure VMs between Azure regions.
* Testing without disruption - You can easily run test failovers to support disaster recovery drills, without affecting production environments.
* No-impact recovery plan testing - Recovery plans allow you to model and customize failover and recovery of multi-tier applications that are spread over multiple VMs. You order groups within plans, and add scripts and manual actions. Recovery plans can be integrated with Azure automation runbooks.
* Protect the SQL Server back end of an application using a combination of SQL Server business continuity and disaster recovery (BCDR) technologies, and Azure Site Recovery.
* Disaster recovery in the cloud—You can replicate workloads running on running on supported on-premises Hyper-V VMs, VMware VMs, and physical servers to Azure, rather than to a secondary site. This eliminates the cost and complexity of maintaining a secondary datacenter. ASR provides orchestrated disaster recovery as a service (DRaaS). When failover occurs, Azure VMs are created based on the replicated data. 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. You can easily fail back to your primary site when it's available again. Advanced network management in Site Recovery and Azure simplifies application network requirements, including reserving IP addresses, configuring load-balancers, and integrating Azure Traffic Manager for efficient network switchovers.
* Testing without disruption - You can easily run test failovers to support disaster recovery drills, without affecting production environments.
* No-impact recovery plan testing - Recovery plans allow you to model and customize failover and recovery of multi-tier applications that are spread over multiple VMs. You order groups within plans, and add scripts and manual actions. Recovery plans can be integrated with Azure automation runbooks.
* Protect the SQL Server back end of an application using a combination of SQL Server business continuity and disaster recovery (BCDR) technologies, and Azure Site Recovery.
Comments
Post a Comment