How to Configure Hyper-V Replica Between Two Hosts
Applies to: Windows Server 2019, 2022 and 2025.
Hyper-V Replica asynchronously copies VM changes to a recovery host. It improves recovery options but does not replace backup or application-level replication.
Hyper-V changes affect network and workload availability. Keep console access and tested VM backups. Visit networkmanager.info for managed Windows VPS services.
Prerequisites
- Prepare source and replica hosts.
- Choose Kerberos HTTP or certificate HTTPS authentication.
- Plan replica storage and firewall.
- Measure bandwidth and RPO needs.
Procedure
Step 1: Enable replica server
Example uses Kerberos on an isolated trusted domain network.
Set-VMReplicationServer -ReplicationEnabled $true -AllowedAuthenticationType Kerberos -KerberosAuthenticationPort 80 -ReplicationAllowedFromAnyServer $falseStep 2: Create authorization entry
Allow the source group and target storage through Hyper-V Settings or supported cmdlets.
Step 3: Enable VM replication
Specify recovery host and frequency.
Enable-VMReplication -VMName 'APP01' -ReplicaServerName 'HV02.corp.example' -AuthenticationType Kerberos -CompressionEnabled $true -ReplicationFrequencySec 300Step 4: Start initial copy
Begin replication.
Start-VMInitialReplication -VMName 'APP01'Step 5: Monitor health
Review state, backlog and last synchronization.
Verification
Replication state should be Replicating with normal health.
Get-VMReplication -VMName APP01 | Format-List State,Health,Mode,FrequencySec,LastReplicationTimeRollback
Use Remove-VMReplication after confirming recovery requirements and preserving the replica or backup needed by the continuity plan.
Operational notes
Test failover should be exercised on an isolated network without disrupting production identity or IP addressing.
Official references
Explore Netcloud24 Canada.
