Operate//guide // IT management
Has your backup ever been tested? What a restore test looks like
A backup job with a green tick says nothing about how long recovery takes after an attack. What a monthly test involves, who runs it and what gets written down afterwards.
Updated: 15.11.2026 · ~6 min read
DNSC’s annual report for 2025 describes an electrical installation company where an employee opened an attachment in an email that appeared to come from a member of CECCAR, Romania’s body of chartered accountants. One of the company’s computers was encrypted and the attacker asked for 12,000 lei, later 15,000. The company did not pay. It rebuilt the system and data from a backup made about two months earlier (DNSC report, page 12, in Romanian, covered by StartupCafe).
That outcome is better than many in the same report. The report does not say what was lost, but a two-month-old backup usually means the work from that period had to be rebuilt from other sources or is gone. The backup existed. It just was not recent.
The second case was told at the Orange Business conference on 21 September 2026 and reported by Mobilissimo. A company making point-of-sale software had spent “tens of thousands” on backup, with copies in Bucharest and Târgu Jiu and replication to another data centre. The attackers deleted the backup. The recovery data centre was hit by the same attack after services had come back to about 90%. The data was eventually recovered, partly by rolling storage back to earlier states. The company says it now tests recovery in 10 minutes.
“We have a backup” versus “we restored it”
“We have a backup” describes a program that runs at night. “We restored it” describes a person who took the copy, brought it up on another machine and worked with it. Between the two sit the problems you only discover on the bad day:
- the job has been failing for three weeks and the alert goes to a mailbox nobody reads;
- the accounting database is copied while it is running and the resulting file will not open;
- only the previous administrator knew the backup encryption password;
- restoring 800 GB over the office connection takes two days, not two hours.
The 3-2-1 rule and what does not count as a backup are covered in the guide Business backup: the 3-2-1 rule. This one is about the part almost everyone skips: the proof.
What a monthly test looks like
A useful test takes a morning, not a week. A three-month rotation might look like this:
- month 1: the accounting or ERP database, restored to a separate computer. The accountant opens the company file and checks the latest invoices;
- month 2: a Microsoft 365 or Google Workspace mailbox, restored to a test mailbox, with last week’s messages;
- month 3: a whole server or virtual machine, started in isolation from the working network, checking that applications start and users can sign in.
On top of that, every month, a few files chosen by a user rather than the administrator: the contract signed in March, yesterday’s quote, a technical drawing buried deep in a folder. That tells you whether the backup covers the folders people actually use, not only the ones on the server.
What gets written down
One page, signed by whoever ran the restore and whoever checked the data. It records the date, what was restored, from which copy (day and time), how long it took from start to usable data, what failed and what was fixed. After six months you have a real history of restore times instead of an estimate. For companies covered by NIS2, the document also serves as evidence of business continuity measures.
How old can the backup be: RPO and RTO in short
These are two questions for the owner, not for the IT person.
RPO: if the server stops right now, how much work are you willing to redo? A day, an hour, ten minutes? The installation company in the DNSC report effectively had an RPO of two months without ever choosing it.
RTO: how long can you go without the system? A warehouse that cannot issue delivery notes for two days loses orders. The document archive can wait a week.
The answers differ by system. The ERP may need hourly backups and recovery the same day, while one copy a day is enough for the archive. A restore test is the only way to find out whether the promised time is realistic.
The copy an attacker cannot delete
The POS company shows that the number of copies is not enough. If all of them can be deleted with the same account, an attacker who gets that account deletes them all. What changes the picture:
- an immutable copy, on storage that refuses deletion during the retention period even for the administrator, or a physically disconnected copy, such as a disk swapped weekly and kept in another building;
- a separate account for the backup console, with MFA, used for nothing else;
- an alert when someone shortens retention or deletes jobs.
The immutable copy goes into the test rotation too, at least once a quarter. A copy nobody can delete but nobody can restore either is no help.
Restore tests and their documentation can be organised as part of IT management. If your company falls under NIS2, the continuity and backup requirements are explained on the NIS2 page.
FAQ
What companies ask us
How often should restores be tested?
Monthly for the important systems, on a rotation: one month the database, one month email, one month a whole server. A full test, with a server or virtual machine brought up from scratch, at least once a quarter. And after any major change: a new server, a different backup product, a move to the cloud.
Does a restore test interrupt work?
No, as long as it runs on a separate computer or virtual machine, isolated from the network people work on. Staff carry on as usual, and someone from the team is only asked at the end to check the restored data.
Our invoicing software is online. Does the provider’s backup cover us?
It covers the data in that application, under the terms of your contract. Check how long the provider keeps copies, whether you can export the data yourself and how long a restore on request takes. Email, shared files and office computers remain your responsibility.
Who should run the test?
The IT administrator does the restore. Someone who works with the data every day, such as the accountant or the warehouse manager, checks that it is correct. Both sign the report, and someone in management reads it.
When did you last restore anything from backup?
Want to know whether your company’s backup would pass a restore test? We can talk it through.