Français
English
Español
Deutsch
NorskPractical guide
Prepare backups and test service recovery
Define RPO and RTO, map dependencies and prove that copies can restore a working service.
Practical guide
A case to prepare your project
An application loses its server. Recovery needs not only the database but uploaded files, configuration, keys and DNS. The exercise rebuilds a usable service independently of the lost server.
Illustrative scenario, to adapt to your organisation.Prepare and perform the checks
Set acceptable limits
Business owners define tolerable data loss and interruption. Translate these into RPO/RTO, copy frequency, retention and recovery order.
Protect copies and access
Inventory data, files, configuration and required secrets. Separate copies from the main system and protect deletion according to the chosen arrangement.
Rehearse in isolation
Restore without sending real messages or payments. Check integrity and a business journey, measure timing and record gaps.
A reusable acceptance checklist
Agree thresholds, owners and test data before testing. Retain dated results, exceptions and the acceptance decision.
| Check | Expected result | Evidence to retain |
|---|---|---|
| Complete coverage | Components needed for the service are inventoried and recoverable. | Dependency list and available copies. |
| Protected copies | Compromising the application account cannot remove every backup. | Privilege, separation and retention review. |
| Functional restoration | Data, files and access work in the recovery environment. | Dated business-journey test. |
| Measured objectives | Actual duration and recovered data point are compared with targets. | Exercise timeline and RPO/RTO gaps. |
Decide using evidence
A target becomes demonstrated capability through a representative exercise. Assign corrections, schedule the next test and preserve required keys. An exit plan includes exports, documentation and control of the domain name.
Standards and reading
References checked on .
Relevant ISO standards
- ISO/IEC 27017:2026
Clarify cloud security and shared responsibility.
- ISO 22301:2019 (+ Amd 1:2024)
Connect recovery with continuity needs.
- ISO/IEC 20000-1:2018 (+ Amd 1:2024)
Structure operations and service review.
These standards help define scope and expected evidence. Citing them does not certify Salott-IT or establish your project’s conformity. A dedicated assessment is required. Include applicable amendments when scoping the engagement.
Technical documentation
Reference books
- Site Reliability Engineering · 2016 edition
Betsy Beyer, Chris Jones, Jennifer Petoff & Niall Richard Murphy (eds.) · Google / O’Reilly
- The Practice of System and Network Administration · Volume 1, 3rd edition
Thomas A. Limoncelli, Christina J. Hogan & Strata R. Chalup · Addison-Wesley · 2016
Original synthesis based on official summaries, open documentation and publishers’ public descriptions or contents. Books are selected references, not a universal ranking. Copyrighted book and standards text is not reproduced.
Start with your actual situation.
Scope, responsibilities, timing and acceptance criteria will be defined in the proposal.