For this issue, which applies solely to the VDP 5.5.6 appliance, you may see the following behaviors.
In the log file for the backup job (located in /usr/local/avamarclient/var-proxy-? and with the file name of JOBNAME-vmimageX.log (X can be 'w' for windows or 'l' for Linux), you may see the following errors:
avvcbimage Info <16041>: VDDK:VixDiskLibVim: Check server edition in license.
avvcbimage Info <16041>: VDDK:VixDiskLibVim: Unexpected server edition ZXN4QmFzaWM=.
avvcbimage Info <16041>: VDDK:VixDiskLibVim: Get NFC ticket completed.
avvcbimage Info <16041>: VDDK:VixDiskLib: Error occurred when obtaining NFC ticket for: [DS_MGMT_IBM501] vSphere/vSphere.vmdk. Error 16064 at 3707.
avvcbimage Error <0000>: [IMG0008] Failed to connect to virtual disk [DataStoreName] Path/VM_Name.vmdk (16064)
(16064) The host is not licensed for this feature
avvcbimage Info <0000>: Connecting virtual disk [DataStoreName] Path/VM_Name.vmdk
avvcbimage Error <0000>: [IMG0008] VixDiskLib_Open([DataStoreName] Path/VM_Name.vmdk) returned (16064) The host is not licensed for this feature
If you open a web browser and navigate to the vCenter's Managed Object Browser and the LicenseManager from there, you may find that the first defined License contains an 'editionKey' with the value of 'esxBasic'
To check this, open a web browser and navigate to "https://<IPofvCenter>/mob/?moid=LicenseManager&doPath-licenses"
Locate the Name [0] with the Type of "LicenseManagerLicenseInfo" (see image below)
To resolve this issue, you can remove the vSphere license and then add it back. This will move the license to the end of the list and allow for backups to run.