Proxmox Backup Server: Complete Configuration Guide

Posted: March 5, 2026 to Technology.

Proxmox Backup Server: Complete Configuration Guide

Proxmox Backup Server (PBS) is the enterprise-grade, open-source backup solution designed specifically for Proxmox VE environments. It provides incremental backups with client-side deduplication, AES-256-GCM encryption, integrity verification, and a web-based management interface. Unlike VMware environments that require expensive third-party backup tools like Veeam, PBS is free, fully integrated with Proxmox VE, and capable of protecting both virtual machines and LXC containers. This guide covers complete PBS deployment and configuration for production use.

Why Proxmox Backup Server

Traditional backup solutions designed for VMware (Veeam, Commvault, Veritas) carry significant licensing costs, often $3,000 to $20,000 or more per year depending on the number of protected workloads. PBS eliminates this cost entirely while providing capabilities that match or exceed commercial solutions for Proxmox environments.

Key capabilities include image-level VM and container backups with change-block tracking, client-side deduplication that dramatically reduces backup storage requirements and network bandwidth, AES-256-GCM encryption for data at rest and in transit, fast single-file restore without full VM recovery, backup verification that boots and validates VMs from backup without affecting production, tape drive support for long-term archival, and a REST API for automation and integration.

Deployment Architecture

Dedicated Server vs VM

For production environments, deploy PBS on a dedicated physical server or a dedicated VM on a separate host from your Proxmox VE cluster. This ensures that a cluster node failure does not also take down your backup infrastructure. The PBS server needs CPU capacity for deduplication and encryption processing, sufficient RAM for deduplication index caching (4 GB minimum, 16 GB or more for large environments), and high-capacity storage for backup data.

Storage Sizing

PBS's deduplication significantly reduces storage requirements compared to traditional full-plus-incremental backup schemes. As a starting guideline, plan for 1.5 to 3 times the total size of your production data. The actual ratio depends on your retention policy, the rate of data change in your VMs, and how much duplicate data exists across VMs. For example, ten VMs with 100 GB each (1 TB total) typically require 1.5 to 3 TB of PBS storage with 30-day retention.

Use ZFS for the PBS datastore to gain data integrity verification, compression, and snapshot capabilities. A mirrored ZFS pool provides both performance and redundancy.

Installation

Download the Proxmox Backup Server ISO from the official Proxmox website. Install it on your dedicated backup server using the guided installer. PBS installs on Debian Linux, similar to Proxmox VE. After installation, access the web interface at https://backup-server-ip:8007.

Initial Configuration

Create a Datastore

A datastore is the storage location for backup data. In the PBS web interface, navigate to Administration, Storage/Disks to configure your storage. If using ZFS, create a ZFS pool from the available disks. Then navigate to Datastore, Add Datastore to create a named datastore on your ZFS pool.

Configure User Authentication

Create a dedicated backup user account for the Proxmox VE cluster to authenticate when sending backups. Navigate to Configuration, Access Control, User Management to create the user. Assign the DatastoreBackup role on your datastore to this user.

Set Up Encryption

PBS supports client-side encryption where the Proxmox VE node encrypts backup data before transmitting it to the PBS server. This means the PBS server never sees unencrypted data, providing protection even if the backup server is compromised. Generate an encryption key on your Proxmox VE node and store it securely. The key is required for both backup and restore operations, so losing it means losing access to your encrypted backups. Store copies of the key in a secure location separate from both your production and backup infrastructure.

Configure Retention Policies

PBS supports flexible retention policies based on keep-last (number of recent backups), keep-hourly, keep-daily, keep-weekly, keep-monthly, and keep-yearly parameters. A common production retention policy keeps the last 3 backups, 7 daily backups, 4 weekly backups, 6 monthly backups, and 1 yearly backup. This provides granular recovery options for recent data while maintaining long-term recovery capability.

Connecting Proxmox VE to PBS

On your Proxmox VE cluster, add the PBS server as a storage backend. Navigate to Datacenter, Storage, Add, Proxmox Backup Server. Configure the PBS server address, port, backup user credentials, datastore name, and encryption key fingerprint. Once configured, the PBS storage appears in the Proxmox VE interface alongside your other storage backends.

Configuring Backup Jobs

Create backup jobs in Proxmox VE by navigating to Datacenter, Backup, Add. Configure which VMs and containers to include, the schedule (daily, weekly, or custom cron expression), the backup mode (snapshot for running VMs, suspend, or stop), compression settings, and notification settings for job success or failure.

For production environments, schedule backups during off-peak hours and stagger jobs across nodes to distribute the load. Use snapshot mode for VMs that cannot tolerate any downtime during backup.

Backup Verification

PBS includes a verification feature that checks backup integrity by reading and validating every chunk in a backup. Schedule regular verification jobs to detect any storage-level data corruption before you need to restore. PBS can also perform automated restore testing by booting a VM from backup in an isolated environment and checking that it starts successfully.

Restore Procedures

Full VM Restore

To restore a complete VM, navigate to the VM's backup history in the Proxmox VE interface, select the desired backup snapshot, and click Restore. You can restore to the original VM (overwriting current data) or create a new VM from the backup. The restore process is fast because PBS only transfers the blocks needed for the selected snapshot.

Single File Restore

PBS supports file-level restore without recovering the entire VM. In the PBS web interface, navigate to the backup snapshot, browse the filesystem, and download individual files or directories. This is invaluable when a user needs a single deleted file recovered without the overhead of a full VM restore.

Advanced Configuration

Remote Sync and Offsite Backup

PBS supports sync jobs that replicate backup data to a second PBS server at a remote location. This provides offsite backup protection following the 3-2-1 backup rule (3 copies, 2 different media types, 1 offsite). Configure a sync job by adding the remote PBS server as a remote in your local PBS configuration, then creating a sync job that specifies the source and target datastores.

Tape Backup

For organizations requiring tape-based long-term archival, PBS supports LTO tape drives. Configure tape drives and media pools through the PBS interface, then create tape backup jobs that write datastore content to tape for offsite storage.

Notifications

Configure email notifications for backup job completion, failure, and verification results. PBS supports SMTP notification delivery and can integrate with external monitoring systems through its API.

Performance Optimization

To maximize PBS performance, use fast SSD or NVMe storage for the PBS datastore, especially for the deduplication index. Ensure adequate network bandwidth between Proxmox VE nodes and the PBS server (10GbE recommended for large environments). Allocate sufficient RAM for deduplication index caching. Use ZFS with appropriate recordsize settings for backup workloads. Schedule backup jobs to distribute load across time windows rather than running all jobs simultaneously.

Security Considerations

Protect your PBS infrastructure with network isolation (place PBS on a dedicated backup network), strong authentication and access control, client-side encryption for all backup data, regular verification to detect tampering or corruption, secure offsite replication for disaster recovery, and backup of the encryption keys in a secure location (a hardware security module or encrypted vault).

PBS in Compliance Environments

For organizations subject to CMMC, HIPAA, or SOC 2, PBS provides the backup and recovery capabilities required by these frameworks. Encrypted backups at rest and in transit address data protection requirements. Retention policies support regulatory data retention mandates. Verification jobs provide evidence of backup integrity. Offsite sync addresses geographic disaster recovery requirements. Audit logging tracks backup and restore operations.

Professional Support

At Petronella Technology Group, we deploy and manage Proxmox Backup Server alongside Proxmox VE clusters for organizations across the Raleigh-Durham area and beyond. Our backup architecture designs incorporate encryption, offsite replication, compliance requirements, and tested restore procedures. Contact us for a backup assessment and PBS deployment plan.