Disaster recovery, rehearsed before you need it.
A recovery site, a tested runbook and a clear way back.
Ransomware hitting now? Call the 24/7 desk
- Total downtime
- 1 h 12 min
- Data at risk
- 6 min since last copy
- NormalCustomers on Mumbai; data copies to Noida.
- Mumbai failsPower, network or ransomware: the site is unreachable.
- DeclaredYour owner says go. We start the runbook.
- SwitchedNoida takes over. Customers are back.
Businesses we’ve hosted and supported since 2009
What is disaster recovery?
Disaster recovery is how you get systems and data running again after a major failure: a site outage, ransomware, a deleted database. It means a second copy, a place to run it, and a tested way to switch.
Different failures, different recovery.
The primary facility or cloud region goes dark.
Fail over to the recovery site from the latest replica.
Replication lag and how fast DNS moves.
Servers are encrypted, and sometimes the replicas too.
Isolate, pick a clean restore point from immutable backups, rebuild, restore.
How recent your last clean, tested copy is.
A table, bucket or mailbox is deleted, by mistake or on purpose.
Point-in-time restore of just that data. No failover needed.
Retention, and whether point-in-time recovery is on.
An update or migration breaks production.
Roll back to the snapshot taken before the change.
Snapshots taken before every change.
Set your recovery limits.
Typical ranges, for planning. We confirm what your systems can achieve.
See what a drill proves.
- Plan Scenario, owner, checks, rollback.
- Fail over Isolated test failover, at a time you choose.
- Prove it Logins, orders, sandbox payments.
- Report Targets met, exceptions, fixes.
- Scenario
- Primary site lost: database and app servers down
- Declared
- 02:00, by the client’s owner
- RTO
- Target 2 h · achieved 1 h 12 min
- RPO
- Target 15 min · recovery-point lag 6 minutes
- Checks
- Login, checkout, sandbox payments, email: passed
- Exception
- DNS TTL too long; lowered to 5 min and re-tested
- Failback
- Back to primary next morning, verified
Fitted around your systems.
Or the tools you already run.
- Virtual machines
- Physical servers
- Cloud VMs
- Databases
- Veeam
- Acronis
- Azure Site Recovery
- Zerto
- Proxmox
- Native replication
- Partner data centre
- Microsoft Azure
- Another cloud region
Know who does what.
Agreed and written into the runbook before anything goes wrong.
| Step | You | ZenoCloud |
|---|---|---|
| Declare recovery | ✓ | |
| Run the failover | ✓ | |
| Check applications | ✓ | ✓ |
| Tell customers | ✓ | |
| Authorise the return | ✓ | |
| Fail back and verify | ✓ |
Disaster recovery pricing.
Itemised: setup, recovery capacity, licences, drills and management · just need backups? See managed backup. Writing your own plan? Use our free DR plan template.
Common questions
What are RTO and RPO?
RTO (recovery time objective) is how long you can be down. RPO (recovery point objective) is how much recent data you can afford to lose. Together they decide the DR setup and its cost.
Is backup the same as disaster recovery?
No. A backup is a copy of data. Disaster recovery adds somewhere to run it, the steps to switch, and a rehearsal that proves it works within your RTO.
What is a DR drill?
A planned, isolated failover to the recovery site at a time you choose, with real checks such as logins, orders and sandbox payments, followed by a report of the RTO and RPO achieved.
Which tools do you use?
Veeam, Acronis, Azure Site Recovery, Zerto and Proxmox, plus native cloud and database replication where they fit better. We work with the tools you already have where we can.
What is DRaaS?
Disaster recovery as a service: the provider runs the replication, the recovery site and the failover for you, usually for a monthly fee. Our Managed DR is DRaaS with scheduled drills.
Does DR help against ransomware?
Yes, with isolated, immutable backups, clean recovery points and a tested restore. Replication alone can copy the damage. Under attack now? Call our 24/7 desk.