The problem isn't your backup. It's that it shares your account.

Almost everyone keeps a backup now. Phones sync to the cloud on their own, laptops copy themselves to a provider overnight, and the folders that matter live in at least two places without anyone thinking hard about it. That is real progress. It also hides a quieter problem: a backup only helps if it can fail separately from the thing it is backing up. A lot of the copies people rely on cannot, because the original and the copy answer to the same account.

The failures making news in 2026 are not dead hard drives. They are accounts being switched off. Sony has removed more than five hundred films that customers paid for, tied to a licensing change with StudioCanal, with the titles vanishing from purchased libraries and no refunds offered. It was not the first time; comparable removals hit customers in 2022 and again in 2023. No disk failed in any of those cases. The bytes were fine. What changed was permission, decided on the other end of an account nobody in the story controlled.

The failure you prepared for is not the one that happens

Ask someone how they protect their files and you will usually hear about hardware. A second drive. A RAID mirror. A cloud sync that copies everything off the laptop. Every one of those defends against a drive dying, which is a real risk and worth defending against. None of them defends against the account itself going away.

These are different failures with different shapes. A dead drive is local, physical, and independent: the drive at your house has nothing to do with the drive at a relative's house, so one dying tells you nothing about the other. An account being disabled is administrative and central. It can reach every copy that logs in with the same credentials at once, no matter where those copies physically sit. That is the whole difference. Distance protects you from the first kind of failure and does nothing against the second.

Why sync quietly fails the test

Cloud sync feels like a backup because there are two copies, one on your device and one on the provider's servers. But both copies live inside the same account. Disable that account and you lose the server copy and the client's permission to reach it in the same moment. The file may still sit on your laptop's disk, but the folder that was keeping it "safe" just became a folder that syncs to nothing.

The versioning and the trash folder that providers offer share the same weakness. They are genuinely useful against the everyday accident, the overwrite or the fat-fingered delete, and you should use them. But they are reached through the same login as everything else. A recovery feature that lives behind the account you just lost is not a recovery feature for losing the account. It is the same reason sync is a poor defense against ransomware: the newly encrypted files sync outward, on schedule, to the copy that was supposed to save you.

The thing that actually matters is not how many copies you have. It is how many points of failure they share. Three copies that all unlock with one password are, against this particular threat, one copy wearing a costume.

What an independent copy looks like

A copy is independent when no single credential, provider, or decision can reach both it and the original. An external drive you keep unplugged qualifies, because nothing done to an account touches a drive sitting in a drawer. A small box in your house that holds files on an ordinary filesystem qualifies, because you hold the only key to it. A second cloud provider counts too, as long as it is genuinely separate, with its own login and its own billing, and not the same company behind a different logo.

There is a one-question test. Name the single thing whose loss takes both your primary and your backup. If you can name one, an account, a provider, a password, a company, then you have one point of failure, not two copies. If you honestly cannot, the copies are independent, and that independence is the property worth having. It is also the one people skip, because adding a third copy inside the account you already use feels like progress and asks nothing of you.

The honest tradeoffs

Independence is not free, and it is mostly paid in effort rather than money. A drive you unplug only protects the moment you last updated it; leave it in the drawer for a year and it holds a year-old snapshot. A box you run yourself is a thing you now maintain, and self-hosting does not delete risk so much as move it onto your own diligence and your own mistakes. A home server with no second copy is still one drive failure away from the same total loss, and it will not send a warning email first.

So this is not an argument to leave the cloud. Sync that just works is worth a lot, and for the everyday case it is the right tool. It is a narrower argument: make sure at least one of your copies does not answer to a login someone else controls. Keep the provider you like. Keep the sync. Then add one copy that a disabled account cannot reach, whether that is an unplugged drive, a spare box at a friend's place, or a drive on a device in your own house. Harbor Dock is built to be that last kind of copy: a plain filesystem on a drive you own, reachable from your phone over a private network, holding files that stay yours whether or not some account somewhere else is still switched on. The point is not the box. The point is that the copy survives the account.