Proxmox ZFS Snapshot Replication for Automated VM Backup
Automate Proxmox VM backups using ZFS snapshot replication. Deploy sanoid for snapshot management, syncoid for push replication, and automate the entire workflow with systemd timers.
Automate Proxmox VM backups using ZFS snapshot replication. Deploy sanoid for snapshot management, syncoid for push replication, and automate the entire workflow with systemd timers.
A practical guide to ZFS pool design and performance tuning for Proxmox homelabs — topology selection, ashift, recordsize, compression, ARC sizing, and real-world monitoring with arcstat and zpool iostat.
Deploy Proxmox Backup Server in your homelab — bare-metal, LXC, or Docker-based setup with ZFS datastores, client config, verification schedules, and offsite sync for a complete 3-2-1 backup strategy.
Set deterministic ZFS ARC limits, add L2ARC without wasting RAM on metadata, and tune recordsize and compression for your Proxmox homelab VMs.
ZFS is the default filesystem on Proxmox VE for good reason — checksumming, snapshots, compression, and built-in replication. But “default” doesn’t mean one-size-fits-all. Pool layout, recordsize, snapshot cadence, and backup strategy all depend on your workload. This post covers the ZFS setup on my Proxmox host (SRV1), the snapshot pipeline, and how ZFS send/receive + sanoid handle retention and offsite recovery. Pool Layout System: HP ProDesk 600 G4 DM (i5-8500T, 32 GB RAM) Disks: 1× NVMe (OS + VMs), 1× SATA SSD (bulk storage) Boot/OS Pool — rpool Standard Proxmox installation creates rpool on the boot disk. No RAID, no redundancy — just a single NVMe: ...