Description
Currently, a backup task (schedule) in Borg Backup Server can only target a single repository. If a user wants to achieve redundancy (e.g., backing up the same production data to both a local fast storage and a remote offsite storage), they have to duplicate the entire task. This creates a high maintenance overhead because any changes to the source paths or exclusions must be manually synchronized across multiple tasks.
I would like the ability to select multiple target repositories within a single Backup Task / Schedule definition.
The UI could use a multi-select dropdown or checkboxes for the "Target Repository" field.
When the task runs, the server should orchestrate the backups sequentially (or based on the queue/concurrent job rules) for all selected repositories, using the exact same source paths and configurations.
Use Case
As a Backup Administrator,
I want to select multiple target repositories within a single backup task,
So that I can easily maintain redundant backups (3-2-1 rule) without the risk of configuration drift when source paths change.
Alternatives Considered
Two task - but they need to be kept in sync.
Alternatively an implementation could be to define a task that inherits from a parent and only the items that are defined differently in the child-task would be overridden.
Description
Currently, a backup task (schedule) in Borg Backup Server can only target a single repository. If a user wants to achieve redundancy (e.g., backing up the same production data to both a local fast storage and a remote offsite storage), they have to duplicate the entire task. This creates a high maintenance overhead because any changes to the source paths or exclusions must be manually synchronized across multiple tasks.
I would like the ability to select multiple target repositories within a single Backup Task / Schedule definition.
The UI could use a multi-select dropdown or checkboxes for the "Target Repository" field.
When the task runs, the server should orchestrate the backups sequentially (or based on the queue/concurrent job rules) for all selected repositories, using the exact same source paths and configurations.
Use Case
As a Backup Administrator,
I want to select multiple target repositories within a single backup task,
So that I can easily maintain redundant backups (3-2-1 rule) without the risk of configuration drift when source paths change.
Alternatives Considered
Two task - but they need to be kept in sync.
Alternatively an implementation could be to define a task that inherits from a parent and only the items that are defined differently in the child-task would be overridden.