5 days ago
Hi Railway Support,
I need help exporting production Postgres volume data for a migration to AWS.
Project: mullbery
Project ID: f4dc7081-465b-4076-b5ef-b8eef02c5218
Environment: production
Account/email: sgashinth@gmail.com
Relevant services/volumes:
-
Postgres service ID: dda52f09-dae6-49b6-a5e9-77406fd44c18
Volume: postgres-volume
Volume ID: 0ccddb98-e33a-4807-990b-b9816310379e
Volume instance ID: 41be394f-6a88-4ea2-8f8b-6d38e8461eaa
Current size shown: about 120 MB
-
Postgres-bSki service ID: d125bdd4-bc7e-4f4c-9310-8254b92e983b
Volume: postgres-volume-4NuK
Volume ID: f39b900c-193c-4b2f-818d-6faac1d1b36c
Volume instance ID: cd7509cb-a54f-4854-ba6e-fc9d471a97bc
Current size shown: about 116 MB
The services are currently offline / NO DEPLOYMENT, and attempts to use pg_dump through the public TCP proxies fail because the server closes the connection. Attempting to start the Postgres service through the API/CLI returns: "Your trial has expired. Please select a plan to continue using Railway."
We urgently need a safe export of these Postgres volumes, preferably a pg_dump/custom dump if Railway can start the database temporarily, or a raw volume/backup export if that is the only option. The goal is to restore the database into AWS without losing production customer data.
Please let us know the fastest supported way to obtain the database export or temporarily enable access long enough to run pg_dump.
1 Replies
5 days ago
Your workspace subscription is currently inactive, which is why the Postgres services cannot start and the TCP proxy connections fail. Your volume data is still attached and has not been deleted. To regain access, resubscribe from your workspace billing settings, and once the subscription is active you will be able to start the Postgres services and run pg_dump through the TCP proxy as usual.
Status changed to Awaiting User Response Railway • 5 days ago