Section 1 of 5
One card per machine. If you have a list, send it later and fill in what you know.
An order of magnitude is enough. It decides how much space the copies need.
Not the size of the disks: how much actually changes. It decides the bandwidth and the cache.
Section 2 of 5
Where the machines you listed run.
Section 3 of 5
This is the part that decides the price. It is a business question, not a technical one, and there is no wrong answer.
Think of the last hour before the failure. Everything created in that hour and not saved anywhere else is gone. A few seconds means the order someone was typing. An hour means the whole morning’s invoices.
For context: this service can go as tight as two seconds and no looser than one hour. If an hour is still too tight for you, that is a backup conversation, not this one.
Not how long it takes to fix the server. How long your people can keep billing, shipping or answering customers without it.
Yesterday morning. Last Friday. The week before someone deleted the wrong file. Longer history costs more space, so it is a decision, not a default.
This is usually the most useful answer in the whole form. It tells us what actually hurts, not what should hurt on paper.
Section 4 of 5
Which networks the machines you want to replicate are on.
The service connects out to our platform, like a browser to a website. It is one rule, and we give you the exact details in writing.
Section 5 of 5
What we need from your side to install it and run it.
One runs the backup service (8 CPUs, 16 GB, 250 GB of disk); the other moves data between your network and ours (4 CPUs, 8 GB, 100 GB).
Installed inside each machine once, and that is the account it needs. We can work through your IT provider instead.
Windows needs one restart after installation. The only forced interruption, and we schedule it with you.
Done
Check the summary below, then send it to us.