A KUHBS backup is selective. It archives only the absolute persistent paths configured by the KUHB for participating TemplateVMs, AppVMs, and StandaloneVMs. It is not a whole-disk or whole-VM snapshot.
Prepare the backup storage
The configured backup Qubes OS VM must already exist and be running. Attach, unlock, and mount its storage at /mnt, then confirm that /mnt/kuhbs-backup exists and is writable by the configured backup process.
KUHBS does not start the backup VM or mount the storage automatically. If you need to retain an older archive, copy or rotate it before starting Backup because KUHBS writes directly to the final archive path.
Run the backup
Use Backup on the KUHB card in the graphical interface, or run:
kuhbs backup <kuhb-id>
KUHBS expands the selected KUHB into its configured participating KUHs and writes their archives to the mounted backup directory. Review the command result and confirm that the expected archives exist before relying on them.
Keep a separate offline copy of important archives. A successful backup does not prove that the source data or archive is free of malware.
Periodically test that the mounted storage and expected archives can be read independently of the application being backed up. Record which KUHB and persistent paths each archive is intended to recover.
Next: Restoring KUHBs .