Cloud Backup & Disaster Recovery
Backup-as-a-Service and DR-as-a-Service with defined RPO and RTO tiers, immutable ransomware-proof copies, automated runbooks and rehearsed failover - replicated across Dollu regions on private paths.
≤ 15 s
RPO on the Continuous tier
≤ 15 min
RTO on the Critical tier
2×/year
Full DR tests included
What is Cloud Backup & Disaster Recovery?
Dollu Cloud Backup & Disaster Recovery protects servers, virtual machines, containers, databases, SaaS data and endpoints from loss, corruption, ransomware and site failure. Backup-as-a-Service captures point-in-time copies to immutable storage in a Dollu region of your choice; DR-as-a-Service keeps a warm or hot replica of your production environment in a second Dollu region or PoP, ready to take over within a defined recovery time. Both are delivered over private connectivity from your sites, your Dollu Cloud environment or your hyperscaler accounts, so backup and replication traffic never competes with production internet links.
Recovery objectives are contractual, not aspirational. We define four tiers - Continuous (RPO under 15 seconds, RTO under 15 minutes), Critical (RPO 5 minutes, RTO 1 hour), Standard (RPO 1 hour, RTO 4 hours) and Archive (RPO 24 hours, RTO 24 hours) - and each application is mapped to a tier during onboarding. Continuous and Critical use block-level or database-native replication; Standard uses frequent snapshots; Archive uses nightly backups with long-term retention. Costs scale with the tier so you pay for fast recovery only where the business needs it.
Ransomware has changed what a backup must be. Every backup copy is written to object storage with object lock in compliance mode, so it cannot be altered or deleted for the retention period by anyone - including administrators and including us. Backups are encrypted with keys you control, held in a separate security domain from production credentials, and scanned for indicators of compromise before restore. Isolated recovery environments let you rebuild and validate systems in a clean network segment before reconnecting to production.
DR that has not been tested is a hope. Every DRaaS contract includes at least two full failover tests a year, plus unlimited non-disruptive test recoveries into an isolated bubble network. Runbooks are automated: boot order, network re-addressing, DNS updates, load-balancer changes and application-level checks run from a single orchestrated plan that is version-controlled and reviewed with you after each test. Reports document achieved RPO and RTO for auditors and regulators, including RBI, PCI-DSS and ISO 22301 requirements.
Why choose Dollu for backup & dr.
The advantages of buying from a carrier that owns its network, interconnects and operations - rather than a reseller.
Recovery times you can put in a contract
Each application is assigned a tier with a defined RPO and RTO, tested twice a year and reported on. Business continuity plans reference measured numbers, not estimates.
Backups that ransomware cannot touch
Object-locked, encrypted copies in a separate security domain with keys you hold, plus pre-restore malware scanning and a clean-room recovery environment.
Tested, documented, auditable
Every test produces a report of achieved RPO, RTO and runbook deviations. Auditors get evidence; your team gets a corrected runbook.
Replication that does not compete with production
Backup and replication ride private paths on the Dollu backbone from your sites, Dollu Cloud or hyperscaler interconnects, so production internet links and users are unaffected.
Pay for speed only where it matters
Tiering lets you put a core database on Continuous and a file server on Archive. Storage is priced per protected terabyte with no restore or egress fees.
Capabilities in detail.
Everything included with Cloud Backup & Disaster Recovery - the platform features, options and controls you get from day one.
- 01
Backup-as-a-Service
Agent-based and agentless backup for VMware, Hyper-V, KVM, physical Linux and Windows servers, Kubernetes persistent volumes, Microsoft 365, Google Workspace and endpoints, with deduplication and compression.
- 02
Database-aware protection
Application-consistent backups and log shipping for PostgreSQL, MySQL, Oracle, SQL Server, MongoDB and Redis, with point-in-time recovery and automated restore verification.
- 03
DR-as-a-Service
Continuous block-level replication for VMs and bare metal into a warm or hot standby in a second Dollu region, with orchestrated failover, failback and network re-addressing.
- 04
Immutable and air-gapped storage
Object lock in compliance mode, retention policies from 7 days to 10 years, logically air-gapped vault accounts with separate credentials and optional cross-region copy.
- 05
Runbook automation
Recovery plans define boot order, dependencies, IP and DNS changes, load-balancer updates and post-boot health checks; plans are version-controlled and executed with one action.
- 06
DR testing and reporting
Two full failover tests a year with Dollu engineers on the call, unlimited isolated bubble-network tests, and reports of achieved RPO/RTO mapped to ISO 22301, RBI and PCI-DSS controls.
- 07
Ransomware recovery
Backup scanning for indicators of compromise, immutable copies, isolated recovery environment for clean rebuilds, and integration with Dollu MDR for incident coordination.
- 08
Private replication paths
Backup and replication traffic carried over Dollu MPLS, SD-WAN, DIA or hyperscaler interconnects with QoS marking, so protection windows do not affect production traffic.
- 09
Self-service portal and API
Protection status, job history, restore requests, retention policies and DR plan status in the portal and via API, with alerts on missed jobs or replication lag.
How it works.
From first conversation to live traffic - a tracked, engineer-led onboarding with a named owner at every step.
- Step 01
Classify
We inventory applications and data, agree business impact and map each system to a Continuous, Critical, Standard or Archive tier with an explicit RPO and RTO.
- Step 02
Deploy
Agents, proxies and replication appliances are deployed, private paths are established and initial seeding is completed - over the wire or by encrypted seed device for large estates.
- Step 03
Automate
Recovery runbooks are written and executed in an isolated bubble network until every application boots, addresses correctly and passes its health checks.
- Step 04
Test and certify
A full failover test is run with your team, achieved RPO/RTO is measured and documented, deviations are fixed and the runbook is baselined for production use.
- Step 05
Operate
24×7 monitoring of jobs and replication lag, quarterly restore verification, twice-yearly full tests and annual tier reviews as your applications change.
Who uses this and why.
Typical deployments across carriers, enterprises, platforms and contact centres.
Banks, NBFCs and payment providers
Regulator-mandated DR with documented RPO/RTO, in-country replica sites and evidence packs for RBI, PCI-DSS and ISO 22301 audits.
Hospitals and healthcare
Immutable protection for EHR, PACS and lab systems with clean-room recovery so a ransomware event does not become a patient-safety event.
Contact centres and BPOs
Replicate dialler, recording and CRM platforms to a second Dollu region with SIP trunks re-pointed automatically so agents keep taking calls through a site outage.
Multi-site enterprises
Replace tape and branch-office backup servers with centralised, deduplicated backup over the corporate SD-WAN and a single DR plan for the whole estate.
SaaS and platform providers
Cross-region replication for Kubernetes and databases with tested failover so customer-facing SLAs survive a regional incident.
Technical & commercial specifications.
Key parameters at a glance. Ask us for the full service description and SLA document.
| Tiers | Continuous ≤15 s/≤15 min; Critical 5 min/1 h; Standard 1 h/4 h; Archive 24 h/24 h |
|---|---|
| Workloads | VMware, Hyper-V, KVM, physical, Kubernetes, databases, M365, endpoints |
| Databases | PostgreSQL, MySQL, Oracle, SQL Server, MongoDB, Redis; PITR |
| Storage | Object lock (compliance mode); AES-256; customer-managed keys |
| Retention | 7 days to 10 years; GFS schedules; legal hold |
| Replica sites | Any second Dollu region: Mumbai, Frankfurt, London, Ashburn, Singapore |
| Testing | 2 full failover tests/year; unlimited isolated bubble tests |
| Transport | Private over MPLS/SD-WAN/DIA/interconnect; seed device for bulk |
| Pricing | Per protected TB and per replicated VM; no restore or egress fees |
| Support | 24×7 NOC; P1 response ≤ 15 min; DR engineer on every full test |
How Cloud is priced.
Cloud and hosting are priced per resource - compute, storage, network egress, backup volume - with managed-service tiers on top. Migrations and DR projects are quoted as fixed scope.
We publish the model, not a public rate card - actual rates depend on destination, route class, volume and regulatory cost. See how every Dollu service is priced.
- Per resource: compute, storage, egress, backup volume
- Managed-service tiers per environment
- Reserved-capacity discounts on 12–36 month terms
- Migration and DR projects as fixed-scope quotes
- Billing
- Monthly recurring plus metered usage; itemised resources on every invoice
- Commitment
- On demand, or reserved for 12–36 months
Backup & DR - your questions answered.
The questions customers and carriers ask us most often before they interconnect. If yours is not here, our team answers within one business day.
Still have a question?
Ask our solutions teamRelated services.
Services customers commonly combine with Cloud Backup & Disaster Recovery.
Put a number on your recovery time.
Share your application list and we will return a tier mapping, RPO/RTO targets and monthly pricing for backup and DR within three business days.
