PowerProtect Data Manager Appliance 5.19.1 Patch Notes
Summary: This article provides information about the patch updates to the Dell Technologies PowerProtect Data Manager Appliance Release 5.19.1.
Instructions
Installation and upgrade considerations
Known issues, environmental and system requirements, and installation or upgrade considerations associated with these patch updates are the same as the parent release. For more information, see the Release Notes and PowerProtect Data Manager Appliance documentation.
Upgrade paths
Upgrading from PowerProtect Data Manager versions 5.15 through 5.19 to version 5.19.1 is supported.
Upgrading directly from versions 5.14 or earlier to version 5.19.1 is not supported. You must first upgrade to a version no more than 4 versions later than the version being upgraded from.
Security advisories
To review the latest Dell security advisories (DSAs), see the PowerProtect Data Manager Security Advisories website.
The Security tab shows DSAs, and the Technical tab shows Dell technical advisories (DTAs). DTAs are issues unrelated to security vulnerabilities.
Patch revision history
| Software version | Description |
|---|---|
| 5.19.1 | Patch 1 (August 4, 2025) |
Patch 1 (August 4, 2025)
Resolved issues
| Issue | Description |
|---|---|
| PPDMESC-10913 | Primary and secondary Domain Name System (DNS) servers are unreachable after updating to DM5500 Operating Environment version 5.19. |
| PPDMESC-10732 | Some backup jobs remain in queued state after updating to PowerProtect Data Manager version 19.19. |
| PPDMESC-10278 | Oracle database restore operation to an alternative Linux host fails when the Parameter File Options field is set to None. |
| PPDMESC-10091 | Active Directory (AD) configuration is not available after updating to PowerProtect Data Manager version 19.19 because some well known CA certifications cannot be resolved. |
| PPDMESC-9807 | Some backup copies are not included during the replication operation. |
| PDM09I-569 | Incorrect licensing size reported for Windows-based virtual machines. |
| PDM09H-371 | Status of deleted virtual machines may not be updated correctly and appear as "Not Detected". |
| PDM09H-369 | If you use the infrastructure-nodes API to view assets, you may see incorrect results in the Tree view. |
| PDM08C-586 | You can now renew certificates from the PowerProtect Data Manager UI for a DM5500 replication target after refreshing rootCA certificates. |
| PDM08C-435 | Cannot exclude PVCs from a protection policy until another namespace is added. |
| PDM08B-482 | File System FLR only displays 100 items per directory. |
| PDM06D-475 | A internal server error occurs (500 error) when trying to modify and save an existing report template. |
| PDM06D-327 | Server DR backup continues to run on a recovered PPDM in the CRS vault. |
| PDM05H-326 | Server DR recovery logic incorrectly requires DR storage unit (SU) password change. |
| PDM05G-529 | Indexing fails for virtual machines with Striped LVM configuration. |
| PDM05E-181 |
Replication fails after updating to DM5500 Operating Environment version 5.19.1 when refreshing rootCA certificates. For more information on renewing certificates, see the PowerProtect Data Manager Security Configuration Guide. |
| PDM05C-796 |
Discovery behaves inconsistently after updating to DM5500 Operating Environment version 5.19.1 when configuring bidirectional Quick Recovery on the replication target. |
| PDM05C-549 |
QR configuration fails with a 401 error: Invalid username or password. Once you add a secondary PowerProtect Data Manager system, ensure that you replace the system-generated credential with the credentials of the source system. To replace the credentials, on the secondary PowerProtect Data Manager system, go to Administration > Credential. Search for a credential with the suffix, <source_system_hostname>_PPDM_QR. Replace this credential with the current credentials of the source system. Note: <source_system_hostname> indicates the source system or primary site. |
| PDM05C-474 |
Reporting node is unavailable after updating to DM5500 Operating Environment version 5.19. |
| PDM05A-1758 | You can now reestablish trust from the PowerProtect Data Manager UI for a DM5500 replication target after refreshing rootCA certificates. |
| PDM04C-365 | Some SQL copy restore jobs do not run concurrently, even when they are targeted at different hosts. |
| PDM02D-740 | PowerStore discovery fails with ADN0005 error. |
Known Issues
| Issue | Description | Workaround |
| PPDMDOCS-4829, DM01C-883 | If a management or data network change is in progress on the System Configuration wizard, the existing default network will be discarded and will not be visible on the UI. | Wait for system reconfiguration to complete before viewing new default networks. |
Deployment and update considerations
| Issue | Description |
| PDM09A-103 | If you are protecting Hyper-V workloads, before updating to PowerProtect Data Manager version 19.19 patch 1 (19.19.0-20), ensure that the scheduled discovery option is set to "Off". |