Cloud Storage (rclone)

This page is about the most common rclone configurations used with ProxSave cloud storage.

For how ProxSave builds remote paths, see docs/docs_file/rclone_cloud_path.md.

Quick checklist

Your rclone remote must be configured on the host: rclone config
Use the remote name (not the provider name) in CLOUD_REMOTE
Prefer CLOUD_UPLOAD_MODE=parallel for large backups with many associated files

Example 1 — Google Drive (safe defaults)

# configs/backup.env
CLOUD_ENABLED=true
CLOUD_REMOTE=gdrive
CLOUD_REMOTE_PATH=/proxsave/backup
CLOUD_LOG_PATH=/proxsave/log

CLOUD_UPLOAD_MODE=parallel
CLOUD_PARALLEL_MAX_JOBS=2
CLOUD_PARALLEL_VERIFICATION=true

RCLONE_TIMEOUT_CONNECTION=60
RCLONE_TIMEOUT_OPERATION=600
RCLONE_TRANSFERS=8
RCLONE_RETRIES=3

Example 2 — Backblaze B2 (bandwidth-limited)

# configs/backup.env
CLOUD_ENABLED=true
CLOUD_REMOTE=b2
CLOUD_REMOTE_PATH=/proxsave/backup
CLOUD_LOG_PATH=/proxsave/log

RCLONE_BANDWIDTH_LIMIT="10M"
RCLONE_TRANSFERS=4
RCLONE_RETRIES=5
RCLONE_TIMEOUT_OPERATION=900

Example 3 — S3 / MinIO (high-throughput LAN)

# configs/backup.env
CLOUD_ENABLED=true
CLOUD_REMOTE=minio
CLOUD_REMOTE_PATH=/proxsave/backup
CLOUD_LOG_PATH=/proxsave/log

CLOUD_UPLOAD_MODE=parallel
CLOUD_PARALLEL_MAX_JOBS=4

RCLONE_TRANSFERS=16
RCLONE_TIMEOUT_OPERATION=900
RCLONE_VERIFY_METHOD=primary

Tip: for S3-compatible endpoints, you’ll usually tune rclone itself in rclone config (region, endpoint, chunk sizes). Keep ProxSave settings focused on timeouts, concurrency, and retries.

Example 4 — Keep cloud traffic “quiet”

Use when API throttling is common (Drive/B2):

RCLONE_TRANSFERS=4
RCLONE_RETRIES=5
RCLONE_FLAGS="--checkers=2 --stats=0"

Example 5 — Debug a cloud upload

1) Run a dry-run with full logs:

proxsave --dry-run --log-level debug

2) Then run a real backup with debug logs:

proxsave --log-level debug

Cloud operations are logged under ${BASE_DIR}/log/ for the run. If a restore/decrypt flow is involved, additional logs may appear under /tmp/proxsave/.