Off-site Backup changelog
All notable changes to Off-site Backup (kv_offsite_backup) are documented here.
The format follows Keep a Changelog and the project uses Semantic Versioning.
[Unreleased]
Section titled “[Unreleased]”[1.0.0] - 2026-11-04
Section titled “[1.0.0] - 2026-11-04”- Scheduled database backups (every 6 or 12 hours, daily, weekly) and files backups (daily, weekly, monthly) at a chosen hour, made with the core Backup/Restore engine (ZIP or TGZ); first backup at the next cron call, failed runs retried after one hour, missed days caught up.
- Destinations: S3-compatible storage (AWS S3, Backblaze B2, Wasabi, Cloudflare R2, DigitalOcean Spaces, MinIO) with AWS Signature Version 4, multipart upload, Content-MD5 and retries; FTP and FTPS (explicit TLS).
- Archive integrity check before the upload; size and MD5/ETag verification after it.
- Optional AES-256-CBC encryption in the OpenSSL file format (PBKDF2-HMAC-SHA256, 100,000 rounds), decryptable with the openssl command.
- Retention per type at the destination (only archives the add-on uploaded) and optional local copies.
- Exclusions and extra paths for the files backup (thumbnails excluded by default).
- Dashboard: last backups, next runs, archives with signed-link download, local download and delete, run log with every step and hashes, connection test, cron command and URL.
- Admin alerts for failed runs, overdue backups and a stopped cron.
- Console cron and key-protected cron URL; one run at a time.