This topic provides instructions to upgrade the Phoenix AWS proxy manually and through the Phoenix portal.
Upgrade AWS proxy through Phoenix portal
With the Agent Upgrade feature, you can upgrade Phoenix AWS proxy to the latest versions from the Phoenix portal with a single click.
Note: This feature is supported from version 4.5 and later. You must manually upgrade to version 4.5 or later to use this feature.
- Log on to Phoenix Management Console.
- On the menu bar, click All Organizations, and select the required organization from the drop-down list.
- On the menu bar, click Manage > Disaster Recovery.
- On the Manage Disaster Recovery page, click the Phoenix AWS Proxies tab.
- Under the Version column, you can view the current status for each AWS proxy.
The current version is the latest version available.
The current version is not upgradable to the latest version through the Phoenix portal.
Note: If the AWS proxy cannot be upgraded to the latest version through an RPM upgrade, you must deploy a new AMI for the latest AWS proxy version.
There is an ongoing upgrades.
Note: Jobs that are in progress at the time of upgrade will resume after the upgrade is complete.
Upgradable 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.
Note: Automatic rollback for RPM upgrade is supported from version 4.6 and later. However, for fresh deployment to version 4.5 and later, automatic rollback is supported from version 4.5.
Manual upgrade of AWS proxy
To manually upgrade the AWS proxy, navigate to the directory that contains the downloaded RPM.
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>
- If you have installed a hot fix on your existing Phoenix version, you cannot automatically upgrade to the next version from the Phoenix portal. You must manually upgrade to the next available version.
- If the client machine restarts during the upgrade, then you must manually upgrade or rollback the client version.
- After triggering the update, if you have any ongoing backup and restore jobs, they will resume after the upgrade.
- If the old version is not present on the client machine, then upgrade rollback will fail. In this scenario, you must manually upgrade or rollback the client.