Not necessarily. Due to the inherent trade-off between security and convenience, it’s possible for a given piece of software to be simultaneously:
As convenient as it can be without sacrificing security (i.e., the only way to make it more convenient would be to give up some security), and
Less convenient than other options (which are able to be more convenient because they aren’t as secure).
(To be clear, I don’t think the Qubes backup tool, or really any piece of software in the real world, actually achieves this.)
No, that’s not the case. For example, sometimes I:
Start the backup.
Go do other stuff.
Come back and see that the backup is done. Start the verification check.
Go do other stuff.
Come back and see that the verification check is done. Do whatever else I need to do with the backup.
Steps 1, 3, and 5 combined don’t take that long, so the total time I actively have to spend on the backup process isn’t that long.
(To be clear, I do think there’s a lot of room for improvement here.)
Well, at least the verification doesn’t take nearly as long as the backup itself, so it’s not quite as bad as starting the whole procedure over, but I’ve long thought it would be more convenient to have an option to automatically verify the backup file upon creation.
I think this is different from what he meant. I think he meant something more like “a bug in the backup process that sometimes causes random data to be missing from the backup.” By contrast, this issue is more like, “X isn’t included in backups by default, but users would benefit from it being included, so we should figure out a way to start including X by default.”