Backups and restore, from the chat and the account
Rekhu Builder 0.9.40 makes backups of a WordPress site and restores them, from the chat or from the project's Connection tab, with a backup of the current state before every restore.
Maintaining a client's site means updates, and updates mean a backup first. Rekhu Builder now makes that backup itself, and puts it back when an update goes wrong.
Back up from the chat or the account
Say "back up the site" in the chat, or click Back up now on the project's Connection tab. The choices:
- Full: the database plus wp-content, so themes, plugins and uploads.
- Database only: posts, pages, settings and users. Quick, and enough before most changes.
The backup runs in the background on the site, so a large site is not cut off halfway. It is kept on the site in a folder the web server refuses to serve; the newest three stay. Caches and other backup plugins' archives are left out.
Before an update, Rekhu Builder now offers back up, then update, and waits for the backup to finish before it starts.
Restore, with two safety nets
A restore overwrites the live site, so it never happens by accident:
- Confirmed by date. Rekhu Builder first says what goes back, from which date, and what is lost. It restores only after you confirm that backup by its date, in the chat or in the confirmation on the Connection tab.
- A backup before every restore. The database as it is now is saved first, so a restore can itself be undone.
The site's connection with your account stays as it is, so the chat keeps working right after a restore. When the host does not let the site change some files, the answer says how many and which, instead of hiding it.
UpdraftPlus
On a site that runs UpdraftPlus, its backups are listed too, and Rekhu Builder can start one there, with UpdraftPlus's own remote storage. Those backups are restored in UpdraftPlus itself.