Cloud vs Local Backups: The Cleanup Angle Nobody Mentions

Two tools for two different disasters

A local backup is fast to restore and cheap per terabyte, and it dies with the flat — fire, flood, theft and a ransomware campaign with a grudge against USB drives all count. A cloud backup survives the house but is bounded by your upload line on the way up and your download line on the way back. The classic 3-2-1 rule — three copies, two kinds of media, one offsite — is not a recommendation to pick a side; it is the admission that you need both.

The cleanup angle nobody mentions

Neither kind fails loudly; both just quietly accumulate. The list below is where the space actually goes.

• File History keeps old versions forever by default — the Advanced settings → Clean up versions dialog reclaims the backup drive
• Cloud sync is not backup: OneDrive and Dropbox propagate deletions, and ransomware encrypts the synced copy too — versioning retention is weeks, not years
• Files On-Demand placeholders still cache real data locally — Free up space on the big folders gives gigabytes back to the system disk
• Image backups stack incremental chains — the chains of machines you no longer own eat the target drive for years
• Retention needs a policy, not a feeling: dailies for a month, monthlies for a year is a sane default for home machines
• Junk you never deleted gets backed up faithfully by both kinds — cleaning the source is the cheapest backup optimization

A setup that survives contact with reality

Pair them by strength: an external SSD with a scheduled image for the machine itself, and the cloud for the irreplaceable small stuff — documents, photos, project files. Test a restore once a quarter, because a backup that has never been restored is a hypothesis, not a backup. And when the backup drive fills, that is not the moment to buy a bigger one — that is the moment to prune versions of files that stopped existing two years ago.

Questions and Answers

Read next