unable to connect to VC from VMwareDataRecovery-1.2.1

[karnash]

Hi,

I have Vcenter 4.1 update 1. I have Vsphere enterprise plus license. I want to install vmware data recovery appliance.

I have downloaded VMwareDataRecovery-1.2.1.1616-369570-i386.iso and then have extracted the iso.

Then I clicked on deploy an ovf > selected the ovf file and appliance gets installed. I installed the plug-in on the VC server.

I can see the application under solutions and applications.

When I try to connect to it, I have credentials of VC server. Administrator and when I enter the password, I can't seem to connect to the appliance.

I can connect via console ...root but can't connect under solutions and applications to the appliance.

So it seems like I can't seem to connect to virtual center from datarecovery.

I can ping the appliance from VC server as I have given it a 192.168.x.x IP address

Can someone advise what am I doing wrong. thanks

[idle-jam]

sometimes a few reboot solve the problem. perhaps you can try?

[karnash]

I have tried many reboots...both of the applicane and the VC server....nothing works...

I can't seem to connect to the VC from the appliance    

[nebben]

Make sure that whatever user you are using to connect, Administrator@VC-HOST in your case, has permissions within your VMware environment itself that cover all hosts/VMs you wish to protect. Also, make sure that whichever client you are using to administer your VDR stuff has firewall ports open on 80, 443, and 22024 between itself and your VCenter server. Your VDR appliances should be able to talk to your ESX hosts on port 902 as well. Using a VMWare Infrastructure Client on your VCenter server makes most of the firewall stuff moot. These things are all in the VDR docs on page 15 (http://www.vmware.com/pdf/vdr_12_admin.pdf).

When you start up the VMs, then start managing them through your VIClient using the VDR plugin, when connecting to the appliance use the same credentials that you've granted access to within your VMWare environment.

[tfindlay]

Did you ever resolve this ?

I've got the same thing, I droped my old VDR 1.2.0 as I rebuilt my vCenter Server machine.

So I followed the instructions, deployed VDR1.2.1.1616 via the OVF template, installed the plugin on my vCenter Server+Client box.

I then login with my user account (domain admin) and go to connect to the VDR guest, I cant change the username, and it wont accept my password.

I can access the console of the machine, login as root etc. but cant login via the web admin page or from vCenter Server.

The only thing I can think of is my VDR guest machine is in a different subnet and has no access to my Active Directory server where the vCenter server box is multi-homed (has 2 IP's, one in each subnet). But is seems crazy for the VDR guest to auth off that host. What if my AD box goes down and I need to recover it ?!?

[tfindlay]

By way of an update, my connection log looks like:

05/16/2011 03:14:39 PM > GetIPv4Address: adressess[0] == 192.168.60.102
05/16/2011 03:14:39 PM > Connecting: Attempting to open the connection...
05/16/2011 03:14:39 PM > DAGclient.Connect (addr): connect started (addr: "192.168.60.202", port: 22024)
05/16/2011 03:14:39 PM > WinRequestor.WinRequestor: Creating client requestor
05/16/2011 03:14:39 PM > WinTCPconnection.Connect: address value before Dns.GetHostAddresses() "192.168.60.202"
05/16/2011 03:14:39 PM > WinTCPconnection.Connect: IPAddress[] length 1
05/16/2011 03:14:39 PM > WinTCPconnection.Connect: IPAddress[0] == 192.168.60.202
05/16/2011 03:14:39 PM > WinTCPconnection.Connect: IPAddress[] endpoint created; address: "192.168.60.202", port: 22024
05/16/2011 03:14:39 PM > WinTCPconnection.Connect: valid connect() for new socket 3772 (addr: "192.168.60.202", port: 22024)
05/16/2011 03:14:39 PM > WinRequestor.Handshake: writing handshake
05/16/2011 03:14:39 PM > WinRequestor.Handshake: writing handshake done
05/16/2011 03:14:39 PM > WinRequestor.Handshake: reading handshake
05/16/2011 03:14:39 PM > WinRequestor.Handshake: reading handshake done
05/16/2011 03:14:39 PM > DAGclient.Connect (chan): connection valid
05/16/2011 03:14:39 PM > DAGclient.Connect (addr): connect done (addr: "192.168.60.202", port: 22024)
05/16/2011 03:15:09 PM > Exception: "The operation timed out"
                       >    at VmCommon.ThreadManager.DoBackgroundTask(Int32 timeoutMilliSeconds, Boolean block, ThreadTask task)
                       >    at VmCommon.BackupAppliance.Connect(Int32 timeoutMilliSeconds, String password)
                       >    at BackupUI.VmBackupPlugin.AuthenticateAppliance(BackupAppliance appliance)
                       >    at BackupUI.VmBackupPlugin.<>c__DisplayClass5.<ActivateAppliance>b__3()
05/16/2011 03:15:09 PM > Connection attempt failed

So it may be an IP issue, but I dont know why yet.

[nebben]

My VDR pair is configured with a local account on my VC server. This was my intention, to always be able to fire up these VDR appliances and manage them regardless of the condition of my AD at that moment.

Make sure that in addition to there being the proper ports open from your VDR appliance and VC, but also your client and the VDR appliance. You also should have given whichever account you are using permissions within VMWare in the datacenter/cluster/host and so on.

When in doubt, try installing the plugin on the VI Client on the VC itself. See if you can make it go from there.

[tfindlay]

Hi again,

Still not having any luck with this, I have been using VI Client /w VDR plugin on my VC Server. Can confirm I can ping/SSH into the VDR guest from this machine, there is no firewall between it and the guest.

Looking into the VDR Guest console, I can see from netstat that there is a process listening on 22024 and my VC Server has a connection to it.

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 *:22024                     *:*                         LISTEN
tcp        0      0 *:5480                      *:*                         LISTEN
tcp        0      0 192.168.40.165:22024        ubvmvc02.tfapac.tontin:4519 ESTABLISHED
tcp        0      0 192.168.40.165:22024        ubvmvc02.tfapac.tontin:4518 ESTABLISHED
tcp        0      1 192.168.40.165:53144        192.168.60.10:ideafarm-chat SYN_SENT
tcp        0      0 192.168.40.165:48490        ubvmvc02.tfapac.tonti:https TIME_WAIT
tcp        0      0 192.168.40.165:48491        ubvmvc02.tfapac.tonti:https ESTABLISHED
tcp        0      0 192.168.40.165:48492        ubvmvc02.tfapac.tonti:https ESTABLISHED
tcp        0      0 *:5488                      *:*                         LISTEN
tcp        0      0 *:5489                      *:*                         LISTEN
tcp        0      0 *:ssh                       *:*                         LISTEN
tcp        0     52 ::ffff:192.168.40.165:ssh   ubvmvc02.tfapac.tont:pharos ESTABLISHED

With regard to authentication .... I've been connecting like so:

Workstation PC (Domain Account) --RDP--> VC Server (Domain Account)

on the VC server...

VI Client -> VC Server (using windows session credentials)

When connecting to VDR I do get a prompt for credentials, based on my domain account, but then it just times out. It would be nice if there was an application log I could find on the VDR Guest that could tell me what it was trying to do and why it wouldnt authenticate the VI Client connection.

[DSTAVERT]

Did you change the default login to the vDR appliance. root and vmw@re if I remember. Try that to see if it works.

[Stephanej]

I got many problems with Data Recovery, include this one...

Unable to connect to the appliance...

(Without modify any settings... no firewall, no credentials changes...)

so I restart the appliance about 6 times, and the connection works from VCenter.

The other problems is there is no Restore Points available ... (Suppose to have more than 50 RP on 30 backup VM)

too many bugs to use this solution as data recovery system...

It's much a "Data Maybe Recovery" System...

[Stephanej]

Just to complete the information...

Maybe I'm lucky...

I success to connect to tha Data Recovery Appliance after rebooting 6 times and...

my Restore Points reappear after deleting the .lck Folder and .lck files on the destination Folder.

No integrity Check needed.