Skip to main content



How can we help you?


Druva Documentation

Why does an inSync Server have multiple instances of inSyncWorker.exe?

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

This article discusses the inSyncWorker.exe process and the reason multiple instances of it are running on the inSync server.

About inSyncWorker.exe

Druva inSync Server has a multi-process architecture. It serves multiple clients at the same time by creating many inSyncWorker.exe processes to perform multiple simultaneous backup and restore related operations.

Multiple instances

An 'inSyncWorker.exe*' process is spawned to serve an incoming client sync or restore request. Once the request is completed the inSyncWorker.exe is not killed, but it is made available to next sync or restore request.

Some instances of inSyncworker.exe are initiated at the time of inSync server startup and are always alive.

Note: There is an upper limit on the number of inSyncWorker.exe instances that can run per storage and it is limited to the maximum number of parallel connections to the storage.

  • Was this article helpful?