Skip to main content
Druva Documentation

Upgrade Phoenix AWS proxy

Phoenix Editions: File:/cross.pngBusiness         File:/tick.png Enterprise     File:/tick.pngElite
(Purchase Separately)

 This topic provides instructions to upgrade the Phoenix AWS proxy manually and through the Phoenix Management Console. Before you upgrade the Phoenix 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 Phoenix 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 Phoenix AWS proxy through the Phoenix Management Console

You can upgrade Phoenix AWS proxy to the latest versions from the Phoenix Management Console with a single click.

Note: You cannot upgrade the Phoenix 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 Phoenix 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 Phoenix AWS proxy.

Supported AWS regions

Druva supports the following AWS regions for disaster recovery:

  • AWS GovCloud (US West)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • EU (Ireland)

  • EU (Frankfurt)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Mumbai)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • South America  (Sao Paulo)

  • Canada (Central)

  • EU (London)

  • Asia Pacific (Hong Kong)

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 Druva Support.

Procedure 

  1. Log in to the Phoenix Management Console.
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Disaster Recovery.
  4. In the left pane, select the Phoenix AWS Proxies tab.
  5. In the Version column, you can view the current status of each Phoenix AWS Proxy along with its version number.
    Status Description

    Latest 

    The current version is the latest version available.

    Non Upgradable 

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

    Note: If the Phoenix AWS proxy cannot be upgraded to the latest version through an RPM upgrade, you must deploy a new AMI for the latest Phoenix AWS proxy version.

    Upgrade scheduled 

     There is an ongoing upgrade.

    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.

  6. Select the proxy that you want to upgrade and click Upgrade.
  7. Click Yes on the confirmation dialog box.

Upgrade Phoenix AWS proxy using RPM

To upgrade the Phoenix AWS proxy, navigate to the directory that contains the downloaded RPM.

Note: You cannot manually upgrade the Phoenix 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 Phoenix 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 Phoenix AWS proxy.

Procedure

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.

Limitations

  • If you have installed a hotfix on the existing Phoenix AWS proxy version, you cannot automatically upgrade to the next version from the Phoenix 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 Phoenix 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.