Symptoms
PowerProtect Data Manager is at version 19.15.VM backups are using VADP Hotadd.Backups are failing with ABV002 error as seen below:
ABV0022: VM Direct engine … is unable to back up the virtual machine on … because of a VDDK issue. The VM Direct engine cannot complete the backup of this virtual machine because a VDDK operation was unsuccesful. Backup has FAILED. Unable to backup virtual disk … Unable to initialize Block Reader. Unable to open source VMDK … VDDK Error: 13. You do not have access rights to this file.
Cause
The PowerProtect Data Manager 19.15.0-17 VM Direct Engine (vProxy) installer has a default configuration of one SCSI controller.
Resolution
Note: As of February 9th, 19.15.0-25 has been released and VM Direct Engines again include four SCSI controllers by default. Upgrade to 19.15.0-25 or higher to apply the update.
Alternatively, if an upgrade is not possible at this time, manually add three SCSI controllers to the External VM Direct Engine.
In vSphere, right-click the VM Direct Engines (vProxy) and select Edit Settings.Select ADD NEW DEVICE > SCSI Controller and set the values to match the existing SCSI controller. As seen below:
Figure 1: Set the LSI logic parallel values.
Repeat these steps two more times. The recommended number of SCSI controllers is four.Select OK when completed and the VM appliance is updated.Run a backup of the Protection Policy.
NOTE: No backup failures may be encountered, but it is observed that many VMs are backed up using NBD on the PowerProtect Data Manager embedded VM Direct Engine. This is because the External VM Direct Engine does not have the SCSI slots available to complete a Hotadd backup. The same resolution applies to increase the External VM Direct Engine (vProxy) SCSI count to four.
