6 days ago
Subject: PITR restore range unavailable despite healthy pgBackRest archive
Service:
Postgres-W_9y
Service ID: 1d67db6f-7df7-44d6-a9d7-3d7058afafff
Deployment ID: b963d6d7-c90b-4736-b9ae-94fc49a3d4c5
Image: ghcr.io/railwayapp-templates/postgres-ssl:18
PITR is enabled and the runtime data plane appears healthy:
- deployment: SUCCESS
- stanza-create: SUCCESS
- full pgBackRest backup: SUCCESS
- S3 catalog verification: SUCCESS
- archive-push: SUCCESS
- archive_mode: on
- archive_timeout: 1min
- archived_count: 22
- failed_count: 0
- archive gap: clear
- archive lag: 0
- PostgreSQL primary, not in recovery
- WAL_ARCHIVE variables and bucket wiring are present
However, Railway CLI and the available Backups/PITR interface still report no restore coverage and expose no restore target range.
Please verify or refresh the PITR coverage/control-plane index and confirm when the restore range and restore picker become available. Do not modify, redeploy, replace or delete the source database without explicit approval.
1 Replies
6 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 6 days ago
6 days ago
PITR needs to be enabled prior to the time you want to restore the data to.
Did you enable it before the date/time of the desired restore point?