Hi
Build 11.0.1.1261 - when doing an adhoc Migration of a vSphere 7 Windows VM running Windows 2019 core, the clock goes forward ONE HOUR. If this happens to be an AD DC then all kinds of horrible problems start with replication between the DCs. All I'm doing is a storage move on an independent ESXi 7.0 host (no vCenter), so the Windows VM moves its storage from one FMS6 datastore to a different one on a different NAS device.
Anyone else seeing this? Is this related to the two weeks when the Us and the EU are out of step? Quite annoying .
As soon a vsphere snapshot is happening on a vm, the vm take over the time of the esxi host.
That‘s expected behaviour and nothing veeam can change. You must make sure, that the esxi time has the correct time the vm needs to have.
.