Please enter search query.
Search <book_title>...
Veritas™ Resiliency Platform 2.2 Solutions for Microsoft Hyper-V
Last Published:
2017-04-07
Product(s):
Resiliency Platform & CloudMobility (2.2)
- 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
Limitations for virtual machine disaster recovery
The following table lists the limitations of virtual machines disaster recovery using Resiliency Platform:
Table:
Limitations | Descriptions |
---|---|
Replication limitations | For more information on replication-based limitations of virtual machines, refer to the Hardware and Software Compatibility List (HSCL). |
The hypervisor should not be added as a host in certain environments | If the applications are installed inside virtual machines running on Microsoft Hyper V technology and the applications are having data that is replicated using EMC SRDF, and these applications are to be configured for DR, then you should not add the hypervisor itself as a host to the IMS. |