[GH-ISSUE #135] [Feature Request] Support Multiple Backup Destinations for a Single Backup Task #114

Open
opened 2026-02-26 21:34:29 +03:00 by kerem · 0 comments
Owner

Originally created by @bobbycw on GitHub (Sep 28, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/135

Description: Simplifying the process, enhance organization, and reduce setup redundancy, I propose implementing support for multiple backup destinations within a single backup task.

Benefits:

  • Efficiency: Reducing the need to create multiple tasks for the same database.
  • Simplification: Easier to manage and improvement in terms of configuration and maintenance.
  • Flexibility: Ability to add or remove destinations without additional task setup.

Proposed Implementation:

  • User Interface:
    • Introduce a section or UI element within the backup task creation/edit screen for adding multiple backup destinations.
    • Allow users to select local and any available S3 destinations for a single backup task.

Example Use Case: A user wants to back up their PostgreSQL database to both a local disk for faster recovery in case of accidental deletion and to one or more remote S3 services for off-site backup and disaster recovery.

Currently, the user has to create two separate tasks, one for each destination. With support for multiple backup destinations, the user could create a single task and specify both the local disk and any S3 services as destinations.

Hope it's fine I'm using AI to rewrite the post, my original only have 2 lines. That's just too short.

Thanks!

Originally created by @bobbycw on GitHub (Sep 28, 2025). Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/135 Description: Simplifying the process, enhance organization, and reduce setup redundancy, I propose implementing support for multiple backup destinations within a single backup task. Benefits: - Efficiency: Reducing the need to create multiple tasks for the same database. - Simplification: Easier to manage and improvement in terms of configuration and maintenance. - Flexibility: Ability to add or remove destinations without additional task setup. Proposed Implementation: - User Interface: - Introduce a section or UI element within the backup task creation/edit screen for adding multiple backup destinations. - Allow users to select local and any available S3 destinations for a single backup task. Example Use Case: A user wants to back up their PostgreSQL database to both a local disk for faster recovery in case of accidental deletion and to one or more remote S3 services for off-site backup and disaster recovery. Currently, the user has to create two separate tasks, one for each destination. With support for multiple backup destinations, the user could create a single task and specify both the local disk and any S3 services as destinations. Hope it's fine I'm using AI to rewrite the post, my original only have 2 lines. That's just too short. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pgbackweb#114
No description provided.