Hi Everyone,
after a successful replica failover from Node A to Node B, I tried to enable the reverse replica on Hyper-V and just got an error that the VM is not in a state to start the replication.
Now Node A is still listed as primary server for the replication, Node B as replica server (I guess that is because the replication has not been reversed). However, on Node A replication looks like it's not configured.
Node B gives me the following options:
- Reverse Replication (not working)
- Remove Recovery Points (won't help I guess)
- Cancel Failover
- Remove Replication
As still node A is shown as primary server, I'm a little bit worried what will happen if I select one of the last two options. Will it remove the VM (as it is running right now on node B, but as replica?).
Did anyone see this behaviour before?
Thanks,
Jens
jensit.wordpress.com