Cron 备份：自动定时备份与版本控制 - Openclaw Skills

什么是 Cron 备份？

Cron 备份技能是一个旨在简化数据冗余和保护的综合实用工具。通过直接与系统 cron 集成，该 Openclaw Skills 解决方案使开发人员能够自动创建带有时间戳的 tar.gz 存档，同时保留关键的文件权限和目录结构。它是配置文件、源代码和应用程序数据的可靠保障。

除了简单的调度，该技能还为备份生命周期引入了智能化。它可以监控版本文件或命令输出，仅在发生更新时触发备份，从而防止冗余存档。通过内置的清理脚本，它根据用户定义的保留期限自动修剪旧备份，确保高效管理存储空间。

下载入口:https://github.com/openclaw/skills/tree/main/skills/zfanmy/cron-backup

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

npx clawhub@latest install cron-backup

2. 手动安装

将技能文件夹复制到以下位置之一

全局模式 ~/.openclaw/skills/ 工作区 /skills/

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

请帮我使用 Clawhub 安装 cron-backup。如果尚未安装 Clawhub，请先安装（npm i -g clawhub）。

Cron 备份 应用场景

• 定期备份关键系统目录和用户工作区。
• 当检测到软件版本更新时，触发特定的自动备份。
• 维护滚动存档窗口，在确保数据恢复的同时优化磁盘空间。
• 为开发和生产环境管理复杂的多目录备份策略。

Cron 备份 工作原理

1. 用户选择需要保护的源目录和用于存放存档的目标目录。
2. 使用提供的设置脚本配置 cron 任务，使用标准 cron 语法定义频率。
3. 执行时，该技能会根据包含时间戳的标准命名约定创建一个压缩的 tar.gz 文件。
4. 如果启用了版本跟踪，脚本会在启动存档前对比当前版本元数据与之前的状态。
5. 清理工具按独立计划运行，删除超过定义时长或数量限制的存档。

Cron 备份 配置指南

首先，确保所有实用脚本都是可执行的：

chmod +x scripts/*.sh

执行初始手动备份：

./scripts/backup.sh /path/to/source /path/to/backup/dir

安排每日凌晨 2 点的自动备份：

./scripts/setup-cron.sh daily /path/to/source /path/to/backup/dir "0 2 * * *"

配置自动清理 7 天前的备份：

./scripts/setup-cron.sh cleanup /path/to/backup/dir "" "0 3 * * *" 7

Cron 备份 数据架构与分类体系

数据组件	格式 / 模式	描述
存档名称	{name}_YYYYMMDD_HHMMSS.tar.gz	带时间戳的存档文件，用于唯一标识
压缩	tar.gz	保留文件属性的标准 Linux 压缩格式
排除项	node_modules, .git, temp	减少存档大小和噪音的默认过滤器
保留策略	基于时间或数量	清理脚本用于管理磁盘占用的逻辑

name: cron-backup
description: Set up scheduled automated backups with version tracking and cleanup. Use when users need to (1) Schedule periodic backups of directories or files, (2) Monitor version changes and backup on updates, (3) Automatically clean up old backups to save space, (4) Create backup strategies for configuration files, code repositories, or user data.

Cron Backup

Automated backup scheduling with version detection and intelligent cleanup.

Quick Start

One-Time Backup

# Backup a directory with timestamp
./scripts/backup.sh /path/to/source /path/to/backup/dir

# Backup with custom name
./scripts/backup.sh /path/to/source /path/to/backup/dir my-backup

Schedule Daily Backup

# Set up daily backup at 2 AM
./scripts/setup-cron.sh daily /path/to/source /path/to/backup/dir "0 2 * * *"

Version-Aware Backup

# Backup only when version changes
./scripts/backup-versioned.sh /path/to/source /path/to/version/file /path/to/backup/dir

Cleanup Old Backups

# Keep only last 7 days of backups
./scripts/cleanup.sh /path/to/backup/dir 7

Core Capabilities

1. Directory Backup

• Creates timestamped tar.gz archives
• Preserves file permissions and structure
• Excludes common temp files (node_modules, .git, etc.)

2. Version-Triggered Backup

• Monitors version file or command output
• Backs up only when version changes
• Useful for software updates

3. Scheduled Execution

• Integrates with system cron
• Supports custom schedules
• Logs execution results

4. Automatic Cleanup

• Deletes backups older than N days
• Keeps minimum number of backups
• Prevents disk space exhaustion

Scripts

All scripts are in scripts/ directory:

• backup.sh - Single backup execution
• backup-versioned.sh - Version-triggered backup
• setup-cron.sh - Cron job setup
• cleanup.sh - Old backup cleanup
• list-backups.sh - List available backups

Backup Naming Convention

Backups follow the pattern: {name}_YYYYMMDD_HHMMSS.tar.gz

Examples:

• openclabak_20260204_101500.tar.gz
• myapp_20260204_000000.tar.gz

Workflow

Setting Up Automated Backups

1. Decide backup strategy

   • What to backup (source directory)
   • Where to store (backup directory)
   • How often (schedule)
   • Retention policy (cleanup days)

2. Run initial backup

   ./scripts/backup.sh /source /backup
   

3. Set up schedule

   ./scripts/setup-cron.sh daily /source /backup "0 2 * * *"
   

4. Configure cleanup

   ./scripts/setup-cron.sh cleanup /backup "" "0 3 * * *" 7
   

Version-Aware Backup Workflow

For software that changes version (like OpenClaw):

1. Identify version source

   • Command: openclaw --version
   • File: /path/to/version.txt

2. Set up versioned backup

   ./scripts/backup-versioned.sh /app /app/version.txt /backups/app
   

3. Schedule version check

   ./scripts/setup-cron.sh versioned /app /backups/app "0 */6 * * *"
   

Common Patterns

Pattern 1: Daily User Data Backup

# Backup workspace daily, keep 30 days
./scripts/setup-cron.sh daily /home/user/workspace /backups/workspace "0 2 * * *"
./scripts/setup-cron.sh cleanup /backups/workspace "" "0 3 * * *" 30

Pattern 2: Version-Aware Application Backup

# Backup when application updates
./scripts/setup-cron.sh versioned /opt/myapp /backups/myapp "0 */6 * * *"
./scripts/setup-cron.sh cleanup /backups/myapp "" "0 4 * * 0" 10

Pattern 3: Multi-Directory Backup

# Backup multiple directories
./scripts/backup.sh /home/user/.config /backups/config
./scripts/backup.sh /home/user/projects /backups/projects

Cron Schedule Format

Standard cron format: minute hour day month weekday

Common schedules:

• Daily at 2 AM: 0 2 * * *
• Every 6 hours: 0 */6 * * *
• Weekly on Sunday: 0 0 * * 0
• Every 30 minutes: */30 * * * *

Cleanup Policies

• Time-based: Keep backups for N days
• Count-based: Keep last N backups
• Combined: Default keeps 7 days minimum, but at least 3 backups

Troubleshooting

• Permission denied: Ensure scripts are executable (chmod +x scripts/*.sh)
• Cron not running: Check cron service status (systemctl status cron)
• Disk full: Run cleanup manually or reduce retention period
• Backup fails: Check source directory exists and is readable