Skip to main content

How can we help you?

Druva Documentation

Upgrade backup proxy

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite


Each Druva release comes with new features and enhancements, and to use these features, you must have the latest version of Hybrid Workloads agent or backup proxy. Druva regularly provides updates to Druva backup proxy to enable it with new features and enhancements. Updates also include bug fixes and performance improvements.

This section also provides options on how to upgrade Druva backup proxy in your environment. As an administrator, you can upgrade Druva backup proxy using the following methods,

  • Upgrade backup proxy through Hybrid Workloads Management Console
  • Upgrade backup proxy through RPM 

Upgrade backup proxy through Hybrid Workloads Management Console

With the automatic agent upgrade feature, you can upgrade backup proxy to the latest versions from the Hybrid Workloads Management Console with a single click. 


Consider the following aspects before you upgrade the backup proxies:

  • Automatic rollback for RPM upgrade is supported from version 4.7.1 and later. 
  • To upgrade the backup proxy from an older version to version 4.7.1 or later, you must deploy the backup proxy. Automatic upgrade is supported from backup proxy version 4.7.1 onwards.
  • If an upgrade is triggered and schedule backup and restore jobs are in queue, the jobs resume after the upgrade is complete.


  1. Log in to the Hybrid Workloads Management Console
  2. From the top menu bar, select your organization if organizations are enabled. 
  3. Click Protect > VMware
    The All Virtual Machines page appears that lists all the registered vCenter/hypervisors. 
  4. You can either select the registered vCenter/ESXi host from the card view or list view or select it from the vCenter/ESXi host list in the left navigation pane.
  5. In the left pane, click Backup Proxies
  6. Under the Version column, you can see the current status for each proxy.



    Latest latest_version.png

    The current version is the latest available version for backup proxies.

    Non Upgradable not_upgraded.png

    The current version is not upgradable to the latest version through the Druva portal.

    Note: If the VMware backup proxy cannot be upgraded to the latest version, you must deploy a new ova for the latest backup proxy version.

    Scheduled upgrade sceduled_upgrade.png

    There is an ongoing upgrade.

    Note: Jobs that are in progress at the time of upgrade will restart after the upgrade is complete. Ongoing backup now jobs will fail after triggering the upgrade.

    Upgradable upgrade_available.png

    The current version is upgradable to the latest available version.

  7. To upgrade individual backup proxies across different pools:
    • Select the backup proxy(s) and click Upgrade.
      Upgrade backup proxy_1.png
  8. To upgrade backup proxies within a pool, click on the Back Proxy Pools tab.
  9. Click on the backup proxy pool.
    • Select the backup proxy(s) and click Upgrade.

Upgrade backup proxy through RPM 

Before you begin

Ensure that your existing backup proxy can be upgraded using RPM. If you are upgrading from an older backup proxy version to the latest backup proxy version, RPM upgrade can fail. For example, if you try to upgrade backup proxy using RPM, and in the logs you see a message like:

Vddk 6.0.3 not found on backup proxy. To install rpm please deploy latest backup proxy OVA

If you see a message similar to the one above, you cannot upgrade the backup proxy using RPM. To upgrade backup proxy, deploy the latest  backup proxy appliance and reconfigure the virtual machines to use the newly deployed backup proxy. 

If you can upgrade the backup proxy using RPM, download the latest backup proxy and perform the following steps. 


From the directory that contains the downloaded RPM, run the following commands:

  1. Open the command prompt.
  2. Run the following command to find the old package name of the Druva installer: 
rpm -qa | grep druva
  1. Run the following command to uninstall the old package:
rpm -e <old_package_name>

When you are prompted Do you want to cleanup all Phoenix config and data files: [yes/no]? [default: no], enter no

If you enter yes, all the Hybrid Workloads agent configuration files will be deleted. When you reinstall the agent you will have to reactivate it. 

  1. Run the following command to install the new package:
rpm –ivh <new_package_name>

where <new_package name> represents the file name (along with the extension) of the new installer.

Related articles 

Deploy Backup Proxy