10 months ago
Dear Railway Support Team,
I am writing to request urgent assistance with recovering data from my MySQL database. Here are the details of my situation:
- Project Information: Project name is "lua-nova's Projects", specifically the subproject "natural-respect" (Project ID: 85f9bf54-098f-462c-b669-72ca2a69c6e9, found in the top left corner of the dashboard]).
- Service: MySQL service, previously deployed successfully last month.
- Volume: "diplomatic-volume", mounted at /var/lib/mysql, still showing consumption.
- Expiration Date: My free trial plan expired on August 21, 2025. I migrated to the $5 Hobby Plan on August 22, 2025.
- Issue: After the expiration, I re-deployed the MySQL service, but the original data did not return. Before the re-deploy, I created new tables with the same names as the old ones, which may have overwritten the original data.
- Logs: The deployment logs from August 22, 2025, 00:23:27 UTC (attached below) show a clean initialization of MySQL 9.4.0 without recovering the previous data:
text
2025-08-22 00:23:25+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.4.0-1.el9 started.2025-08-22 00:23:26+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'2025-08-22T00:23:26.576370Z 0 [System] [MY-015015] [Server] MySQL Server - starting.2025-08-22T00:23:26.703933Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.4.0) starting as process 12025-08-22T00:23:26.710823Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.2025-08-22T00:23:27.716041Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.2025-08-22T00:23:28.220233Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '9.4.0' socket: '/var/run/mysqld/mysqld.sock' port: 3306 - Request: I suspect the new tables overwrote the original data in the "diplomatic-volume". Is there any way to recover the original data from the volume? The service is using the startup command docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --innodb-buffer-pool-size=1G, which disables binary logs, complicating recovery.
I kindly request your immediate assistance, as the expiration occurred less than 24 hours ago, and I am within the 30-day retention window. Please let me know if you can restore the previous data or export the volume for manual recovery. I am available to provide any additional information needed.
Thank you for your support!
Best regards, lua-nova
4 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Awaiting User Response Railway • 10 months ago
Status changed to Solved jake • 10 months ago
jake
Unfortunately if you do not have backups there is no way to recover this
10 months ago
Thank you for your response. I understand that without existing backups, recovery may not be possible. However, I would like to know if there is any way to add or enable a backup option now to prevent future data loss.
Additionally, I migrated to the on August 17, and I’m confused about how this data loss occurred so soon after the migration. Could you please clarify why backups are only offered for [the other service] and not for the plan I’m currently using? Any further details on how I can protect my data moving forward would be greatly appreciated.
Thank you for your assistance.
Status changed to Awaiting Railway Response Railway • 10 months ago
10 months ago
Not with the Hobby plan. You will need to upgrade to Pro for you to enable volume backups for the database.
Status changed to Awaiting User Response Railway • 10 months ago
9 months 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 • 9 months ago