Overview
To deliver a consistent reliable backup experience, the inSync Client’s resilient capabilities now proactively monitor inSync Client health and automatically recover from rare situations where the application may become unresponsive or is not able to connect to Druva Cloud.
This function operates silently in the background, requiring no user intervention, thereby ensuring your backups remain on schedule and your data stays protected.
How it Works
Continuous Monitoring
The inSync Client agent now actively watches for signs of something unusual , including:
Connection health
Detects the state of inactive connection and restarts itself to re-establish connection if required.Backup activity health
Ensures the backup processes remain responsive and don’t get stuck.
Automatic Recovery- Without Disruption
If an issue related to connectivity or backup is detected, the inSync Client can automatically take corrective action to restore normal operation.
Recovery workflow
To avoid unnecessary restarts, recovery is only evaluated after the device has been running steadily for several days. From there, recovery may occur if:
inSync Client is not connected to Druva Cloud for several days (typically last 3 days),
ORNo Backup activity is detected by Druva Cloud for several days (typically last 5 days).
A short waiting period is built in to ensure the inSync Client doesn’t react prematurely.
Example Based Scenario
Scenario 1: Consider a device with the inSync Client that has been offline for 5 days. The client first evaluates network connectivity over the last 3 days and automatically restarts without interrupting the user's ongoing tasks.
Scenario 2: If the inSync client is connected to the cloud, however no file sync has happened in the last 5 days, the application reboots. This restart is performed to recover from any missed backup events caused by unexpected interruptions.
📝 Note
inSync client does not currently support automatic recovery from system-specific configuration changes that may impact backup operations.