General EditionThe Daily StandardNo sponsors, no sales pitch

Clear reporting on the choices people actually face.

Technology

Your Backup Vendor's Contract Says You Must Verify Restores. Here Is What That Test Costs

A four-chair dental practice ran its first real test restore after three years of paying for backups. The contract had always said the verification was theirs to do.

A small dental office reception desk after hours with a desktop computer, an external hard drive connected by cable, and a printed service agreement with cla...
A small dental office reception desk after hours with a desktop computer, an external hard drive connected by cable, and a printed service agreement with cla...

A four-chair dental practice in a strip mall had been paying a backup vendor a flat monthly fee for a little over three years. The office manager could point to a green checkmark in a web dashboard every morning. Nobody had ever pulled anything back out. When the practice finally scheduled a test restore on a Tuesday evening after the last patient left, the question was not whether the backup existed. It was whether the practice-management database inside it would open, and how many hours and dollars finding out would consume.

That is the gap this piece is about. The monthly invoice buys storage and a transfer agent. It does not buy a verified ability to resume seeing patients on Wednesday morning. The contract, read closely, says so.

The clause that assigns verification to the customer

Service agreements for cloud backup are not written to promise your data comes back. They are written to promise that a service runs. The operative language varies, but a provision in substantially this form appears in most of them:

Customer is solely responsible for verifying the integrity and recoverability of Customer Data and for maintaining independent copies of any data Customer cannot afford to lose.

Read that twice before reading the uptime commitment. The uptime commitment usually covers the availability of the console and the ingestion endpoint. It does not cover whether a 40 GB SQL database written over 1,100 incremental sessions reassembles into a file the practice software will mount.

Two other clauses matter as much. The first is the limitation of liability, which in these agreements is commonly capped at fees paid over some preceding window, frequently twelve months. For a practice paying a modest monthly fee, that cap is a number smaller than one day of lost production. The second is the data deletion provision, which sets how long copies survive after cancellation or nonpayment. Thirty days is common. If a card expires and nobody notices, that clock is already running.

The National Institute of Standards and Technology is the federal body responsible for publishing guidance on contingency planning and recovery for information systems, and the distinction it draws is the useful one: a backup is a copy, a recovery is a demonstrated outcome. The contract sells you the first and assigns you the second.

What the monthly line item actually pays for

Ask the vendor to break the recurring charge into its parts, because the parts behave differently as the practice grows. Most bills resolve into some combination of these:

  • Protected data volume. Usually billed per gigabyte or in tiers. This grows on its own as imaging files accumulate.
  • Retention and version count. Keeping 90 days of daily versions costs multiples of keeping 14. Retention is often the single largest lever on the bill, and the one set once at signup and never revisited.
  • Endpoints or seats. A per-device or per-server charge, independent of volume. A server license and a workstation license are rarely the same price.
  • Retrieval and egress. Some plans include restores. Others bill per gigabyte pulled down, or charge for a shipped drive. This is the line that only appears on the invoice in the month you have a problem.
  • Support tier. Whether a human answers at 7 a.m. on a Wednesday, and what the response window is in writing.

For the dental practice, the retrieval terms were the surprise. The plan included unlimited restores, which sounded generous until the office manager found the clause capping download speed for accounts in the lowest tier. The data was free to retrieve. The time was not.

The test restore, priced out

The dominant cost of a test restore is labor and downtime, not storage fees. Price it in those units.

The practice needed somewhere to restore to that was not the production server, because overwriting the live database to test the backup is how a small problem becomes a closed office. That meant a spare workstation with enough disk, or a short-lived cloud instance billed by the hour. Then the IT contractor's time: one block to set up the target, one block to run and monitor the restore, one block to open the restored database in the practice software and confirm that yesterday's appointments, last week's X-rays, and the ledger all appear. Hourly contractor rates in your market, times those blocks, is the real number. Ask for it as a fixed-fee engagement with a written deliverable rather than open hours.

Three cost drivers move that figure more than anything else:

  1. How the database is captured. An application-aware snapshot restores as a database. A file-level copy of an open database file may restore as a corrupt one, and discovering that is itself the value of the test.
  2. How far back you need to go. Restoring last night is a short job. Restoring a version from six weeks ago, after a ransomware dwell period, means walking a version chain and may mean multiple attempts.
  3. Where the restore target lives. Pulling 400 GB down a business cable connection is an overnight job. A seeded local copy, or a vendor-shipped drive, turns it into an afternoon.

What a passing test leaves behind on paper

The deliverable is not a green checkmark. It is a one-page record with the date, the backup timestamp restored, the target it was restored to, elapsed time from start to usable, who performed it, and the specific items checked inside the restored data. The practice now has two of these, filed with the service agreement. The elapsed time on the second was under half the first, because the contractor had already written down the steps.

That page is also what an insurer, a lender, or a HIPAA risk assessment asks for. A dashboard screenshot answers a different question than the one being asked.

The practice kept the same vendor. It shortened retention on workstations, lengthened it on the server, moved up one support tier, and put a test restore on the calendar for the first Tuesday of each quarter. The monthly bill moved by a modest amount. What changed was that the office manager can now say how long Wednesday morning would take to arrive.