Study guide
8.2 Azure Site Recovery Architecture for Hybrid Workloads
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
8.2 Azure Site Recovery Architecture for Hybrid Workloads
Key Takeaways Explain This Topic AI
Azure Site Recovery replicates entire virtual machines for orchestrated failover of whole workloads -- it targets recovery time, while Azure Backup targets recovery point granularity and retention.
VMware/Hyper-V-to-Azure replication requires a configuration server, process server, and master target server; Azure-to-Azure replication needs only the Mobility service extension on each VM.
App-consistent recovery points quiesce the application for transactional integrity and are taken on a configurable interval (commonly 1-12 hours); crash-consistent points are more frequent but less reliable for databases.
Recovery plans group VMs into failover units with defined boot order and automation steps, which is what actually lets a multi-tier application meet a stated RTO.
Test failover validates a DR plan in an isolated network without disrupting production replication, satisfying recurring compliance-testing requirements described in exam scenarios.
Last updated: July 2026
Why This Topic Matters
Azure Site Recovery ( ASR ) is Microsoft's flagship disaster recovery orchestration service and the direct answer to the official skill "Recommend a recovery solution for Azure and hybrid workloads that meets recovery objectives" whenever the scenario spans on-premises and Azure together -- the "hybrid" half of that bullet. AZ-305 scenarios frequently describe a company with an on-premises VMware or Hyper-V estate that wants Azure as a DR target, or an Azure region that needs a DR partner region. Confusing ASR (replicates whole machines for orchestrated failover) with Azure Backup (protects point-in-time data) is one of the most common mistakes candidates make, and the exam exploits it directly.
Core Concept: ASR Replicates Machines, Not Just Data
ASR continuously replicates entire virtual machines -- OS disk, data disks, and configuration -- to a target location so the whole machine can be failed over and brought online, rather than restored file-by-file. This makes ASR the tool for recovery time , while Azure Backup (covered in the next section) is the tool for recovery point granularity and long-term retention.
Supported Replication Scenarios
- Source Target Replication components
- Azure VM (region A) Azure VM (region B) Mobility service extension on the VM; no separate servers needed
VMware VM (on-premises) Azure Configuration server, process server, master target server, Mobility service agent on each VM
Hyper-V VM (on-premises) Azure Hyper-V Recovery Manager integration via Configuration server, no in-guest agent required for Hyper-V
Physical server (on-premises) Azure Process server + Mobility service agent
For Azure-to-Azure replication, ASR uses continuous, near-real-time replication -- there is no separate configuration server to deploy, which is why the exam often frames Azure-to-Azure ASR as the simplest hybrid-adjacent DR pattern to recommend when both regions are already Azure.
For VMware/Hyper-V-to-Azure , three roles matter:
Configuration server -- coordinates replication, manages data flow, and hosts the process server (usually the first component deployed on-premises).
Process server -- installed alongside or near the configuration server; receives replication traffic, performs caching, compression, and encryption before sending to Azure.
Master target server -- automatically deployed in Azure; receives replicated data during failback.
Recovery Points, Consistency, and Recovery Plans
ASR keeps a rolling window of recovery points so you can fail over to a point before a corruption event, not just the latest replicated state. Two consistency types matter for the exam:
Crash-consistent recovery points are captured very frequently (as often as every few minutes) but only guarantee the disk state as if the VM had crashed -- in-flight application transactions may be incomplete.
App-consistent recovery points additionally quiesce the application (using VSS on Windows) so multi-tier applications like SQL Server come back in a transactionally consistent state. App-consistent snapshots are taken on a configurable interval, commonly defaulting to every few hours (adjustable from 1 to 12 hours), because the quiescing operation has more overhead than a crash-consistent snapshot.
A recovery plan groups multiple VMs (e.g., a web tier, an app tier, and a database tier) into one failover unit with defined boot order and can inject manual or automated (Azure Automation runbook) steps between tiers -- for example, waiting for the database tier to come fully online before starting the app tier.
Test Failover: Non-Disruptive Validation
One of ASR's most exam-relevant features is test failover , which spins up replica VMs in an isolated network without impacting production replication or the live environment. This lets an architect satisfy compliance requirements for periodic DR testing (a recurring theme across this whole chapter) without any customer-facing risk. A scenario asking "how do we validate our DR plan quarterly without disrupting production" is describing test failover almost verbatim.
Failover and Failback
After a real disaster, you perform a failover (planned, with a final data sync, or unplanned, from the last available recovery point) to bring the replica VMs online as the new production. Once the primary site is restored, failback reverses replication direction to resynchronize and cut back over -- ASR supports failback to the original on-premises site or original Azure region without a full re-protection from scratch, provided the original source is still recognized by the vault.
Common Decision Traps
Recommending Azure Backup when the requirement is "bring the whole application online in another region quickly" -- that is an ASR use case, not a backup use case.
Recommending ASR when the requirement is "retain 7 years of monthly snapshots for audit" -- that is a backup/long-term-retention use case, not ASR's job (ASR's recovery point window is measured in hours to a few days, not years).
Assuming crash-consistent recovery points are always sufficient for databases; app-consistent points are needed when transactional integrity at failover time is a stated requirement.
Forgetting that a recovery plan's boot order and automation steps are what actually make a multi-tier failover meet a stated RTO -- a bare VM-by-VM failover with no orchestration will be slower and less predictable.
Exam Scenario
A company runs a three-tier application on VMware on-premises and wants an Azure-based DR site with an RTO under 2 hours and the ability to test the DR plan every quarter without impacting production. The correct recommendation: deploy a configuration server and process server on-premises, enable ASR replication for all VMware VMs to the target Azure region, group the tiers into a recovery plan with the correct boot order, and use test failover for the quarterly validation requirement.