my Proxmox Backup Server Guide - Full Walkthrough Series Pt.4

[@bopal93]

What a timing. Just about to setup pbs today and thought it would be nice to watch a guideline video

[@TheSporty3]

Timed very well, Been digging into your guides over the last few weeks of Christmas/near years break! Keep it up :) Thankyou

[@raddinox2707]

My OCD hurt me so much when you typed 4092 for 4 gigs of ram, should be 4096!

[@wizdude]

I came here to say exactly the same!

[@weholmes5315]

I recently set up PBS on a 2011 Mac Mini, got it working flawlessly, and just pulled the plug on my Proxmox cluster to explore new pastures (Unraid and ARC Loader). Byeee! 😅

[@hU5k1]

Thanks this was my next setup, perfect timing

[@YM-xz6xt]

I'd love to see a video regarding users and how to setup on proxmox and different, VM, LXC, shares and running applications.

[@YM-xz6xt]

If you want to use the "ocean" ZFS for other purpose as well, why not try to passthrough a subdataset to the VM, just like we can bind mount on LXC. It is pretty easy to do with 9pshare.

[@herdsire90210]

You can also backup to an LVM if you set it as a dump folder on the local host.

[@eaglw99]

Considering a single disk setup, which are the best practice to use it as a nas? Disk pass through, mount on host and pass mount point on lxc, samba from a lxc… I’m very lost right now!

[@romayojr]

why is your deduplication factor so low? have you configured prune & gc jobs yet?

[@csd4ni3l]

The main problem for me with the .raw files is not that they are files, its that when you back up containers or vms using .raw, they cant be snapshotted natively(in lvm or in zfs), meaning the host will use suspend or stop mode instead of snapshot mode. This will stop or suspend the container/vm, copy the whole disk to a temporary place, and then upload that to pbs, and then unsuspend or start the container or vm, instead of snapshotting while it is still running, which is much better in my opinion.

[@bopal93]

This!

[@AceBoy2099]

I'd love updates on pbs. I have it running on my proxmox and followed a video on setting it up to write to my truenas machine via network share, but when I went to try and use it I couldn't figure out how to access the backups from a new instance (I thought my proxmox was messed up, turned out the storage was full (lvm i think it was, cant recall; this stemmed from trying to "upgrade" the capacity of the originally installed ssd instead of building new and migrating backups over) and wouldn't let the vms start).

[@wizdude]

Question: you’ve setup the pbs backup volume as compressed ZFS inside ocean which is compressed ZFS. Is this best practice? Because the dual compression will actually result in a larger file size. I’m wondering if it would be better to use a standard volume or is it just better because of the other advantages offered by ZFS? Perhaps it should still be ZFS but not compressed? Interested in peoples thoughts.

[@CBSYS]

I'm thinking of following your series to setup my environment, but my question is there a reason you went with 22.04 instead of 24.04

[@rolfamfelt9946]

Set up pbs prune job and garbage collector. It will save a lot of storage.

[@eevor]

Where is pt3?

[@TechHut]

kzbin.info/www/bejne/bWrIZ354jsiJo7M

[@kriffos]

You really should install PBS on hardware and not as a VM if you are serious about using it for backups.

[@enderst81]

Or pass through the disks to the VM.

[@kriffos]

@@enderst81 This helps a little, but may still be problematic. If your PVE fails, so does the PBS. If you reinstall your PVE, you will not be able to restore VMs from the backup, you will have to reinstall your PBS first.

[@sijahel6284]

​@@kriffosactually ElectronicWizardly have demonstrate how he restore pve with a fresh installed pbs, so as long the datastore are intact in the disks the pbs should able to restore it

[@kriffos]

​@@sijahel6284 I did not say it is impossible, but it is more work and will take longer. You can decide for yourself if that is ok for you or not. I like to keep it simple and prefer a faster recovery.

[@pavlovsky0]

4096!!!!! you did that just to bug folks like me ;-)

[@tubeDude48]

Seagate...NO THANKS! 4096 is the standard, not 4092.