RES-01
Data resilience and continuity
Backup assessment
Who it's for: any IT department that has not tested a full restore in more than six months, or has no up-to-date record of what it protects.
The problem: a backup platform that runs without visible errors is not a platform that restores. And you cannot properly protect what you have never inventoried: without documented criticality, the same policy applies everywhere.
What I do
- inventory of workloads by type and environment, including forgotten scopes
- classification by criticality, with expected RTOs and RPOs set against those actually delivered
- review of policies, retention periods and backup windows
- verification of application consistency (VSS, database agents, quiescing)
- verification of immutability and of the 3-2-1 rule
- real restore tests on a representative sample
- analysis of failure logs over 90 days
Deliverables
- functional workload specification: inventory, criticality, RTO/RPO, applicable policy
- status report with coverage map
- list of gaps ranked by criticality
- prioritised remediation plan, costed in days
What changes
you hold a defensible record of what you protect, and you know, with evidence, what would restart and what would not.
Prerequisites: read access to the backup console, a technical point of contact, a test window.
Quoted on request — reply within 48h