Enhancement: simplify configuration for multiple database backups #31

New Issue

MrUnknownDE · 2026-04-05T16:15:37+02:00

MrUnknownDE commented

2026-04-05 16:15:37 +02:00

Originally created by @ced455 on 3/25/2026

Description:

At the moment, configuring backups for multiple databases requires creating a separate configuration for each one.

In environments with many databases, this can lead to a repetitive workflow, as similar configuration steps need to be performed multiple times.

Suggestion:

It could be helpful to introduce a way to duplicate an existing backup configuration.

Such a feature would allow:

Reusing the same settings from an existing configuration
Reusing the same readonly user if one was created during the initial setup
Updating only the database name

Benefits:

This would streamline the process of adding new databases by reducing the amount of manual input required.
Instead of repeating the full configuration each time, the workflow could become:

Duplicate an existing configuration
Adjust the database name
Save

This approach could make managing backups for multiple databases more efficient while keeping the current flexibility.

*Originally created by @ced455 on 3/25/2026* **Description:** At the moment, configuring backups for multiple databases requires creating a separate configuration for each one. In environments with many databases, this can lead to a repetitive workflow, as similar configuration steps need to be performed multiple times. **Suggestion:** It could be helpful to introduce a way to duplicate an existing backup configuration. Such a feature would allow: * Reusing the same settings from an existing configuration * Reusing the same readonly user if one was created during the initial setup * Updating only the database name **Benefits:** This would streamline the process of adding new databases by reducing the amount of manual input required. Instead of repeating the full configuration each time, the workflow could become: 1. Duplicate an existing configuration 2. Adjust the database name 3. Save This approach could make managing backups for multiple databases more efficient while keeping the current flexibility.

MrUnknownDE closed this issue

2026-04-05 16:15:37 +02:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/databasus#31