It’s geared towards all the things. The beauty of Veeam is it supports incremental and synthetic backups for all paradigms: file, volume, and system for bare metal and VMs and to a wide array of targets. This makes it very flexible and efficient. You set it and forget it until you accidentally delete something, then you fire it up, load the backup and select what you want to restore from a tree. Peace of mind and lack of headache.
Once you leave Windows you can pretty much throw UX and UI out the window. I’ve given up trying to find solutions that are intuitive or easy to learn; at this point I’m just trying to find things that actually just work at all.
Well, clearly. I agree. But OS setup and config are things that exist, too. And they take time. And it’s really comforting to know that if anything goes wrong you can restore the entire machine to the last backup state, data AND OS, with no worries.
Unless they’ve been backed up, this is quite a non-trivial exercise for me. Setting up a new machine exactly the way I’m comfortable with it can take several days (after being done with work.) I’ve set up Project Trident from scratch twice and it’s not something I enjoyed or would ever like to do again (this isn’t a strike against Trident, it’s just how I find OS setup in general. It’s very involved for me, so I try to minimize its occurrence.)
I guess I understand BSD and ZFS have different paradigms from what I’m used to. I’m a very Point-Click-Done person.
So let’s say hypothetically I do a full ZFS backup to my Ubuntu 18.10 PC and my BSD SSD crashes. What would the process of restoring the entire BSD installation - settings, data and all - from that backup to a new SSD look like?