Practical business guide
Your backup says successful. Can you actually restore a file?
Run a small, authorised recovery exercise without overwriting live files, and record what it proves.

A green backup notification tells you that a job reported success. It does not, by itself, show that your team can recover the right version of a file when a customer is waiting. A small recovery exercise turns that assumption into something you can inspect.
This is a practical guide, not a report of a newly discovered attack. CISA's #StopRansomware Guide recommends offline, encrypted backups of critical data and regular tests of their availability and integrity. The exercise below is AIT Technology's suggested starting point; it is not a complete disaster recovery test.
Agree the scope before touching a backup
Ask the person responsible for backups to approve the exercise. Choose a harmless test document, a separate recovery folder and a time when you will not interrupt a live backup job. Use your provider's documented restore process. If the only option would overwrite production files or restore an entire system, stop and arrange a suitable test environment with your IT provider.
- Create a fictional document with a recognisable sentence such as “Recovery exercise, version one”. Record its filename and creation time.
- Let the normal backup process include it. Confirm the recovery point that should contain that version; do not assume the latest job includes every device or folder.
- With approval, update the test document to “version two”. Keep the original test copy available. There is no need to delete a live file or simulate malware.
- Restore version one into the agreed separate folder. Check the destination carefully before confirming the operation.
- Open the recovered document with an appropriate application. Check its contents, version and relevant metadata, and confirm who can access it.
Record evidence, not just a tick
Write down the backup product, recovery point, person performing the test, destination, start and finish times, expected content and actual result. Record any missing permissions, unavailable credentials or dependency on a single person. Keep credentials out of the test record.
If you compare checksums, compare the restored file with the matching original version, not a later edited copy. A checksum can support a byte-for-byte comparison; it does not prove that an application or an entire business process will work.
Ask two different recovery questions
How much work could we lose? Compare the usable recovery point with the business's acceptable data-loss window. How long would recovery take? Record the observed time, including finding the right backup and gaining access. A single-file result cannot predict the time to rebuild all systems.
Cloud synchronisation and a backup can provide different recovery capabilities. Check your actual retention, version history, deletion recovery, account recovery and isolation arrangements rather than assuming that a synced folder is sufficient.
A successful file restore is a beginning
Repeat the exercise for representative data and, with specialist support, test important applications and dependencies in a separate environment. CISA warns that ransomware can target accessible backups. Review how your backups are protected from compromised accounts and how recovery keys are kept accessible to authorised people.
If you suspect an actual compromise, follow your incident response plan and get qualified help. Do not reconnect a possibly compromised system merely because a backup is available.
Make the next test useful to your business
Choose one process you could not comfortably lose for a day. AIT Technology can help define a recovery exercise and adapt documentation to your systems, departments and responsibilities. Scope and any implementation cost must be agreed before paid work begins.
Source checked 19 November 2026: CISA #StopRansomware Guide. This established guidance is not presented as a new announcement. For broader procedures and printable records, see our cybersecurity operations manual.
