[Feature Request] Automated Restoration from Backups (Auto-Restore Config) #66

New Issue

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

MrUnknownDE commented

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

Originally created by @K2Dmtz on 3/13/2026

Currently, Databasus provides an excellent experience for automated, scheduled backups. However, to maintain environment parity (e.g., syncing Production data to QA), the restoration process still requires manual intervention. I am proposing a new Auto-Restore feature that allows users to configure a destination database to automatically ingest backups based on specific selection logic.

Use Case

Environment Syncing: Every day, after a production backup is completed, it should automatically be restored to a QA or Staging database to keep data fresh for testing.
Automated Testing: Validating that backups are functional by automatically loading them into a secondary instance.

Proposed Features

"Restore" Tab in UI: A dedicated section to manage restoration jobs, similar to the existing backup configurations.
Backup Selection Logic (Restoration Source):
- Latest Successful Backup: The system automatically identifies and restores the most recent backup with a Success status. This ensures the QA environment is always up-to-date with the very latest production state. OR
- Latest Successful Backup of Specific Date: Allows the user to target a specific point-in-time (e.g., "Restore the latest successful backup from last Friday"). This is critical for debugging issues that occurred on a specific date or running regression tests against historical data.
Auto-Restore Configuration:
- Target: Connection details for the destination database (e.g., QA/Staging).
- Trigger: Option to "Restore immediately after source backup finishes" or run on its own cron schedule.
Security & Maintenance:
- Auto-Decryption: Use the existing secret.key to automatically decrypt and decompress the backup file before restoration.
- Clean Slate Option: A toggle to "Drop and Recreate" the target database to ensure a clean restoration.

Current Workaround
Currently, users must manually download the encrypted file from storage (S3, SFTP, etc.), decrypt it using the secret key, and then run manual pg_restore or mysql commands. Automating this would make Databasus a true end-to-end database lifecycle tool.

*Originally created by @K2Dmtz on 3/13/2026* Currently, Databasus provides an excellent experience for automated, scheduled backups. However, to maintain environment parity (e.g., syncing Production data to QA), the restoration process still requires manual intervention. I am proposing a new Auto-Restore feature that allows users to configure a destination database to automatically ingest backups based on specific selection logic. **Use Case** - **Environment Syncing:** Every day, after a production backup is completed, it should automatically be restored to a QA or Staging database to keep data fresh for testing. - **Automated Testing:** Validating that backups are functional by automatically loading them into a secondary instance. **Proposed Features** 1. **"Restore" Tab in UI:** A dedicated section to manage restoration jobs, similar to the existing backup configurations. 2. **Backup Selection Logic (Restoration Source):** - **Latest Successful Backup:** The system automatically identifies and restores the most recent backup with a Success status. This ensures the QA environment is always up-to-date with the very latest production state. **OR** - **Latest Successful Backup of Specific Date:** Allows the user to target a specific point-in-time (e.g., "Restore the latest successful backup from last Friday"). This is critical for debugging issues that occurred on a specific date or running regression tests against historical data. 3. **Auto-Restore Configuration:** - **Target:** Connection details for the destination database (e.g., QA/Staging). - **Trigger:** Option to "Restore immediately after source backup finishes" or run on its own cron schedule. 4. **Security & Maintenance:** - **Auto-Decryption:** Use the existing secret.key to automatically decrypt and decompress the backup file before restoration. - **Clean Slate Option:** A toggle to "Drop and Recreate" the target database to ensure a clean restoration. **Current Workaround** Currently, users must manually download the encrypted file from storage (S3, SFTP, etc.), decrypt it using the secret key, and then run manual pg_restore or mysql commands. Automating this would make Databasus a true end-to-end database lifecycle tool.

MrUnknownDE closed this issue

2026-04-05 16:15:41 +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#66