News

Does Google back up my Google Workspace data?

Google keeps Google Workspace running, but it doesn't keep a backup you can restore from — and its own documentation puts your data squarely on your side of the line. Here's where Trash, admin restore and Vault run out, and what an independent, off-domain backup actually needs to look like.

Short answer: no. Google keeps Google Workspace running, but it does not keep a backup of your data that you can restore from. Your Gmail, Drive files, Shared drives, Calendar and Contacts are your responsibility, and Google's own terms say so.

This surprises a lot of people. Google runs some of the most reliable infrastructure on the planet, files are replicated across data centers, and a deleted file sits in Trash for a month. That feels like a backup. It isn't. Replication protects against Google losing a disk. It does nothing when a user empties Trash, an admin deletes an account that owned half the company's documents, or ransomware encrypts every file in a synced folder and Drive for desktop faithfully uploads the encrypted versions.

This article explains what Google actually promises, what the built-in protections cover, where they run out, and what a real backup of Google Workspace looks like.

What Google actually promises: the shared responsibility model

Google runs the service; you own the data in it. Google spells this out in its shared responsibility documentation, which names Google Workspace as a SaaS product and describes the split like this:

Responsibility area

Who is responsible

The data you choose to store in the application

Customer

Access controls and access policies

Customer

Identity and user management

Customer

The application itself

Google

Network and underlying infrastructure

Google

Physical hosts and datacenters

Google

Google's own summary is that the cloud provider always remains responsible for the underlying network and infrastructure, while customers always remain responsible for their access policies and data. Google even lists where and how you manage encryption keys as one of the decisions that ties directly to your responsibility to protect your data.

Google prefers to talk about "shared fate" rather than shared responsibility, meaning it offers guidance, blueprints and tooling to help you secure your workloads. That is a real commitment to help. It is not a commitment to hand you back a mailbox or a Shared drive you deleted three months ago. Google's data protection guidance for Workspace likewise expects the customer to have a policy covering backup, recovery and restoration of their own data. Google guarantees availability of the service, not recoverability of your data.

What Google's built-in protections cover (and their limits)

Google Workspace does ship with recovery features, and they are useful. The problem is that every one of them is short-lived, lives inside the same domain it protects, or is aimed at compliance rather than recovery. Here are the windows as Google documents them:

Feature

What it covers

Window

Where it stops

Gmail and Drive Trash

Items a user deleted

30 days, then auto-purged

Emptied by the user, or expired, and the item leaves Trash

Admin restore of Drive or Gmail data

Items removed from a user's Trash

25 days after leaving Trash

Purged after 25 days; not even Google support can bring it back

Restore a deleted user

The whole account, with its Gmail and Drive

20 days after deletion

Permanently deleted after 20 days

Admin Drive restore, per user

All files removed in a date range

Up to 25 days

All-or-nothing by date range; one restore job at a time; stops if the user runs out of storage

Drive version history

Earlier versions of a file

30 days or 100 versions for uploaded files

Per file; does not help when the file itself is deleted

Google Vault

Retain and search Gmail, Drive, Chat and more for compliance

As configured

Business Plus and Enterprise editions; an eDiscovery and hold tool, not a restore tool

Three things stand out. First, the windows are measured in days, not years. A deletion nobody notices for a quarter is unrecoverable under every default above; Google's own security whitepaper says data is gone after 25 days even if you contact support. Second, everything is inside the same Workspace domain, under the same super admin credentials. If the domain is compromised, the "backup" is compromised with it. Third, none of these give you a copy you control: you cannot download it, move it to another provider, or restore it into a different domain.

Google Takeout and the Data Export tool can produce a one-time archive, but they are manual, slow for large domains, and produce a pile of files rather than a versioned, restorable backup.

The gaps: scenarios where data is gone for good

These are the cases we hear about most often, and none of them are exotic.

The employee who left three weeks ago. An admin deletes the account to stop paying for the seat. Twenty days later the account, its Gmail and its Drive are permanently gone. Then a customer asks for the contract that only ever lived in that person's inbox.

The owner problem. In Google Drive, files belong to the user who created them. Delete that user without transferring ownership and every document they owned disappears from everyone else's "Shared with me" as well. Shared drives fix this for new files, but most domains still have years of My Drive content owned by individuals.

The quiet deletion. Someone tidies a Shared drive and removes a folder they think is obsolete. Thirty days in Trash, 25 more days for an admin restore, then it is purged. Nobody looked for it for two months.

Ransomware through Drive for desktop. Malware encrypts files on a laptop. Drive for desktop sees changed files and syncs them, as designed. Version history helps for individual files, but rolling back thousands of files across many folders by hand is not a recovery plan.

The compromised super admin. Phishing or a stolen session token gives an attacker super admin. Every built-in protection, from Trash to admin restore to Vault retention rules, is now controlled by the attacker.

The malicious insider. A departing employee empties their Trash on the way out. The admin restore window starts ticking the moment they do, and nobody knows to look.

The suspended subscription. A lapsed payment or billing dispute suspends the Workspace subscription. Google warns that subscriptions suspended for more than 60 days may be cancelled and the user data lost with them.

Calendar, Contacts, Chat and everything else. Calendar events and Contacts have no admin restore at all. Chat and Meet recordings depend on Vault policies most domains have never set. Sites, Forms and Keep have their own quirks.

In every one of these cases, Google has done exactly what it promised: the service stayed up. The data loss happened on the customer's side of the line, so recovery is the customer's job.

What a real backup of Google Workspace needs to look like

A backup closes the gap only if it is independent of the thing it protects. For Google Workspace that means five properties:

  1. Stored outside the domain. The copy must live somewhere a Workspace super admin credential cannot reach: your own object storage, another cloud, or a provider's storage under a separate account. If a compromised super admin can delete the backup, it isn't one.

  2. Retention you set, not Google. Twenty and 25 days are grace periods. A backup should keep versions for months or years, on a schedule you choose, so a deletion discovered next quarter is still recoverable.

  3. Encrypted before it reaches storage. Mail and files should be encrypted before they reach storage, so the storage provider never sees plaintext. Then decide who should hold the key: you, for maximum control, or the backup vendor, for a fully managed service. Know which one you have chosen, especially if you handle regulated data such as PHI or financial records.

  4. Restorable in full and in part. You need to be able to bring back a single email, a folder, a whole mailbox, or a whole user, and to restore into the same domain or a different one. Cross-domain restore is what saves you when the original domain is suspended or gone.

  5. Covers the workloads people actually use. At minimum Gmail, Drive including Shared drives, Calendar and Contacts. Google-native formats (Docs, Sheets, Slides) need to be exported in a form you can actually open later.

The classic 3-2-1 rule still applies: three copies, on two kinds of media, one of them off-site. For SaaS data, "off-site" means off-domain. Google's own replicas are copies one and two on the same medium in the same place. The third copy is the one you own.

How Duplicati fills the gap: managed or self-hosted

Duplicati offers two ways to keep an independent, off-domain copy of your Google Workspace data. Both cover Gmail, Drive, Shared drives, Calendar and Contacts, both restore into the same domain or a different one, and both keep versions for as long as your policy says. They differ in who runs the backup and who holds the encryption key.

Managed Google Workspace backup

The Duplicati Console runs the backups for you. Connect your domain, pick the users, and Duplicati schedules and executes every job on its own infrastructure. There is nothing to install and no server to maintain.

  • Zero infrastructure. Backups run in Duplicati's cloud; your only job is choosing who to protect.

  • Storage included. Each protected user includes 100 GB of Duplicati cloud storage. You can point the backup at your own destination instead.

  • Encrypted at rest. Data is encrypted before it reaches storage. Because Duplicati runs the jobs and restores on your behalf, Duplicati Inc holds the encryption key for managed backups.

  • Best for small and mid-sized businesses, and MSPs who want one console and one policy across many client domains with nothing to host.

Self-hosted Google Workspace backup

You run Duplicati on your own server, VM or workstation and add a per-user Google Workspace license from the Console. Backups pull from your domain and land in a destination you choose: Duplicati Cloud Storage, S3-compatible object storage, Google Cloud Storage, Azure Blob, Backblaze B2, a NAS, or dozens of others.

  • You hold the key. Data is encrypted client-side on your machine with a passphrase only you know. Neither Duplicati nor the storage provider can read it.

  • Your storage, your rules. Any destination Duplicati supports, with retention and immutability configured on your side.

  • Central visibility. The Console still monitors the jobs, alerts on failures and lets you manage many machines and domains from one place.

  • Best for organizations with data residency or key-custody requirements, regulated workloads, and MSPs who already run Duplicati for endpoint and server backup.


Managed

Self-hosted

Who runs the backup

Duplicati Console

You, on your own machine

Encryption key

Held by Duplicati Inc

Held by you

Storage

100 GB per user included, or your own

Your own destination

Setup

Connect domain, pick users

Install Duplicati, add Workspace license

Cross-domain restore

Yes

Yes

Either way, the copy lives outside the Google Workspace domain, under credentials a compromised super admin does not have, with retention Google's timers cannot touch.

Frequently asked questions

Isn't Google's replication a backup? No. Replication copies your data, including deletions and ransomware-encrypted files, to another datacenter within seconds. It protects Google against hardware and site failure. It does not let you go back in time.

We have Google Vault. Isn't that enough? Vault retains and lets you search data for legal and compliance purposes, which is valuable. But it is administered from inside the domain, requires Business Plus or Enterprise licensing, and offers no way to restore a user's mailbox or Drive into place, or to export a clean copy you control to a different domain.

Do I need to back up Drive, or just Gmail? All of it. Drive and Shared drives usually hold more business-critical content than mailboxes, and file ownership tied to individual users makes Drive the more fragile of the two when accounts are deleted.

How much does it cost to back up Google Workspace with Duplicati? Both options are licensed per Google Workspace user. Managed backup includes 100 GB of Duplicati cloud storage per seat; self-hosted backup uses storage you already have. Current pricing is on the Duplicati pricing page.

How do I start? Sign in to the Duplicati Console. For managed backup, connect your Google Workspace domain and choose the users to protect; the first backup runs from there. For self-hosted backup, install Duplicati on a machine you control, add a Google Workspace license, and point the job at your own storage.

Sources: Google Cloud, Shared responsibilities and shared fate; Google Workspace security whitepaper, Data recovery; Google Workspace Admin Help, Recover deleted files and folders for Drive users.

Get started for free

Pick your own backend and store encrypted backups of your files anywhere online or offline. For MacOS, Windows and Linux.

Pick your own backend and store encrypted backups of your files anywhere online or offline. For MacOS, Windows and Linux.

  • Example image