Picture the small drive on the shelf beside the desk, the one with the blue light that has been on for two years, and consider what you actually know about it. You know it was set up. You know nothing has complained since. What you almost certainly do not know is whether a file put into it in March could be taken back out this evening, in a form that opens, with the folder structure intact and the version you wanted rather than the one from a week later. A backup is not a device or a subscription. It is a restore that has been performed at least once.
Deciding in Advance What You Would Miss
Before touching any software, spend ten minutes listing what would genuinely hurt to lose, because the answer is usually shorter and stranger than people expect. Photographs and video account for most of the volume and most of the grief. Tax records, scanned documents, the folder of contracts, and whatever spreadsheet the household actually runs on account for very little volume and most of the practical damage. Everything else, including the operating system and the applications sitting on top of it, is replaceable by reinstalling, which is tedious rather than tragic.
That list is the specification the backup has to meet, and writing it down immediately exposes the things nobody thought to include. Messages and photographs living only on a phone. A password manager whose vault has never been exported. Email held in a web account with no local copy anywhere. Files inside a work laptop that belongs to somebody else. A backup covering the desktop computer perfectly while missing all four of those is a common arrangement, and it looks entirely healthy right up until the day it is needed.
The Restore Is the Only Test That Counts
Pick three files from the list, ideally stored in different places and different formats, and get them back. Not the backup software's report saying they are present, and not a green tick on a dashboard, but the actual files, opened, with the content still in them. Restore them into a new folder rather than over the originals so nothing is at risk while you experiment. This takes twenty minutes on a healthy system, and it is the only procedure that distinguishes a working backup from a hopeful one.
Two things commonly go wrong at this point, and both are worth discovering on a quiet Tuesday. The first is that the software cannot be persuaded to restore anything at all without a password nobody wrote down, or an account nobody can log into, or an installation of the same program at the same version. The second is that the restore works perfectly and delivers a file that has been silently corrupt for months, backed up faithfully in that condition every night since. Neither problem is fixable at the moment of an actual loss.
Where the Copies Actually Live
The rule of thumb that has survived decades of changing technology is three copies of anything you care about, on two different kinds of storage, with one of them somewhere else entirely. The reasoning is unglamorous: a single drive fails, two drives in the same room burn or flood or get carried out together by the same burglar, and a cloud account can be lost through a billing error or a forgotten login as easily as through anything dramatic. Most households already hold two of the three and quietly believe they have all of it.
The Failures That a Working Backup Still Allows
A synchronizing folder is not a backup, and this is the most expensive misunderstanding in the category. If a file is deleted, overwritten or encrypted on the computer, a sync service will faithfully reproduce that change everywhere within seconds, because reproducing changes is precisely what it was built to do. Versioning and a deleted items window mitigate this, but both have a limit measured in days or weeks, and a problem that goes unnoticed for two months has usually outlived them both.
Ransomware is the case that turns this from theoretical into practical, since it will encrypt anything the computer can write to, including an attached backup drive. The National Institute of Standards and Technology publishes the security framework a great many organizational recovery plans are written against, and the piece of it households benefit from most is simple enough to apply at home: keep at least one copy the working machine cannot reach on its own. A drive plugged in only on the first Saturday of the month is a crude version of the same idea, and it works.
An Hour Now Against a Weekend Later
The evening described here costs about an hour and produces three durable things: a short written list of what is covered, a note of where each copy lives and how to get into it, and the knowledge that a restore has been performed successfully by the person who would have to perform it under pressure. Put the note somewhere a spouse or a colleague could find it, because a backup only one person can operate is a single point of failure wearing a disguise.
Then repeat the restore test once a year, on a date attached to something already in the calendar so it does not depend on anybody remembering. That small blue light on the shelf will keep glowing either way, and it will look exactly as reassuring on the evening the drive has quietly stopped writing as it did on the day everything worked. The light is not the evidence. The file you pulled back out of it last spring is the evidence, and it is worth renewing.