still no immutability option, without a solid immutability option you still need another backup solution.
Proxmox Backup Server 4.2 released!
- Thread starter t.lamprecht
- Start date
For regular datastores this is not easily implemented and requires the underlying storage to provide some mechanism to do so, see https://bugzilla.proxmox.com/show_bug.cgi?id=4293.
For datastores backed by S3, this might get implemented based on the discussion in https://bugzilla.proxmox.com/show_bug.cgi?id=6780 and the there linked forum thread, but I cannot give an ETA.
Edit: FYI, what you can already do is sync to offsite remotes or store to tape if the goal is ransomware protection https://pbs.proxmox.com/docs/storage.html#ransomware-protection-recovery
Last edited:
Adding to your link to the manual I want to point out, that for regular datastores it's not really needed since you can
- Use tapes or usb discs ("removable datastores") as air-gapped backup target
- Setup another PBS behind a firewall so neither the primary PBS nor the PVE nodes can access it. Then the remote PBS can do a pull-sync to the primary PBS.
I had some trouble installing 4.2 on old hardware - it seems the underlying Debian Trixie has dropped support for several components, I could not get the install to complete on a Dell R510 with H700 perc card. I fully understand this is way beyond ideal hardware but what I thought was a full HBA card in a failed newer system turned out to be one of those mini daughter cards (thanks Dell! ), so I have to make do with the H700 in an older chassis as a stop-gap solution. I'm using 2 x fast SSD in hardware raid1 for boot and then the remaining 6 bays each as a RAID0 volume of an enterprise quality SSD which is presented to PBS for ZFS (RAIDZ2) for the data pool. Like I say - not ideal. But I'm also putting in a NAS for 'colder' archive backups in a remote building.
I was getting squashfs errors and it looked like the boot media was faulty. I also suspected it was using EFI rather than Legacy on the older chassis but that wasn't the issue either. I tried a lot of different permutations but came to the conclusion it wasn't possible to install 4.2. What worked was install older PBS 3.2 and upgrade to 4.2 - that was very smooth and no problems. Resulting system seems to be working better than I expected of such old hardware. Smartctl can see the smart data using megaraid so it's reasonably robust.
Anyway, just thought I'd share that 3.2 and upgrading is very smooth if you are using older hardware in a home lab etc. Its my first time trying PBS and I have to say I'm already a huge fan.
I was getting squashfs errors and it looked like the boot media was faulty. I also suspected it was using EFI rather than Legacy on the older chassis but that wasn't the issue either. I tried a lot of different permutations but came to the conclusion it wasn't possible to install 4.2. What worked was install older PBS 3.2 and upgrade to 4.2 - that was very smooth and no problems. Resulting system seems to be working better than I expected of such old hardware. Smartctl can see the smart data using megaraid so it's reasonably robust.
Anyway, just thought I'd share that 3.2 and upgrading is very smooth if you are using older hardware in a home lab etc. Its my first time trying PBS and I have to say I'm already a huge fan.