Proxmox Backup Server Setup Guide for Small Businesses

Proxmox Backup Server (PBS) is the backup companion to Proxmox VE, and setting it up properly comes down to five things: dedicated hardware or a separate VM host, a well-planned datastore, sensible retention (prune) rules, regular verification, and a second copy offsite. PBS gives you incremental, deduplicated backups of VMs and containers, with optional client-side encryption, at no license cost. This guide walks through a practical setup for a small business.

What Proxmox Backup Server does

PBS stores backups as deduplicated chunks. After the first full backup, each new backup only sends changed data, which keeps nightly jobs short and storage growth modest. Key features include:

• Incremental, deduplicated backups for KVM virtual machines and LXC containers.
• Client-side encryption, so data is encrypted before it leaves the Proxmox VE host.
• Verification jobs that re-read chunks to detect corruption.
• Sync jobs to replicate a datastore to a second PBS, for example offsite or in the cloud.
• Granular restores, including individual files from inside a VM backup.
• Tape support (LTO) for organizations that need offline media.

Step 1: Plan the hardware

The most important rule: do not store your only backups on the same server you are backing up. If that host fails, is stolen or is hit by ransomware, you lose both.

Practical options for a small business:

• A small dedicated server or workstation-class machine with ECC memory.
• Enterprise SSDs, or HDDs with an SSD special device if you use ZFS, since PBS performs many small random reads during verification and restores.
• A ZFS mirror or RAIDZ pool for the datastore.
• A network connection that can move your nightly change volume comfortably.

Step 2: Install PBS

Download the PBS ISO from the Proxmox website and install it like Proxmox VE, or add the PBS packages to an existing Debian system. After installation, the web interface is available on port 8007:

https://<pbs-ip-address>:8007

Apply updates first. If you have a subscription, enable the enterprise repository; otherwise configure the no-subscription repository.

Step 3: Create a datastore

A datastore is the directory where PBS keeps backup chunks. You can create it in the web UI under Administration > Storage / Disks, which also builds a ZFS pool for you, or from the shell:

# Create a datastore on an already-mounted ZFS dataset
proxmox-backup-manager datastore create store1 /mnt/datastore/store1

Next, create a dedicated user, for example backup@pbs, and grant it the DatastoreBackup role on that datastore. Avoid using root for daily backup traffic.

Step 4: Connect Proxmox VE to PBS

In Proxmox VE, go to Datacenter > Storage > Add > Proxmox Backup Server and enter the server address, datastore, user and the fingerprint shown on the PBS dashboard. The equivalent command is:

pvesm add pbs pbs-office --server 192.168.10.50 --datastore store1 \
  --username backup@pbs --password 'use-a-strong-password' \
  --fingerprint <sha256-fingerprint-from-pbs>

In the same dialog you can generate an encryption key. If you enable it, store a copy of the key somewhere safe outside the cluster, such as a password manager and a printed paper copy. Without the key, encrypted backups cannot be restored.

Step 5: Schedule jobs and set retention

Create a backup job under Datacenter > Backup, select the VMs, the PBS storage and a schedule outside business hours. Then define pruning on the datastore. A common starting point:

Retention option	Example value	What it keeps
keep-last	3	The three most recent backups
keep-daily	7	One backup per day for a week
keep-weekly	4	One per week for a month
keep-monthly	6	One per month for six months

Adjust these to your compliance and business needs. Pruning removes index references; a scheduled garbage collection job then frees the unused chunks.

Step 6: Verify and test restores

Schedule a verify job so PBS regularly re-reads backup data and flags problems. Verification is not the same as a restore test, though. At least quarterly, restore a real VM to an isolated network and confirm the application starts and the data is current. Document how long it took, because that is your realistic recovery time.

Step 7: Keep a copy offsite

Follow the 3-2-1 approach: three copies of your data, on two types of media, with one offsite. With PBS, the simplest method is a sync job that pulls the datastore to a second PBS in another location or a cloud server. For extra ransomware resilience, restrict the remote side so the primary site cannot delete its backups.

Our Proxmox virtualization service includes designing and monitoring PBS deployments, and our cloud and dedicated servers team can host an offsite PBS target.

FAQ

Can I run Proxmox Backup Server as a VM on my Proxmox cluster?

You can, and it is useful for testing, but for production it should not live only on the cluster it protects. If you virtualize it, place it on a separate host or pair it with an offsite sync target.

Does PBS back up physical servers or only VMs?

PBS is designed around Proxmox VE VMs and containers, but the proxmox-backup-client tool can also back up files and directories from Linux machines. Windows physical servers usually need a different approach.

How much storage does PBS need?

It depends on your data size, daily change rate and retention. Deduplication helps a lot with similar VMs, but measure your real usage after the first few weeks and plan growth from there.

Get a second opinion on your backups

Backups only matter when a restore works. If you are not sure yours would, request a free IT assessment and we will review your backup design, retention and recovery process with you.