The User Backup Inactivity alert appears only in the inSync Management Console. inSync generates this alert when a user has not completed a backup from their device within the period defined in the inSync profile associated with that user.

An inSync administrator sets this period at the profile level, under General > Backup Inactivity Alert in the profile summary. Administrators can change this value at any time.

This alert helps an administrator quickly identify how many users have not completed a backup within the period configured for their profile.

Administrators can also configure an email notification so that affected users are alerted directly. This is configured separately from the alert itself, under Alerts -> Settings in the inSync Management Console.

📝 Note

Backup inactivity alerts are configured only at the user level and cannot be customized for individual workloads.

By default, the User Backup Inactivity alert is visible only in the inSync Management Console. To also notify affected users by email, complete the following steps.

4. Clear the Notify User checkbox if you do not want to notify users by email.

For more information, see Configure Alert Settings for Endpoints and SaaS Apps and Manage SaaS Apps and Endpoints Alerts.

The alert clears automatically once the affected user's device completes a backup successfully. Complete the following steps in order they are sequenced from least to most disruptive until the backup succeeds.

2. Confirm the user's status is not Preserved and that the device associated with the user is not Disabled.

For steps, see Activate users and Disable, enable or delete a user device.

📝 Note

After you enable a device, the inSync Client can take up to 30 minutes to perform the manual backup, scheduled backup, restore, auto-upgrade, decommission, and sync operations.

3. Confirm the user has a device associated with their account. An administrator may have deleted the device by mistake. Click Users in the inSync Management Console to open the Manage Users page.

If the user has no associated devices, check the administrator Audit Trails for more detail. To view the Audit trails for administrators, refer to the View Admin Audit Trails page.

If the issue persists, continue to the next step.

4. Confirm the inSync Client is still installed on the user's device. Users sometimes remove the inSync Client without realizing what it is.

If it is not installed, install and activate it.

If the inSync Client is already installed and activated, start a backup and check how it performs.

5. Confirm the Druva inSync Client Service is running. Open services.msc to check its status.

If the service is already running, restart it: stop Druva inSync Client Service, end all inSync processes in Task Manager, then start Druva inSync Client Service again. Start a backup afterward and check the result.

⚠️Warning

Stopping the Druva inSync Client Service and ending inSync processes will interrupt any backup currently in progress on that device. Confirm no backup is actively running before you restart the service, or be prepared to restart the backup afterward.

6. Confirm antivirus exclusions are configured correctly and are not interfering with inSync processes on the device. See Antivirus recommendations for inSync/Endpoint Client.

7. If the backup still fails, review the inSync Client logs on the device to identify the cause.
​

Log file locations:

For more information, see View backup and restore logs.

8. Use the error text in the logs to identify the specific cause and resolve it.

📝 Note

inSync Client can generate a range of different errors. The troubleshooting steps needed depend on the specific error shown in the logs.

If none of the above steps resolve the issue, contact Druva Support for further assistance.