Comprehensive data protection for all workloads
Post Reply
DCourtel
Novice
Posts: 3
Liked: 1 time
Joined: Nov 09, 2012 9:38 am
Contact:

DC gets 2 hours ahead during snapshot

Post by DCourtel »

Hi all, we have add memory to our ESX, we see that our Domain Controler get 2 hours ahead when the snapshtop start.

- At 00h30 the policy on VeeamBackup start, it backup some servers.
- At 02h00 it is the turn of our DC to be saved. Snapshot services start (VeeamVssSupport, Microsoft Software Shadow Copy Provider)
- The serveur clock display 2 hours ahead
- The backup finish some minutes after
- Snapshot services stop
- The clock on the server is ok.

Can someone help us ?

Thanks.
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: DC gets 2 hours ahead during snapshot

Post by Vitaliy S. »

Could you please tell me what happens if you snapshot this VM manually using vSphere Client? Also do you see the same behavior if you trigger a VSS snapshot inside the guest OS (DC VM)?
DCourtel
Novice
Posts: 3
Liked: 1 time
Joined: Nov 09, 2012 9:38 am
Contact:

Re: DC gets 2 hours ahead during snapshot

Post by DCourtel »

Hi Vitaliy, thanks for your quick answer.
Good question. I've test, and effectively the server get 2 hours ahead when making a snapshot. when the snapshot is in place the clock go back. And when I remove the snapshot the clock go 2 hours ahead again and back to normal once the snapshot is removed.
I also try on server that is not a DC. Same issue.
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: DC gets 2 hours ahead during snapshot

Post by Vitaliy S. »

That's exactly what I've thought. Check the time settings on your ESX(i) server and consider using NTP. I bet that the reported time on your hosts will also be 2 hours ahead.
DCourtel
Novice
Posts: 3
Liked: 1 time
Joined: Nov 09, 2012 9:38 am
Contact:

Re: DC gets 2 hours ahead during snapshot

Post by DCourtel » 1 person likes this post

Many thanks for your help Vitaliy. We have solved our issue by reconfiguring time settings on our ESX.
Post Reply

Who is online

Users browsing this forum: Google [Bot], Semrush [Bot], smace and 209 guests