N/A

Hello, the native backups feature does not support sending the backups to S3 to begin with.

Right, sorry. I can't find the documentation on this qickly, any chance you can help with a link?

awesome, thanks! for context - I'm trying to estimage the potential cost for us if we'd move to railway. since backups are priced at $0.25/gb it looks like it's cheaper to send data to s3 and pay for egress anyway 🙂

you may have missed a crucial bit of information from that page, you are only charged for the incremental size

yeah, not sure I understand that fully. can you elaborate on the example of a 100GB potgres with daily backups retained for a month? what would be the cost?

I'm a bit confused, so this is not pg_dump type of backup? just a volume replica?

there's no way for me to tell you exactly.

incremental backups mean we do not charge you for data that still exists in the current volume or previous backups.

that's correct, this is not pg_dump, it is a ZFS snapshot.

you will not be paying for 100gb of storage per every backup you do.

say you have a volume with 100gb of data on it, you take a backup, and then delete 1gb of data, well then you only have to pay for that deleted data.

unless you plan to delete the entire contents of your volume, backups will be far cheaper paying for the egress to s3

so if I have a volume of 100gb, the base backup cost is $25 and then if the volume growth by 10GB a month, the price will increase by $2.5 each month?

there is no base backup cost, you'd pay for the data currently in the volume though.

you store more data, yes of course the cost will increase.

all-right, that's quite confusing, but anyway - thanks a lot for the help, appreciate it!

tl;dr it's going to be cheaper than egress to s3

thanks! the other concern is keeping backup with the same provider we host the services

you are protected from any platform faults on our side, as we take our own backups too

!s