Overview
This article explains how the backup of Shared Data in Google Drives is carried out by Druva inSync.
Within the inSync profile -> SaaS Apps -> Google Drive -> a checkbox labeled as “Backup shared data owned by other users” allows you to back up the data that resides in the “Shared With me” section of the user’s Google Drive. Check the screenshot below:
inSync’s backup code works differently on the basis of this checkbox when it is checked and when it is unchecked.
Read through the following different scenarios, that will explain the backup patterns for the “Shared With Me” section of the user’s Google Drive:
Scenario 1:
A Folder is shared between the users and Backup of shared data is disabled in inSync:
Let’s take a look at the following example:
Einstein creates a folder named “First Parent Folder”
He shares the folder with Newton with EDIT rights.
Newton navigates to the “Shared with me” section and finds the shared folder.
Newton uploads a test file named “Test.txt” in this shared folder which is around 43 MB in size.
Now within Druva inSync, we have disabled the setting for “Backup shared data owned by other users” as displayed below:
Druva will run the backup of these 2 users with the following results:
For Einstein -> inSync will run the scan of his “My Drive” only.
Einstein owns the folder - “First Parent Folder”
Since Einstein is the owner of the First Parent Folder -> we will backup all the items that are created inside this folder (including the “Test.txt”)
Einstein’s G-drive usage in Druva inSync will show as 43 MB along with the Test.txt file in the snapshot.
For Newton’s backup -> the Test.txt is owned by Newton … however, it is present in the “Shared with me” section of the Newton’s drive > and we are not backing up Shared data here — so inSync will NOT backup the Test.txt file for Newton.
Newton’s G-Drive usage in Druva inSync will show as 0 MB and the file will not be visible for restore.
Discrepancy: Google will calculate the usage based on the file owner. Thus, in Google Drive, the usage pattern will show: Einstein = 0 MB and Newton = 43 MB,
Thus, we will see the following usage discrepancy: (Refer below table)
User | G-Drive Usage | inSync Snapshot Size | inSync Backup Size |
Einstein | 0 | 43 MB | 43 MB |
Newton | 43 MB | 0 | 0 |
Scenario 2:
Folders are not shared. Files are shared directly from My Drives.
Backup Shared Data is Enabled.Backup is Un-Ordered.
Example:
Einstein shares a file named “Test.txt” with Newton -
Backup Shared Data owned by other users is Enabled.
Newton completes the backup before Einstein.
Now, Einstein completes the backup.
The following will happen:
Newton will back up the shared file and Test.txt will be visible in Newton’s snapshot, available for restore.
Newton’s Total backup Data will be 43 MB and the Snapshot size also will be 43 MB.
Einstein completes the backup.
However, since the file is the exact same file that was already backed up by Newton, inSync will not use up the storage again for Einstein for this file. (Deduplication).
inSync will create a reference of that file under Einstein’s snapshot and thus, the snapshot size will show as 43 MB.
And, the total backup data for Einstein will be 0.
From the customer’s overall inSync storage usage point of view, the total used space including both these users will be 43 MB only.
Here are the statistics in such a scenario: (Refer below table)
User | G-Drive Usage | inSync Snapshot Size | inSync Backup Size |
Einstein | 43 MB | 43 MB | 0 |
Newton | 0 | 43 MB | 43 MB |
Thus, with the deduplication process, the storage used will not multiply, even if the Backup Shared Data checkbox is selected.
❗ Important
For Google Drive, Deduplication is NOT done on the basis of the file names.
For Google Drive items, inSync detects the uniqueness of a file, based on the File ID in Google.
For whatever reason, if the File ID Changes in Google, then the new File ID will be considered as a new file and inSync will back it up separately.
Scenario 3.1:
A Folder is shared between the users and Backup of shared data is Enabled in inSync
Backup is Un-Ordered
Einstein creates a folder named “First Parent Folder”
He shares the folder with Newton with EDIT rights.
Newton navigates to the “Shared with me” section and finds the shared folder.
Newton further creates 2 sub folders within this folder - named as “Child Folder 1” and “Child Folder 2” -> and then adds a file in the Child Folder 2 titled as “Test.txt” which is around 43 MB in size.
“Backup shared data owned by other users” is enabled in this scenario.
Now, Einstein is not backing up yet. But Newton completes the backup of the Drive.
Thus, as discussed in Scenario 2, the Test.txt file will get backed up under Newton’s backup and at this point, we will see the following storage usage: (Refer below table)
User | G-Drive Usage | inSync Snapshot Size | inSync Backup Size |
Einstein | 0 | Not Backed up yet | Not Backed up yet |
Newton | 43 MB | 43 MB | 43 MB |
Scenario 3.2:
In continuation of the above points, Admin now disables the “Backup shared data owned by other users”
Now Einstein runs the backup of his Google Drive.
Since the checkbox is disabled, inSync will now look for Einstein’s My Drive -> inSync will find the folder owned by Einstein: “First Parent Folder” -> inSync will backup everything that resides inside that folder including the Test.txt file.
Einstein will thus see the “Test.txt” file in his backup snapshot.
But the same file was backed up previously by Newton, and we have the deduplication process here in play for Einstein's backup. Hence, when the backup for Einstein is complete, inSync will show the file in the snapshot but the size of the file will not get added again towards Einstein’s usage.
Finally, Newton also completes the backup, and this time the shared with me section, will not be scanned by inSync.
Thus, the numbers in this specific snapshot will look like this:
User | G-Drive Usage | inSync Snapshot Size | inSync Backup Size |
Einstein | 0 | 43 MB | 0 |
Newton | 43 MB | 0 MB | 43 MB |
In case of storage statistics discrepancies for Google Drive backups, ensure to check all of the above listed information.
If this does not help answer the discrepancies, then please reach out to Druva Support for further investigation.