vADP Hotadd Supported Disks

Last post 03-10-2011, 8:45 PM by Brad Scott. 7 replies.
Sort Posts: Previous Next
  • vADP Hotadd Supported Disks
    Posted: 03-10-2011, 3:28 PM

    Hi,

    I am doing some testing with v9 SP1a hotadd VM backups.

    I have a VM that is a MA and a VSA proxy however i am having an issue when backing up a virtual machine on the same ESX server where i get the following error:

    CVMDiskInfo::Dispatch_VixDiskLib_Open() - VixDiskLib_Open failed Err=d You do not have access rights to this file

    Error opening Virtual Machine disk(s).  Please ensure that the proxy is able to communicate with the ESX host and resolve the ESX host address.  Also verify that the disks types configured to the virtual machine are supported.

     

    The permissions error is strange as I am connecting directly to an ESX server using the root user account.

    The disk issue is also not making any sense the only thing different about the disks is that they are set to thin provisioned. I did not think that was an issue though.

    The MA can communicate to the ESX server as it is creating a snapshot before this error occurs.

    Has anyone else come across this problem before?

  • Re: vADP Hotadd Supported Disks
    Posted: 03-10-2011, 3:42 PM

    The failure happens when this particular disk is trying to be hot-added to the proxy server. 

    Does the vixdisklib.log file have any further details or do you see any errors in the VIC GUI?

  • Re: vADP Hotadd Supported Disks
    Posted: 03-10-2011, 3:57 PM

    No the vxdisklib.log file looks fine. This is the first time this VM is being backed up so the HDD is being added to hotadd.

    The ESX server is 4.1 ESXi using and Advanced vSphere license which i understand is supported for ESXi.

  • Re: vADP Hotadd Supported Disks
    Posted: 03-10-2011, 4:05 PM

    Advanced and above licensing supports hotadd so you are good to go from that front.  Can you doublecheck where this VMDK lives in comparison to the hotadd VM to see why the issue appear erroneous?

  • Re: vADP Hotadd Supported Disks
    Posted: 03-10-2011, 4:12 PM

    Both VM's the MA/VSA Proxy and the target client are all on Datastore1

  • Re: vADP Hotadd Supported Disks
    Posted: 03-10-2011, 5:12 PM

    Although root should have full access, can you attempt the following:

    Open  you VIC GUI and log directly into the ESX server using root. 

    Go to the VM in question and right click go to add permissions

    Add root as the user and select the drop down for administrator to ensure all things are checked.  Make sure proprogate to all child objects is selected and save the changes.  Then try a backup and see whats up.

  • Re: vADP Hotadd Supported Disks
    Posted: 03-10-2011, 6:34 PM

    OK I have tried the following:

    Updated the Gateway address for the VMKernal

    Added DNS entry for the MA/Proxy for the ESX hostname (even through I am not using it)

    Added the security you mentioned above

    Rebooted the ESX server

    The error is now the following:

    2812 be0 03/11 12:24:56 3402 CVMDiskInfo::Dispatch_VixDiskLib_Open() - VixDiskLib_Open failed Err=d You do not have access rights to this file

    2812 be0 03/11 12:24:56 3402 CVMWareInfo::_MountVM_VCB4() - Failed to Open Disk [[DataStore1] Sandbox/Sandbox-000002.vmdk]

    2812 be0 03/11 12:24:56 3402 CVMWareInfo::_MountVM_VCB4() - Unable to open any disks on VM Sandbox 1 attempted

    2812 be0 03/11 12:24:56 3402 CVMWareInfo::MountVM() - MountVM_VCB4() failed!!

    2812 be0 03/11 12:24:56 3402 CVMWareInfo::_UnmountVM_VCB4() - Unmounting Disks for VM [Sandbox]

    2812 b30 03/11 12:24:56 3402 CVMDiskInfo::_VixDiskLibThread() - Calling VixDiskLib_Disconnect for thread be0

    2812 b30 03/11 12:24:56 3402 CVMDiskInfo::_VixDiskLibThread() - Completed VixDiskLib_Disconnect for thread be0

    2812 b30 03/11 12:24:56 3402 CVMDiskInfo::_VixDiskLibThread() - Calling VixDiskLib_Cleanup for thread be0

    2812 b30 03/11 12:25:03 3402 CVMDiskInfo::_VixDiskLibThread() - Completed VixDiskLib_Cleanup for thread be0

    2812 be0 03/11 12:25:03 3402 CVMWareInfo::_UnmountVM_VCB4() - Removing Snapshot of VM [Sandbox] Guid [564dfd50-7e58-4158-9b9e-e61212ae5244]

    2812   5 03/11 12:25:04 3402 ### RemoveSnapshot --- Removing Snapshot __GX_BACKUP__ 240-snapshot-14 from VM Sandbox

    2812 be0 03/11 12:25:06 3402 CVMWareInfo::_UnmountVM_VCB4() - Successfully removed Snapshot of VM [Sandbox] Guid [564dfd50-7e58-4158-9b9e-e61212ae5244]

    2812 be0 03/11 12:25:06 3402 vsbkp::CheckVMInfoError() - VM [Sandbox] Error opening Virtual Machine disk(s).  Please ensure that the proxy is able to communicate with the ESX host and resolve the ESX host address.  Also verify that the disks types configured to the virtual machine are supported. 2812 be0 03/11 12:25:06 3402 CVMWareInfo::_UnmountVM_VCB4() - Unmounting Disks for VM [Sandbox]

  • Re: vADP Hotadd Supported Disks
    Posted: 03-10-2011, 8:45 PM

    Right found a resolution to this.

    Turns out that the Virtual Client for CommVault comes with it's own version of VDDK. Installing VDDK v1.2 or even 1.1 conflicts with this instance which is located in <simpana install location>\base\VMWARE\VDDK and as such refuses to backup the vmdk files.

    Uninstalling the VDDK instances from Add/Remove Programs fixes the issue.

     

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy