OriginChain docs
dashboard · restoration

Restoration in the dashboard.

Restore your instance to a previous point in time. Restoration runs through the operation-backend, which provisions a fresh instance from the chosen recovery point — your existing instance is not modified. You'll need a target timestamp inside the archive coverage window (visible on the Backups page).

  1. 1. Open /app/backups and pick the source instance.
  2. 2. Scroll to Restore to timestamp.
  3. 3. Enter a target timestamp (UTC). With the Intra-Segment PITR add-on, you can also tick LSN-precise for sub-second restoration.
  4. 4. Click Dry run. The preview panel shows which segments will be replayed, the resolved restore LSN, and the estimated restore duration. The Execute button stays disabled until the dry-run succeeds.
  5. 5. Click Execute restore. The destructive-action confirm dialog asks you to confirm. The new instance shows up in /app/instances as restoring, then transitions to running with a fresh bearer issued.
OriginChain Schema Query Backups DATA / BACKUPS Restore to timestamp TARGET TIMESTAMP (UTC) 2026-05-02T03:14:00Z DRY RUN EXECUTE Use intra-segment LSN-precise restore requires Intra-Segment PITR addon Dry-run preview VALID RESOLVED RESTORE LSN 0x9a3f:21c REPLAY PLAN snap-08fa2 · 2026-05-02T03:00Z · base seg-000141 · 64 MiB · replay seg-000142 · 64 MiB · replay (partial) ESTIMATED DURATION ~ 2 m 40 s creates a new instance · existing instance untouched · fresh bearer issued on completion 3 4 5
restore dialog · dry-run preview · execute disabled until dry-run succeeds

What restoration does

Restoration through the dashboard provisions a fresh instance from the closest snapshot before the target timestamp, replays sealed segments up to (and partially through) the resolved LSN, and verifies the snapshot opens cleanly. Your existing writing instance is never touched. The restored instance ships with a brand-new bearer; rotate any clients to it explicitly.

Without the Intra-Segment PITR add-on, restoration is precise to the sealed-segment boundary closest to (but not after) the target timestamp. With the add-on, restoration is precise to the WAL frame nearest the target.

Common errors

  • no archive at that timestamp — the target is outside the archive coverage window. Check Sealed-segment shipping on /app/backups for the oldest available timestamp.
  • restore in progress — only one restore per source instance can run at a time. Wait for the current job to finish on /app/instances.
  • instance not in restorable state — the source instance must be running (not currently restoring). Check the instance status pill before retrying.
  • LSN-precise unavailable — Intra-Segment PITR add-on is not enabled. Either enable from /app/billing/addons or untick the LSN-precise checkbox to fall back to sealed-segment precision.
  • execute disabled — the dry-run hasn't completed (or returned errors). The Execute button stays disabled until you have a successful dry-run preview.