Hyper-V: Virtual Hard Disks with Paging Files Should be Excluded from Replication

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.

Note: The following sections provide details about the specific issue. Italics indicates UI text that appears in the Best Practices Analyzer tool for the specific issue.

Issue

Paging files should be excluded from participating in replication, but no disks have been excluded.

Impact

Paging files experience a high volume of input/output activity, which will unnecessarily require much greater resources to participate in replication. This impacts the following virtual machines: <list of virtual machines>

Resolution

If you have not already done so, create a separate virtual hard disk for the Windows paging file. If initial replication has already been completed, use Hyper-V Manager to remove replication. Then, configure replication again and exclude the virtual hard disk with the paging file from replication.

Additional references