No matter what best practice guide you check, there will be a important recommendation to make sure the time synchronisation of your VMware vCenter and the VMware ESXi are configured and working correctly. If you ignore that and your VMware ESXi timedrift starts, it can become a very nasty situation.

Using our latest version of Performance Analyzer, we have a dashboard and alerts that help you to control your vCenter and ESXi timedrift to take counteractions.

The dashboard mentioned is called VMware Config: Clocks and Timedrift and does exactly that – showing all of your ESXi hosts and you vCenter time and timedrift. That timedrift is compared to the Performance Analyzer appliance and also your VMware vCSA.

Performance Analyzer VMware ESXi timedrift

Disadvantages having timedrift

You might think, having a couple of seconds timedrift can’t be such a big issue. Actually, it does. It affects backup, redo logs, active directory synchronisation, Kerberos authentification, cookie duration and all kinds of database actions or query results. Therefore, you should always make sure to have the correct time set as precise as possible.

The higher the VMware ESXi timedrift compared to the time of the other peers the worse are the effects. We learned about situations where AD users couldn’t logon anymore or AD computer dropped out of the active directory, because the timedrift was more than 5 minutes, so Kerberos went crazy.

We also noticed that when customers complained to not see the dashboards being populated with data. Or having a gap in the charts of several hours. In any of these cases, the VMware ESXi timedrift was way off on the host the Performance Analyzer virtual machine was running on. Once the ESXi time was corrected, all went well. As we encountered these situations pretty frequently we decided to check against any time source we can find in the customers environment and try to triangulate what time is best.

Make sure to have correct time

There are plenty of ways how to make sure the time is always correct, just make sure to  chose and stick to your choice and don’t mix it.

VMware vCSA

You can configure the time synchronization on your VMware vCSA pretty straightforward by login into the admin page: https://vcsa:5480, select time and edit the time synchronisation.

vcenter vcsa ntp

Best is to use three NTP Server for the synchronisation (ignore our demo screenshot setting :-)).


The ESXi hosts should also synch the time with three NTP server and you can either use host profiles, powercli scripts or manually configure that.

VMware ESXi time synchronisation

Make sure that the service is started and the time is correct. If the timedrift is already to high, you might need to manually set the time first before the synchronisation picks up.

VMware Tools

In many if not most cases the time synchronisation of the virtual machines (VMware tools) is active and syncs with the time of the ESXi host. More precise – the VM syncs with the time of the ESXi host its running on. 

Think of a cluster of 10 ESXi hosts and 9 have the correct time, but one has the wrong time (let’s say 30 minutes). Your virtual machine runs fine on all 9 ESXi hosts, but the moment DRS or manual vMotion moves the VM to the ESXi host with high timedrift, your VM is happily taking that time.

Of course that doesn’t happen if you have NTP or AD timesync in your virtual machine configured and don’t use the VMware tools time synchronisation feature.

Therefore, make sure to either use NTP/AD timesync or VMware tools timesync and have all ESXi hosts sync the time with a NTP servers.

There are a couple of KB articles you should read if you’re not certain on the configuration:

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.