Hello everyone!
How to create full dom0 backup, without qube data, like if i try installed kde, and my system broke after is, i can restore my work dom0 backup and fix my error
Best -in my eyes- always is to boot from external (i.e. loading a live system like TailsOS) and doing a complete image backup from the Qubes disk (with the Gnome tool āDisksā). This will keep all data and after somethings will be broken, you always can put the saved image back (w/āDisksā) to the disk without any problemā¦
the downside is: you often have to do this image backup, after you changed somethings major in Qubes/dom0 (updates / new templates / etc.) which is quite oftenā¦
1 Like
A full disk image is the safest rollback for experimenting with KDE, but I would keep it separate from normal Qubes backups. The built-in Qubes backup is mainly for qubes/templates, not a clean dom0 snapshot/rollback mechanism. Also make sure the image target is offline/unmounted and at least as large as the internal disk; restoring an image overwrites everything, including qube data.
1 Like
If the goal is only to recover from a KDE/dom0 experiment, I would not mix that with the normal Qubes backup workflow. Make a full disk image before the change, or use a real snapshot at the storage layer if your install supports it, then treat restore as āoverwrite the whole diskā.
For a smaller failure, also note the boring rollback path: switch to a tty, check dnf history in dom0, and undo the transaction that installed KDE packages. That is less complete than an image, but often enough if only the desktop environment broke.
Small correction: the Qubes backup tool is good for qubes/templates and some dom0 user config, but I would not treat it as a full dom0 rollback. For a KDE experiment, either image/snapshot before the change, or at least save the dom0 package state first with dnf history and the transaction ID, so you can undo the desktop packages from a TTY if the GUI breaks.