a month ago
Hello Railway Support,
I am the owner of a Railway workspace containing the LexProtec project.
Our trial has expired, and the dashboard indicates that our PostgreSQL volume data is scheduled for deletion on November 23, 2026.
We have PostgreSQL volumes associated with two environments: production and preview-2-2-c. Both environments currently have no active deployments.
Before upgrading to the Hobby plan, I would like to confirm the following:
- Will upgrading to Hobby prevent the scheduled deletion of the existing PostgreSQL volumes in both environments?
- Can the upgrade be completed while keeping all application and PostgreSQL services stopped?
- If upgrading automatically resumes any services, is there a supported procedure to prevent this?
- Is there a supported way to preserve or export the PostgreSQL volume data without starting the original application or database service?
- Can Railway provide temporary preservation while we arrange a verified backup?
Please do not restart, redeploy, restore, modify, or delete any resources without my explicit authorization.
Our priority is data preservation, not immediate application availability.
Thank you for your assistance.
1 Reply
a month ago
Both Postgres services still have their volumes attached, in production and in preview-2-2-c. Subscribing to Hobby does not create a new database or restore a backup. Recovered deployments mount the existing attached volume. We can't confirm the deletion date from here, so check that the deletion notice is gone from the dashboard after subscribing.
You can't activate Hobby and keep services stopped. Clicking "Deploy with Hobby" only opens the subscription form. Once you click "Subscribe to Hobby Plan" and the subscription becomes active, we automatically redeploy the deployments that were stopped when the trial ended. That covers every project and environment in the workspace, not only the service you have open. No setting lets you skip this or choose which services come back. These are normal redeployments, so any pre-deploy command or start-command migration on your application services will run.
There is also no supported way to export or browse Postgres volume data while the database service is stopped. Volume file access and data exports both need the service attached and running. If you want a verified backup before the application starts, subscribing will still bring the Postgres and application services back together. Before you subscribe, remove any migrations from the application's pre-deploy or start commands so they can't change the data on that first deploy.
We have not restarted, redeployed or modified any of your resources.
Status changed to Awaiting User Response Railway • 26 days ago
19 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 • 19 days ago