2 months ago
We have restored a Postgresql volume from a backup 2 weeks ago. Issues:
- The restored volume did not inherit the backup schedules from the original volume and thus no new backups have been created (we had another issue just now and no new backups since recovery.. massively dangerous UX)
- It errors when I try to manually create a backup from it
2 Replies
2 months ago
Thanks for reporting this.
On backup schedules: restoring from a backup creates a new volume (you can see it has a different name based on the backup timestamp). Since it's a new volume, you'll need to configure backup schedules on it separately. The original volume with its schedules is still retained but unmounted. We agree this should be made clearer in the UI during the restore flow so you're not left without backup coverage unknowingly.
On manual backup failing: when restoring, we copy all backup history from the source volume to preserve recovery points. However, this can exceed the manual backup count limit (10 per volume), which then blocks new manual backups. Scheduled backups are not affected by this limit. You currently have 16 backups on the restored volume.
Workaround: delete 7+ older backups from the restored volume to get under the limit and unblock manual backup creation.
Status changed to Awaiting User Response Railway • 2 months ago
sam-a
Thanks for reporting this. On backup schedules: restoring from a backup creates a new volume (you can see it has a different name based on the backup timestamp). Since it's a new volume, you'll need to configure backup schedules on it separately. The original volume with its schedules is still retained but unmounted. We agree this should be made clearer in the UI during the restore flow so you're not left without backup coverage unknowingly. On manual backup failing: when restoring, we copy all backup history from the source volume to preserve recovery points. However, this can exceed the manual backup count limit (10 per volume), which then blocks new manual backups. Scheduled backups are not affected by this limit. You currently have 16 backups on the restored volume. Workaround: delete 7+ older backups from the restored volume to get under the limit and unblock manual backup creation.
2 months ago
Thanks, please make errors say this ie. too many backups and I figured that might be the case with the restored volume logic but again should be highlighted. This was a really high-risk near-miss as it's our auth db.
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved jake • 2 months ago