Skip to main content

How can we help you?

Druva Documentation

Manage Phoenix AWS proxy

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

This topic provides instructions to perform the following tasks on the Phoenix Management Console:

Register Phoenix AWS proxy

To register Phoenix AWS proxy on the Phoenix Management Console, see Register Phoenix AWS proxy.

Upgrade Phoenix AWS proxy

To upgrade Phoenix AWS proxy manually and through the Phoenix Management Console, see Upgrade Phoenix AWS proxy.

Delete Phoenix AWS proxy

If you are an administrator, you can delete an instance of Phoenix AWS proxy at any time. After the delete operation, Phoenix AWS proxy loses the persistent connection. However, you can activate Phoenix AWS proxy again, see Reactivate Phoenix AWS proxy.

Note: You can delete the Phoenix AWS proxy only if it is not attached to any administrative group, AWS policy, or a DR plan. Also, you can delete a registered AWS account on the Phoenix Management Console only if all the attached AWS policies are deleted. 

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, click the Phoenix AWS proxies tab.
  5. On the Phoenix AWS proxies page, select the Phoenix AWS proxies that you want to delete, or select the checkbox next to the Name column to delete all the proxies, and click Delete.

    Delete proxy confirmation.png

When you delete a Phoenix AWS proxy, all the ongoing DR restore jobs on that Phoenix AWS proxy get canceled.

Reactivate Phoenix AWS proxy

To activate a previously deleted Phoenix AWS proxy, you must reactivate it. When you reactivate a Phoenix AWS proxy, it establishes a persistent connection with the Druva Cloud. The Phoenix AWS proxy is no longer disconnected, and it performs a disaster recovery of the virtual machines across an ESXi or a vCenter Server based on the backup schedule. 

For more information, see Register Phoenix AWS proxy.

Before you begin

Ensure that you save the activation token in a text file during the registration of the Phoenix AWS proxy. Phoenix also lists the generated activation token under Manage > Activation Tokens.

Procedure

  1. Log in to the Phoenix AWS proxy.
  2. Restart the Phoenix AWS proxy client service using the following command:
    /etc/init.d/Phoenix restart 
  3. Once the Phoenix AWS proxy client service is running, run the following command:
    PhoenixActivate <activation_token>

Note: If the Phoenix AWS proxy is offline with the jobs running or queued on the proxy, and if the new job is triggered for the same virtual machine, all the running and queued jobs are canceled and triggered for another proxy in the same AWS account and region. 

Verify the health of the Phoenix AWS proxy 

To check the health of the Phoenix AWS proxy, perform the following tasks:

  1. Log in to the Phoenix Management Console.
  2. Click the dropdown next to All Organizations, and select the organization that has your Phoenix AWS proxies.
  3. In the menu bar, click Disaster Recovery.
  4. In the navigation pane on the left, click Phoenix AWS proxies
  5. On the Phoenix AWS proxies page, the Connection Status column:
    • Displays a green tick if your Phoenix AWS proxy is connected to Druva Cloud. 
    • Displays a red cross if your Phoenix AWS proxy is not connected to the Druva Cloud. To re-establish a connection between the two:

Ensure that the Phoenix AWS proxy EC2 instance is up and running. If you are unable to get the Phoenix AWS proxy EC2 instance to start, deploy another Phoenix AWS proxy. The proxy deployment should complete in less than ten minutes. For any further assistance, contact Support.

View deployed proxies.png

  • Was this article helpful?