Backup OpenClaw Configuration

Overview

This skill provides automated backup and restore functionality for all OpenClaw configuration files. It creates timestamped archives containing your complete OpenClaw setup, including main configuration, workspace, skills, and user data.

What gets backed up:

• - ~/.openclaw/ - Main configuration
• INLINECODE1 - System-level configuration
• INLINECODE2 - Local data
• INLINECODE3 - Workspace, skills, and memory

Quick Start

Backup Your Configuration

Run the backup script:

CODEBLOCK0

Example:
CODEBLOCK1

Output:

• - Creates openclaw_backup_YYYYMMDD_HHMMSS.tar.gz archive
• Creates openclaw_backup_YYYYMMDD_HHMMSS.info metadata file
• Shows backup summary with file list and archive size
• Automatically deletes backups older than 15 days to manage disk space

Restore from Backup

Run the restore script:

CODEBLOCK2

Example:
CODEBLOCK3

Process:

1. 1. Shows backup information from .info file
2. Lists all files that will be restored
3. Requires confirmation before proceeding
4. Backs up existing files with .bak extension
5. Restores configuration to original locations

After restore:
CODEBLOCK4

Workflow

Backup Workflow

1. 1. Check prerequisites

1. 2. Create backup structure

1. 3. Copy configuration files

1. 4. Create archive

1. 5. Report results

Restore Workflow

1. 1. Validate backup

1. 2. Safety confirmation

1. 3. Backup existing files

1. 4. Extract and restore

1. 5. Complete and notify

Use Cases

Before Upgrade

CODEBLOCK5

Transfer to New Machine

CODEBLOCK6

Disaster Recovery

CODEBLOCK7

Configuration Locations

For detailed information about what gets backed up, see config-locations.md.

Summary:

• - Main config: ~/.openclaw/ - Gateway config, extensions, tokens
• Workspace: ~/.openclaw/workspace/ - Skills, memory, user data
• System config: ~/.config/openclaw/ - systemd services, preferences
• Local data: ~/.local/share/openclaw/ - Cache, runtime data

Best Practices

Regular Backups

Create backups regularly, especially after:

• - Installing new skills
• Modifying configuration
• Adding extensions
• Important workspace changes

Secure Storage

• - Backup archives contain sensitive data (tokens, credentials)
• Store backups in secure location
• Consider encrypting with gpg for sensitive environments
• Don't share backup archives publicly

Testing Backups

After creating a backup, verify it:
CODEBLOCK8

Troubleshooting

Permission Denied

If you see permission errors:
CODEBLOCK9

Gateway Won't Start After Restore

If Gateway fails to start after restore:
CODEBLOCK10

Missing Directories

The backup script gracefully handles missing directories:

• - Skips directories that don't exist
• Shows warning for each missing directory
• Still creates valid backup with available data