12 days ago
Project: misterjobsai's Project (gps-deuda-backend)
Environment: production
Service: Postgres
Plan: Pro
I initiated a volume backup restore from the Backups tab
on my PostgreSQL service.
Backup selected: 2026-06-24 00:10 UTC
Size: 216 MB
Type: manual volume backup
After the restore process completed:
-
A new volume "postgres-2026-06-24 00:10 UTC" appeared
in the project.
-
The Postgres service shows badge "Edited — 2 Changes".
-
Clicking the badge shows no detail, no staged changes,
no Deploy button, no Discard option anywhere in the UI.
Actions NOT taken:
- No Deploy has been triggered.
- No DATABASE_URL has been changed.
- No volume has been manually mounted or detached.
- No additional Restore has been initiated.
Current production status:
- Health check: {"status":"ok","db":"conectada"}
- PostgreSQL reachable and serving traffic normally.
Please confirm:
-
Which volume is currently mounted to production Postgres?
-
Is the restored volume staged and pending deployment?
-
What exactly are the "2 Changes" shown in the badge?
-
How can staged changes be inspected from the dashboard?
-
How can they be discarded safely without deleting
either the production volume or the restored volume?
-
Can the restored volume be attached to a separate
temporary PostgreSQL service for integrity testing?
-
What is the supported procedure for testing a restored
volume backup in isolation without affecting production?
No action will be taken on volumes or deployments until
Railway confirms the current state and safe next steps.
GitHub repo: github.com/MisterJobsAI/gps-deuda-backend
2 Replies
12 days ago
Your original volume (postgres-volume) is still mounted to the Postgres service and serving production traffic, which is why everything is healthy. The restored volume (postgres-2026-06-24 00:10 UTC) is currently unattached and pending deployment. The "2 Changes" represent the staged volume swap (unmount old, mount new). To review and discard, click the "Details" button on the staged changes banner at the top of the project canvas, not the badge itself. From the details panel you can discard individual changes by clicking the "x" next to each one. To test the restored volume in isolation, you can create a new temporary Postgres service in the same environment and attach the restored volume to it at /var/lib/postgresql/data before deploying, which will leave your production service untouched.
Status changed to Awaiting User Response Railway • 12 days ago
7 days ago
Following up on our previous thread about the volume
backup restore.
We have discarded two of the three staged changes
(both mount-path swap entries). One staged change remains:
"postgres-2026-06-24 00:10 UTC will be added"
Current state:
-
Production Postgres service is Online and healthy
-
postgres-volume is still mounted to production
-
The restored volume appears as an independent node
on the project canvas and is not mounted to any service
-
No Deploy or Apply has been triggered
-
Backend health check confirms: {"status":"ok","db":"conectada"}
Please confirm:
-
If we discard this remaining staged change, will the
restored volume remain available in the project as
an unattached volume?
-
Or will discarding this change permanently remove
the restored volume object?
-
Is there a supported way to keep the restored volume
as an unattached object without applying the mount
swap to production?
-
Can this restored volume be attached to a separate
temporary PostgreSQL service for integrity testing?
-
Does discarding this staged change affect the original
backup from which the restored volume was created?
We do not want to:
- modify production
- replace the production volume
- delete the original backup
- lose the restored volume before testing it
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 7 days ago
Status changed to Solved misterjobsai • about 20 hours ago