Skip to main content
Druva inSync : Fundamental prerequisites
Updated over a week ago


Configuring software involves setting up various elements and parameters to ensure that the software operates optimally within a given environment.

If not implemented correctly, there is a potential for encountering challenges during the backup/restore process, such as performance issues, backup inactivity, or interruptions in service.

Here are fundamental prerequisites that need to be configured for Druva inSync:


  • Network Essentials : Allowing Druva traffic

Network traffic encompasses all the communications and interactions that take place on a network between Druva cloud server and client machine, including the TCP 3-way handshake and other TCP packets like keep alive packets, SSL packets over TCP port 443 between computers and servers, routers.

It is crucial to white list Druva traffic to ensure seamless communication between the device and the cloud server.
Druva strongly advises white listing the domain * on TCP port 443 including TLS 1.2 protocol as a best practice, eliminating the need for separate white listing of individual IP addresses.

If you prefer opting for IP address white listing, Please contact Druva Support for the authorized list of IP addresses for white listing in your environment.

  • Security / DLP software exceptions
    In order to communicate or execute backup operations, the inSync client needs to uphold a continuous connection with the inSync cloud server, this leads to the continuous execution of services and processes in the system's memory throughout the machine's uptime

Antivirus programs keep an active handle on such applications that are present in the memory and interact with the operating system services.

It is crucial to specify exclusions for inSync processes and paths to ensure proper behaviour of the processes

Excluding Druva inSync processes:

Platform : Windows

πŸ“ Note
​inSync.exe, inSyncAgent.exe inSyncCPHwnet64.exe ,inSyncUSyncer.exe, inSyncUpgrade.exe

Platform: MAC

πŸ“ Note
​inSyncDecommission, inSync,inSyncUpgrade

Excluding Druva inSync paths :

Platform : Windows

πŸ“ Note
​C\ProgramData\Druva\inSync4C:\Program Files\Druva (For 32 bit machines)C:\Program Files (x86)\Druva (For 64 bit machines)

❗ Important

The path may change depending on the installation directory.

Platform: MAC

πŸ“ Note
​/Users//Library/Application Support/inSync/Users//inSync Share/Data/Application/druva/insync/contents/resources/insync/contents.MacOS

The exclusions can be added based on any of the below parameter:

  1. Hash value
    You can retrieve the hash value using below powershell command on windows
    >Get-FileHash <File path>/file name
    On MAC
    >sha1sum <filename>

  2. Path, path + subfolders

  3. File type

  4. File name ( Executable file name)

  • Resources on the device

We must recognize that there are constraints on the resources available to the device and There is a cap on the extent to which we can utilise the resources on the machine.

You can fine-tune the resources for optimal efficiency.

CPU Priority:

Druva provides the option to define a maximum limit for CPU utilisation during the backup.
The limit you establish will determine the extent to which the CPU is allowed to be involved in the backup process, directly influencing the duration of the backup.

To configure the CPU priority, please refer Assigning CPU Priority


Network bandwidth refers to the maximum rate of data transfer across a network over a specific communication link. Bandwidth is a critical factor in determining the speed and capacity of data transmission between devices or systems connected to a network.

To configure the network bandwidth, please refer Set bandwidth for device backups

Did this answer your question?