Skip to main content
All CollectionsGoogle WorkspaceProtect Google Workspace data
Understanding the backup data size accounting for Google Workspace
Understanding the backup data size accounting for Google Workspace
Updated over a year ago

Overview

Druva performs incremental forever backup of Google Workspace data (in Google Drive) after the first full backup. To understand how Druva accounts for backup data size, we must also understand how Google natively accounts for the backup data size.

Here are the key considerations that will help you understand how the backup data size (Total backup data size and Last backup data size) is accounted for:

Native files

Druva: Includes the size of the native file while calculating the backup data size .

Google Storage: Does not include the size of native files (docs, sheets, slides etc.).

Impact: The backup data size reflected in Druva will be higher than what is reflected in Google Storage.

Deleted files

Druva: Includes the deleted file size, even after files are deleted because Druva retains the snapshots till the retention period is not expired.

Google Storage: Does not include the size of the deleted files.

Impact: The backup data size reflected in Druva will be higher than what is reflected in Google Storage. Files are compacted from snapshots only when they go past the data retention period.

Same files stored in multiple locations

Druva: Includes all the copies of the same file stored in multiple locations.

Google Storage: Same file located in multiple folders or location in Google Drive is counted as a single file.

Impact: The backup data size reflected in Druva will be higher than what is reflected in Google Storage because Druva accounts for all the copies. For example, a 5 MB file located in three folders in Google Drive will be counted as 5MB in Google storage while in Druva it’s counted as 15 MB.

File size

Druva: Includes the actual file size that is provided when Druva reads the file for backup.

Google storage: Google saves data in compressed format and reflects the compressed file size.

Impact: The backup data size reflected in Druva will be higher than what is reflected in Google Storage because in Druva the data set size is based on the actual file size.


💡 Tip

You can reduce the files copied by excluding all the shared data from other users and allow backup only of the primary user drive.

This configuration is available while configuring a Profile. Uncheck the Backup shared data owned by other users option to reduce source data for backup and avoid duplicity. For more information see, Update a profile.


Did this answer your question?