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
- Protecting Hyper-V virtual machines using array-based replication - an overview
- Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
- Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
- Configuring Hyper-V virtual machines for disaster recovery using EMC RecoverPoint
- Configuring Hyper-V virtual machines for disaster recovery using Hitachi TrueCopy Universal Replicator
- Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
- Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
- Configuring Hyper-V virtual machines for disaster recovery using IBM XIV Remote Mirror
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Understanding the role of resiliency groups in disaster recovery operations
- How Resiliency Platform configures disaster recovery protection for virtual machines
- Prerequisites for configuring Hyper-V virtual machines for disaster recovery
- Limitations for virtual machine disaster recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing virtual machines for remote recovery (DR) in vCloud
- Section IV. Managing disaster recovery
- Managing resiliency plans
- About resiliency plans
- Creating a new resiliency plan template
- Editing a resiliency plan template
- Deleting a resiliency plan template
- Viewing a resiliency plan template
- Creating a new resiliency plan
- Editing a resiliency plan
- Deleting a resiliency plan
- Executing a resiliency plan
- Viewing a resiliency plan
- Creating a schedule for a resiliency plan
- Editing a schedule for a resiliency plan
- Deleting a schedule for a resiliency plan
- Viewing a schedule for a resiliency plan
- Monitoring risks, reports, and activites
- About the Resiliency Platform Dashboard
- Understanding asset types
- Displaying an overview of your assets
- About risk insight
- Displaying risk information
- Predefined risks in Resiliency Platform
- Viewing the current risk report
- Viewing the historical risk report
- Viewing reports
- Managing activities
- Viewing activities
- Aborting a running activity
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
- Glossary
Taking over a resiliency group of virtual machines
Takeover is an activity initiated by a user when the production data center is down due to a natural calamity or other disaster, and the virtual machines need to be restored at the recovery data center to provide business continuity. The user starts the virtual machines at the recovery data center with the available data. Since it is an unplanned event, the data available at the recovery data center may not be up to date. You need to evaluate the tolerable limit of data loss, and accordingly take the necessary action - start the virtual machines with the available data, or first use any other available data backup mechanism to get the latest copy of data, and thereafter start the virtual machines. The takeover operation brings up the virtual machines at the recovery data center using the last available data.
Perform the resync operation after successful completion of takeover operation.
If the recovery data center is in cloud, then takeover operation from cloud data center to production (on-premises) data center is not supported.
To perform takeover operation on virtual machines
- Prerequisites
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 between the production and recovery data center is complete.
- Navigate
Assets (navigation pane)
Resiliency Groups
- Double-click the resiliency group to view the details page. Click Takeover.
- Select the target data center and click Next.
If the Takeover 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.