惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
Tenable Blog
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
V
Vulnerabilities – Threatpost
G
GRAHAM CLULEY
Simon Willison's Weblog
Simon Willison's Weblog
C
CXSECURITY Database RSS Feed - CXSecurity.com
P
Privacy International News Feed
H
Heimdal Security Blog
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
S
Secure Thoughts
MyScale Blog
MyScale Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
V
Visual Studio Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
L
LINUX DO - 最新话题
D
Darknet – Hacking Tools, Hacker News & Cyber Security
The Cloudflare Blog
美团技术团队
Recorded Future
Recorded Future
T
Tailwind CSS Blog
Latest news
Latest news
Security Archives - TechRepublic
Security Archives - TechRepublic
Security Latest
Security Latest
Know Your Adversary
Know Your Adversary
Cloudbric
Cloudbric
Schneier on Security
Schneier on Security
I
Intezer
L
LINUX DO - 热门话题
P
Palo Alto Networks Blog
云风的 BLOG
云风的 BLOG
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Vercel News
Vercel News
Attack and Defense Labs
Attack and Defense Labs
人人都是产品经理
人人都是产品经理
L
LangChain Blog
爱范儿
爱范儿
博客园 - 三生石上(FineUI控件)
博客园 - 叶小钗
L
Lohrmann on Cybersecurity
S
SegmentFault 最新的问题
W
WeLiveSecurity
C
Cybersecurity and Infrastructure Security Agency CISA
S
Securelist
SecWiki News
SecWiki News
V2EX - 技术
V2EX - 技术
IT之家
IT之家
Cyberwarzone
Cyberwarzone
F
Full Disclosure
Spread Privacy
Spread Privacy
阮一峰的网络日志
阮一峰的网络日志

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice ceph-osd crashes with kernel 6.17.2-1-pve on Dell system [META] Links on Proxmox Forum Website Hardwarer oder Software RAID Joining a cluster with already created guests VM PDM missing backup jobs from PVE / Log retention Remove VM.Monitor from all users/roles, PVE 9.2 Proxmox Freezing (new instalation) 9.2.2 - Intel 12700T No Web gui and random connection reset by peer [SOLVED] - i40e module for X710 Intel NIC Dutch Proxmox Day 2026 How pools use the space Corosync initiiert Reboot trotz Verfügbarkeit der Systeme Opt-in Linux 7.0 Kernel for Proxmox VE 9 available After PVE 8to9 upgrade, unable to check guest fs freeze status Problem with MegaRAID SAS3508 controller proxmox-kernel-7.0.2-6-pve failing network service Auto sync guest time after rollback of VM snapshot with RAM/state Broadcom BCM57504 (100G) bnxt_en TX timeout and NIC reset on Proxmox 8.1.5 — while BCM57414 (25G) works fine on same host QEMU 11.0 available on pve-test and pve-no-subscription as of now 350 MPM Solventless Lamination Machine for High-Speed Flexible Packaging Making sense of NVMe zfs and SMART errors [SOLVED] - PVE loses network connection after kernel upgrade to proxmox-kernel-7.0.0-3-pve [SOLVED] - Remove or reset cluster configuration. Proxmox 8.4.1 Fresh Install BCM57416 10G Ethernet Adapter Not Recognized PDM 1.1.1 unable to add AD realm with anonymous search [TUTORIAL] - Developer Workstation (Proxmox-VE 9) with cinnamon (LMDE7) SDN zone shows "pending" on peer nodes after node reboot (9.2.x) Cluster not quorate - extending auth key lifetime! Proxmox not rebooting properly (SOLVED) Proxmox 9 Stuck on loading initial ramdisk With new HA-Disarm Feature is there a Documentation for NUT Setup on Clusters? Proxmox 8.3 Installation Issue on ProLiant DL380 Gen9 Cluster networking setup LXC System images unavailable [SOLVED] - Fix: NVIDIA Drivers Failing after upgrade to Proxmox 9.2.2 (Kernel 7.0.2-6-pve) / NovaCore Conflict Install NUT directly on Proxmox VE and control guests from here driver usb for windows 7 System startup error and no network: Failed to start ifupdown2-pre.service - Helper to synchronize boot up for ifupdown. PBS backup space grow up constantly Proxmox Datacenter Manager 1.1 released! IPv4 not available in newly created VM Recommended Setup for Offsite Proxmox Backups? Hetzner Storage Box & Remote PBS Challenges duplicate, please delete this passthrought an USB device "by ID" to CT PDM Installer Freezes at 66% Tried PDM for the first time (version 1.1) - had issues PDM 1.1 automated install Suche Server-Provider für Proxmox connecting sdn to edge firewall SDN, IPAM & DHCP Migrating from read-only file system Ubuntu 26.04 installation fails for unknown reason Status Unbekannt nach Cluster Join Installing Proxmox Backup Server on Mac Mini (Late 2012) kernel 7.0 performance issue with zfs pools PVE becomes unreachable via ethernet but OS is running [SOLVED] - New 9.2 install - can't find 7.0.2-6-pve , not all the time [SOLVED] - Backup and dedupe a VM with LUKS Gibt es mit PVE 2.x ggf. Änderungen bei der RAM-Nutzung, bzw. deren Anzeige bei VMs? Way more NAGware, very little functionality, bugs galore Root squashing virtiofsd with --uid-map Intel ixgbe Driver Update Fail Help to fix Proxmox access issues after power cut Passkey Login (not 2FA) Roblox VM detection - can be overcome? [TUTORIAL] - ZFS-Autosnaptshot inkl. Rollback und Daten direkt recovern (Windows/Linux) How to stop PVE Kernel upgrade [SOLVED] - very long waiting to log in to lxc debian 11 ssh [TUTORIAL] - Configuring Fusion-Io (SanDisk) ioDrive, ioDrive2, ioScale and ioScale2 cards with Proxmox Increase maximum USB devices in vm.conf
I need help for setting up backup solution
invalid@exam · 2026-05-22 · via Proxmox Support Forum

I built my Proxmox homelab on Z890 chipset with Intel Core Ultra 5 235 and 64GB of RAM a year ago.
OS and VMs are on enterprise SSD with single disk ZFS configured (RAID1 would be great, but I don't have it), and cheap storage consists of five WD Red Plus 8TB disks with ZFS raid-z2 configured. I use cheap storage for all my media files and as destination for VM backups.

I finally decided to backup those VMs and media files properly, and in order to do that I acquired ASUS Prime N100I-D D4-CSM with 32GB of RAM, NVMe for OS and three SATA disks for backup storage (two WD Red Plus 8TB and one WD Red Plus 4TB disk). Motherboard has only one PCIe 3.0 x1 slot which I slotted with ASM1064 on which I connected those three hard drives.
I'm not interested in parity since this should be for backup and I want to maximize usable space. And now I don't know what to do next...
First on my mind was choosing PBS, but what file system should I choose for those three WD Red drives and how should I configure backup from Proxmox's ZFS media storage? I would avoid spending more money if that is possible.

I assume you have your main unit on 24/7 and turn on the backup unit manually from time to time to do backups of the main unit?

PBS has a lot of benefits for backing up and restoring VMs/LXCs over your current local backups. This is even already the case without the backup unit in place and you could consider this a seperate step to transition from local backups to a local PBS server on the main unit.
If you go that way, from my experience you really want the PBS datastore on SSD. Assuming your enterprise SSD is large enough to hold a PBS datastore for your deduplicated VM/LXC backups with some retention, you can install PBS in an LXC on your main unit for regular backups of all VMs/LXCs except PBS itself. Create a separate backup scheme for only the PBS LXC on the local storage, outside of PBS as you do now.
You probably already make regular zfs snapshots of the datasets on your 'cheap storage' zpool. If not, consider the excellent sanoid tool by Jim Salter. It's in the default Debian repo's.

Next up is your backup unit. Install PBS on the NVME and you ideally also want the datastore on the NVME again. Create a pull sync job that drags in the PBS backups from the main unit. Additionally, setup a zpool for your other data. Ideally you want a 3x8TB zpool alongside the nvme where you can sync the data from the 'cheap storage'. So sell the 4TB and get an extra 8TB disk. ;-) Or use the 4TB as a 3rd off-site external drive backup of your most important files in case your house burns down.

Create a script that runs the PBS sync pull job from the main PBS unit, a sync of the 'cheap storage' pool and you can also sync important folders of the proxmox host to the backup unit, including the aforementioned backups of the PBS LXC. Syncoid again is great for incrementally syncing zfs datasets to another zpool but you can also use rsync and create zfs snapshots manually after each sync as you prefer. You can either run the script manually or automated on boot of the backup unit.

You can obviously also go without PBS and just sync your current VM/LXC backups to the backup unit but PBS definitely has its advantages.

Last edited:

I assume you have your main unit on 24/7 and turn on the backup unit manually from time to time to do backups of the main unit?

PBS has a lot of benefits for backing up and restoring VMs/LXCs over your current local backups. This is even already the case without the backup unit in place and you could consider this a separate step to transition from local backups to a local PBS server on the main unit.
If you go that way, from my experience you really want the PBS datastore on SSD. Assuming your enterprise SSD is large enough to hold a PBS datastore for your deduplicated VM/LXC backups with some retention, you can install PBS in an LXC on your main unit for regular backups of all VMs/LXCs except PBS itself. Create a separate backup scheme for only the PBS LXC on the local storage, outside of PBS as you do now.
You probably already make regular zfs snapshots of the datasets on your 'cheap storage' zpool. If not, consider the excellent sanoid tool by Jim Salter. It's in the default Debian repo's.

Next up is your backup unit. Install PBS on the NVME and you ideally also want the datastore on the NVME again. Create a pull sync job that drags in the PBS backups from the main unit. Additionally, setup a zpool for your other data. Ideally you want a 3x8TB zpool alongside the nvme where you can sync the data from the 'cheap storage'. So sell the 4TB and get an extra 8TB disk. ;-) Or use the 4TB as a 3rd off-site external drive backup of your most important files in case your house burns down.

Create a script that runs the PBS sync pull job from the main PBS unit, a sync of the 'cheap storage' pool and you can also sync important folders of the proxmox host to the backup unit, including the aforementioned backups of the PBS LXC. Syncoid again is great for incrementally syncing zfs datasets to another zpool but you can also use rsync and create zfs snapshots manually after each sync as you prefer. You can either run the script manually or automated on boot of the backup unit.

You can obviously also go without PBS and just sync your current VM/LXC backups to the backup unit but PBS definitely has its advantages.

My main unit is up 24/7 and I currently I do manual backups from time to time to my ZFS raid-z2 pool with cheap disks (which are also on my main machine). I never thought of setting up PBS as LXC on my Proxmox, but it sounds like an interesting idea, but SSDs are too damn expensive to put backups on them.
I'll set up PBS on machine I acquired for backup, set stripe zpool with existing disks (if it dies, it dies, it's backup anyway) and try Syncoid as soon as possible.

UdoB

Distinguished Member

There are many, many posts written about a good setup. My personal key-points (in a very small nutshell) are these:

  • PBS must be self-contained, on separate hardware; especially when you have only one PVE (no cluster) you want to have access to the backups as easy as possible = without installing a new (virtual or co-hosted) PBS first
  • PBS, the OS, should live on redundant media - it must be available when you are already in trouble - and Murphy's law exists
  • PBS datastore must be have some redundancy - it must be available when there is already a disaster happening - and Murphy...
  • if you absolutely need to use rotating rust (like I do), then you really, really want to add two (one mirror) small, but fast SSD/NVMe for a Special Device - 0.3% of the datastore capacity is large enough, e.g. 72 GB for 24 TB (...but opt for 240 or 500 GB if possible and add "Small Blocks".)

Just my two €c and your mileage may absolutely vary...

See also https://pbs.proxmox.com/docs/installation.html#recommended-server-system-requirements

----
Edit, adding one piece: while still best practice, there is no need to separate OS from the data - at least not in a Homelab. You can install on all spindles you have, with the required redundancy. All of these disks will be bootable. Then, after everything is up and running, add that the mirrored "Special Device". The result is a single, large rpool.

Last edited:

It is hard to disagree with any of those. But then there are the homelab/budget restrictions that OP clearly pointed out and are frankly quite common outside production/enterprise use.

Having 2 PBS copies is always better than one. Adding a local PBS to PVE enables 24/7 scheduled backups without additional cost or power consumption, while much more efficient compared to regular local backups. If the main unit dies you can still restore from the second, offline PBS.

OP: Fun to watch if you are new to PBS:
https://youtu.be/KxPl8SHREcE

Last edited:

So standard Proxmox backup doesn't do incremental backups and PBS does?
If that is the case PBS in LXC container makes sense for local backups to another zfs pool. But do I really need backups on the same machine where my Proxmox is when I have PBS on the separate machine? I don't really need 24/7 scheduled backups and if my Proxmox machine dies, backups would die with it anyway.

Also, I set up sanoid and syncoid for zfs pool (with cheap disks) that contains data and I want to thank daanw for recommending it to me, it is a great solution.

If that is the case PBS in LXC container makes sense for local backups to another zfs pool.

Exactly. Separate zpool in the same machine holding the PBS datastore and backups of the PBS LXC.

In case the Proxmox rpool dies:
- reinstall Proxmox,
- restore the last backup of the PBS LXC from the separate zpool in the same machine.
- restore all the other VMs and LXCs from PBS.

All should be back online in less than 30 min.

In case the second zpool dies, have a second PBS on another machine that does a regular sync of all VMs and LXCs from the first PBS and a copy of the PBS LXC backups.

Last edited:

So standard Proxmox backup doesn't do incremental backups and PBS does?

No backups in PVE are incremental, they are all full. However PBS stores only one copy of each chunk of duplicate data, across all VMs.

Exactly. Separate zpool in the same machine holding the PBS datastore and backups of the PBS LXC.

In case the Proxmox rpool dies:
- reinstall Proxmox,
- restore the last backup of the PBS LXC from the separate zpool in the same machine.
- restore all the other VMs and LXCs from PBS.

All should be back online in less than 30 min.

In case the second zpool dies, have a second PBS on another machine that does a regular sync of all VMs and LXCs from the first PBS and a copy of the PBS LXC backups.

So difference between restoring from local and remote PBS is just the restore speed?

Now that I have separate PBS machine working I see that it is consuming 16GB of ram (of max 32GB). How common is setting up second Proxmox with LXC PBS instead of standalone PBS?

Last edited:

So difference between restoring from local and remote PBS is just the restore speed?

No, it's about making efficient scheduled incremental backups without additional second machine powered on all the time.

Now that I have separate PBS machine working I see that it is consuming 16GB of ram (of max 32GB).

From my experience, a PBS LXC can run without any problems with 512MB of RAM assigned, not even fully using that.

The 16GB you see used on a bare metal install is probably ZFS claiming the default 50% of total RAM for ARC.

Last edited:

From my experience, a PBS LXC can run without any problems with 512MB of RAM assigned, not even fully using that.

The doc says that PBS should have at least 2-4 GB RAM plus 1GiB RAM per TB backup space: https://pbs.proxmox.com/docs/installation.html#system-requirements

Now this is for a bare metal install so I can easily imagine that for a LXC you might get away with less.

The 16GB you see used on a bare metal install is probably ZFS claiming the default 50% of total RAM for ARC.

Or the regular caches of the Linux kernel.

Last edited: