Overview
When restoring data from the Druva Browser interface, users may observe that the backup size displayed in the Druva Console appears significantly larger than the actual size of files downloaded during restore.
Problem Description
Users performing a restore operation via the Druva Console or Browser interface might notice the following behavior:
Backup Size in Druva Console: Large (includes multiple backup components).
Actual Restored Data Size: Noticeably smaller than the console snapshot size.
This mismatch can cause confusion for administrators and end-users.
Cause
The difference occurs because of how inSync calculates backup size vs. what is eligible for on-demand restore:
Druva endpoint backups include:
Persona Backup: Captures user system and application settings.
Files and Folders Backup: Captures user-selected or policy-defined data.
The console backup size reflects the combined footprint of these components.
System and application settings (Persona data) can only be restored during device activation or replacement flows using the inSync Client—not through on-demand restore or download from the browser.
When restoring via the browser interface, only standard files and folders are available, excluding system settings and application configuration data.
As a result:
Displayed Backup Size = Files & Folders + Persona Backup
Downloadable Restore Size = Files & Folders only
Key Takeaways
Backup size on the console reports the backup size, inclusive of all protected components (Files & Folders + Persona Backup).
Persona/system settings cannot be restored on-demand; they require inSync Client activation on a device.