From over 175k this morning to this:
root@truenas[~]# zfs list -t snapshot | grep tank | wc -l
4725
I’ll need to monitor over the next few days, but looks like a massive improvement.
Did you make it in addition to PBS or instead of? If the latter – why? I’m planning to set up PBS but still haven’t.
PBS doesn’t back up the Proxmox host (AFAICT), just the VMs on it. In fact, there’s almost no documentation on how to back up the host. This was my solution to do that.
1 Like
Agreed, I’ve once searched it myself. Seems like proxmox and truenas are considering boot-pool as something ephemeral.
And yet, plain zfs snapshots do not contain RAM (iirc snapshots from the proxmox ui do).
I’ve a suspicion that it can cause some problems for restoring machines which have been running during the snapshots. IMO, all these snapshots are similar to restoring from a power-loss moment. Did you have any issues so far?
…which makes sense for TrueNAS–download the config file, upload it to a new installation, and you’re good to go. There’s no equivalent mechanism for Proxmox, unfortunately.
Not as yet. But again, I’m not backing up VMs, just the host.
IIRC, each cluster node contains all the configs from the other node (doesn’t work for the manual host tweaks, though). But that won’t help in the case of natural DISASTAH or hacked cluster.
Ah, makes sense. I didn’t pay enough attention – you have clearly mentioned the OS pools. Thanks for the insight.
P.s. So how do you back up your VMs, then?
That’s PBS.
1 Like