VMware Cloud Community
a_p_
Leadership
Leadership
Jump to solution

VDR: Correct time configuration

Located in Germany, I installed a vSphere environment (all GA versions) with the appropriate time config.

Hosts, Virtual Center and the Data Recovery VM are set to Europe/Berlin (GMT +2:00).

After connecting to the appliance in vCenter, it shows a 4 hour difference in the time configuration tab. E.g. at Noon it says 4PM and displays a warning about more than 5 minutes difference between the vShpere-Client and the Recovery appliance!?

Backup runs ok, however the logs have the wrong time stamp.

Is there anything I missed in the configuration or is this just a bug?

Thanks

André

Reply
0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

Mirko,

thanks for the hint. I am at least able to reproduce the issue.

To get a correct time in the plug-in I need to do the following:

1. Set timezone to etc/GMT+1 and check "System clock uses UTC"

2. Reboot the appliance

3. Set timezone back to "Europe/Berlin" and uncheck "System clock uses UTC"

4. Set the correct date and time in the appliance using the date command.

Well, this is a workaround only. It seems there is a little bug somewhere which has to be fixed.

André

View solution in original post

Reply
0 Kudos
13 Replies
Krede
Enthusiast
Enthusiast
Jump to solution

I have the same problem. Im located in Denmark.

Reply
0 Kudos
pharmer
Enthusiast
Enthusiast
Jump to solution

We have the exact same problem with the New Zealand timezone.

Our VC4 server, ESX hosts, SQL database, Active directory controllers and vSphere client as well as the VDR appliance all have correct time and regional settings

The VDR plugin however continues to report a major discrepancy (5 hours 47 minutes out) even though the VDR plugin says it is in the right timezone

I have tried different client platforms, re-import of the VDR appliance, new VC server etc - all with same result

Add this to the already reported logon problems to the VDR appliance and strange snapshot failures (even though manual snapshots work) - means VDR cannot be considered even for small production backup

Just my 2c

Reply
0 Kudos
Roelofz
Contributor
Contributor
Jump to solution

Same here, just started the appliance, real time is 9:19 AM, Appliance time is 1:19 PM, 4 hours difference.

Located in the netherlands, GMT02:00

Regards,

Roelof

Regards, Roelof
Reply
0 Kudos
5ynack
Contributor
Contributor
Jump to solution

Shutdown vm, then change settings to enable "Synchronize guest time with host" under VMware Tools options.

No more time warning for me :smileycool:

Reply
0 Kudos
Krede
Enthusiast
Enthusiast
Jump to solution

On which machine - the VDR appliance? - I tried that, that didnt help me.

Reply
0 Kudos
GarethWilson
Contributor
Contributor
Jump to solution

i have the same problem (GMT) if i look on the vdr console and type "date" it reports the correct time yet the VDR secrtion of VC says a completely different time

Reply
0 Kudos
pharmer
Enthusiast
Enthusiast
Jump to solution

Setting "Synchronize guest time with host" on the VDR appliance does not help in my case

From the commandline, the VDR appliance already reports correct timezone and clock

The plugin still reports 5 hours+ discrepancy

Reply
0 Kudos
Mirko_Huth
Enthusiast
Enthusiast
Jump to solution

Had the same issue. I resolved it on my mschine by doing the following on the vdr macine:

1. Check "System clock uses UTC"

2. Choose one of the etc/GMT (e.g. gmt+1 for germany) entrys instead of the country/city entrys.

3. Reboot the vm

a_p_
Leadership
Leadership
Jump to solution

Mirko,

thanks for the hint. I am at least able to reproduce the issue.

To get a correct time in the plug-in I need to do the following:

1. Set timezone to etc/GMT+1 and check "System clock uses UTC"

2. Reboot the appliance

3. Set timezone back to "Europe/Berlin" and uncheck "System clock uses UTC"

4. Set the correct date and time in the appliance using the date command.

Well, this is a workaround only. It seems there is a little bug somewhere which has to be fixed.

André

Reply
0 Kudos
mcwill
Expert
Expert
Jump to solution

We had a similar problem and solved it by enabling ntp within the VDR app, it's stopped by default.

If you check you will find that /etc/ntp.conf is already setup to use the centos.pool.ntp.org hosts, you can leave this as is but I changed ours to 0-2.uk.pool.ntp.org

Start ntpd...

/etc/init.d/ntpd start

Set ntpd to run automatically at boot...

chkconfig --level 345 ntpd

You can check that ntp is running correctly by...

ntpq -p

Hope this helps,

Iain

Reply
0 Kudos
kot99
Contributor
Contributor
Jump to solution

This is strange, but none of solutions above helped me Smiley Sad

Plugin reports 5 hours+ discrepancy...any other solutions ???

Reply
0 Kudos
GarethWilson
Contributor
Contributor
Jump to solution

a.p. posted the solution below and this worked fine for me

To get a correct time in the plug-in I need to do the following:

1. Set timezone to etc/GMT+1 and check "System clock uses UTC"

2. Reboot the appliance

3. Set timezone back to "Europe/Berlin" and uncheck "System clock uses UTC"

4. Set the correct date and time in the appliance using the date command

e.g. login to the VDR appliciance command line - set the current time and date to June 10th 2009, 11:16pm, type date 100623162009 where 10 is the 10th june, 06 is the month june, 2316 is 11:16pm and 2009 is the year

Reply
0 Kudos
kot99
Contributor
Contributor
Jump to solution

everything is fine now !!!

ntp just need some time to sync...

thanks.

Reply
0 Kudos