Hi All,
Not sure if this is the correct space for this topic, however i'll give it a go anyway.
We have a 2 Hosts (HP DL385) Windows Server 2012 Failover Cluster.
Storage is provided by a 12 Bay NAS with iSCSI connections (This is catering for CSV's and Quorum)
We are running 2 Virtual domain controllers (2008R2)
The issue we experience is that if the cluster goes down, and when it comes back online the time on the domain controllers (one or the other or both) skews by any where up to 3 days which causes havoc for our office until we can resync clocks with the PDCe.
Time Synchronisation Integration Service is disabled on both Domain Contollers
A few days back we need to reboot the storage on the cluster, and the tasks performed were as follows:
-Power off all virtual machines (Graceful Shutdown)
-Put all CSV's into maintenance mode
-Offline Disk Witness to Quorum
-Rebooted Storage (Waited until it came back online)
-Online Quorum Storage (Successful)
-Bring CSV's out of maintenance mode (Successful & Browsable)
-Power on all Virtual Machines (Successful)
This is where the time Skewed and caused headaches. The time for some reason went to 2 days 11hrs in the past on 1 domain controller.
With this DNS lookups failed to work, Cluster services failed, Cluster Aware Updating Failed, RDP to VM's (and Virtual Hosts) by DNS Name failed (Date time error)
There doesn't seem to be anything in the EventLog except for date/time stamp on events being 2 days in the past.
Now this is why i'm not sure if the issue is cause by fail over clustering, or is an issue with the domain controllers.
Any advice regarding this or if anyone has seen this behaviour before any info would be great
Thanks
Rob