Re:Tech

A Restore Test Makes a Second Copy. Who Is Allowed to Destroy It

A backup you have never restored is a guess, but a rushed restore spawns copies nobody planned to dispose of, and disposal is governed locally.

The advice to test your backups is correct and almost always delivered without its second half. A restore is not a read operation in any practical sense. It writes your data onto a second machine, a spare drive, a bench laptop belonging to whoever is helping you, and when the test succeeds, that data still exists in every place the test put it. The rushed version of this exercise is worse than no test at all, because it scatters readable copies across hardware you do not track, and nothing in the checklist tells you who is coming to take them away.

The technician on the bench is holding your data, not just your drive

Someone else is usually standing next to this decision. A managed services technician restoring a client file server, a bookkeeper's IT contractor pulling last quarter's ledger off a tape, a hospital records clerk verifying that an archive still opens. That person leaves the job with something. Sometimes it is a scratch drive used as a staging area, sometimes the old array that was replaced mid-test, sometimes a laptop with a mounted image nobody unmounted. The equipment leaves the building in a van. What happens next is not a technical question, and it is not covered by the backup software's documentation.

The honest ones tell you this up front. Ask any competent shop what they do with a decommissioned drive and you get a specific answer: it is degaussed, it is shredded to a stated particle size, it is wiped with a verified overwrite and the verification log is retained, or it goes to a downstream processor whose name they will give you. The vague answer, that it gets recycled, is the one worth pausing on. Recycling is a destination, not a method, and the two are not interchangeable when the drive holds payroll records.

What your state does and does not let you throw away

This is where the rules stop being national. A number of states have banned electronics from municipal solid waste outright, which means the drive you pulled during the restore test cannot go into the dumpster behind the office, and in those states the ban is enforced at the hauler and the transfer station rather than at your loading dock. Other states have no landfill ban at all and rely on manufacturer take-back programs, county collection events, or a permanent household hazardous waste site open two Saturdays a month. The Environmental Protection Agency oversees the broader handling of electronic waste, but the rule that actually governs your parking lot is written closer to home.

The practical effect is that identical restore tests, run the same afternoon in two states, end differently. In one, the old array goes to a certified processor with a manifest and a weight ticket. In the other, it sits in a supply closet for eleven months because nobody could work out where to take it, which is its own security problem dressed up as inertia. Call your county solid waste authority before the test, not after. The person who answers that phone knows which processors are permitted in your jurisdiction and will say so plainly.

Layered on top of the waste rules are the data disposal statutes, and those vary too. Many states require that records containing personal information be destroyed, not merely discarded, when they are no longer retained, and some name acceptable methods while others simply require that the information be rendered unreadable. A few reach further and impose the obligation on the vendor you hired as well as on you. That last point matters when the restore test is being run by an outside contractor, because it decides whether the certificate of destruction is a courtesy or a document you are entitled to demand.

The records clerk knows how long the copy has to live

The other person standing next to this decision is whoever owns your retention schedule. In a medical practice it is the compliance officer working from state law on how long a chart is kept, which is not the same number in Texas as it is in Massachusetts. In a small town clerk's office it is the state archives retention schedule, which is binding and specific and often longer than anyone expects. In a two-person business it is usually nobody, which is how a restore test ends with a spare drive holding seven years of client tax documents that should have been destroyed in year four.

A backup that restores cleanly but contains records you were required to purge is not a passed test. It is a discovery. That is an argument for slowing the exercise down rather than abandoning it, because the same afternoon that proves the archive is readable can also prove what is inside it. Pull a directory listing, check the oldest date, and compare it against whatever schedule applies to your work. The clerk or compliance officer can give you that number in a phone call, and the number is the thing that tells you how many copies you are allowed to keep.

Plan the leftovers before you plan the restore

A test worth running has a disposal line in it. Decide in advance which machine receives the restored data and whether that machine is wiped, retained, or destroyed when the test ends. Decide who signs for the old hardware, what the certificate of destruction has to list (serial numbers, method, date, the name of the downstream processor), and where it gets filed. Book the pickup or the drop-off before you start, so the window between test and disposal is measured in days. The whole plan fits on one page and it converts an open-ended mess into a scheduled errand.

It also changes what you ask a vendor. Instead of asking whether they test backups, ask what leaves the site afterward, who transports it, and what paper comes back. Ask whether they hold a permit in your state and whether the processor they use does. The shops that do this properly answer immediately, because the answer is the same every week and they have already worked out the route. The ones who have never thought about it tell you something reassuring and general, and that gap is the most useful thing you will learn about them.

The reason to slow down is not caution for its own sake. A restore proves the archive works; a planned restore proves the archive works and leaves the building holding exactly the number of copies you intended. Those are different results, and only one of them is finished when the technician packs up.

Yours,

Astrid Vollmer

Astrid writes about rubble, disposal, and what the skip will not take.