Drive on a Shelf Against Copy in a Data Center: Which Failures Each One Survives
The two options fail in completely different ways, which is the actual argument for having both. What matters is which failure you are protecting against.
| Author | Corinne Adeyemi |
|---|---|
| Section | Innovation |
| Published | |
| Length | 933 words · 4 min |

Backup gets discussed as a single decision with two options, and framed that way it produces a stalemate: one camp likes the drive it can hold, the other likes the copy it cannot lose in a fire. Both are right about their own preference and both are answering a question that has not been asked properly. The real question is which failures you intend to survive, because the two approaches fail in almost perfectly complementary ways. Once the failures are named the comparison becomes short, and the answer for most households turns out not to be a choice at all.
The Failures Worth Naming
Five things destroy data and they are not equally likely. A drive dies, which is ordinary and eventually certain. A file is deleted or overwritten by mistake and the mistake is noticed weeks later. A laptop is stolen or left somewhere. A house floods, burns, or is damaged in a storm, taking everything inside it including anything on a shelf. And ransomware encrypts everything reachable from the machine, including, crucially, any backup drive plugged into it at the time. Any backup strategy should be evaluated against that list rather than against a feature comparison, since a system that covers three of the five leaves two open.
What a Local Backup Does Well
An external drive or a small network device attached at home is fast in both directions, which matters more than people expect. Backing up a large photo library takes hours rather than weeks, and restoring a failed machine from a local copy is an afternoon rather than a multi-day download. There is no ongoing subscription, no dependence on a company continuing to exist, and no upload limit imposed by a home internet connection. For the first failure on the list, a dead drive, and for the second, a file deleted by accident, a local backup is the fastest and cheapest answer available.
Its weaknesses are exactly the ones a shelf implies. It is in the same building as the thing it is protecting, so fire, flood and theft take both at once. And a drive left permanently connected is visible to anything that infects the machine, which is why an approach that alternates two drives, one connected and one unplugged in a drawer, is meaningfully stronger than a single drive that never moves.
What a Cloud Backup Does Well
Off-site storage answers the failures a shelf cannot. A house fire, a burst pipe, a burglary and a regional flood all leave the copy untouched, and continuous services also keep previous versions of files, which is what saves you from the deletion noticed six weeks later and from ransomware encrypting everything it can reach. It requires no discipline once configured, which is its largest practical advantage, since the most common failure of any backup system is a human being forgetting to run it.
The costs are equally real. Restoring a large amount of data over a home connection is slow enough to matter during a bad week, monthly fees continue indefinitely, and you are relying on a provider's continued existence and on your own ability to get back into the account. Any household using cloud backup should confirm that recovery does not depend solely on an email account that might itself be compromised.
Two settings decide most of the value and both are worth checking rather than assuming. The first is version history: how far back the service keeps previous copies, since a thirty-day window is ample for an accidental deletion and thin protection against something that has been quietly corrupting files for a season. The second is what is actually included, because many services exclude external drives, virtual machine files, and anything larger than a stated size by default, and those exclusions are usually where the irreplaceable material lives in a household that takes photographs seriously.
Where the Two Sit Side by Side
Set against the five failures, the pattern is clean. A dead drive: both work, local is faster. An accidental deletion: both work if versioning is enabled, and this is the one where the setting matters more than the medium. Theft of a laptop: both work. Fire or flood: cloud only. Ransomware: cloud, or a local drive that was physically unplugged when it happened. There is no column where local wins outright on coverage and no column where cloud wins outright on speed, which is the entire reason the sensible answer is both.
Emergency planning guidance published through the federal preparedness program makes the same point about documents in general rather than about files specifically: a copy that lives only where you live is not a copy for the purposes of a disaster. That is worth extending to the paperwork nobody thinks of as data, insurance policies, deeds, an inventory of what is in the house, all of which are far easier to photograph now than to reconstruct later.
The Step That Makes Any of It Real
A backup nobody has restored from is a hypothesis. Twice a year, pick a file at random, restore it from each system, and open it, which takes ten minutes and is the only way to discover that the drive has been silently failing for four months or that the cloud service excluded a folder you assumed it was covering. Write down what you did and when. The households that come through a bad week well are not the ones with the most sophisticated arrangement; they are the ones who found out in March that the restore works, and could therefore spend a difficult October thinking about something else.
About the author
Corinne writes for readers doing some of the work themselves.