Backup & Restore
Keeps the backups Core makes: on this site, in your own S3-compatible bucket, or both, with a checksum you can re-check, a download for restoring, and an email when backups stop.
Not open yet No card
Description
Keeps the backups Core makes: on this site, in your own S3-compatible bucket, or both, with a checksum you can re-check, a download for restoring, and an email when backups stop.
What it does
- Backups of the database: every backup Core makes (its full export: content, settings, users and every module's data) is kept, squeezed, on this site
- Scheduled backups, daily or weekly: Core makes each one by itself when it is due, and this module keeps it
- Cloud destinations: your own S3-compatible bucket (Cloudflare R2, Backblaze B2, AWS S3), as well as or instead of this site
- Backup logs: when each was made, how big, how many tables and rows, where it went, and why one failed
- A SHA-256 checksum for every backup, and a button that re-reads the stored copy and checks it
- Download any backup as one file, and a look inside any export file that says what it holds and whether Core's Import will take it, without changing anything
- Keeps the newest backups you choose and clears out older ones
- An email to administrators, at most once a day, when a backup fails or scheduled backups stop arriving, and the age of the last good backup on the dashboard
- Files (media): a backup lists the media library but does not hold the files, because a module cannot read the media store. Needed: a way for a module to read a media file's bytes, or for Core's export to offer them. Not built yet.
- One-click restore: restoring replaces the site's data and is Core's Import screen, with one checked and recorded path. A module cannot call Core's import. Needed: `api.restore(bundle, mode)` that runs Core's own import for a signed-in administrator. Not built yet.
- Incremental backups: every backup is the whole export. Not built yet.
- Pre-update backup: Core announces `core.backup.before` and `core.backup.after` around a backup, but nothing announces that an update is about to be applied, so there is no moment to back up before one. Not built yet.
- Google Drive, Dropbox and OneDrive: each needs sign-in with that service, which cannot be tested here. Not built yet.
- Files other modules keep privately (uploaded CVs, downloads for sale) and saved secrets: Core keeps these out of every export on purpose. Not built yet.
- Staging copies. Not built yet.
Stands in for
UpdraftPlus.
These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.
What comes across
What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.
- From UpdraftPlus
- Comes across: How many backups were kept, the S3-compatible or Amazon S3 bucket and folder, and whether reports were emailed. The report says which schedule to choose (daily or weekly) under Settings → API and backups, which is Core's setting.
- Does not: The backups already made (WordPress files and database dumps: bring content over with Core's WordPress importer), access keys and tokens (typed in again on the Backups screen), file backups, and Dropbox, Google Drive, FTP and other non-S3 destinations.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From BackWPup
- Comes across: From the first job that backs up the database: how many backups were kept, the S3 bucket, folder and region, and whether a log was emailed. The report says which schedule to choose (daily or weekly) under Settings → API and backups, which is Core's setting.
- Does not: Other jobs (one schedule is kept here), the backups already made, access keys (typed in again on the Backups screen), file backups, and Dropbox, FTP and other non-S3 destinations.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
No importer yet for: BackupBuddy, BlogVault.
Using a plugin that is not named here? It is built for your site On The Fly. How that works
Changelog
1.0.0 November 18, 2026
Backup & Restore: keeps the backups Core makes, on this site and in your own S3-compatible bucket, with a checksum for each, a check that re-reads a stored copy, keep-the-newest, and an email when backups fail or stop. A backup holds the site's data, not media files; restore is through Core's Import screen.
1.1.0 November 17, 2026
Backup & Restore 1.1.0: imports UpdraftPlus and BackWPup settings: how many backups are kept, the S3-compatible or Amazon bucket, folder and region, and the failure email. The report says which schedule to pick under Settings, API and backups. Access keys are never read from the file, and the old archives stay behind (bring content over with the WordPress importer).
Get Backup & Restore when WebHD opens
One form on the home page: your WordPress address, then your email.
No card Takes a minute No fake scan