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
Performing the resync operation
When disaster strikes on a production data center, the takeover operation is invoked to start the resiliency groups on the recovery data center.
Since the production data center is not working, the data replication between the two sites does not happen. After the production site is back up and running, you need to prepare the production site for the next failover or for a migration operation. This preparation includes cleaning up any residue and resuming the replication from the recovery to the production site.
Use the Resync operation on the Resiliency Platform console to automate these steps for the required resiliency groups. This operation cleans up the residue which includes stopping applications and virtual machines, unregistering virtual machines, unmounting file systems, datastores, etc. If the recovery data center is Amazon Web Services, then the virtual machines are not unregistered.
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 proceed.
See Manually cleaning up virtual machines.
If the recovery data center is in cloud, and if while configuring the resiliency group for remote recovery, the Enable reverse replication option was selected, then do not run the Resync operation till the replication is complete and the state is IN Sync.
Performing the resync operation
- Navigate
Assets (navigation pane)
Resiliency Groups
- Double-click the resiliency group to view the details page. Click Resync.
- In the Resync panel, select the production data center name from the drop-down list, and click Next.
If the Resync 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.