Usage

Open Administration > Off-site backup.

Dashboard

• Back up database now / Back up files now: runs a backup at once and shows the result. Keep the tab open; a files backup of a big store can take several minutes.
• Test connection: writes a small test file to the destination, reads it back and deletes it.
• Cards: last database and files backup, archives stored at the destination with their total size, successful and failed runs in the last 30 days.
• Overview: schedule, next run, retention and content of each type; destination with the last connection test; encryption status with the decrypt command; cron command and URL with the last cron call.

Archives

Every archive the add-on uploaded and has not deleted, with its date, size and checks:

• Size + checksum: remote size and MD5 checksum match the archive on your server.
• Size verified: the size matches; the storage does not report an MD5 (some encrypted buckets). The upload itself carried a Content-MD5 header that the storage checks.
• Encrypted: AES-256, decrypt with the command on the Overview tab.
• Local copy: still in var/backups on this server.

Download opens a short-lived signed link (5 minutes) on S3-compatible storage, or streams the archive through the admin panel on FTP. Delete removes the archive from the destination.

Run log

One line per run with status, type, trigger (cron, cron URL, manual), size and duration. Open a line to see every step: archive, check, encryption, upload, verification, retention, and the MD5 and SHA-256 of the archive.

Alerts

When the last backup of a type failed, when no backup succeeded for more than twice the schedule interval, or when the cron has not run for two days, administrators see a warning once on the next admin page and a red box on the dashboard. Mark as seen hides a failure alert.

Restoring

Restoring is a manual step, so you decide what and where to restore.

Database:

1. Download the database archive (and decrypt it if it ends in .enc).
2. Unpack it: it contains one .sql file.
3. Import it into an empty database, for example with phpMyAdmin or mysql -u USER -p DATABASE < file.sql.
4. Point config.local.php to that database if it is a new one.

Files:

1. Download the files archive (decrypt it if needed).
2. Unpack it into the store root, or into an empty folder to copy single files back.
3. Clear the cache folder var/cache.

Test a restore on a copy of your store from time to time: a backup you never restored is a hope, not a plan.