Four hours, stated in the contract.
Every disaster recovery vendor publishes a recovery time. Few will commit to one contractually. Intelssoft states its recovery time in the agreement, with a defined remedy.
Objective (RTO)
Objective (RPO)
availability
failover testing
What the commitment means
A figure published in a datasheet carries no obligation. Where recovery takes eleven hours rather than four, the datasheet provides no remedy, and the responsibility rests with whoever selected the vendor.
Our recovery time is a term of the agreement. It is measured from the moment of declaration, tested to a schedule agreed in advance, and where it is missed, a remedy applies.
The clause is short, and your legal team may review it before any commitment is made.
How the commitment is met
Continuous replication
The recovery site is never more than seconds behind. Nothing is restored from tape or object storage at the moment it matters.
Pre-built target
Network mapping, VLANs and subnets are configured before the incident rather than during it.
Non-disruptive testing
Failover is rehearsed in isolation to an agreed schedule. An untested recovery time is not a commitment.
Agentless
No in-guest software to fail during an incident, and nothing to patch between them.
Ask your current provider to commit to their recovery time in writing.
Then ask us. A disaster recovery architect will review your estate and confirm what can be guaranteed before anything is signed.