MigraDrive Docs — Backups

rclone remote configuration

Don’t paste real keys into docs or commit them to disk. Store secrets in a password manager/secrets manager.

# provide credentials via environment variables
export RCLONE_S3_ACCESS_KEY_ID="REPLACE_ME"
export RCLONE_S3_SECRET_ACCESS_KEY="REPLACE_ME"

rclone config
# New remote: migradrive
# Type: s3
# Provider: Other
# region: us-east-1
# endpoint: https://s3.migradrive.com
# acl: private

# If you must store keys, prefer an encrypted rclone.conf kept secure.

One-way sync (recommended)

Mirrors your local folder to MigraDrive (deletes remote files that were deleted locally).

rclone sync /srv/backups migradrive:backups/srv1 --progress --transfers 8 --checkers 16

Use sync when you want remote to match local exactly.

Copy (no deletions)

Adds new/updated files without deleting anything on MigraDrive.

rclone copy /srv/backups migradrive:backups/srv1 --progress --transfers 8 --checkers 16

Use copy for append-only retention patterns.

Cron example (daily at 2:15 AM)

15 2 * * * /usr/bin/rclone sync /srv/backups migradrive:backups/srv1 --transfers 8 --checkers 16 --log-file /var/log/rclone_migradrive.log

For enterprise setups, systemd timers are preferred over cron for better logging and reliability.

Verification (do not skip)

Spot-check remote contents after the job runs.

rclone lsf migradrive:backups/srv1 --max-depth 2 | head
rclone size migradrive:backups/srv1