Skip to content
Subject: Supported consistent volume export and isolated restore procedure Hello Railway Support,
thanhvn2003
OP

a month ago

Subject: Supported consistent volume export and isolated restore procedure

Hello Railway Support,

Our production service factory-digital-web uses a persistent volume mounted at /data, with FACTORY_DIGITAL_STATE_ROOT=/data. It stores application JSON records and receipts. A manual native backup was created on 14 October 2026, shown as 34 MB.

Before deploying a website update, we need to verify that these records can be recovered safely.

What supported procedure can we use to obtain an application-consistent copy of the entire volume and validate its restoration in an isolated location, without replacing the live volume or starting application/provider actions?

Please clarify:

  1. Whether a native backup can be exported or restored to a separate test target.
  2. If not, whether CLI volume-directory download is suitable, and how all writers should be paused and drained to ensure consistency.
  3. Required access, expected downtime, and any additional charges.

We have not initiated a restore. Please provide guidance only; do not change our resources.

Thank you.

Closed

3 Replies

Railway
BOT

a month ago

A native volume backup can't be exported as a downloadable archive or restored to a separate test target. Restores only work within the same project and environment. A restore creates a new volume and stages a swap onto your service, and deploying that swap redeploys the live service, so it isn't an isolated test. If you discard the staged swap, the restored copy stays unattached, and there's no supported way to browse, download, or attach that copy for validation.

A native backup is a point-in-time snapshot of the whole volume, with every file captured together. That makes it crash-consistent, not application-consistent: we don't pause your application or flush its in-memory state when the snapshot is taken.

The CLI can download a directory from the volume while it's attached to a running deployment of the service, for example railway volume files download /data ./local-copy (CLI reference). That reads the live volume. There's no platform control that pauses or drains writers during the download, so getting a consistent copy depends on stopping writes within your own application first. You can then validate the downloaded copy wherever you like, outside the live service.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway

A native volume backup can't be exported as a downloadable archive or restored to a separate test target. Restores only work within the same project and environment. A restore creates a new volume and stages a swap onto your service, and deploying that swap redeploys the live service, so it isn't an isolated test. If you discard the staged swap, the restored copy stays unattached, and there's no supported way to browse, download, or attach that copy for validation. A native backup is a point-in-time snapshot of the whole volume, with every file captured together. That makes it crash-consistent, not application-consistent: we don't pause your application or flush its in-memory state when the snapshot is taken. The CLI can download a directory from the volume while it's attached to a running deployment of the service, for example `railway volume files download /data ./local-copy` ([CLI reference](https://docs.railway.com/cli/volume)). That reads the live volume. There's no platform control that pauses or drains writers during the download, so getting a consistent copy depends on stopping writes within your own application first. You can then validate the downloaded copy wherever you like, outside the live service.

thanhvn2003
OP

a month ago

hỏi tiếp Railway Support có quy trình được hỗ trợ để dừng hoàn toàn ứng dụng rồi sao chép volume khi ứng dụng đã dừng hay không, gồm khả năng truy cập dữ liệu lúc đó. Chỉ chuẩn bị câu hỏi, chưa thao tác


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

Apologies, we only correspond in English. Please open a new thread in English.


Status changed to Closed Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...