I hope you guys can help us.
At the moment we use the latest VDR release 220.127.116.111 and vSphere Client 4.0.0 with VDR plugin 18.104.22.168 which is enabled.
Yesterday we had no problems to connect to our VDR.
But today we were not able to connect.
We get no error or something that can help me to find the problem.
The vSphere client tries to connect for some seconds while the status is: Attempting to connect..
Then the status switch back to "Not connected" and how i already said, no errors.
I already tried to solve to problem with a reboot of the VDR, but still the same.
Then I had a look onto the console, but the same here, no errors.
From our vCenter Server I can ping the VDR and I can login into the webinterface.
At the moment i have no idea what could be the problem
How do you connect to the vDR appliance using the IP address or hostname ?
Have you tried connecting to the VDR appliance from the ESX host i.e. direct connect to the ESX host using vSphere client and then try to connect to vDR appliance ?
We have a KB http://kb.vmware.com/kb/1018216 which would help you troubleshoot/isolate the issue.
All the best !!!
Normaly we connect via virtual machine name (not the real Hostname of the appliance).
The vSphere client normally obtain the appliances and offer them in the dropdown menue to connect.
This had worked for us till today.
To determine that we have no DNS/network problems I switched the VDR from DHCP over to a static IP. I also reconfigured everything in our DNS.
I can ping from our vCenter server our VDR via IP & name ( == virtual machine name)
I also can ping from our VDR our vCenter server by name & IP.
So there should be no network/dns problems.
One of the first things I tried was to connect over IP, but the clients shows exactly the same behavior.
Normale we use our vSphere client to connect to the vCenter Server.
I tried your tip and connected directly to the ESX host and tried to connect the VDR. What should I say? Same behavior here!
We still have an older VDR installed and we still can connect to this one without any problems. So I'm sure there's something wrong with our latest (and productive) VDR.
I also tried step 5 from KB1018216 (datarevovery.ini with higher timeout settings), but still no changes/effects.
After I switched to a static IP and reconfigured dns i wasn't able to login to the webinterface (yes i used the right IP ), so I rebooted the VDR again. And now???
It works! :smileycool:
Well I am glad that the issue is now fixed !!!
I have the same problem for the first time connection to VDR, but I am using VDR version 1.2 the latest one and I am running vCenter 4.1 on Win 2008 R2 and I tried to connect to VDR from the vCenter Machine and from XP 32-bit Machine with no luck
can you give us some details what you have tried to resolve the issue?
Are your sure that your dns resolution/network is ok?
Did you setup a static ip for your vdr?
Do you get some errors or can you see something in VDR's console?
That you can access a VDR to manage your backups, you can try to download again the latest VDR and install a second one.