v0.5.1 – Offer to enable SFTP upload for all profiles

New

• After a successful Save and test connection, the Settings tab asks whether to enable Upload to SFTP for all profiles that do not upload yet. No leaves the choice to the profiles. The question only appears when an encryption key is set, because uploads require encryption.

v0.5.0 – Scheduled backups overview, settings in one form

New

• Scheduled backups on the Backups tab: every profile with a schedule, its next run (soonest first, overdue runs marked), SFTP upload and the result of its last run.
• Setup steps on the Settings tab, shown until encryption is set up and, with an SFTP user, the connection was tested once.

Changed

• The Settings tab is now one form with one Save settings button. Before, the general part and the SFTP part had their own buttons, and saving one discarded unsaved changes in the other.
• Test connection became Save and test connection. Create key pair and Reset host key save the page first, so entered values are no longer lost.
• If a value is invalid, nothing is saved and all errors are shown at once. Before, the valid SFTP fields were saved anyway.

v0.4.0 – Uploads into the base folder backups

SFTP uploads now go into a base folder backups, so a sync tool such as a NAS can take exactly this folder.

Changed

• Backups are uploaded to <own folder>/backups/<domain>/, on HiDrive /users/<name>/backups/<domain>/.
• A relative Base folder now starts in the own folder of the account instead of the login folder /. . means the own folder itself; a path starting with / is used as it is.

Upgrading

Sites that left the base folder empty uploaded to /users/<name>/<domain>/ until now. After the update, new backups go to /users/<name>/backups/<domain>/. Move the existing site folder into backups/ on the server (e.g. in the HiDrive web interface), otherwise the old backups there are no longer cleaned up. If a sync tool pulls from the account, point it at the backups folder.

v0.3.0 – Separate retention for the SFTP server, keep 3 on the site

Backups on the site and on the SFTP server now have separate retention rules, so the off-site copy can keep more than the site.

New

• Keep on SFTP server per profile (default: 7 backups) and Keep on SFTP server for days. The plugin cleans up the site and the SFTP server separately. Keep more on the server than on the site, so a copy that pulls from it (e.g. a NAS with Cloud Sync) has time to fetch every backup.

Changed

• Profiles keep 3 backups on the site by default instead of 7.

Upgrading

Profiles that still use the old default of 7 are set to 3 on the site when the plugin updates. The SFTP server keeps 7 as before. Profiles with another number stay as they are.

v0.2.0 – SSH key login for SFTP (works with HiDrive 2FA)

SFTP uploads now log in with an SSH key, and every site has its own key pair. This makes the off-site copy work with HiDrive two-factor authentication and lets you lock out a single site without touching the others.

New

• SSH key login for SFTP. Under Tools → Backups → Settings → Upload to SFTP, click Create key pair. The private key is created on the site and never leaves it. Download the public key (rmd-backup_<domain>.pub, comment rmd-backup <domain>) and add it to the SFTP account (HiDrive: Settings → Account → backup account → Open-SSH).
• One key per site. An account can hold many keys. To lock out a site, delete only its key in the account; all other sites keep working.
• Works with HiDrive two-factor authentication. Password logins would need the current code and fail in scheduled runs; key logins do not.
• Fingerprints (SHA256 and MD5) to compare with the key list of the account.
• RMD_BWP_SFTP_AUTH and RMD_BWP_SFTP_PRIVATE_KEY in wp-config.php.
• Site Health reports an SFTP key or password that can no longer be decrypted.

Upgrading

Sites that use the password login from 0.1.0 keep it after the update. To switch: create a key pair, add the public key to the account, set Login to SSH key and run Test connection. Only then enable two-factor authentication for the account.

v0.1.0 – Lightweight backups with encryption and SFTP off-site copies

First release of RMD Backup WordPress, a lightweight backup plugin: one zip per run with the files and the database, on a schedule, with automatic cleanup and a log for every run.

Features

• One zip per run with the files, the database dump (database.sql.gz) and backup-info.json. File names start with the date, followed by the site's domain.
• Profiles for what to back up: database, WordPress core, wp-config.php, plugins, themes, uploads and the rest of wp-content, with exclusion rules in .gitignore syntax. Five profiles are prepared on activation.
• Schedules per profile: hourly, daily, weekly or monthly.
• Retention by number and age; the newest backup is always kept.
• Log for every run, viewable and downloadable in the admin; old logs are cleaned up automatically.
• Email notification after warnings or errors, or after every run, with the log attached.
• Encryption with age: only the public key is stored on the site (RMD_BWP_AGE_RECIPIENT in wp-config.php). Decrypt with age -d -i key.txt -o backup.zip backup.zip.age. Requires the PHP extension sodium.
• Off-site copies via SFTP, e.g. to STRATO HiDrive: only encrypted backups, resumable uploads, pinned host key, retention on the server.
• Robust on shared hosting: runs in short steps that continue in the background, so PHP time limits do not matter.
• WP-CLI commands (wp rmd-backup run <profile>) and Site Health checks.

Installation

Download rmd-backup-wordpress.zip below (not the “Source code” archives), upload it under Plugins → Add New → Upload Plugin and open Tools → Backups. Later versions are offered as normal plugin updates.