From ce914234e80bcba7c0d3a8c989fabdecf456d068 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 5 Feb 2024 18:05:05 -0700 Subject: [PATCH] Update Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md --- .../Rebuild Failover Cluster Replication.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) 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 6ca91ef..048333f 100644 --- a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md +++ b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md @@ -46,11 +46,15 @@ At this point in time, we need to remove the GuestVM from all of the servers in - 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**" +- Remove GuestVM from the node it appears on + - On one of the replication cluster nodes, we will 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 +Now we need to clean up the storage left behind by the replication cluster. + +- Within a node of the replication cluster + - Navigate to `C:\ClusterStorage\Volume1\HYPER-V REPLICA\VIRTUAL HARD DISKS` + - Delete the entire GUID folder noted in the previous steps. `e.g. 020C9A30-EB02-41F3-8D8B-3561C4521182` ## Production Cluster - CLUSTER-01 ### Enable Replication on GuestVM in Cluster-01 (Production Cluster)