mirror of
https://github.com/databasus/databasus.git
synced 2026-04-06 00:32:03 +02:00
Backup restoration and portability concerns with Postgresus #397
Assignees
MrUnknownDE
Clear assignees
MrUnknownDE
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github/databasus#397
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dudustefanello on 11/19/2025
Hi,
I have a question regarding backup restoration in case of server failure or migration.
How should I proceed to restore backups on a different server if I lose access to the original Postgresus instance? I'm currently using S3 as the storage backend, but I noticed that the objects in the bucket have randomized names, which makes manual recovery difficult.
Additionally, it seems there's no way to back up Postgresus's internal database. This feels problematic, as it prevents transferring the application from one server to another. In issue #95, it's mentioned that backing up the internal database doesn't make sense, but I respectfully disagree — I believe backing up Postgresus's internal database is just as important as backing up any other PostgreSQL database.
Could you clarify the recommended approach for restoring backups in a disaster recovery or migration scenario?
Thanks in advance!