The Proxmox Backup Server Setup
Proxmox Backup Server standing behind every guest on your node or cluster, with one of your machines restored from its backup, booted in front of you and timed before we hand anything over.
Most Proxmox environments have backup jobs running. Far fewer have a restore that anyone has watched finish, which is the only version that protects you.
We put Proxmox Backup Server behind every guest on your node or cluster, with retention worked out from how much work you could afford to lose and how far back you need to reach. We generate your recovery key on your own cluster and keep no copy of it.
Then we restore one of your machines from its backup onto a spare ID, start it with the network disconnected, and time how long it takes to reach a login prompt. You finish with that number, plus a written procedure your own team can repeat.
What's included
Proxmox Backup Server standing behind every guest on your node or cluster, including the ones you create after we leave, because the job covers the environment rather than a list that goes stale
A restore you have watched work: one of your machines brought back from its backup, started with its network disconnected so it cannot collide with the original, and timed, with the test copy removed afterwards
A second proof at file level: one file pulled straight out of a snapshot, so getting back a deleted document never means restoring a whole machine
Deduplicated, encrypted copies kept off the machines they protect, with the recovery key generated on your own cluster and held only by you
A retention policy computed from two answers you give us, how much work you could afford to lose and how far back you need to reach, with the arithmetic written down beside it
A weekly integrity check that reads the stored data rather than assuming it, and failed jobs raised on a channel you name, tested with a real message you confirm receiving
Both restore procedures in writing, the recorded evidence behind every check, and a plain-English handover of what is protected and how far back you can reach
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
Root or sudo SSH access to your Proxmox node or cluster, up to three nodes
A machine for the backup server, running Debian 12 or 13 or Proxmox Backup Server, with a local disk mounted for the backups
Two answers from you: how much work you could afford to lose, and how far back you need to reach
One guest of 200 GB or less for the test restore, and a window when we may run it
The person who will hold the encryption recovery key, and where failure alerts should go: email, webhook or Gotify
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Proxmox Audit & Tune-up
We inspect your Proxmox platform against 96 checks, rank what we find by how much trouble it will cause you, and repair the eight worst problems — so you stop guessing what state the machines your business runs on are in.
The Server Admin Day
A senior system administrator works a full day on your server backlog, from the patch level nobody has checked to the backup nobody has restore-tested. Book one day or a run of dates, and each day ends with a written account of every hour.
The Proxmox Cluster
Three Proxmox servers joined into one cluster with working high availability, proved by deliberately killing a node in a window you choose, so you watch the platform recover before you trust anything to it.