[FEAT] Support Multiple Backup Configurations per Database #394

New Issue

MrUnknownDE · 2026-04-05T16:16:22+02:00

MrUnknownDE commented

2026-04-05 16:16:22 +02:00

Originally created by @SethPheasant on 11/21/2025

Summary

First, thank you for creating and maintaining Postgresus — it’s an excellent tool, and I truly appreciate the functionality and simplicity it brings to managing PostgreSQL backups.

Currently, Postgresus allows only one backup configuration per database. This limitation restricts users to a single backup target and schedule. I would like to request support for multiple backup configurations for the same database, each with its own destination and cadence.

Problem Statement

In many environments, a single backup target is not sufficient for reliability, redundancy, or compliance. For example:

A user may want hourly backups to a local NAS for fast recovery.
In addition, they may want daily or weekly backups to a cloud provider (such as Google Cloud Storage) for off-site disaster recovery.

Because only one configuration can currently be defined, users must choose between competing needs or manually reconfigure backups—both of which reduce resilience and increase administrative burden.

Proposed Enhancement

Enable multiple independent backup configurations per database. Each configuration should specify:

Backup target (e.g., local filesystem, NAS, S3/GCS, etc.)
Backup schedule or cadence
Retention policy
Any necessary credentials or connection parameters

Each configuration should operate independently, allowing a single database to be backed up to multiple destinations on different schedules.

*Originally created by @SethPheasant on 11/21/2025* ### Summary First, thank you for creating and maintaining Postgresus — it’s an excellent tool, and I truly appreciate the functionality and simplicity it brings to managing PostgreSQL backups. Currently, Postgresus allows only one backup configuration per database. This limitation restricts users to a single backup target and schedule. I would like to request support for multiple backup configurations for the same database, each with its own destination and cadence. ### Problem Statement In many environments, a single backup target is not sufficient for reliability, redundancy, or compliance. For example: - A user may want hourly backups to a local NAS for fast recovery. - In addition, they may want daily or weekly backups to a cloud provider (such as Google Cloud Storage) for off-site disaster recovery. Because only one configuration can currently be defined, users must choose between competing needs or manually reconfigure backups—both of which reduce resilience and increase administrative burden. ### Proposed Enhancement Enable multiple independent backup configurations per database. Each configuration should specify: - Backup target (e.g., local filesystem, NAS, S3/GCS, etc.) - Backup schedule or cadence - Retention policy - Any necessary credentials or connection parameters Each configuration should operate independently, allowing a single database to be backed up to multiple destinations on different schedules.

MrUnknownDE closed this issue

2026-04-05 16:16:22 +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#394