Open the trash in Google Drive and you are looking at the first of several safety nets in Google Workspace. Each one is useful. None of them is a backup, and knowing where each one ends is most of the work of protecting your account.
This article walks through what Google keeps, where those protections stop, and what a separate Google Workspace backup should add.
What Google does well
Google keeps the service running. Your mail and files are stored redundantly, so a hardware fault in one of its data centers does not cost you data. That is availability, and it is Google’s side of the arrangement.
For everyday mistakes, Workspace has several layers:
- Trash in Drive and Gmail. Deleted items wait in the trash, then are removed automatically after a set period.
- Admin restore. For a limited window after items leave the trash, a Workspace admin can restore a user’s deleted Drive files or Gmail messages from the admin console.
- Version history. Google Docs, Sheets and Slides keep a record of edits. Other files in Drive keep earlier uploaded versions for a time.
- Google Vault, on editions that include it, retains mail and files under rules your admin sets, so they can be searched and exported for legal and compliance work.
Google publishes the exact windows for each of these in its admin help pages. They change from time to time, so check the current figures rather than relying on anyone’s memory, including ours.
Where the safety nets end
The windows close. Trash empties, and admin restore has a time limit. A mistake found after both have passed is permanent. Late discovery is common: a folder removed in a spring cleanup is often missed only when someone needs it months later.
Vault is not a restore tool. Vault keeps data so it can be found and exported. It does not put a folder back where it was, with its sharing settings, in a few clicks. Exports come out as files that someone then has to sort through. Vault also keeps only what its rules cover, and an admin can change those rules.
Deleted users take their data with them. When an admin deletes a user, Google offers to transfer their Drive files and some other data to another person. Mail is not part of that transfer. If nobody moves it first, it is deleted with the account once a short recovery window passes. Some editions offer an archived-user license to keep a departed account’s data, at a cost.
A sync client can spread a bad change. Google Drive for desktop keeps a computer and Drive in step. Mass deletions or ransomware-encrypted files on one computer can reach Drive like any other change. Trash and version history help if the problem is caught early.
Everything sits behind one set of keys. All of the above lives in your Workspace tenant. A stolen super admin password, a mistaken bulk action, or a billing problem that suspends the account affects the safety nets and the data at the same time.
Shared drives behave differently
Shared drives belong to the organization rather than to a person, so files do not vanish when someone leaves. That is a real improvement over files kept in personal My Drive folders.
Permissions still matter. Members with manager or content manager access can delete files in a shared drive, and those deletions go to the shared drive’s trash on the same kind of timer as everything else. A well-meant reorganization by one person is still a deletion.
It is worth checking who holds those roles in each shared drive. It is easy to make everyone a manager on the day a drive is set up, and never look again.
When someone leaves the company
Departing staff are a common way for Workspace data to slip away, and a short written routine closes most of the gap. Before an account is deleted:
- Confirm the backup holds a recent copy of the account, including mail.
- Move any files the person owns in shared folders into a shared drive, so the organization owns them.
- Transfer their remaining Drive files to their manager during deletion.
- Decide what happens to their mail: keep it in the backup, migrate it to a shared account, or keep the account on an archived-user license where your edition offers one.
- Write down what was done, by whom and on what date.
Steps 1 and 5 are the ones that get skipped when someone leaves in a hurry. They are also the ones that matter most a year later.
What a backup should do
A separate backup copies Gmail, Drive, shared drives, Calendar and Contacts out of Workspace on a schedule, and keeps versions for a period you choose. When comparing options, look for:
- Several copies a day, so a morning’s work is covered.
- Shared drives as well as My Drive, with folder structure and sharing kept.
- Retention of a year or more, extendable for records you must keep. Your accountant or counsel sets that number.
- Departed users kept without needing a paid Workspace license for them.
- Restore to the same or a different account, so a departed person’s files can go straight to their replacement.
- Separate credentials, so a Workspace admin cannot delete the backup.
- Tested restores on a schedule, with a written result.
The Google Workspace Backup plan copies Gmail, Drive, shared drives, Calendar and Contacts 3 times a day. It keeps a year of versions by default, extendable to 7 years, and restores into the same or a different account. It starts from $4 per user per month (indicative), and sits within our Microsoft 365 and Google Workspace backup service.
If some of the terms here are new, the backup and recovery glossary explains retention, versioning and the rest in a line each.
Example: a spring shared drive cleanup
Consider a 16-person event planning company that keeps vendor contracts in a shared drive. In April, the operations manager reorganizes the drive and deletes a folder called “Old vendors,” believing everything in it was duplicated elsewhere. It was not.
In November, a venue disputes a cancellation fee. The signed contract was in that folder. The trash emptied long ago, and the admin restore window has passed. Without a backup, the company asks the venue for its copy of the contract and hopes for the best.
With a backup, someone searches it for the venue’s name, finds the folder as it stood on the last copy before the April cleanup, and restores it into the shared drive as a new folder. The contract is back in the same shared drive, with its folder structure intact. Our target for a single file is 1 business hour from the request to support@ezbre.com.
Nobody in this example did anything careless. One person tidied up, and the gap only showed when the files were needed seven months later.
Google Workspace and Microsoft 365 compared
If you run both, or are choosing between them, the backup picture is similar. Both platforms keep the service available. Both catch recent deletions for a limited time. Neither keeps a long-term copy outside your tenant that you control. Does Microsoft 365 back up your data? covers the Microsoft side in the same way.
Audit your own domain
Six questions, most of which you can answer from the admin console in one sitting:
- Which Workspace edition do you have, and does it include Vault?
- Who holds super admin rights, and do they all use two-factor sign-in?
- What is your written process when someone leaves: transfer, archive or delete?
- Who can delete files in each shared drive?
- Is any copy of your Workspace data held outside Google?
- When did someone last restore something deleted more than a month ago?
If the answer to question 5 is no, start there.
Go through it together
If you would like someone to go through this with you, the free backup check covers Google Workspace too. In 45 minutes, remotely, we look at what is protected today, run one test restore and send a written page of findings. Book a free backup check when it suits you.
