Veritas™ Resiliency Platform 2.2 Solutions for Microsoft Hyper-V
- Section I. Overview of Resiliency Platform
- Section II. Preparing your environment
- Using array-based replication
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Section IV. Managing disaster recovery
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activites
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
Prerequisites for configuring Hyper-V virtual machines for disaster recovery
Before you run the wizard to configure disaster recovery protection for a resiliency group of Hyper-V virtual machines, ensure that you have met the following prerequisites for virtual machine configuration:
The virtualization servers for the virtual machines must be added to Resiliency Platform at the production and recovery data center.
For more information on adding asset infrastructure, refer to the Deployment Guide.
The virtual machines, that you use to create the resiliency group, should be online on one of the data centers (production or recovery). But the replication disk should be attached to both the data centers.
If you add new disks, ensure that they are visible from the guest operating system.
Ensure that the integrations services are installed and running inside the virtual machines.
Ensure that you have disabled the 'Quick removal' policy for disks in Windows Server 2008 R2 and disabled the 'write-cache' policy for disks in Windows Server 2012 R2.
If you want to do IP customization, ensure that the Hyper-V virtual machines are updated with the latest Hyper-V integration services.
Additional prerequisites for the virtualization environment depend on the type of replication you are using.
For array based replication see See Protecting Hyper-V virtual machines using array-based replication - an overview.
For recovery on Amazon Web Services
The Paravirtual (PV) Drivers must be installed. Follow the documentation of AWS for more information.
Ensure that the Replication Gateways have sufficient storage to handle the replication for the planned number of protected virtual machines.
Both the on-premises gateway and the cloud gateway must have external storage equivalent to 12GB for each asset protected by the gateway pair. For example, if a gateway pair supports 10 virtual machines, the on-premises gateway and the cloud gateway must each have 120 GB of external storage.
A maximum of 40 volumes or disks can be attached to the cloud Replication Gateway.
On Windows hosts, initialize and reboot the disks that are attached to IDE controller.
A bucket must be created in S3 and a policy must be created that assigns the following permissions:
s3:GetBucketLocation and s3:GetObject permissions on the bucket
ec2:ImportSnapshot, ec2:DescribeSnapshot, and ec2:CopySnapshot permissions on all the resources
One role named ImportSnapshotRole must be created and the above policy is associated with this role. The service vmie.amazonaws.com should be able to assume this Role.
For more information about the permissions required, refer to the AWS documentation.