{"id":1325,"date":"2026-11-16T13:20:00","date_gmt":"2026-11-16T13:20:00","guid":{"rendered":"https:\/\/bhaso.com\/blog\/?p=1325"},"modified":"2026-11-18T22:20:00","modified_gmt":"2026-11-18T22:20:00","slug":"two-backup-habits-compared","status":"publish","type":"post","link":"https:\/\/bhaso.com\/blog\/two-backup-habits-compared\/","title":{"rendered":"Two Backup Habits Compared: The Tick Mark vs the Test Restore"},"content":{"rendered":"<p>Imagine two small companies that sell the same kind of product and keep their customer orders in the same kind of system. One evening both suffer an unlucky accident that wipes the live data. By the next afternoon one of them is shipping parcels again, while the other is explaining to customers why their orders have vanished. The difference was not budget. It was a habit, and the habit has recently picked up a name: BackupOps. The two approaches are weighed below, told through a pair of invented owners, Meena and Farid, who stand for patterns rather than real firms.<\/p>\n<h2>Meet the two habits<\/h2>\n<p>Farid is organised in the way most of us are. He bought a reputable backup service, set it to run every night, and checked the green tick on his dashboard each Monday. When the tick was green he felt covered, and he moved on to things that earn money.<\/p>\n<p>Meena bought a similar service, but she added a ritual. Once a month she picked a random item, restored it into a scratch area, opened it and confirmed that the numbers matched. She wrote the date and the result in a shared sheet. The ritual took about forty minutes. It felt like busywork until the evening it did not.<\/p>\n<h2>What each one measures<\/h2>\n<p>The Ops Atlas, the reference collection run by xOps School, discusses this exact contrast in its <a href=\"https:\/\/www.xopsschool.com\/backupops\/\">write-up of BackupOps as restore engineering<\/a>. Its blunt view is that the share of jobs that finish successfully is a vanity metric. The Atlas illustrates this with a worked example of six business assets: 1,188 of 1,200 jobs succeeded, which sounds like 99 percent, yet only one of the six assets could be shown to be recoverable, roughly 17 percent. Farid&#8217;s Monday tick is the first number. Meena&#8217;s sheet is the second.<\/p>\n<p>Put plainly, Farid measures effort, and Meena measures outcomes. Effort is cheap to show and feels reassuring. Outcomes take a bit of work to collect and sometimes deliver bad news, which is exactly why they are useful.<\/p>\n<h2>Four points where the habits part ways<\/h2>\n<h3>Where the copies live<\/h3>\n<p>Farid keeps his copies in the same cloud account as his live system, protected by the same administrator login. Meena keeps one copy in a separate account that her daily credentials cannot delete. The Atlas urges readers to count failure domains rather than copies. Several copies that share a login are, in effect, one copy waiting for a single bad moment, whether that is a mistake or a stolen password.<\/p>\n<h3>How fresh the copy really is<\/h3>\n<p>Farid knows that his job starts at one in the morning. What he has not noticed is that the copy only reaches the storage vault at five. The Atlas shows this arithmetic for a nightly job: with that timing, the worst-case gap is around 28 hours, even though the business promised itself a 24-hour limit. Meena added the transfer time to her calculation, so her promise matched reality. The takeaway for owners is simple: delays in moving a copy count as lost time.<\/p>\n<h3>What happens when something fails<\/h3>\n<p>When Farid&#8217;s job fails, he gets an email, and so does everybody else who ignores that inbox. When Meena&#8217;s job simply stays quiet, an alert fires, because her setup watches for the absence of a success signal and sends it to a channel outside the normal production tools. The Atlas makes this same point: silence should raise an alarm, since silence is what a broken job looks like.<\/p>\n<h3>Who is responsible<\/h3>\n<p>In Farid&#8217;s firm, backups belong to everyone, so they belong to nobody. Meena has one named person per important asset. The Atlas warns that shared ownership of restore testing is a recurring root cause in public incidents, including a well-known database outage in 2017 in which several protective layers turned out to be broken.<\/p>\n<h2>What the accident revealed<\/h2>\n<p>On the evening in question, Farid&#8217;s restore started cheerfully and then stalled. The latest copy was incomplete, and the earlier ones were older than he had assumed. He recovered most of the orders from email confirmations and spent a week rebuilding the rest. Meena restored from her separate account, replayed the few hours missing, and was selling again before lunch. She lost an afternoon&#8217;s worth of data, which her policy had already declared acceptable.<\/p>\n<p>Neither owner was careless, and neither was lucky. One of them had simply found out in advance what a restore feels like.<\/p>\n<h2>The costs people forget to compare<\/h2>\n<p>Meena pays more. A second account, a longer retention window and her monthly ritual are all real costs. The Atlas gives a rough sense of scale in its own worked case: a ten terabyte estate with a thirty-five day retention can end up holding about 3.4 times the protected data once primary and vault copies are counted. Storage grows faster than owners expect, and that is a budgeting conversation worth having early.<\/p>\n<p>Against those costs sits an outage that can stop sales for days. For a small business, the comparison is less about technology spending and more about how long you can survive without your own records. Our earlier note on <a href=\"https:\/\/bhaso.com\/blog\/navigating-business-technology-solutions-with-bhaso-com\/\">picking technology for a growing business<\/a> makes a similar point from the buying side, and the piece on <a href=\"https:\/\/bhaso.com\/blog\/mastering-modern-cash-flow-how-to-spot-spending-leaks-protect-digital-payments-and-extend-runway\/\">finding spending leaks and extending runway<\/a> shows why unplanned downtime is such a painful drain on cash.<\/p>\n<h2>Borrowing Meena&#8217;s habit<\/h2>\n<p>You do not need to rebuild anything to start. This week, choose the single dataset your business could least afford to lose and answer three questions. Where does each copy sit, and could one login erase them all? How old is the newest copy by the time it arrives somewhere safe? When did someone last restore from it and look at the result?<\/p>\n<p>If you cannot answer the last one, put a date in the calendar, restore one item and write down what happened. Do the same next month. In a year you will have twelve small proofs, and that record is worth far more than a dashboard that has been green the whole time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A story of two small business owners with identical backup tools and very different outcomes, and what BackupOps says about measuring recovery instead of effort.<\/p>\n","protected":false},"author":6,"featured_media":1326,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[166],"tags":[],"class_list":["post-1325","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-technology"],"_links":{"self":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1325","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/comments?post=1325"}],"version-history":[{"count":1,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1325\/revisions"}],"predecessor-version":[{"id":1451,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1325\/revisions\/1451"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media\/1326"}],"wp:attachment":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media?parent=1325"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/categories?post=1325"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/tags?post=1325"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}