Update Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md

This commit is contained in:
Nicole Rappe
2024-02-05 17:40:11 -07:00
parent 22d8f20512
commit 40f4c5c6a1

View File

@ -7,16 +7,21 @@
### Locate the GuestVM
You need to start by locating the GuestVM in the Production cluster, CLUSTER-01. You will know you found the VM if the "Replication Health" is either `Unhealthy`, `Warning`, or `Critical`.
### Remove Replication from GuestVM
- Within Hyper-V: Failover Cluster Manager
- Within a node of the Hyper-V: Failover Cluster Manager
- Right-Click the GuestVM
- Navigate to "**Replication > Remove Replication**"
- Confirm the removal by clicking the "**Yes**" button `You will know if it worked when the "Replication State" is `Not enabled`
- 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`
## Replication Cluster - CLUSTER-02
### Delete the GuestVM from Replication Cluster
- Within Hyper-V: Failover Cluster Manager
- Right-Click the GuestVM
-
- Within a node of the replication cluster's Hyper-V: Failover Cluster Manager
- Right-Click the same GuestVM and click "Manage..." `This will open Hyper-V Manager`
- Right-Click the GuestVM and click "Settings..."
- Navigate to "**ISCSI Controller**"
- Click on one of the Virtual Disks attached to the replica VM, and note the full folder path for later. e.g. `C:\ClusterStorage\Volume1\HYPER-V REPLICA\VIRTUAL HARD DISKS\020C9A30-EB02-41F3-8D8B-3561C4521182`
!!! warning "GUID Identification"
You need to note the folder location so you have the GUID. Without the GUID, cleaning up the old storage associated with the GuestVM replica files will be much more difficult / time-consuming. Note it down somewhere safe, and reference it later in this guide.
Delete the GuestVM manually from Hyper-V Manager on Host-05, Host-06, Host-07, Host-08)
Delete the GuestVM's replicated VHDX storage from replication storage on C:\ClusterStorage\Volume02