19 days ago
Hi, my trial plan expired and my Postgres service went offline. I have important production data in the database that I need to export urgently.
Could you please either:
- Temporarily restore access to my Postgres service so I can run pg_dump
- Or provide a database backup/dump file
The data includes important user and account information that I cannot lose.
Thank you.
4 Replies
19 days ago
Your workspace subscription is currently inactive, which is why your Postgres service has been stopped. Your volume data is still retained, so you can recover it by resubscribing to a paid plan at your billing settings. Once the subscription is active, you can redeploy your Postgres service and run pg_dump to export your data.
Status changed to Awaiting User Response Railway • 19 days ago
Railway
Your workspace subscription is currently inactive, which is why your Postgres service has been stopped. Your volume data is still retained, so you can recover it by resubscribing to a paid plan at [your billing settings](https://railway.com/workspace/billing). Once the subscription is active, you can redeploy your Postgres service and run pg_dump to export your data.
19 days ago
I understand I need to subscribe to recover data. However, I'm from Russia and cannot use international payment cards due to sanctions. Is there any other way to get a backup of my data without subscribing? The volume data is still retained as you mentioned.
Status changed to Awaiting Railway Response Railway • 19 days ago
Status changed to Open Railway • 19 days ago
19 days ago
You can go to https://railway.com/workspace/plans and select the Free plan. You'll then be able to redeploy your database and run pg_dump.
19 days ago
0x's answer is the key part: if Free is available for the workspace, switch back to Free, redeploy Postgres, and dump before doing anything else.
After redeploy, don't run app migrations/startup as the recovery step. Just dump the DB first: from your laptop against the public database URL, or from a temporary Railway service in the same project/network if public networking is off.
Then get that dump somewhere safe before touching the project again. I'd also verify tables and row counts before deleting/recreating anything, because a fresh Postgres service can look "fixed" while still not being the old data.