Backups operated by someone else
Your own Proxmox Backup Server or BackupPC instance, configured to your retention, replicated offsite to our second Troy facility, and operated by our team.
Backup infrastructure, run as a service
Managed Backups is a private install per customer: your own Proxmox Backup Server for VMs and containers, your own BackupPC instance for general Linux and Windows file-level backups, or both. We run the storage, the dedup, the schedules, the agents, the offsite replication, and the recovery work.
It fits Proxmox shops who want PBS without staffing the operations work, MSPs running BackupPC across a fleet of customer endpoints, and IT teams who own the systems but don't want to own the backup software too. Same engineering team that runs the cloud platform runs the backup platform underneath it.
The platform, plainly
Open-source backup engines, single-tenant per customer, on storage we own.
Proxmox Backup Server for VM and container snapshots. BackupPC for file-level backups of Linux and Windows fleets. Picked per workload.
Every customer gets their own PBS or BackupPC instance. No shared dedup pool, no shared retention table, no shared blast radius.
Replication from the primary instance to our second Troy facility runs on the schedule the contract calls for. Geo-separation without leaving our network.
Where the work happens
Provisioning is ours. We size the dedicated PBS or BackupPC instance to your workload count, change rate, and retention target. We stand up the storage, install the agents, schedule the first full backups, validate restores end-to-end, and document the recovery procedure before we call it live.
Day-2 operations are ours too. Agent upgrades, software patches, storage growth, schedule changes, retention pruning, and the offsite replication run on a schedule we hold. Backup success and failure are monitored from outside the instance; a failed job opens a ticket on our side, not yours. If something starts failing quietly, we notice.
Restores are a ticket away. Single file, single VM, single mailbox, or a full disaster recovery scenario against the offsite copy. We test restores regularly so the path is exercised before you need it, and the test results are available on request. Coverage and credit terms are written into the SLA so the bar is in writing.
Questions backup customers ask first
The ones we hear from teams sizing a real backup story, not a checkbox one.
What backs up well to PBS versus BackupPC?
PBS is the right answer for Proxmox VMs and LXC containers. It runs incremental-forever, deduplicates across snapshots, and integrates directly with the Proxmox UI for restore. BackupPC is the right answer for general Linux and Windows fleets backing up at the file system level, especially desktops, mixed-OS environments, and anything where a file-level restore matters more than a VM-level one. Some customers run both for different parts of the same infrastructure.
Why a private install per customer instead of a shared service?
Restore isolation. A shared backup pool is one bad day from a noisy-neighbor restore window or a cross-tenant exposure conversation. A private PBS or BackupPC instance is yours: your storage, your retention, your dedup pool, your credentials. The trade-off is a slightly higher floor price; the benefit is that a restore at 2 a.m. doesn't queue behind anyone else's.
How does offsite replication work?
The primary instance lives at one Troy facility; the replica lives at the other. Replication runs on a schedule you set, typically nightly for the daily delta and weekly for a full sync. Both ends are on our network, so the replication traffic doesn't traverse the public internet. If the primary goes down, restores can pull from the replica.
What retention do you offer?
Whatever the contract calls for. Daily, weekly, monthly, and annual tiers compose normally; we'll write the schedule that fits your RPO target and your storage budget. PBS dedup keeps the actual storage footprint a fraction of the apparent size on workloads with low daily change. Tell us how far back you need to go and how often you change things; we'll quote what holds it.
Big enough to deliver, small enough to care
Tell us what you're backing up, how often, and how far back you need to go. We'll quote an instance sized to fit and a recovery plan written down.
Get in Touch