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
Migrating a resiliency group of virtual machines
Migration refers to a planned activity involving graceful shutdown of virtual machines at the production data center and starting them at the recovery data center. In this process, replication ensures that consistent virtual machine data is made available at the recovery data center. In Veritas Resiliency Platform, the migration of virtual machines is achieved by grouping them in a resiliency group, configuring disaster recovery for the resiliency group, and thereafter performing the migrate operation on this resiliency group.
If you perform the takeover operation, then you must perform the resync operation before you migrate back to the production data center.
If the Enable reverse replication option is not selected while configuring for remote recovery, then you need to run the Resync operation before migrating the virtual machines back to the production data center.
See Performing the resync operation.
If the recovery data center is AWS cloud, then before you migrate from the cloud data center to the on-premises data center, you need to reboot and then refresh the virtual machine in the cloud.
To migrate virtual machines
Ensure that the replication is in Active state and the data is consistent.
It is recommended to stop or disable NetworkManager on RHEL hosts having multiple NICs.
For Hyper-V virtual machines, ensure that the network mapping of all the required virtual switches across the data centers is complete.
See Setting up network mapping between production and recovery data centers.
If the recovery data center is in AWS, then ensure that the network mapping of all the required subnets across the data centers is complete.
- Navigate
Assets (navigation pane)
Resiliency Groups
- Double-click the resiliency group to view the details page. Click Migrate.
- Select the target data center and click Next.
If the Migrate operation fails, check
to know the reason and fix it. You can then launch the operation. The operation restarts the migrate workflow, it skips the steps that were successfully completed and retries those that had failed.Do not restart the workflow service while any workflow is in running state, otherwise the
operation may not work as expected.