A backup fulfils its purpose when the required application and matching data can be made usable again. Program versions, settings and other dependencies may be needed alongside data. Grassroot IT therefore considers restarting the supported business process.
Derive requirements from the task
The organisation determines tolerable downtime and loss of recent changes. These limits inform backup scope, method, ownership and retention. Protect backups against unauthorised access and the same harmful events that could affect operational copies.
Name the people responsible for backup and recovery. A copy in an unknown location is insufficient. Required access and instructions must also be available through the intended procedure.
Actually test recovery
A suitable trial restores a saved state in an isolated environment. Check necessary functions and business results. Record the application version, data state, outcome and gaps found.
The Bavarian State Office for Information Security’s backup guidance, version 1.3 dated 10 February 2020, explains this connection. Our specific checks depend on the real application. Include changes to important dependencies in the change procedure.