There are use-cases where one would want to backup the same snapper config to multiple borg repositories, possibly with different encryption/retention settings. This is not possible at the moment, as snapborg_backup=true is written to the snapper snapshot userdata as soon as it has been backed up and this is obviously too little information if we have multiple borg repos.
This could be solved in 3 ways:
- Don't use snapper snapshot userdata at all and create a new database specific to snapborg where the mappings are stored.
- Encode the backup information in the snapper userdata
- Write the snapper snapshot ID in the borg backup metadata (name) and on each execution of snapborg run
borg list beforehand to determine which snapshots have already been backed up
There are use-cases where one would want to backup the same snapper config to multiple borg repositories, possibly with different encryption/retention settings. This is not possible at the moment, as
snapborg_backup=trueis written to the snapper snapshot userdata as soon as it has been backed up and this is obviously too little information if we have multiple borg repos.This could be solved in 3 ways:
borg listbeforehand to determine which snapshots have already been backed up