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 explains where to locate the PowerProtect Data Manager (PPDM) Software Serial ID (SWID) needed when creating a service request, including UI steps and license file method.

PowerProtect Data Manager (PPDM) storage replication encryption displays a status of "Off - Mismatch" after enabling replication encryption in PPDM. The Data Domain replication target does not appear in the GUI when configuring replication. This occurs because PPDM replication encryption requires File Replication DD Encryption to also be enabled on the Data Domain.

PowerProtect Data Manager (PPDM) supports backup and restore of Network Attached Storage (NAS) assets. Before running NAS backups, administrators must complete four setup steps. These include enabling the NAS asset source, deploying a NAS Protection Engine, adding credentials, and adding the NAS appliance or share. This guide walks through each step covering supported appliances including PowerScale/Isilon, PowerStore, Unity, and NetApp.

PowerProtect Data Manager (PPDM) vCenter and Data Domain (DD) discoveries stop running. Scheduled discoveries no longer execute and manually triggered discoveries remain queued indefinitely. The discovery-service retains a stale task ID from a previous discovery job after a service restart. This prevents new discovery tasks from processing.

Upgrade PowerProtect Data Manager with best practices: verify compatibility, take snapshots, follow security advisories, and use SolVe Procedure Generator.

When installing a PowerProtect Data Manager (PPDM) File System agent on a Windows multi-LAN environment, the agent registers with the correct IP address but the wrong Fully Qualified Domain Name (FQDN). The server has multiple network interfaces with different IPs and FQDNs. PPDM selects the first FQDN from its discovery results regardless of the IP chosen during installation.

PowerProtect Data Manager (PPDM) login with a Windows Active Directory account fails with an authentication error. The certificate from the Active Directory server has expired. PPDM cannot authenticate users against the external identity provider until the certificate is renewed.

PowerProtect Data Manager (PPDM) PowerMax volume restores from replication copies fail with error AERR0030. Restores from active storage complete successfully. The disaster recovery site does not have a Storage Direct proxy configured for the target PowerMax array.

A PowerProtect Data Manager (PPDM) upgrade on an AWS-deployed appliance fails during the RPM package installation phase. The /boot partition does not have enough space for the new kernel package. The partition contains leftover .vmimport files from the original AWS VM import process. These files consume space on the small 192 MB partition and prevent the upgrade from completing.

File Level Restore (FLR) of Linux VMware Virtual Machines (VM) fails with error ARV0032 because PowerProtect Data Manager cannot mount backup disks over NFS. Workaround is Instant Access restore of the VM and copy files.

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.

Logs Partition on the PPDM appliance is filling. Logmgr is not cleaning actively enough. This issue may occur on any PPDM appliance. However, this KB article should only apply to release 19.21 and later releases.

Linux file system backups performed through PowerProtect Data Manager fail with the error "5083-Invalid sequence number" during the data write operation to the Data Domain. The failure occurs when the DDR write operation encounters an invalid sequence number, which causes the write to fail and the backup to abort.

PowerProtect Data Manager (PPDM) discovery jobs for Cloud Snapshot Manager (CSM) fail when a CSM protection plan contains more than 100 assets. PPDM attempts to build a summary payload that exceeds the internal API size limit. The API returns an HTTP 413 "Payload Too Large" error. This aborts the discovery and protection processes. This is a known defect affecting PPDM versions 20.2 and earlier.

Dell PowerProtect Data Manager remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

VCenter SSL host certificates were renewed (new root + intermediate chain). Virtual Machine (VM) backups failed with "The VM Direct engine cannot complete the backup … connection between the vCenter Server and the ESXi (Elastic Sky X Integrated) host" error, and logs showed the certificate state as UNKNOWN.

This article explains the cause and resolution of the NVRAMRemoteBatteryFailure alert (Event ID: EVT-NVRAM-00202) on Data Domain systems; This alert indicates a critical hardware fault with the NVRAM remote battery, which must be resolved before the file system can be accessed.

An administrator cannot access the PowerProtect Data Manager appliance via SSH even though the PowerProtect Interface remains accessible. This issue occurs for one of two reasons: (1) the administrator attempts to SSH with a user account that was created in the PowerProtect Interface, which does not grant SSH access; or (2) the admin SSH account is locked due to repeated failed login attempts or the SSH password is forgotten. Unlocking the admin account or resetting the SSH password via the vSphere console resolves the issue.

The PowerProtect Data Manager interface cannot edit or modify a protection policy and displays a 503 error indicating that vCenter discovery has not been started or is still in progress. The root cause is a stale vCenter Server instance UUID stored in the Elasticsearch database (ESDB) that no longer matches the current vCenter instance UUID. PPDM cannot reconcile the mismatched UUIDs during discovery, which blocks protection policy operations. Dell resolved this issue in PowerProtect Data Manager release 19.14.0‑20.

On PowerProtect Data Manager server cloudmgr service is restarting resulting in cloud tier jobs to fail.

Exchange backups log a VolumeStream error and display "Unable to read from the volume. The device is not ready." The cause is a volume change creating a Volume Copy Block (VCB), invalidating the file handle.

This article explains how to resolve ADS0005 errors during DD system discovery in PowerProtect Data Manager caused by a misconfigured login session limit that prevents authentication token generation.

When configuring PostgreSQL database backups through the PowerProtect Data Manager (DM) Generic Application Agent, the default pg_dump backup script uses /tmp as a temporary staging area before writing the backup data to the Data Domain. If the PostgreSQL database is larger than the available space in /tmp, the backup fills the file system, causing PowerProtect Data Manager to run out of disk space, and the backup fails. This issue affects PowerProtect Data Manager environments using the default PostgreSQL backup script parameters.

PowerProtect Data Manager application recovery using Cyber Recovery Manager fails. The failure happens when doing the Storage-Unit replacement task. The 'Copy-catalog' service on PPDM crashes and restarts due to OutOfMemoryError during the storage unit replacement process which causes the problem.

The PowerProtect Data Manager appliance generates alert SYS0003 indicating low capacity on the /root mount point when available capacity on the root file system drops below 30%. Orphaned upgrade files from PowerProtect Data Manager 19.14 or 19.15 upgrades remain in the /usr/local/brs/lib/cdr/upgrade/ directory and consume disk space on the root mount point.

The PowerProtect Data Manager appliance generates alert SYS0003 indicating low capacity on the /logs mount point. The alert triggers when available capacity on the /logs file system drops below 25%. PowerProtect Data Manager includes an automatic log purge mechanism that activates when the /logs used capacity exceeds 90%, but the gap between the 25% alert threshold and the 90% purge threshold means the alert may persist for an extended period before automatic cleanup occurs.

The PowerProtect Data Manager appliance generates a daily SYS0003 alert indicating low capacity on the /agents mount point. The PowerProtect Data Manager 20.1.0.0-17 release includes uncompressed Oracle AIX agent packages and debug symbols that occupy excessive space on the /agents file system. This is a known defect that causes the /agents mount point to exceed its capacity threshold.

When PowerProtect Data Manager performs a DISASTER_RECOVERY:\ backup, the backup includes all available drives from the server, which can result in unexpectedly large backup sizes and potential storage space issues.