This topic provides instructions to upgrade the Druva AWS proxy manually and through the Hybrid Workloads Management Console. Before you upgrade the Druva AWS proxy, verify that the content of the IAM policy attached to the IAM role matches the content defined in the DruvaIAMPolicy topic.
Note: If you have deployed Druva AWS proxy without using a CloudFormation Stack, ensure that you only open an outbound port 443 (HTTPS). For secured remote login, you can open an inbound port 22 (SSH).
Upgrade Druva AWS proxy through the Hybrid Workloads Management Console
You can upgrade Druva AWS proxy to the latest versions from the Hybrid Workloads Management Console with a single click.
Note: CentOS has reached end-of-support. If you have your proxy deployed on CentOS (AWS proxy version 6.3.3 or earlier), you must manually upgrade it to Ubuntu proxy by deploying the CloudFormation stack. For more information, see Deploying CloudFormation stack template for migrating AWS Proxy from CentOS to Ubuntu.
Supported AWS regions
To know the AWS regions that Druva supports for disaster recovery, see the Downloads page.
In addition, AWS provides other regions that Druva can support for disaster recovery. For more information on regions that AWS provides, see Global Cloud Infrastructure. To know more about the regions that Druva can support for disaster recovery, but are not listed in the previous list, contact Support.
- Log in to the Hybrid Workloads Management Console.
- On the menu bar, click All Organizations, and select the required organization from the drop-down list.
- On the menu bar, click Disaster Recovery.
- In the left pane, select the Druva AWS proxies tab.
- In the Version column, you can view the current status of each Druva AWS proxy along with its version number.
The current version is the latest version available.
The current version is not upgradable to the latest version through the Druva portal.
Note: If the Druva AWS proxy cannot be upgraded to the latest version through an RPM upgrade, you must deploy a new AMI for the latest Druva AWS proxy version.
There is an ongoing upgrade.
Note: Jobs that are in progress at the time of upgrade will resume after the upgrade is complete.
The current version is upgradable to the latest available version.
- Select the proxy that you want to upgrade and click Upgrade.
- Click Yes on the confirmation dialog box.
Upgrade Druva AWS proxy using RPM
To upgrade the Druva AWS proxy, navigate to the directory that contains the downloaded RPM.
Note: You cannot manually upgrade the Druva AWS proxy from version 4.7.x to 4.8.0 using an RPM upgrade.
This feature is supported from version 4.8.0 and later. You must deploy a new Druva AWS proxy using an AMI for version 4.8.0. You can launch the latest AMI from the AWS console. For more information, see Register Druva AWS proxy.
1. Locate the current installed RPM.
rpm -qa | grep druva
2. Remove the existing RPM.
rpm -e <curr_rpm_name>
3. Install the new RPM.
rpm -ivh <new_rpm_name.rpm>
Note: Automatic rollback for RPM upgrade is supported from version 4.8.0 and later. However, for fresh deployment to version 4.8.0 and later, automatic rollback is supported from version 4.8.0.
- If you have installed a hotfix on the existing Druva AWS proxy version, you cannot automatically upgrade to the next version from the Hybrid Workloads Management Console. You must manually upgrade to the next available version.
- If the client machine restarts during the upgrade, you must manually upgrade or rollback the client version.
- If you upgrade the Druva AWS proxy with version 4.8.0 to 4.8.2, any ongoing DR failover job fails. However, any ongoing DR restore job resumes after the upgrade.
- If the old version is not present on the client machine, the upgrade rollback will fail. In this scenario, you must manually upgrade or rollback the client.