I lost about eighteen months of freelance client work in one afternoon, three years ago now, and I still feel a small phantom flinch whenever I hear a laptop make an unusual clicking noise, even on a device that isn’t mine. My old laptop’s hard drive just died, no warning, no gradual slowdown to tip me off, just a black screen one morning and a very expensive data recovery quote from a specialist afterward that I genuinely couldn’t afford at the time, so most of it was just gone. Contracts, invoices, half finished design files, years of accumulated client correspondence. I’d told myself for ages that I should really set up proper backups, in that vague, low priority way people tell themselves they should really start exercising more, and then the hard drive just made the decision for me in the worst possible way. So this is genuinely the topic I feel most strongly about writing properly, because I think most people are exactly where I was, knowing they should back things up, and just never quite getting around to actually doing it.

The single most important shift I made after that whole disaster wasn’t picking some fancy backup solution, it was just understanding a simple concept that a data recovery technician mentioned to me almost in passing while delivering the bad news about my dead drive  the 3 2 1 rule. Keep three copies of anything genuinely important, on at least two different types of storage media, with at least one of those copies stored somewhere physically separate from your main location. It sounds almost obsessively cautious when you first hear it, but the logic clicked for me instantly once I thought about my own situation  if I’d had even one additional copy sitting somewhere other than that exact same laptop, none of that eighteen months of work would have actually been lost.

On Windows, the built in tool most people don’t realize is sitting there ready to use is File History, and I genuinely wish someone had pointed me to it years before my hard drive died rather than after. You can find it by searching “File History” directly in the Start menu, and once you’ve connected an external drive  even something as simple and cheap as a basic USB hard drive from any electronics shop  File History will automatically, continuously back up your Documents, Pictures, Desktop, and other key folders on a schedule you configure, by default checking for changes every hour. What I appreciate most about it now is genuinely the “set it and forget it” nature of the whole thing  once it’s configured, it just quietly runs in the background, and you don’t have to remember to manually copy files anywhere ever again, which was honestly my actual failure mode before, remembering to do it manually and just… not, for months at a stretch, because manual backup is exactly the kind of task that’s easy to keep postponing indefinitely.

For Mac users, Time Machine is genuinely one of the more elegant built in backup solutions I’ve encountered across either operating system, and if you’re on a Mac and not using it already, I’d genuinely stop reading this and go set it up before finishing the rest of this piece. Plug in an external drive, and macOS will actually prompt you directly, asking if you’d like to use it as a Time Machine backup disk. Say yes, and from that point forward it automatically backs up your entire system, not just specific folders, on a rolling schedule, keeping hourly backups for the past day, daily backups for the past month, and weekly backups going back further, which means you’re not just protected against total drive failure but also against the more mundane disaster of accidentally deleting or overwriting a file three weeks ago that you only just now realized you needed back.

Local backups solve the “my drive physically died” problem, but I think it’s worth being honest that they don’t fully solve everything, because a backup drive sitting right next to your main computer doesn’t protect you against a house fire, a theft, or honestly just misplacing the external drive itself, which I’ve genuinely done before with a much less critical backup drive, and the mild panic of frantically searching for it taught me something about why that “1” in the 3 2 1 rule, the off site copy, actually matters in practice rather than just in theory. This is where cloud backup comes in, and I want to be specific here because I think people often conflate cloud sync services with actual backup, and they’re not quite the same thing even though they overlap usefully. Something like OneDrive on Windows, or iCloud Drive on Mac, syncs specific folders to the cloud and keeps them updated across devices, which is genuinely useful and does provide a real degree of off site protection, but it’s worth understanding that sync generally mirrors changes both ways  if you accidentally delete a file locally, that deletion often syncs to the cloud copy too, within whatever grace period the recycle bin or trash retention offers before it’s genuinely gone everywhere.

For something closer to a true, independent backup rather than just synced mirroring, I ended up setting up a dedicated cloud backup service, Backblaze specifically in my case, which for a fairly modest monthly fee just continuously backs up your entire computer in the background, maintaining actual version history over time rather than just mirroring your current state. I’ll be honest, paying a recurring subscription for this felt like an unnecessary expense right up until I actually needed to restore a single accidentally overwritten file about eight months after setting it up, at which point the modest yearly cost felt laughably cheap compared to what I’d lost in that original hard drive disaster.

Something I’d genuinely encourage anyone setting any of this up to actually do, and something I skipped for embarrassingly long myself, is testing an actual restore at some point after setting up your backup, rather than just trusting the setup process worked correctly and never verifying it. I did this a few months after configuring File History on my current laptop, deliberately restoring an old version of a document just to confirm the whole pipeline genuinely worked end to end, and honestly felt a small, disproportionate wave of relief watching the file come back correctly, given how directly it connected to my worst previous experience with exactly this kind of thing going wrong.

If I’m honest about the actual emotional core of all this, beyond the practical setup steps, it’s that backing up your files isn’t really about the technology at all, it’s about not repeating a very specific, very avoidable kind of loss that I genuinely didn’t understand the real weight of until it happened to me directly. Eighteen months of work, gone in an afternoon, over something that would have cost me maybe an hour of setup time and the price of a cheap external hard drive to have prevented entirely. I don’t think I’m being dramatic saying that hour is genuinely one of the best investments of time most people reading this could make this week, even though, I get it, it doesn’t feel urgent at all right up until the exact moment it very suddenly, very expensively does.