From a3508744130567fb219c93682d446379ff3c88ff Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 5 Feb 2024 17:54:38 -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, 4 insertions(+) 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 f909ce3..73597bd 100644 --- a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md +++ b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md @@ -35,6 +35,10 @@ Now that you have noted the GUID of the storage folder of the GuestVM, we can sa !!! 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. +- Within the same node of the replication cluster's Hyper-V: Failover Cluster Manager `Switch back from Hyper-V Manager` + - Right-Click the GuestVM and click "**Remove**" + - Confirm the action by clicking the "**Yes**" button + ### Delete the GuestVM manually from Hyper-V Manager on all replication cluster hosts PLACEHOLDER