Chat now with support
Chat with Support

Metalogix Replicator 7.4 - Reference Guide

Reference Guide
Metalogix Replicator Documentation Replicator Central Administration Configure Web Application Manage Replication Groups Manage Replication Connections Manage Classifications Manage Map Families
Actions Configure Map Family Configure Replication Map Settings Manage Map Family
Monitor Replicator About Metalogix Replicator Site Settings

Compression Settings


Compression settings allow Replication Packages to be reduced in size, if required. Reducing the size of Packages also reduces the amount of bandwidth required when sending them, but increases the amount of processor time and power required to process them, as they have to be shrunk and then expanded again.




Replication packages are compressed before they are sent in order to save bandwidth.


No data compression.

Differencing Compression (DC)

Differencing Compression (DC) allows data to be synchronized with a remote source using compression techniques to minimize bandwidth and network resources requirements. However, while it minimizes bandwidth usage, it requires the most CPU resources of all available methods.

DC is useful for moving data across a wide area network when the data transmission costs outweigh the costs of increased CPU processing for compressing and expanding the files. This is most useful when there is a large amount of data being transferred and the actual changes in the data are small.

DC works by creating a signature file on the Source Web Application then sending it to the Target Web Application. The Target Web Application then creates a signature file, compares the two files and sends a file back to the source telling the source what bits it needs from the file.

For example, a Word document is modified on the source by changing one word in the document after the signature comparison is complete. Only the part of the file that changes is replicated, resulting in significant bandwidth savings.

Note: DC requires the most CPU resources of these compression modes and increases the amount of time required to process packages.

Note: If the connection is in a direct group, then Remote Differential Compression (RDC) is used. If the connection is in an adaptive group, then Metalogix Dynamic Compression (MDC) is used. It is important to note that MDC depends on data found in the Packages Replicator Data folder. If the "retain completed packages for" section is set to a shorter period of time or if you manually clear packages on the Monitor Replication page, then you may end up removing packages used by MDC to reduce the total amount of transferred data. Metalogix recommends that if you are using MDC compression, you select a retention period long enough to maintain a complete history of packages and that you do not manually clear packages from the Monitor Replication page.

Note: To use DC, you must install Remote Differential Compression as a Windows feature on the servers where Replicator is installed before creating connections. When you create a connection, you will not be able to select this option. Instead, create the connection and then edit it again to configure DC.

DC Size Threshold

DC, if selected, will only be used for packages that are greater than the size specified in this field. Any packages that are smaller than this specified size will not be scanned for differentials, but replicated in entirety.

This parameter is measured in KB. The entry must be a positive decimal number.

Note: This number can only be adjusted if the compression mode is set to Differencing Compression (DC).

This size indicates the combined sizes of all files within a single replication package.

This setting is client-specific, and must be adjusted as required to find the best level for your organization.

BITS Transports Settings

This section controls BITS job priority settings, and compression type settings.



When BITS is set as the Transport method, priority levels can be assigned for the local network.

·BITS - High Priority
Uses as much bandwidth on the local network interface as it can.

·BITS - Normal Priority
Uses only the idle bandwidth on the local network interface. Normal Priority, transport settings can be further configured with the Windows Local Group Policy Editor (gpedit.msc). When using Normal Priority, transports will use the settings set in Group Policy editor for the server where the transfer is initiated.

This option determines whether or not BITS takes up a large amount of bandwidth when update downloads occur (high priority) or is relegated to a smaller amount of bandwidth (normal priority).

Note: The BITS priority setting only affects the local network interface, and does not affect BITS operation beyond the local server.

If a large quantity of replication is occurring, set the BITS mode to a lower priority in order to avoid interrupting or slowing regular network traffic.


This parameter specifies that the Kerberos network authentication protocol is to be used when communicating with the target Web Application.


Note: Kerberos is only available when Transport is set to BITS.

Related Documents