Study guide
7.5 Hyper-V Virtual Hard Disks & Checkpoint Management
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
7.5 Hyper-V Virtual Hard Disks & Checkpoint Management
Key Takeaways Explain This Topic AI
VHDX is the standard modern disk format supporting up to 64 TB, 4 KB logical sector alignment, and log-based power failure resilience, while VHD Set (VHDS) provides shared virtual disks for guest clustering.
Virtual disk provisioning types include Fixed Size (predictable peak IOPS, zero host storage oversubscription risk), Dynamically Expanding (space-efficient, expands on demand), and Differencing (parent-child delta chain).
Production Checkpoints use in-guest Volume Shadow Copy Service (VSS) or Linux fsfreeze to create application-consistent point-in-time disk state without capturing memory, but a checkpoint is not a durable backup.
A Windows Server 2012-or-newer domain controller on a VM-GenerationID-aware hypervisor detects checkpoint restore, resets its invocation ID and RID pool, and safely resynchronizes; unreplicated post-checkpoint changes are still lost.
Checkpoint deletion triggers automated, asynchronous live merging of the .avhdx differencing file back into the parent base VHDX without requiring virtual machine downtime.
Last updated: August 2026
Hyper-V Virtual Hard Disks & Checkpoint Management
Storage subsystem configuration in Hyper-V dictates virtual machine I/O performance, data resilience, snapshot integrity, and multi-node clustering capabilities. Understanding virtual hard disk formats, provisioning models, PowerShell maintenance cmdlets, and the operational differences between Production and Standard Checkpoints is vital for Windows Server enterprise operations.
1. Virtual Hard Disk Formats: VHD vs VHDX vs VHD Set
Hyper-V supports three distinct virtual hard disk formats, each engineered for specific storage architectures and operational lifecycles. +-----------------------------------------------------------------------------------------+
- | VIRTUAL HARD DISK FORMAT SPECIFICATIONS |
- | |
- | VHD (Legacy Format) VHDX (Modern Standard) VHD SET (.VHDS Shared) |
- | +--------------------------+ +--------------------------+ +----------------------+ |
- | | Max Capacity: 2 TB | | Max Capacity: 64 TB | | Shared Guest Cluster | |
- | | Sector Size: 512 bytes | | Sector Size: 4 KB (4Kn) | | Shared SCSI Disk | |
- | | Vulnerable to corruption | | Resilient internal log | | Host-level VSS backup| |
- | | on sudden power failure | | tracks metadata updates | | Online disk resizing | |
- | +--------------------------+ +--------------------------+ +----------------------+ |
- +-----------------------------------------------------------------------------------------+
- Detailed Technical Comparison
- Specification VHD (Legacy) VHDX (Modern Default) VHD Set ( .vhds )
- Maximum Size 2040 GB (~2 TB) 64 TB 64 TB
- Logical Sector Alignment 512 bytes 4 KB (Advanced Format 4Kn / 512e) 4 KB
Power Failure Resilience Low (susceptible to header corruption) High (Internal transaction log protects metadata integrity) High (VHDX-backed architecture)
Performance Profile Standard I/O alignment Optimized for modern large-sector physical storage arrays Optimized for multi-VM shared access
Shared Storage Clustering Not Supported Supported only via legacy Shared VHDX Native Shared Storage for Guest Failover Clusters
Online Resizing Not Supported Supported (Expand/Shrink while VM is running) Supported (Expand/Shrink while cluster is online)
- Host-Level Backup Supported Supported Supported (Allows host VSS backups of guest cluster disks)
- The VHD Set ( .vhds ) Architecture for Guest Clustering
Prior to Windows Server 2016, building a Guest Failover Cluster (clustering two VMs across physical hosts) required presenting physical Fibre Channel/iSCSI LUNs directly into VMs or using legacy shared VHDX files (which could not be backed up at the host level or resized online).
VHD Sets ( .vhds ) solve this by maintaining a small metadata file ( .vhds ) referencing underlying .avhdx differencing files for each cluster node.
Fully supports online disk resizing and host-level Hyper-V VSS backups without exposing physical SAN architecture into guest operating systems. # Create a new shared VHD Set for guest clustering
- New-VHD -Path "C:\ClusterStorage\Volume1\SharedDisks\GuestClusterDisk.vhds" `
- SizeBytes 500GB `
- Dynamic
- 2. Virtual Disk Provisioning Models
When provisioning VHD or VHDX files, administrators choose between three storage allocation models: +-----------------------------------------------------------------------------------------+
- | VIRTUAL DISK PROVISIONING COMPARISON |
- | |
- | [FIXED SIZE] [DYNAMICALLY EXPANDING] [DIFFERENCING DISK] |
- | +--------------------------+ +--------------------------+ +----------------------+ |
- | | Physical host storage is | | Physical storage starts | | Parent Base Disk | |
- | | 100% pre-allocated at | | minimal (~4 MB) and | | (Read-Only Template) | |
- | | disk creation time. | | expands on demand up to | +----------+-----------+ |
- | | | | max declared boundary. | | (Delta) |
- | | - Zero allocation latency| | | +----------v-----------+ |
- | | - Zero overcommit risk | | - High space efficiency | | Child Differencing | |
- | | - Highest sustained IOPS | | - Allocation overhead | | Disk (.vhdx / .avhdx)| |
- | +--------------------------+ +--------------------------+ +----------------------+ |
- +-----------------------------------------------------------------------------------------+
Fixed Size Virtual Hard Disks:
The entire virtual disk capacity is allocated on the physical storage array when created.
Advantages: Highest predictable read/write IOPS, zero runtime block allocation overhead, no risk of host volume oversubscription/exhaustion.
Use Case: High-throughput transactional databases (SQL Server, Oracle) and enterprise production workloads.
Dynamically Expanding Virtual Hard Disks:
Allocates a minimal header file on physical storage and grows incrementally as data blocks are written inside the guest OS.
Advantages: Maximizes storage utilization across multi-VM density environments.
Trade-offs: Small performance overhead during block expansion; risk of physical volume exhaustion if overprovisioned storage is fully written by multiple VMs.
Differencing Disks:
A parent-child relationship where the parent disk is designated Read-Only (e.g., a sysprepped Windows Server golden image), and all subsequent writes/deltas are stored in the child differencing disk.
Crucial Rule: The parent virtual hard disk must never be modified . If the parent disk is booted, edited, or corrupted, the entire child differencing disk chain is permanently invalidated and destroyed.
3. PowerShell Disk Management Operations
Hyper-V provides comprehensive PowerShell cmdlets for creating, inspecting, resizing, converting, and compacting virtual disks. # 1. Create a 100 GB Dynamically Expanding VHDX
New-VHD -Path "D:\Hyper-V\Disks\AppDisk.vhdx" -SizeBytes 100GB -Dynamic
- # 2. Create a Differencing Disk linked to a Golden Master parent
- New-VHD -Path "D:\Hyper-V\Disks\ChildVM01.vhdx" `
- ParentPath "D:\Hyper-V\Templates\Server2025_Master.vhdx" `
- Differencing
- # 3. Expand a VHDX online while the VM is running
- Resize-VHD -Path "D:\Hyper-V\Disks\AppDisk.vhdx" -SizeBytes 250GB
- # 4. Convert a legacy VHD to modern VHDX format (offline)
- Convert-VHD -Path "D:\Hyper-V\Disks\LegacyDisk.vhd" `
- DestinationPath "D:\Hyper-V\Disks\ModernDisk.vhdx" `
- VHDType Dynamic
- # 5. Compact a Dynamically Expanding VHDX to reclaim unallocated zeroed blocks
- # Step A: Mount VHDX as Read-Only
- Mount-VHD -Path "D:\Hyper-V\Disks\AppDisk.vhdx" -ReadOnly
- # Step B: Optimize and shrink physical file footprint
- Optimize-VHD -Path "D:\Hyper-V\Disks\AppDisk.vhdx" -Mode Full
- # Step C: Dismount VHDX
- Dismount-VHD -Path "D:\Hyper-V\Disks\AppDisk.vhdx"
- 4. Checkpoint Architecture: Standard vs Production Checkpoints
Hyper-V provides two distinct checkpoint architectures that operate on fundamentally different underlying principles. +-----------------------------------------------------------------------------------------+
- | STANDARD VS PRODUCTION CHECKPOINT ARCHITECTURE |
- | |
- | [STANDARD CHECKPOINT (Legacy Snapshot)] [PRODUCTION CHECKPOINT (Default)] |
- | +---------------------------------------+ +------------------------------------+ |
- | | Captures Active CPU & RAM State | | NO Memory State Captured | |
- | | Creates .avhdx differencing disk | | Invokes In-Guest VSS / fsfreeze | |
- | | Restores exact running millisecond | | Flushes in-flight I/O transactions | |
- | | | | Creates clean application- | |
- | | Not application-consistent | | Application-consistent disk state | |
- | | Captures volatile memory state | | Still not a durable backup | |
- | +---------------------------------------+ +------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
- Comprehensive Checkpoint Comparison Matrix
Architectural Attribute Standard Checkpoint Production Checkpoint (Default)
In-Guest Mechanism None (Hypervisor freezes CPU execution) Volume Shadow Copy Service (VSS) in Windows; fsfreeze in Linux
Memory (RAM) State Captured & dumped to .vmrs / .bin state file Zero memory state captured ; VM boots cleanly upon restoration
Application Consistency None (Application memory is frozen mid-transaction) Application-consistent (VSS writers flush database buffers to disk)
Transactional Workloads Not application-consistent; avoid as a rollback point for databases VSS-consistent point-in-time state; still not a durable backup
Reversion Behavior Restores disk plus captured execution and memory state Restores application-consistent disk state and starts the guest cleanly
Disk Mechanism Creates .avhdx differencing disk Creates .avhdx differencing disk # Configure a VM to enforce Production Checkpoints
Set-VM -VMName "VM-SQL-01" -CheckpointType Production
- # Configure ProductionOnly (fails if VSS snapshot cannot be taken instead of falling back to Standard)
- Set-VM -VMName "VM-SQL-01" -CheckpointType ProductionOnly
- # Disable checkpoints entirely on a mission-critical workload
- Set-VM -VMName "VM-DC-01" -CheckpointType Disabled
- 5. Domain Controller Checkpoint Restore: Safe Restore vs. USN Rollback
The result of reverting a virtualized domain controller depends on both the guest version and how the rollback was performed. Do not apply the old “every snapshot causes USN rollback” rule to a modern Hyper-V deployment.
VM-GenerationID-Aware Safe Restore
Windows Server 2012 and later AD DS stores the hypervisor-provided VM-GenerationID in NTDS.dit and compares it with the current value when the domain controller starts. A supported Hyper-V checkpoint restore changes that identifier. On detecting a mismatch, AD DS:
Generates a new replication invocation ID so the restored database is treated as a new incarnation.
Discards the local RID pool, preventing duplicate security identifiers.
Performs non-authoritative inbound replication for AD DS changes and resynchronizes SYSVOL.
Those safeguards prevent reuse of old update sequence numbers and let the domain controller safely re-enter replication. They do not make a checkpoint a backup: locally originated changes made after the checkpoint and never replicated outbound are permanently lost. Microsoft recommends Windows Server Backup inside the guest for durable domain-controller recovery.
When USN Rollback Is Still a Risk
A legacy domain controller, a hypervisor that does not expose VM-GenerationID, or a restore method that does not change the identifier can bypass safe restore. Copying an older VHD/VHDX into place and some file- or full-disk restore workflows fall into that category. The restored DC may reuse USNs that its partners have already recorded in their high-water marks. AD DS can quarantine detected rollback by stopping Netlogon and inbound and outbound replication and logging Directory Service event 2095; undetected cases can produce inconsistent objects and lingering-object cleanup.
The exam distinction is therefore precise: supported checkpoint restore of a Windows Server 2012-or-newer DC on VM-GenerationID-aware Hyper-V triggers safe restore; unsupported image rollback can trigger USN rollback. Use neither path as a substitute for an AD-aware system-state backup.
6. Checkpoint Operations & Automatic Live Merging
Managing checkpoints in Hyper-V is streamlined via PowerShell: # Create a new checkpoint before performing OS patching
Checkpoint-VM -VMName "VM-APP-01" -SnapshotName "Pre-Patching-Baseline"
- # Query existing checkpoints for a VM
- Get-VMSnapshot -VMName "VM-APP-01"
- # Restore a VM to a designated checkpoint
- Restore-VMSnapshot -VMName "VM-APP-01" -Name "Pre-Patching-Baseline" -Confirm:$false
- # Delete/Remove a checkpoint
- Remove-VMSnapshot -VMName "VM-APP-01" -Name "Pre-Patching-Baseline"
- Background Live Merge Mechanics
When a checkpoint is created, Hyper-V freezes the base .vhdx file and writes all ongoing disk I/O into an .avhdx differencing disk .
When an administrator executes Remove-VMSnapshot , Hyper-V initiates an asynchronous Live Merge in the background.
The hypervisor merges all delta blocks from the .avhdx file directly back into the parent .vhdx while the virtual machine remains fully online and running .
Once the merge reaches 100% completion, Hyper-V points the VM worker process back to the parent .vhdx and automatically deletes the orphaned .avhdx file from physical disk storage.