Backup & Restore

Rediacc can back up encrypted repositories to external storage providers and restore them on the same or different machines. Backups are encrypted — the repository’s LUKS credential is required to restore.

Configure Storage

Before pushing backups, register a storage provider. Rediacc supports any rclone-compatible storage: S3, B2, Google Drive, and many more.

Import from rclone

If you already have an rclone remote configured:

rdc config storage import rclone.conf

This imports storage configurations from an rclone config file into the current config. Supported types: S3, B2, Google Drive, OneDrive, Mega, Dropbox, Box, Azure Blob, and Swift.

View Storages

rdc config storage list

Push a Backup

Push a repository backup to external storage:

rdc repo push my-app -m server-1 --to my-storage

Option	Description
--to <storage>	Target storage location
--to-machine <machine>	Target machine for machine-to-machine backup
--dest <filename>	Custom destination filename
--checkpoint	Create a CRIU checkpoint before pushing (for containers with rediacc.checkpoint=true label). Target auto-restores on repo up
--force	Override an existing backup
--tag <tag>	Tag the backup
-w, --watch	Watch the operation progress
--debug	Enable verbose output
--skip-router-restart	Skip restarting the route server after the operation

Pull / Restore a Backup

Pull a repository backup from external storage:

rdc repo pull my-app -m server-1 --from my-storage

Option	Description
--from <storage>	Source storage location
--from-machine <machine>	Source machine for machine-to-machine restore
--force	Override existing local backup
-w, --watch	Watch the operation progress
--debug	Enable verbose output
--skip-router-restart	Skip restarting the route server after the operation

List Backups

View available backups in a storage location:

rdc repo backup list --from my-storage -m server-1

Bulk Sync

Push or pull all repositories at once:

Push All to Storage

rdc repo push --to my-storage -m server-1

Pull All from Storage

rdc repo pull --from my-storage -m server-1

Option	Description
--to <storage>	Target storage (push direction)
--from <storage>	Source storage (pull direction)
--repo <name>	Sync specific repositories (repeatable)
--override	Override existing backups
--debug	Enable verbose output
--skip-router-restart	Skip restarting the route server after the operation

Scheduled Backups

Automate backups with a cron schedule that runs as a systemd timer on the remote machine.

Set Schedule

rdc config backup-strategy set --destination my-storage --cron "0 2 * * *" --enable

You can configure multiple destinations with different schedules:

rdc config backup-strategy set --destination my-s3 --cron "0 2 * * *" --enable
rdc config backup-strategy set --destination azure-backup --cron "0 6 * * *" --enable

Option	Description
--destination <storage>	Backup destination (can be set per-destination)
--cron <expression>	Cron expression (e.g., "0 2 * * *" for daily at 2 AM)
--enable	Enable the schedule
--disable	Disable the schedule

Push Schedule to Machine

Deploy the schedule configuration to a machine as a systemd timer:

rdc machine deploy-backup server-1

View Schedule

rdc config backup-strategy show

Browse Storage

Browse the contents of a storage location:

rdc storage browse my-storage

Best Practices

• Schedule daily backups to at least one storage provider
• Test restores periodically to verify backup integrity
• Use multiple storage providers for critical data (e.g., S3 + B2)
• Keep credentials secure — backups are encrypted but the LUKS credential is required to restore