A practical way to check whether your important files can return to usable life before something goes wrong
By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.
A glowing bridge connects two manuscript islands, a visual metaphor for giving saved work a route back to use. Original conceptual painting.
There is a particular comfort in seeing a message that says a backup has finished. Something has been copied. The work seems less fragile. You can close the laptop and think about the next task.
That reassurance matters, especially when the files contain something difficult to recreate: a manuscript, a carefully edited recording, years of photographs or the working documents behind a small organisation. But a completed backup is only part of the story. At some point, the saved work may need to come back.
Can you find the right version? Can you retrieve it without overwriting something newer? Will it open in the software you have? Are the images, audio clips or other supporting files there too?
A small recovery rehearsal can help answer those questions while there is time to deal with the surprises. The purpose is not to manufacture a crisis or prove that nothing can ever go wrong. It is to learn whether the route from a stored copy to usable work is as clear as you imagine.
Start with what would be hardest to replace
You do not have to begin by testing every file you own. Choose a small, representative piece of work whose loss would matter, and make sure you have permission to handle it.
Consider an illustrative example: a community group has prepared a booklet for an upcoming event. The finished PDF is easy to find, but the editable document uses photographs kept elsewhere. The person who made it remembers how everything fits together. A backup test that checks only the PDF would answer one question, whether the booklet can be viewed. It would not establish whether someone can revise it for the next event.
Decide what recovery means for the selected work. You might need to read it, edit it, export it or continue a project with its supporting material. Those are different levels of usefulness.
For private or sensitive records, use an authorised process and an appropriately protected test location. A harmless sample may be a better first exercise than copying confidential material into a new folder or device just to see what happens.
Know which protection you are relying on
A file stored somewhere else may be protected in several ways, and the differences matter. A service may synchronise the current file between devices, retain older versions, keep deleted items temporarily or provide a separate backup arrangement. The exact behaviour depends on the product, account and settings.
Ask what happens when a file is accidentally changed or deleted. Does that change reach the other location? Can you recover an earlier version, and for how long? What would happen if you could not sign in to the usual account?
The UK's National Cyber Security Centre describes a commonly used approach called the 3-2-1 rule: at least three copies, on two devices, with one backup offsite. Its guidance also recommends protected offline backups or a suitable cloud backup service and regular restoration tests. These are resilience recommendations, not a guarantee or a claim that any three copies provide equivalent protection. The guidance was published in May 2021 and checked in October 2026. NCSC data-security guidance
The practical question is which failures your arrangement can withstand. Several copies that depend on the same vulnerable account, device or location may share a weakness. Get qualified help when evaluating protection for organisational systems or important sensitive data.
Make the first rehearsal deliberately safe
Begin with the backup service's current official instructions. Look for a supported way to retrieve a copy into a separate location rather than replacing the original. If the process is unclear, stop and ask the provider or administrator before experimenting.
Do not delete your working file to create a test. Do not disconnect essential systems, disable security controls or attempt a full device reset merely to practise. A first exercise should help you learn without putting live work at risk.
For a suitable ordinary document, the rehearsal might involve selecting a known backup version and restoring it into a clearly identified test folder that does not replace the live file. Open that retrieved copy and check its contents. The details will vary by service; some systems require an administrator or a dedicated test environment.
New Zealand's government-backed Own Your Online guidance recommends checking backups through restoration and says an IT service provider can help. It also advises website owners to clarify backup frequency, retention and possible restoration charges with their hosting provider. These are useful questions to resolve before an emergency, rather than assumptions to make from a plan's marketing name. Own Your Online backup guidance
A successful small-file exercise is a starting point. It does not establish that an entire website, database or computer can be recovered in the same way.
Check the contents as well as the filename
A familiar filename can hide an unfamiliar version. Open the restored copy and inspect something you can recognise: a recent paragraph, a particular photograph, a worksheet calculation or an edit made before the selected backup time.
Keep the expected time in mind. A copy made before yesterday's work should not contain yesterday's changes. That is a limit of its timing, not necessarily a malfunction. The important discovery is whether the available recovery point is recent enough for your needs.
In the illustrative booklet project, the team might compare the restored document with the approved event date and check that the photographs appear correctly. They could also confirm that the document remains editable if editing is part of the intended recovery.
Avoid making changes to the restored copy unless the exercise specifically calls for them. Keep it separate from the current working version so that a test does not quietly become another competing master.
For complex or high-stakes records, visual inspection alone may be insufficient. An administrator may need technical integrity checks, application testing or a more formal recovery exercise.
Remember the tools needed to use the files
Data can survive while the environment needed to use it does not. An old project may depend on software, a particular format, linked assets or a service that has changed.
The British Library's March 8, 2024 review of its October 2023 cyberattack offers a serious public example. It reported that unaffected backup sources had been identified in December, but restoring services was hampered by damaged infrastructure and older applications that could not simply be brought back. Its board had approved an 18-month Rebuild & Renew programme in December 2023. That was a recovery plan described at the time, not a statement about the Library's present status or an estimate for other organisations. British Library incident review, March 2024
The lesson to draw is limited but important: having recoverable data and having a working service are related, separate achievements.
For an individual creator, the corresponding question may be much smaller. Can the saved audio project find its recordings? Can the design file locate its images? Is there a readable export as well as an editable original? Keep legitimate software and support arrangements in view, rather than assuming that a folder of files contains everything needed to continue.
Test the route to access without weakening security
A backup is difficult to use if the only recovery instructions are on the device that has failed. The same problem can arise when access depends entirely on an unavailable account or phone.
Check that you understand the provider's supported account-recovery process. Keep necessary recovery information secure and accessible through an appropriate arrangement. Do not place passwords or recovery codes in an ordinary shared document, email them around or turn off account protection to make a rehearsal easier.
In a team, identify who is authorised to request a restore and who can approve it. Knowing that a supplier keeps copies is different from knowing which person can contact that supplier and what information they will need.
A simple note can describe the process without exposing its secrets. It might name the service, the responsible role and the location of the approved instructions. Where access is sensitive, follow the organisation's established security procedures.
If an actual cyber incident is suspected, a routine practice exercise is no longer the right model. Seek appropriate technical help before reconnecting backups or restoring files that could be affected.
Record the gap you discovered
The most useful result of a rehearsal may be something that did not work.
Perhaps the backup excluded a folder you assumed was included. Perhaps you recovered the document but not its supporting images. Perhaps the process worked, yet required more time or assistance than expected.
Record the date, what you tried to recover, the backup version used, whether it opened correctly and any unresolved problem. Keep the record proportionate. A brief, accurate note is better than a large checklist completed without attention.
Separate what was demonstrated from what remains unknown. Restoring one photograph proves something about that photograph and that retrieval process. It does not prove that every file is intact or that recovery would be possible under every failure scenario.
Choose the next improvement from the evidence. That might be correcting backup coverage, clarifying responsibility, preserving a supported export or arranging a broader test with an administrator. There is no need to buy a new service before understanding the gap.
Give important work a believable way home
A recovery plan should fit how the work changes. A project updated every day and an archive that rarely changes may need different arrangements. Revisit the process after meaningful changes to devices, software, accounts or responsibility, and agree on an appropriate testing routine for the risks involved.
The aim is not constant checking. It is enough understanding to replace a vague hope with specific evidence: this copy existed, this version could be retrieved, these contents opened and these limits still need attention.
Your work carries time, effort and decisions that may be difficult to repeat. A careful rehearsal respects that investment. It lets you discover a missing step on an ordinary day, when the original is still there and the next action can be considered calmly.
Which piece of important work would you most like to know you could bring back, and what small, safe test would help you find out?
