Proxmox Backup to TrueNAS: Easing Storage Pressure

Moving a Proxmox Backup Server (PBS) datastore to a TrueNAS system directly relieves storage pressure by offloading deduplicated backup chunks and their metadata to a separate, expandable pool, freeing the Proxmox host’s local disks for VMs and CTs. You keep the fast, incremental backup workflow PBS provides while gaining TrueNAS’s mature ZFS storage management, snapshots, and easy disk replacement. This article explains why that move helps, how to do it safely, and what to watch out for.

Why Proxmox Backup Server Creates Storage Pressure

Proxmox Backup Server (PBS) is a Debian-based backup solution designed for Proxmox VE. It stores VM and container backups as chunks in a datastore, using client-side deduplication and compression. Every backup run only transfers and stores the changed data blocks, so daily backups are small. However, the deduplication index and the accumulated chunks grow without bound as you keep more restore points. A single VM with a 100 GB disk, backed up daily for a month, can consume several hundred GB of datastore space, even with deduplication, because each day’s changes add new chunks. When the datastore lives on the same physical disks as the hypervisor’s VMs, the backup workload competes for the same IOPS and capacity, eventually filling the disk and stalling both backups and production workloads.

What TrueNAS Adds to the Backup Equation

TrueNAS is a free and open-source network-attached storage operating system built on ZFS. Its core strengths are data integrity (checksums on every block), snapshots, replication, and flexible pool management. ZFS pools can be expanded by adding vdevs or replacing disks with larger ones, and they can be configured with RAID-Z1, RAID-Z2, or mirrors to tolerate disk failures. TrueNAS also supports SMB, NFS, and iSCSI, so it can serve as a central backup target for multiple Proxmox hosts. By moving the PBS datastore to a TrueNAS system, you separate backup storage from compute storage, which is a standard best practice in virtualization environments.

How the Move Works: NFS, SMB, or iSCSI

PBS does not have a native TrueNAS plugin, but it can use any POSIX-compliant filesystem mounted over the network. The most common approach is to create a dataset on TrueNAS, share it via NFS, and mount it on the PBS host at a path like /mnt/truenas-pbs. Then you create a new datastore pointing to that mount point. Alternatively, you can use SMB (CIFS) with the cifs mount options, but NFS is generally preferred for Linux-to-Linux performance and permission handling. iSCSI is also possible, but it adds a filesystem layer (like ext4 or XFS) on top of the block device, which loses ZFS’s native compression and checksums unless you use ZFS on the client, which is not typical.

Here is a typical migration sequence:

• On TrueNAS, create a dataset (e.g., pool/backup/pbs) with compression enabled (ZFS LZ4 or ZSTD) and set the share to NFS.
• On the PBS host, install the NFS client if not present, then mount the share with the appropriate options (e.g., mount -t nfs truenas-ip:/mnt/pool/backup/pbs /mnt/truenas-pbs).
• Add a new datastore in the PBS web UI pointing to that mount point.
• Copy existing backups from the old datastore to the new one using proxmox-backup-client or a simple rsync of the .chunks and .index.json files. Be aware that a plain file copy is not atomic, so it is safer to use the built-in proxmox-backup-manager to verify the datastore after copying.
• Once verified, remove the old datastore or keep it as a local cache.

Choosing the Right TrueNAS Setup for PBS

The performance of PBS on TrueNAS depends heavily on the network and the ZFS pool layout. For a small home lab, a single Gigabit Ethernet link is acceptable, but 10 GbE is recommended if you have many VMs or large disks. For the pool, mirrors give better random write performance, which matters for backup ingestion, while RAID-Z gives more usable space per disk. ZFS recordsize is critical: PBS writes chunks of variable size (typically 4 MB to 64 MB), so a recordsize of 1 MB or 4 MB on the dataset is a good starting point. The default 128 KB may cause excessive fragmentation and overhead. You can set recordsize=1M on the TrueNAS dataset before copying data. Also enable atime=off to reduce write amplification.

Common Problems and How to Avoid Them

One frequent issue is permission errors: PBS runs as the backup user, so the NFS share must allow that user to write. On TrueNAS, you can set the dataset’s ACL to grant write access to the PBS host’s UID (usually 34). Another problem is that NFS over a slow network can cause backup timeouts. Increase the PBS client timeout settings if you see connection timeout errors. Also, if you use SMB, ensure the share is mounted with the vers=3.0 option and proper credentials; otherwise, you may hit file locking issues. Finally, do not forget to monitor the TrueNAS pool’s health—ZFS will not repair silent corruption unless you have redundancy, so use mirrors or RAID-Z and run regular scrub jobs.

Costs and Capacity Planning

Moving to TrueNAS does not eliminate the need for storage; it just moves it. You still need enough raw capacity to hold all backup chunks plus overhead. A good rule of thumb is to allocate at least 1.5 times the total size of all VM disks you plan to back up, assuming daily incremental backups with weekly fulls. Deduplication on PBS is global per datastore, so the more VMs you back up, the better the ratio, but it is not a guarantee. ZFS compression can further reduce the footprint, especially for text-heavy or sparse data. Remember that TrueNAS itself uses some RAM (1 GB per TB of storage is a common guideline) and that ZFS writes are copy-on-write, so you need free space for snapshots and pending writes. Plan for at least 20% free space on the pool.

Safety and Backup of the Backup

Putting all your backups on a single TrueNAS box is a single point of failure. If the TrueNAS system dies, you lose your backups. Therefore, you should replicate the PBS datastore to another location, either using TrueNAS’s built-in replication to a second TrueNAS, or by using PBS’s remote sync feature to another PBS instance. Also, enable ZFS snapshots on the TrueNAS dataset to protect against accidental deletion or ransomware. Test restores regularly—a backup that cannot be restored is worthless. The PBS web UI has a Verify feature that checks chunk integrity; run it weekly.

Frequently Asked Questions

Can I run PBS directly on TrueNAS as a plugin?

No official plugin exists, but you can run PBS in a VM on TrueNAS (if the hardware supports virtualization) or in a jail/container using TrueNAS SCALE’s Docker support. However, the simplest and most reliable method is to run PBS on a separate small machine or VM and use TrueNAS as the storage backend via NFS.

Will I lose deduplication if I move the datastore to TrueNAS?

No. PBS deduplication happens at the client level (on the Proxmox host) before data is written to the datastore. The chunks are stored as files, and TrueNAS does not need to deduplicate them. However, TrueNAS’s ZFS compression can still save space on top of PBS’s own compression, though it may be redundant.

What is the best network filesystem for PBS: NFS or SMB?

NFS is generally better for Linux-to-Linux workloads because it handles POSIX permissions and locking more cleanly. SMB works but requires careful mount options and can be slower. iSCSI is not recommended unless you have a specific reason, as it adds complexity without benefit.

How do I migrate my existing PBS backups to TrueNAS without re-backing up everything?

You can copy the entire datastore directory (including .chunks and .index.json) to the new mount using rsync or cp -a. After copying, run proxmox-backup-manager datastore verify to check integrity. This avoids re-reading all VM data.

Does TrueNAS need a lot of RAM for PBS storage?

ZFS uses RAM for caching, so more is better. For a small setup, 8 GB is workable, but 16 GB or more is recommended if you have many TB of storage. The rule of thumb is 1 GB of RAM per TB of raw storage, but this is not a hard limit.

Can I use TrueNAS as the only backup location for multiple Proxmox hosts?

Yes, you can create multiple datasets or a single large dataset and point multiple PBS instances to it, as long as each PBS has its own subdirectory. However, ensure the network bandwidth and TrueNAS CPU can handle concurrent backup streams.

Related

• Best Industrial IoT Sensors for Boilers and Paper Mills
• Alternative Proteins: Are Plant-Based and Cultured Foods Safe?
• Quota Circuit Breaker: What to Rerun After 15 Jobs