Skip to main content

 

Druva Documentation

Delete and reactivate Phoenix AWS proxy

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

  This topic provides instructions to delete and reactivate the 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 policy or server group. Also, you can delete the AWS account only if all the attached AWS policies are deleted. 

Procedure

  1. Log on to 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 Manage > Disaster Recovery.
  4. On the Manage Disaster Recovery page, click the Phoenix AWS Proxies tab.
  5. Select the Phoenix AWS proxy instances that you want to delete and click Delete.

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

Reactivate Phoenix AWS proxy

To activate a previously deleted Phoenix AWS proxy, you will have to reactivate the Phoenix AWS proxy. When you reactivate an instance of AWS proxy, Phoenix AWS proxy establishes a persistent connection with Phoenix Master. The Phoenix AWS proxy is no longer disconnected; and instead, it performs a DR of the virtual machines across an ESXi or a vCenter Server following the backup schedule. 

Procedure

  • Register and activate the Phoenix AWS proxy. For more information, see Register Phoenix AWS proxy.
    The Phoenix AWS proxy will be reactivated.

After reactivating the Phoenix AWS proxy, restart the Phoenix AWS proxy client service using the /etc/init.d/Phoenix restart command.

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

  • Was this article helpful?