Proxmox Backup Server vs. Veeam: which backup solution for Proxmox VE?

Have Proxmox Backup Server set up and operated - WZ-IT plans local and external PBS backups, encryption and retention, and takes over day-to-day operations. View PBS offering · Fixed-price restore test

Anyone introducing Proxmox VE or moving from VMware eventually faces the backup question: stay with Proxmox Backup Server (PBS) or use Veeam Backup & Replication, which many teams know from their VMware days? Since version 12.2 from August 2024, Veeam supports Proxmox VE through a dedicated plug-in (12.2 release notes). That turns the decision from a matter of preference into a trade-off between integration, features and cost.

This comparison shows where each solution is the better choice, works through a cost example and explains how the two products can be combined. The PBS fundamentals are covered in What is Proxmox Backup Server?.

Table of contents

• Two products, two approaches
• Where Proxmox Backup Server is stronger
• Where Veeam is stronger
• The differences at a glance
• Cost example: 3 hosts and 30 VMs
• Ransomware protection: 3-2-1 and immutability
• Combine or switch
• Decision guide
• Our approach at WZ-IT
• Further reading

Two products, two approaches

Proxmox Backup Server comes from the same vendor as Proxmox VE and is integrated directly into the virtualization platform as a storage target. A backup job is created in the Proxmox web interface; PBS receives the data, splits it into chunks, deduplicates and verifies it. The software is licensed under the AGPLv3 and is free without feature restrictions. The current release is PBS 4.2 from April 29, 2026 (roadmap).

Veeam Backup & Replication is a cross-platform backup suite for VMware, Hyper-V, Nutanix AHV, Proxmox VE, physical servers and cloud workloads. For Proxmox, a plug-in deploys worker VMs on the Proxmox hosts and writes the data to Veeam repositories. The current version 13.1 supports Proxmox VE 8.2 to 9.2, both standalone hosts and clusters (system requirements). Version 13.1 added VM replication between Proxmox hosts and Instant Recovery to Proxmox.

The fundamental difference: PBS is a specialized tool for the Proxmox ecosystem, Veeam is a central backup platform for heterogeneous estates that treats Proxmox as one source among many.

Where Proxmox Backup Server is stronger

Native integration. PBS needs no worker VMs and no separate management server. Backup, restore, live restore and browsing individual files all run from the Proxmox web interface (File Restore in the PVE docs). New Proxmox releases are supported by the same vendor at the same time.

LXC containers. PBS backs up VMs and containers alike. The Veeam plug-in does not support LXC containers, VM templates, passthrough disks or VM disks on BTRFS storage (Veeam: considerations and limitations). If you run many services in containers, you need a second path for them with Veeam.

Deduplication across the entire datastore. PBS stores identical chunks only once, across all VMs, containers and backup snapshots (PBS docs). According to its own documentation, Veeam deduplicates within each individual backup job (compression and deduplication). With many similar VMs and long retention, this makes a noticeable difference in storage requirements.

Cost and licensing model. PBS is licensed, if at all, per backup server, with unlimited clients and unlimited storage (Proxmox pricing). When the environment grows by more VMs, license costs stay the same.

Simplicity. One Debian-based server, one datastore, one backup job: for many mid-sized environments, that is sufficient and easier to operate than a suite with backup server, proxies, workers and repositories.

Where Veeam is stronger

Application-consistent backup with item-level recovery. PBS creates file-system-consistent backups via the QEMU guest agent, using VSS on Windows (PVE wiki). Veeam goes further: application-aware processing, transaction log backup for SQL Server, Oracle and PostgreSQL with point-in-time restore (guest processing) and Veeam Explorers for individual mailboxes, databases or AD objects. Veeam itself names one limitation: SQL Server in a Windows failover cluster is only backed up image-level through the Proxmox plug-in.

Heterogeneous estates. If VMware, Hyper-V, physical servers or cloud VMs run alongside Proxmox, Veeam covers everything with one console and one portable license. Backups can be restored across platforms, for example a VMware VM directly to Proxmox, with Veeam attempting to install the required VirtIO drivers.

Immutability. Veeam provides true immutability through a hardened Linux repository or object storage with Object Lock (Veeam: immutability). PBS has no comparable WORM mode (see the section on ransomware protection).

Tape and enterprise reporting. PBS can write to LTO tapes and libraries natively (PBS tape backup). Veeam, however, is broader in tape handling, reporting, malware detection and recovery orchestration, especially in the higher editions. If you already have a Veeam tape infrastructure and reporting for audit and management, you keep it.

The differences at a glance

Cost example: 3 hosts and 30 VMs

Assumption: three Proxmox hosts with 30 VMs, backed up locally and to a second copy offsite. Only the license costs of the backup software are compared. All prices as of October 2026, subject to later changes.

Sources: Proxmox PBS pricing, official Veeam store, Foundation Edition. Veeam also sells enterprise licenses through partners at project-specific prices; the store price serves as a reference, and term and tax treatment should be checked in the quote before purchase. The free Veeam Community Edition is limited to 10 workloads and is not sufficient in this example.

Not included in the table: the Proxmox VE subscription for the hosts (identical in both scenarios, see How much does Proxmox cost?), hardware for backup storage, a dedicated backup server for Veeam and an additional backup path for LXC containers. Thanks to datastore-wide deduplication, PBS usually needs less storage for the same retention.

Ransomware protection: 3-2-1 and immutability

A backup only protects against ransomware if an attacker with admin rights in production cannot delete it. The basic rule is 3-2-1: three copies, two media types, one copy offsite. It is extended to 3-2-1-1-0: additionally one immutable or offline copy and zero unresolved verification errors.

With Veeam, the immutable copy is typically implemented via a hardened repository with a defined retention lock or via object storage with Object Lock. During the lock period, backups can be neither modified nor deleted (hardened repository).

With PBS, protection comes from the architecture:

• A second PBS at another location pulls the data via pull sync. The source PBS holds no credentials for the target. The approach is described in the guide to the PBS offsite pull architecture.
• Proxmox hosts only get permission to write backups, not to delete them.
• Individual snapshots can be marked as protected and are then safe from prune jobs and manual deletion (PBS docs).
• LTO tape or removable media are suitable for the offline copy. S3 Object Lock must not be enforced on an active PBS datastore, because prune and garbage collection need to delete objects.
• Client-side encryption with AES-256-GCM ensures that an offsite provider cannot read the data, for example with encrypted backups on a Hetzner Storage Box.

Regardless of the product: a backup is only proven once the restore has been tested and its duration documented.

Combine or switch

Combine. Many environments do well with a split: PBS backs up all VMs and containers quickly and deduplicated, while Veeam or a Veeam-managed agent handles the few systems with Exchange, SQL Server or Active Directory that require item-level recovery. What matters is clear responsibility per system and coordinated backup windows so snapshots do not overlap.

From VMware with Veeam to Proxmox. Veeam can restore backups of VMware VMs directly to Proxmox VE. That is a workable migration path for individual systems, alongside Proxmox's own import wizard (see Migrate from VMware to Proxmox). After the migration, it is worth checking whether Veeam is still needed for the new environment.

From Veeam to PBS. Existing Veeam backups cannot be imported into PBS. The usual approach is parallel operation: PBS takes over from a cut-off date, and the Veeam backups remain readable until their retention period ends.

Decision guide

PBS fits when the environment is predominantly Proxmox VE, LXC containers are in use, license costs should not grow with the number of VMs and file-system-consistent backups are sufficient for the applications.

Veeam fits when VMware, Hyper-V or physical servers will keep running in parallel, Exchange, SQL Server or Active Directory must be recoverable at item level, a Veeam tape infrastructure exists or central reporting across all platforms is required.

Both fit when most systems are simple, but a few need application-level recovery.

If you are looking for file-level backup tools for servers outside Proxmox, see the comparison restic, Borg or Kopia.

Our approach at WZ-IT

We run Proxmox environments with Proxmox Backup Server as the standard. We do not operate Veeam; we assess existing Veeam installations neutrally and define responsibilities clearly:

1. Assessment: Which systems need application-level recovery, which RTO and RPO targets apply, which retention is mandatory?
2. Target design: PBS alone or a clear split in which Veeam continues to be run by your team or your Veeam partner, including an offsite copy and an immutable or offline copy.
3. Build and operation: Setup of local and external Proxmox Backup Server, monitoring of backup, sync and verify jobs as part of Managed Proxmox.
4. Proof: Documented recovery through the restore test and, for the whole cluster, a disaster recovery concept with tested procedures.

Further reading

• What is Proxmox Backup Server? - features, license and tiers in detail
• PBS offsite backup with pull architecture - sync direction, retention and 3-2-1-1-0
• Encrypted backups on Hetzner - offsite copy on the Storage Box
• PBS 4.2: S3 storage stable - object storage as a datastore
• How much does Proxmox cost? - subscription and total cost
• Proxmox vs. VMware - the platform comparison
• restic, Borg or Kopia - file-level backup tools

Need a backup concept for Proxmox? We review your requirements, assess PBS and Veeam for your environment and, if you wish, take over building and operating the backups with Proxmox Backup Server.

Book an initial consultation · Proxmox Backup Server as a managed service · Proxmox disaster recovery