Overview
Antivirus and third-party encryption software can interfere with inSync operations by locking active files and folders during real-time or on-access scans. This interference may cause:
Configuration file corruption
Unexpected application behavior
Local database corruption
Loss of data references
To prevent these issues, Druva strongly recommends adding exclusions for inSync application files, folders, and processes in your antivirus configuration.
Why Exclusions Are Critical
File Locking Issues
Antivirus software frequently locks files during scanning
Locked database files prevent inSync from updating references
This can lead to data corruption and sync failures
False Positive Detection
Antivirus may quarantine or delete frequently accessed inSync files
Database and log files are often flagged as suspicious due to high activity
Antivirus Exclusion Configurations
For inSync Cloud (AD Connector)
AD Connector Server Exclusions
Folders to Exclude:
C:\Program Files\Druva\
C:\ProgramData\Druva\
C:\Windows\Temp\Druva\
[Custom installation directory if different]
Processes to Exclude:
ADConnector.exe
For inSync Client (Version 7.2.0 and Later)
Windows Client
Folders to Exclude:
C:\Program Files\Druva\inSync\
C:\Program Files (x86)\Druva\inSync\
C:\ProgramData\Druva\inSync\
%USERPROFILE%\AppData\Local\Druva\inSync\
%USERPROFILE%\AppData\Roaming\Druva\inSync\
Processes to Exclude:
inSync.exe
inSyncAgent.exe
inSyncCPHwnet64.exe
inSyncUpgrade.exe
inSyncUsyncer.exe
inSyncDataplane.exe
Process Locations:
C:\Program Files\Druva\inSync\X.X.X\amd64\ (where X.X.X is the version number)C:\Program Files (x86)\Druva\inSync\X.X.X\amd64\ (for 32-bit installations)
macOS Client
Folders to Exclude:
~/Library/Application Support/inSync/
~/Library/Preferences/com.druva.insync.plist
/var/log/inSync
Processes to Exclude:
inSync
inSyncDecommission
inSyncUpgradeDaemon
inSyncUpgrade
Process Locations:
/Applications/Druva inSync.app/Contents/MacOS/
Note: These processes are hidden by default. Use ps -ef | grep -i inSync
in Terminal to view them.
Linux Client
Folders to Exclude:
/opt/Druva/
/home/<username>/.inSync/
Note: Replace <username> with the actual username for user-specific paths.
Processes to Exclude:
inSync
Implementation Steps
Access your antivirus console or settings panel
Navigate to exclusions/exceptions settings
Add folder exclusions using the paths listed above for your platform
Add process exclusions for the specified executables
Save and apply the configuration
Restart inSync services if necessary
Verify exclusions are working by monitoring inSync logs for antivirus-related errors
Troubleshooting
Common Issues and Solutions
Q: inSync is still experiencing issues after adding exclusions. What's next?
Verify all paths and processes are correctly excluded
Check if your antivirus has separate real-time and scheduled scan exclusions
Ensure exclusions apply to all scan types (real-time, full system, custom scans)
Review inSync logs for specific error messages
Contact Druva support with log details
Q: How do I know if antivirus interference is affecting inSync?
A: Look for these indicators:
Sync failures or delays
inSync services are failing to start
Antivirus alerts about inSync processes
Best Practices
Configure exclusions before installing inSync to prevent initial conflicts
Apply exclusions to both real-time and scheduled scans
Regularly review and update exclusions when upgrading inSync versions
Document your exclusion settings for future reference
Test backup and restore operations after implementing exclusions
Monitor inSync performance to ensure exclusions are effective