Discussions specific to the VMware vSphere hypervisor
- Posts: 46
- Liked: never
- Joined: Oct 28, 2015 9:36 pm
- Full Name: Joe Brancaleone
I'm new to this scenario that was just deployed. What are the known issues/limitations to doing this? So far I see the re-IP upon failover doesn't work, which makes sense since the offline VM can't have any data changes to the OS disk presumably. We also came across WIndows DC replicas coming online with incorrect Windows time (exactly 8 hours ahead of PST instead of what it says its set to, PST), which it appears to be getting from the CMOS clock (failover in a bubble with no access to NTP server). However a Veeam replication/failover should not have any effect on the CMOS clock correct?
- Product Manager
- Posts: 13776
- Liked: 2684 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
the limitations are listed in the user guide
While I personally would avoid replicating domain controllers (I so old enough to remember USN rollbacks), I cannot remember anything around wrong clock. Do you have a Veeam support case number for that observation?
- VP, Product Management
- Posts: 6508
- Liked: 1357 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
We do not take care about any clock related things. The operating system will start and get from whatever is configured the time. First this will be from the hardware at boot. Which in this case is emulated by the virtualization host. I would check the time settings there. If the OS is started then this time might change based on NTP or other time settings within Windows. So it is mor of a question for the Windows Admin.
If disk is encrypted, we can not set the reIP settings as we do not have access to the registry.
Users browsing this forum: Google [Bot] and 26 guests