RES-03
Data resilience and continuity
Disaster recovery and secondary site design
Who it's for: an organisation that must guarantee the recovery of a critical system after a disaster, and has to choose between a physical site, a sovereign cloud and a public cloud.
The problem: a written recovery plan is not a recovery plan. Without an RTO/RPO matrix validated by the business, without a sized replication architecture and without a tested failover plan, the document remains an intention — and without a costed comparison of hosting scenarios, the investment decision is made blind.
What I do
- gathering of business requirements and construction of the RTO/RPO matrix
- classification of applications by criticality and identification of the dependencies between them
- sizing study for the secondary site: compute, storage, network and inter-site bandwidth
- comparison of hosting scenarios — internal physical site, sovereign cloud, public cloud, or a hybrid model — on achievable RTO, data sovereignty, cost and reversibility
- design of the replication architecture and of the flows to the remote site
- definition of failover, failback and degraded-mode procedures
- offsite copy of backups through backup copy jobs, including seeding of the first synchronisation
Deliverables
- RTO/RPO matrix validated by the business
- architecture document for the secondary site: flow diagrams, components, roles, justified sizing
- comparative study of hosting scenarios, with a reasoned recommendation
- budget estimate per scenario: hardware, licensing, hosting, bandwidth and services
- failover and failback plan
- recovery test plan
What changes
a recovery commitment you can defend before an executive committee or a regulator, and an investment decision based on compared scenarios rather than on a single quotation.
Prerequisites: access to the application inventory and data volumes, a business contact to arbitrate RTOs and RPOs, the regulatory constraints on data location.
Quoted on request — reply within 48h