How to test a Disaster Recovery plan properly
A practical guide to testing service recovery, including scenarios, dependencies, success criteria, evidence, limitations and retesting.
Read the articleInsights
Technical explanations grounded in operational work
Articles and guides for infrastructure teams working through recovery, modernisation, automation and cloud-estate decisions.
Published
Latest insights
What evidence should a Disaster Recovery test produce?
The records a DR test should retain to show its scope, technical results, service validation, limitations, decisions and required actions.
Read the articleYour RTO says four hours. Can you prove it?
How to compare a stated recovery time objective with the full measured route from disruption and invocation to a usable, accepted service.
Read the articleWhat an Azure inventory should prove before governance work begins
A useful Azure inventory establishes scope, coverage, relationships and provenance before it is used to prioritise governance or optimisation work.
Read the articleHow to assess VMware options without starting with an exit assumption
A VMware decision should compare credible estate and workload options against evidence, rather than treating retention or migration as a predetermined answer.
Read the articleBackups are not Disaster Recovery
Why successful backup jobs do not prove that a critical service can recover, and what infrastructure teams should validate instead.
Read the articleApply it to your environment
Want to apply this thinking to your environment?
Cygnus can turn the same practical questions into a technical review, clear findings and a prioritised action plan.