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.
Windows Server 2012
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.
Paging files should be excluded from participating in replication, but no disks have been excluded.
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>
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.
Really? So no page file on the C drive? Which means if the VM bluescreens I get no crash dump? So I'm replicating the VM because it's an important VM, right? It's an important VM therefore if it crashes I need to be able to find out why (from the crash dump file). Except according to this I can't do that. Not good. Please (please!) correct me if I'm wrong...
This is mainly a concern if you replicating across a WAN as the page file will see significant changes while the data volumes may not. If you are on a LAN and bandwidth is not a problem leave your page file alone.