From b8fa8377122cfab20cb7f95b4d58843e19623b27 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 5 Feb 2024 18:01:16 -0700 Subject: [PATCH] Update Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md --- .../Rebuild Failover Cluster Replication.md | 9 ++++++++- 1 file changed, 8 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 73597bd..6ca91ef 100644 --- a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md +++ b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md @@ -40,7 +40,14 @@ Now that you have noted the GUID of the storage folder of the GuestVM, we can sa - Confirm the action by clicking the "**Yes**" button ### Delete the GuestVM manually from Hyper-V Manager on all replication cluster hosts -PLACEHOLDER +At this point in time, we need to remove the GuestVM from all of the servers in the cluster. Just because we removed it from the Hyper-V: Failover Cluster did not remove it from the cluster's nodes. We can automate part of this work by opening Hyper-V Manager on the same Failover Node we have been working on thus far, and from there we can connect the rest of the replication nodes to the manager to have one place to connect to all of the nodes, avoiding hopping between servers. + +- Open Hyper-V Manager + - Right-Click "Hyper-V Manager" on the left-hand navigation menu + - Click "Connect to Server..." + - Type the names of every node in the replication cluster to connect to each of them, repeating the two steps above for every node +- Remove GuestVM from Every Node + - On every replication cluster node where we can see the GuestVM listed, we are going to Right-Click the GuestVM and select "**Delete**" ### Delete the GuestVM's replicated VHDX storage from replication ClusterStorage PLACEHOLDER