Dedicated resources
- Compute and storage are separate from other customers.
- Allow space for records, indexes and growth.
Storage & recovery
Keep your data.
Plan its recovery.
Choose your storage, review available backups and practice restoring your application.
Three separate decisions
Capacity, availability
and recovery.
Decide how much space you need, how the app stays available and how you restore data.
An optional warm standby
- Copies changes asynchronously and can lag behind.
- Keep backups as well as the standby.
Daily snapshots
- Daily snapshots are the dedicated recovery baseline.
- Check available copies and test a restore.
Understand your configuration
Compare your
backup options.
Recovery features depend on your plan and instance settings.
| Option | What to expect | What to check |
|---|---|---|
| Free configuration | Shared resources within the current plan quota. | Plan for development data; do not assume point-in-time recovery. |
| Dedicated snapshots | Daily snapshots stored for the dedicated instance in its region. | Which copies are available, how long they are kept and how to restore them. |
| Archive streaming | Opt-in preview for archived changes alongside snapshots. | Check archive coverage and supported recovery points. Daily snapshots remain the baseline. |
Restore time varies. Test it with your data and record how long it takes.
A restore you have rehearsed
Restore in
three steps.
Write down who starts the restore, checks the data and reconnects the app.
Read about durability- 01
Choose a backup
Choose an available snapshot or supported recovery point that covers the data you need.
- 02
Restore a separate copy
Restore into a fresh instance while the running application stays separate.
- 03
Check and reconnect
Check records, permissions and queries. Reconnect the app after they pass.
Build with OriginChainDB