FeatureRestores for WordPress
When an update breaks your site or it gets hacked, a restore puts it back the way it was. With BlogVault you can check a backup works before you restore it, bring back the whole site or only the part that broke, and restore even when your site won’t load at all.
In this example, an automatic plugin update breaks a store’s checkout one morning. Here is how the owner gets it back: choose a backup, choose what to restore, test it, then restore.
Backups are shown on a timeline with the changes made between them, so you can see which update caused the problem and pick the backup just before it.
Restore everything, or only one plugin, some files and database tables, or one subsite. Everything else stays as it is.
BlogVault opens the backup as a temporary website you can click through. Your live site isn’t changed while you check.
BlogVault compares the backup with your live site and copies back only what’s different. If WordPress won’t load, the Emergency Connector does the restore instead.
Most problems don’t need the whole site rolled back. Start with the smallest restore that fixes the problem.
Try a test restore▸ Restores and the Emergency Connector are on every plan
Open any backup as a temporary site on our servers. Click through it and check the page that broke before you restore.
Pick files, database tables, a plugin or a theme. Only those come back; new posts, orders and uploads stay put.
BlogVault compares the backup with your site and copies back only the differences, so even a large site is usually restored in minutes.
If your site has crashed, the BlogVault plugin can’t run. The Emergency Connector restores the site using your FTP and database logins instead.
Choosing the right backup matters. Too old and you lose good work; too new and the problem comes back with it. BlogVault shows what changed between backups, so you can see exactly when something went wrong.
Plugin and theme updates, file changes and new content are listed between backups.
A bad plugin update is the most common cause of a broken site. Put just that plugin back to its earlier version, without touching the rest of the site.
Most backup tools can make a copy of your site. The difference shows when you need to restore it.
Host backups are still worth having. They are mainly designed to recover the host’s servers, so restoring a single site from them is often slower and all-or-nothing.
365days of backups
Some problems go unnoticed for weeks: a hacked file, spam accounts building up, or a setting someone changed by mistake. You need a backup from before the problem started, so BlogVault keeps up to 365 days of backups.
Compare plansStores and Multisite networks need more careful restores, because new orders keep arriving and each subsite has its own content.
Real-time backups save every order as it’s placed. When you restore the site to before a bad update, the orders placed since then are kept.
Real-time backups · WooCommerce plan
See real-time backupsSubdomain and subdirectory networks are backed up in full. Restore the whole network, or only the subsite that broke while the others stay online.
Up to 25 or 100 subsites · Business and WooCommerce plans
Multisite backups“If you are looking for a great backup & restore system, you can’t get anything better than BlogVault. Simple for new users with all the functionality required for a website. Do yourself a favour, just use BlogVault.”
The same engine backs up, restores, stages and moves your site. Here is where it helps next.
Backups that finish on any host, even for sites of 100 GB and more. Only the changes are copied, and every backup is stored encrypted off your server.
How backups workA staging site is a private copy of your site for testing updates. Try changes there, then push the ones that work to your live site.
How staging worksEvery order is backed up the moment it’s placed, so you can restore your store after a bad update without losing sales.
See real-time backupsNo credit card · 14-day money-back guarantee