Skip to content
Orindle

Cloud Storage vs Cloud Backup: What's the Difference?

Sync, storage and backup are three different promises. Confusing them is how people lose files that were 'in the cloud'.

Published 16 Nov 20265 min read
Two contrasting abstract scenes: an active file synchronisation path between devices on one side, a protected recovery vault on the other

A file on your laptop, synced to a folder in the cloud, is one file in two places. That sounds like a backup and behaves like one — right up until you delete the wrong folder, or ransomware encrypts your documents, and the change propagates faithfully in seconds. Synchronisation is not protection. It is a very fast mirror.

Storage, sync and backup are three different promises

Cloud storageFile syncCloud backup
Primary jobHold files somewhere you can reach themKeep two locations identicalKeep a recoverable copy over time
Survives disk failureYesYesYes
Survives accidental deletionOften, via a binNo — the delete propagatesYes, for the retention window
Survives ransomwareSometimes, if a clean version existsNoUsually, with versioning
Survives account compromiseRarelyNoSometimes, if the backup is separate
Typical interfaceA web app and driveA synced folderAn agent that runs on a schedule
What each one actually guarantees.

Most consumer products blur these together, and reasonably so: Google Drive, OneDrive and Dropbox all store files, sync them and keep some version history. The distinction matters less as a category question and more as a question about *your* failure modes — what does the product do when you make a mistake, versus when your hardware fails.

Version history and recovery: the part that decides everything

The single most useful thing to check in any product is how far back you can recover and whether a deleted file is still there afterwards. Providers differ widely and quietly: 30 days is a common consumer window, some plans extend it to 180 days or a year, and end-to-end encrypted services vary in whether older versions are recoverable at all without a key.

A concrete example of how this plays out. You overwrite a spreadsheet with an empty file at 10:00 and do not notice for three weeks. If your provider keeps versions for 30 days, you can recover it. If it keeps seven, you cannot, and the file exists — with the right name, the right location and no data. That is the specific shape of loss that catches people who believe they are backed up.

Common data-loss scenarios, and what protects you

  • Laptop drive fails. Cloud storage alone protects you. The file is elsewhere; the disk is irrelevant.
  • You delete the wrong folder. A bin with a retention window protects you. Sync alone does not — the deletion is replicated before you notice.
  • Ransomware encrypts your documents overnight. Version history and an independent backup protect you. A continuously synced folder does not: the encrypted versions overwrite the clean ones.
  • Your account is compromised and files are deleted. Only a separate copy survives. Anything inside the compromised account is under the attacker's control.
  • You overwrite a file and notice a month later. Version history protects you — if the window is longer than a month.
  • The provider makes a mistake. Rare, and the reason a second copy at a different provider or on a local drive is worth having for anything irreplaceable.

Two real-world examples

The freelance designer

Works entirely from a synced cloud folder so every project is available on both machines. Deletes a client folder after a project closes, meaning to archive it first. Every machine syncs within seconds. The bin saves her — for the retention period. If the retention period had been a week and she had tidied up on a Friday before a two-week holiday, the folder would be gone permanently. Storage and sync did their job; they were never asked to do backup's job.

The small business

Runs on a shared drive with 30 days of version history, which covers accidental deletion well. It does not cover an account-level compromise, or a sync client bug that propagates a corrupt state. A weekly export to a separate destination is dull, cheap and the reason the business still has its finance files. The lesson is not that their cloud storage is bad — it is that the cloud was doing one job and they assumed it was doing two.

When you need both

If losing a file would be an inconvenience, storage with a bin and some version history is genuinely enough. If losing it would be a problem — irreplaceable photos, client work under contract, financial records, a book you are writing — you need a second, independent copy, because every single-copy arrangement has exactly one failure mode that ends it.

  • Storage covers: the disk dying, needing files on another device, sharing, and everyday convenience.
  • A bin covers: your own mistake, briefly.
  • Version history covers: overwriting, and damage you notice within the retention window.
  • Backup covers: all of the above plus compromise, ransomware and provider error — because it is independent.

The practical version of 3-2-1 for a person rather than a company: files in cloud storage, synced to one machine, plus an external drive that is plugged in monthly, plus the provider's version history. That is three copies, two media, one offsite, and it takes about an hour a year to maintain.

Where Orindle fits in this

Orindle is cloud storage. Files live in Cloudflare R2 with encryption at rest, deletes move to a bin with a retention period, and the account is protected by server-side authorisation on every request. That covers storage and it covers the common accidental deletion case.

If you are choosing storage for files you intend to share as well as keep, our guide to sharing large files online covers the access-control side of the same question.

Further reading

CISA — Data backup options

The 3-2-1 framing and its rationale, from a government security agency.

Orindle — Trash and retention

What Orindle's bin does and does not do.

Frequently asked questions

Does cloud storage count as a backup?
Only if the copy is independent of the original failure. If deleting a file deletes it in the cloud too, you have synchronisation, not backup. A backup survives the mistake as well as the disk failure.
Does Orindle provide backup?
No, and it should be described carefully. Orindle stores files and moves deleted files to a bin with a configurable retention period before removing them. That helps with accidental deletion. It is not a backup service, does not take point-in-time snapshots of your whole account, and should not be your only copy of anything irreplaceable.
What is the 3-2-1 rule?
Three copies of the data, on two different types of media, with one copy offsite. It is old, it is boring, and it remains the standard because most data loss involves more than one failure at once.

Written and reviewed by the Orindle team. This article is editorial content published by Orindle, which sells cloud storage. Where a competitor is discussed, the figures come from the provider's own published pages and are dated in the text. Prices and allowances change; re-check before relying on them.

All articles