You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Existing archive files are never overwritten. Output paths inside the source state/workspace trees are rejected to avoid self-inclusion.
28
34
-`openclaw backup verify <archive>` checks that the archive contains exactly one root manifest, rejects traversal-style archive paths, and confirms every manifest-declared payload exists in the tarball. `openclaw backup create --verify` runs that validation immediately after writing the archive.
29
35
-`openclaw backup create --only-config` backs up just the active JSON config file.
30
-
- If you only need a SQLite-safe sync artifact for one OpenClaw database, use [`openclaw snapshot`](/cli/snapshot). Backup is for broad recovery archives.
36
+
- If you only need a SQLite-safe sync artifact for one OpenClaw database, use `openclaw backup sqlite snapshot`. `backup create` is for broad recovery archives.
37
+
38
+
## SQLite snapshot artifacts
39
+
40
+
Use `openclaw backup sqlite snapshot` when you need a syncable artifact for one
41
+
SQLite database. A snapshot repository stores verified snapshot directories
42
+
containing `manifest.json` and `database.sqlite`, so a host, container, object
43
+
storage sync, or backup system can copy those files instead of copying a hot
44
+
SQLite database.
45
+
46
+
Use `openclaw backup create` when you need a broader local recovery archive for
47
+
OpenClaw state, config, auth profiles, credentials, sessions, and optional
48
+
workspaces. Backup archives may contain SQLite-safe database copies, but their
49
+
output and restore model are archive-level, not a per-database snapshot
50
+
repository.
51
+
52
+
### What to sync
53
+
54
+
Sync the snapshot directory created under the repository. A snapshot directory
55
+
contains:
56
+
57
+
-`manifest.json`
58
+
-`database.sqlite`
59
+
60
+
Do not sync live SQLite runtime files as the portability artifact:
61
+
62
+
-`openclaw.sqlite`
63
+
-`openclaw.sqlite-wal`
64
+
-`openclaw.sqlite-shm`
65
+
-`openclaw-agent.sqlite`
66
+
-`openclaw-agent.sqlite-wal`
67
+
-`openclaw-agent.sqlite-shm`
68
+
69
+
Those files are hot runtime state. `openclaw backup sqlite snapshot create`
70
+
reads the live database and writes a compact, verified SQLite artifact that can
71
+
be copied by a host, container, object storage sync, or backup system.
72
+
73
+
SQLite snapshot artifacts are still sensitive state. Global and per-agent
74
+
artifacts can include auth profile records, session state, plugin state, and
75
+
other credentials-adjacent data from the source SQLite database. Protect
76
+
snapshot repositories with the same access controls, encryption, retention
77
+
policy, and upload destination restrictions you use for OpenClaw backups and
78
+
live state.
79
+
80
+
### Named SQLite targets
81
+
82
+
Use named targets when snapshotting OpenClaw-owned SQLite state:
0 commit comments