PowerProtect Data Manager 19.15 Deployment Guide

Cluster Shared Volume assets

After PowerProtect Data Manager is updated, any Cluster Shared Volume asset with a backup copy is listed twice in Assets pages, once with a status of Deleted and once with a status of Available. The Deleted entry continues to exist until the backup copy expires.

IPv6

IPv6 is only supported with new deployments. Using IPv6 after updating from PowerProtect Data Manager 19.11 or earlier is unsupported.

Memory requirements

An update package accounts for any new memory requirements. If additional memory is required, it attempts to automatically increase the memory that is assigned to PowerProtect Data Manager. If the amount of memory cannot be automatically increased, a precheck warning asks you to manually increase it.

To review memory requirements, see the PowerProtect Data Manager Administrator Guide.

Migrating to SupportAssist

SupportAssist provides automated support capabilities for PowerProtect Data Manager systems. SupportAssist replaces Secure Remote Services (SRS).

If you have configured SRS previously, the PowerProtect Data Manager system automatically migrates SRS to SupportAssist when you update PowerProtect Data Manager.

If you do not have SRS configured, you can configure SupportAssist directly. For instructions on configuring SupportAssist, see Connect to support services through SupportAssist.

System health

For up to a couple of hours after installing an update patch, the Health window displays a score that indicates the system is in poor health. This score and status remains in effect until all post-update activities are complete.

Updating DD or DDVE

If you are updating DD or DDVE software simultaneously with PowerProtect Data Manager, ensure that the following sequence of events is followed:

1. Disable all protection policies that use the affected DD or DDVE storage systems.
2. If any jobs started by protection policies are running, wait for them to complete.
   NOTE:Any scheduled replication, cloud tier, or extended replication jobs continue to run, and might fail during the update.
3. Update the DD or DDVE software.
4. Enable all protection policies that were disabled.

Updating the versions of TSDM VIB

Depending on the installed versions of TSDM VIB on ESXi hosts, the versions that are supported, and if VIB management is enabled or disabled, the versions of VIB are automatically updated with the version of PowerProtect Data Manager.

For more information about PowerProtect Data Manager package updates and the versions of TSDM VIB, see the PowerProtect Data Manager Virtual Machine User Guide.

Updating from version 19.11 and Continue On protection-policy options

If you update from PowerProtect Data Manager 19.11 or earlier, the Continue backup on data access denied and the Continue backup on ACL access denied protection-policy options are both reset to an unselected state.

If selecting either Continue On option is necessary for successful backups, the backups fail with the following error messages:

ABF0001: Unable to protect the asset … on the host … from the backup performed at time … because the following error occurred: Unable to backup the directory due to permission or locked state.
The backup for this asset cannot be completed because an error occured.

Updating from versions 19.11 through 19.14 and configured SMIS servers

The update package cannot be installed when attempting to update a PowerProtect Data Manager system that is configured to use an SMIS server.

When attempting to install the update package, the following error message is displayed:

If you are unable to remove all SMIS servers used as asset sources, contact Customer Support.

Updating from versions 19.11 through 19.14 and native reporting

Sometime after the update package is installed, the reporting engine undergoes a maintenance cycle on the reporting database to improve native-reporting performance.

The maintenance cycle takes place according to the following criteria:

• At least two successful server DR backups have been performed.
• It runs at midnight.

Additional considerations about the maintenance cycle include the following:

• It should only last a few minutes.
• The report browser is unavailable. Reports cannot be generated or viewed.
• Alerts are displayed for the start and stop of the maintenance cycle.
• Any reports that were scheduled to run during the maintenance cycle are delayed and run immediately after the maintenance cycle is complete.
• Once the maintenance cycle completes successfully, it never runs again.
• If for some reason the maintenance cycle is not complete after 50 minutes, it is aborted.
• If the maintenance cycle is unsuccessful or aborted, another maintenance cycle is scheduled for the following midnight.
• If a server DR backup takes place during the maintenance cycle, the backup of the reporting engine fails, but all other server DR data is successfully backed up.
• NOTE:To ensure the successful backup of the reporting engine, do not schedule server DR backups to run between midnight and 1:00 a.m. until after the maintenance cycle completes. Alternatively, after the maintenance cycle completes successfully and the backup of the reporting engine fails, perform a manual server DR backup.

Updating from version 19.12 or earlier and increased heap-memory settings

When updating from PowerProtect Data Manager 19.12 or earlier, increased heap-memory settings of the VMDM service are lost.

To resolve the issue, follow these steps:

1. Create a file named vmdm-env-local in /usr/local/brs/lib/vmdm/bin/.
2. Add the following content to the vmdm-env-local file:

   CUSTOMER_JVM_OPTS="-Xmx1536m"

   NOTE:In this example, replace 1536 with the megabyte value of the heap memory.
3. Run the following commands:

   chown admin:app vmdm-env-local

   chmod g+rwx,u+x vmdm-env-local

4. Run vmdm restart to restart the VMDM service.
   NOTE: Ensure that no other virtual machine operations such as protection or recovery are running.

Updating from version 19.12 and update-package upload times

The upload of an update package can repeat indefinitely when updating from version 19.12. This repetition causes the update process to never complete, making it impossible to update PowerProtect Data Manager. For steps to resolve the issue, see Manage PowerProtect Data Manager 19.12 user-token expiry.

Updating from version 19.13 or earlier and non-default ports

When updating from a deployment of PowerProtect Data Manager version 19.13 or earlier that is configured to use non-default ports, backup and restore operations might fail with error messages similar to the following.

ABA0009: … Unable to backup … asset … because of an agent host connection or agent service issue.
The protection policy backup was unsuccessful because either the agent host cannot be reached or the agent service is not running.

To resolve the issue, perform the following steps:

1. Install the update package.
2. Log in to the PowerProtect Data Manager server console using administrator credentials.
3. Run the command /usr/local/brs/lib/adm/config/configurePortInAllHostRecord.sh.