a month ago
Hello Railway team,
We’re documenting data retention and account-deletion procedures for our application.
Our Postgres service’s Backups tab shows:
- One “Pre-Security-Patch Backup”
- an existing platform-created backup.
- No backup schedule
- A Restore button, but no visible expiry date or individual deletion option
Could you confirm:
- Does this platform-created backup expire automatically? What retention period or expiry date applies?
- Can this backup be deleted individually without affecting the live PostgreSQL database or volume? If so, what is the supported procedure?
- After deletion or expiry, are any recoverable copies retained by Railway, and for how long?
- Is there published documentation covering retention for these platform-created security-patch backups?
This is an information request only. Please do not delete, restore, or modify the backup, database, or volume.
Thank you.
3 Replies
a month ago
The Pre-Security-Patch Backup is a snapshot of your Postgres volume taken immediately before a Railway-initiated security patch, and it is kept for 30 days from when it was taken. When that expiry is reached it is deleted automatically. The expiry the backup carries is the entire lifecycle, with nothing extra on top of it.
Deleting an existing backup is not restricted by plan, so a Hobby workspace can remove one that is already there. When you delete a backup yourself, it is removed at that point instead of waiting for its expiry.
After a backup has expired or been deleted, we do not restore data from it.
General backup behavior, including the scheduled retention periods, is covered in our volume backups documentation.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
The Pre-Security-Patch Backup is a snapshot of your Postgres volume taken immediately before a Railway-initiated security patch, and it is kept for 30 days from when it was taken. When that expiry is reached it is deleted automatically. The expiry the backup carries is the entire lifecycle, with nothing extra on top of it. Deleting an existing backup is not restricted by plan, so a Hobby workspace can remove one that is already there. When you delete a backup yourself, it is removed at that point instead of waiting for its expiry. After a backup has expired or been deleted, we do not restore data from it. General backup behavior, including the scheduled retention periods, is covered in our [volume backups documentation](https://docs.railway.com/volumes/backups).
a month ago
Thank you. Could a Railway team member confirm that the stated 30-day retention applies specifically to platform-created Pre-Security-Patch Backups, and clarify whether any recoverable copies remain afterward?
My dashboard shows an existing backup with only a Restore button. What is the supported way to view its exact expiry and delete it individually without affecting the live database or volume?
Please provide information only; do not modify or delete anything.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Yes, the 30-day retention applies specifically to the Pre-Security-Patch Backup: it is a snapshot of the Postgres volume taken immediately before the security patch, and it is deleted automatically when its 30-day expiry is reached. After a backup expires or is deleted, we do not perform data restoration from it.
You can see its exact expiry by expanding the backup in the Backups tab, where the details show an "Expires" field.
Our earlier reply was wrong about deletion on Hobby. Deleting an individual backup is only available on Pro, which is why your dashboard shows only the Restore button. On Pro, deletion is in the menu next to each backup and removes only that snapshot, without affecting the live database or volume. On Hobby, the backup is removed automatically at its expiry.
Status changed to Awaiting User Response brody • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 29 days ago