4 months ago
It'd be great to not have to worry about backups on Railway at all.
We offer an S3-backed automated Postgres backup template, but having this in dashboard itself as a tab would be killer.
- Input S3/GCS/some other cloud storage credentials
- Set a schedule
- We automatically
pgdump
/mysqldump
/etc. your database to the configured cloud storage at the schedule you configure
"Popular" meaning widely-deployed on Railway, e.g. Postgres, MySQL, and Mongo. A more generic way of doing this would be automated volume snapshots that we can ship to any cloud storage provider, and/or combining the two (volumes -> ship snapshot; databases -> ship native dumps).
6 Comments
samthompsonkennedy
4 months ago
👆 would be amazing!
I think going for both volume, and "popular" databases would be the way to go, you don't want to lose
pgdumpas an example. We also run other databases such as Chroma vector store, which would be cool to backup as well.
faces-of-eth
4 months ago
I'd add Redis to the list perhaps but echo the original poster's request.
Additionally, being able to load this data, or a seed data file into PR environments or forked environments would be clutch. Right now I'm hacking this as a custom one-off data loader service that only runs in environments lacking a PRODUCTION environment variable
dwaynemac
3 months ago
maybe this could be implemented in a more generic way providing a native backup solution for VOLUMES.
3 months ago
the team has mentioned volume snapshots as the backup method, this would allow taking backups of services that use sqlite databases, along with so much more
dwaynemac
3 months ago
Volume snapshots would be awesome
mbrookson
2 months ago
I’d also say a restore feature would be useful. I’d have a lot more confidence with backups and recovery if it was natively baked in to the platform.