Hyper-V: Compression is recommended for replication traffic

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 indicates UI text that appears in the Best Practices Analyzer tool for the specific issue.

Issue

The replication traffic sent across the network from the primary server to the Replica server is uncompressed.

Impact

Replication traffic will use more bandwidth than necessary. This impacts the following virtual machines: <list of virtual machines>

Resolution

Configure Hyper-V Replica to compress the data transmitted over the network in the settings for the virtual machine in Hyper-V Manager. You can also use tools outside of Hyper-V to perform compression.

Additional references