Study guide

14.4 Storage Replica & Storage Quality of Service

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

14.4 Storage Replica & Storage Quality of Service

Key Takeaways Explain This Topic AI

Storage Replica replicates raw blocks below the file system, so open files, running VHDX files and live databases replicate without file locking.

Storage Replica runs on Windows Server Datacenter without limits and on Windows Server Standard from Windows Server 2019, where it is capped at a single volume of up to 2 TB.

Each partnership needs a data volume and a dedicated log volume on both sides, and the destination data volume is dismounted while replication is active.

Synchronous replication delivers RPO 0 and requires round-trip latency of about 5 ms or less; asynchronous replication has no latency recommendation but a non-zero RPO.

Storage QoS minimum IOPS is a soft reservation that raises alerts, while maximum IOPS is a hard token-bucket ceiling; Dedicated policies apply per disk and Shared policies pool the limit across a group.

Last updated: August 2026

Storage Replica & Storage Quality of Service

Maintaining business continuity and guaranteeing predictable storage performance are two sides of the same Windows Server storage discipline. Storage Replica protects a volume by mirroring its blocks to another server or cluster for disaster recovery, and Storage Quality of Service (Storage QoS) protects the workloads already running by keeping any single virtual machine from consuming the whole storage subsystem.

Mastering the operational mechanics of synchronous versus asynchronous replication, the volume and log requirements of a partnership, and the difference between Dedicated and Shared Storage QoS policies are core competencies tested on the AZ-800 exam.

1. Storage Replica Architecture & Mechanics

Storage Replica is a volume-level, block-based disaster recovery feature of Windows Server. It is unrestricted in Datacenter edition; Standard edition also supports it from Windows Server 2019 onward , but is limited to a single replicated volume of up to 2 TB in one partnership. Unlike application-level replication (such as Hyper-V Replica, SQL Server Always On, or DFS Replication), Storage Replica operates underneath the file system at the raw partition block layer. +-----------------------------------------------------------------------------------+

  • | STORAGE REPLICA ARCHITECTURE |
  • | |
  • | [SOURCE SERVER / NODE] [DESTINATION SERVER / NODE]|
  • | +-----------------------+ +------------------------+ |
  • | | Application (SQL/VM) | | Destination Filesystem | |
  • | +-----------------------+ | (Dismounted / Offline) | |
  • | | +------------------------+ |
  • | v ^ |
  • | +-----------------------+ +------------------------+ |
  • | | File System (NTFS/ReFS| | File System Driver | |
  • | +-----------------------+ +------------------------+ |
  • | | ^ |
  • | v | |
  • | +-----------------------+ +------------------------+ |
  • | | SR Filter Driver | =====(SMB3 / RDMA)=======> | SR Filter Driver | |
  • | +-----------------------+ Block-Level Replication +------------------------+ |
  • | | | | | |
  • | v v v v |
  • | [Src Log] [Src Data] [Dst Log] [Dst Data] |
  • | (Volume L:) (Volume D:) (Volume L:) (Volume D:) |
  • +-----------------------------------------------------------------------------------+
  • Key Architectural Characteristics

Block-Level Operation: Replicates raw storage blocks rather than individual files. It seamlessly replicates in-use files, open SQL Server .mdf / .ldf databases, running Hyper-V .vhdx disks, and locked system files without file system locking conflicts.

Storage-Agnostic: Operates across completely heterogeneous storage hardware. Source and destination volumes can reside on Storage Spaces Direct (S2D), SAN LUNs, iSCSI arrays, hardware RAID, or direct-attached NVMe/SATA drives.

Volume Pairing & Log Architecture:

Each replication partnership requires two volumes on the source and two matching volumes on the destination: one Data Volume (e.g., D: ) and one dedicated Log Volume (e.g., L: ).

Log volumes act as write-ahead transaction journals and must be formatted with NTFS or ReFS. To minimize write latency, log volumes should always reside on high-speed solid-state media (NVMe or SSD).

While replication is active, the destination Data Volume is placed in a dismounted / offline state to prevent accidental writes or split-brain corruption.

2. Replication Modes: Synchronous vs. Asynchronous

Storage Replica supports two fundamental replication modes based on Recovery Point Objective (RPO) requirements and network latency. +-----------------------------------------------------------------------------------+

  • | SYNCHRONOUS VS ASYNCHRONOUS REPLICATION MODES |
  • | |
  • | FEATURE / METRIC SYNCHRONOUS REPLICATION ASYNCHRONOUS REPLICATION |
  • | --------------------+-------------------------------+---------------------------|
  • | Recovery Point Obj. | **Zero Data Loss (RPO = 0)** | **Low RPO (RPO > 0)** |
  • | Acknowledgment Flow | App write acknowledged ONLY | App write acknowledged |
  • | | after destination log commit | immediately on source log |
  • | Latency Limit | **<= 5 ms Round-Trip (RTT)** | No strict latency limit |
  • | | (<= 2 ms recommended) | (Permits high WAN latency)|
  • | Bandwidth Req. | **>= 1 Gbps** (10GbE rec.) | Scaled to write rate |
  • | Network Distance | Metro-distance (< 30-50 km) | Global / Intercontinental |
  • | Primary Use Case | Campus HA / Stretched Cluster | Cross-region Disaster Rec.|
  • +-----------------------------------------------------------------------------------+
  • Synchronous Replication Write Sequence

The application issues a write I/O to the source file system.

The Storage Replica filter driver intercepts the write and writes the block to the Source Log Volume .

Simultaneously, the driver transmits the block across the network (over SMB3/RDMA on TCP port 445 / port 5445) to the destination server.

The destination filter driver writes the block into the Destination Log Volume .

The destination server sends a write acknowledgment back to the source server.

The source server sends an I/O completion confirmation to the application.

In the background, both source and destination asynchronously flush data blocks from their respective Log Volumes to their Data Volumes.

3. Storage Replica Topologies & PowerShell Management

Storage Replica can be deployed across four architectural topologies: +-----------------------------------------------------------------------------------+

  • | STORAGE REPLICA TOPOLOGIES |
  • | |
  • | 1. SERVER-TO-SERVER (Standalone to Standalone) |
  • | [Server01 (D: & L:)] ============================> [Server02 (D: & L:)] |
  • | |
  • | 2. CLUSTER-TO-CLUSTER (Cluster to Cluster) |
  • | [Cluster 1 (CSV D: & L:)] =======================> [Cluster 2 (CSV D: & L:)] |
  • | |
  • | 3. STRETCHED CLUSTER (Single Cluster Spanning Two Sites) |
  • | [Site A Nodes (CSV D:)] <--(Auto Failover / SR)--> [Site B Nodes (CSV D:)] |
  • | |
  • | 4. SERVER-TO-SELF (Test / Volume-to-Volume on Same Machine) |
  • | [Server01 Volume D:] ============================> [Server01 Volume F:] |
  • +-----------------------------------------------------------------------------------+
  • Topology Details

Server-to-Server: Replicates volumes between two standalone Windows Server instances. Manual failover involves reversing replication direction.

Cluster-to-Cluster: Replicates storage between two independent Failover Clusters (e.g., Primary Datacenter S2D Cluster to DR Datacenter S2D Cluster).

Stretched Cluster (Stretch Cluster): A single Failover Cluster spanning two geographic sites with site awareness. Storage Replica handles the underlying storage replication while Failover Clustering orchestrates automated virtual machine live migration and failover.

  • Deploying Storage Replica via PowerShell # Step 1: Install Storage Replica Feature on both servers
  • Install-WindowsFeature -Name Storage-Replica, FS-FileServer -IncludeManagementTools -Restart
  • # Step 2: Validate replication topology, network latency, and disk write performance
  • Test-SRTopology `
  • SourceComputerName 'SRV-NYC-01' `
  • SourceVolumeName 'D:' `
  • SourceLogVolumeName 'L:' `
  • DestinationComputerName 'SRV-MIA-01' `
  • DestinationVolumeName 'D:' `
  • DestinationLogVolumeName 'L:' `
  • DurationInMinutes 10 `
  • ResultPath 'C:\SRReports'
  • # Step 3: Establish a Synchronous Server-to-Server Replication Partnership
  • New-SRPartnership `
  • SourceComputerName 'SRV-NYC-01' `
  • SourceRGName 'RG-NYC-Data' `
  • SourceVolumeName 'D:' `
  • SourceLogVolumeName 'L:' `
  • DestinationComputerName 'SRV-MIA-01' `
  • DestinationRGName 'RG-MIA-Data' `
  • DestinationVolumeName 'D:' `
  • DestinationLogVolumeName 'L:' `
  • ReplicationMode Synchronous
  • # Step 4: Query replication status and synchronization progress
  • Get-SRPartnership
  • Get-SRGroup
  • # Step 5: Execute Disaster Recovery Failover (Reverse Replication Direction)
  • Set-SRPartnership `
  • NewSourceComputerName 'SRV-MIA-01' `
  • SourceRGName 'RG-MIA-Data' `
  • DestinationComputerName 'SRV-NYC-01' `
  • DestinationRGName 'RG-NYC-Data'
  • 4. Editions, Prerequisites and Network Requirements

Before a partnership can be created, the environment must satisfy a short but unforgiving prerequisite list:

  • Requirement Detail
  • Directory An Active Directory Domain Services forest — both servers must be domain members
  • Edition Datacenter (unlimited) or Standard from Windows Server 2019 (one partnership, one volume, ≤ 2 TB)
  • Compute At least 2 GB of RAM and two cores per server

Storage layout A data volume plus a dedicated log volume on each side; log volumes must be NTFS or ReFS and should be faster than the data storage

  • Partition style Both data volumes must be GPT ; MBR is not supported
  • Latency About 5 ms round trip or less for synchronous replication; no latency recommendation for asynchronous
  • Firewall A single IANA port — TCP 445 , or TCP 5445 when using an SMB Direct/iWARP configuration

Because the transport is SMB 3 , Storage Replica inherits SMB multichannel, RDMA support over iWARP, InfiniBand and RoCE v2, packet signing, AES-128-GCM encryption and Kerberos AES-256 authentication between nodes without any separate configuration.

Two behaviours are worth committing to memory because they invert common assumptions:

The destination volume is inaccessible while replicating. Its drive letter may still be visible in File Explorer, but no application can read or write it. Test-Failover temporarily mounts a read-write snapshot of the destination for backup or validation without breaking the partnership.

Storage Replica is not a backup. It replicates every block change, including deletions, immediately. A user who empties a volume empties both copies. Point-in-time recovery still requires a backup product, although Storage Replica does replicate VSS snapshots because it operates at the partition layer.

Network compression for Storage Replica data transfer is supported only on Windows Server Datacenter: Azure Edition from OS build 20348.1070 onward — it is not a general Windows Server capability.

5. Storage Quality of Service (Storage QoS)

In multi-tenant virtualization and shared storage environments, a single runaway virtual machine ("noisy neighbor") executing massive random I/O can saturate physical disk spindles or RDMA queues, starving adjacent mission-critical workloads. Storage Quality of Service (Storage QoS) in Windows Server Failover Clustering provides centralized policy management to regulate and guarantee IOPS throughput. +-----------------------------------------------------------------------------------+

  • | STORAGE QUALITY OF SERVICE (QoS) |
  • | |
  • | STORAGE QoS POLICY TYPES: |
  • | |
  • | 1. DEDICATED (SINGLE-INSTANCE) POLICY |
  • | Policy: Min 500 IOPS, Max 2,000 IOPS |
  • | - VM 1: Guaranteed 500 IOPS, Throttled at 2,000 IOPS |
  • | - VM 2: Guaranteed 500 IOPS, Throttled at 2,000 IOPS |
  • | (Limits apply INDIVIDUALLY to each VM) |
  • | |
  • | 2. SHARED (AGGREGATED) POLICY |
  • | Policy: Min 1,000 IOPS, Max 5,000 IOPS |
  • | - [VM 1 + VM 2 + VM 3] Collectively share the 5,000 IOPS limit |
  • | (Limits apply CUMULATIVELY across the group) |
  • +-----------------------------------------------------------------------------------+
  • Policy Parameters & Types

Minimum IOPS (Reservation): A soft reservation threshold (calculated using normalized 8 KB I/O units). If a workload receives fewer IOPS than the minimum, the cluster generates performance alerts for remediation.

Maximum IOPS (Limit): A hard ceiling enforced using a token-bucket algorithm. The storage subsystem throttles virtual machine I/O to prevent the workload from exceeding the defined limit.

Dedicated Policies: The minimum/maximum IOPS rules are applied independently and discretely to each assigned virtual hard disk or VM.

Shared Policies: The minimum/maximum IOPS thresholds are pooled and shared collectively across all assigned virtual disks or VMs. # Create a Dedicated Storage QoS Policy for High-Priority Database VMs

  • New-StorageQoSPolicy `
  • Name 'Gold-Tier-Policy' `
  • PolicyType Dedicated `
  • MinimumIops 1000 `
  • MaximumIops 5000
  • # Create a Shared Storage QoS Policy for Dev/Test VMs
  • New-StorageQoSPolicy `
  • Name 'DevTest-Shared-Policy' `
  • PolicyType Shared `
  • MinimumIops 500 `
  • MaximumIops 2500
  • # Assign the Policy to a Hyper-V Virtual Hard Disk Drive
  • Get-VM -Name 'VM-SQL-PROD' | Get-VMHardDiskDrive | Set-VMHardDiskDrive -StorageQoSPolicy 'Gold-Tier-Policy'
  • # Monitor Storage QoS Performance and Policy Compliance
  • Get-StorageQoSVolume
  • Get-StorageQoSFlow | Format-Table InitiatorName, StorageNodeName, NormalizedIops, Limit, Status

Loading diagram... Storage Replica Synchronous Write Sequence and Acknowledgment Pipeline