Skip to content
Recover MySQL Data After Trial Expiration
lawrencethetsokabi-dot
OP

23 days ago

Subject: Urgent — Recover MySQL Data After Trial Expiration

Hello Railway Support,

My Railway trial has expired, and my Matsepe School Management System is offline. My project has two services: "matsepe-school-management" and "MySQL".

The MySQL service has a persistent volume attached, but no backups are listed. My workspace currently shows only paid plan options.

I need to preserve my existing school database and migrate the application to another hosting provider because my budget is very limited.

Could you please confirm:

  1. Whether my original MySQL volume and database files are still intact.
  2. Whether the volume has a scheduled deletion date or data-retention deadline.
  3. Whether I can recover the existing database and export it safely.
  4. Whether temporary database access is possible without committing to an ongoing paid plan.

Please do not delete, wipe, detach, or reset my existing MySQL volume. Preserving the school records

Solved

3 Replies

Railway
BOT

23 days ago

Your MySQL volumes are still there: each MySQL service in your workspace has its volume attached, holding roughly 155-160 MB of data, and neither is marked for deletion. Your services are offline because their deployments were stopped when the trial ended. Stopping them did not wipe the volumes.

To get to the data, the database has to run again. Subscribing to Hobby from the Plans page automatically redeploys the services that were stopped. The MySQL service comes back on its existing volume, not on a new empty database, and you can then export with your usual MySQL dump tool. Subscribing also redeploys your application service, so any migrations in its start or pre-deploy command will run against the database.

We can't give you a fixed date until which the volume will be kept, and we can't promise it will be kept indefinitely while the workspace stays on the expired trial.


Status changed to Awaiting User Response Railway • 23 days ago


Railway

Your MySQL volumes are still there: each MySQL service in your workspace has its volume attached, holding roughly 155-160 MB of data, and neither is marked for deletion. Your services are offline because their deployments were stopped when the trial ended. Stopping them did not wipe the volumes. To get to the data, the database has to run again. Subscribing to Hobby from the Plans page automatically redeploys the services that were stopped. The MySQL service comes back on its existing volume, not on a new empty database, and you can then export with your usual MySQL dump tool. Subscribing also redeploys your application service, so any migrations in its start or pre-deploy command will run against the database. We can't give you a fixed date until which the volume will be kept, and we can't promise it will be kept indefinitely while the workspace stays on the expired trial.

lawrencethetsokabi-dot
OP

23 days ago

My main priority is to recover and export the existing Matsepe High School MySQL database without upgrading to Hobby, if possible. Please let me know whether temporary access or another recovery option is available. I want to preserve all existing school records and avoid creating an empty replacement database.


Status changed to Solved lawrencethetsokabi-dot • 23 days ago


Status changed to Awaiting Railway Response dizzydes90 • 23 days ago


dizzydes90
EMPLOYEE

23 days ago

There isn't a temporary-access or export route on our side: we don't export or hand over volume contents, and a stopped database can only be read by running it again, which needs an active plan on the workspace. The lowest-cost path is Hobby ($5/month, which includes $5 of usage): subscribing redeploys the MySQL service on its existing volume, you export with mysqldump, and you can cancel afterwards. Your data stays on the volume as it is until then; we haven't touched it.


Status changed to Awaiting User Response Railway • 23 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...