With Jetpack Backup, you can restore your site to a particular point in time — to a specific day or prior to a specific event, change, or issue that you may have encountered — with a single click of a button.
This feature is only available on Jetpack sites with a paid plan.
Restore your site to a particular event
- Open your Activity.
- Scroll down or use filters to find the event you’d like to restore to
- Click the ellipsis (three dots) icon, then click Restore to this point to open the Restore Site dialog box.
- Click Confirm Restore.
- Your site will begin to restore to the specific point in time you have selected. At the top of the Activity page, you can follow the progress of the restore.
- When the restore has completed, you’ll see a confirmation message.
- Click the View Site button to see your site restored to the event that you selected.
Download a backup
- Open your Activity.
- Scroll down or use filters to find the event that you’d like to use, then click the ellipsis (three dots) icon, and choose Download backup.
- On the Create downloadable backup page, click Create download.
- At the top of the Activity page, you can follow the progress of the download creation.
- When it has completed, you’ll see a confirmation message. You can use the Download button to download the backup.
You will also receive email updates on the progress of your restore. For backups, you will receive an email with a link that you can use to download the backup.
The most recent 1,000 events are displayed in your site’s Activity. Jetpack cannot restore your site to an event that does not appear in the Activity and only certain events can be used as a restore point. Applicable events will have the Restore option listed.
Does Jetpack Backup back up nested WordPress installations?
No. We only back up one WordPress site per installation (per Jetpack Plan). We skip any nested directory trees that contain a wp-config.php file.
Do restores delete files?
No. Restores do not delete files. They add and overwrite. However, if you restore to a point before a file (an image, for example) was added, anything in the database referencing the image will be gone. So, the image will not appear on the site, but the image file will still be on the filesystem.
Can I restore even if my site is down or has a fatal error?
Yes! Because Jetpack’s restore system operates separately from the Jetpack plugin itself, you can still restore to a prior event even when your site is down. Important: if your site is down, you’ll see “This site cannot be accessed” in WordPress.com. DO NOT click the Disconnect link there, or you will not be able to access your site’s Activity, and so will not be able to perform a restore.
Have questions? Feel free to contact support for more personalized assistance.
Why am I seeing “Unable to restore the table______ due to existing foreign key constraints”?
Jetpack Backup detected tables that have FOREIGN KEY constraints. The one-click restore feature only supports restoring tables with FOREIGN KEY constraints for WooCommerce. Jetpack Backup does not currently support restoring such tables for any other plugins.
If your site has database tables which use FOREIGN KEY constraints, you’ll need to proceed with one of the following options:
- If you’re comfortable manually restoring your database, then we recommend doing so. You can restore everything but your site’s database using a one-click restore, and then restore the database afterwards by following the “Importing SQL Files” steps here. Knowledge of CLI, phpMyAdmin or equivalent is required.
- You can run a single-file/table restore, which is outlined here. This method allows you to restore specific files, or database tables, rather than the site as a whole and is helpful for working around FOREIGN KEY constraints.
- The final option is for us to enable an option that will tell Jetpack Backup to ignore FOREIGN KEY constraints, which will allow a one-click restore to complete. Note: this is only recommended if the database table(s) in question will be repaired after the restore, or if you know that you’ll never use the table(s) in question.