I have the same issue with VDP 6.1 and vCenter 6.0.0.
I've opened support request.
im running 6.0 for VC and ESXi in this Environment
same here. I wanted to give VDP a test in my VCSA 6 Update 2 (just updated from Update 1 a few hours ago) environment and maybe use it as a replacement for our current vmware backup solution. I Downloaded the current VDP ova from VMWare Downloads (v6.1.2) and followed the install guide - all went well - up until I tried to click on the "connect" button in the vCenter Web Client VDP plug-in.
And yes, I have double checked DNS - forward and reverse.
Its not the known bug that the plug-in does not even show up in the Web Client. I see the plug-in and can basically start it. I just cannot connect to my VDP instance when asked to. The screen grays out (changing the cursor to the famous "please wait" clock) as soon as I click on the "connect" button and nothing happens. ever. I even uninstalled and unregistered the VDP installation (via https://MyvCenter/mob), reinstalled the whole VDP appliance. Same result.
Any news on this?
I'm in the same boat here with vCSA 6.0 U2 and VDP 6.1.2. The screen in the web client turns grey and there is no error message or timeout.
Same story here, i have reinstalled and unregistered the VDP installation. Connect = grayed out!
same problem here. U2 with VDP 6.1.2.
Also opened a request ticket 3 days ago.
Do you use a Standard Switch or a distributed Switch? When I connect VDP to a Standard Switch it worked. But when I add a VM on a distributed Switch to a backup Job it hangs
When I reconnect it to qa distributed Switch same Problem as you.
We are using distributed switch. When we changed to standard it worked.
But still waiting for support.
As I wrote I connect with standard switch, but it's immposible to add new backup job - system hangs.
Yes we use a distributed switch also. I was wondering about this. The port group that I'm using for the vCenter and the VDP appliance is in ephemeral mode. I changed to vCenter and VDP to a port group with static binding but there was no difference. I'll see if I can try the standard switch.
Are the vCenter and the vApp in the same subnet ?
We got same problem here (deployment is okay but we cannot connect to the vapp thru vsphere web client) and vmware support respond to us that VDP doesn't support routing between VDP and vCenter (?!).
We use dvs too with all component un 6.0U2 (vcenter/esxi) and VDP in 6.1.2 version.
Yes, same subnet between vCenter and VDP. ESXi is on a different subnet.
In my case all vCenter, VDP and ESXi in same subnet. As soon as you go to vCenter 6.0 U2 the only supported version of VDP is 6.1.2. Backups would be great to have.
I tried installing VDP 6.1.1 but ended up with the same issues. I think that the issue is vCenter (VCSA) 6.0 U2. If there are no patches for it I might be forced to try to VCSA 6.0 U1 that was working fine before.
This is also the case with vCenter 5.5 U3 :/
Any response from VMware Support?