Recovering virtual machines from VMware to AWS using NetBackup Image Sharing
Using the Resiliency Platform, you can recover VMware virtual machine from NetBackup generated backup images that are stored into AWS S3 buckets to the AWS cloud target data center.
In figure the on-premises data center is the source data center and the target data center is an AWS cloud region. The Infrastructure Management Server (IMS) in the on-premises data center discovers the vCenter server and the backup configuration from the NetBackup primary server. NetBackup with the Image Sharing feature, which is available from NetBackup version 8.2 onwards, backs up the virtual machine images along with the image metadata from the on-premise data center into the designated S3 bucket.
For backing up the data in AWS S3 bucket, either NetBackup CloudCatalyst or MSDP-C configuration can be used.
The recovery using these backup images is achieved using a NetBackup Cloud Recovery Server (CRS) virtual appliance that is deployed in the cloud data center. The image metadata stored in the S3 bucket allows the NetBackup CRS to read the image information and create an Amazon Machine Image (AMI). This AMI is then used to provision cloud instances in the cloud data center during the recover operation.
The following table provides the summary of deployment, configuration, and recovery of virtual machines to cloud using NetBackup generated backup images that are stored in S3 bucket using the Image Sharing feature.
Table: Recovering virtual machines using NetBackup images
Tasks | More information |
|---|---|
Plan your environment | Refer to the Veritas Resiliency Platform Overview and Planning Guide to know about the product, its components, features, and capabilities. Refer to the Veritas Resiliency Platform Release Notes for release information such as main features, known issues, and limitations. Ensure that the configuration details in your environment match the requirements mentioned in the checklist. Checklist for recovery of VMware virtual machines to AWS cloud using NetBackup |
Deploy and configure the virtual appliances | Veritas Resiliency Platform is deployed as virtual appliances. Download and deploy the virtual appliances for Resiliency Manager and IMS in both the data centers.
For more information on CRS, refer to About Image Sharing using MSDP cloud topic in NetBackup Deduplication Guide. |
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.
|
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 VMware 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 recovery on local or remote data center. |
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 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 recover (local or remote) operations on the resiliency groups. Note: The rehearsal operation is not supported from AWS to VMware. |
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. |
