Skip to main content
Druva Documentation

Deploy Phoenix AWS proxy

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

Overview

Phoenix AWS proxy is an Elastic Compute Cloud (EC2) instance that runs the Phoenix disaster recovery service. It orchestrates copying data from the Phoenix Cloud to your AWS account and creates a DR copy at a frequency specified in the DR plan. The Phoenix AWS proxy runs in your AWS account. The Phoenix AWS proxy is launched in the same AWS region where the virtual machine backups are located. The EC2 instances are started in the same region for disaster recovery.

Watch the following video to know more about how to deploy Phoenix AWS proxy.

​​​​​​

Phoenix AWS proxy setup workflow

You must first select the AWS storage region on the Phoenix Management Console and create an AWS CloudFormation stack to define the AWS resources. Phoenix uses AWS CloudFormation to automate the current manual proxy deployment processes. It also includes the prerequisites of proxy deployments, such as the creation of IAM policy and IAM role, creation of IAM instance profile, security group, and attaching the policy to the proxy, deploy proxy by registering and activating the proxy.

AWS CloudFormation provides a simple JSON-based template to define all the AWS resources that you need to deploy your infrastructure for disaster recovery and a stack to create and manage the resources. For more information, see AWS CloudFormation Concepts.

The following diagram depicts the workflow to set up the Phoenix AWS proxy and the corresponding portals to perform the setup.

 

Step Description
Step 1: Select the AWS storage region ​​​​​​

Select the AWS storage region on the Phoenix Management Console where you want to deploy the Phoenix AWS proxy for disaster recovery.

See, Deploy Phoenix AWS proxy

Step 2: Click the Create CloudFormation Stack button Click the Create CloudFormation Stack button on the Register Phoenix AWS Proxy page to configure your AWS resources. You are redirected to your AWS account.
Step 3: Log in to your AWS account Log into your AWS account to define the AWS CloudFormation stack parameters.
Step 4: Create AWS CloudFormation Stack
  1. Define Phoenix configuration parameters
    Select one of the deployment template options, such as InfraAndProxyDeployment or ProxyDeployment, to deploy the IAM policies, roles, and proxy instances in your AWS account.
  2. Define Network configuration parameters
    Select the VPC and subnet specific to your AWS account to launch the Phoenix AWS proxy.
  3. Define AWS EC2 configuration parameters
    Select a type for the AWS proxy instances and an EC2 key-pair to enable SSH access to the proxy instance. Depending upon your subnet settings, select the Auto-Assign public IP option as true or false.
  4. Review and create the stack
    Validate the parameters selected and click Create to create the stack.

See, Deploy Phoenix AWS proxy

Step 5: View the deployed proxy

On the Phoenix Management Console, select your organization and click Disaster Recovery > Phoenix AWS Proxies tab, and view the deployed proxy on the Phoenix AWS Proxies tab.

See, Deploy Phoenix AWS proxy

Note:  To  login to the AWS proxy use "centos"  as the username  and use the key pair you provided while deploying the AWS proxy.

Considerations

  1. You must register the Phoenix AWS proxy in the same region as the server storage region.
  2. For disaster recovery over intranet:  Before you deploy Phoenix AWS proxy in the AWS customer account, ensure you have created an Amazon Virtual Private Cloud. For more information, see Create VPC for AWS proxy deployment.
  3. When you delete a stack, AWS does not delete resources attached to the stack. Ensure that you manually delete the resources attached to the AWS account.

Select an AWS region on the Phoenix Management Console 

  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, click Register Phoenix AWS Proxy.
  6. On the Register Phoenix AWS Proxy page, from the AWS Region drop-down list, select the AWS region where you want to deploy the proxy. For example, us-west-2.

    NoteDeploy the Phoenix AWS proxy in the same region where the virtual machines that you intend to configure for disaster recovery are backed up in Phoenix. For example, if the virtual machines are backed up to a storage in Phoenix that is located in the US-East region, deploy the Phoenix AWS proxy in the US-East region.

    Register_proxy_cfs.PNG

    The Activation Token section displays an activation token that is used while creating the CloudFormation Stack.

    Note: Phoenix lists the activation token under Manage > Activation Tokens.

  1. In the AWS CloudFormation Stack section, click Create CloudFormation Stack to register the Phoenix AWS proxy.

If you are logged in to the AWS Management Console, you are directed to the Quick Create Stack page. Else, you are directed to the login page of the AWS Management Console. Use your credentials to log in and the Quick Create Stack page appears.

Create a CloudFormation Stack on the AWS Management Console

The Quick create stack page on the AWS Management Console uses a proxy deployment template depending on your first-time proxy deployment or the subsequent deployments.

  1. In the Quick create stack page configure parameters for your AWS resources defined in the template.

    General stack parameters

    CFS_template.JPG

    Field Description
    Template URL Displays the URL of the Druva deployment template used for your proxy deployment.
    Stack description The description of the Druva deployment template used.
    Stack name Displays the name generated by Phoenix for your stack.
    Phoenix Configuration parameters
    CFS_parameters1.JPG
    Field  Description
    DeploymentType
    • InfraAndProxyDeployment: This template is used for the first-time proxy deployment. It is a JSON-based CloudFormation template, which is used to deploy the IAM policies, roles, and proxy instances in your AWS account.

      Note: If you have deployed an IAM role using the InfraProxyDeployment option and try to use the same option to launch an instance, the stack creation process fails as it tries to create the DruvaIAMRole role, which is already created.

    • ProxyDeployment: This template is used to deploy only proxy instances and reuse the existing IAM policies and roles created for your AWS account during the previous deployments.
    PhoenixActivationToken Displays the Phoenix activation token generated based on the selected AWS storage region on the Phoenix Management Console.
    InstanceCount Specify the number of proxy instances that you want to launch. You can specify up to 5 instances. The default value is 1.
    Network Configuration parameters
    CFS_parameters2.JPG
    Field Description
    VPC Select a Virtual Private Cloud (VPC) network specific to the AWS account to launch the Phoenix AWS proxies.
    Subnet Select a subnet to launch the Phoenix AWS proxies in the specific network in your VPC.
    Amazon EC2 Configuration parameters
    CFS_EC2_config1.JPG
    Field Description
    InstanceType

    Select the instance type for the Phoenix AWS proxy.

    Note: It is recommended to select the instances based on the following configuration: 8 CPUs, 16 GB memory, 3500 Mbps bandwidth, 10,000 IOPS.

    KeyPair Select an EC2 key-pair to enable SSH access to the proxy instance.
    AutoAssignPublicIP

    Select the option based on the chosen subnet.

    • true: Select this option if you want to assign a public IP after launching the Phoenix AWS proxy and have chosen a public subnet in Step 3.
    • false: Select this option if you do not want to assign a public IP after launching the Phoenix AWS proxy and have chosen a private subnet in Step 3.
      The stack template may list certain capabilities for AWS CloudFormation to create the AWS resources in your stack.

      Note: When you deploy Phoenix AWS proxy using the CloudFormation Stack, Phoenix DRaaS opens an outbound port 443 (HTTPS). For secured remote login, you can open an inbound port 22 (SSH). 

  2. In the Capabilities section, select the check boxes acknowledging that AWS CloudFormation might create IAM resources with custom names and that AWS CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND.
  3. Click Create stack.
  4. Verify the status of stack creation on the Stacks page on the AWS Management Console. If the status is:
    • CREATE_COMPLETE: Phoenix lists the registered Phoenix AWS proxy on the Phoenix AWS Proxies tab on the Phoenix Management Console.
    • CREATE_FAILED:  Check the Events section on the Stacks page on the AWS Management Console for more details. You can also contact Druva Support. See Troubleshoot common scenarios.
  5. You can view the deployed AWS resources, such as EC2 instance IDs and security groups, on the Resources tab on the Stacks page.
    CFS_stack_resources.JPG

View deployed proxy

After the registration completes successfully, the Phoenix AWS proxy appears on the Phoenix AWS Proxies page. 

DR_Phoenix_AWS_Proxies_tab.PNG

  • Was this article helpful?