This section provides instructions for updating
PowerProtect Data Manager from an older version to the most recent version. It also provides considerations around updates in general.
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 installations. 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 Administration and User 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 are updating
DD or
DDVE software simultaneously with
PowerProtect Data Manager, ensure that the following sequence of events is followed:
Disable all protection policies that use the affected
DD or
DDVE storage systems.
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.
Update the
DD or
DDVE software.
Enable all protection policies that were disabled.
Updating from version 19.9
PowerProtect Data Manager 19.9 limited the size of update packages to a size less than that of the
PowerProtect Data Manager 19.13 update package. To resolve this issue, follow
KB article 000207379 before performing the update.
Updating from version 19.9 in a GCVE environment
CAUTION: If you do not have certain vCenter permissions set before the update, discovery fails.
If you are updating from version 19.9, ensure the following permissions of every GCVE-located vCenter server that has been added as an asset source:
The
GVE.LOCAL\CloudOwner user is mapped to the
Cloud-Owner-Role role at the vCenter level.
The
GVE.LOCAL\CloudOwner to
Cloud-Owner-Role mapping is not restricted to a lower-level container object in the vSphere object hierarchy.
Updating from version 19.9 in a Kubernetes environment
CAUTION: If you do not follow a Kubernetes-specific update procedure,
PowerProtect Data Manager might fail to function properly.
If you are updating from version 19.9 and have Kubernetes configured, see the
PowerProtect Data Manager Kubernetes User Guide for Kubernetes-specific considerations.
Updating from version 19.10 and the
reporting engine
CAUTION: If you do not follow a
reporting engine–specific update procedure, the
reporting engine fails to update when the
PowerProtect Data Manager update package is installed.
If you are updating from version 19.10 and have deployed the
reporting engine, see the
PowerProtect Data Manager Administration and User Guide for
reporting engine-specific considerations.
Updating from version 19.12 and update-package upload times
The upload of an update package can repeat indefinitely. This repetition causes the update process to never complete, making it impossible to update
PowerProtect Data Manager to 19.13 or later. For steps to resolve the issue, see
Manage PowerProtect Data Manager 19.12 user-token expiry.
Data is not available for the Topic
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: <>()\