Week 7 · Wednesday
What to back up and how to test it
Identify the records and systems your business needs, check what your backups include, and plan a safe restore test that leaves live work unchanged.
Imagine your backup software reports success every night. Then your team discovers that the customer photographs it needs were saved in a folder that was never included.
The backup may have completed exactly as configured. The business still has a gap.
On Monday, we separated saving, syncing, and backing up. Today, we will turn "We have backups" into a more useful statement: "We know what is covered, and we have checked that we can get it back."
You do not need to become a backup administrator. Your role as an owner is to identify what matters, assign responsibility, and ask for evidence that recovery works.
Start with business tasks
Choose the work your team must be able to resume. A Jacksonville contractor might need current estimates and site photographs. A Swansboro shop might need sales records, stock information, and supplier details. These are illustrative examples, not accounts of particular customers.
Use the technology inventory from Week 1, then add a recovery question for each important task:
| Business task | Information to consider | Question to investigate |
|---|---|---|
| Finish an estimate | Measurements, photographs, pricing, and the draft estimate | Are phone uploads and project folders both covered? |
| Manage appointments | Bookings, contact details, and service notes | Can the provider recover a deleted record, and who requests it? |
| Keep the books | Transactions, attachments, and the data needed for reports | What is included in recovery, beyond an exported report? |
| Operate the website | Content, uploaded images, and settings | Who can restore the site and verify that it works? |
The table is a conversation starter. Your actual applications determine the right backup method. A list of file names is not enough if the business needs relationships between records, attachments, or application settings.
Check what is included and what is missing
Ask the person responsible for each service to show you its backup coverage. Look for new employees, recently added devices, moved folders, and new online applications that might fall outside an older plan.
A backup of a laptop does not automatically include information held only inside a cloud application. NIST notes that different cloud services may require different backup approaches, and some information may not be readily available for a conventional backup. NIST: Protecting data from ransomware and other data loss events.
For a subscription application, ask what the provider can restore and whether you need an additional service or supported export process. An export is information copied out of an application into another format. A spreadsheet of transactions may be useful, but it may not recreate the original application, its attachments, or its settings.
Ask for a demonstration of what an export can bring back. If it cannot be imported into the service, record the useful purpose it does serve, such as consulting a historical report.
Include what makes the records usable
Business information can depend on supporting pieces: the correct application, settings, account access, and sometimes an encryption key. The UK's National Cyber Security Centre includes essential system configuration data in its backup guidance. NCSC: Data security.
Consider an imaginary estimating spreadsheet. Recovering the file is helpful, but the person using it may also need a compatible application and a linked pricing file. A copy that opens with broken calculations is not a successful recovery of that task.
Record who manages those dependencies. Keep the location of secure recovery instructions in your plan, rather than copying passwords, recovery codes, or keys into a shared document.
Give backup monitoring a named owner
Automatic backups still need someone to notice when they stop working. Agree who reviews completion reports and failed jobs, who handles an alert, and who covers that responsibility when the usual person is away.
Set a backup schedule based on how much new work the business could afford to recreate. Set retention based on how far back you may need to recover, along with applicable business requirements. There is no single interval that suits every record or application.
The Canadian Centre for Cyber Security recommends defining backup frequency, recovery responsibilities, and routine testing. Canadian Centre for Cyber Security: Backup guidance.
The owner does not have to perform every technical step. They need to know which service or person does it and what happens when something fails.
Test a restore without disturbing real work
A restore retrieves information from a backup so it can be used again. A successful backup notification and a successful restore answer different questions.
Arrange a small test with the authorized person managing your backups. Start with a harmless sample document or approved test data. If the system cannot restore separately without changing live records, have the provider design a safe test.
For the first test:
- Agree on the sample and the expected result. Note what should be in the recovered item and which date or version you want.
- Confirm the destination. Use a separate, access-controlled test location or supported test environment. Leave the current business data untouched.
- Recover the sample through the actual backup process. Do not substitute a fresh copy of the live file.
- Open and inspect it. Check the contents, version, readability, and anything important to using it.
- Record the result and elapsed time. Include delays finding instructions, gaining authorized access, and retrieving the information.
- Close out the test. Assign any fixes and remove temporary test copies through the agreed process when they are no longer needed.
Do not delete an important original to prove that a backup exists. Do not send customer information to a personal account or unapproved device for convenience.
NIST recommends testing whether backup information is usable and measuring recovery activities to find gaps. NIST: Backup testing and monitoring.
Be clear about what the result proves
Suppose your team restores a sample estimate in twelve minutes and confirms its contents. That is useful evidence for the sample and process you tested.
It does not establish that the entire accounting system, every photograph, and all user access can be restored in twelve minutes. A larger recovery can involve different applications, more information, and additional people.
Build confidence in stages. Start with a small restore. Then arrange broader tests for the systems that matter most, with the provider responsible for protecting normal operations.
Keep a short test record:
| Field | What to record |
|---|---|
| Scope | Which item, system, and recovery version were tested |
| Result | What was recovered and what the business checked |
| Time | Start, finish, and significant delays |
| Follow-up | The problem, accountable person, and target date |
A twenty-minute exercise: choose the first test
List three information sets your business would find difficult to recreate. For each, name the business task, storage location, recovery method, responsible person, and last successful test date.
Choose one where the answer is unclear. Arrange a safe test with the appropriate provider or administrator. The exercise is to define and schedule that test, not to make unreviewed changes to a live system.
On Friday, we will use what you learn to answer two business questions: how long can work stop, and how much recent work could you recreate?
Your takeaway: Know what your backups cover, then verify recovery with a controlled test. Record the result, its limits, and the next improvement.
Follow the Small Business Learning Series for new articles on Monday, Wednesday, and Friday at 1 p.m. Eastern.