The replication health will also show this message: At the same time, HVR stops tracking the guest writes for the VM and nothing is replicated. When the VM enters the “Resynchronization Required” state, the replication health becomes “Critical” and the VM is scheduled for resynchronization. Reverting volume to an older point in time using Volume backup and restore. Importing an older VM copy, when migration by using export-import Restoring a backed-up copy of the Replica VM Out-of-sequence or Invalid log file is applied Reverting the volume to an older point in time Tracking log file is not closed gracefully VHD and logs are on SMB and connectivity to the SMB storage is flaky. Size of tracking log files > 50% of total VHD size for a VM Mount/modify VHD outside the VM, Edit disk, Offline patching The VM enters the “Resynchronization Required” state when any one of the conditions are encountered: Site In fact, in the normal course of replication this is quite a rare event. It would become quite obvious after going through this table below that Resync is not expected to occur regularly. (NOTE: In this post we will use a VM named “RESYNC VM” in all examples and screenshots.) When does resynchronization happen? Resynchronization (or Resync) is the process of re-establishing the baseline – by ensuring that the primary and replica VHDs have exactly the same data stored. Thus in a rainy day scenario (details in following section), when HVR determines that the replica VM can no longer be kept in sync with the primary by applying the replicated changes then resynchronization is required. However, due to factors beyond the control of the administrator – such as faulty hardware and OS bugchecks – it is possible that the primary and Replica VMs are not in sync. This is achieved through the process of initial replication, and establishes a baseline on which replicated changes can be applied. To begin with, Hyper-V Replica (HVR) requires that the data on the virtual hard disks (VHDs) of the primary and replica VMs be the same. Hyper-V Replica runs 24 hours, 365 days in a year for any VM that has been enabled for replication it ensures that the data on the primary site and the Replica site are kept as closely in sync as supported. Hyper-V Replica provides protection to VMs by tracking and replicating changes to the virtual hard disks (VHDs) of the VM. Feedback In this article What is resynchronization and why is it needed?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |