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
Manually cleaning up virtual machines
In Microsoft Failover Cluster environments, the Resync operation may fail in the first step to cleanup the virtual machine residue. You can manually cleanup the virtual machine residue and re-initiate the Resync operation.
To manually cleanup virtual machines
- Logon into the Hypervisor console.
- Open the Failover Cluster Manager snap-in.
- Select Roles in the tree view.
- Select the appropriate virtual machine resources that were configured to the resiliency group on which you want to perform the Resync operation.
Remove the Resources.
- Open Hyper-V Manager and delete the virtual machines that were added to the Resiliency Group on which you want to perform the Resync operation.