Evaluate Azure-specific HADR solutions
In this we will learn how to Evaluate Azure-specific HADR solutions.
Azure only: Disaster recovery solutions
You can have a disaster recovery solution for your SQL Server databases in Azure by using availability groups, database mirroring, or backup and restore with storage blobs.
Availability groups
- Firstly, availability replicas running across multiple datacenters in Azure VMs for disaster recovery. However, this cross-region solution helps protect against a complete site outage.
- Secondly, within a region, all replicas should be within the same cloud service and the same virtual network. Because each region will have a separate virtual network, these solutions require network-to-network connectivity.
Database mirroring
Principal and mirror and servers running in different datacenters for disaster recovery. However, you must deploy them by using server certificates. Further, SQL Server database mirroring is not supported for SQL Server 2008 or SQL Server 2008 R2 on an Azure VM.
Backup and restore with Azure Blob storage
Production databases backed up directly to Blob storage in a different datacenter for disaster recovery.
Replicate and fail over SQL Server to Azure with Azure Site Recovery
Production SQL Server instance in one Azure datacenter replicated directly to Azure Storage in a different Azure datacenter for disaster recovery.
Hybrid IT: Disaster recovery solutions
You can have a disaster recovery solution for your SQL Server databases in a hybrid IT environment by using availability groups, database mirroring, log shipping, and backup and restore with Azure Blob storage.
Availability groups
- Some availability replicas running in Azure VMs and other replicas running on-premises for cross-site disaster recovery. However, the production site can be either on-premises or in an Azure datacenter. Because all availability replicas must be in the same failover cluster, the cluster must span both networks (a multi-subnet failover cluster).
- Secondly, this configuration requires a VPN connection between Azure and the on-premises network.
- Further, for successful disaster recovery of your databases, you should also install a replica domain controller at the disaster recovery site.
Database mirroring
- One partner running in an Azure VM and the other running on-premises for cross-site disaster recovery by using server certificates. However, partners don’t need to be in the same Active Directory domain, and no VPN connection is required.
Further, another database mirroring scenario involves one partner running in an Azure VM and the other running on-premises in the same Active Directory domain for cross-site disaster recovery. A VPN connection between the Azure virtual network and the on-premises network is required. - Lastly, for successful disaster recovery of your databases, you should also install a replica domain controller at the disaster recovery site.
Log shipping
- One server running in an Azure VM and the other running on-premises for cross-site disaster recovery. However, Log shipping depends on Windows file sharing. So a VPN connection between the Azure virtual network and the on-premises network is necessary.
- Further, for successful disaster recovery of your databases, you should also install a replica domain controller at the disaster recovery site.
Reference: Microsoft Documentation