OriginChain docs
dashboard · backups

Backups in the dashboard.

Inspect your instance's recovery points and continuous backup streaming status. You'll need a running instance and the Backups area is read-only - there are no destructive actions here. Restoration lives on its own page; see Restoration.

  1. 1. Open the sidebar and click Backups (or jump to /app/backups).
  2. 2. Pick your instance from the Instance dropdown.
  3. 3. The Recent snapshots table lists per-tier snapshots (Tier 1: 90d, Tier 2: 365d, Tier 3: 365d).
  4. 4. The Continuous archive shipping table lists every segment + checkpoint shipped to the archive.
  5. 5. The Continuous backup stream panel shows last-shipped timestamp, last-shipped LSN, and effective RPO. Pause/resume control is available when the Sub-Second PITR add-on is active.
OriginChain Schema Query Backups Logs DATA / BACKUPS Backups Recent snapshots 7 SNAPSHOTS snap-08fa2 · 2026-05-02T03:00Z · 14.2 GiB · ready snap-08e91 · 2026-05-01T03:00Z · 14.1 GiB · ready snap-08d4c · 2026-04-30T03:00Z · 13.9 GiB · ready Continuous archive shipping GA 142 SEGMENTS seg-000142 · 64 MiB · 12 s ago seg-000141 · 64 MiB · 4 m ago Continuous backup stream RUNNING ADDON: SUB-SECOND PITR LAST TS 2026-05-02T03:14:09.412Z LSN 0x9a3f:21c RPO ~ 0.6 s PAUSE RESUME 1 5
backups page · snapshots · continuous archive shipping · continuous backup stream

What each piece means

Snapshots
Taken automatically: hourly on Tier 1, every 15 minutes on Tier 2, every 5 minutes on Tier 3. Each snapshot is an image of the engine state at that point. Restorable to a fresh instance via the dashboard or HTTP API.
Continuous archive shipping (GA, all tiers)
Once a log segment is rolled, it ships to the archive continuously. Restoration replays the archive up to a chosen target timestamp at archive precision, which is sufficient for most workloads.
Continuous backup stream (Sub-Second PITR add-on)
Sub-second LSN-precise PITR. The continuous backup stream pushes the live log between roll events on a sub-second cadence so the archive is never more than a few seconds behind production. Tune the window/min-delta to trade archive cost against RPO precision.
RPO (Recovery Point Objective)
The maximum data loss window if the writer dies right now. With continuous archive shipping the RPO is the time since the last roll event (typically a few minutes). With the continuous backup stream running, the RPO is the configured window - typically under one second.

Common errors

  • backups add-on not enabled on the continuous backup stream section - enable Sub-Second PITR from /app/billing/addons.
  • no snapshots yet - the instance is younger than its tier's snapshot cadence. Wait for the next scheduled snapshot.
  • continuous backup streaming disabled - the add-on is enabled but the operator-side spawn flag has not been set. Contact support@originchain.ai.
  • RPO drifting - last-shipped timestamp is more than a minute behind wall clock. Check /app/metrics for shipper backpressure or archive throttling.
  • instance paused - snapshots and continuous backup streaming pause when the instance is paused. Resume from /app/instances.