Recovering virtual machines from AWS region to AWS region
Using Veritas Resiliency Platform, you can configure and protect your virtual machines for recovery from AWS region to AWS region highlights these features:
Deploy the VSA's in both AWS region using AWS Marketplace CloudFormation templates.
Real time updates related to network and virtual machines support is enabled for the virtual machines which are present on the target data center.
Edit the migrated virtual machine, add/ remove the virtual machine from a resiliency group on the target data center.
Rehearsal operation is enabled when target data center is AWS and vice versa.
Enable or disable IP customization on both source and target data center.
The following table provides the summary for deployment, configuration, and recovery of virtual machines from AWS region to AWS region.
Table: Recovering virtual machines from AWS region to AWS region
Tasks | More information |
|---|---|
Plan your environment | Refer to the Overview and Planning Guide to know about the product, its components, features, and capabilities. Refer to the Release Notes for release information such as main features, known issues, and limitations. Ensure that the configuration details in your environment are compatible with the requirements mentioned in the checklist. Checklist for deployment and disaster recovery configuration |
Deploy and configure the virtual appliances | Veritas Resiliency Platform is deployed as virtual appliances. Download and deploy the virtual appliances in the AWS cloud data center as well as in the premises data center. Refer to the following topics: Download the files required for deployment Deploy the Resiliency Platform components in AWS Through AWS marketplace using CloudFormation templates Deploy the virtual appliances for one or more IMS and Replication Gateway in the premises data center Configure the virtual appliances as Veritas Resiliency Platform components About configuring the virtual appliances Prerequisites for configuring Resiliency Platform components |
Set up the resiliency domain | Set up the infrastructure and basic settings of the Veritas Resiliency Platform resiliency domain. These tasks are performed after you configure the Resiliency Manager and log in to the web console. Refer to the following topics: Getting started with a new Resiliency Platform configuration Configure the settings for the resiliency domain: Adding AWS cloud data center (if not done during getting started wizard) |
Add asset infrastructure | Before you can monitor and manage data center assets from the console, you must add the asset infrastructure to Veritas Resiliency Platform. The IMS then discovers the asset information for monitoring and operations in the console. |
Infrastructure Pairing | For recovering assets to AWS you have to do following infrastructure pairing:
|
Create resiliency groups | After adding the assets to Resiliency Platform, you organize the related assets into a resiliency group that you can protect and manage as a single entity. You can create a resiliency group either for basic monitoring (start or stop virtual machines) or for remote recovery. |
Advanced features | Virtual business services, resiliency plans, and evacuation plans are some of the features of Veritas Resiliency Platform that you can additionally use to customize the process of recovery of your assets. |
Perform remote recovery operations | Once you have configured the resiliency groups for remote recovery, you can perform rehearsal and cleanup rehearsal operations on the resiliency groups. You can also perform migrate, recover, or resync operations on the resiliency groups. |
Monitor assets | You can monitor risks to the recoverability or continuity of your protected assets. Run various reports to view the status of the assets in your data center. And view details about operations such as the status (in-progress, finished, or failed), start and end time, and the objects on which the operation was performed on the Activities page. |
Miscellaneous references | After the virtual appliances are deployed and configured, you are given limited menu-based access to the operating system and the product. You need to use klish menu to manage the configuration-related changes to the product and to troubleshoot. You can also use klish to update Resiliency Platform components. |
