Windows Server / Hyper-V & Failover Clustering
Inspect Hyper-V Replica health before assuming a recovery copy is current
A replica VM can exist while replication is delayed or failed. Inspect the relationship and health for the actual protected VM.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-VMReplication -VMName 'APP01' | Format-List *Read the result
The output exposes configured replication endpoints and status information for the relationship. It must be interpreted with recovery-point age and relevant events.
Resolve and verify
Compare network, authentication and destination storage evidence with the reported error. Repair the specific dependency and verify replication catches up.
Before changing production
Do not fail over or resynchronize without reviewing data-loss exposure, service ownership and the current primary's state.