Qubes-scripts VS wyng-backup

No, Qubes don't use this qube to fetch updates. I personally don't use the Qubes Updater for that reason, I have a lot of debian/fedora StandaloneVM/AppVM and only a few are listed as upgradable. I use this script, there is a way to upgrade all VMs with Salt too but I can't find anything to exclude what I want (ex: Windows), when I see something available to upgrade, I just start this script in dom0 and forget about it until it end.

For people who don't want to use ZFS but are okay with LVM: wyng-backup (formerly sparsebak)

https://github.com/tasket/wyng-backup

Tasket/wyng-backup: Fast Time Machine-like backups for logical volumes\ (3 comments)

Backups: This is a major problem for internet-isolated VMs. For internet-isolated VMs, I use this tool: https://github.com/tasket/wyng-backup. But it does only backup the Qube from the shutdown state. The Qube doesn't need to be shutdown, but it doesn't use the live volume. (You can actually run it on live volumes, but it's not supported for that.) In internet-connected VMs, I just use restic or borg. You're right that an offline backup solution is actually more complicated in this regard. The simple way of attaching a USB drive will only attach to one Qube at a time. Now there should be a way to attach the USB drive to only a backup qube, and do some sort of passthrough between the Qubes, but I don't know exactly how to do this.