Lost production data after upgrading from Trial to Hobby
l17yxl
HOBBYOP

13 days ago

Hello.

My Railway trial expired and after upgrading to the Hobby plan my service restarted with a clean filesystem.

My application stored important production data inside the container filesystem because I apparently did not configure a persistent volume correctly.

Now all previous deployments show as REMOVED and the current /data/data.json was reset to a new empty file (~324 bytes).

I lost all production data that was entered and accumulated during the last month.

Project: worthy-manifestation

Service: Scryde-L2-Party-Portal

Environment: production

Is there any way to restore old deployment filesystems, snapshots, backups, or recover deleted container data from before the trial expiration?

Thank you.

Solved

3 Replies

Railway
BOT

13 days ago

Unfortunately, data written to the ephemeral container filesystem (outside of a persistent volume) is not recoverable. Container filesystems are temporary and do not survive redeployments, and we do not retain snapshots or backups of previous deployment filesystems. The backup and restore feature only applies to data stored in volumes. Going forward, you can attach a volume to your service to persist data like /data/data.json across deployments.


Status changed to Awaiting User Response Railway 13 days ago


l17yxl
HOBBYOP

13 days ago

I understand the filesystem was ephemeral, but I would still like a human support engineer to confirm whether there is absolutely no way to access removed deployment storage, internal snapshots, temporary recovery data, or infrastructure-level backups from before the trial expiration.

This data is extremely important to me.

Thank you.


Status changed to Awaiting Railway Response Railway 13 days ago


imbriaco
EMPLOYEE

13 days ago

Confirming as a human engineer: there is no way to recover data that was stored on the ephemeral container filesystem. We do not retain removed deployment filesystems, internal snapshots, or infrastructure-level backups of container storage. Once a deployment is removed, its filesystem is gone permanently. Only data stored in a persistent volume is eligible for backup and recovery. For future protection, you can attach a volume to your service at a mount path like /data so that files persist across deployments and restarts.


Status changed to Awaiting User Response Railway 13 days ago


Status changed to Solved imbriaco 13 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...