[Feature]: Multiple Backup Jobs / Destinations

[kayvanaarssen]

Problem or use case

.

Proposed solution

Make it possible to have multiple backup jobs / schedules / destinations
We need this for specific servers to backup to multiple destinations.

Also multiple jobs with multiple timing options is needed

Alternatives considered

No response

Component

Other

How important is this to you?

Blocking my use case

Additional context

No response

Checklist

• I searched existing issues and this is not a duplicate
• I would be willing to help test this feature

[wnstfy]

Phase 1 Complete - v3.1.0 Released

Multi-job support has been implemented and released in v3.1.0.

What's Available Now

Job Management Commands:

backupd job list                      # List all jobs
backupd job show <name>               # Show job config and status
backupd job create <name>             # Create new job (empty config)
backupd job delete <name>             # Delete job and timers
backupd job clone <src> <dst>         # Clone job configuration (recommended)
backupd job run <name> [db|files|all] # Run backup for job
backupd job enable <name>             # Enable job
backupd job disable <name>            # Disable job
backupd job timers <name>             # Show systemd timers
backupd job regenerate <name>         # Regenerate scripts

Key Features:

• Each job has isolated configuration and scripts
• Jobs stored in /etc/backupd/jobs/{jobname}/
• Automatic migration: existing config becomes "default" job
• Full backward compatibility with existing commands
• Job-aware history tracking

Creating New Jobs

Recommended approach - clone from existing job:

sudo backupd job clone default staging
# Then edit /etc/backupd/jobs/staging/job.conf to change:
# - RCLONE_DB_PATH, RCLONE_FILES_PATH (different destination)
# - WEB_PATH_PATTERN (different source if needed)
sudo backupd job regenerate staging

Alternative - create empty job:

sudo backupd job create staging
# Manually edit /etc/backupd/jobs/staging/job.conf
# Set: DO_DATABASE, DO_FILES, RCLONE_REMOTE, RCLONE_*_PATH
sudo backupd job regenerate staging

Remaining Phases

Phase 2 (v3.2.0) - Per-Job Scheduling:

• Different schedules per job (e.g., production hourly, staging daily)
• Per-type enable/disable (disable just db or files timer)
• backupd job configure <name> wizard for easier setup

Phase 3 (v3.3.0) - Multi-Destination:

• Multiple destinations per job (primary + replicas)
• Automatic replication using restic copy
• Cross-destination health monitoring

Feedback welcome!

[wnstfy]

Progress Update - v3.2.0 Released

Completed Features

v3.1.0 - Multi-Job Support

• Multiple independent backup jobs with separate configurations
• Each job can target different remote destinations
• CLI: backupd job {list|show|create|delete|clone|run|enable|disable}
• Jobs stored in /etc/backupd/jobs/{jobname}/

v3.2.0 - Per-Job Scheduling via CLI

• Independent schedules per job and backup type
• backupd job schedule <job> <type> <schedule> command
• Support for db, files, verify, verify-full types
• --show, --disable, --json, --all flags
• Schedule validation with OnCalendar format checking
• Conflict detection warns about overlapping schedules
• Interactive schedule menu for non-CLI users
• Fixed: enable_job() now recreates timers from stored config

Example Usage

# Create jobs for different destinations
backupd job create production
backupd job create staging

# Set different schedules per job
backupd job schedule production db "*-*-* */2:00:00"    # Every 2 hours
backupd job schedule staging db "*-*-* 03:00:00"       # Daily at 3 AM

# View all schedules
backupd job schedule --all

Release Info

• Version: v3.2.0
• Commit: 93dba5c
• Release: https://github.com/wnstify/backupd/releases/tag/v3.2.0
• Commits: BACKUPD-008 through BACKUPD-026 (18 commits)

Potential v3.2.1 Enhancements

• Schedule conflict resolution (auto-suggest alternative times)
• Bulk schedule operations across jobs
• Schedule templates/presets

Keeping open for feedback and potential enhancements.