Managing virtual machines for remote recovery (DR) in Amazon Web Services
Using the Resiliency Platform console, you can organize virtual machines into a resiliency group, apply the remote recovery for hosts service objective, and configure them for remote recovery in Amazon Web Services (AWS). From version 3.5, Resiliency Platform now supports ENA instance type for the workloads.
The wizard prompts for the inputs that are needed for the selected service objective and replication technology.
To manage virtual machines for remote recovery in AWS
- Prerequisites
See Prerequisites for configuring VMware virtual machines for recovery to AWS.
See Prerequisites for configuring Hyper-V virtual machines for recovery to AWS.
- Navigate
Assets (navigation pane) > Resiliency Group(s) tab > Manage & Monitor Assets
You can also launch the wizard from the Unmanaged or Overview tabs.
- Select the assets:
Select Host as the asset type, select the data center, and select other filters as needed to display a list of virtual machines.
Drag and drop virtual machines to Selected Assets.
For resiliency group consisting of VMware virtual machines, ensure that each resiliency group is mapped to only one ESX cluster.
- The next page displays the environment for the selected assets.
- The next page lists the service objectives that are available for the selected asset type. You can expand the service objective to view details. Select the service objective that provides disaster recovery operations.
- Select the target (recovery) data center.
- Select the Replication Gateway pairs.
- Select the volume type.
- In the Confirm Resiliency Platform Data Mover Details panel, verify the replication gateway pair selection and the asset information.
You can choose to Enable reverse replication after performing migrate operation on this page.
- Complete the customization for AWS.
See AWS Customization options panel.
About Elastic Networking Adapter (ENA) support in Resiliency Platform
- View the network summary. Expand a virtual machine to view additional information about the source and target networks.
- Complete the network customization steps for the virtualization technology.
- Use the Customize System Generated Workflows panel to enable manual intervention at predefined points during the Migrate and Recover operations on both the data centers. This is an optional step.
- Verify the summarized information and enter a name for the resiliency group.
Note:
After configuring the virtual machines for disaster recovery, do not rename the datastores.
If you rename, See Troubleshooting: If datastores are renamed.
When you finish the wizard steps, Resiliency Platform invokes a workflow which initializes the DR configuration. You can view the progress or ensure that this operation is successfully completed on the Activities page.
See Viewing activities.
Verify that the new resiliency group is added to the Resiliency Groups tab.
See Viewing resiliency group details.
When you have added a new data disk or removed a data disk from the virtual machine, it may happen that the data does not remain consistent on source and target data center. Hence, it is recommended to first place the resiliency group in maintenance mode, edit the desired changes and exit the maintenance mode.
See Editing a resiliency group in maintenance mode. for more details.
See Placing a resiliency group in maintenance mode. for more details.
If the operation fails and you want to delete the resiliency groups, and while deleting the resiliency group if you face any issues, you need to perform manual cleanup steps.See Troubleshooting: Delete resiliency group operation.
More Information