Free tool

DR Planner

Describe what you would need to bring back and how fast. The planner works out how much replica storage that takes, how long the first copy takes over your own link, and what replication costs you in bandwidth every day after that — then sends it to us as an assessment request.

Plan your disaster recovery

Work out what DR would actually involve

Ten questions, and the planner shows the three numbers that decide a DR project: the replica footprint, how long the first seed takes over your link, and the bandwidth replication costs you every day after that. No prices — the figures that set a price come out of the assessment, not out of a form.

What are you running today Replication is agentless, so the hypervisor matters more than what is inside the VMs.
Where it runs
Servers to protect Virtual machines, or physical servers if that is what you run.
servers
Of those, how many cannot wait The ones where an hour down is a problem. Everything else belongs in a slower, cheaper tier — paying to replicate the dev box is how a DR budget dies.
critical
How fast do the critical ones need to be back Your RTO. It is the single biggest driver of what DR costs, because it decides how much has to be running before anything goes wrong.
Storage actually used Used, not provisioned — replication copies what is there, not what was allocated.
TB
How much of it changes in a day If you do not know, 5% is a fair starting point for a mixed estate. We measure it properly during the assessment — this one number moves the storage figure more than any other.
% a day
Restore points kept Restore points are kept on top of the replica. Thirty days of a fast-changing estate can cost more storage than the estate itself — the figure on the right shows you.
days
Uplink at the source site This decides how long the first copy takes. It is the step every DR project underestimates.
Mbps
Anything we should know

Rather talk it through?

If your estate does not fit a form — and plenty do not — tell us what you run and we will work it out with you.

FAQ

Frequently Asked Questions

Why does it not show a price?
Because the three inputs that move the monthly figure most — used storage, change rate and which servers are genuinely critical — are estimates until someone has looked at the estate. A number built on those would be revised downwards in the first meeting, which is a poor start for a service whose whole value is rigour. The assessment establishes the real figures and the quote follows from them.
Is this not just backup?
No. Backup answers can I get the file back. Disaster recovery answers can we trade on Tuesday. The difference shows up in the arithmetic: restoring 4 TB over a 1 Gbps link takes around nine hours before anyone can log in, which is a fine afternoon for a lost file and a disastrous one for a business that has stopped.
Where does the second copy live?
For UAE customers, inside the UAE — Equinix DX1 in Dubai, with Fujairah as the second site. For European customers, Vienna. Data does not move outside the region you chose without your written agreement; that commitment is in the Data Processing Agreement, not just in sales copy.
What will you need from us for the assessment?
An inventory export if you have one — RVTools is ideal for VMware — and an hour with whoever knows which applications matter. Not a procurement process. The point of the call is to replace the guesses in this form with measured numbers.
How long does the first copy take?
Longer than people expect, which is why the planner shows it. 4 TB over a 200 Mbps link is about two days at line rate, and nothing runs at line rate. Where that figure is uncomfortable we seed from disk instead and replicate the difference, which is a decision worth making early rather than discovering in week three.
Do we have to install anything in our VMs?
No. Replication is agentless — it works at the hypervisor, so a mixed estate of Windows and Linux is no harder than a uniform one, and nobody has to approve an agent rollout before the project can start.
Does testing DR mean taking production down?
No, and this is the point that decides whether a DR plan is real. Replicas boot in an isolated network while the originals keep running, so a test is a scheduled afternoon rather than an outage. The usual reason a DR plan goes untested is that testing it means stopping the business — remove that and the test actually happens.