Home > Data Protection > PowerProtect DP Series Appliances > White Papers > Dell PowerProtect DP Series Appliance: Configuration Best Practices > Upgrade PowerProtect DP Series Appliance software (DP4400)
This section describes how to upgrade the PowerProtect DP Series Appliance software for a DP4400 model.
Table 15 details the supported upgrade paths for PowerProtect DP Series Appliance 2.6 on DP4400 models.
Note: If you do not update the firmware before running the software upgrade workflow, you cannot receive hardware-fault alerts on the Appliance Configuration Manager.
Table 15. Supported upgrade paths
Current version of PowerProtect DP Series Appliance | Supported version of PowerProtect DP Series Appliance for upgrade | More information |
PowerProtect DP Series Appliance version 2.3 | PowerProtect DP Series Appliance version 2.6 | You can directly upgrade to PowerProtect DP Series Appliance version 2.6, through the upgrade binary available on the Dell Support site. |
PowerProtect DP Series Appliance version 2.3.1 | PowerProtect DP Series Appliance version 2.6 | |
PowerProtect DP Series Appliance version 2.4 | PowerProtect DP Series Appliance version 2.6 | |
PowerProtect DP Series Appliance version 2.4.1 | PowerProtect DP Series Appliance version 2.6 | |
PowerProtect DP Series Appliance version 2.5 | PowerProtect DP Series Appliance version 2.6 |
This section describes the list of core PowerProtect DP Series Appliance components that are required for the upgrade process.
Upgrade components:
This section includes the prerequisites that you must complete before you begin the upgrade procedure.
Note: All the existing Protection Software packages and the snapshots are deleted before the upgrade.
admin@vdppunvm140:~/>: status.dpn
To restart MCS on Protection Software, log in to the Protection Software Utility Node with SSH (ssh login credential is admin and the password is the common appliance password that you would have provided) by using the Protection Software IP address, and run the command to stop it:
dpnctl stop mcs
Next, run the command to restart the Protection Software Server:
dpnctl start mcs
Upgrade the software for the components of PowerProtect DP Series Appliance from the Upgrade tab of the Appliance Configuration Manager.
Note: Ensure that only the upgrade file exists in this folder and no other post or prepatch packages exist.
If you do not have the executable permission, enter chmod 644 Idpa_Upgrade_<version>.tar.gz command to obtain the permission.
Note: The validation process takes approximately 15 minutes, and the Appliance Configuration Manager can time out while waiting. To resume the session, you must log in again.
The system validates the following:
Note the following Hypervisor upgrade prerequisites:
Note: The private IP address of the VCSA, 192.168.100.108, is only required temporarily during the upgrade process.
A table displays the current version, new version, and type (for example, major, patch) of each component for which an upgrade is available.
If the validation is not successful, check the errors that are displayed when you hover on the exclamation mark. Resolve all the errors and click Revalidate. If you want to cancel the upgrade and return to the Appliance Configuration Manager dashboard, click Cancel.
The upgrade process starts. The Appliance Configuration Manager also undergoes an upgrade which results in users getting logged out of Appliance Configuration Manager.
Note: The upgrade process can take five to six hours, during which all jobs on the PowerProtect DP Series Appliance must be quiesced. The system is not accessible during parts of the upgrade.
Note: If the upgrade process is still running, do not shut down or reboot the Appliance Configuration Manager or restart the dataprotection_webapp service.
If you have shut down or rebooted the Appliance Configuration Manager, or restarted the dataprotection_webapp service while the upgrade process is still running, and if you are unable to see the progress of the upgrade after the Appliance Configuration Manager is rebooted, contact Dell Support.
Note: After the upgrade is complete, there can be a scenario where Protection Software is in maintenance mode and the jobs cannot be started then. After Protection Software comes out of the maintenance mode, the jobs are started as per the next schedule.
Note: After the upgrade is complete, acknowledge the notification Event ConnectEMC notification failed on the Protection Software Administrator user interface. This notification is generated during an upgrade when the Protection Software service is disconnected.
Note: After the upgrade is complete, there is a warning on Hypervisor Manager about a potential vulnerability issue that is described in CVE-2018-3646. See https://kb.vmware.com/s/article/57374 and https://kb.vmware.com/s/article/55806 for more information. PowerProtect DP Series Appliance uses the Hypervisor version which has the fix for this vulnerability, however this fix is not enabled by default as it has severe performance impact. See the “Security updates and patching” section on the PowerProtect DP Series Appliance Security Configuration Guide for more information.
The following components are updated:
The dashboard with all the products and their upgraded versions is displayed along with the newly configured Appliance Configuration Manager.
If the upgrade for any component fails, then the upgrade process is stopped until you troubleshoot and resolve the failure. However, if there are any noncritical warnings, the upgrade process continues. These warnings must be resolved once the upgrade process is completed to ensure a trouble-free operation of PowerProtect DP Series Appliance.
You can troubleshoot the upgrade failures using the different options available.
When there is an upgrade failure for a component, the progress bar is displayed in red and you can see the RETRY and DOWNLOAD LOGS buttons.
To retry the upgrade again, click the RETRY button. Alternatively, you can click DOWNLOAD LOGS to download the logfiles.
If the Protection Software upgrade fails while upgrading the PowerProtect DP Series Appliance appliance software, and if you are retrying the Protection Software upgrade even after 24 hours of failure, you must manually upgrade the Protection Software server. If the Protection Software upgrade fails during the RETRY operation, with a message Validated checkpoint not found, you must manually resolve this issue by creating a checkpoint on the Protection Software Server. To create a checkpoint on the Protection Software Server, see the section Upgrade prerequisites for upgrade prerequisites. After you create a valid checkpoint, go to the Protection Software UI and click the Sync button which is displayed for the failed component.
If the Hypervisor Manager is rebooted when any component upgrade is in progress, the upgrade process stops. You must wait until the services on the Hypervisor Manager server are running, and attempt a retry of the upgrade for that component.
To verify that the Hypervisor Manager server services are running, log in to the Hypervisor PlatformvSphere client console. A successful login indicates that the services on the Hypervisor Manager server are started.
If the rollback is successful:
If the rollback fails:
If the PowerProtect DP Series Appliance rollback fails during the upgrade procedure, perform the following manual steps. Many of these steps are completed by the PowerProtect DP Series Appliance upgrade workflow because the PowerProtect DP Series Appliance upgrade does not stop operations if an error is encountered.
To delete the BeforeUpgrade Hypervisor Manager snapshots from all the components, perform the following steps on each of the components where the BeforeUpgrade snapshot exists:
i Shut down the Protection Software Service.
ii Revert to the snapshot and delete the snapshot.
iii Change all the data disks to independent-persistent.
iv Power on the Protection Software Service to verify if all the Protection Software services are up and running.
i Revert to snapshots of all Reporting & Analytics VMs Services such as Reporting & Analytics Datastore Server, Reporting & Analytics Application Server, Reporting & Analytics Agent, Reporting & Analytics DD Processor Tool, and others.
ii Delete the snapshots.
iii Log in using Putty to the Reporting & Analytics Datastore Server, and note down the datastore directory in /data01 with the name datastore-xxxx.
iv Run the following command:
/opt/emc/dpadpa/services/bin/dpadpa.sh datastore import /data01/datastore-*/
v Log in to the Reporting & Analytics Application Server using Putty and run the following command:
/opt/emc/dpa/services/bin/dpadpa.sh service start
vi Verify that the services are correctly starting by going to https://dpaAppServerIp:9002.
i Stop the SEARCH Services.
ii Shut down or power off the SEARCH vApp.
iii Revert to the snapshot BeforeUpgrade.
iv Delete the snapshot BeforeUpgrade from all SEARCH VMs.
v Change hard disk 3 mode to independent-persistent for all the SEARCH VMs.
vi Power on the SEARCH vApp.
vii Ensure that all SEARCH Services are up and running.
i Log in to SEARCH Index Master Node using Putty.
ii Run the following commands:
service dpworker status
service unicorn status
service elasticsearch status
dpnctl start scheduler
If it is present, record its name and uninstall it by using the –e dataprotection-upgrade-rpm-name command.
service dataprotection_webapp stop
service dataprotection_webapp start
If both the upgrade process and the snapshot recovery fail, collect the log files in the following locations and contact Dell Support: