AvailableSold on its ownCloud (SaaS)On-premisesAir-gapped

TotalHealDisasterRecoverDisaster Recovery

Recovery plans that bring servers back at another site in order, with health checks, and drills that measure the real recovery time.

Trial: 30 days. You sign in to the TotalHeal console with a Sttiz account and activate DisasterRecover Disaster Recovery. No card.

TotalHeal DisasterRecover Disaster Recovery icon
The problem

Most disaster-recovery plans are documents. Nobody knows the real recovery time until the day it is needed, and on that day steps get skipped under pressure.

DisasterRecover turns the plan into a runbook the system enforces: servers recover in order at the DR site, health checks prove they work, people confirm the gates, and quarterly drills measure the recovery time you would really get.

What it does

DisasterRecover Disaster Recovery, feature by feature.

Plans in order

Recovery groups in order; each server mapped to the DR server it recovers on, original paths or a folder, and health checks (HTTP status, TCP connect, path exists).

Targets and readiness

RPO and RTO targets, worst restore-point age against the RPO, DR servers not seen for an hour, last drill and when the next is due.

Failover runbook

A second person declares the disaster; points are frozen; the newest clean, verified point is selected; groups recover in order; health checks run; DNS switch and business sign-off are confirmed steps; a report closes it.

Non-disruptive drills

Every group restores into a scratch folder on the DR server, is cleaned up and reported — every 90 days by default, started by the schedule.

Measured, not assumed

Achieved RTO, worst RPO, targets met, files and bytes restored, checks passed and failed, and findings, kept for audit.

No skipped gates

A run never skips a gate; a failed step fails the run with its reason.

Architecture

How DisasterRecover Disaster Recovery works.

DisasterRecover turns the DR plan into an enforced runbook: servers recover in order at the DR site, health checks prove they work, people confirm each gate, and scheduled drills measure the recovery time and data age you would really get.

DisasterRecover Disaster Recovery reference architecture: Runs restore the selected points onto DR servers in order; every gate waits for a person; reports record the achieved RTO and RPO.
Runs restore the selected points onto DR servers in order; every gate waits for a person; reports record the achieved RTO and RPO.
  1. DeclareA second person declares the disaster.
  2. SelectThe newest clean, verified point per server is frozen and chosen.
  3. RecoverGroups recover in order on the DR servers.
  4. ValidateHealth checks run; DNS switch and sign-off are confirmed.
  5. ReportAchieved RTO, worst RPO and findings are kept.

Platforms and deployment

Platforms

DisasterRecover Disaster Recovery platforms
PlatformHow it is covered
Linux serversProtected by TotalHeal RecoveryVault, with the TotalHeal agent at the DR site

Deployment

DisasterRecover Disaster Recovery deployment options
ProfileStatus
SaaS (India region)AvailableSingle-region service.
On-premises control planeAvailableDelivered with our team from the on-premises kit.
Air-gappedAvailableOffline kit, offline licence file and offline update bundles.
Pricing

Unit and tiers.

Priced per protected server per year. Counted: servers in a DR plan. List prices are not published yet — our team quotes per unit and term.

DisasterRecover Disaster Recovery tiers
BusinessEnterprise
Plans, readiness, failover runbook, drills, reportsIncludedIncluded
PriceContact salesContact sales

DisasterRecover is sold on its own and needs RecoveryVault.

Government profile. Government is a profile, not a separate tier or price list: the Elite tier with Government defaults switched on — data residency in India, four-eyes approval of policy changes, a distinct approver for every approval-level action, retention of at least 180 days, and the CERT-In and DPDP reporting clocks.

All business products: units and tiers →

What you need

  • TotalHeal RecoveryVault
  • A server at the recovery site with the TotalHeal agent
For government and tenders

Procurement documents for DisasterRecover Disaster Recovery

The datasheet is public. The full dossier is sent on request, so we can match it to your tender.

  • Datasheet. What the product does, platforms, deployment profiles, tiers and honest limits.
  • Compliance matrix. Each requirement marked comply, partial or no, with an evidence reference — CERT-In directions, DPDP, ISO 27001 controls touched, accessibility of the console, data residency.
  • Bill of materials. SKUs per sizing, the unit and quantity formula, customer-side components and services.
  • Architecture and hardening. How the product is deployed and the hardening guidance for each component.
  • SLA. Support tiers, response targets the team can meet, update cadence and end-of-life policy.
  • OEM authorisation letter. A MAF template for resellers and system integrators, with product names exactly as on the SKU.

Works well with

Talk to us

Get a quote for DisasterRecover Disaster Recovery.

Tell us how many protected servers you need and how you want to deploy. We reply with a quote and the procurement documents you ask for.

Or email business@totalhealsecurity.com.

We use your details only to reply. You can also write to business@totalhealsecurity.com.