AZ-305 ยท Backup and disaster recovery
Disaster recovery with Azure Site Recovery
Azure Site Recovery for Azure-to-Azure, VMware/physical and Hyper-V to Azure, recovery plans, test failover, failover and failback, replication RPO.
Key points
- Site Recovery: replication with failover and failback; Azure VMs, VMware, Hyper-V (every 30 seconds), physical servers.
- Azure-to-Azure: Mobility service extension, source-region cache storage account.
- Crash-consistent points every 5 minutes; app-consistent off by default.
- Test failover: replication continues; planned: zero loss; unplanned: unreplicated changes lost.
- Recovery plans: groups, start-up order, runbooks.
Source: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-overview
Practice questions
How often does Site Recovery create crash-consistent recovery points for replicated Azure VMs?
- Every 30 seconds
- Every 5 minutes
- Every hour
- Once a day
Show answer
Answer: B. Every 5 minutes
Crash-consistent recovery points are generated every 5 minutes and this cannot be changed. App-consistent points follow the frequency you set in the replication policy.
Which sources can Azure Site Recovery replicate to Azure?
- Azure VMs from one region to another
- On-premises VMware virtual machines
- On-premises Hyper-V virtual machines
- An Azure SQL Database logical server
- Blob containers in a storage account
Show answer
Answer: A. Azure VMs from one region to another, B. On-premises VMware virtual machines, C. On-premises Hyper-V virtual machines
Site Recovery replicates machines: Azure VMs between regions, on-premises VMware VMs, Hyper-V VMs and physical servers. Azure SQL Database relies on its own geo-replication, failover groups and geo-restore, and blob data is protected by storage features and Azure Backup, not Site Recovery.
When you enable replication for an Azure VM with the default policy, Site Recovery creates app-consistent recovery points automatically.
Show answer
Answer: False
False. The default replication policy has an app-consistent snapshot frequency of 0 hours, which means disabled. Only crash-consistent points (every 5 minutes) are created until you set a frequency.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
