hi guys,
First off, some info:
I'm helping set-up a DR site for a client and they'll be using Hyper-V Replica. The DR servers are up and running in a cluster and all roles have been configured including the Hyper-V Replica Broker (on the DR servers).
However, I ran into a problem bringing the Broker role on the existing production server online (it's on a failed state).
Now I've already searched the web a bit and found solutions similar to my problem:
https://blogs.technet.microsoft.com/askpfeplat/2012/12/09/why-adding-hyper-v-replica-connection-broker-fails-in-failover-cluster-manager/
Unfortunately, the methods described in the article and other webpages I've found (which offers pretty much the same solution) still do not work.
So my next step would be to try and do the steps described in this post:
https://www.experts-exchange.com/questions/28081209/Windows-2012-Hyper-V-Replica-Broker-Fails-to-Start.html
The post describes repairing the cluster but I'm not sure if there is any impact to the production environment as, I believe, the cluster name resource needs to be in a failed state or offline to attempt a repair.
So tl;dr, if I bring the cluster name resource offline, will it affect the virtual machines running on the cluster? Are there any other effects or steps I need to do to make sure that I can successfully bring the resource online again?