What is Hyper-V Replica and is it enough for DR?
Hyper-V Replica asynchronously replicates a VM to a second host, with intervals from 30 seconds to 15 minutes. Not a backup replacement, but a cheap DR mechanism if you have a second location.
Try this first
- 1Enable on the target host: in Hyper-V Manager, Replication Configuration, allow replication from a specific source server.
- 2On the source: right-click the VM, Enable Replication, pick the target host, replication frequency (30 sec, 5 min or 15 min) and number of recovery points (up to 24 hours).
- 3Initial replication: choose network or portable media (export/import on a USB disk) for large VMs and slow WAN.
- 4Test failover regularly: right-click the replica VM, Test Failover. Spins up a test VM on an isolated network without taking over the real one.
- 5Document the recovery procedure: on real failure, Planned or Unplanned Failover on the replica, adjust IP for the target location, communicate to users.
When to bring us in
Replica is not a backup: a corrupt file replicates too. Always combine with a real backup strategy (Veeam, Nakivo, Azure Backup) with point-in-time restores.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.