Skip to main content
Network parameter reference
Updated over a week ago


Druva does not recommend and/or mandate changing the environment to comply with the parameter values specified in this article. Instead, the objective is to help you to obtain optimal functionality from the application in the most efficient manner possible. inSync does not govern these values, as these are set at the RPC level of the TCP/IP stack of the application and hence handled by the underlying stack.

You can use these values as a reference to achieve your expected network performance or to handle possible environmental issues regarding backups and restores.

Network parameter reference values




Maximum permitted MTU size

1500 bytes

Default limit

Minimum permitted MTU size

576 bytes for IPv4
1289 bytes for IPv6

Recommended MTU size

1460 bytes with 20 bytes for TCP Header and 20 bytes for IP Header for a total of 1500 bytes

Maximum permitted Jitter

Since Jitter may adversely impact an application performance, Druva recommends no or minimal Jitter in the environment.

What is Jitter?
Jitter in IP networks is the variation in the latency on a packet flow between the two systems, when some packets take longer to travel from one system to the other.

What causes Jitter?
Jitter results from network congestion, timing drift and route changes.

Why is Jitter problematic?

  • Jitter is especially problematic in real-time communications like IP telephony and video conferencing.

  • It is also a serious problem for hosted desktops and virtual desktop infrastructure (VDI).

  • Jitter can lead to audio and video artifacts (unintended deviation or inconsistency) that degrade the quality of communications.

TCP window sizing for WIN10 / WIN7 desktop machines

Less than 4 MB

This is best handled by the underlying operating system and is not a function of the inSync.

Maximum permitted size of file transfer

Optimal restore speed depends on the data set, as there is no specific number. Observations have revealed the restore speed in the range of 20 GB/Hr to 100 GB/hr depending on file sizes, file types and more.

The backups are observed to be optimal at 100 GB/hr for file sizes between 1 MB to 4 MB. The performance is suboptimal for other extremes of file sizes.

Network latency requirements

Minimum latency

0 ms

Maximum latency

40 ms

Recommended permissible latency

20 ms

For best performance, lesser latency the better.

💡 Tip

Druva does not have a reference document for network parameter values as it is handled by the underlying OSI stack at the RPC level for the inSync application.

Did this answer your question?