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.

A recovery fails in PowerProtect Cyber Recovery because the Vault host cannot verify a CA‑signed certificate replicated from the Production host, leading to authentication errors.

The PowerProtect Data Manager (PPDM) appliance is used to protect the environment with Data Domain (DD) storage. The DD certificates display as expired in the PPDM UI. The Renew Certificate action in PPDM fails because the HTTPS certificate on the DD appliance itself has already expired. PPDM cannot retrieve a valid certificate until the DD generates a new one.

The PowerProtect Data Manager (PPDM) appliance is used to protect the vSphere environment with the VM Direct Engine solution. A disabled VM Direct Engine remains in DisablePending status. A redeployed VM Direct Engine remains in MaintenancePending status. Stale session metadata prevents the status from transitioning. The cause of the stale sessions is unknown.

The reporting engine was unable to send reports by email. No email notifications were received.

When configuring OpenID Connect (OIDC) Single Sign-On (SSO) between PowerProtect Data Manager (PPDM) and Okta, the Identity Provider creation fails during validation.

Performing a PowerProtect Data Manager Recovery from within Cyber Recovery fails shortly after the sandbox creation completes with Invalid Credentials Supplied error.

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.

PPDM recovery fails to connect with storage-unit while doing Data Domain storage replacement

Deploying a new Reporting Engine or upgrading to PowerProtect Data Manager (PPDM) 19.17.0-10 fails with the error "Failed to start the report service" because the certificate generation process cannot resolve the Reporting Node's IP address via nslookup. The nslookup failure is caused by a malformed /etc/resolv.conf file on the Reporting Node where multiple DNS nameserver entries are merged onto a single line instead of listed on separate lines. This is a software defect — PPDM generates the /etc/resolv.conf file on the Reporting Node during deployment, and the 19.17.0-10 build incorrectly merges multiple DNS entries onto a single line.

When any one of the Base Path of PowerScale source Volume for which snapshots are created, is deleted in PPDM, Execution of the expiration policy on all snapshots of that account fails.

List of PowerProtect Data Manager Agent executables or folders for whitelisting within antivirus software.

The PowerProtect Data Manager (PPDM) appliance is used to protect SQL database assets. Adding SQL assets to a protection policy fails with error code ACS0001. The configuration job cannot validate the storage connection to the Data Domain. Port communication from the backup client to the Data Domain data interface is blocked.

This article explains the network traffic flow in PowerProtect Data Manager (PPDM) NAS Protection Engine and provides guidance for multi-LAN configuration to segregate management and data traffic.

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.

PowerProtect Data Manager Linux deployment ppdmadmin status reports Core is Unhealthy due to HTTP Proxies

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 PowerProtect Data Manager (PPDM) appliance is used to protect the vSphere environment with the VM Direct Engine. The Automatic Update Setting for VM Direct Protection Engines is disabled. After upgrading PPDM, the VM Direct Engine is automatically redeployed to the new version. This occurs because the environment has only one VM Direct Engine for the protection type.

PowerProtect Data Manager (PPDM) version 20.3 supports multiple VLAN configurations for NAS Protection Engines. Multi-VLAN configuration segregates management and data traffic across different network segments. Existing protection engines cannot be modified with new VLANs after deployment. New NAS Protection Engines must be deployed with the required VLANs configured during the initial deployment.

Upgrade of reporting engine fails to "execute postupgrade steps for upgrade: otel-collector-reporting-node"

PowerProtect Data Manager (PPDM) services may fail to start after a boot or restart. This article provides guidelines for troubleshooting service startup failures. It covers the recommended troubleshooting order, log analysis approach, and required log collection for Dell Support.

The PowerProtect Data Manager (PPDM) appliance is used to protect the environment with Data Domain (DD) storage. Scheduled DD discovery jobs intermittently fail with error code ADS0005 and connection timeout errors. Full discoveries complete without error and backups remain unaffected. The failures are caused by HTTP connection-pool exhaustion in the discovery-service.

RecoverPoint for Virtual Machines: Protected Virtual Machines are impacted when using PowerProtect Transparent Snapshot Data Mover (TSDM) backups.

After upgrading the PowerProtect Data Manager to versions 20.2 or 20.3, large number of MON0043 alerts are observed everyday.

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.