Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager 19.12 Cloud Disaster Recovery User Guide

Deploy Cloud Disaster Recovery

The following procedure describes how to deploy Cloud Disaster Recovery in AWS and AWS GovCloud from the PowerProtect Data Manager UI.

Prerequisites

Ensure that you have:

  • An AWS or AWS GovCloud account that is configured before connecting to the cloud account
  • A PowerProtect DD system that is configured at the production site
  • Reviewed the prerequisite requirements for the cloud service that you are deploying. The latest prerequisites are listed in the Cloud Disaster Recovery Installation and Administration Guide.
  • Reviewed the requirements for managing access keys for IAM users as described in the AWS documentation.
  • A snapshot of PowerProtect Data Manager before configuring Cloud Disaster Recovery.

Steps

  1. From the PowerProtect Data Manager home page, select Infrastructure > Storage.
    The Storage page appears.
  2. In the Cloud Disaster Recovery tab, click Configure.
    A warning message is displayed with the information about the time that is taken to complete the deployment process.
  3. Click Yes to proceed with the deployment process.
    The Cloud DR initialization process starts.
  4. The Cloud Disaster Recovery wizard opens after the Cloud DR initialization process completes.
  5. In the Proxy Settings page, select the Connect to HTTP Proxy Server check box to configure a proxy server.
    Configuring a proxy server is optional.
    1. Enter the proxy host address and the port number in the respective fields.
    2. Select the Use user authentication (AWS) only check box. Enter the credentials for the proxy server in the respective fields.
      Skip this step if you do not want to enable user authentication for the proxy server.
    3. Click Connect to connect to the proxy server.
      Proxy server can be configured after deploying Cloud DR also.
  6. Click Next.
    The Cloud Account page is displayed.
  7. In the Cloud Account page, select AWS.
    The Enter AWS account credentials page appears.
  8. Specify the following fields in the Enter AWS account credentials page:
    • Access Key ID
    • Secret Key ID
    For more information about obtaining the access and secret keys for AWS users, see Managing Access Keys for IAM Users in AWS documentation.
  9. Click Show IAM Policy to view the Identity and Access Management policy that is required for Cloud DR implementation.
    The Define the AWS IAM policy section of Cloud Disaster Recovery Installation and Administration Guide provides instructions for creating an AWS policy that uses this IAM policy.
  10. Select Accept AWS Terms to accept the AWS marketplace terms, and click Connect.
    Cloud DR is connected to the AWS account.
  11. Click Next.
    The Cloud DR Targets page appears.
  12. Select the appropriate storage account from the Storage Account list.
    The cloud target contains the installation files and determines the region in which Cloud DR Server is deployed.
  13. Click Connect.
    The Cloud Networking page is displayed.
  14. Perform the following steps in the Cloud Networking page.
    1. Select Public Network or Private Network from the Network Selection list.
      If you deploy Cloud DR over a VPN, select Private Network.
      ppdm-cdrs-deployment_cloud_networking
    2. Select an appropriate VPC in the Select VPC list.
      If you are deploying Cloud DR over a VPN, select the existing VNET where the VPN gateway is located.
    3. Select an appropriate subnet for the VNET in the Select Subnet.
    4. Enter the CIDR range for the new subnet in the IPV4 CIDR Range section.
      NOTE
      • Before selecting an existing subnet, verify that the network security group that is assigned to the subnet allows inbound traffic for HTTPS port 443.
      • The CIDR range must comply with the Azure/Azure Government CIDR range limitations. Allowable range is between /16 and /27.
  15. Click Next.
    The Cloud Admin page is displayed.
  16. From the Specify Cloud Admin page, specify the following fields:
    1. Email Address
      Use this email address to recover forgotten password.
    2. Password
    3. Confirm Password
  17. Click Next.
    The Configure Cloud DR Server summary page appears.
  18. The Cloud Disaster Recovery Setting Information appears on the Storage page, and an informational dialog box confirms that Cloud DR server is deploying.
    1. To monitor the deployment from the Jobs page, click Go to Jobs.
    2. To monitor the deployment from the Storage page, click OK. When the deployment is complete, the public address of the Cloud DR Server hostname is displayed. If you want to open the Cloud DR Server UI in a new tab, click the server hostname link.
  19. Review the Cloud DR server details.
    1. To change the details of the Cloud DR server, click Back, and repeat the appropriate steps.
    2. To deploy Cloud DR in PowerProtect Data Manager, click Deploy Cloud DR Server.
    The deployment of Cloud DR Server to Cloud DR target begins. Deploying Cloud DR Server can take about 20 minutes.

Results

The Cloud Disaster Recovery Setting Information appears on the Storage page, and an informational dialog box confirms that Cloud DR server is deploying.
PPDM Cloud DR AWS Deployment

To monitor the deployment from the Jobs page, click Go to Jobs. To monitor the deployment from the Storage page, click OK. When the deployment is complete, the public address of the Cloud DR Server hostname is displayed. If you want to open the Cloud DR Server UI in a new tab, click the server hostname link.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\