Skip to content
No matter
adbluesoftware
OP

a month ago

.

Solved

1 Reply

Railway
BOT

a month ago

Volume backups and PostgreSQL point-in-time recovery require Pro; Hobby has neither. Scheduled backups run daily (kept 6 days), weekly (1 month) and monthly (3 months). PITR continuously archives WAL, takes a weekly full and daily differential backup, and keeps the last 4 fulls, for a window of roughly 4 weeks starting from when you enable it. A PITR restore creates a new sibling service and leaves the original untouched, while volume backups restore in place and only within the same project and environment. See Point-in-Time Recovery.

Backups are not isolated from the volume or project: wiping a volume deletes its backups, and a dashboard project deletion gives 48 hours to cancel before volumes and backups are destroyed. Backups and PITR data are stored in the service's deploy region, so we have no native cross-region copy or automatic export to storage outside Railway.

For instance failure, PostgreSQL can be converted to high availability with automatic failover. Hobby and Pro include no SLA and no guaranteed RPO or RTO; contractual SLAs and BAAs are part of Enterprise agreements.

For monitoring, our database docs suggest an observability stack such as the Prometheus and Grafana templates. On Hobby and Pro, support runs through Central Station with no live calls.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

25 days 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 • 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...