Skip to main content

Protecting Google Workspace Apps with Druva inSync

Updated in the last hour

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 Slides

    • application/vnd.google-apps.spreadsheet' - Google Sheets

    • application/vnd.google-apps.document' - Google Docs

    • application/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 .PPTX files (>400 MB) may fail due to Google API infrastructure limits.

    • Workaround: Split large files or convert them to PDF.

  • 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 .


Workflow: Implementation Steps

  1. Integrate: Configure inSync with a Google Super Admin account.

  2. Assign: Enable Google Workspace backup within a Profile.

  3. Restore: Restore data to the original location, a custom location, or download data.

Did this answer your question?