Time shift on backed up server when snapshot is taken

KB ID:
1202
Product:
Veeam Backup & Replication
Version:
4.x, 5.x
Published:
Last Modified:
2013-04-29

Challenge

There is a time shift on the guest VM during the Veeam job when the snapshot is taken. You are getting messages such as the following in the system event log:

Event ID: 1 The system time has changed to <date:time> from <date:time>.

Cause

By default, VMware Tools synchronizes the virtual machine's time after a few specific events that are likely to leave the time incorrect.

Solution

To address, disable (uncheck) the "Time synchronization between the virtual machine and the ESX server." option in the VMTools settings.

User-added image

If this is not enough, you can also disable time synchronization as described in this VmWare KB: http://kb.vmware.com/kb/1189. This Knowledge Base solution suggests the following steps.

  • Open the virtual machine's configuration file (.vmx ) in a text editor and set these options to zero. If the entries do not exist, add them.

    Note: 0 = disabled, 1 = enabled.

    tools.syncTime = "0"
    time.synchronize.continue = "0"
    time.synchronize.restore = "0"
    time.synchronize.resume.disk = "0"
    time.synchronize.shrink = "0"
    time.synchronize.tools.startup = "0" 
    time.synchronize.resume.host = "0"
  • Select the virtual machine in the VMware Infrastructure Client inventory. On the Summary tab, click Edit Settings, then click the Options tab and select General (under Advanced). Click Configuration Parameters, then click Add Row and add this information:
tools.syncTime = "0"
time.synchronize.continue = "0"
time.synchronize.restore = "0"
time.synchronize.resume.disk = "0"
time.synchronize.shrink = "0"
time.synchronize.tools.startup = "0"
time.synchronize.resume.host = "0"

Rate the quality of this KB article: 
4.2 out of 5 based on 27 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit