docs(8.0): consistency-model concept + snapshots guide — Db API replaces branching docs
This commit is contained in:
parent
e5feae4104
commit
cc8037db10
23 changed files with 1053 additions and 1871 deletions
|
|
@ -134,8 +134,8 @@ console.log(health.overall)
|
|||
await reader.close()
|
||||
```
|
||||
|
||||
Every mutation method (`add`, `update`, `delete`, `relate`, `commit`,
|
||||
`fork`, `branch`, ...) throws on a read-only instance with a clear message.
|
||||
Every mutation method (`add`, `update`, `delete`, `relate`, `transact`,
|
||||
`restore`, ...) throws on a read-only instance with a clear message.
|
||||
|
||||
## Backups
|
||||
|
||||
|
|
@ -148,9 +148,10 @@ brainy inspect backup /data/brain /backups/brain-2026-05-15.tar
|
|||
```
|
||||
|
||||
For periodic backups (hourly, daily), schedule this via cron or your
|
||||
container scheduler. For point-in-time recovery, use Brainy's COW
|
||||
`commit()` API — the snapshots there are content-addressed and never
|
||||
overwritten.
|
||||
container scheduler. For point-in-time recovery, use the Db API's
|
||||
`db.persist(path)` — a self-contained hard-link snapshot that later writes
|
||||
can never alter, restorable with `brain.restore(path, { confirm: true })`.
|
||||
See [Snapshots & Time Travel](./snapshots-and-time-travel.md).
|
||||
|
||||
## Comparing two stores
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue