remote-backups.comremote-backups.com
Contact illustration
Sign In
Don't have an account ?Sign Up

Managed vs Self-Hosted Proxmox Backup Server on a VPS

You can run Proxmox Backup Server on a rented VPS for offsite backups. Or you can use a managed PBS target and skip the server administration. Both get your data offsite. The difference is how much of your time goes into keeping it running.

At a Glance

Factorremote-backups.comSelf-Hosted VPS
Monthly cost (2 TB)€17.00€10-25 (VPS + storage)
Setup time5 minutes2-4 hours
Monthly maintenanceNone1-2 hours
PBS updatesHandled by providerYou run them
Security hardeningHandled by providerYour responsibility
MonitoringBuilt-inYou set it up
Root accessNoYes
Multi-client supportDedicated datastoreFull control, unlimited clients
Immutable backupsYes (€3/TB/mo add-on)DIY (manual credential separation)
Geo-replicationYes (€4/TB/copy/mo)DIY (second VPS + sync jobs)
AutoscalingYes (included)Manual (resize volume/disk)

Comparison based on publicly available information as of March 2026.

What Running PBS on a VPS Involves

Installing Proxmox Backup Server on a Debian VPS is the easy part. Keeping it production-ready is where the work lives.

Initial Setup

  • Provision a VPS with 2+ cores, 4+ GB RAM, and enough disk space
  • Install Debian 12 and add the PBS repository
  • Install and configure proxmox-backup-server
  • Set up ZFS pool or ext4 filesystem for the datastore
  • Configure TLS certificates (Let's Encrypt or self-signed)
  • Harden SSH (key-only auth, non-standard port, fail2ban)
  • Configure firewall (iptables/nftables, allow only PBS port + SSH)
  • Create datastore, users, and API tokens

Ongoing Maintenance

  • Apply OS security updates (weekly or via unattended-upgrades)
  • Update PBS when new versions release
  • Monitor disk space and garbage collection
  • Check sync job logs for failures
  • Renew TLS certificates
  • Monitor server health (CPU, RAM, disk I/O)
  • Handle VPS provider maintenance windows and reboots
ZFS on VPS: Most VPS providers don't offer ZFS-formatted disks. You'll run ZFS on top of ext4 or raw block storage, which works but loses some ZFS advantages like native compression and ARC tuning. RAM is often limited on budget VPS plans, and ZFS performance suffers with less than 4 GB available.

True Cost Comparison

Raw VPS pricing looks cheaper. But the total cost includes your time and the risk of things you might miss.

Self-Hosted (2 TB, Hetzner CX32)

  • VPS (4 vCPU, 8 GB, 80 GB): €8.49/mo
  • Additional volume (2 TB): €104/mo
  • OR: smaller VPS + Storage Box workaround

Plus 1-2 hours/month for updates, monitoring, troubleshooting. At €50/hr, that's €50-100/month in time cost.

Cash cost: €15-112/mo
Total with time: €65-212/mo

Managed PBS (2 TB)

  • 2 TB managed: €17.00/mo
  • Setup time: 5 minutes (one-time)
  • Monthly maintenance: 0 hours

Includes server-side verification, pruning support, monitoring, and PBS updates.

Total: €17.00/mo

The cash-only comparison at smaller volumes (using a cheap VPS + Storage Box workaround) can favor self-hosting. But the moment you add the value of your time or the cost of an outage caused by a missed update, managed PBS wins on total cost.

When Self-Hosting Makes Sense

Running your own PBS on a VPS is the right call when:

  • You want full root access and control over every configuration detail
  • You're already managing VPS infrastructure and adding PBS is incremental work
  • You need to serve multiple PBS clients (homelabs, friends, small clients) from one instance
  • You want to run additional services on the same VPS (monitoring, DNS, VPN)
  • You enjoy the learning experience and treat it as a homelab project
  • You have 10+ TB of data where per-TB pricing differences compound significantly

If you're comfortable with Linux server administration and already maintain VPS infrastructure, self-hosting PBS is straightforward.

Features You'd Have to Build Yourself

Self-hosting gives you a PBS instance. remote-backups.com gives you a PBS instance plus protection layers that take real effort to replicate on a VPS.

Immutable Backups

A read-only copy with credential separation that survives ransomware and compromised PBS credentials. On a self-hosted VPS, you'd need to set up a second datastore with separate user accounts, restricted permissions, and your own change-timeout logic. Most people skip this step.

€3/TB/mo. Learn more

Geo-Replication

Automatic replication to separate datacenters every 15 minutes. On a VPS, achieving this means renting a second VPS in a different region, setting up PBS there too, and managing sync jobs between them. Double the maintenance, double the cost.

€4/TB per copy/mo. Learn more

Autoscaling

Automatic storage scaling in 100 GB increments. On a VPS, you resize volumes manually, and most providers require a reboot. Miss a resize and your backups fail silently until you notice.

Included at no extra cost. Learn more

When Managed PBS Saves You Time

A managed target is the better fit when:

  • Backup infrastructure isn't where you want to spend your sysadmin hours
  • You want offsite backups working in minutes, not hours
  • You don't want to worry about VPS security, updates, or certificate renewals
  • Predictable monthly cost matters more than squeezing the lowest per-TB rate
  • You need reliable offsite backups for production workloads, not a side project
  • Your dataset is under 10 TB and the per-TB premium is small in absolute terms

Set up a sync job with client-side encryption and your offsite backup runs itself. Check our pricing page for current rates.

Frequently Asked Questions

Hetzner, Netcup, and OVH are popular choices in the Proxmox community. Look for providers offering Debian 12 images, at least 4 GB RAM, and affordable block storage. Avoid providers that restrict kernel modules (ZFS needs them) or limit disk I/O heavily.

Yes, but with caveats. Most VPS providers give you virtual disks on shared storage. ZFS works on these but can't tune ARC or use hardware-specific features. Allocate at least 4 GB RAM for ZFS. Alternatively, use ext4 for the PBS datastore, which works fine and uses less memory.

At minimum: SSH key-only authentication, firewall allowing only PBS port (8007) and SSH, fail2ban for brute-force protection, automatic security updates, and TLS certificates for the PBS web interface. Consider restricting PBS API access to your home IP range via firewall rules.

Your sync jobs fail until the VPS comes back. PBS handles this gracefully by retrying on the next schedule. But if the outage is prolonged or the VPS loses data, you've lost your offsite copy. Managed PBS providers typically have redundancy built into their infrastructure.

Yes. Point your local PBS sync job at the new managed target and run a full sync. Once the initial replication completes, update your schedule and decommission the old VPS. Your backup history transfers as part of the sync.

Skip the VPS Administration

100 GB free. Native PBS sync jobs, zero maintenance. Set up offsite backups in 5 minutes instead of 4 hours.