Start here.
Ask the person who looks after the app to restore a sample into a safe test area. Have someone who does the work open a familiar job, check its attachments, and explain what they could do next. Record how recent the copy is, how long the test took, and which parts still need checking.
- Choose a job with records and attachments your staff can recognise.
- Ask the supplier to show the restore in a separate test area.
- Record which changes might be missing and who would put them back.
Pick one job you would need to finish tomorrow
Imagine a sign shop whose job app holds approved artwork, install addresses and notes from the crew. A supplier says the backup runs every night. The owner wants to know whether the installer could still find the approved artwork and address if the app stopped working.
Choose one job your team knows well. List the few things a colleague would need to carry it on, including anything they open from a link. An order number in the restored app is useful, but the installer still needs the artwork. Ask which parts come back with the order and which depend on another service.
Ask for a demonstration away from live work
Have the person responsible for recovery restore a sample job or an approved copy into a separate, restricted test area. Agree what information can be used and who can see it. Ask them to keep customer messages and other live actions switched off during the exercise.
Before the demonstration, agree what success looks like. Ask a colleague who normally does the job to find it, open the right attachment and explain the next step. If the supplier can only show a downloaded file, record what the file contains and which parts of the working app still need testing.
The Canadian Centre for Cyber Security recommends regularly verifying that the way you restore backups works. Start with a small rehearsal and ask your provider how it fits into their wider recovery tests.
Write down two different times
First, ask how recent the recovered information is. In a hypothetical Tuesday test, suppose the copy contains changes through Monday at 6 p.m. Any jobs added or changed after that point need to be checked against another record. Name the person who would do that and where they would look.
Next, time how long it takes to get to a usable result. Record when the test starts and when the colleague can finish the agreed task. Ask separately how long it could take to reach the right person and arrange a restore during an actual interruption. A timed test of one job gives you a starting point for that conversation.
Keep a short record of what the exercise proved
Write down the copy date, the job you chose, the result and the missing pieces. Include any step that needed help from someone outside the test. In the sign shop example, the crew might be able to read addresses but still have to call the office for artwork.
Decide what needs a follow-up demonstration. If the exercise used a supplier’s account, check how your team would get access. If it proved that one job could be opened, ask what a larger test would need to cover before the whole team could work again.
| Check | Example result | Follow-up |
|---|---|---|
| Find an install address | The job opens and the address matches the approved record. | Check whether a later address change is missing. |
| Open the approved artwork | The job opens but the artwork link needs access to another service. | Ask who can restore or grant access to the file. |
| Give the crew their next task | The install notes are visible in the test copy. | Show how staff would get those notes if they cannot sign in to the live app. |
Agree what people do while they wait
Ask where staff should record new jobs during an interruption and who checks them against the restored records. The sign shop could use an agreed temporary job list. After recovery, someone needs to check which entries were already saved, which changed later and which must be entered.
Keep the supplier contact and the recovery instructions somewhere the designated staff can reach when the app is unavailable. Repeat the relevant parts of the exercise when important records, connected services or responsibilities change.
Send a simple request to your supplier
Use these details to agree on a restore test your team can take part in.
- The job
- Name a sample job and list what staff need to open and check.
- The test area
- Agree which data you can use and who will keep test activity separate from live work.
- The result
- Ask for the copy date, the time to reach a usable result, and a list of anything the test did not cover.
Planning something with a similar workflow?
Discuss your project with usA couple of common questions.
Is a downloaded spreadsheet enough to test recovery?
It can show you have a readable copy of some information. Open it and check a job against what staff need. Ask separately how you would recover attachments, permissions, and the steps people complete in the app.
Should we restore a backup over the working app to test it?
Ask the people responsible to use a separate test area. Agree how it stays isolated from customers, payments and live messages before running the exercise.
What if our provider already runs restore tests?
Ask what their most recent test proved, which parts of your service it covered, and whether you can see a sample job being recovered. Use their evidence to decide what still needs checking.