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

PowerProtect Data Manager 19.16 Deployment Guide

Troubleshooting PowerProtect Data Manager software updates

Review the following information related to updating the PowerProtect Data Manager software.

Installing an update package immediately fails with a 500 error

A package update might fail immediately after attempting to install it and display the following error:

500: Failed to start the update process.
The service is unavailable.

The Sysmgr.log file shows entries similar to the following:

[c.e.b.s.s.UpgradeServiceImpl.upgradeAppliance(474)] -  Failed to add certificate to KeyStore /data01/brs/upload/dellemc-ppdm-upgrade-sw-19.13.0-20.pkg (1).dellemc-ppdm-upgrade-sw-19.13.0-20.pkg (1).pkg (No such file or directory)
java.io.FileNotFoundException: /data01/brs/upload/dellemc-ppdm-upgrade-sw-19.13.0-20.pkg (1).dellemc-ppdm-upgrade-sw-19.13.0-20.pkg (1).pkg (No such file or directory)

In this example, the package name has been renamed from dellemc-ppdm-upgrade-sw-19.13.0-20.pkg.

To resolve the issue, delete the package, upload it again, and retry the installation.

If you cannot delete the package from the user interface, perform the following procedure:

  1. Log in to the PowerProtect Data Manager server console using administrator credentials and change to the root user.
  2. Run the command cd /data01/brs/upload.
  3. Run the command rm <update_package>, replacing <update_package> with the renamed update package.

Mounting a read-only file system results in a failed update

If you mount a read-only file system under the /home/admin or /home/sysadmin directories on the PowerProtect Data Manager node, the update cannot complete successfully. Ensure that you remove read-only file system mounts before updating PowerProtect Data Manager.

Automatic vCenter server discovery fails immediately after an update

An automatic vCenter server discovery might run shortly after an update, when the system is still in maintenance mode. If this discovery occurs, it fails without an error.

To determine the status of the vCenter server discovery, go to the Infrastructure > Asset Sources window. If the discovery fails, it is restarted every 30 minutes until the vCenter server is successfully added as an asset source. You can also manually discover the vCenter server when the system is no longer in maintenance mode.


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: <>()\