I want to setup the vSphere Data Protection VM. The Import was successful.
But after that I opened the Webbrowser, entered "https://IP-aress:8543/vdp-configure".
At the side "vCenter registration" I entered
-vCenter port (443).
But what I have to enter at "SSO hostname"???
I tried the same hostname like the vCenter hostname, because I installed the vCenter SSO at the same machine.
I always get an error message, if I want to test the connection:
"The connection test did not complete successfully.
Modify your network settings or VDP credentials
and then click "Test connection" to run the
connection test again."
See also in the screenshot.
In the DNS I registered the VDP machine, also with a reverse lookup.
What is wrong?
yes, the name resolution is working fine.
Also if I try to enter the ip adress, I get the same error message.
Is it right, that at vcenter hostname and at SSO hostname I enter the same content?
The SSO service is also installed at the vCenter server.
If your installation is standalone(vcenter & SSO) on single box, then you have to provide the same name for vcenter & SSO.
The issue is mostly associated with your network configuration.
Try this steps:
1.ssh to the appliance using the default password "changeme"
2.try if you can ping the vcenter from appliance.
3.If ping reply is timed out !!. then you will have to look at your network configuration.
I checked the network settings again, further I configured also the hosts file at the VDP machine.
The network resolution with a ping from VDP to the vCenter and backwards was fine.
But nothing happened.
I installed vCenter and VDP completely new again.
Now in the vCenter registration at "vCenter-username" I entered the username with "domainname\username" format.
Now I get an error windows with a red cross only!?!
Is this VDP feature experimental??
I must say that first time deployment is a bit tricky and need to be done with much attention following the admin guide strictly
You might have done it right, but just want to give you a hint.
The "only cross" might be a miss in providing a message in local language (i18n).
VDP is a not an experimental product. once deployed properly should be perfect for a VM backup & recovery.
my god - I have solved it.
The vCenter user name is not an "normal" administrative account from the domain the vCenter is a member of, instead there I have to enter "system-domain\admin"!
OK - I just read this also in the admin guide.
How you wrote - this installation is anything else, but not easy like the older VDR versions...
Thank you for your help. Now I will test this non-experimental feature:-)
Great..I am happy that got going...
VDP deployment in fact looks complex but actually gives a ready made appliance. You do not have to install even the file level restore client .
I'm running into a similar problem with my VDP. It says that the user is don't have enough permissions even though it's a vCenter admin (see attachment below please). The name resolution works fine both ways and I can log into vCenter with the credentials I created for the VDP user and perform any admin task.
Here's a shot of the vCenter Role Manager:
I'm using the vCenter Server Appliance with DB's and SSO embedded.
Thanks in advance.
Thanks for your reply, but I got no luck. I still have the same error, but now I have a support request open for this problem.
I'll post the results once I get a reply from VMware.
Sehr geehrte(r) eMail-Absender/in,
ich bin bis einschl. 16. Oktober 2012 nicht in meinem Büro zu erreichen.
Eingehende E-Mails werden daher nur verzögert oder erst anschließend wieder bearbeitet.
In dringenden Fällen wenden Sie sich bitte an meine Kollegen unter der Rufnummer 05401-8442-0.
Dear Sir or Madam,
until October 16th I am not in my office.
Mails will be handled after my return.
In cases of urgency please call my colleagues at +49(0)5401-8442-0.
Mit freundlichen Grüßen / Kind Regards,
ISO Datentechnik GmbH
Amtsgericht Bad Iburg, HRB 3473
Geschäftsführer: Martin Osterfeld
Tel. +49 5401 8442-0
FAX +49 5401 8442-22