Skip to content
Start free
All products

Database storage

A home for your data.
A plan for recovery.

Store application data with dedicated capacity, regional snapshots and documented recovery options.

Start free Review deployment options

Choose capacity. Prepare recovery.

Daily storage snapshots provide the recovery baseline for dedicated configurations.

Regional storage, snapshots and recoveryIllustrative example
Your chosen regionDedicated configuration
WriterActive application data
Asynchronous replicationStandby may lag
Optional standbyAvailability configuration
Daily storage snapshotRecovery baseline
Encrypted snapshot archiveStored in the instance's region
Recover into a fresh instanceChoose an available recovery point
  1. Earlier snapshotRetained history
  2. Selected snapshotRestore source
  3. Later changeFor example, a bad import
  4. Fresh instanceValidate, then reconnect

Optional archived changes extend a snapshot when available. Archive streaming remains a preview.

  1. Configure your instance

    Choose a region and dedicated compute and storage for your workload. Review capacity, availability and recovery settings together.

  2. Recover from an available point

    Restore into a fresh instance using the selected snapshot and available archived changes. Check the recoverable point before choosing your target.

Archive streaming is an opt-in preview; plan current recovery around daily snapshots.

How recovery works

Why OriginChainDB

Dedicated resources

On dedicated configurations, database compute and storage are separate from other customers.

Configure capacity

Regional backups

Dedicated storage snapshots are encrypted and archived in the instance's region.

Snapshot details

Clear recovery behavior

Review write durability, archive status and operational limits before setting your recovery expectations.

Durability and recovery
Choose a deployment

Capacity and protection
are separate decisions.

Start with the workload, then choose the resources and recovery options it needs.

Storage choices by configuration
What you chooseFreeDedicated
ResourcesShared starting configurationDedicated compute and storage
CapacityCurrent free-plan quotaChoose capacity for the workload
RecoveryPoint-in-time recovery not includedDaily snapshots; review available recovery points
AvailabilityReview the plan's limitsOptional asynchronous standby

Scroll to compare both plans

A standby supports availability. Snapshots provide recovery history. Choose each for the failure you need to handle.

Configure a dedicated instance
A practical restore plan

Recover the data.
Verify the application.

A successful restore is more than a running instance. Check that the recovered records and your application's connections match the state you expect.

Read the recovery runbook
  1. 01

    Choose an available point

    Inspect the snapshot and archive state. Select a recoverable point before the unwanted change.

  2. 02

    Restore a fresh instance

    Recovery uses the chosen snapshot and available archived changes. Keep the source available for comparison.

  3. 03

    Validate before switching

    Check application-critical records, query results and permissions. Then update the application to use the recovered instance.

Plan against the recoverable point.

Archive streaming is still a preview. Current recovery planning should use daily snapshots, rather than a promised per-second recovery window.

Check archive limitations

Put it to work.

Start with the right capacity

Free offers a shared starting configuration. Dedicated opens resource and recovery choices; free configurations do not include point-in-time recovery.

Compare deployment choices

Plan backups and availability

A standby and a backup serve different purposes. Standby replication is asynchronous; recent acknowledged writes may be lost if the writer fails.

Understand standby recovery

Build with OriginChainDB.

Start free Review deployment options