Challenge
Jobs of any type fail with the error, “Application is shutting down.” For example:Application is shutting down. Failed to download disk. Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}
BackupSynthesizedStorageToTape failed Application is shutting down. Unable to receive file. Application is shutting down.
In Event Viewer on the Veeam Backup & Replication server, a time change of several minutes is recorded in the System log a few minutes before the error occurs:
SEVERITY:Informational
SOURCE:Microsoft-Windows-Kernel-General
EVENT ID:1
DESCRIPTION:System time changed from 2016-03-31T12:06:22.375327200Z to 2016-03-31T12:12:23.623952000Z.
Cause
The Veeam Backup Service uses a system of timed leases as part of monitoring the many processes it manages. Usually this error involves a five minute lease for the VeeamAgent processes (Data Movers). When the Veeam Backup Service is operating normally, this lease is continually renewed. If the lease expires, the associated process is shut down.Typically the lease will expire either because the system time has changed by several minutes, or because a problem communicating with the Veeam Backup Configuration Database has prevented the Veeam Backup Service from renewing the lease.
Solution
On VMware virtual machines, VMware Tools will periodically synchronize the system time with the ESXi host. If the time on the host differs from the NTP server used by Windows, the system time will repeatedly shift between the two different times. The best solution is to synchronize the time on the ESXi host, the Veeam Backup & Replication server and/or the domain controllers to the same source. If this is not possible, you should disable VMware Tools time synchronization for the Veeam Backup & Replication server.As a quick but incomplete workaround, you can run the following from the command line on the Veeam Backup & Replication server:
"c:\Program Files\VMware\VMware Tools\VMwareToolboxcmd.exe" timesync disable
If time synchronization does not appear to be the problem, please contact Veeam Support.