From 6f1ca342b01b4ca3d20f8887c65a831d0ec97692 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 5 Feb 2024 17:52:27 -0700 Subject: [PATCH] Update Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md --- .../Failover Cluster/Rebuild Failover Cluster Replication.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md index 22a6ffc..f909ce3 100644 --- a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md +++ b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md @@ -31,7 +31,9 @@ Now that you have noted the GUID of the storage folder of the GuestVM, we can sa - Navigate to "**Replication > Remove Replication**" - Confirm the removal by clicking the "**Yes**" button. You will know if it removed replication when the "Replication State" of the GuestVM is `Not enabled` - Right-Click the GuestVM (again) `You will see that "Enable Replication" is an option now, indicating it was successfully removed.` - - Wait for any Checkpoint Merges to finish `The G + +!!! note "Replica Checkpoint Merges" + When you removed replication, there may have been replication checkpoints that automatically try to merge together with a `Merge in Progress` status. Just let it finish before moving forward. ### Delete the GuestVM manually from Hyper-V Manager on all replication cluster hosts PLACEHOLDER