Automate Backups of the Files You Cannot Afford to Lose
A designer I work with lost eleven months of client files in about four seconds. She had not been careless in the way people imagine. Everything lived in a synced cloud folder, the folder had a green tick, and the laptop was two years old.

A designer I work with lost eleven months of client files in about four seconds. She had not been careless in the way people imagine. Everything lived in a synced cloud folder, the folder had a green tick, and the laptop was two years old. Then she tidied up a project directory, emptied the bin to free space, and the deletion travelled to the cloud exactly as the service was built to do. The green tick had never meant what she thought it meant.
This is the gap in most people's setup. Not laziness, and not a missing hard drive sitting in a drawer. The files are being copied somewhere, continuously, by software that works perfectly. What nobody automated was the part that keeps a second copy the mistake cannot reach. That takes one evening to build and about four minutes a month to maintain, and I would rank it above every other automation I have set up.
Sync copies your mistakes too
Dropbox, OneDrive, iCloud Drive and Google Drive are sync services. Their job is to make every device agree. If you delete, rename or encrypt a file, agreement means that change arrives everywhere, including on the copy you were counting on.
They do keep version history, which saves people often enough that the confusion is understandable. The limits are the problem. Most consumer plans keep 30 days of file versions, and the restore flow is per file, so a folder of 400 items becomes an afternoon of clicking. A corrupted project file you only open every quarter will already be outside the window by the time you notice.
Three failure modes get through sync untouched: a deletion you do not notice for two months, a file that silently corrupts, and ransomware that encrypts the folder while the sync client dutifully uploads the encrypted versions. A backup is different from sync in one specific way. It keeps old states that your computer can no longer change.
Pick the storage before you pick the tool
People start with software and stall. Start with where the bytes go, because that decides everything else. These are the four options I see working for individuals and very small teams, with prices as of late 2026.
| Where | Rough cost | Good at | Weak at |
|---|---|---|---|
| External SSD, 2 TB, left plugged in | 95 to 130 dollars once | fast restores, no subscription | fire, theft, forgetting to plug it in |
| Backblaze Personal Backup | around 99 dollars a year | unlimited size, set and forget | one computer per licence |
| Backblaze B2 or Wasabi plus restic | 6 dollars per TB a month | versioned, encrypted, scriptable | needs 90 minutes of setup |
| iCloud or Google One, 2 TB | about 10 dollars a month | phone photos, zero effort | it is sync, not real versioning |
My own setup runs two of these at once: an SSD on the desk for speed and B2 for the copy that survives the building. Total cost last year was 41 dollars of storage fees plus the drive. The second copy is not paranoia, it is the thing that makes the first copy restorable when the drive fails during the restore, which does happen.
The schedule that actually runs
Automation here is boring on purpose. Hourly snapshots to the local drive, a nightly push to the remote, and a retention rule that keeps the last 7 days, 4 weeks and 6 months. On macOS, Time Machine already does the local half if you let it. On Windows, File History plus a scheduled restic task covers it. On Linux, restic with a systemd timer takes twenty minutes to write.
What matters more than the tool is what you include. Be specific rather than complete. My list is five paths: the documents folder, the code directory, the photo library, a password manager export, and a config folder with licence keys and tax files. Everything else on the machine is reinstallable, and trying to back up the whole disk is how people end up with a job that takes nine hours and silently stops running.
Name things so the automation can find them without you adjusting the script every quarter. A job pointed at one stable folder tree keeps working for years, while a job pointed at seven scattered locations breaks the first time you reorganise a project, which is the same argument behind deciding what you should and should not automate in the first place.
A backup you have never restored is a guess
The standard advice stops at scheduling. Set it up, check the green tick, move on. I think that is the single weakest habit in personal automation, because an unverified backup gives you the feeling of safety without any of the substance, and the feeling is what stops you from checking.
Four things commonly fail quietly. The disk fills and the job starts skipping. A credential expires and the remote push returns an error nobody reads. A path gets renamed and one of five folders stops being included. Or the encryption passphrase lives only in the password manager that was inside the backup, which is a loop I have genuinely watched someone discover at the worst possible moment.
So automate the alarm, not just the job. I use a dead man switch: the backup script pings a monitoring URL on success, and if no ping arrives in 26 hours, the service emails me. Healthchecks.io gives you 20 of those free, and Uptime Kuma does it on your own box. This flips the logic in the only way that helps, from noticing a failure to being told about silence, and it is why every automation needs an off switch and a voice.
Then put one calendar event on the first Saturday of each quarter, fifteen minutes, titled restore test. Pick a real file from three months ago, restore it to a new folder, open it. The first time I did this I learned my photo library was excluded by a filter I had written myself. Fifteen minutes, four times a year, is the whole price of knowing.
Your phone is a separate problem
Most people have their phone photos covered and almost nothing else. Messages, voice notes, the authenticator app and anything in a sandboxed app often sit outside the automatic backup entirely.
Two fixes worth an evening. Turn on the full device backup, iCloud Backup or Google One backup, and check the date it last completed rather than assuming it is on. Then export your authenticator seeds or move to a provider with its own encrypted backup, because a lost phone with no exported seeds locks you out of the accounts you need to reach your backups. Run an audit of the rules that quietly fail across both devices twice a year and you will find at least one.
If you do one thing this week, make it the list of five paths. Write them down, point one tool at them tonight, and leave the rest for the weekend.
FAQ
Is Google Drive or Dropbox enough as a backup?
Not on its own. They sync, so deletions and corruption propagate, and version history usually runs out after 30 days. Keep them, then add one versioned backup your computer cannot overwrite.
How often should backups run?
Hourly to a local drive and once a night to a remote copy suits most people. Ask yourself how much work you are willing to redo, and set the interval just under that.
What does a small backup setup cost per year?
Roughly 100 dollars for an unlimited consumer service, or about 70 dollars a year for 1 TB of object storage with restic, plus a one off drive at around 110 dollars.
How do I know the backup is working?
Have the job report success to a monitor that alerts you when it goes quiet, and restore one real file every quarter. A green tick in an app is not evidence until you have opened a restored file.
More in Automation
Automation
Automate Renewal Reminders Before a Subscription Bills
The email arrived at 06:14 on a Tuesday and said thank you for renewing. I had not renewed anything.
Automation
How to Schedule Social Media Posts in One Hour a Week
Posting to social media every day eats small chunks of time that add up to hours, and the posts still go out late, rushed, or...
Automation
Invoice Reminder Automation That Gets Clients to Pay on Time
You finished the job, sent the invoice, and now it is 19 days overdue while you wonder whether chasing it will sound rude.