Age encryption, gzip/zstd compression, parallel dumps via mydumper, automatic rotation and restore of files and databases.
Encryption, compression, parallel dumps, rotation, verification and restore
The modern Age encryption standard. Individual keys for every server, private keys encrypted with AES-256-CBC. Download a recovery key for emergency restore.
Choose between gzip (default) and Zstandard — a modern algorithm with a better compression ratio. Configurable compression level.
Standard mysqldump or multi-threaded mydumper for parallel dumps. Configure the number of threads to speed things up.
Archive — a compressed archive, then upload. Rsync — a mirror copy for site files. Two modes for different needs.
retention_count — keep the last N copies. retention_days — keep for X days. Automatic cleanup of stale backups.
Restore of site files and databases on the original server. Databases — into another database on that server. Pre-restore copy and auto-rollback — for site files.
Upload backups to remote servers over SFTP. Inline credentials or a shared provider for multiple profiles.
Every run is saved: status, file name, size, source size, checksum, time, errors.
The verify_after_upload flag: the checksum is verified after the upload to remote storage completes.
The notify_on_failure flag: alerts via Email or Telegram if a backup fails.
A full backup of the project directory: source code, uploads, configs. A separate profile for each site on the server.
A separate profile for each database. Support for mysqldump, mydumper, compressed and encrypted formats.
Each profile — a separate configuration: compression type, dump engine, transfer mode, retention policy, encryption. Full run history with metadata.
Restore of site files and databases on the original server. A database can be restored into another database on that server. For site files a pre-restore copy is created, and on error — an automatic rollback of the files.
Each server gets its own Age key pair. The private key is stored encrypted (AES-256-CBC) in the server_backup_keys table. The public key encrypts backups on the fly.
Two retention modes, automatic cleanup of stale backups
Number of copies
Keep the last N backups. When a new one is created — the oldest is deleted automatically. Great for a fixed number of restore points.
Number of days
Keep backups no older than X days. Anything older — is deleted automatically. Great for compliance and retention over a fixed period.
Every run stores complete information: file, size, checksum, errors
Encryption, rotation, verification and restore — all out of the box. Set it up once and forget it.
We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.