> Software > Secure > Auto Recovery > Virtual Machines > Planning > Hypervisor Configuration Requirements > Amazon Web Services > Configure replication for AWS

Configure a periodic replication group for Amazon Web Services

A periodic replication group creates new backups on a schedule and replicates virtual machines to an Amazon Web Services (AWS) target site based on the selected recovery point objective (RPO) for cyber resilience and disaster recovery.

Prerequisites

Configure a replication target for Amazon Web Services

Start the configuration wizard

  1. From the Command Center navigation pane, go to Auto recovery > Replication groups.

  2. On the upper-right area of the page, click Add.

  3. On Select Workload Type, select Virtual machines, and then click Next.

  4. From the Production site hypervisor vendor list and the Recovery site hypervisor vendor list, select Amazon Web Services, and then click Next.

  5. On Select Replication Type, select Periodic replication, and then click Next.

Provide general information

  1. In Replication group name, enter a name for the replication group.

  2. From the Production site hypervisor list, select the source hypervisor or create a new hypervisor.

  3. Click Next.

Select content to replicate

  1. On the upper-right area of the page, click Add.

  2. From the Browse and select VMs list, select one of the following:

    • By region: Select instances based on the region that they reside in.

    • By zone: Select instances based on the zone that they reside in.

    • By tags: Select instances based on tags that are assigned to them.

    • By instance type: Select instances based on their type, such as t2.micro or c5.large.

  3. To view by instance ID, enable Show instance ID toggle.

  4. Select the VMs or instances to include in the replication group, and then click Add.

  5. Click Next.

Select storage copies

  1. From the Primary copy list, select the primary copy to use.

  2. Optional: To add a secondary copy, click Add copy, and then from the Secondary copy list, select the secondary copy to use.

  3. From the Select the copy for replication list, select the copy to use for replication.

  4. Click Next.

Configure replication options

  1. From the Target list, select an existing replication target or create a new target.

  2. In Replication runs every, enter the replication interval.

  3. From the Period list, select the time unit.

  4. Under Recovery time objective (RTO), select the replication mode:

    • Warm site replication: The data is replicated and VMs are deployed to the target during failover to optimize cost.

    • Hot site replication: The data is replicated to the target immediately after group creation to minimize RTO. The VMs are deployed during failover.

  5. The Enable replication immediately after group creation toggle is enabled by default. Disable it if you don’t want replication to start immediately. This option applies only to hot site replication.

  6. Click Next.

Configure pre- and post-scripts (optional)

  1. If you want to run pre- and post-scripts before and after failover or failback, configure the scripts on this page.

  2. In the row of the script, click Edit edit button outline grey/gray pencil.

  3. In Path, enter the location of the script file.

  4. From the Credential list, select the credential for the UNC network.

  5. Click Save.

  6. Click Next.

Configure override options (optional)

Use override options when a specific VM needs different recovery site settings than the replication target defaults.

  1. Select the VM, click the action button action button, and then select Override replication options.

  2. Update the settings you need, and then click Save.

  3. Click Next.

Configure advanced options (optional)

  1. Enable the Unconditionally overwrite if VM already exists toggle to replace existing instances at the destination.

    Auto recovery operations from incremental backups are not affected by this setting. Subsequent incremental backups and auto recovery updates are applied to the destination instance without overwriting the instance. If the destination instance is currently running, the auto recovery operation fails.

  2. Enable the Continue to next priority on failure toggle to continue with the next priority instance if one fails.

  3. In Failover delay between different priority VMs (in mins), enter the delay time.

  4. From the Transport mode list, select any of the following:

    • Automatic (default): This option selects the best transport mode for your environment and the type of operation that you're performing.

    • Commvault HotAdd: Used for replication and failover operations to AWS when the access node and destination are in the same zone.

    • Amazon EBS direct: Used for cross-zone and cross-region full VM replication and failover operations and attach disk operations by using the EBS Direct API.

    • AWS VM Import/Export: Used for cross-region VM conversions.

  5. Click Next.

Summary

  1. Review the settings, and then click Submit.
×

Loading...