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

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.

PowerProtect Data Manager (PPDM) backups may show "This job is queued and pending execution" in step logs even after successful completion. Backup files are available on the Restore tab. This UI display issue has no functional impact and is fixed in release 19.21 (bug PDM06C‑1489).

Knowledge base (KB) article that describes PowerProtect Data Manager Exchange backup failures due to port conflicts.

Replication jobs may fail when the PowerProtect Data Manager server attempts to connect to the replication source machine to check its status. If the connection attempt is initiated and a connection is not established within eight seconds, the job fails.

Incremental backup fails due to PowerProtect Data Manager not responding in the Snapshot and slice stage. Affected version 19.19 Fixed version in 19.21

The PowerProtect Data Manager appliance is used to protect the vSphere environment with the Transparent Snapshot Data Mover (TSDM) solution. There are Multiple hosts failing to install TSDM bundle with error code ABV0032.

The PowerProtect upgrade fails to update one or more disruptive subcomponents.

SQL Backup failure with error message: PowerProtect Data Manager error 63 Unable to access .ddbmcon.gatherinfo file from the settings folder.

By default, the installation wizard (CLR deployment wizard) creates the stored procedures in the master database. However, it is possible to create and register the T-SQL stored procedures in a user database, which is not a master database.

Resolving PowerProtect Data Manager database backup failure with FILESTREAM functionality: Set FilestreamEffectiveLevel to 3, enable FILESTREAM for Transact-SQL access, and restart SQL Server service.

This knowledge base article is to implement possible enhancements to the SQL table restore for Large Databases.

This article contains information about Hyper-V Backups failing with error "Connecting to remote server failed with the following error access is denied. For more information, see the remote troubleshooting help topic."

Hyper-v Backup Promotion to full Scenarios

PowerProtect Data Manager Active Directory Granular level recovery (GLR) Fails with Invalid Credentials.

With the release of PPDM 19.16 patch 2, an ability to enable the PPDM Certificate Authority (CA) functionality was made available. This supports signing of Certificate Signing Requests (CSRs) using an Intermediate Certificate Authority (Intermediate CA). This enhancement provides users who want to replace self-signed certificates with a customer-signed CA. This allows a flexible and secure certificate issuance process. This allows integration of hierarchical certificate structures and also replacing self-signed certificates with customer CA certificates.

Unable to restore namespace using Velero as imagestreamtags.image.openshift.io is not found.

K8s restore to existing namespace with PersistentVolumeClaim (PVC) fails with Insufficient Permissions.

Hosts that have agent services show multiple messages saying "agentService: OSError: [Errno 0] Error" in /var/log/messages OS file. This is not causing any issues with the connection between PowerProtect Data Manager and Agent, it is an unwanted error getting logged.

This article discusses whether custom changes can be made to the operating system on which the PowerProtect Data Manager (PPDM) server runs.

SystemDR backups after upgrade are not starting.

PowerProtect Data Manager: RecoverFcdTask: Unable to query volume for PV. ServerFaultCode: Permission to perform this operation was denied.

PowerProtect Data Manager - nodeSelector is not working for Velero pod for OpenShift.

PPDM: Oracle RMAN Backup Failure: ORA-19506: failed to create sequential file, name="…/XXXXXXXX-XXXXXXXX-ff".

Windows File System backups fail upon the addition of new nodes to the cluster.

The following article provides some guidelines to troubleshoot PowerProtect Data Manager services not starting.

PowerProtect Data Manager NAS backup causing OneFS panic and data unavailability due to changeFileTracking feature, must disable changeFileTracking.

How to use backup operator username instead of the sysadmin or DD Boost in PowerProtect.

PowerProtect Data Manager versions 19.15 to 19.19 may experience issues with Windows Network Time Protocol (NTP) configurations. The NTP configuration shows that "None of the specified NTP servers are suitable for time synchronization" error message during deployment.