Overview
This article clarifies how changes made to the backup frequency interval within the Druva inSync client on an endpoint are recorded, even if not immediately updated in the inSync console's user interface.
Problem Description
When a user changes the backup frequency interval directly in the Druva inSync client, this change is not reflected in the inSync management console's UI.
Here is how the user may change the backup frequency once permitted from inSync user profile:
inSync client UI > Click on Settings and move the cursor as per the frequency needed:
Cause
This is by Druva inSync's design. The changes made by the user are user specific and are not visible on Admin UI.
Client-side interval changes are written locally to the inSync.cfg file on the user device.
The console reflects this change after the next backup, as the updated inSync.cfg is collected with logs.
For example, if a backup completes at 9:00 AM (4-hour interval), and the user changes it to 1 week at 9:15 AM, logs from the 9:00 AM backup show the old interval. Only after the next backup (based on the new interval) will the configuration reflect server-side.