As per: http://support.microsoft.com/kb/939322
Did you know that Microsoft states:"We do not guarantee and we do not support the accuracy of the W32Time service between nodes on a network. The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs. The W32Time service is primarily designed to do the following:"
So basically, Cyara components can all be running up to 2 seconds off of the clock reference time when using standard NTP, which you can imagine can caus problems in fault resolution (different server logs, different times), as well as causing some faults in itself (scheduler/CE/portal timing mismatches)
To rectify this, we rolled out a product called Domain Time 2, purchasing enough licenses for all PoP servers (VMs included), as well as all Dev/Devops servers in Melbourne.
Netops has rolled out this product, and after a trial period, followed by a small rollout in US, we've successfully deployed this to all major PoPs (US WC&EC, UK, and AU).
All time on Cyara servers are now managed from one server per location, and all remain with 5ms of the reference clock.
As per attached image, this shows a VM time drift over the last few days, keeping very close to the reference clock.
So far this product has proved highly useful in the Cyara cloud environment, so something to keep in mind for deployments, etc.
Further information can be found here:
https://www.greyware.com/software/domaintime/v5/overview/index.asp
Comments
1 comment
Muhammad Faisal Can you please review this article?
Please sign in to leave a comment.