Hello, I would like to have your opinion and if yes or no it is a normal behaviour.
I am experiencing an issue regarding the behaviour of my replication architechture from clustered servers to standalone replica server.
I am running highly available VM on a WS2012 Hyper-V Cluster (2 Hyper-V nodes). The storage (Netapp FAS2240) is attached via iSCSI. CSV is enabled. Hyper-v Broker OK …
Everything works so far regarding the cluster itself and replication. My VM are replicated on a third WS2012 Hyper-V Server outside the cluster (same domain). Replication is OK, failover test OK, planned Failover OK, reverse replication OK !
The problem is when I am simulating a power outage on one of the cluster nodes, (everything operates as expected), the VM are rebooted on the surviving node but the status of the replication goes to “Critical” full resynchronization is needed then (error Hyper-v-vmms Id 32544 : virtual disk modified by compaction, expansion or offline) ?!
In brief, the replication is OK when the two nodes are online : I can live migrate the VM (replication stays OK), move the broker from one node to the other (replication stays OK), move the CSV from one owner to the other (replication stays OK). But as soon as one of the two nodes is offline, the replication is broken and need a full resync : ID 32544, 32326, 32026 !
Is this behaviour normal when replicating from a cluster or should the replication continues normally despite the node failover ? I guess something is wrong there.
BRGDS
Ludo