an hour ago
General procedure guidance only; please do not change any account or infrastructure. Docs limit manual volume backups to 50% capacity. For a stopped PostgreSQL service above that threshold, can support raise this limit without starting/redeploying the service? What supported process captures a current recoverable copy while preserving the original? Can a snapshot be exported or restored to an isolated service without replacing the source attachment? Please clarify required restarts, redeployments and incremental charges. No project IDs, credentials, customer data or private configuration are supplied.
3 Replies
an hour ago
When data is above the 50% threshold, growing the volume first lets manual backups fit again. Live Resize on Hobby and Pro normally runs without downtime. If the volume is at 100% capacity, it switches to an offline resize, which restarts the service.
A backup restore always creates a new volume from the snapshot and leaves the original volume in your project, unmounted. It then stages a change that mounts the restored volume on the same service. Nothing changes until you click Deploy, and Deploy redeploys that service. Backups can only be restored into the same project and environment.
We don't offer a supported way to export a snapshot, or to attach a restored volume to a separate isolated service while the source keeps its current attachment. Support can't do that for you either.
Backups are incremental and copy-on-write. You're billed only for each backup's incremental size, at volume storage rates, charged by the minute and invoiced monthly. A restored volume is a new volume and is billed as storage while it exists. See Backups and Volumes.
Status changed to Awaiting User Response Railway • about 1 hour ago
an hour ago
Please route this procedure question to a Railway support engineer for field-specific confirmation. We have not established actual filesystem utilization: please distinguish VolumeInstance.currentSizeMB, sizeMB, VOLUME_USED_SIZE_BYTES and VOLUME_TOTAL_SIZE_BYTES, including freshness when a service is stopped. Does a manual volume backup work while its attached PostgreSQL service is stopped, without starting/redeploying it or changing the source attachment? If a backup is eligible, can current data be recovered to a separately isolated target without deploying over the original service, or is a controlled source start required for a logical export? The automated answer does not establish those prerequisites. Please clarify the supported sequence and cost calculation. Guidance only; no account/resource changes, limit changes or purchases are authorized. No resource identifiers, credentials or private data are supplied.
Status changed to Awaiting Railway Response Railway • 44 minutes ago
4 minutes ago
There is no supported way to recover current data from a volume backup into a separate, isolated target while the original service stays as it is. A restore always creates a new volume and stages a swap onto the same service. The swap only takes effect when you click Deploy, and Deploy redeploys that service. Discarding the staged swap leaves the original attachment unchanged and the restored copy unattached. We don't support attaching that copy to another PostgreSQL service or exporting data from it, and support can't do this for you either. Restores also only work within the same project and environment.
A logical export such as pg_dump is the way to get a portable copy. It needs a reachable, running database, so a stopped PostgreSQL service has to be started first.
For the 50% rule, compare the volume's used space with its capacity, as shown in the volume's metrics. We can't confirm how fresh those figures stay while the service is stopped, or whether a manual backup will run while its service is stopped. If your plan depends on either point, test the sequence on a non-production copy first.
On cost, backups are incremental and copy-on-write. You're billed only for each backup's exclusive incremental size, at volume storage rates, per minute, and invoiced monthly. A restored volume is a new volume and is billed as storage until you delete it. See Backups.
Status changed to Awaiting User Response mykal • 4 minutes ago