Study guide
8.2 Hyper-V Replica & Azure Site Recovery (ASR)
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
8.2 Hyper-V Replica & Azure Site Recovery (ASR)
Key Takeaways Explain This Topic AI
Hyper-V Replica provides host-level, storage-agnostic asynchronous virtual machine replication across standalone or clustered Hyper-V hosts over standard LAN/WAN connections.
Replication authentication supports HTTP over TCP port 80 (Kerberos authentication within trusted Active Directory forests) or HTTPS over TCP port 443 (mutual X.509 certificate authentication for cross-domain or untrusted networks).
Replication frequency can be configured for 30 seconds (low latency), 5 minutes (standard baseline), or 15 minutes (bandwidth constrained), with optional VSS-enabled application-consistent snapshots.
Extended Replica enables cascading replication from the secondary replica server to a tertiary disaster recovery site, supporting multi-tier geographic business continuity.
Azure Site Recovery (ASR) automates the replication of on-premises Hyper-V virtual machines directly to Azure Managed Disks, providing cloud-orchestrated failover, isolated test drills, and non-disruptive failback.
Last updated: August 2026
Hyper-V Replica & Azure Site Recovery (ASR)
Disaster recovery planning ensures an organization can maintain operational continuity when a catastrophic event—such as a flood, extended power blackout, cyber incident, or localized datacenter failure—destroys or isolates primary compute infrastructure. In Microsoft hybrid environments, organizations achieve comprehensive disaster recovery through two primary technologies:
Hyper-V Replica : A built-in, host-level asynchronous replication feature that replicates virtual machines between on-premises Hyper-V hosts without requiring expensive storage arrays or SAN replication licenses.
Azure Site Recovery (ASR) : A cloud-native disaster recovery orchestration service that replicates on-premises Hyper-V virtual machines directly into Microsoft Azure storage, providing low-cost, cloud-burst failover capabilities.
1. Hyper-V Replica Architecture & Core Concepts
Hyper-V Replica operates at the hypervisor layer, tracking changes to a virtual machine's virtual hard disks ( .vhdx ) using a log-based tracking mechanism. Periodically, these delta change logs are compressed and transmitted across the network to a secondary (Replica) Hyper-V host, where they are applied to the replica virtual disks. +-----------------------------------------------------------------------------------------+
- | HYPER-V REPLICA ARCHITECTURE |
- | |
- | PRIMARY SITE (Production) REPLICA SITE (Disaster Recovery) |
- | +------------------------------------+ +------------------------------------+|
- | | Primary Hyper-V Host | | Secondary Replica Hyper-V Host ||
- | | [VM-PROD-01 (Running)] | | [VM-PROD-01 (Off / Standby)] ||
- | | - VHDX Active Writes | | - Replica VHDX Disk Base ||
- | | - Replication Delta Log (HRL) | | - Recovery Point Snapshots (HRL) ||
- | +-----------------+------------------+ +-----------------+------------------+|
- | | ^ |
- | |======== Asynchronous Replication Delta =======| |
- | HTTP Port 80 (Kerberos) / |
- | HTTPS Port 443 (Certificates) |
- | |
- | CASCADE (OPTIONAL): |
- | Secondary Replica Host ======= Extended Replication ======> Tertiary DR Site Host |
- | (30s / 5m / 15m) |
- +-----------------------------------------------------------------------------------------+
Key Architectural Characteristics:
Storage-Agnostic: Primary and replica hosts can use completely different storage subsystems (e.g., primary on NVMe SAN, replica on local DAS SATA drives).
Workload-Agnostic: Replicates any guest operating system supported by Hyper-V (Windows Server, Windows client, Linux).
Cluster Integration (Hyper-V Replica Broker): When primary or secondary Hyper-V hosts are clustered, the Hyper-V Replica Broker cluster role must be provisioned. The Broker provides a single virtual NetBIOS/FQDN name and IP address, managing VM placement and tracking replica states even if the VM Live Migrates between cluster nodes.
2. Replication Authentication & Transport Security
Hyper-V Replica supports two distinct authentication and encryption protocols for data transmission: +-----------------------------------------------------------------------------------------+
- | HYPER-V REPLICA AUTHENTICATION MODES COMPARISON |
- | |
- | AUTHENTICATION MODE PORT / PROTOCOL SECURITY ATTRIBUTES BEST DEPLOYMENT |
- | --------------------+-----------------+------------------------+----------------------|
- | Kerberos (HTTP) | TCP Port 80 | - Mutual AD auth | Single Active |
- | | (Unencrypted) | - Unencrypted payload | Directory Forest |
- | | | - Requires domain join | Dedicated secure WAN |
- | --------------------+-----------------+------------------------+----------------------|
- | Certificates (HTTPS)| TCP Port 443 | - Mutual X.509 certs | Untrusted domains, |
- | | (Encrypted TLS) | - Full SSL/TLS payload | Cross-forest, |
- | | | - Subject Name/SAN chk | DMZ, Public Internet |
- +-----------------------------------------------------------------------------------------+
Certificate Authentication Requirements:
When using HTTPS (Port 443) mutual certificate authentication, X.509 certificates installed on both primary and replica servers must satisfy strict validation rules:
Enhanced Key Usage (EKU): Must support both Client Authentication ( 1.3.6.1.5.5.7.3.2 ) and Server Authentication ( 1.3.6.1.5.5.7.3.1 ).
Subject Alternative Name (SAN): Must match the FQDN of the Hyper-V host or the Hyper-V Replica Broker cluster name.
Trust Chain & Revocation: Must chain up to a trusted Root CA installed in the Trusted Root Certification Authorities certificate store on both hosts, with accessible CRL (Certificate Revocation List) distribution points. # Configure the local Hyper-V host as a Replica Server accepting HTTPS traffic
- Set-VMReplicationServer -ReplicationEnabled $true `
- AllowedAuthenticationType Certificate `
- CertificateThumbprint "3A5B7C9D0E1F2A3B4C5D6E7F8A9B0C1D2E3F4A5B" `
- ReplicationAllowedLocationsPath "D:\Hyper-V\ReplicationStorage" `
- DefaultStorageMappingType BySystemName `
- Port 443
- 3. Replication Intervals & Recovery Point Types
Hyper-V Replica allows administrators to tailor the Recovery Point Objective (RPO) and snapshot retention policy per virtual machine.
1. Replication Frequency
Administrators select one of three preset replication intervals:
30 Seconds: Minimizes data loss for critical transactional workloads; requires high-throughput, low-latency network interconnects.
5 Minutes: The default balanced setting for standard enterprise workloads.
15 Minutes: Designed for low-bandwidth, high-latency WAN links or branch office links.
2. Recovery Point Retention & Application Consistency
Standard (Crash-Consistent) Recovery Points: Captures the state of virtual hard disks at the exact moment of replication. Captures data on disk as if the server suffered a power outage.
Additional Recovery Points: Allows storing hourly historical snapshots for up to 24 hours , enabling administrators to roll back ransomware infections or database corruption to an earlier point in time.
Volume Shadow Copy Service (VSS) Application-Consistent Snapshots: Hyper-V invokes the in-guest VSS framework via Hyper-V Integration Services to flush open application memory buffers, commit database transactions (e.g., SQL Server or Exchange), and write clean recovery points at configured intervals (e.g., every 1 to 12 hours). # Enable replication for a specific production VM with 30-second interval and VSS snapshots
- Enable-VMReplication -VMName "VM-SQL-01" `
- ReplicaServerName "hv-dr-host.corp.contoso.com" `
- ReplicaServerPort 443 `
- AuthenticationType Certificate `
- CertificateThumbprint "3A5B7C9D0E1F2A3B4C5D6E7F8A9B0C1D2E3F4A5B" `
- CompressionEnabled $true `
- ReplicationFrequencySec 30 `
- RecoveryHistory 24 `
- VSSSnapshotFrequencyHour 4
- # Initiate the baseline initial replication over the network
- Start-VMInitialReplication -VMName "VM-SQL-01"
- 3. Extended Replica (Cascading DR)
Extended Replica (also known as 3-tier replication) allows the secondary replica server to forward incoming replication deltas to a tertiary disaster recovery site. For example: Primary (Chicago) --> Secondary Replica (Dallas) --> Extended Replica (Phoenix) .
Constraint: The extended replication interval must be equal to or greater than the primary replication frequency (e.g., if Primary-to-Secondary is 5 minutes, Secondary-to-Tertiary must be 5 minutes or 15 minutes).
Loading diagram... Hyper-V Replica Failover Types & Workflows
4. Failover Operations: Test, Planned, and Unplanned
Hyper-V Replica supports three distinct operational failover workflows: +-----------------------------------------------------------------------------------------+
- | FAILOVER WORKFLOW CHARACTERISTICS |
- | |
- | FEATURE TEST FAILOVER PLANNED FAILOVER UNPLANNED FAILOVER|
- | --------------------+----------------------+----------------------+-------------------|
- | Primary VM State | Continues running | Must be turned off | Destroyed/Offline |
- | Data Loss (RPO) | None (Isolated test) | Zero data loss (RPO=0| Potential data |
- | | | | loss (RPO > 0) |
- | Replication Impact | Continues unhindered | Flushes final delta | Severed / Stopped |
- | Target Network | Isolated non-prod VMS| Production network | Production network|
- | Execution Location | Secondary Host | Primary Host first | Secondary Host |
- +-----------------------------------------------------------------------------------------+
- 1. Test Failover ( Start-VMFailover -AsTest )
Allows testing disaster recovery runbooks without interrupting production workloads or pausing replication. Hyper-V creates a temporary test virtual machine ( VM-SQL-01 - Test ) instantiated from a chosen recovery point and attaches it to an isolated, non-routable virtual switch. After testing, Stop-VMFailover -AsTest deletes the temporary VM and discards its differencing disks.
2. Planned Failover ( Start-VMFailover )
Used during scheduled maintenance, anticipated weather emergencies, or planned datacenter migrations. Guarantees zero data loss (RPO = 0) :
The primary VM is cleanly powered off.
The administrator triggers planned failover from the primary host ( Start-VMFailover -VMName "VM-SQL-01" -Prepare ).
Hyper-V transmits all uncommitted pending write deltas to the replica server.
The replica server starts the VM.
Reverse replication is configured to protect the workload back to the primary site ( Set-VMReplication -Reverse ).
3. Unplanned Failover
Executed directly on the secondary Replica host when the primary datacenter suffers total unexpected destruction. The administrator selects the most recent or known-good recovery point and powers on the replica VM. Because unexpected outages prevent sending the final uncommitted delta, an unplanned failover carries some data loss bounded by the configured replication interval.
5. Azure Site Recovery (ASR) for Hyper-V
Azure Site Recovery (ASR) extends disaster recovery into the cloud by orchestrating replication of on-premises Hyper-V virtual machines directly to Microsoft Azure Storage . +-----------------------------------------------------------------------------------------+
- | AZURE SITE RECOVERY (ASR) ARCHITECTURAL FLOW |
- | |
- | [ON-PREMISES HYPER-V HOST] [AZURE CLOUD INFRASTRUCTURE] |
- | +-------------------------------+ +---------------------------------+ |
- | | Windows Server 2022 Hyper-V | | Recovery Services Vault | |
- | | - ASR Provider | | - Replication Policy | |
- | | - MARS Agent |=== HTTPS 443 ==>| - Recovery Plans & Runbooks | |
- | | | +---------------------------------+ |
- | | [VM-APP-01] | | |
- | | - Real-time VHDX Delta Log | +--------------v------------------+ |
- | +-------------------------------+ | Azure Storage (Managed Disks) | |
- | | - Standard / Premium SSD Disks | |
- | +---------------------------------+ |
- +-----------------------------------------------------------------------------------------+
ASR Deployment Components & Workflow:
Recovery Services Vault: The centralized Azure Resource Manager entity that holds replication policies, recovery plans, and orchestration mappings.
Azure Site Recovery Provider & MARS Agent: Installed on physical Hyper-V cluster nodes. Communicates outbound over HTTPS (Port 443) with Azure; no incoming firewall ports required.
Storage Replication: Virtual disk changes replicate to Azure Storage Accounts (or directly to Azure Managed Disks). In steady-state replication, no Azure virtual machine compute charges are incurred —organizations pay only for raw blob/disk storage consumption.
Recovery Plans & Orchestration: ASR Recovery Plans group multi-tier applications (e.g., Web tier, Application tier, Database tier) into sequenced failover groups, executing integrated Azure Automation Runbooks to update DNS records, adjust load balancers, and assign network security groups upon failover.