License Editions: For license details, see Plans & Pricing.
Overview
Druva inSync integrates with Google Workspace to provide centralized governance, backup, and restore capabilities for Gmail, Google Drive, and Shared Drives.
User Mapping Logic
To ensure data is backed up to the correct identity, inSync maps users using one of the following identifiers:
Email Address: Direct match of the inSync user email to the Google Workspace account.
User Principal Name (UPN): Mapping via a configured Active Directory attribute.
šStorage Note: Google Workspace backup data consumes the Organization Quota, not individual user backup quotas.
Supported Data & Metadata
1. Gmail & Contacts
Contents:
Emails along with the attachments
Calendar events along with links to the attachments
Contacts
Metadata:
Email ā To, From, Cc, Bcc, Subject, Sent On, Received On
Attachment ā Name, Size
Time Stamp - Created, Modified, Received, Sent
Labels
2. Google Drive & Shared Drives
Contents
Files and folders that are owned by the user or that are shared with the user with download permission.
Shared Drives
Trash data
Comments
Metadata:
Title
Description
Created Date
Modified Date
File Size
Original Filename
Owners
Last Modifying User
Md5checksum
3. Native Google MIME Types Supported
Below are the MIME type for the native file type that would be backed up in Druva. All other native file types will be skipped.
application/vnd.google-apps.presentation- Google Slidesapplication/vnd.google-apps.spreadsheet'- Google Sheetsapplication/vnd.google-apps.document'- Google Docsapplication/vnd.google-apps.drawing'- Google Drawings
ā ļø Critical Limitations & Exclusions
To ensure backup integrity, note the following constraints:
Unsupported Apps: Google Forms and Google Sites are excluded from backups.
File Size Limits: Large Google Slides or
.PPTXfiles (>400 MB) may fail due to Google API infrastructure limits.Workaround: Split large files or convert them to PDF.
Auto-converted Google Docs/Slides presentations: When Microsoft Office files (such as
.pptx) are uploaded with Google Drive's Convert uploads to Google Docs editor format setting enabled, Google converts them into native Google Docs/Slides formats. During backup and restore operations, inSync relies on Google Drive APIs to export these items back to standard Office format. Due to a Google API limitation (conversionUnsupportedConversionPath), Google may fail to export certain complex presentations, resulting in incomplete (undersized) or corrupted files upon restore or download.
ā
āRecommendation: To ensure complete data fidelity and avoid restore issues:In Google Drive, go to Settings > General > Uploads and clear the Convert uploads to Google Docs editor format checkbox.
Upload and store presentation files in their native Microsoft Office (.pptx) format.
Run a new backup after making this change. Backups taken before the change remain subject to this limitation and cannot be remediated. The updated setting applies only to data backed up after the change.
ā
Calendar Attachments: These are stored in the user's Google Drive. Druva backs up the link to the attachment within the Calendar event.
Comments: Some Google Doc comments may be skipped due to platform-side API limitations.
The My Computer folder for syncing local files is excluded from backups and restores. Only My Drive and Shared Drives are backed up and restored. However, My Computer files may be included in the estimation API.
Gmail "Spam" Label Handling: Druva inSync successfully backs up emails with the system-defined "Spam" label. However, due to Google Workspace architectural constraints, these emails are consolidated under the All Mail view on the restore screen instead of a dedicated "Spam" folder. When performing an In-Place Restore, these items will typically appear in the destination Inbox or All Mail view, rather than returning to the system's active spam filter.
Workflow: Implementation Steps