<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - VDR: Correct time configuration</title>
    <link>http://communities.vmware.com/community/vmtn/vsphere/datarecovery-vcb?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Thu, 11 Jun 2009 09:06:02 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-06-11T09:06:02Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1280395?tstart=0#1280395</link>
      <description>&lt;br /&gt;
everything is fine now &lt;img src="!" alt="!" class="jive-image"  /&gt;&lt;br /&gt;
&lt;p /&gt;
ntp just need some time to sync...&lt;br /&gt;
&lt;p /&gt;
thanks.</description>
      <pubDate>Thu, 11 Jun 2009 09:06:02 GMT</pubDate>
      <author>kot99</author>
      <guid>http://communities.vmware.com/message/1280395?tstart=0#1280395</guid>
      <dc:date>2009-06-11T09:06:02Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1280413?tstart=0#1280413</link>
      <description>a.p. posted the solution below and this worked fine for me&lt;br /&gt;
&lt;br /&gt;
&lt;u&gt;To get a correct time in the plug-in I need to do the following:&lt;/u&gt;&lt;br /&gt;
1. Set timezone to etc/GMT+1 and check "System clock uses UTC"&lt;br /&gt;
2. Reboot the appliance&lt;br /&gt;
3. Set timezone back to "Europe/Berlin" and uncheck "System clock uses UTC"&lt;br /&gt;
4. Set the correct date and time in the appliance using the date command &lt;br /&gt;
&lt;p /&gt;
e.g. login to the VDR appliciance command line - set the current time and date to June 10th 2009, 11:16pm, type &lt;b&gt;date 100623162009&lt;/b&gt; where 10 is the 10th june, 06 is the month june, 2316 is 11:16pm and 2009 is the year</description>
      <pubDate>Thu, 11 Jun 2009 09:03:18 GMT</pubDate>
      <author>GarethWilson</author>
      <guid>http://communities.vmware.com/message/1280413?tstart=0#1280413</guid>
      <dc:date>2009-06-11T09:03:18Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1280412?tstart=0#1280412</link>
      <description>This is strange, but none of solutions above helped me &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/sad.gif" alt=":(" /&gt;&lt;br /&gt;
&lt;br /&gt;
Plugin reports 5 hours+ discrepancy...any other solutions ???</description>
      <pubDate>Thu, 11 Jun 2009 08:55:30 GMT</pubDate>
      <author>kot99</author>
      <guid>http://communities.vmware.com/message/1280412?tstart=0#1280412</guid>
      <dc:date>2009-06-11T08:55:30Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1275994?tstart=0#1275994</link>
      <description>We had a similar problem and solved it by enabling ntp within the VDR app, it's stopped by default.&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Start ntpd...&lt;br /&gt;
&lt;br /&gt;
/etc/init.d/ntpd start&lt;br /&gt;
&lt;br /&gt;
Set ntpd to run automatically at boot...&lt;br /&gt;
&lt;br /&gt;
chkconfig --level 345 ntpd&lt;br /&gt;
&lt;p /&gt;
You can check that ntp is running correctly by...&lt;br /&gt;
&lt;br /&gt;
ntpq -p&lt;br /&gt;
&lt;br /&gt;
Hope this helps,&lt;br /&gt;
Iain</description>
      <pubDate>Mon, 08 Jun 2009 11:24:12 GMT</pubDate>
      <author>mcwill</author>
      <guid>http://communities.vmware.com/message/1275994?tstart=0#1275994</guid>
      <dc:date>2009-06-08T11:24:12Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1276002?tstart=0#1276002</link>
      <description>Mirko,&lt;br /&gt;
&lt;br /&gt;
thanks for the hint. I am at least able to reproduce the issue.&lt;br /&gt;
&lt;br /&gt;
&lt;u&gt;To get a correct time in the plug-in I need to do the following:&lt;/u&gt;&lt;br /&gt;
1. Set timezone to etc/GMT+1 and check "System clock uses UTC"&lt;br /&gt;
2. Reboot the appliance&lt;br /&gt;
3. Set timezone back to "Europe/Berlin" and uncheck "System clock uses UTC"&lt;br /&gt;
4. Set the correct date and time in the appliance using the date command. &lt;br /&gt;
&lt;br /&gt;
Well, this is a workaround only. It seems there is a little bug somewhere which has to be fixed. &lt;br /&gt;
&lt;p /&gt;
Andr&amp;eacute;</description>
      <pubDate>Mon, 08 Jun 2009 10:53:07 GMT</pubDate>
      <author>a.p.</author>
      <guid>http://communities.vmware.com/message/1276002?tstart=0#1276002</guid>
      <dc:date>2009-06-08T10:53:07Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1274701?tstart=0#1274701</link>
      <description>&lt;br /&gt;
Had the same issue. I resolved it on my mschine by doing the following on the vdr macine:&lt;br /&gt;
&lt;p /&gt;
1. Check "System clock uses UTC"&lt;br /&gt;
&lt;p /&gt;
2. Choose one of the etc/GMT (e.g. gmt+1 for germany) entrys instead of the country/city entrys.&lt;br /&gt;
&lt;p /&gt;
3. Reboot the vm&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 05 Jun 2009 20:54:52 GMT</pubDate>
      <author>Mirko Huth</author>
      <guid>http://communities.vmware.com/message/1274701?tstart=0#1274701</guid>
      <dc:date>2009-06-05T20:54:52Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1273407?tstart=0#1273407</link>
      <description>&lt;br /&gt;
Setting "Synchronize guest time with host" on the VDR appliance does not help in my case&lt;br /&gt;
&lt;p /&gt;
From the commandline, the VDR appliance already reports correct timezone and clock &lt;br /&gt;
&lt;p /&gt;
The plugin still reports 5 hours+ discrepancy</description>
      <pubDate>Thu, 04 Jun 2009 23:20:41 GMT</pubDate>
      <author>pharmer</author>
      <guid>http://communities.vmware.com/message/1273407?tstart=0#1273407</guid>
      <dc:date>2009-06-04T23:20:41Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1272540?tstart=0#1272540</link>
      <description>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</description>
      <pubDate>Thu, 04 Jun 2009 14:10:02 GMT</pubDate>
      <author>GarethWilson</author>
      <guid>http://communities.vmware.com/message/1272540?tstart=0#1272540</guid>
      <dc:date>2009-06-04T14:10:02Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1272315?tstart=0#1272315</link>
      <description>&lt;br /&gt;
On which machine - the VDR appliance? - I tried that, that didnt help me.</description>
      <pubDate>Thu, 04 Jun 2009 10:29:00 GMT</pubDate>
      <author>cm-vc</author>
      <guid>http://communities.vmware.com/message/1272315?tstart=0#1272315</guid>
      <dc:date>2009-06-04T10:29:00Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1272235?tstart=0#1272235</link>
      <description>&lt;br /&gt;
Shutdown vm, then change settings to enable "Synchronize guest time with host" under VMware Tools options.&lt;br /&gt;
&lt;p /&gt;
No more time warning for me &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/cool.gif" alt="B-)" /&gt;  &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Thu, 04 Jun 2009 08:48:28 GMT</pubDate>
      <author>5ynack</author>
      <guid>http://communities.vmware.com/message/1272235?tstart=0#1272235</guid>
      <dc:date>2009-06-04T08:48:28Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1272180?tstart=0#1272180</link>
      <description>&lt;br /&gt;
Same here, just started the appliance, real time is 9:19 AM, Appliance time is 1:19 PM, 4 hours difference.&lt;br /&gt;
&lt;p /&gt;
Located in the netherlands, GMT02:00&lt;br /&gt;
&lt;p /&gt;
Regards,&lt;br /&gt;
&lt;br /&gt;
Roelof</description>
      <pubDate>Thu, 04 Jun 2009 07:34:00 GMT</pubDate>
      <author>Roelofz</author>
      <guid>http://communities.vmware.com/message/1272180?tstart=0#1272180</guid>
      <dc:date>2009-06-04T07:34:00Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1272101?tstart=0#1272101</link>
      <description>We have the exact same problem with the New Zealand timezone. &lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
I have tried different client platforms, re-import of the VDR appliance, new VC server etc - all with same result &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Just my 2c</description>
      <pubDate>Thu, 04 Jun 2009 06:14:34 GMT</pubDate>
      <author>pharmer</author>
      <guid>http://communities.vmware.com/message/1272101?tstart=0#1272101</guid>
      <dc:date>2009-06-04T06:14:34Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1272068?tstart=0#1272068</link>
      <description>I have the same problem. Im located in Denmark.</description>
      <pubDate>Thu, 04 Jun 2009 05:44:41 GMT</pubDate>
      <author>cm-vc</author>
      <guid>http://communities.vmware.com/message/1272068?tstart=0#1272068</guid>
      <dc:date>2009-06-04T05:44:41Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>VDR: Correct time configuration</title>
      <link>http://communities.vmware.com/message/1270745?tstart=0#1270745</link>
      <description>&lt;br /&gt;
Located in Germany, I installed a vSphere environment (all GA versions) with the appropriate time config.&lt;br /&gt;
Hosts, Virtual Center and the Data Recovery VM are set to Europe/Berlin (GMT +2:00). &lt;br /&gt;
&lt;p /&gt;
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!?&lt;br /&gt;
Backup runs ok, however the logs have the wrong time stamp. &lt;br /&gt;
&lt;p /&gt;
Is there anything I missed in the configuration or is this just a bug? &lt;br /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
Andr&amp;eacute;</description>
      <pubDate>Wed, 03 Jun 2009 10:48:36 GMT</pubDate>
      <author>a.p.</author>
      <guid>http://communities.vmware.com/message/1270745?tstart=0#1270745</guid>
      <dc:date>2009-06-03T10:48:36Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>13</clearspace:replyCount>
    </item>
  </channel>
</rss>

