Hi
We are using Server 2012 (not R2), we have a 4 node Hyper-V Cluster and a 2 node SOFS with about 70 VMs. We have been using this setup for about 15 months successfully.
We have also been using Hyper-V Replica successfully for this amount of time for 2 SQL servers and various other servers such as Terminal Servers and File Servers.
We have rebuilt one of our SQL Servers and have setup replication again for it however as soon as Initial Replication has completed the VM goes into "Resynchronisation Required" state. If I then Resume Replication the result is the same - Initial Replication works but as soon as that is done we go back to "Resynchronisation Required".
We are replicating over a dedicated 100MB/s lease line and the remote storage has 4 X 15K drives in a RAID10 and is used for nothing but this SQL Server. The combined size of the Primary VMs OS, DB & Logs VHDX drives is approx. 500GB.
I have run the replication overnight when no one is using the systems and backups have completed. I have also tried to do the Initial Replication via external media but before I have even imported the Primary VM into the Replica server we go into "Resynchronisation Required".
Historically speaking this SQL Server has replicated without issue. We are using the EnableWriteOrderPreservationAcrossDisks cmdlet to keep each disk in sync.
Does anyone know what would cause a VM to go into this state so quickly after Initial Replication?
Many thanks