[Feature] Schedule label grouping

[stormbyte]

I do think this one belongs more here:

If the backups are viewed from the schedule perspective is is possible to separate multiple backup folders inside one archive.
When the different schedules have different prefixes it possible too use --glob-archives filter to select relevant archives.

View archives from the schedule point should then use that filter and because we have the schedule information it's also possible to view the reason why a backup is still present.

I use currently the following shell command:

borg prune --dry-run --list --glob-archives "${BACKUP_PATH##*/}_*" --keep-minutely "${KEEP_MINUTELY:-60}" --keep-hourly "${KEEP_HOURLY:-24}" --keep-daily "${KEEP_DAILY:-7}" --keep-weekly "${KEEP_WEEKLY:-4}" --keep-monthly "${KEEP_MONTHLY:-6}" "${REPOSITORY}"

The 'Backups' will hold the data per schedule so the data from the other schedule will not be inside that backup.
Might confuse some people as the list of all backups will show all labels.

The reason I ask this is that if there is no separation then a 1 on 1 relation between the repository and the backup folder would be simpler.
Otherwise the purge scheme will only check for the current set of data and purge all others.
For example if a 5 hour purge schema was setup for 1 and a 1 hour + 7 day + 1 week schema the 5 hour schema will always purge the 7 day and 1 week backups.

[mlapaglia]

Right now we just support 1 repo per folder. Admittedly I personally only scratch the surface of what borgbackup can do. If the functionality you want to add lines up with features supported by borgbackup feel free to implement and open a PR. Make sure the new work lines up with the existing structure/flow/ease of use the rest of the app provides 🙏 if you've got questions about implementation ask, if you've got ideas on refactoring existing functionality lmk. I am a Python/FastApi beginner!

[stormbyte]

I think that if there is only support for 1 repo then either:

• A unique constriant so that a single repo cannot be choosen multiple times.
• A notification that when using the repository multiple times can result in unexpected behaviour
• A link to the documentation of borg https://borgbackup.readthedocs.io/en/stable/usage/prune.html

Or group the schedules per Repository and if there are more then one
then a notification that all schedules will be run on that Repository.

If one does not know that all the prune schedules will be run.
Then the results will be confusing when you miss backups.