Backups: The One Thing Everyone Skips Until It's Too Late

Of all the tech advice we give, this is the one people most wish they'd taken sooner: back up your data. Drives fail without warning, ransomware can lock up everything in seconds, laptops get lost, stolen, or dropped, and a single wrong click can delete years of photos. When it happens, recovery is often impossible or expensive — but a good backup turns a disaster into a minor inconvenience.

The rule that actually works: 3-2-1

The standard worth remembering is the 3-2-1 rule: keep 3 copies of anything important, on 2 different types of media, with 1 of them stored offsite (or in the cloud). That way no single failure — a dead drive, a house fire, a theft, a ransomware infection — can take out everything at once.

Important: syncing is not backing up

A lot of people assume Google Drive, OneDrive, iCloud, or Dropbox are their backup. They're not — they're sync. If a file gets deleted, corrupted, or encrypted by ransomware on your computer, that change syncs up to the cloud too, and the good version is gone. Sync is convenient, but real backup keeps separate, versioned copies you can roll back to.

The main options and providers

What we recommend, in order. At a bare minimum, turn on the backup already built into your operating system — on Windows that's File History / Windows Backup, on a Mac it's Time Machine. It's free, it's included, and it's far better than nothing. But treat it as the floor: Windows' built-in option leans on OneDrive folder sync with limited free space, so it isn't a true, complete offsite backup. And if File History is the only backup you have, read the last two sections of this article before you rely on it — a Windows update broke it between July and September 2026, and the fix Microsoft shipped on September 22 is an optional update that does not install itself.

For real offsite protection we recommend Backblaze — it quietly backs your whole computer up to the cloud for a low flat price (iDrive, Carbonite, and Acronis are fine alternatives). And if you'd rather not pay a subscription or hand your data to a third party, we've got you covered with our own solution (below) that runs on storage you own.

Local backup: an external hard drive paired with the tools already built into your computer — Time Machine on a Mac, File History on Windows — gives you a fast, free local copy. For a home or small business with several computers, a NAS (network drive) is a tidy central option.

The best setup is usually both: a local backup for quick restores and a cloud backup for the offsite copy — which is exactly the 3-2-1 rule in practice.

Our custom option: your own storage, protected against bitrot

If you'd rather not hand your data to a subscription — or you simply have a lot of it — we also build a custom backup solution that runs on your own storage. We set you up across multiple drives with redundancy, so your backup isn't trusting a single disk. That also protects against "bitrot": the silent data corruption that can quietly creep into files sitting on one drive over the years, where a photo or document slowly goes bad without anyone noticing.

It's the same principle Backblaze uses to keep data safe — spread it across drives so one failing or corrupting disk can't take your data with it — but run on hardware you own. No monthly storage fee, full control of where your data lives, and protection that doesn't hinge on one drive staying healthy. We size it to how much you need to protect and set it to run automatically.

Make it automatic — and test it

The backup that actually saves you is the one that runs by itself, because manual backups get forgotten. Set it to run automatically, and then — this is the step everyone skips — occasionally check that you can actually restore a file from it. A backup you've never tested isn't a backup yet; it's a hope.

How to tell whether your backup actually ran

Almost nobody checks, and the reason is understandable: backup software is designed to be invisible, so silence feels like success. It isn't. Backups rarely fail with a bang. They stop because the external drive got unplugged for a trip and never went back on, because the drive came back with a different letter, because the password on the network share changed, because the destination filled up, because the laptop is never awake at the hour the schedule fires — or, the one nobody thinks to consider, because an operating-system update changed the backup software underneath you. Every one of those failures is silent, and every one of them stays silent until the day you need a file back. That day is a bad day to find out.

On Windows, File History lives in the old Control Panel rather than in Settings: open Control Panel, go to System and Security, and choose "Save backup copies of your files with File History" — that is Microsoft's own label for it. The panel shows when files were last copied. Read that date, and ask yourself honestly whether it is recent enough that losing everything since then would be survivable.

Then do the check that actually proves something, because a status screen can be wrong. Open File Explorer, right-click a folder you know you changed in the last week — Documents, the folder with this year's invoices, this month's photos — and choose "Restore previous versions." The Previous Versions tab is the list of what your backup can genuinely hand back to you. If that tab is empty, or the newest version in it is months old, you are not protected, no matter what the status screen said thirty seconds earlier. This test takes about fifteen seconds and it is the single most useful thing in this article.

On a Mac the equivalent is quicker. Click the Time Machine icon in the menu bar: Apple's own documentation says the top of that menu shows "how much of the current backup is done, or the date and time of the latest backup." If the icon isn't there, look in System Settings under General > Time Machine. Same question — is that date recent, and does the backup disk it names still exist?

If you pay for a cloud backup such as Backblaze, iDrive, Carbonite, or Acronis, open the app on the computer rather than the company's website, and read two numbers: when the last backup completed, and how much is still waiting to upload. A first backup of a full computer legitimately takes days or weeks, so a large "remaining" figure in week one is normal. The same figure unchanged in month three is not — that is a job that has stalled, and stalled jobs do not announce themselves either.

Finally, once or twice a year, restore something. Not in theory — actually pick a file, restore it to a different place such as the Desktop so you don't overwrite the live copy, open it, and confirm it is the version you expected. For a business, restore the thing that would actually hurt to lose: the accounting company file, the client folder, the year's invoices. Put it in the calendar the way you'd schedule a smoke-alarm test. Almost every unrecoverable data loss we get called about involved a backup that someone believed in and nobody had ever opened.

A live example: Windows File History broke in the summer of 2026 — and the fix does not install itself

We are spending a section on one specific bug because it is the cleanest illustration of the point above that we have seen in years — and because File History is the backup a lot of our customers are relying on right now, on our advice.

The first stage is the one that matters most, because it was invisible. On July 28, 2026, Microsoft released the optional preview update KB5101684 for Windows 11 24H2 and 25H2 (builds 26100.8973 and 26200.8973). Its release notes include a fix aimed at File History itself: "This update fixes an issue that affects File History automatic backups to network shares using Server Message Block (SMB). Backups did not work because Windows showed a false ‘invalid credentials’ error when connecting to SMB shares." From that update onward, users began reporting on Microsoft's own Q&A and community forums that File History still appeared to be working — it still wrote files to the backup drive — but the "last backup" time in the control panel stopped advancing, and the Previous Versions tab came up empty even for files that had just been edited and saved. Similar reports followed on Windows 10 22H2 machines after KB5120249 on August 11, 2026. In other words: for roughly six weeks, the part that quietly stopped was the part you only use in an emergency.

The second stage is the loud one. On September 8, 2026, Microsoft shipped that month's security update, KB5124008, for Windows 11 24H2 and 25H2 (builds 26100.9445 and 26200.9445). After it, File History on a lot of machines stopped running at all: the panel opens, but it asks you to connect a drive — while the drive is plugged in, visible in File Explorer, and perfectly able to be read from and written to. "Run now" does nothing. One person reporting it on Microsoft's Q&A site tested it properly across three computers, uninstalling the update to get File History back and reinstalling it to break it again, which is a better piece of evidence than most bug reports contain.

Microsoft has now confirmed it, and the dates matter, because this article said the opposite a week ago. On September 19, 2026, Microsoft added a titled known issue to the KB5124008 support page: "File History might stop working after installing September 2026 Windows update." The symptoms it lists are the ones described above, in Microsoft's own words — a "Reconnect your drive" message "even when a compatible backup drive is connected and functioning properly," a "Last Backup" timestamp that "might not update," and previously backed up files showing "No previous version available." It also adds one detail we did not have, and it is the one that lets you confirm you have this particular bug rather than an ordinary drive fault: Event Viewer may record application crash events referencing FileHistory.exe and KERNELBASE.dll. Three days later, on September 22, the same page gained a resolution line: "This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124010."

There is a catch, and it is why this section is still here rather than deleted. KB5124010 is a preview update — optional and non-security — and optional updates do not install themselves. Leave it alone and the fix reaches you rolled into October's Patch Tuesday on October 13, 2026. To get it now, open Start, then Settings > Windows Update > Advanced options > Optional updates, and in the "Optional updates available" area click the link to download and install it. On Windows 11 24H2 and 25H2 the update is KB5124010 (builds 26100.9550 and 26200.9550); on 26H1 the same fix ships as KB5124006 (build 28000.3086). Both were released on September 22, 2026.

One wrinkle if you are on 24H2, because it stacks awkwardly. Microsoft's own release notes call KB5124010 "the final preview update for Windows 11, version 24H2" — there will not be another optional update on that version for this fix to arrive in. And October 13, 2026 is both the next Patch Tuesday and the day 24H2 Home and Pro stop receiving updates at all. So on 24H2 Home or Pro the fix lands inside what is also your final update, which makes the move to 25H2 that was already on your list rather more pressing. On 24H2 Enterprise and Education, supported until October 12, 2027, the monthly security updates carry on as normal.

So what should you do? The thing not to do is still the advice circulating on every forum thread about this: do not uninstall the September security update and block it. September 2026 was the largest Patch Tuesday Microsoft has ever shipped, and two of the flaws it closed — an elevation-of-privilege bug in the Windows Update stack (CVE-2026-81963) and one in the Advanced Local Procedure Call component (CVE-2026-85880) — were already being exploited in real attacks before the patch existed. Trading two live, exploited vulnerabilities for a backup feature was a bad deal when waiting was the only alternative. It is a plainly worse one now that there is a forward fix that takes two minutes to install.

Then do the part everyone skips. Run the Previous Versions test from the section above — first to find out whether you were affected at all, and then again after you install the fix. That second check is not a formality: Microsoft's resolution is written against the September symptom, the "Reconnect your drive" message, and it says nothing about the July stage, where the backup kept running and the restore list quietly stopped filling. A fix you have installed but never verified sits in exactly the same category as a backup you have configured but never restored from, which is the subject of this entire article. If it turns out you have lost ground, get a current copy off the machine today by any means at all: plug in the external drive and drag your Documents, Desktop and Pictures folders onto it by hand, or turn on a cloud backup and let it run. A manual copy is not a versioned backup and should not be your permanent answer — but a copy from today beats a beautifully configured backup that last worked in July. Two things still to avoid: don't buy a replacement external drive, because the drive was never the problem and a new one will behave identically; and don't settle into the old "Backup and Restore (Windows 7)" tool as a long-term plan, because unlike File History it genuinely is on Microsoft's deprecated-features list and has been for years.

The reason this belongs in an article about why you need a backup, rather than in a Windows troubleshooting post, is the shape of it. Nobody did anything wrong. The drive was fine, the settings were fine, the schedule was fine, and the computer installed exactly the updates it was supposed to install. The backup broke anyway, it broke silently, and the first stage broke the restore while leaving the backup looking healthy. That is precisely what the 3-2-1 rule is for: if File History on the external drive was your only copy, this bug is the whole story, but if you also had a cloud backup running, it was a footnote.

How we can help

We set up backups for homes and small businesses all the time: picking the right mix of local and cloud, automating it so you never think about it, and verifying that it restores. It's the cheapest insurance in technology — and we'd much rather set yours up than try to recover data that was never backed up.