Google Workspace Backup

Not in the sense most people mean. Google protects comprehensively against their own infrastructure failing — hardware loss, data centre outage, corruption in their systems — with redundancy you could not match yourself. What that does not cover is anything originating from your side: a user deleting something, a departing employee clearing their Drive, ransomware encrypting files that then sync, or an administrator error. For those you have recovery windows measured in weeks, not a backup.

Items a user deletes sit in their own trash for 30 days and they can restore them. Once trash is emptied, an administrator has 25 days to recover them, after which Google purges them and they cannot be recovered. A deleted user account can be restored for 20 days, which brings back their Gmail, any Drive files that were not transferred, and their primary calendar. Those figures were checked against Google's administrator documentation in September 2026 and Google does revise them.

No, and this is the most expensive misunderstanding in this area. Vault retains, searches, exports and places legal holds on data — it answers a compliance question. Google's own documentation states plainly that you cannot directly restore Vault-retained data to a user's Drive: you can export it, which gives you a file, not the folder back where it was. Businesses regularly buy a higher edition believing they have bought backup, and discover the difference during an incident.

Many small businesses genuinely do not, and we will tell you so rather than sell it. If your files are in Shared Drives owned by the company, you have a real leaver process, and nothing is under a retention obligation, the built-in windows cover the realistic scenarios. It becomes worth pricing when discovering a loss two months later is plausible, when one person holds a lot of irreplaceable work, or when a regulator, contract or auditor requires demonstrable point-in-time recovery.

Move organisational files into Shared Drives owned by the company rather than leaving them in individuals' Drive accounts. It removes the largest single category of data loss — files leaving with the person — costs nothing, and takes an afternoon. The second is writing a leaver process that suspends before it deletes.

Partly, and not at scale. Drive keeps version history, so an individual encrypted file can usually be rolled back to a previous version. What it does not do well is thousands of files at once — restoring them individually is not a realistic incident response. Version history is a genuine mitigation for isolated damage and not a substitute for a recovery plan where a whole synced folder tree has been encrypted.

You start a twenty-day clock, and that is usually a worse trade than it appears. The licence saving is small against the risk of discovering three weeks later that something of theirs was needed. Suspend the account instead, which preserves everything and stops access immediately, then transfer files and delegate mail before deleting anything. Some editions also offer archived-user licences that retain a leaver's mail at lower cost than an active seat.

Retention decides how long data is kept and when it is destroyed — it is a policy instrument that can delete as readily as preserve. Backup is about getting a specific thing back to a specific point in time after something went wrong. They are frequently sold as though they are the same and they answer different questions. An organisation can satisfy a retention obligation perfectly and still be unable to recover a folder somebody deleted in March.