Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager Appliance 5.15.0.0 Release Notes for DM5500

Resolved issues

The following issues have been resolved in Data Manager Appliance Software 5.15.0.0.

Table 1. Resolved issues in Data Manager Appliance Software 5.15.0.0Data Manager Appliance Software resolved issues
Issue ID Description
DMAS(P)-244856 Occasionally, when there was a heavily loaded system from VMware VADP workload with "swapfile exclusion" option and/or "metadata indexing" option enabled on policies, the system exhausted all the internal connections to the storage system over time due to a connection leak that did not get cleaned up in time, leading to backups being stalled. The VM backups failed with the following error:
Cannot connect to backup server
192.168.100.109':  [5040]

This issue has been fixed.

DMAS(P)-246120 When using an external protection storage or DDVE as the replication target, the system got into a state where creating a storage unit with retention lock compliance failed with the following message:
400: The specified Security Officer credential is invalid

This issue has been fixed.

DMAS(P)-246132 Occasionally, replication configuration was reported as failed even when it succeeded. This issue has been fixed.
DMAS(P)-238165 When the Kubernetes controller configuration parameter k8s.ppdm.vspherecsi.use.fsagentwas enabled to use the File System agent as the data mover for vSphere CSI backups, backups randomly failed with an error similar to the following due to CSI snapshot creation failure:
Unable to create snapshot … : Failed to check and update snapshot
content.

This issue has been fixed.

DMAS(D)-202647 There were no mtree commands. However, the mtree help was still visible in the CLI. This issue has been fixed.
DMAS(I)-23172 After an upgrade, a misleading critical alert (IAM db creation failed) was observed on the dashboard. However, the database was created successfully. This issue has been fixed.
DMAS(I)-23235 Occasionally, in situations where iDRAC may have delayed response, upgrade pre check failed with an error. This issue has been fixed.
DMAS(I)-23692 You would notice a non-Dell branded login screen after Keycloak upgrade. It was an intermittent issue. After reloading the page again, the Dell branded login screen was displayed. This issue has been fixed.
DMAS(P)-204271 Virtual machine protection backups failed with the following error:
The backup had terminated unexpectedly
This issue has been fixed.
DMAS (D)-188507 You might have observed socket timeout exception during the execution of the REST request for Protection storage log bundle creation workflow.
This issue occurred when Protection storage took more than 10 minutes for support bundle creation. The timeout was set to 10 minutes. Therefore, if the REST request took more than 10 minutes, the following error was observed:
java.net.SocketTimeoutException: Read timed out
This issue has been fixed.
DPDUI-2772 Protection Job logs were pushed off the bottom edge of the viewable screen. This issue has been fixed.
DMAS (I)-22847 When an AD user navigated to the Access Control > Directory Settings page, an internal server error was returned. This issue has been fixed.
DMAS(P)-235318 Protection job creation failed when elasticsearch was unavailable, resulting in jobs without children. This issue has been fixed.
DMAS(P)-240033 In the Assets window, providing a fully qualified domain name in a Host/Cluster/ Group Name filter did not return any matching entries. This issue has been fixed.
DMAS(P)-240922 When deleting a policy with a vault stage, the description of the unconfig job displayed "null" instead of the policy name. This issue has been fixed.
DMAS(P)-241340 During the appliance shutdown, the PowerProtect Data Manager Appliance UI did not check if iDRAC admin access was enabled or not and no warning was displayed. This issue has been fixed.
DMAS(P)- 242586 The PowerProtect Data Manager Appliance UI temporarily displayed a deleted storage unit. This issue has been fixed.
DMAS(P)-204271 When running many concurrent backup jobs and using a VM Direct Engine configured with either Hot Add or NBD, and where indexing was enabled or swap files were excluded, a backup job failed. The following error messages were seen:
ABV0006: VM Direct engine ... is unable to back up the virtual machineThe backup had terminated unexpectedly. (500)Protection of this virtual machine by the VM Direct engine cannot be completed because the backup was unsuccesful
This issue has been fixed.
DMAS(P)-243430 The filter on the Alerts page did not work as expected and showed both the unacknowledged and acknowledged alerts. This issue was observed only in Chrome when accessed from a Windows Jump Host. This issue has been fixed.
DMAS(P)-242971 When you attempted to create a storage unit on the replication target appliance with retention lock compliance, the UI prompted for security officer credentials. If the credentials entered were valid, but not for the security officer role, then the storage unit creation operation was initiated, however it failed when enabling compliance retention lock mode on the storage unit. The storage unit was deleted. However, a new storage unit with the same name could not be created immediately until garbage collection was run. You could wait for the scheduled garbage collection to run or trigger garbage collection manually using the Clean Now option on the Storage page. This issue has been fixed.
DMAS(I)-22933 If a registered AD's bind credentials were changed, and if it was not updated in the DM5500 appliance, the re-registration of the user for MFA failed with no error message. This lead to confusion because the re-registration screen did not appear during the next login. This issue has been fixed.
DMAS(P)-244108 Storage unit deletion from the PowerProtect Data Manager Appliance UI failed due to a timeout. When you retried the delete operation, it failed with the following error:
500: Failed to connect to PowerProtect DD System. errorNum: 5075 er
rorMessage: the user has insufficient access rights
This issue has been fixed.
DMAS(P)-246421 During the license download operation, you might have observed two instances of audit logs with identical information. This issue has been fixed.
DMAS(P)-246311 When you tried to delete a storage unit and the delete operation failed, the error message showed the internal ID instead of the storage unit name. This issue was observed if the credentials provided are not for the security officer role when deleting a storage unit with retention lock compliance. This issue has been fixed.
DMAS(P)-246276 After upgrade, server DR backup failed and within one hour backups resumed. You might have also observed a dip in health score during server DR backup failures. This issue has been fixed.
DMAS(P)-244802 When Retention Lock Compliance was enabled on the appliance, during the process, occasionally, the operation resulted in an error. The following error was displayed under System Jobs:
System Retention Lock Compliance Configuration Failed 
This issue has been fixed.
DMAS(P)-243985 Occasionally, where the Search cluster ran into any NFS I/O errors, especially during an upgrade, the upgrade failed with the following message:
OS precheck /Search cluster is not operational

The errors were transient. This issue has been fixed.

DMAS(P)-243831 The error message displayed when storage unit creation failed did not provide sufficient information. This issue has been fixed.
DMAS (C)-18860 A restore operation from a recovered vault using the Create and Restore New VM restore type failed. This issue occurred if the production DM5500 backup user and the vault user have different UIDs and the DDOS version was greater than or equal 7.10. This issue has been fixed.
DMAS(I)-24123 The network subnet is validated and shows an error in the UI when customer network subnet conflicts with appliance restricted subnet during Day 2 configuration of the Add Network or System Configuration page. Contact Dell Support to resolve network subnet conflict.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\