Articles
Invalid entry. Please use only Letters, numbers and any special characters except <>)(%/;,=#-/*
30 out of 691 shown
691 out of 691 shown
This article provides curated links to Dell PowerProtect Data Manager product documentation, videos, and information including deployment, configuration, administration, and disaster recovery.
Updated: November 12, 2025
ID: 000196987
Data Protection Advisor agent on Windows fails to register with the application server due to error HTTP response code is 403
Updated: September 10, 2025
ID: 000184051
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.
Updated: January 20, 2026
ID: 000385556
The Protection Jobs for several virtual machines (VMs) are failing with ABV0016 after a recent vCenter migration.
Updated: January 20, 2026
ID: 000412385
Scheduled or manual PowerProtect Data Manager NAS asset discover fails with Java out of memory heap space error.
Updated: January 20, 2026
ID: 000222437
PowerProtect Data Manager for Network Attached Storage (PPDM NAS) synthetic full backups of a Unity CIFS share fail with error ABNA0004.
Updated: January 20, 2026
ID: 000224629
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."
Updated: January 20, 2026
ID: 000218252
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
Updated: January 20, 2026
ID: 000223275
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.
Updated: January 20, 2026
ID: 000224705
Backups of VM assets are shown as 0 bytes in the PPDM UI (only cosmetics issue). Customer can restore VM without any issue.
Updated: January 20, 2026
ID: 000225054
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)
Updated: January 20, 2026
ID: 000210719
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.
Updated: January 20, 2026
ID: 000214960
PowerProtect Data Manager(PPDM) can't discover or backup VMs if they are protected by RecoverPoint, according to the PPDM VM Guide
Updated: January 20, 2026
ID: 000215026
PPDM does not allow more than 2500 assets to be added to a Protection Policy.
Updated: January 20, 2026
ID: 000215106
PPDM cannot backup VMs with no disks
Updated: January 20, 2026
ID: 000218150
PowerProtect Data Manager Centralized restore for SQL System databases fails with error code ARS0001
Updated: January 20, 2026
ID: 000345684
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
Updated: January 20, 2026
ID: 000225212
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
Updated: January 20, 2026
ID: 000225219
Customer cannot add Quick Recovery PowerProtect Data Manager facing error: Gateway Timeout Error
Updated: January 20, 2026
ID: 000225324
PowerProtect Data Manager Protection Policy job group status appears as Completed with Exceptions.
Updated: January 20, 2026
ID: 000225939
This KB article describes account requirements to add a Hyper-V Server or Cluster asset source in PowerProtect Data Manager.
Updated: January 20, 2026
ID: 000359505
The vCenter Asset Source discovery fails when discovering vCenters with virtual machines with no associated data center.
Updated: January 20, 2026
ID: 000209930
Deployment or Upgrading of PowerProtect Data Manager Reporting Engine to 19.17 Reporting Engine may fail.
Updated: January 20, 2026
ID: 000228160
PowerProtect Data Manager TSDM vSphere Installation Bundle (VIB) missing from ESXi host
Updated: January 19, 2026
ID: 000397489
PPDM is attempting to log in to vCenter using a domain login account with OKTA instead of the vCenter service account configured for the asset source.
Updated: January 16, 2026
ID: 000412320
After upgrading PowerProtect Data Manager (PowerProtect Data Manager) to version 19.19, the VMware vCenter discovery job stopped responding.
Restarting the discovery service allowed manual discovery to complete successfully.
Updated: January 16, 2026
ID: 000372541
PowerProtect Data Manager Report Browser shows no data.
Updated: January 15, 2026
ID: 000203397
PowerProtect Data Manager - scheduled report fails when "Canceled & Skipped" is selected; manual run works. Fix by editing the report template: Clear "Canceled & Skipped," save, then recheck it and save again.
Updated: January 15, 2026
ID: 000414952
Upgrade PowerProtect Data Manager with best practices: verify compatibility, take snapshots, follow security advisories, and use SolVe Procedure Generator.
Updated: January 15, 2026
ID: 000323604
Indexing jobs become stuck at 100% complete but remain in a Running Status in PowerProtect Data Manager 19.19 due to a code defect. This defect is resolved in version 19.20 and later.
Updated: January 15, 2026
ID: 000324792