Hyper-V: Resynchronization of replication should be scheduled for off-peak hours
This article is intended to provide more information about a specific issue that can be identified by running a Best Practices Analyzer scan for Hyper-V. It also can be used without running a scan, as general troubleshooting and best practice information to help you configure your server appropriately. If you have troubleshooting steps or information that would improve this article, please add it. For instructions on how to edit a TechNet Wiki article, see Wiki: How to Use the Editor.
For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.
Operating System |
Windows Server 2012 |
Product/Feature |
Hyper-V |
Severity |
|
Category |
Note: The following sections provide details about the specific issue. Italics indicate UI text that appears in the Best Practices Analyzer tool for the specific issue.
Issue
Resynchronization of replication for the primary virtual machines is not scheduled for off-peak hours.
Impact
The longer a virtual machine is in a state requiring resynchronization, the longer the replication log files grow and the more unreplicated changes occur on the primary virtual machines. This impacts the following virtual machines: <list of virtual machines>
Resolution
Use Hyper-V Manager to modify the replication settings for the virtual machine to perform resynchronization automatically during off-peak hours.
Additional references