Backups
What a backup is, the four scopes, where it goes, and how the list is kept tidy.
Making one
Open a site, then its Backups tab. Choose a scope and press Backup …. The bar at the top of the page shows the four steps and the result stays until you dismiss it. Or, from the site list, hover a row and press Back up — that runs the site's default scope, which you set in Preferences.
Scopes
| Full | The whole web root — WordPress core, wp-content, uploads, config — plus the database. The one to keep on a schedule. |
|---|---|
| Content + DB | wp-content (themes, plugins, uploads) plus the database, without core and root files. Enough to rebuild a site on a fresh WordPress, and the scope migrations default to. |
| Content | wp-content only. Files without the database. |
| Database | The database only, as a compressed SQL export. |
wp-content/cache is always left out.
What a backup contains
A folder named <site>-<dd>-<mm>-<yyyy>_<hh>-<mm>-<ss> holding:
public.tar.gz(Full) orwp-content.tar.gz(Content scopes) — the files, one compressed archive made on the server and downloaded once.database.sql.gz— the database export, when the scope includes it.manifest.json— what this backup is: site, scope, source folder, time, table prefix, and every file with its SHA-256 checksum and size.
The checksum is verified after download, and again before a restore. A backup that does not verify is not offered for restore.
Where they live
By default ~/Backups/wpgo; change it in Preferences. An external drive or a synced folder is fine. The details dialog (ⓘ on any row) shows the exact folder and opens it.
Retention
Scheduled backups keep the newest 3, 7, 14 or 30 per site (chosen in the schedule) and remove the rest after each run. Manual backups are never removed automatically.
Deleting
Delete moves the folder into a .trash folder beside the backups and shows Undo for a moment. The trash is emptied after a day.
All backups
Backups in the rail lists every backup of every site, with the site name on each row and the same actions.