8 months ago
Project ID: 9919c9fe-50ab-4ee5-8f7d-7f838a5a1dce
Service ID: 42667f90-2626-4dc2-b6ad-c53542e903b8
SITUATION:
My production MySQL service lost all data during Railway's forced Metal migration.
TECHNICAL DETAILS:
- MySQL service was running
- Database contained production data
- After migration: complete database reinitialization, all tables empty
DOCUMENTATION DISCREPANCY:
According to Railway's Metal migration docs, services without volumes should be treated as "stateless migrations" with:
- "No downtime"
- "Just landing into a new region"
However, I experienced complete data loss and reinitialization, which contradicts the documented stateless migration behavior.
RECOVERY REQUEST:
Your documentation mentions:
1. Backups created during migration process
2. Rollback options for failed migrations
3. Data preservation for stateless deployments
Can Railway engineering staff help me:
- Attempt the documented rollback procedures
- Check if data exists in the old region before cleanup
@Railway Team - Need official engineering support only
1 Replies
8 months ago
Hello,
Your Postgres database does not have a volume, you deleted it 5 months ago -
Without a volume, data persistence is not possible, so unfortunately, the data that was stored only temporarily would be gone, and it would be irrecoverable.
No backup was created before the migration because there was no volume to back up.
Rollbacks do not capture temporary data, so this would not be applicable.
There is no data reservation for stateless services; by the very name, they are stateless.
Going forward, I recommend you add a volume at the correct mount point so that the database will have persistent storage.
Best,
Brody
Attachments
Status changed to Awaiting User Response Railway • 8 months ago
7 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 • 7 months ago