Disaster Recovery & Business Continuity : Recovery that has been rehearsed. Continuity the board has signed.
Most firms have backups. Far fewer know how long a restore takes, which systems come back first, or what the business does in the meantime. Golonex sets the objectives, writes the plans, runs the tests, and keeps the evidence — on the platform you already have.
Part of security assurance. Golonex plans and tests recovery; the backup platform is yours or your vendor’s, overseen by the seat.
Objectives, plans, verification, exercises, evidence.
Recovery objectives
RTO and RPO per system, agreed with the business owner and written down — the figures every test is measured against.
Disaster recovery plan
Failover runbooks per system, the order things come back in, who does what, and how you know it worked.
Business continuity plan
How the organisation operates while systems are down: decision rights, communications, manual workarounds, and the return to normal. Written for the board to sign.
Backup verification
Immutable copies exist where the plan says they do, retention matches the policy, and restores actually work — checked, not read off a dashboard.
Exercises
Restore tests on a cycle, tabletop exercises with the business, and failover exercises where the plan calls for them — each with a written result.
Evidence
Objectives, plans, test results, and gap actions mapped to your framework — NIST 800-171 3.8.9, ISO 27001 A.8.13 and A.5.30, PCI DSS 12.10, or the RBI BCP/DR expectations.
Inventory, verify, plan, test.
Inventory and objectives
List the systems that matter, agree RTO and RPO for each with the owner, and record the dependencies between them.
Verify what exists
Check the backups, replication, and recovery environment you already have against those objectives. Write up the gaps.
Write the plans
DR runbooks and the business continuity plan, reviewed with the people named in them, signed by the board.
Test and report
Run the exercises on the agreed cycle. Every result — pass or fail — goes into the monthly report and the evidence pack.
A plan that has been run, not just written.
- Recovery objectives per system, agreed and documented
- DR runbooks and a board-signed business continuity plan
- Restore, tabletop, and failover results — including what failed and what was done about it
- A monthly report and an evidence pack mapped to your framework
The infrastructure the plan recovers — servers, cloud, network — can be run by managed infrastructure, so the people who patch it are the people who rehearse bringing it back.
Disaster recovery & business continuity — your questions, answered
Do you provide the backup platform? +
No. The backup and replication platform is yours or your vendor’s. Golonex sets the recovery objectives, writes the plan, runs the tests, and keeps the evidence. Where your platform cannot meet the objectives, we say so in writing and recommend what would — we do not sell it.
What is the difference between backup, disaster recovery, and business continuity? +
Backup means your data survives. Disaster recovery means your systems come back within an agreed time and to an agreed point. Business continuity means the organisation keeps operating while that happens — who decides, who communicates, what runs manually. This service covers the second and third, and verifies the first.
How are recovery objectives set? +
Per system, with the business owner, during scoping: how long it can be down (RTO) and how much data it can lose (RPO). Those figures are agreed in the engagement, written into the plan, and then tested against — they are not a standard number we quote in advance.
How often are restores and failovers tested? +
On a schedule agreed in the engagement and set by your framework: restore tests on a regular cycle, a tabletop exercise with the business, and a full failover exercise at least annually where the plan calls for one. Every test produces a written result, including what did not work.
Does this cover regulated environments outside the US? +
Yes. For Indian banks and co-operative banks, the plan, the DR drill record, and the board-signed BCP are built to what the RBI expects, and the work runs through our India branch. See the India page for the regulatory detail.
Who runs it? +
A named Golonex engineer owns the cadence — objectives, tests, evidence, the monthly report — with a second engineer briefed for cover. A failover exercise is always a team: infrastructure, application, and business owners together.
How is it priced? +
Fixed monthly pricing by seat, dedicated or fractional, set before the month starts. A six-month minimum for the engineer seat; exercises that need a team are scoped as a team, three to six months.
Find out how long a restore really takes.
Bring your system list and whatever plan exists today. Thirty minutes tells you where the objectives are missing and what the first exercise would test.
Managed delivery — seven practices · All managed delivery →
Managed GCC
Your Global Capability Center — set up, run, and handed over
02Managed talent
Supervised engineering seats in six practices
03Managed software delivery
Teams and builds with a Golonex lead on every engagement
04Managed infrastructure
Azure, AWS, Google Cloud, on-prem, and the data center
Security assurance
Recovery, patching, evidence, identity, and people — tested, not assumed
You are here
Managed Microsoft ecosystem
Microsoft 365, Azure workplace, and Dynamics 365
07Managed process & AI automation
A process lead in your business, automating the work