PowerProtect Data Manager

This article provides curated links to Dell PowerProtect Data Manager product documentation, videos, and information including deployment, configuration, administration, and disaster recovery.

Data Protection Advisor agent on Windows fails to register with the application server due to error HTTP response code is 403

The vCenter discovery fails with ADS0006 indicating a connectivity issue between PowerProtect and the vCenter server.

PPDM NAS Unity backup failed to reach the snapshot limit

PPDM NAS Backups of CIFS and or SMB shares fail with error: ABNA0023

PPDM NAS recover redirected to an NFS share on the same or different NAS fails with error code ARNA0023

PowerProtect Data Manager NAS backups fail with the error "Failed to parse the Override Append Path" and warning "Exception occurred while parsing the chunk metadata information."

PowerProtect Data Manager (PPDM) NAS large backup appears stuck before completion or cancellation due to job timeout.

Virtual machine (VM) restore jobs remain in queued status with 0% progress.

There is a significant increase in 409 conflict messages in the vmdm log after upgrading to PowerProtect 19.21.

The backup of the Linux file system failed with error ABF0001: ddfssv command failed with Fatal signal 11. Sufficient free space and --nouserinfo did not help. Prior cases were fixed by upgrading the client agent to version 19.18 or newer.

The Protection Jobs for several virtual machines (VMs) are failing with ABV0016 after a recent vCenter migration.

Scheduled or manual PowerProtect Data Manager NAS asset discover fails with Java out of memory heap space error.

PowerProtect Data Manager for Network Attached Storage (PPDM NAS) synthetic full backups of a Unity CIFS share fail with error ABNA0004.

The error message displayed when trying to install the VMware Installation Bundle (VIB) on the ESXi host: ABV0032:VM Direct engine is unable to configure protection for the host 'ESXi hostname' on vCenter "hostname."

VM SQL Application-Aware transaction log backups are failing with 'MSSQLDM Agent' is unable to perform 'backup_transaction_log' operation. ​​​​​​​SQL Server application-consistent data protection for virtual machines

When doing an FLR on Windows, the backups mounts without issues but when browsing the directories, some or all directories fail to be opened and browsed due to the 400: Access denied error. The user used to mount the backup can access these files and has permissions on the original VM for these folders. They can access these files from the mount point with the same user.

Backups of VM assets are shown as 0 bytes in the PPDM UI (only cosmetics issue). Customer can restore VM without any issue.

Virtual Machine (VM) backup fails because vCenter vSAN-Health service is down. The message seen in the PowerProtect Data Manager (PPDM) UI is vCenter SOAP call 'DpSnapshot' failed: POST "/vsanHealth": 503 Service Unavailable (500)

PowerProtect Data Manager (PPDM) Health Warning reports the following. Unable to perform Server Backup Validation Health Check due to the mount point /data01/server_backups is nonempty.

PowerProtect Data Manager(PPDM) can't discover or backup VMs if they are protected by RecoverPoint, according to the PPDM VM Guide

PPDM does not allow more than 2500 assets to be added to a Protection Policy.

PPDM cannot backup VMs with no disks

PowerProtect Data Manager Centralized restore for SQL System databases fails with error code ARS0001

Attempts to upgrade to PowerProtect Data Manager 19.16 fail with error: PPDM upgrade failed UPG0126 - Unable to update one or more disruptive PPDM sub-components. Failed sub-components: NASProxy

Attempts to upgrade to PowerProtect Data Manager 19.16 fail with error: PPDM upgrade failed UPG0126 - Unable to update one or more disruptive PPDM sub-components. Failed sub-components: NASProxy

Customer cannot add Quick Recovery PowerProtect Data Manager facing error: Gateway Timeout Error

PowerProtect Data Manager Protection Policy job group status appears as Completed with Exceptions.

This KB article describes account requirements to add a Hyper-V Server or Cluster asset source in PowerProtect Data Manager.

The vCenter Asset Source discovery fails when discovering vCenters with virtual machines with no associated data center.