Restore only archives you intend to trust. KUHBS does not inspect an archive for malware, and restoring old application state can reintroduce a previous compromise.
Prepare the targets and storage
The destination KUHs must already exist and be halted. Start the configured backup Qubes OS VM, attach and unlock the storage, and mount it so the archives are available under /mnt/kuhbs-backup.
Restore preflights the complete explicit request before changing its targets. It overlays archive contents onto the configured destination paths; it does not delete destination files that are absent from the archive and is not an exact whole-disk rollback.
Run the restore
Use Restore on the KUHB card in the graphical interface, or run:
kuhbs restore <kuhb-id>
Review the result before starting the restored KUHs, then verify each application and the minimum data you expected to recover.
Restore the smallest necessary dataset first. Keep older archives offline until the restored application has been started, checked, and confirmed not to require any additional historical state.
When a matching archive is available during Create, KUHBS can restore it before running the KUHB’s setup scripts. Keep only the archives you intend to use in the active backup directory before rebuilding.
Next: Upgrading KUHBS Itself .