2 hours ago
Hi Railway team,
I accidentally restored an old backup on my MySQL service and deployed the staged change. The restore is now stuck on "Restoring backup..." and I can't cancel it.
- Project: abundant-truth (Project ID: <5caa5f0c-98dc-4770-ba1d-cdc1965f195a>)
- Environment: production
- Service: MySQL
- Backup restored by mistake: "Pre-Security-Patch Backup" (25 days old, 164 MB)
- Original volume: mysql-volume (still in the project, now unmounted)
What I need:
- Cancel / clean up the stuck restore.
- Re-attach the original volume "mysql-volume" to the MySQL service (same mount path as before) so the database returns to its current state.
Please do NOT delete "mysql-volume" — it contains the only current copy of our data.
Thank you!
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
2 hours ago
The restore is no longer running, and there is nothing left to cancel: it finished, created a separate new volume from that 25-day-old backup, and your MySQL service is now mounted on that new volume. Your original mysql-volume is still in the project, unattached, with its data intact (about 203 MB) and its mount path still set to /var/lib/mysql.
To switch back, first detach the restored volume from the MySQL service with railway volume detach --volume <restored volume name>, then attach the original with railway volume attach --volume mysql-volume --service MySQL, using the railway volume CLI commands. Once MySQL is redeployed on mysql-volume, the restored copy is unused and you can keep it or delete it, just make sure you delete the restored one and not mysql-volume.
Status changed to Awaiting User Response sam-a • about 2 hours ago