WordPress backup management across every client site

It is keeping track of backups across your sites: which have a recent copy, when each job ran, how it finished, how much storage it uses and why any failed. CMDPress shows this for every managed site in one view and lets you create, list and restore backups per site.

As often as the site changes. A store or busy blog may need daily backups, while a site that rarely changes can go longer between them. Always take a fresh backup before major updates, and use CMDPress to spot sites that have gone too long without one.

Yes. CMDPress can create, list and restore backups per site, including to your own Amazon S3. Keeping a copy away from the web server means a hosting problem does not take your backups down with the site, and you can still see each job’s storage use in the dashboard.

Common causes are a full disk or storage quota, a job that times out on a large site, file permission errors, or expired remote storage credentials. In CMDPress, the failed site’s logs and recent activity are one click away, so you can find out which cause it was.

Open the site in CMDPress and restore it from one of its listed backups. Backups are created, listed and restored per site, so a restore touches only the site that needs it. Before you restore, check when the backup ran so you know which later changes will be lost.