Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Backup and restore OpenClaw workspace, configs, and agent data to a Synology NAS via SMB. Use when: backing up workspace files, restoring from a snapshot, ch...
Backup and restore OpenClaw workspace, configs, and agent data to a Synology NAS via SMB. Use when: backing up workspace files, restoring from a snapshot, ch...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Backup OpenClaw data to a Synology NAS over SMB. Designed for secure, automated daily snapshots with configurable retention.
For VPS-to-NAS backups, use Tailscale for secure connectivity without exposing SMB to the internet: Install Tailscale on the Synology (Package Center โ search "Tailscale") Install Tailscale on the VPS โ see Tailscale's official install guide for your platform Join both to the same tailnet Use the Synology's Tailscale IP in config For local network setups, use the NAS local IP directly.
Create a dedicated user on the Synology (e.g., openclaw-backup) with minimal permissions Create or choose a shared folder (e.g., backups) Grant the user read/write access to only that folder
Create an SMB credentials file with restricted permissions โ never store credentials in config or scripts: # Create the file and set permissions (replace placeholders with your values) touch ~/.openclaw/.smb-credentials chmod 600 ~/.openclaw/.smb-credentials # Edit the file and add two lines: # username=<your-synology-user> # password=<your-synology-password> nano ~/.openclaw/.smb-credentials
Create ~/.openclaw/synology-backup.json: { "host": "100.x.x.x", "share": "backups/openclaw", "mountPoint": "/mnt/synology", "credentialsFile": "~/.openclaw/.smb-credentials", "smbVersion": "3.0", "backupPaths": [ "~/.openclaw/workspace", "~/.openclaw/openclaw.json", "~/.openclaw/cron", "~/.openclaw/agents" ], "includeSubAgentWorkspaces": true, "retention": 7, "schedule": "0 3 * * *" } Note on sensitive files: The .env file (containing API keys) is not included in the default backup paths. If you want to back it up, add "~/.openclaw/.env" to backupPaths โ but ensure your Synology share has restricted access and the dedicated user has minimal permissions. FieldDescriptionDefaulthostSynology IP (Tailscale or local)requiredshareSMB share pathrequiredmountPointLocal mount point/mnt/synologycredentialsFilePath to SMB credentials filerequiredsmbVersionSMB protocol version3.0backupPathsPaths to backupworkspace + configincludeSubAgentWorkspacesAuto-include workspace-* dirstrueretentionDays of snapshots to keep7scheduleCron expression (host timezone)0 3 * * *
apt-get install -y cifs-utils rsync
For persistent mounts across reboots, add to /etc/fstab: //<host>/<share> /mnt/synology cifs credentials=<credentials-file>,vers=3.0,_netdev,nofail 0 0
scripts/backup.sh Runs an incremental backup. First run copies everything; subsequent runs only sync changes.
scripts/restore.sh [date] Restores from a specific date's snapshot (e.g., 2026-02-20). Without a date, lists available snapshots.
scripts/status.sh Shows last backup time, snapshot count, total size, and mount health.
~/.openclaw/workspace/ โ memory, SOUL, AGENTS, skills, all workspace files ~/.openclaw/workspace-*/ โ all sub-agent workspaces (if enabled) ~/.openclaw/openclaw.json โ main config ~/.openclaw/cron/ โ cron job definitions ~/.openclaw/agents/ โ agent configurations ~/.openclaw/.env โ opt-in only (contains API keys โ add to backupPaths manually if desired)
backups/ โโโ 2026-02-20/ โ โโโ manifest.json โ โโโ workspace/ โ โโโ workspace-email/ โ โโโ workspace-news/ โ โโโ agents/ โ โโโ cron/ โ โโโ openclaw.json โโโ 2026-02-19/ โโโ ...
Credentials: Always use a dedicated credentials file with restricted permissions (chmod 600). Never inline secrets in config files, scripts, or fstab. Network: Use Tailscale or a VPN for remote backups. Never expose SMB (port 445) to the public internet. Sensitive data: The .env file contains API keys and is excluded from default backup paths. Only include it if your NAS share is properly secured with restricted user permissions. NAS user: Create a dedicated Synology user with access to only the backup share โ not an admin account. Retention: Old snapshots are pruned by moving them to the Synology trash (if supported) or deleting them. Increase retention for critical environments.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.