Greetings everyone.
Yesterday we had a time problem over one of our production servers, 2008R2, I had not too much to investigate why it was caused, cause it was urgent to solve it, but maybe anyone here could lend me a hand in figuring why it was caused and avoid it happening again.
Any further investigation overt this problematic machine won't be possible, it was a virtual one which, for other reason, needed to be deleted, the physical is working again.
I'll try to explain the problem:
Yesterday, at 4PM, the machine suddenly changed his hour to 1AM of today (+9 hours), event viewer just showed and information message like "System time and date has been changed" by system service.This server was w32tm synced to es.pool.ntp.org, forzing the resync just let the correct time for about 20 secs, then it would go wrong again.
Forzing it with cmd time date, or control panel, same result.
So I checked hyper-V time sync from his physical machine, which we manually deactivated when we NTPed it, somehow it was activated, as soon as I deactivated it, time was again synced correctly with NTP.The time in the physical machine was correct all the time.
So the questions I would like to get solved would be:
-Why would hyper-v time sync mess up the virtual machines, even if hyper-V host time is correct? is there any way to fix this if its a known bug?
-Why would hyper-V time sync reactivate itself alone? any way to ensure this won't happen again?
All our enviroment is running under Hyper-V, if this has happened in this machine I would need a way to diagnose/fix it so it won't happen in anymore, sorry for not being able to give you more data about the problem we have, but I could add anything you need if its not "problematic machine related".
Regards.
Carlos.