I'm having a problem connecting to Data Recovery appliance from vShpere client with DR plugin.
I do get prompted for vCenter password, then I get the following error message: "Error: The connection was unexpectedly closed"
I have tried every single solution described in http://communities.vmware.com/thread/208385?start=0&tstart=0 with no success. This is my setup and the things that I've tried so far:
-vCenter4 (eval mode) on a Windows 2008 R2 x64 single-homed server (no Linked mode)
-2 x ESX4 clusters Enterprise-Plus licenses
-single Data Recovery 1.1.0.707 appliance
-default self-signed "VMware default certificate" certificate on vCenter
-firewall allows any traffic both ways between VC and DR
-vSphere client and VDR plugin runs from VC machine
-tried both FQDN and IPs when connecting to VC and DR
-administrative account to VC has a password that does not contain non-ASCII characters
-no VM with more than 16 IPs
-tried with enabled/disabled "vCenter requires verified host SSL certificate" option
When running in 'datarecovery -app' with logging set to 7, I see successful communication back and fort between VC and DR and then the last traffic is from DR to port 443 on VC, right before it fails ( see log below). It really makes me think that the problem is with VC server, probably with the fact that VC has default self-signed certificate that DR doesn't trust, but this is just my guess..
This has been a very frustrating experience with DR appliance and I would really like to get some answers from you guys. Any help would be greatly appreciated.
-Peter
-
"datarecovery -app" output:
Connected using API Namespace vim.version.version5.
Authenticating user Administrator
Sending soap request to : login
Received soap response from : login
Sending soap request to : retrieveInternalContent
Received soap response from : retrieveInternalContent
Sending soap request to : retrieveContent
Received soap response from : retrieveContent
Sending soap request to : queryView
Received soap response from : queryView
Sending soap request to : retrieveContent
Received soap response from : retrieveContent
UUID: SMBIOS UUID is reported as '42 15 a2 c6 46 cd 6b 02-b3 64 4b 26 11 7f 93 24'.
Sending soap request to : retrieveContent
Received soap response from : retrieveContent
Sending soap request to : retrieveContent
Received soap response from : retrieveContent
Sending soap request to : queryView
Received soap response from : queryView
Sending soap request to : createFilter
Received soap response from : createFilter
Sending soap request to : checkForUpdates
Received soap response from : checkForUpdates
PropCollIF::UpdateCheck: retry loopcount was: 0
VcbAPI::PropCollWrap::GetOIData: Got an unknown type of data object: vim.dvs.DistributedVirtualPortgroup
VcbAPI::PropCollWrap::GetOIData: processing HostSystem host-553
Sending soap request to : GetContent
Received soap response from : GetContent
Sending soap request to : GetLicenseAssignmentManager
Received soap response from : GetLicenseAssignmentManager
Sending soap request to : isFeatureAvailable
Received soap response from : isFeatureAvailable
VcbAPI::PropCollWrap::GetOIData: processing Folder group-v3
VcbAPI::PropCollWrap::GetOIData: processing VirtualMachine vm-531
The change associated with VM property collector field guest.hostName is NULL
The change associated with VM property collector field snapshot is NULL
VcbAPI::PropCollWrap::GetOIData: processing VirtualMachine vm-560
The change associated with VM property collector field snapshot is NULL
VcbAPI::PropCollWrap::GetOIData: processing Datastore datastore-147
VcbAPI::PropCollWrap::GetOIData: Got an unknown type of data object: vim.dvs.DistributedVirtualPortgroup
VcbAPI::PropCollWrap::GetOIData: processing Datacenter datacenter-7
VcbAPI::PropCollWrap::GetOIData: Got an unknown type of data object: vim.dvs.DistributedVirtualPortgroup
VcbAPI::PropCollWrap::GetOIData: Got an unknown type of data object: vim.dvs.DistributedVirtualPortgroup
Using proxy/session authentication, sessionId=52 05 dc 29 c2 a2 0a 71-c0 cc 4c 94 98 a4 8a f9:10.64.60.146, useSSL=0
-
(btw, it can communicate fine on port 443)