Search the VMware Knowledge Base (KB)
View by Article ID

VDP 6.1.3 stops responding while VMs with multiple VMDKs on vSAN are backed up (2149101)

  • 1 Ratings
Language Editions


  • vSphere Data Protection 6.1.3 stops responding or fails at 92% while backing up virtual machines with multiple VMDKs on the vSAN.
  • The avvcbimage plugin gets crashed and throws stack dump when connecting to virtual machines VMDK files.
  • The proxy will not check the applicable transport mode, but it will try to connect using SAN mode directly.
  • In the /usr/local/avamarclient/var/vra-backups-reg-b-15-1486469231481-7a5a7913735e8b2bb706d0ee8aa4c821072a42b4-1016-vmimagel.log file, you will see the entries similar to:

    2017-02-07T12:16:15.730Z avvcbimage Info <14693>: skipping 103936 unchanged sectors in PAX stream at sector offset 104753152 for unused region
    2017-02-07T12:16:16.199Z avvcbimage Info <12030>: VADP cbt changed data was 11,283,005,440 bytes (21%)
    2017-02-07T12:16:16.199Z avvcbimage Info <40654>: isExitOK()=0
    2017-02-07T12:16:16.199Z avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Close: Close disk.
    2017-02-07T12:16:28.090Z avvcbimage Info <9679>: Virtual disk connection to '[LAX01A-VSAN01-MGMT01] e07e9858-7cd3-9d9c-29d2-ecf4bbd89670/hbrimagedisk.RDID-45ab4dce-ab2d-4892-a936-904a554ea88d.vmdk' has been closed
    2017-02-07T12:16:28.090Z avvcbimage Info <19718>: Found Disk from Device Key: '2001'.
    2017-02-07T12:16:28.090Z avvcbimage Info <9674>: virtual disk [LAX01A-VSAN01-MGMT01] e07e9858-7cd3-9d9c-29d2-ecf4bbd89670/hbrimagedisk.RDID-7b5e491d-f6ef-457a-aa72-a4448f3c8583.vmdk will be connected readonly
    2017-02-07T12:16:28.090Z avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_OpenEx: Open a disk.
    2017-02-07T12:16:28.090Z avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [LAX01A-VSAN01-MGMT01] e07e9858-7cd3-9d9c-29d2-ecf4bbd89670/hbrimagedisk.RDID-7b5e491d-f6ef-457a-aa72-a4448f3c8583.vmdk.
    2017-02-07T12:16:28.429Z avvcbimage Info <16041>: VDDK:VixDiskLibVim: Request RandomAccessRO diskKey = 2001, readOnly = 1, openSnapshot = 0.
    2017-02-07T12:16:28.524Z avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.
    2017-02-07T12:16:28.524Z avvcbimage FATAL <5889>: Fatal signal 11 in pid 25609
    2017-02-07T12:16:28.525Z [VcbImageBackupAssistThread]  FATAL ERROR: <0001> uapp::handlefatal: Fatal signal 11
    2017-02-07T12:16:28.525Z [VcbImageBackupAssistThread]  | 00000000006b9511

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Deploy the external vSphere Data protection proxy and disable the SAN mode check to back up the virtual machines with multiple VMDKs on the vSphere Data Protection 6.1.3.


This issue occurs due to a known issue in VMware Virtual Disk Development Kit version 6.5, where ESXi stops responding to VDDK connections when SAN mode is selected for VMDKs on the vSAN datastores which leads to the inability of vSphere Data Protection to perform the backup. For more information, see Virtual Disk Deployment Kit Release Notes.


This is a known issue affecting vSphere Data Protection 6.1.3.
To resolve this issue, perform the following steps:
  1. Deploy an external vSphere Data Protection proxy on the vSAN datastore.

    1. Log in to the vSphere Data Protection configure utility using the root user credentials.
    2. On the Configuration tab, click the settings icon in the Proxies section and select Add external proxy. The Add external proxy dialog box appears.
    3. On the Host and Storage page, select the host, storage, and network connection to deploy the proxy on, and click Next.
    4. On the Network connection page, provide the IP settings of the proxy and click Next.
    5. On the Ready to Complete page, review the deployment settings and click Finish button.

      Note: If you have deployed an external vSphere Data Protection proxy and if you are not performing emergency restore, disable the internal proxy.

      For more information, see vSphere Data Protection documentation.

  2. SSH to the vSphere Data Protection external proxy virtual machine and open the /usr/local/avamarclient/var/vddkconfig.ini file for editing.
  3. Disable the SAN mode check by adding the line at the end of the file and save the file:


  4. (Optional) Restart the avagent and vmwareflr services using these commands:

         service avagent-vmware restart
         service vmwareflr restart
Note: When the external proxy is enabled, you cannot perform emergency restores. For emergency restores, disable the external proxy and enable internal proxy.

For more information, see the following Dell | EMC articles:
Note: You will require a Dell | EMC support account.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.


VDP 6.1.3, Multiple VMDKs, vSAN

See Also

Language Editions


Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 1 Ratings