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.

Dell PowerProtect Data Manager remediation is available for the Apache Log4j Remote Code Execution Vulnerability that may be exploited by malicious users to compromise the affected system. Dell recommends implementing this remediation as soon as possible in light of the critical severity of the vulnerability.

This article provides comprehensive instructions for using the GSAN Mover tool to migrate Avamar file system backup metadata to Dell PowerProtect Data Manager. The tool facilitates seamless migration while preserving historical backup metadata and maintaining data integrity.

Restore and FLR do not work for the Deleted NAS-Server from the Appliance.

A COPY_UPDATE job to unlock a retention lock returns CPM0016 indicating no matching MTrees. This is due to a stale cached API connection that routes the request to the wrong Data Domain system.

Service Level Agreement (SLA) compliance alert ID "CPLE0001" reports "No copies found" for existing Hyper‑V backups in PowerProtect Data Manager 20.2 and earlier. The defect is cited in PPDMESC‑15086.

Broadcom support of Transparent Snapshot Data Mover (TSDM) was returned in VMware Cloud Foundation version 9.1. This changed with the VMware vCenter Lifecycle Manager (vLCM) components requiring usage of the Application Programming Interface (API). With PowerProtect Data Manager 20.1, there is a manual method of deploying TSDM in VMware Cloud Foundation.

The virtual machine (VM) restore is configured, but it remains in a queued state with no progress due to an expired Data Domain certificate.

Performing a PowerProtect Data Manager (PPDM) Recovery within Cyber Recovery fails in Phase 1 after running for two hours.

Backups for Linux file system show ASBA0004, with one available and other NOT_DETECTED assets. Issue stems from the file system’s UUID changing after unmount mount actions, so the asset is not detected.

Virtual Machine (VM) Restore is using a different PowerProtect DD IP than expected for a VM restore. This can lead to failure due to VMware ESXi to DD communication or the restore writing data over an undesired DD IP interface.

ItemPoint compatibility with Outlook version for Exchange Granular recovery.

The last MultiSystem Reporting (MSR) collection status is showing as SKIPPED.

File System Agent backup fails with error "SQLite database initialization failed" and indicates a missing PLCTLP folder on the Data Domain.

Performing a PowerProtect Data Manager recovery within Cyber Recovery fails with the following: Message: Alert ID 2027 - PPDM Server DR copy recovery failed

An upgrade precheck returns error UPG0021, showing a failure in the Cloud Native component of PowerProtect Data Manager.

Broadcom returned support of Transparent Snapshot Data Mover (TSDM) in vSphere version 9.1 but changed the VMware vCenter Lifecycle Manager (vLCM) components requiring usage of the Application Programming Interface (API). With PowerProtect Data Manager 20.1, there is a manual method of managing the TSDM vSphere installation Bundle (VIB).

The Linux file system registration returns "preferred address is invalid" for Fully Qualified Domain Name (FQDN) or IP. A localhost.localdomain entry in the hosts file causes the agent to resolve an incorrect hostname.

This article identifies a case where the script get_dd_mtree_credential.py does not produce any output because it was accidentally zero'ed out.

The Share Size filter is missing and unsupported after upgrade to 20.1.0.0-17, preventing exclusion of replication NAS assets.

The PowerProtect Data Manager appliance is used to protect the vSphere environment with the Transparent Snapshot Data Mover (TSDM) solution. A virtual machine (VM) backup job fails with ABV0025 indicating the virtual disk requires a feature not supported by this program.

The PowerProtect Data Manager appliance is used to protect the vSphere environment with the virtual machine (VM) Direct Engine solution. The virtual machine backup fails with "ABV0030 msg.changetracker.MIRRORCOPYSTATUS" indicating a snapshot creation issue.

Network Data Management Protocol (NDMP) backups fail with error: ABNDMP0003: Unable to backup the NDMP asset because an error occurred on the Accelerator node: code 176: fatal signal (error code 10026)

ABNA0025: Unable to complete the SNAPSHOT_AND_SLICE operation because the snapshot path of the PowerStore share XXX for snapshot DELL-XXXX cannot be detected.

During a Cyber Recovery vault restore, PowerProtect Data Manager incorrectly inherits the production network interface from the asset’s protection policy, causing restore failures and misleading error messages. The issue appears in version 20.1 and earlier.

This article describes the issue when deleting Hyper-V virtual machines (VM) in the PowerProtect Data Manager UI.

PowerProtect Data Manager Upgrade fails to start with code "UPG0045."

LiveOptics data collection for Data Protection component PowerProtect Data Manager, returns errors '429' and '404'.

PowerProtect Data Manager backup for a VM fails when attempting to configure the VM for TSDM backup by enabling the LWD filter driver on the VM. The error received is "Unable to ENABLE LWD on VM1 - SPIF filters change failure: Not enough resources..Failed to attach I/O Filter vmwarelwd."

VM backups are failing with the error "The vCenter task failed. The operation is not allowed in the current state'. The error code is 'ABV0016'