recommended Config
- Thread starter pille99
- Start date
It does not need to be a separate server. But it is recommended. I want my PBS to be available/usable when my PVE dies completely.
You know the 3-2-1 rule? Three backups on two different media, one off-site.
When you build one PBS there is no redundancy per se. There are at least two levels: I want my hardware storage devices to be redundant. To achieve this I utilize ZFS. Usually I take some legacy hardware (spinning disk) and add a fast special device to get acceptable performance.
To get redundancy on the higher level I just build a second PBS and pull-sync backups from the first one. This adds some more advantages, @Johannes S described malware protection aspects somewhere...
I run a PBS in a container (using local storage) on each PVE node (I don't use a cluster) for fast local backups. And let various PBS sync between themselves, as they are on different systems and in different locations. This fulfills the 3-2-1 principle and gives a a distributed backup, much like Git for example where every system has a full local copy.
Indeed, e.g. here: Post in thread 'How can I prevent root user in PVE to delete backups created via PBS?' https://forum.proxmox.com/threads/h...te-backups-created-via-pbs.179330/post-832059
But to give Credit where it's due: My setup is based on the ones @Falk R. described in the German forum as his to-go-setup for the businesses he supports im his consulting Gigs.
The manual is also worth a read in that regard:
https://pbs.proxmox.com/docs/user-management.html
https://pbs.proxmox.com/docs/storage.html#ransomware-protection-recovery