I have a Windows 2008 R2 VM running MS SQL which I set up for VR replication 10 days ago. The initial sync took almost 5 days, but that seems typical for a VM of its size in our environment. The problem is that as of this morning the first delta sync had not completed 5 days after the initial sync finished.
Interestingly, I just checked vCenter Events for this particular VM and something has changed within the past 2 hours:
- At 9:33 (Eastern Time) it reported an RPO violation of 8524 minutes. That is just about 6 full days, yet the initial sync had finished 5 days + 2 hours earlier. This doesn't seem to make sense.
- At 9:46 it reported "Delta completed". "Yay", I thought, but....
- 5 seconds later it reported an RPO violation of 7318 minutes. On one hand this doesn't seem to make sense, on the other it looks like a correction because now it's about the correct number of minutes since the initial sync finished.
- Looking at the VR Monitor, it shows a status of OK with an RPO Violation and the Sync Point of 5+ days ago, the time that the initial sync finished.
I successfully replicated and tested a failover of a similar SQL VM a couple of weeks ago. The one difference that I can think of is that one of the VMDKs for this problem VM had a duplicate name, thus had to go on a different data store from the other VMDKs on the target host. However, I have done the same for other replicated VMs and have not had a problem.
If anyone can tell me whether this is a known issue, what else to look for or suggestions for a fix, it would be greatly appreciated. I can give more information regarding versions, etc. as needed.
Thanks.
