Cron Backup

Automated backup scheduling with version detection and intelligent cleanup.

Quick Start

One-Time Backup

Schedule Daily Backup

Version-Aware Backup

Cleanup Old Backups

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
• INLINECODE2 - Version-triggered backup
• INLINECODE3 - Cron job setup
• INLINECODE4 - Old backup cleanup
• INLINECODE5 - List available backups

Backup Naming Convention

Backups follow the pattern: INLINECODE6

Examples:

• - INLINECODE7
• INLINECODE8

Workflow

Setting Up Automated Backups

1. 1. Decide backup strategy

1. 2. Run initial backup

1. 3. Set up schedule

1. 4. Configure cleanup

Version-Aware Backup Workflow

For software that changes version (like OpenClaw):

1. 1. Identify version source

1. 2. Set up versioned backup

1. 3. Schedule version check

Common Patterns

Pattern 1: Daily User Data Backup

Pattern 2: Version-Aware Application Backup

Pattern 3: Multi-Directory Backup

Cron Schedule Format

Standard cron format: INLINECODE11

Common schedules:

• - Daily at 2 AM: INLINECODE12
• Every 6 hours: INLINECODE13
• Weekly on Sunday: INLINECODE14
• Every 30 minutes: INLINECODE15

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