Insights

A backup is the beginning. What about recovery?

The useful outcome is a return to work. Agree what must be recovered, who is responsible and how the restored system will be checked.

Prepared by

English edition published:

Define what needs to be recovered

List the systems and data with owners and priorities. One process may need the latest document; another needs an application, configuration and all its dependencies. Plan for the working result rather than files alone.

Assign responsibility

Agree who checks the backup, investigates failures and decides to restore. Describe access to the backup repository separately from permission to delete data. Those arrangements need to fit the actual environment.

Practise recovery safely

A successful backup message does not prove that the whole system can be used. An agreed recovery exercise needs an isolated environment, recorded results and checks of data consistency, login and a basic business operation.

After the exercise, compare the outcome with the business need. Update missing steps, documentation and contacts, then agree further tests and improvements.

Example: an order-handling application

Suppose a business wants to resume work within four hours and can tolerate losing no more than one hour of new records. These are illustrative requirements to test, not a promise that the existing backup meets them.

Restore the agreed application and data in isolation. Check login, a sample order and an attachment, including configuration dependencies. Prevent the test environment sending messages or carrying out operations in external systems.

Record what the exercise established

  • Which point in time was recovered?
  • How long did restoration and verification take?
  • Who confirmed that basic work was possible?
  • Which permissions, files or instructions were missing?
  • Who will improve the plan, and when will it be tested again?

Backups also need protection from an incident affecting the main system. CISA recommends offline, encrypted backups of critical data and regular tests of their availability and integrity. See the CISA #StopRansomware Guide.

Let’s discuss your needs

What would you like to improve?

A short description is enough to start. You do not need a finished specification.

Tell us about your project Ask a quick question