2 years ago
The most relevant thread I've found so far for state-of-the-art db backups in railway is https://discord.com/channels/713503345364697088/1126783082859614260, which suggests that older db backup methods like those suggested here https://blog.railway.app/p/postgre-backup will incur an egress tax, and that the best bet is volume-based backups which were in the works as of 2023-07-08. I can't find any hooks or mention of volume backups since then, is that still in the works. If so, does the current state-of-the-art of the railway db backups still incur an egress tax?
9 Replies
2 years ago
sending your backups to an external storage provider will incur egress fees.
volume snapshotting is planned, but there is currently no eta.
instead, send your backups to a minio service within your project across the private network, that way theres no egress fees, only the cost of the storage used.
though depending on the size of your database, you would need to weight the costs of egress vs. disk.
is there a crossover at some point, where it's cheaper to network i/o a MB than store it? or you're saying for storing multiple backups on the same volume?
2 years ago
im sure there would be, you would have to do the math with the size of database you plan to backup
ok, so ingress and egress are per project, not per service, yeah? sorry i'm sure that's in the docs somewhere and i haven't looked it up, but it seems implied by what you're saying. a MB leaving one service and travelling to another via private network is effectively not counted?
2 years ago
railway doesnt charge for public ingress, only public egress.
a MB leaving one service and travelling to another via private network is effectively not counted?
correct, only data leaving the private network is charged
2 years ago
there are currently no good templates im aware of that backup to a volume, what i would do for that is pair the official backup template with the minio template