Is OneDrive a backup? Why sync and recycle bins fall short
OneDrive and Google Drive keep files available across devices, but sync, recycle bins and version history do not amount to an independent backup. This guide explains how deletions spread, where retention runs out, what a compromised administrator account can destroy, and how to build a protected copy you have actually tested.
Key practical checks for owners
- ✓Sync mirrors deletions and unwanted changes to every connected device, so it is a convenience feature rather than a backup.
- ✓The NCSC advises against relying solely on cloud version history or deleted-file recovery for critical data.
- ✓Keep at least one independent copy that an ordinary staff login or a hijacked administrator account cannot alter or delete.
- ✓Retain backups for at least a month and run a restore test so you know the recovery works.
What sync does and what a backup does
OneDrive and Google Drive are built to keep the same files available on a laptop, a phone and the web. When someone edits, renames or deletes a file in one place, the service copies that change everywhere else. That behaviour is what makes shared working easy, and it is also why a sync folder cannot protect you from your own mistakes.
A backup is a separate copy, held somewhere the original cannot reach, that you can return to after something goes wrong. The NCSC says organisations should not rely solely on cloud-service version history or deleted-file recovery for critical data, and should keep an independent copy in another safe place or service. The same advice applies to both OneDrive and Google Drive.
How a deletion spreads to every device
Suppose a member of staff clears out an old client folder in the OneDrive folder on their laptop. The deletion syncs to the cloud, then to every colleague who shares that folder. A ransomware infection on one laptop works the same way: encrypted files are uploaded as the new current version and replace the clean ones.
The recycle bin and version history can often reverse this, but only within limits set by the service. Those limits can include how long deleted items are kept, how many versions are held, and whether the person who needs the file still has permission to see the bin. The NCSC describes this recovery as limited and not a substitute for a reliable backup, so treat it as a first aid kit rather than a hospital.
Retention limits and the gap nobody notices
Most small businesses discover a retention limit only when they need something that has already aged out. A spreadsheet corrupted three weeks ago, a folder deleted before a long holiday, or a contract overwritten by an old version can all fall outside the recovery window by the time anyone looks.
The NCSC recommends retaining backups for longer than a single rolling copy, at least a month, so that you can step back past the point where a problem started. Check what your Microsoft 365 or Google Workspace plan actually retains for deleted files and prior versions, and compare that with how quickly your business would notice a quiet loss.
When the administrator account is the problem
A backup that lives inside the same tenant as the data shares the same weak point: the administrator login. If an attacker phishes a global administrator, or a disgruntled leaver still holds admin rights, they can delete files, empty recycle bins and remove the retention settings that would have saved you. The ICO's ransomware guidance asks organisations to assess whether backups are offline or segregated, who can alter or delete them, and whether changes or deletions would be detected.
The practical answer is separation. Keep at least one copy that is not reachable through the main network or the primary admin account, and make sure previous versions are protected from accidental or malicious deletion. Limit the number of people with administrator rights, protect those accounts with multi-factor authentication, and make the credentials for the backup service different from the ones used for daily work.
Setting up an independent copy you can trust
Start by listing the data the business could not operate without: client records, finance files, contracts, shared mailboxes and the configuration needed to rebuild systems. The NCSC advises backing up essential data together with the configuration data needed to operate systems, keeping multiple copies in different locations. Then choose a third-party cloud-to-cloud backup tool or a separate storage target that sits outside your Microsoft 365 or Google Workspace admin control.
For the independent copy, work through the setup in the order below. The exact menu names vary by product, but the sequence holds.
- 1Create a dedicated account for the backup service that is not used for daily email or file work.
- 2Turn on multi-factor authentication for that account and for every administrator account in your Microsoft 365 or Google Workspace tenant.
- 3Connect the backup tool to OneDrive, SharePoint, Google Drive, mail and shared drives, and select the data identified as essential.
- 4Set retention to at least 30 days and enable immutability or deletion protection where the product offers it.
- 5Configure alerts so that a failed job or a sudden mass deletion emails more than one person.
- 6Run the first full backup and confirm the item count matches the live data.
- List of data sets covered by the backup, with an owner named for each
- Screenshot or export of the retention period and deletion protection settings
- Record of who holds administrator rights on the backup service and the cloud tenant
- Evidence that multi-factor authentication is enforced on those accounts
- Backup job logs showing recent successful runs and any failures followed up
Testing restores and handling erasure requests
A backup you have never restored is an assumption. Schedule a restore test at least twice a year: pick a folder and a mailbox at random, recover them to a clean location, and record how long it took and whether the files opened. UK GDPR expects you to be able to restore availability and access to personal data in a timely manner after a physical or technical incident, and a dated test record is the clearest evidence that you can.
Backups also hold personal data, so consider erasure requests. The ICO says organisations must think about how a valid request applies to backup systems, including the retention schedule, and may put the data beyond use until it is replaced under that schedule. Document that approach in your retention policy so a request received next year is handled consistently.
- Dated restore test record showing what was recovered and how long it took
- Named person responsible for running and signing off each test
- Written retention schedule that covers backup copies
- Note of how erasure requests are applied to backup data
- Follow-up actions from any test that failed or ran slowly
Common questions
- Is OneDrive a backup for my business files?
- Not on its own. OneDrive keeps a synchronised copy and offers a recycle bin and version history, but a deletion or unwanted change spreads to every connected device. The NCSC advises against relying solely on cloud version history or deleted-file recovery for critical data and recommends keeping an independent copy in another safe place or service.
- Does Google Drive protect against ransomware?
- Google Drive version history and trash can help you roll back some changes, but encrypted files can sync as the new current version, and recovery depends on what the service still holds. The NCSC's advice for OneDrive applies equally here: keep a separate, protected copy of important data so you are not relying on one service to undo an attack.
- How long should backups be kept?
- The NCSC recommends retaining backups for longer than a single rolling copy, at least a month, so you can recover from a problem that went unnoticed for a while. Make sure previous versions are protected from accidental or malicious deletion, and check that your retention matches how quickly your business would realistically spot a loss.
- What if an attacker gets into our administrator account?
- An attacker with administrator access can delete files, empty recycle bins and change retention settings inside the same tenant. That is why the ICO's ransomware guidance asks who can alter or delete backups and whether deletions would be detected. Keep one copy outside the main admin control, protect admin accounts with multi-factor authentication, and alert on mass deletions.
- Do backups affect UK GDPR erasure requests?
- Yes. The ICO says you must consider how a valid erasure request applies to backup systems, including your retention schedule. Where data cannot be removed immediately, it can be put beyond use until the backup is replaced under that schedule. Record this approach in your retention policy so requests are handled consistently.
- How often should we test a restore?
- At least twice a year, and after any major change to your systems or backup tool. Recover a random folder and mailbox to a clean location, note how long it took and whether the files opened, and keep the dated record. UK GDPR expects you to restore access to personal data in a timely manner after an incident.
Official UK sources checked
- Small organisations guide to cyber security | Backing up your ...
- 10 Steps to Cyber Security | Data security
- How do we find and retrieve the relevant information? | ICO
- Ransomware and data protection compliance
- Encryption scenarios
- Right to erasure
- Using online services safely | Back up your organisation's ...
- Security outcomes | ICO
Related UK cybersecurity guides
Ransomware-proof backups for Microsoft 365 and Google Workspace
Cloud platforms keep their own services running, but that does not give every business an independent copy of deleted, encrypted or maliciously altered files.
How to apply the 3-2-1-1-0 backup rule in a small UK office
The 3-2-1-1-0 model means three copies of your data, on two types of storage, one copy off-site, one copy offline or immutable, and zero errors proven by a restore test. It is a practical model rather than a UK regulatory requirement, but it matches NCSC advice on isolated backups and regular restore testing. This guide shows how to build it for a business with 5 to 50 staff and how to run a quarterly restore test.
How to Enforce 2-Step Verification in Google Workspace
Enforcing 2-Step Verification in Google Workspace is done from the Admin console under Security, Authentication. This guide covers the admin path, choosing an organisational unit or group, staging the rollout so staff can enrol, protecting administrator accounts first, and handling recovery codes and lost devices before enforcement begins.
