If MicroShift service is restarted, it will create a backup for current boot (based on version file which contains that boot id).

Because microshift does not update particular backup - it only creates new ones and deletes old ones, this behaviour will prevent a proper backup from being created when the host reboots.

100%

1. MicroShift svc is running
2. Note the contents of /var/lib/microshift/version
3. Check the contents of /var/lib/microshift-backups
4. Restart MicroShift svc
5. Check the contents of /var/lib/microshift-backups - new backup appeared
6. Restart MicroShift host
7. Check MicroShift's logs (sudo journalctl -u microshift -b 0): log is present "Backup already exists"

MicroShift creates backup on svc restart without host reboot which prevent proper backup from being created on system boot

MicroShift does not create backups without system reboot.

For example, if boot_id obtained from /var/lib/microshift/version is the same as current boot ID, then skip the backup. It should only be created for past, previous boot