Veeam Continuous Data Protection
Six short sections about your systems. Ten minutes.
That part is ours. If a question does not make sense, choose “I don’t know” and move on.
Section 1 of 6
One card per system, not per server. A system is anything your business would notice stopping: email, the ERP, the file server, the app your sales team lives in.
Write the name your people use, not the server name. “Invoicing” is more useful to us than “SRV-BCN-04”. If one system runs on four servers, say four and name them later.
You will not know every technical detail, and we are not going to pretend otherwise. Disk layout, firmware mode, encryption: we check those with whoever manages your servers. Answer what you know, leave the rest blank.
Section 2 of 6
How your servers are built and who touches them.
The software we protect them with depends on it. If nobody in the room knows, choose “not sure” and we will find out.
A group of servers presented as one. It changes what we can protect and how.
Your own team, an IT company, your cloud provider, or nobody in particular.
An order of magnitude is enough. It decides how much space and bandwidth the service needs.
Not the size of the disks. How much actually changes: new invoices, new photos, new mail. It decides how much capacity and bandwidth the service needs.
Section 3 of 6
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 6
The copies have to travel out of your network and be reachable when you need them. We need to know who controls that path.
The service talks out to our platform, like a browser talks to a website. Usually this needs one rule. We will give you the exact details, in writing.
Separate networks, not Wi-Fi names. “Two, one for servers and one for everything else” is a perfect answer.
Nothing in production is touched. We start a copy on our side to prove it works. Evenings or weekends are normal answers.
Section 5 of 6
What you can give us to run the service, and what you already own.
One runs the backup service itself (about 8 CPUs, 16 GB of memory, 250 GB of disk). The other moves data between your network and ours (about 4 CPUs, 8 GB, 100 GB). Modest servers by today’s standards, and they sit on your side so the data does not leave through one small pipe.
The service is installed once inside every protected machine, and that is the account it needs. We can work with your IT provider instead if you prefer not to hand it over.
It is a normal piece of software, installed once. Some companies have a policy about what runs on production servers; we would rather know now than during the rollout.
Windows servers need one restart after the software is installed. It is the only forced interruption in the whole setup, and we schedule it with you.
It does not stop us protecting them, but it changes how the copy is stored on our side, and we have to plan for it. “Not sure” is a normal answer.
The continuous protection part of the licence sits in the higher editions. If you are on the free Community edition, this service needs an upgrade and we will tell you plainly.
An existing Veeam licence, a reseller you must buy through, a contract that ends soon. It changes how we quote, not whether we can do it.
Section 6 of 6
The last box is usually where the useful surprises are.
You send this back, we read it, and we come back with a call and a short list of gaps. You will not receive a 40-page proposal. You will receive a plan you can argue with.
Done
Check the summary below, then send it to us.