Proxmox VE has become the hypervisor of choice for IT teams running cost-effective virtualization — and adoption accelerated significantly after Broadcom’s VMware licensing changes pushed organizations toward alternatives. More than 1.5 million Proxmox hosts are deployed globally, with that number growing.
To see how this works in practice, you can learn how to back up Proxmox VMs step-by-step.
Running Proxmox in production and protecting what’s running on it are two different problems. Proxmox Backup Server (PBS) handles the basics well for small, single-cluster environments. Once infrastructure grows beyond that — multiple clusters, mixed hypervisors, cloud storage requirements, compliance obligations — the gaps in native PBS become operational risks.
This guide covers how Proxmox Backup Server works, where it performs well, where it hits its limits at enterprise scale, and what IT teams need to evaluate when choosing a backup strategy that fits their actual environment.
What Is Proxmox Backup Server?
Proxmox Backup Server is an open-source backup solution developed specifically to complement Proxmox VE.
It backs up virtual machines and containers running on Proxmox hosts with genuine efficiency, using a chunk-based incremental approach that keeps backup windows short and storage consumption manageable for small-to-medium environments. PBS includes built-in deduplication within a datastore, AES-256 client-side encryption, basic retention policy management, and a clean web interface for monitoring backup jobs. For teams running a handful of Proxmox nodes on local or NFS storage, PBS is a solid and cost-effective starting point.
The question isn’t whether PBS is good at what it does — it’s whether what it does is enough for your environment.
How Proxmox Backup Server works
Backup architecture
PBS operates as a separate server (or VM) that Proxmox VE nodes connect to as a storage target. Backups use the vzdump utility built into Proxmox VE, which snapshots VMs and LXC containers and streams them to PBS.
- Chunk-based storage: Data is split into variable-size chunks, deduplicated within a datastore, and stored with SHA-256 integrity verification.
- Incremental backups: After the initial full backup, only changed chunks are transferred — reducing network load and backup window duration.
- Encryption: AES-256 with client-side key management. Data is encrypted before leaving the Proxmox host.
- Pruning and retention: Configurable schedules control how many daily, weekly, and monthly backups are retained per VM or container.
Storage support
PBS stores backup data in datastores — directories on local disk, NFS mounts, or CIFS shares. Each datastore manages its own chunk store, deduplication index, and catalog. PBS does not natively support cloud storage providers like AWS S3, Azure, Google Cloud, or Wasabi. Achieving cloud-tiered backups with PBS requires manual configuration of third-party sync tools outside the PBS interface.
If you’re configuring storage, here’s a detailed guide on setting up Proxmox backup datastores using NFS, SMB, and ZFS.
Recovery capabilities
PBS supports full VM restore directly through the Proxmox VE interface, file-level restore via a FUSE mount, and point-in-time recovery across retained snapshots. Recovery is reliable within a single-cluster environment. Cross-site or cross-hypervisor recovery is not natively supported.
Where PBS works well
PBS delivers genuine value in the environments it was designed for:
- Single Proxmox cluster with local or NFS-attached storage
- Small-to-medium teams managing under 50 VMs
- Environments where all workloads run exclusively on Proxmox VE
- Teams comfortable managing backup infrastructure manually
- Organizations without formal compliance audit requirements
In these scenarios, PBS is free, technically sound, and doesn’t require additional investment. There is no reason to add complexity on top of it unless the environment demands it.
Where PBS runs into limits at enterprise scale
The limitations become operational problems at a predictable point in infrastructure growth. Here is where IT teams run into them:
1. No multi-hypervisor coverage
PBS backs up Proxmox workloads only. If your environment includes VMware, Hyper-V, physical servers, or cloud workloads running alongside Proxmox — or if you are mid-migration from VMware to Proxmox — you need separate backup infrastructure for each platform. That means separate consoles, separate recovery procedures, and separate skills your team maintains.
VMware-to-Proxmox migrations typically span 6 to 18 months. During that window, teams run both hypervisors simultaneously. PBS creates a backup gap for VMware workloads that requires a parallel solution — doubling administrative overhead during an already complex migration.
2. No centralized multi-site management
Each PBS instance operates independently. IT teams managing Proxmox clusters across three data centers have three separate PBS instances with no unified view. Answering basic questions — which site missed its backup window, whether retention policies are consistent across locations, what total storage consumption looks like — requires logging into each instance individually. This does not scale and creates compliance blind spots in distributed environments.
3. No native cloud storage tiering
Enterprise backup strategies like 3-2-1-1 (three copies, two media types, one offsite, one immutable) require backup data to move across storage tiers automatically. PBS handles local and NFS storage well but does not natively write to AWS S3, Azure, Google Cloud, or Wasabi. Achieving cloud-tiered backups requires third-party tooling outside PBS, adding operational complexity and manual processes that introduce human error.
4. No immutable storage
Immutable backups — where backup data cannot be modified or deleted even by administrators — are a core ransomware defense and a compliance requirement for regulated industries. PBS does not support immutable storage natively. For organizations in healthcare, financial services, or government, this is frequently a procurement blocker.
5. Limited compliance tooling
HIPAA, SOC 2, PCI DSS, and ISO 27001 require documented retention policies, comprehensive audit trails, and certified security controls. PBS provides basic retention management and encryption, but lacks the audit logging, compliance reporting, and security certifications that regulated industries require from infrastructure vendors.
At scale, many teams compare PBS with enterprise tools — see Proxmox vs Veeam vs Zmanda comparison.
Proxmox Backup Server storage sizing by environment
Undersizing PBS storage is the most common configuration mistake — especially in environments where VM counts grow faster than storage procurement cycles. Use this table as a baseline:
The Zmanda Pro effective storage figures assume client-side deduplication and forever incremental backups — after the initial full backup, only changed data blocks are captured. The 90% storage reduction figure is typical in enterprise deployments running standardized OS images across VMs.
For CPU and RAM sizing on the PBS server: minimum practical spec is 4 cores and 8 GB RAM for environments up to 20 VMs. For 50 or more VMs with concurrent backup jobs, plan for 8 to 16 cores and 16 to 32 GB RAM to prevent job queuing.
Default port: PBS uses port 8007 for its web interface and API. Proxmox VE uses port 8006 for its own management interface. Ensure port 8007 is open between Proxmox VE hosts and the PBS server.
Proxmox Backup Server vs. Zmanda Pro: Side-by-side comparison
For IT teams evaluating whether PBS covers their requirements or whether a dedicated enterprise solution is warranted:
The decision point for most IT teams: PBS is sufficient when Proxmox is your only platform and your environment stays within a single site. Once you add other hypervisors, require multi-site visibility, need compliance-grade controls, or want cloud storage as a native destination — a dedicated enterprise backup solution closes the gaps PBS leaves open.
For production environments, consider an enterprise Proxmox backup solution that supports centralized management, cloud storage, and immutability.
How Zmanda Pro extends Proxmox Backup for enterprise environments
Zmanda Pro treats Proxmox as one protected platform in a unified backup ecosystem — not as an isolated product with its own silo. This is the practical difference for IT teams managing infrastructure that includes Proxmox alongside VMware, physical servers, databases, or Microsoft 365.
- Agentless Proxmox VM backup
One agent installation per Proxmox host covers all VMs on that node. No agents inside guest VMs means no per-VM maintenance overhead as your environment scales. Backups use Proxmox’s native APIs for host-level snapshots with application consistency. - Unified console across all infrastructure
The same console that manages Proxmox backups also covers VMware vSphere, Microsoft Hyper-V, Windows and Linux physical servers, databases (MySQL, MS SQL, Oracle, MongoDB, MariaDB), and Microsoft 365. One set of policies, one recovery workflow, one dashboard for job status and storage consumption across your entire environment.
For organizations mid-migration from VMware to Proxmox — a process that typically spans 6 to 12 months — this eliminates the parallel backup infrastructure problem. Both platforms are covered simultaneously from day one of migration through final decommission. - Forever incremental with up to 90% storage reduction
After the initial full backup, Zmanda Pro captures only changed data blocks — forever. Client-side deduplication and compression reduce storage consumption by up to 90% across your entire infrastructure. This is the primary driver of Zmanda Pro’s up to 50% lower TCO compared to traditional enterprise backup solutions.
A Fortune 50 customer running 100,000+ workloads including 25TB+ databases achieved 80%+ savings on licensing costs compared to their previous backup vendor. A large US franchisee operator with 2,600+ sites across 44 states reduced storage usage by 89% (10:1 ratio) while enabling a single operator to manage backups for hundreds of sites. - Native cloud storage destinations
Zmanda Pro writes directly to AWS S3, Microsoft Azure, Google Cloud Storage, Wasabi, Backblaze B2, local disk, and NAS/SAN from a single backup policy. Replicate to multiple destinations simultaneously for automated 3-2-1-1 compliance without manual data movement.
For organizations evaluating cloud storage costs: Zmanda Cloud Storage (powered by Wasabi) costs $20,340/year for 250 TB — compared to $113,052 for Microsoft Azure and $125,946 for AWS S3 at the same scale. 3-2-1-1 compliance is achievable in under 15 minutes with a 2-click setup. - Immutable backups for ransomware protection and compliance
Zmanda Pro supports object lock on S3-compatible storage and ZFS local storage — making backup data immutable for a defined retention period. Even administrators cannot delete or modify protected backups during the lock window. This satisfies ransomware recovery requirements and compliance mandates from HIPAA, SOC 2, PCI DSS, and ISO 27001.
For a detailed guide to immutable backup configuration, see: Understanding immutable backups - Recovery: Full VM, file-level, and point-in-time
Zmanda Pro supports full VM restoration directly to Proxmox or any other supported hypervisor, file-level recovery to retrieve specific files without restoring an entire VM, and point-in-time restoration to roll back to a precise state before an incident. Most VM recoveries complete in 15 to 60 minutes.
Common Proxmox backup use cases
1. VMware-to-Proxmox migration
Organizations migrating from VMware to reduce licensing costs need backup coverage for both platforms throughout a migration window that typically spans 6 to 18 months. PBS cannot cover VMware. Zmanda Pro covers VMware vSphere and Proxmox VE simultaneously from the same console — as VMs migrate, backup coverage remains uninterrupted with no staff retraining or new recovery procedures.
For full migration planning guidance: VMware migration services with Zmanda
2. Multi-site enterprise deployments
IT teams managing Proxmox clusters across multiple data centers or geographic locations need centralized visibility into backup status, storage consumption, and policy compliance without logging into each PBS instance individually. Zmanda Pro provides a single management console across all sites with consistent policy enforcement and automated cross-site replication for geographic redundancy.
3. Compliance-driven environments
Healthcare organizations running Proxmox for patient data workloads, financial services firms with PCI DSS or SEC obligations, and government agencies with air-gap requirements all need backup infrastructure that satisfies auditors. Zmanda Pro’s immutable storage, audit logs, SOC 2 Type II and ISO 27001 certifications, and HIPAA BAA availability close the compliance gaps that PBS leaves open.
For healthcare-specific requirements: Protect healthcare data and maintain compliance with Zmanda Pro
4. SMB and mid-market Proxmox deployments
Smaller IT teams adopting Proxmox for its cost advantages often find that PBS requires more manual administration than their team can sustain as VM counts grow. Zmanda Pro’s 15-minute deployment, automated scheduling, and centralized policy management reduce administrative overhead without requiring dedicated backup infrastructure expertise.
See our SMB backup solutions overview: SMB backup solutions for small mid-size businesses
Getting started with enterprise Proxmox backup
If you are evaluating backup options for a Proxmox environment that has grown beyond what PBS was designed for, start here:
- Audit your current environment: How many VMs and containers are running? What other platforms exist alongside Proxmox? What are your RTO and RPO requirements?
- Identify your compliance requirements: Does your industry require immutable backups, audit trails, or specific security certifications?
- Define your storage strategy: Are you targeting local-only, hybrid cloud, or full cloud? Do you need 3-2-1-1 compliance?
- Test before you commit: Any enterprise backup solution worth evaluating should be testable in your actual infrastructure. Zmanda Pro offers a free trial for hands-on evaluation in your own environment.
FAQs
