Skip to content
BotClawAgent ObserverTracking personal agents: progress and limits
2026.10.02
SOURCE · CONDITIONS · EVIDENCE

Verify a backup by restoring into a separate directory

Inventory and verify an OpenClaw archive, then restore into a test target. Keep credentials private; an archive existing on disk is not a recovery test.

Official documentation checkedRevision 2
Published
Oct 1, 2026
Reviewed
Oct 1, 2026
Content updated
Oct 1, 2026
Applicable version
Not pinned; check current documentation
Platforms
OpenClaw CLI host with separate test storage

Before you start

  • Enough space for an archive and an isolated restore target
  • Private storage: archives may contain authentication material

Choose what you need to recover: configuration, workspace, memory and session state. Define that inventory before creating the archive, so missing data is detectable. The procedure below is a review checklist based on the current backup CLI, not a recorded restore.

Inspect and create

  1. Run the dry-run inventory and compare included paths with your recovery list. Keep the report private if it exposes account paths.
  2. Create the backup with verification enabled. Store the archive in a separate protected location and record its checksum privately.
  3. Verify the archive and restore into a new empty test directory. Do not target the active configuration or overwrite a working gateway.
openclaw backup create --dry-run --json
openclaw backup create --verify
openclaw backup verify <archive>
openclaw backup restore <archive> --target ./restored-openclaw

Recovery acceptance

Compare the restored inventory with your list: expected files, nonempty memory and the intended session records. Inspect configuration without connecting the restored instance to live messaging. Declare runtime recovery only after a separately authorized, isolated startup and a harmless baseline task.

Common failures

A config-only backup may omit the data needed for your recovery goal. A checksum verifies archive identity, not application usability. If verification fails, preserve the archive, record the error and create a fresh backup; do not destroy the sole remaining copy.

Evidence and limits

Official documentation checked

  • Original BotClaw acceptance procedure based on linked official documentation. Product commands were not executed; check your installed version.

Sources

Cite or read with tools

https://botclaw.tech/items/wf-backup-restore

MarkdownJSONMCP