Dell PowerProtect Data Manager Appliance 5.13.0.0 Release Notes for DM5500

PDF

Resolved issues

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

Table 1. Resolved issues in Data Manager Appliance Software 5.13.0.0Data Manager Appliance Software resolved issues
Issue ID	Description
DMAS(P)-190124	If a virtual machine was encrypted and vCenter 7.0 or later was used, an Instant Access virtual machine restore job failed to automatically migrate the virtual machine from the Protection Storage NFS datastore to local storage. When this event occurred, the restore job had a `Completed with Exceptions` status. This issue has been fixed.
DMAS(P)-197328	When performing a file-level restore to a new folder on a Linux virtual machine with Run with Elevated Privileges selected and logged in as a user in the local sudousers list, the new folder was owned by the root user. This prevented the restored files from being viewed. This issue has been fixed.
DMAS(P)-208668	When the Server DR backup was not successful for Reporting Agent, and then the delete_back operation was performed, the following failure error was displayed in Details field under System Jobs > Job ID:<xxxx>: `Unable to perform ReportingNode Agent operation 'delete_backup' on VM reporting.dpappliance.local (vm-33): ReportingNode Agent command error: exit status 1` This issue has been fixed.
DMAS(P)-208485	Users were unable to update credentials of replication systems. This issue has been fixed.
DMAS(P)-208676	Sometimes, the backup job was completed successfully with the error message `Unable to obtains status of Search plugin`. This error occurred when there was an issue in the VDDK connection to the Hypervisor Manager, which resulted in connection exhaustion. This issue has been fixed.
DMAS(P)-208232	If the page number was changed in Add Policy wizard, the total selected Assets number was not displayed . This issue has been fixed.
DMAS(P)-207494	You could not switch directly from All assets to Selected assets on the Resource Group Configuration page. This issue has been fixed.
DMAS(P)-207441	The Server DR backup job showed incorrect status on the Jobs page. The Jobs page of the job id showed the status as `Success`, whereas the details pane of the same job id showed `Failed` status with the failure reason. This issue has been fixed.
DMAS(P)-206818	When extracting the update package, the system failed to fetch the list of packages error. This issue has been fixed.
DMAS(P)-205869	Observed wrong throughput calculation in the UI. This issue has been fixed.
DMAS(P)-205827	The Details field of a failed job under Protection Jobs >Job ID <xxxx> incorrectly displayed the asset name instead of storage unit name in the alert error message. This issue has been fixed.
DMAS(P)-205826	The status of the Preparing for restore step was incorrect when Restore failed due to unhealthy Velero pod. This issue has been fixed.
DMAS(P)-205766	If there are two systems that are set as replication targets for each other with sync enabled, and if you deleted one system and added it back as replication target, the direction details on the UI was displayed as Outgoing instead of Bidirectional. This issue has been fixed.
DMAS(P)-205755	After the Administrator created the Security Officer role user, you could not modify the user information of the Security Officer. This issue has been fixed.
DMAS(P)-204161	When the Cloud Recall job was initiated and if the Protection Storage was full, the recall job did not fail immediately, and took 7 days to fail. During this job period, Protection Storage moved some files from cloud to local storage and made the copies inconsistent. This issue has been fixed.
DMAS(P)-203927	User could not perform centralized file-level restore of files with filenames starting with a hyphen (- ). This issue has been fixed.
DMAS(I)-16724	Server DR failed for SupportAssist after Day 1 configuration. This issue has been fixed.
DMAS(I)-16683	Creation of a log bundle failed with a warning message. This issue has been fixed.
DMAS(D)-173864	The administrator username to log in to CLI must be unique. If you deleted an existing admin user and created another with the same username, the login failed. This issue has been fixed.
DMAS(D)-173854	The Expand Capacity window did not display the error message `Storage expansion is not possible` when you removed and added a disk and immediately tried to open the Expand Capacity option. This issue has been fixed.
DMAS(D)-163889	Application or Consumer of DD Boost library did not see specific error code indicating that operations like fastcopy had failed due to mtree/storage-unit reaching or exceeding quota limit. They saw a generic error. This issue has been fixed.