Backup & Recovery

 View Only
  • 1.  vSphare Data Protection option not shown in vSphere Web Client

    Posted Oct 31, 2012 05:07 PM

    Hi,

    I have just upgraded vCenter virtual appliance from version 5.0 to 5.1.0.5100-799730. Then I have installed vSphereDataProtection-5.1.56.179. Deployment and setup finished with no errors. When I log in to VDP website, all services are "green" and running.

    When I log in vSphere Web Client, I cannot see Data Protection as an item in menu...

    I have tried to register VDP in vCenter once more (have changed name to IP in VDP configuration - vCenter registration). After VDP restart I was watching all messages shown on console, and VDP has registered in vCenter.

    I have tried to restart VDP, vCenter, to log in and out from vSphere Web Client, no success.

    What can be wrong?

    Thanks,

    Marcel



  • 2.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Posted Oct 31, 2012 06:56 PM

    If you are using active directory, I would suggest using the domain administrator account and also make sure that the user is assigned as administrator on the vCenter rather than try to use a active directory group.



  • 3.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Posted Oct 31, 2012 09:14 PM

    Greg, I am using local default "root" accounts in both vCenter and VDP. Is there anything special I should check in root Permissions?



  • 4.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Posted Oct 31, 2012 10:13 PM

    There shouldn't be anything specific with root permissions needed.

    Two things to check:

    1) There is a known defect that when you log into the web client, the VDP appliance will not show up the first time.  If you log out and back in, the VDP appliance will show up the 2nd time.

    2) If the above is not applicable, then in a browser, go to https://<vCenter_IP>/mob

    3) Click on content hyperlink

    4) Click on ExtensionManager hyperlink

    5) Check to see if the Extension "com.vmware.vdp" shows.

    If the Extension does not show, then it is a permissions issue we need to figure out, as the VDP appliance did not install properly.

    If it is showing, then we would need to look at logs, which means a VMware support case would most likely be required.



  • 5.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Posted Nov 08, 2012 09:26 AM

    Hi Greg,

    I have logged more than two times to vCenter and I don't see VDP there.

    When I have checked ExtensionManager in MOB, there is no com.vmware.vdp extension.

    I have reinstalled VDP before entering this incident, no help.

    Which logs are required? Where can I find them?

    Thanks,

    Marcel



  • 6.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Broadcom Employee
    Posted Nov 08, 2012 10:04 AM

    Can you paste the contents of av_boot.log located in /root of appliance



  • 7.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Posted Nov 16, 2012 06:30 PM

    Check date/time and NTP settings on your hosts, vCenter, and VDP.

    I was setting up a little test lab of all the new 5.1 stuff and frogot to setup time and NTP. After I got that sorted, I reran /vdp-configure/. After VDP rebooted it showed up in the vSphere Web Client as it should.



  • 8.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Posted Nov 20, 2012 02:51 PM

    This was happening to my team with VDP and VDR.  I just figured out how to get the option to show again.  Goto the login, attempt to login wtih your account and an invalid password.  After it kicks out the error, login again successfully.  This just worked for 3 different people on my team with different machines, browsers, etc.



  • 9.  RE: vSphare Data Protection option not shown in vSphere Web Client

    Posted Nov 26, 2012 01:48 PM

    Hi

    Try to run once again https://<ip address of VDP appliance>:8543/vdp-configure/ with SSO admin credentials. I had the same problem, that VDP didn't show up in the vSphere web client with other credentials.