15 days ago
Hi
I have a question regarding the PITR backup for a Postgres database.
When looking at the template for your Postgres image, I can see you have pgBackRest integrated into that. This enables the PITR feature I can enable in the UI, which seems nice!
As a normal procedure we want to have backups in an external source as well(S3 bucket in this case). As far as I can see I can enable the pgBackRest feature by inserting enviroment variables for my S3 instance. Is that correct?
If that is correct will that make it possible to recover via. the UI? So can we get the same easy-recovery UI with an external backup source?
If that is not possible, do you have any suggestions to "get the best of both worlds"?
1 Replies
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
Railway's PITR feature uses pgBackRest with a single archive repository pointed at a Railway-managed storage bucket. There is no support for a second pgBackRest repository, so you cannot add an external S3 destination alongside the built-in one within the same pgBackRest configuration.
Status changed to Awaiting User Response Railway • 15 days ago
Status changed to Solved madsmhm • 14 days ago