Skip to content
No-cost recovery/export and retention deadline for offline MySQL volume
briccitly
OP

18 minutes ago

I need help preserving and recovering data from an existing MySQL 8 service on the Free plan. Its persistent volume is named mysql-volume (500 MB, mounted at /var/lib/mysql). The service is offline with no active deployment; the original volume remains attached.

A read-only CLI file listing/export attempt returned:

"Service MySQL has no active deployment in environment production. Deploy or restart the service before using file commands."

We have not restarted it because no charges are authorized.

Please confirm:

  1. Is a free read-only export of the existing data or an existing backup possible without starting a deployment or activating a paid plan?
  2. Are any earlier backups/snapshots available, and what are their dates and exact retention/deletion deadlines?
  3. What is the original volume's exact retention/deletion deadline (date, time and timezone), and is any action required to prevent data loss?
  4. What safe export procedure preserves the original volume and data without deleting, detaching, replacing, overwriting or modifying them?
  5. If a physical export is possible, what exact MySQL version is required, is it crash-consistent or application-consistent, and can a checksum be provided? We will validate restoration before treating it as a recoverable backup.

No charges are authorized. Do not restart MySQL, create a deployment or billable backup, restore over the original data, change the plan, upgrade or initiate billing. If free recovery is unavailable, please explain the limitation before any operation. Please use a secure channel for any backup download or additional account identifiers. No credentials, tokens, database contents or full internal IDs are included in this public post.

Awaiting User Response

1 Reply

Railway
BOT

17 minutes ago

The MySQL service's volume is still attached and in a ready state, holding roughly 239 MB of data. It has no backups or snapshots, so there are no backup dates or retention deadlines to give you.

The volume is not scheduled for deletion. Its data stays in place until someone deletes the volume, the service, or the project, so no action is needed right now to protect it. We can't give you a guaranteed future deletion date.

All file access to a volume, including CLI file commands, works through a running deployment. That is why the CLI asked you to deploy or restart the service. We don't offer a staff-run export, a physical copy of the volume, or a download link, so there is no free read-only export while the service is offline.

If you do bring the service back, the files will come from the live MySQL 8 data directory on that volume. We don't certify whether a copy is consistent and we don't provide checksums. Choosing an export method, checking consistency, and testing a restore are up to you, for example by running a logical dump from the running database and validating it.


Status changed to Awaiting User Response Railway • 17 minutes ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...