Welcome to the Snapshot Pro user guide! This document explains each of the Snapshot Pro features and provides instructions on how to create and store backups of your website and quickly restore it.

If you haven’t installed Snapshot Pro yet, visit the Snapshot Pro product page to download or to get a quick overview of the many available features. If you are a WPMU DEV member, use one-click installation to install Snapshot Pro directly to any connected site.

Privacy Policy Information

Upon activation or when certain features are configured, this plugin may add cookies to the user’s browser, store personal information in your database, or integrate with 3rd-party applications. You may need to disclose this information to your site visitors. For details, see Our Plugins in our privacy policy documentation.

WPMU DEV Hosting Backups

If your site is hosted with WPMU DEV, nightly backups are created for you automatically. See our Hosting Backups guide for a thorough explanation of the backup system in place for sites we host.

Backup FAQs

Did you know that WPMU DEV supports multiple ways to backup sites, including hosting backups, managed backups, and backups created with either of two versions of our Snapshot plugin? To help you make an informed decision on which backup option is best for your project, see our Backups FAQs doc.

13.1 Getting Started

Copy chapter anchor to clipboard

As of version 4.0, Snapshot Pro’s backups are incremental and support both scheduled and manual backups from the Hub, for both sites hosted with WPMU DEV and on third-party hosting.

Snapshot Pro uses the WPMU DEV API to create a secure connection for backup and restore. The API is connected by installing the WPMU DEV Dashboard plugin and connecting your WPMU DEV account. To learn more about the WPMU DEV Dashboard plugin and connecting your site to the WPMU DEV API, visit the WPMU DEV Dashboard documentation.

Thrive With Snapshot v4

Wanting to really take advantage of everything that Snapshot v4 has to offer? Check out our blog on how to Get the Most from Your Site Backups for all the inside tips and tricks.

Get started by installing and connecting the WPMU DEV dashboard plugin and the latest version of Snapshot. This will add a new menu item to your WordPress dashboard. Go to the Snapshot menu item to configure your Backups.

Note: If you would like to see a visual representation of how much space your backups occupy for each site, you can view this on the My Account page of your Hub.

User Profile 'My Account'

Click on Statistics under the Add-Ons tab, and you’ll find a handy chart showing the percentage of the storage distribution of Snapshot backups for all your sites. Hover over each segment to reveal the size of the backups taken up by that site. Every WPMU DEV member gets 10Gb to start, and upgrade plans for increased storage are available in that Addons section.

Snapshot backups shown on your Account page

13.1.1 Setup Wizard

Link to chapter 1

The Setup Wizard will open the first time you click into Snapshot. If this is a fresh install of the plugin on a site, you’ll first be given the option to select either the default Basic Config or one of your own Custom Configs, or to set up the plugin manually.

Snapshot Pro setup wizard

If you select to apply the Basic config, clicking that option will apply it immediately, and you can edit & fine-tune the settings if needed afterwards.

If you select to apply one of your own custom configs, clicking that option will pop open a modal window where you can choose which of your custom configs you want to apply to this site.

Apply a custom config in Snapshot

If you choose to continue with manual setup, you’ll be prompted to set up a “Daily”, “Weekly”, or “Monthly” backup schedule. Choose the day, day of the week/month, and time you want backups to be scheduled. You can also choose “None” and create a schedule later if you prefer. See the Backups section for more.

Set backup schedule in Snapshot setup wizard

If you do not want to schedule a backup at this point, you can also just click the “X” icon in the upper right corner to close the wizard and continue to the Snapshot Dashboard.

Click Save to schedule your managed backups. When saved, the wizard will close with a notification at the top of your screen about when your first backup will run.

Snapshot backup schedule confirmation notice

You’ll also find your schedule displayed at the top of the Snapshot Backups screen where you can edit it if needed.

Snapshot backup schedule

NOTE:

The first time backups can take some time to complete since the first backup is a full site backup. Subsequent backups will be much faster as they are incremental backups. Apart from scheduled backups, you can also run backup manually. For more information, see the Backups section below.

The Snapshot Pro Dashboard provides an overview of your scheduled backups, what third-party destinations are linked, and when your last backup was run. The dashboard has three modules:

This chapter provides information about what is available in the Snapshot Dashboard section.

Constant Improvement

Whether you’re new to Snapshot or you’re a veteran, it’s worth knowing that we are dedicated to constantly improving Snapshot in every way possible. And some of the newer feature additions are ones that you don’t want to miss out on – like incremental backups and third-party storage options. For more information on these key features, check out Snapshot v4 Introduces New Incremental Backups and Third-Party Storage.

13.2.1 Overview

Link to chapter 2

The Overview section is a quick way to see what settings and destinations are set up and active with your Snapshot backups. Available information in the Overview section includes:

  • Backups Available – Number of backups currently being stored in your cloud storage
  • Available Destinations – The number of connected backup locations. A full explanation of what destinations are and how to configure them can be found under the Destinations section of this guide.
  • Last Backup – Lists the date and time of your most recent successful backup
  • WPMU DEV Storage Space – Available WPMU DEV Storage Space included with your plan and how much storage has been used. Every WPMU DEV member gets 10Gb to start, and upgrade plans for increased storage are available in the Addons section of your Account page. If you are running both Snapshot version 3 and version 4, this includes the total storage used across both versions.

dashboard overview statistics

13.2.2 Backups Overview

Link to chapter 2

The Backup overview module is a quick way to see information about your latest backups. For more information about configuring Backups, visit the Backups chapter. The Backup Overview module shows:

  • Title – This is the date of a scheduled backup or the title you entered for an on-demand backup
  • Destination – Tells what storage solution is being used

Overview of backups in Snapshot 4.0 dashboard

Clicking the “View All” button redirects you to the Backups section where you can get more detailed information about all available backups.

Click the “Backup Now” button to trigger an on-demand once-off backup. In the Creating Backup modal that pops open, you will add a title or a note about the backup to help make your backup easier to identify. For more information about creating Backups, visit the Backups chapter.

If you would like to apply global file exclusion settings, check the box next to the “Apply global file exclusions set in the settings page.” For more information, see the Global Exclusions section in Backups Settings.

13.2.3 Hosting Backups Overview

Link to chapter 2

The Hosting Backups widget gives you a brief overview of your latest hosting backups with the date, time and destination of each backup. Click the View All button to jump to the Hosting Backups tab to access and manage all of your hosting backups.

hosting backups dashboard overview

13.2.4 Destinations Overview

Link to chapter 2

The Destinations Overview module lists all your connected cloud storage accounts where backups can be stored.

dashboard destinations overview

Click the View All or Add Destination button to open the Destinations tab where you will be able to connect other destinations and get more information about your connected accounts. You can also click the toggle of any third-party destinations to activate/deactivate them or click the gear icon to configure them.

Learn more about Destinations and configuration options in the Destinations chapter.

The Backups screen has everything you need to view, manage, configure, run, restore, delete, and download Snapshot 4.0 backups. At the top of the screen is an overview showing the following information:

  • Backups available – Number of backups currently being stored in your cloud storage.
  • Storage space – The amount used and total amount of available WPMU DEV Storage Space included with your plan.
  • Last backup –The date and time of your most recent successful backup
  • Next scheduled backup – The date and time of next scheduled backup. If no schedule has been set, this will indicate Never.
  • Backup schedule – The current backup schedule. If no schedule has been set, this will indicate None.

Snapshot backup overview

13.3.1 Backups Tab

Link to chapter 3

There are numerous things you can do in the Backups tab. Here’s a list linked to the corresponding sections describing each task in this doc below:

Please see the Restoring Backups chapter below for details on how to restore your Snapshot backups.

Create a Manual Backup

The first time you visit the Backups tab, you’ll be greeted with a prompt to run a backup now if you haven’t already. Click the Backup Now button to get started. This first backup will be the base backup and is a full backup of your site. Any following backups will be incremental, regardless of whether they are manual or scheduled.

No backups yet in Snapshot 4.0

Optionally enter a title and descriptive comment for your manual backup, and apply global file exclusions if needed. Click Run Backup to initiate the backup.

Create a manual backup

The modal will close and you’ll see a progress bar indicating at which step the backup is currently at. Once that has completed, you’ll see your new manual backup in the list of Available Backups.

Manual backup progress in Snapshot 4.0

Create a Backup Schedule

If you have not yet set up a schedule for your backups, or wish to modify your existing backup schedule, click the Manage link in the Overview section next to Backup schedule.

Create a backup schedule

This will open a modal just like the one you saw when you went through the Setup Wizard. The backup scheduler lets you choose to create a “Daily”, “Weekly”, or “Monthly” schedule. Choose the day, day of the week/month, and time you want backups to be scheduled. Click the Save Schedule button to finish.

Set backup schedule in Snapshot 4.0

Available Backups

Once you have at least one backup completed, you’ll see a list of all your available backups with the most recent one at the top. You can create a new incremental manual backup at any time by clicking the Backup Now button at top-right.

Backup Now button

For each backup, the Title is either the name entered at the time of backup, or the date. The Storage is WPMU DEV, and the Destination is the cloud service to which the backup was exported. The Frequency is either the schedule at which the backup was saved (Daily, Weekly, or Monthly), or None if the backup was saved manually.

Click on a listed backup to access additional information and available actions. The following details are available for each backup:

  • Export Destination – This lists all of the destinations to which your backup has been exported.
  • Current Schedule – Clicking on the schedule opens the schedule modal for you to change the frequency, day, and time your backup runs.
  • Global Exclusions – A list of any global exclusions applied to your backup at the time of the specific backup. Get more details about setting and understanding Global Exclusions in the Settings chapter of this document.
  • Date – When the selected backup ran.
  • Export Size – This notes the size of the selected backup.
  • Comment – S descriptive comment to help distinguish between saved backups. Click the pencil icon next to the comment to edit the backup comment.

Backup details

Additional Actions per Available Backup

There are four action buttons along the bottom of the details section for any backup:

  • Delete
  • Restore
  • View Logs
  • Download

Delete a Backup

Click the Trash icon to delete the most recent backup.

Delete Backup button

As Snapshot backups are incremental, you can only delete the most recent backup of the site from this page. See the Incremental Backups chapter below for more information. If you need to delete all the backups from your site, you can do that on the Backups > Settings tab.

When you delete backups, you will be asked to provide your WPMU DEV account password as a security precaution.

Note that if you signed up to WPMU DEV using your Google account and have not yet set a WPMU DEV password on your Hub Account page, you can authenticate the backup deletion using your Google account instead.

Confirm WPMU DEV password

If you select to authenticate with your Google account, you’ll be prompted to select and confirm the account you wish to use for this action.

Login to your WPMU DEV account

If you want to delete subsequent backups after providing your password, you will simply need to confirm the deletion and will not need to provide your password each time.

confirm delete backup

This security precaution can be enabled/disabled via The Hub backup settings. For more information on those settings, please refer to the Hub 2.0 Backups documentation.

View Logs

Clicking the View logs button opens the backup log in the Logs tab. Get more information about the logs tab in the Logs section of this document.

View Logs button

Download a Backup

Clicking the Download button will prepare an export version of the selected backup and email you a link that allows you to download the backup. The email will also contain the name of your selected backup so you can identify it; handy in case you’ve chosen to download several of them.

The link in the email expires in 7 days, but the backup itself will of course still be stored for 50 days. If the download link expires and you need to download that specific backup again, click the Download button again to generate a new email and link.
Download Backup button

13.3.2 Logs Tab

Link to chapter 3

Clicking the Logs tab opens a history of all the backups for the site. You can use these to debug issues and see what’s happening behind the scenes with each backup.

The Available Logs section is an overview of all backups with the most recent backup at the top. Backup information includes the Date and Destination.

View all backup logs in Snapshot 4.0

Clicking a backup will open the full log for that backup. Sort the information from your log with:

  • All – Display the entire report
  • Warning – Only display warnings and errors
  • Errors – Only display errors

Sort backup logs in Snapshot 4.0

Click Load More to view additional log entries, or click Download to download the entire log of timestamped actions. Additionally, click View Backup to navigate to the backup listed on the Backups page.

Logs button

13.3.3 Settings Tab

Link to chapter 3

The Backups Settings tab allows you to set exclusions and view the number of backups your site will save, among other useful settings.

Exclusions

Exclude Large-Size Folders

Sometimes large folders and other plugins’ backup files cause issues during a backup, causing it to get stuck. Use this feature to exclude those potentially problematic folders by clicking the toggle.

exclude large-size folders toggle

You can view the full list of folders that will be excluded by the feature by clicking on the arrow next to the toggle. This will trigger the row to drop down and reveal the list.

list of excluded large-size folders

Global File Exclusions

This setting allows you to choose specific files or folders you want to exclude from your once-off and scheduled backups. Enter the relative path to the file or folder you would like to exclude from your backup and press enter to add an exclusion; for example: /wp-content/custom-folder/ or /file.php.

You can also use the shortcut buttons to automatically exclude WordPress Core files & folders, the Themes directory and/or the Plugins directory.

Snapshot global file exclusions

Click the X icon next to any added exclusion to remove it from the list. If more than one exclusion has been added, click Clear exclusions to remove all exclusions at once.

Storage Limit

By default, WPMU DEV’s cloud storage will keep the most recent 30 backups of manual and scheduled backups each, before removing the older ones. However, you can change this to any number between 1 and 30 by inputting the number and clicking Save.

Set storage limit in Snapshot

This can also be adjusted within The Hub. Check The Hub Backups documentation for more information on this.

Please be aware that backup rotation can take some time if you change the limit to a lower number here. For example, if you already have 30 backups stored and set the limit to 10, it may take several hours for the API to process the request and remove older backups.

This is not to be confused with how long backups are retained. Remember, you won’t necessarily create one new backup per day. Backups are retained for 50 days with Snapshot v4, meaning that you could hit your storage limit of 30 backups (or whatever limit you have set) before you hit your time limit of 50 days. For example, if you create one new manual backup every day for 31 days (with a storage limit of 30 days), the first manual backup you created would be replaced on the 31st day and therefore would not have been retained for the full 50 days that are available. The difference between the storage limit and the retention time for backups is an important distinction to make.

Where Snapshot v4 really shines is in the fact that you can store up to 30 manual backups and 30 scheduled backups (60 in total) for up to 50 days. This means that more backups are stored for longer and it is largely due to the fact that v4 uses incremental backups as opposed to full backups like in Snapshot v3. More information on incremental backups and why v4 is more efficient can be found in Incremental backups.

Note that manual and scheduled backups each have a separate incremental backup chain, and each has a separate base backup. So if you are already running scheduled backups on your site, there is no need to run regular manual backups as that would just wind up doubling the backup storage space used.

Storage region

You can select which storage region you prefer for all your backups:

  • United States – This region is recommended for better performance.
  • Europe – This region is EU data protection directive compliant.

Select WPMU DEV cloud storage region in Snapshot 4.0

If you switch between regions, you will be required to provide your WPMU DEV account password as a security precaution.

Confirm WPMU DEV password

This security precaution can be enabled/disabled via the Hub backup settings. For more information on those settings, please refer to the Hub 2.0 Backups documentation.

IMPORTANT

If you switch to a new region, your existing backups will be deleted, and any new backups will be stored in the newly selected region.

Delete Backups

Delete is a one-click option to remove all backups. Clicking the Delete button will open a modal where you will need to confirm your action by providing your WPMU DEV account password and clicking Delete. Click Cancel or the close modal icon [X] to close without Deleting remote backups.

Delete all backups in Snapshot 4.0

13.3.4 Notifications Tab

Link to chapter 3

When enabling the Notifications module, you can select to receive an email notification when either a manual or scheduled backup fails or completes.

email notifications settings for backups

By default, your admin email will appear as a recipient but all emails can easily be added or removed. If you remove all recipients, we’ll automatically turn off the notifications. Remember to Save Changes to keep your changes.

13.4 Restoring Backups

Copy chapter anchor to clipboard

Snapshot enables you to restore a site backup using any of several options.

If your site is still up and running:

  • Restore any available backup right in your wp-admin with a click of a button. See the Restore From Your Site Admin chapter below for details.

If your website is down (ie. white screen of death or unable to access wp-admin), there are 2 ways you can restore a backup:

  • Manually restore by uploading your backup and an installer file to your server and use the Snapshot Installer wizard. See the Restore With An Installer File chapter below for details.
  • Alternatively, you can try the automated FTP restore tool in your Hub; see Auto restore via FTP in our Hub 2.0 > Backups documentation.

13.4.1 Restore From Your Site Admin

Link to chapter 4

On the Snapshot Backups screen in your site admin, click on your desired backup to expand it. Then click the Restore button to open the Restore Backup modal.

Restore button

The Restore Backup modal indicates the directory where the backup will be restored. Click the “Restore” button to restore to the selected backup. Keep the page open until the process has finished.

Directory where backup will be restored in Snapshot 4.0

During the restoration, a progress indicator will let you know where the restore is at, and which steps have already been taken.

There are 5 steps in restoring your site:

  • Backup exported
  • Download backup
  • Restore files
  • Restore database
  • Finalize restoration
NOTE

The restore process will overwrite the database and restore all files contained in the backup, but it will not delete any files uploaded to the site after the backup was made. So any plugins, themes, media, etc, added to the site after the backup was made will still be there once the restore completes. Please keep this in mind and know that you would need to delete those files manually before or after the restore if you don’t want them anymore.

Progress of backup restore in Snapshot 4.0

This process could take a few minutes for small sites and up to a few hours for larger sites. A notification will appear at the top of your screen when the restoration is complete, and will include a link to view the site.

Backup restore success message in Snapshot 4.0

If the backup restore from your site fails for any reason, you’ll see an alert like this at the top of your screen, with specific information about the failure if it’s available. Click the links to check the logs or contact our support if you need help.

Snapshot backup failed notice

You can also try restoring via FTP instead from your Hub. Click the FTP restoration method link to be redirected automatically to the correct screen in your Hub to proceed with that. For more information about that process, please see our Restore Website (Snapshot) documentation.

NOTE:

To protect your site during the Restore process, if an error occurs while a backup is being exported or downloaded, the restoration will pause, cancel the restoration process, and leave your site as is. If the errors persist, use the Logs to locate the issue or contact your support team.

Restore backup when there is no access to the site

If you need to restore a backup of your site, but can’t access the wp-admin to get it done, the above procedure of restoring your website will of course not work.

Snapshot v4 also allows you to restore backups via the Hub where you can use the Auto restore via FTP process.

You can also download the needed files to restore the site manually with an installer file, as seen in the next chapter.

13.4.2 Restore With An Installer File

Link to chapter 4

If your site is not accessible, and the Auto restore via FTP option in your Hub is not working for you, you can download the needed backup files and upload them to your server manually. Then follow the directions in the Snapshot Installer Wizard to get the site back up and running again.

Step 1 – Get your backup files

There are 2 places where you can get the files you need for your backup restore:

Get the files from your Hub

To get the files from your Hub, go to the Backups tab for the site you need to restore, and click on the backup you want.

Select Snapshot backup in the Hub

Then, in the modal window that pops open, click the Restore button.

Snapshot backup restore modal

Select the My website is unavailable option.

Backup restore options in the Hub

You’ll then see the 2 files you need to download: your backup zip file and the snapshot-installer.php file.

Backup restore site inaccessible option in the Hub

The installer file will download right away. But it will take a few minutes for the backup files to be zipped up, so the system will send that to you at your WPMU DEV account email address as soon as that’s done.

Get the files from your Account page

If your site is no longer connected to your Hub, you can access your backup and the installer file from your WPMU DEV Account page. Click on your profile image in the top-right corner of your Hub and select My Account.

My Account link in the Hub

In the Add-Ons section, click the View Backups & Statistics link on the far-right of the Snapshot row to toggle it open. Under All Backups, filter the list if needed to display only backups for Active, Deleted or All Sites. Then click the Download link for the backup you want.

View Snapshot backups on your Account page

This will open a modal window where you can download the full backup and the snapshot-installer.php file which is required to restore a backup for a site that is inaccessible.

Download a Snapshot backup from your Account page

Step 2 – Upload the files to your server

Now that you have obtained the files you need to restore your backup, you’ll need to use either an FTP/SFTP or SSH connection to upload the backup package and installer file to your server. If you are not sure how to use an FTP/SFTP client or SSH, see our SFTP & SSH documentation.

The installer file will download as a zip file named snapshot-pro-standalone-restore-script-2.zip. If that file does not unzip automatically on your computer, be sure to unzip it manually to get the snapshot-installer.php file inside. That’s the installer file you want to upload.

However, do not unzip the backup download once you receive it via email though. If that one does unzip automatically on your computer when you download it, be sure to zip it up again before uploading to your server.

Upload both the zipped backup package and the unzipped snapshot-installer.php file to the root directory of your WordPress site. This is most often the public_html directory, but it may be different depending on your particular setup.

Have enough space on your server?

Before uploading your files and running the restore wizard, please ensure you have enough disk space on your server for the process to run. You should account for at least double the size of your backup zip as the restore process will extract its contents and create temporary folders while it is running. A lack of adequate disk space on your server will cause the restore to fail.

Step 3 – Run the Snapshot Installer wizard

When the files have been uploaded to your server, go to https://yourwebsite.com/snapshot-installer.php in your browser, replacing yourwebsite.com with your site’s actual domain name.

This will open the Snapshot Wizard that will walk you through all the steps of your backup restore. Click the Get Started button at the bottom to begin.

Run the Snapshot installer wizard

Requirements Check

The first step will begin by running a check of all the requirements for the backup restore.

Requirements check in Snapshot installer wizard

This step only takes a few seconds and will look for any issues that can possibly hinder a successful backup restore. If no issues are found, the wizard will automatically proceed to the Database Configuration step.

If any issues are found, they will be listed as below.

  • Backup Archive not found – This appears if the backup zip has not yet been uploaded to the same directory as the installer file.
  • PHP MySQLi module not found – Snapshot needs the MySQLi module to be installed and enabled on the target server. If you use a managed host, contact them directly to have this module installed and enabled.
  • Zip module not found – To unpack the zip file created by Snapshot, the PHP Zip module will need to be installed and enabled. If you use a managed host, contact them directly to have it added or updated.
  • PHP v7.0 or newer is required – Snapshot Pro requires PHP version 7.0 or later. If your host is using an older version of PHP Snapshot Pro will display a low PHP version or PHP version is out of date warning. You’ll need to update your PHP version to proceed.
  • Open_basedir is enabledopen_basedir must not be configured on your server. If it is, you’ll need to disable it or contact your host for help to get that done.
  • Max Execution Time is too low – A minimum execution time of 150 seconds is recommended to give the migration process the best chance of succeeding. If you use a managed host, contact them directly to have it updated.

Issues found by the Snapshot installer wizard

Click on any issue to expand it and reveal the steps needed to resolve it. Then click the Re-Check button at the bottom to run the requirements check again.

Details of issue found by the Snapshot installer wizard

Once all issues are resolved, the wizard will automatically proceed to the next step.

Database Configuration

The next step is to connect to your database. It is recommended you create a new database, but if you are restoring a backup to overwrite an existing site where a wp-config.php file is detected, you’ll have the option to overwrite the existing database once you’ve tested the connection.

Click the toggle next to Use the database credentials from your current wp-config file. Then click the Test Connection button at the bottom to verify that the connection does indeed work.

Use existing database in Snapshot installer wizard

Note that if you change the detected Database Prefix shown here, the restore process will create a new set of database tables with that new prefix instead of overwriting the existing tables.

If you prefer to use a new database as recommended, do not toggle the option above, and enter the credentials in the fields provided instead. Then click the Test Connection button.

Use new database in Snapshot installer wizard

If the connection is successful, you’ll see a confirmation message appear, and you can then click the Deployment button to proceed.

Successful database connection in Snapshot installer wizard

Deployment

While the Deployment is running, you will see a progress bar indicating the overall progress of the backup restore, and which step the installer is currently working on.

Backup deployment in Snapshot installer wizard

If there are any issues that prevent the backup restore from completing, the installer will stop and notify you that the deployment has failed.

Click the View Logs button to get detailed information about what went wrong so you can fix the issues and attempt the restore again.

Deployment failed in Snapshot installer wizard

Once the restore has completed, you’ll be prompted to click the Run Cleanup button, which we highly recommend.

Deployment complete in Snapshot installer wizard

Note that if there are any files included in your backup that could not be restored, due to permission issues for example, a notice will appear once the deployment has completed. Click on that notice to view a list of which files could not be automatically restored so you can upload them manually if needed.

Deployment skipped files in Snapshot installer wizard

Finish and Cleanup

This final step will remove the installer file, the backup zip and all temporary files created by the restore wizard so your site will be exactly as it was when you made the backup.

Once that’s done, you’ll see a confirmation message which will disappear after a few seconds and your newly restored site will load in your browser.

Cleanup complete in Snapshot installer wizard

13.5 Hosting Backups

Copy chapter anchor to clipboard

If your site is not hosted with WPMU DEV, this module will not be visible to you. At the top of the screen is an overview showing the following information:

  • Backups available – Number of backups currently being stored in your cloud storage
  • Last backup – Lists the date and time of your most recent successful backup
  • Next scheduled backup – The date and time of the next backup according to the schedule you set. If no schedule is set yet, this will indicate “Never“.
  • Backup schedule – The currently set backup schedule. If none is set yet, this will indicate “None“.

Hosting Backup overview

Underneath the overview is a panel with more details on each backup. This is where you will find a list of all your backups created on WPMU DEV hosting, as well as Automate backups.

available hosting backups

If you want to download a hosting backup straight from Snapshot v4, click the Download button and a backup link will be processed and sent to your email address. Please note that the time taken for the backup link to be processed and sent to you varies depending on the size of the site.

Hosting Backup details

At the moment, backups cannot be created or restored through the plugin but this is something that will be incorporated in future releases. For the time being, you can click the Manage button for a quick link to the Hub, where you can fully manage all of your hosting backups.

Storage Limit

Currently, WPMU DEV hosting backups will be removed after 30 days. This storage limit cannot be changed.

A destination is a 3rd-party location where your Snapshot backups can be stored.

Want a quick overview of Destinations?

Check out How to Quickly Backup to S3, Google Drive, and Dropbox Using Snapshot Pro on the blog. Read on below for detailed instructions for each available destination.

At the top of the Destinations screen, is an Overview module with:

  • Number of destinations
  • Last backup destination
  • Available WPMU DEV storage space

Destinations overview

Below is the Destinations module with a list of connected destinations. Hub connected sites are automatically connected to WPMU DEV cloud storage and do not require any additional setup to connect. The Hosting Backups module is only accessible by WPMU DEV Hosting and does not require any further configuration.

The Destinations module lists:

  • Name – Name of the destination, provider, or location where the backup will be stored.
  • Directory – This is where the backups are being stored. WPMU DEV cloud storage does not allow you to change directories.
  • Schedule – The current schedule for your backups.
  • Exported Backups – This is the number of backups currently being stored on your account.

destinations details

The destinations module allows you to add multiple destinations for your backups, even from the same third-party storage provider. You can manage these destinations with the configuration tools.

Third-party Backups

As you may know already, WPMU DEV Cloud Storage stores incremental backups of your site. However, if you choose to add a third-party destination, full site backups will be uploaded to that destination, not incremental backups.

All destinations can be re-configured, deactivated, or deleted at any point. Simply slide the toggle to deactivate the destination, or click on the gear icon for alternative options, which are:

  • Edit destination – Change your current setup with regards to your destination name, bucket, directory path, connection credentials, and storage limit.
  • View directory – Use this to jump to your third-party destination account.
  • Delete – Click Delete to remove his destination.

destination-configuration-tools

Single Schedule

While you can add as many destinations as needed, you can only set up one backup schedule. It is not possible to have different schedules running for different destinations. The schedule that you have configured will apply to all destinations that you have added.

To add a new destination for your backups, click the Add Destination button.

add destination button

The following Snapshot destinations are supported:

  • Amazon S3 (and S3 Compatible Storage)
  • Google Drive
  • Dropbox
  • FTP/SFTP

Connect to a 3rd-party storage destination in Snapshot

NOTE

Any third-party destinations that are added do not bypass the WPMU DEV Cloud Storage. Your backups go through the WPMU DEV Cloud Storage and from there, they are sent to the new destination. So, you can think of these third-party destination backups as full site copies of your last backup, rather than a new backup.

New destinations are added by using a set of credentials to connect to the third-party destination. These credentials are not stored on your site, they are stored safely on the WPMU DEV end.

Deleting Backups

Since the backups sent to third-party destinations are copies of the WPMU DEV backups, The Hub only shows the backups stored on the WPMU DEV storage space. This means that deleting a WPMU DEV backup will not delete the copy stored on any third-party destination. You will have to access your own accounts for the connected third-party destinations to delete the copies stored there.

13.6.1 Amazon S3

Link to chapter 6

After clicking Add Destination, a modal will pop up with the backup destination options. Ensure that Amazon S3 is selected and click Next.

amazon s3 storage

Under the Amazon S3 tab, enter the following credentials to connect:

  • AWS Access Key ID
  • AWS Secret Access KEY
  • AWS Region

connect amazon s3

NOTE

China (Beijing) and China (Ningxia) AWS regions are currently unsupported by Snapshot.

If you are unsure about how to find your Amazon S3 credentials, you can click on the How to get Amazon S3 credentials? dropdown arrow. This will trigger the row to expand and reveal a step-by-step guide to finding your credentials for both Root and IAM users.

amazon s3 credentials step-by-step guide

We have also included a full step-by-step guide which you can find in the How to get Amazon S3 Credentials section below.

Once you have entered your credentials and selected your AWS Region, click Next. You can now select your Bucket and provide the Directory Folder Path (optional).

Remember to add a forward slash before your folder name. You also need to separate any subfolders from the main folder with a forward slash, as well as any subsequent sub-folders. For example, these would be correct directory folder pathways: /folder and /folder/subfolder/next_subfolder.

choose bucket and directory for amazon s3

You will also be required to set the Backup Storage Limit. This is the number of backups that will be stored before new backups start to replace old ones.

If you want to test whether your connection is working, you can click the Test Connection button. If your connection is on the right track, you will receive a success notification. Click Next to proceed.

Now you can give your destination any name that you want. This is to help you identify your new destination from the full list.

destination name for amazon s3

You can return to any steps by clicking the Back button or if you’re done with everything, click Save Destination.

How to Get Amazon S3 Credentials

To find your Amazon S3 credentials, all you have to do is follow these simple steps:

create a new amazon s3 bucket

Take note of the Bucket region as you will need this to connect properly.

Navigate to the My Security Credentials section by clicking on your account name in the top right-hand corner.

my security credentials tab in amazon s3

From there, you can expand the Access keys (access key ID and secret access key) tab and click Create New Access Key.

create new access key in amazon s3

In the popup modal, you will receive your Access Key ID and the Secret Access Key. Be sure to download the key file and keep your access keys safe. Use these credentials to connect Amazon S3.

13.6.2 S3 Compatible Storage

Link to chapter 6

The beginning of this process is much like connecting Amazon S3. From the Destinations tab, click the Add Destination button and select Amazon S3 from the available options.

amazon s3 storage

Click Next to proceed to the next screen.

Now, you can select your preferred S3 Compatible Storage option from the dropdown menu.

choose an s3 compatible storage

The available storage options are:

Backblaze

Once you have selected Backblaze from the dropdown menu, you will see a set of credential fields that are needed to connect Backblaze. The required credentials are:

  • keyID
  • applicationKey
  • Region

Backblaze credentials needed to connect (1)

Either expand the How to get Backblaze credentials bar or see the section below for a guide to finding those credentials. Enter your credentials and click Next. You can now choose your bucket, directory path, and storage limit, as shown in the Amazon S3 section. Give your destination a name and save it to complete the setup.

How to Get Backblaze Credentials

create a backblaze bucket

Take note of the region as this is something you will need later to connect. Your region can also be viewed in the Buckets section and is specified in the Endpoint. In this example, the region is us-west-00.

backblaze bucket endpoint

Go to App Keys, scroll down to the Your Application Keys section, and click the + Add a New Application Key button.

Create an app at Backblaze for Snapshot destination

In the modal window that pops open, give your app key a Name, and select whether it should have Access to all buckets or just a specific one. Adjust the other options if needed and click the Create New Key button.

Create an app at Backblaze for Snapshot destination

You will then see a Success message where your applicationKey will be displayed only once.

Create an app at Backblaze for Snapshot destination

Copy the applicationKey now and paste it in the corresponding field in your Backblaze destination in Snapshot. Then copy the keyID and paste that along with the Region you copied above into the corresponding fields in your destination as well. Click the Next button there.

Backblaze app for Snapshot destination

Then Choose the Bucket you want to use, and click the Test Connection button to verify the account.

Test Backblaze app for Snapshot destination

Click the Next button. Then enter a Name for your destination if you wish and click Save Destination.

Backblaze app for Snapshot destination

DigitalOcean Spaces

Once you have selected DigitalOcean Spaces from the dropdown menu, you will see a set of credentials that you need to provide. The required credentials are:

  • Access Key ID
  • Secret Access Key
  • Region

digital ocean connection credentials

Either expand the How to get DigitalOcean credentials bar or see the section below for a guide to finding those credentials. After entering your credentials in the fields, click Next. You can now choose your bucket, directory path, and storage limit, as shown in the Amazon S3 section. Give your destination a name and save it to complete the setup.

How to Get DigitalOcean Spaces Credentials

If you don’t already have an existing space, click Create and select Spaces from the dropdown menu.

create new digital ocean space

Take note of the region chosen for the space, as this is an important credential to successfully connect DigitalOcean Spaces as a new destination. You can always view your region at a later stage by viewing your Endpoint in your Space Settings section. The region appears before .digitaloceanspaces.com; in the example below, this would be nyc3.

digital ocean spaces region in endpoint

Furthermore, the region can be viewed by hovering over your space under the main Projects tab.

digital ocean spaces region by hover

Navigate to the API section and under Spaces access keys, click Generate New Key.

API section in digital ocean

generate new key for digital ocean space

Once you have named your key and have clicked Generate Key, you will see the Test key (access key) and Secret (secret key) appear. These are the credentials you can use to connect your DigitalOcean Space.

access key credentials digital ocean

Wasabi

If you have selected Wasabi from the dropdown menu, you will see a set of credential fields that you need to fill in to connect. The required credentials for Wasabi are:

  • Access Key ID
  • Secret Access Key
  • Region

Wasabi credentials needed to connect

Either expand the How to get Wasabi credentials bar or see the section below for a guide to finding those credentials. Once you have entered your credentials, you can click Next. You can now choose your bucket, directory path, and storage limit, as shown in the Amazon S3 section. Give your destination a name and save it to complete the setup.

How to Get Wasabi Credentials

If you haven’t created a bucket yet, you can create one by clicking on Create Bucket.

create bucket in wasabi

Remember the region you have chosen here since this is an important piece of information needed to successfully connect Wasabi.

Next, go to the Access Keys tab on the left sidebar and click Create New Access Key.

create new access key for wasabi

Select Root User and click Create.

create root user access key wasabi

This will generate your access key and secret key credentials. Be sure to download the key file now because you will not be able to retrieve your access key again.

Google Cloud

If you have selected Google Cloud from the dropdown menu, you will see a set of credential fields that you need to fill in to connect successfully. The required credentials for Google Cloud are:

  • Access Key
  • Secret
  • Region

google cloud required credentials

Either expand the How to get Google Cloud credentials bar or see the section below for a guide to finding those credentials. After providing your credentials, click Next. You can now choose your bucket, directory path, and storage limit, as shown in the Amazon S3 section. Give your destination a name and save it to complete the setup.

How to Get Google Cloud Credentials

Once you have logged in, you need to navigate to your Storage page from the sidebar on the left.

storage tab google cloud platform

Next, go to Settings>Interoperability, which is where you can create a new HMAC key.

google cloud settings interoperability

A little further down that page, you can click Create a key for a service account.

create a key for a service account

Now choose the service account that you want your HMAC key to be associated with and click Create key. A key module will pop up where you can copy your Access key and Secret. Make sure to copy the key’s secret at this point because once you close the module, you won’t be able to view it again.

google cloud hmac key

The last piece of the puzzle to connect everything is the Region which can be found on your Storage page. If you look under the Location column, you will be able to see the region for that bucket. In the example below, the region is us-east1.

google cloud region

Other

Selecting Other from the S3 Compatible options allows you to add a destination that may not be listed. To connect to this destination, you will need to provide the following credentials:

  • Access Key ID
  • Secret Access Key
  • Endpoint

add other destination

Once you have filled in these credentials, click Next.

Choose the bucket for your destination by using the dropdown field. You can also provide a Directory Folder Path if you wish, but this is not essential, as well as adjust your Backup Storage Limit. Click Next when you’re done.

choose bucket for other destination

Lastly, give your destination a name to distinguish it from your other destinations and click Save Destination.

name other destination

13.6.3 Google Drive

Link to chapter 6

Once you have clicked Add Destination from your Destinations tab, you will need to select Google Drive in the destination modal and then click Next.

google drive storage

From here, all you need to do is click Connect with Google to connect Snapshot with your Google Drive. For more information on the use of our Google Drive authorization, read our Privacy Policy.

connect with google for google drive

Select which Google account you want to connect to Snapshot.

choose a google account

Click Allow so that Snapshot can access your Google Drive to store copies of your backups. You can always de-authorize your Google Drive connection with Snapshot by following the steps in De-authorize Google Drive account.

allow snapshot access to google drive

Once the connection has been established, you will see a confirmation modal where you can click Next to continue setting up your destination.

google drive authorization successful

All that is required now is for you to provide your Directory ID. If you are unsure of where to find your Directory ID, you can refer to our guide on How to find your Directory ID. You can also adjust your Storage Limit, which will set the maximum number of backups that will be stored before new backups start replacing older ones. When you’re ready, click Next.

connect google drive

The last step is to give your destination a name to help you identify it among your other destinations. When you’re done, click Save Destination to complete the process.

name google drive destination

Editing Google Drive Destination

At the moment, there is no option to edit a Google Drive destination. If you need to change your destination, with the same Google account, you will need to remove the existing destination and add a new one.

How to find your Directory ID

Snapshot will send your backup copies to a folder of your choice which means that if you don’t already have a folder for this, you will need to create one. You can create one by clicking New in the top left-hand corner and selecting Folder.

create new google drive folder

Name the folder and click Create.

name google drive

Navigate to your folder and copy the Directory ID from the URL. This is the path at the end of the URL. In the example below, the full URL is https://drive.google.com/drive/folders/1IUupJopejLS4Piauv9yB_p9nz3ZK0ggy which means that the Directory ID would be 1IUupJopejLS4Piauv9yB_p9nz3ZK0ggy.

google drive directory ID

This is the Directory ID that you can use to complete your Google Drive destination setup.

IMPORTANT

Snapshot will create a child-folder inside your destination folder with the name of the site you connect, and store that site’s backups in that folder. Do not use any such auto-created child-folder as the Destination ID for a different site’s backups, because the API will overwrite the contents inside with new backups from the site it was created for. Also, do not delete or rename these auto-created child-folders as that will cause subsequent backups to fail.

De-authorize Google Drive Account

If you decide at any point that you no longer want WPMU DEV to be linked to your Google Drive, you can choose to de-authorize the account. This is stipulated in our Privacy Policy document, which you may want to read through if you have any questions regarding the use of your data with Snapshot.

NOTE

De-authorizing your Google Drive account will mean that any Google Drive destinations on all of your sites will no longer work. For this reason, we advise that you only de-authorize your account if you are sure that you do not want Google Drive to be connected to Snapshot.

To remove WPMU DEV access, follow these steps:

Scroll down to Third-party apps with account access and click Manage third-party access.

manage third-party access for google drive

Select Snapshot from your list of third-party apps and click Remove Access.

remove third-party access to google drive

You will then be asked to confirm the removal of access. Click Ok to proceed or click Cancel to exit without making any changes.

13.6.4 Dropbox

Link to chapter 6

To add a Dropbox account as a Snapshot destination, first click Add Destination.

add destination button

Select Dropbox from the list of destinations, and click Next.

dropbox storage

Click Authenticate to be redirected to the Dropbox authorization page.

connect dropbox (step 1)

Sign in with your Dropbox account credentials, or create a new account.

connect dropbox (step 2)

When prompted, click Allow to allow the Snapshot DB API to connect to your Dropbox account.

connect dropbox (step 3)

Once the connection has been established, you will be redirected back to Snapshot. Click Next to proceed.

connect dropbox (step 4)

Enter a name for the Dropbox directory to which Snapshot backups will be saved, and the maximum number of backups that should be saved to Dropbox before older backups are removed. Click Next to proceed.

connect dropbox (step 5)

Finally, enter an identifying name for the new Dropbox destination, and click Save Destination to complete the connection process.

connect dropbox (step 6)

13.6.5 FTP/SFTP

Link to chapter 6

After clicking Add Destination from your Destinations tab, select FTP/SFTP in the destination modal and then click Next.

Add FTP/SFTP storage destination in Snapshot

In the 1st part of the form that appears, select the protocol required by your host – FTP or SFTP – then enter the details needed to connect to your server.

  • Host – The hostname provided by your host, for example: ftp.somesite.tld
  • Port – Defaults to 21 for FTP or 22 for SFTP. Change if a specific port is provided by your host.
  • User – The username you chose when creating your FTP account.
  • Password – The password you chose when creating your FTP account.

Add FTP/SFTP storage destination details in Snapshot

In the 2nd part of the form, you’ll specify the following information:

  • Directory Path – The location on your FTP server where you want your backups to be stored.
  • Backup Storage Limit – The maximum number of backups that will be stored before cycling out the oldest ones. For example, if you set this to 10 and run an 11th backup, the oldest one will be deleted from your FTP destination and replaced with the newest one.
  • Use Passive Mode – If you are configuring a plain FTP connection, you can set this to On if needed (default is Off). Note that this option does not appear for SFTP connections.
  • Server Timeout – Increase this for slow connections if needed.

Add FTP/SFTP storage destination details in Snapshot

Snapshot will create a folder with your site name in your specified Directory Path location, and all backups for the site will be stored there. Note that the directory path you specify must already exist on your server.

For example, if you set the Directory Path to the root of your WordPress install, the backup location will be created there. Ideally, you would store backups outside of your WordPress install or on a different server though; we have just provided this example as an illustration.

Example location of FTP backup destination in Snapshot

Note that if you use the same location as the Snapshot FTP destination for multiple sites, each site will have its own folder with the corresponding site name.

When you’ve entered all the information, click the Test Connection button. You should see a message appear at the top of the modal to confirm the connection is successful.

Notice of successful FTP connection in Snapshot

Click Next, and enter a Name for your destination so you can easily identify it. Then click Save Destination to finish.

Name your FTP connection in Snapshot

The Settings screen is where you will find your Snapshot API Key, Site ID, options to manage what happens to content if Snapshot is deleted, and gives you the ability to reset your plugin settings.

13.7.1 General

Link to chapter 7

The General tab is basic information about your Snapshot connection, including your Snapshot API Key that connects to your cloud storage and your website ID.

Snapshot API Key

This unique key is used to connect Snapshot on your site with WPMU DEV cloud storage. Click the copy button to copy the Snapshot API key to your clipboard if needed.

WPMU DEV API key in Snapshot 4.0

Site ID

This is your website’s WPMU DEV ID. Click the copy button to copy the Snapshot API key to your clipboard if needed.

WPMU DEV site ID in Snapshot 4.0

13.7.2 Configs

Link to chapter 7

The configs module allows you to save your Snapshot configurations and apply them to your current site or any of your other sites in just a few clicks.

To help you get started, we provide a Basic Config denoted with a blue checkmark. It includes the recommended settings that are ideal for fresh installations. Applying the Basic Config will configure Snapshot as follows:

Save a Configuration

To save your current configuration, click Save Config.

Save a new config in Snapshot

Then, enter the name and optional description you want to use to identify your configuration and click Save or click Cancel to exit without saving.

Save a config in Snapshot

You can save an unlimited number of configurations so there is no need to be frugal with how many configurations you save for your sites. All configurations will be listed alphabetically according to the names you set.

If you want to view more information about your saved configuration, click the arrow to reveal a list showing you which modules are active for that configuration.

Snapshot config details

To make changes to a saved configuration, click the gear icon. The available actions are:

  • Apply – Apply the saved configuration to this Snapshot installation.
  • Download – Download the saved configuration as a .json file.
  • Name & Description – Edit the name and description for the saved configuration.
  • Delete – Permanently delete the saved configuration.

Config management options in Snapshot

Apply a Configuration

If you have downloaded a configuration from another site and you want to apply it to your current one, click Upload at the top of the Configs screen, and select the relevant .json file from your computer. Snapshot will import your settings and add the imported config to your list of Preset Configs.

Upload a config in Snapshot

You will be asked to confirm the configuration application to the site. Click Apply once again to follow through with applying the chosen configuration or click Cancel to exit without changing any of your current Snapshot settings.

Apply a config in Snapshot

You can also apply any existing config to your site by clicking on the Apply button next to the gear icon, or by clicking on the gear icon and then selecting Apply from the options menu.

Apply a config in Snapshot

IMPORTANT

If the storage region in the config you select is different than the one you have currently set in Snapshot Backups > Settings, applying the config will delete all existing backups. An alert will appear in the confirmation modal to remind you of this.
Snapshot configs region change warning

Sync with the Hub

Snapshot configurations will automatically be synced with the Hub. Synced configs can be accessed and applied directly from the Config or Backups modules in the Hub, or from the Snapshot installation of any of your sites.

If a new config created in the Hub doesn’t appear immediately in the Snapshot Settings module, click Re-check to get the updated list to refresh your data.

Sync config data from Snapshot with your Hub

Exceptions

It’s important to note that the following settings & options cannot be exported or imported from one site to another with a custom config as they must be configured individually on each site:

  • Destinations – Any Destinations you may have set up will not be included in the config, and any existing destinations will not be affected when you apply a config to a site.

13.7.3 Data & Settings

Link to chapter 7

The Data & Settings tab is where you manage how Snapshot stores and handles information created by the plugin.

Uninstall

The Uninstall module allows you to configure what you do with backups when Snapshot is uninstalled. You can choose to either Keep or Remove backups.

Be sure and click the “Save Changes” button after making changes.

Uninstall options in Snapshot 4.0

Note: Selecting the Remove option here will not restore the default storage limit nor will it delete your connected destinations. Please be sure to either make those changes manually or use the Reset Settings option below before uninstalling the plugin.

Delete Logs

If you need to delete the backup logs from your server, click the Delete button here, and confirm the action in the modal that pops open.

Delete Snapshot logs

Reset Settings

Use the Reset button in the Reset Settings module to roll back to default Snapshot settings.

Reset settings in Snapshot 4.0

NOTE:

The Reset Settings option will instantly reset all settings back to their defaults, and remove any destinations you have active. It will not delete existing backups though.

This module gives you direct access to Snapshot tutorials that may be extremely beneficial in helping you get the most out of the plugin. Click on any of the articles to read the full blog post or click View All to view all WPMU DEV tutorials.

Snapshot Tutorial screen

13.9 Special Notes about Snapshot 4.0

Copy chapter anchor to clipboard
  • For Snapshot 4.0 to work, your site needs to be connected to the Hub via WPMU DEV Dashboard.
Using The Hub With Snapshot

Keeping your site fully backed up and secure has never been easier with The Hub and Snapshot working together. For more information, check out our blog on Keeping Your WordPress Sites Fully Backed-up with Snapshot and The Hub.

  • Version 4 requires your website to be publicly accessible on the internet. Snapshot version 4 will not have a backup to local feature. This is by design, and there is not a plan to add this feature.
  • Integration of third-party storage destinations is in active development. Currently, Google Drive, Amazon S3 (and S3 Compatible providers like Backblaze), Dropbox and FTP/SFTP are included.
  • Partial backups (i.e. your theme only) are planned for a later release.
  • Snapshot begins iterating files at the WP root. Everything at that level and beyond, is iterated and included in the backup. Example: If your website has an abc/public_html/wp-config.php, an abc/public_html/exampleA path will be included in the backup. An abc/exampleB file path will not be included the backup.
  • Snapshot will backup any file added to your filesystem no matter how it was added – whether uploaded through the WP admin page, FTP/SFTP, SSH, or another method. If a file exists on the server, it will be iterated and included in the backup.
  • Snapshot does not currently have support for websites on a host using the Windows operating system.
  • If you are hosting with Siteground, please ensure you are using their Standard PHP mode, not Ultrafast PHP, which imposes performance limits that prevent Snapshot backups from completing.
  • PHP version requirement: 7.0 or above.

13.10 Incremental Backups

Copy chapter anchor to clipboard

Snapshot cloud backups are incremental. This means the only time Snapshot iterates over all files and db tables is the very first backup (unless a site is changed drastically between backups). The first backup in each site (manual or scheduled) is a full-site backup. We call that the base backup. Note that if an existing backup schedule is modified, a new base backup will be taken. All later backups — both scheduled and manual — are incremental backups, and understanding what that means is important.

In simplest terms, an incremental backup copies and stores only data that has been changed since the last backup. When you look at your backup list and see multiple backups created during the past several days, you are not looking at multiple copies of your full site, but rather the incremental changes that have been backed up since the last full backup.

Incremental backups are superior to traditional backups in a number of ways; perhaps most importantly, they are small and fast. This allows you to backup your site more frequently.

Example: A 500MB site was backed up last night and today you added 5MB of data. You want to protect the new data, but why backup the entire site when 99% of its data hasn’t changed? An incremental backup only includes the new data, will have the smallest possible impact on your storage capacity, has a lower impact on server load, and is much faster.

When a backup is restored or downloaded, these incremental backups are merged with the full backup (base backup) to produce an up-to-date copy of the site. You can download the exported up-to-date backup from the Backups page and also from the Hub.

As noted above, Snapshot has a 30-day backup rotation schedule and a 50-day time to expiry. When the oldest backup is removed from our storage, Snapshot automatically converts the next oldest backup to the new base backup. No action is required on your part.

What will happen to my current backups?

Managed backups

Upgrading to Snapshot 4 will have no impact on the managed backups we automatically create for our members. However, upgrading to Snapshot 4 will impact any additional backups members may have created with previous versions of Snapshot, as noted below.

Snapshot backups

Snapshot 4 is not simply an update of the current version, but an entirely new and improved plugin, so installing 4 will not replace a previous version currently active on a site. In fact, both versions can be active on the same site at the same time, with the following caveats:

  • Snapshot 4 cannot be used to restore backups created with a previous version and vice versa.
  • Snapshot backups stored locally–on your site’s WPMU DEV server–are not deleted when 4 is installed, but are deleted and unrecoverable when v3 is uninstalled. If a site has no locally-stored Snapshot backups, v3 will be automatically uninstalled when v4 is activated. If local Snapshot backups do exist, members will be given the option to leave v3 installed and active.
  • For the time being, v3 will continue to work independently of v4, but at some point in the future, this may cease to be true.
  • Snapshots created with v3 then uploaded to a third-party provider or downloaded to your computer cannot be uploaded and restored with v4. Once v3 has been uninstalled, these backups can only be restored manually. See our Manual Restore Instructions for guidance.

Are destinations still available?

Yes, Snapshot v4 includes support for the following destinations. See the Destinations chapter above for details.

  • Amazon S3 (and S3 Compatible Storage)
  • Google Drive
  • Dropbox
  • FTP/SFTP

Note however that if you have uploaded backups to 3rd-party destinations that were created with v3, they cannot be restored with v4. Once v3 has been uninstalled, those backups can only be restored manually. See our Manual Restore Instructions for guidance.

Is Snapshot 4 compatible with WordPress multisite?

Yes! Snapshot 4 is completely compatible with WordPress multisite installations, so you can be sure your entire network is covered.

Does Snapshot 4 support subsite backups?

The initial release of Snapshot 4 does not support subsite backups, although this feature will be considered for future releases. Currently, you can create and restore backups for the entire network.

Does Snapshot 4 support partial backups?

The initial release of Snapshot 4 does not support partial backups, although this feature is slated for a future release.

Do I have to update to PHP 7.0 or higher?

Yes. Snapshot 4 requires PHP 7.0 or higher. If you are running an earlier version of PHP and do not wish to update to 7.0 or higher, you should not upgrade to Snapshot 4.

Does Snapshot 4 support white label?

Yes, Snapshot 4 can be white labeled via the features found in WPMU DEV Dashboard > White Label.

Can I download backups directly?

Yes, after you click “Download” we’ll send you a secure download link via email to your WPMU DEV account email address.

Can I change the email where backups are sent?

Snapshot 4 does not currently support the option to change the email account your backups will be sent to – but rest assured this feature is coming in a future release.

Can I store my backups locally?

Yes. With the FTP/SFTP destination, backups can be stored locally.

Where are my backups specifically stored?

Snapshot 4 lets you choose between two data centers located in the United States (east N. Virginia) or in Europe (Ireland).

Can I use Snapshot 4 to migrate my site?

Snapshot 4 was specifically created to be a backup plugin. For site migration we’d highly recommend checking out our Shipper Pro plugin.

How are my Snapshot backups secured?

The WPMU DEV Cloud Backups are protected by server-side encryption. When a backup file is saved, it is encrypted at the object level and decrypted for you when you access it through the Hub or via the plugin’s back end.

Our awesome support team is always on call, should you need any help. However, sometimes it is helpful to troubleshoot issues yourself first. Below is a list of some known troubleshooting cases and their appropriate responses to help you along.

If you require any assistance, or if the issue you’re having is not covered here, don’t hesitate to contact our 24/7 live support.

How to Edit Your wp-config and .htaccess Files

Many of the solutions to the issues mentioned in this section will require you to access your wp-config or .htaccess file. If you are new to making adjustments to these files, we recommend reading Editing Your WordPress wp-config File and Editing Your .htaccess File for more information.

13.12.1 Backup Failed

Link to chapter 12

Insufficient Storage

Message in Snapshot log: snapshot_failed_storage_limit

Error: snapshot_failed_storage_limit

If you receive the snapshot_failed_storage_limit message, you may be out of storage on the WPMU DEV Cloud. In these cases, try to free up some space for the new backup or consider upgrading your WPMU DEV Cloud storage.

File Error

Message in Snapshot log: snapshot_failed_FetchFileslist

Error: snapshot_failed_FetchFileslist

Another possible issue for a failed backup is the snapshot_failed_FetchFileslist error. To fix this, follow these steps:

Step 1: Add define('SNAPSHOT4_FILELIST_LOG_VERBOSE', true); to the wp-config.php file right above the *That's all, stop editing! Happy publishing* line.

Step 2: Run a manual backup and check the log file to see where the backup failed. Exclude the reported file or folder.

You may also need to increase the memory limit and execution time to these values:

max_execution_time = 600
memory_limit = 512M

This can be added to your php.ini.

Adjusting PHP Limits

Sometimes the standard WordPress configuration doesn’t meet the standards required by your site. With a few tweaks, you could aid some of the errors that you may be experiencing. Read our blog on how to  Increase the Maximum Upload and PHP Memory Limit for more information.

Large File

Message in Snapshot log: snapshot_failed_SiteNotRespondedZipstreamError

Error: snapshot_failed_SiteNotRespondedZipstreamError

If you receive the snapshot_failed_SiteNotRespondedZipstreamError error, try the following options to resolve the issue.

Option 1

Try increasing the memory limit and execution time to these values:

max_execution_time = 600
memory_limit = 512M

This can be added to your php.ini.

Option 2

Step 1: Add define( 'SNAPSHOT4_CHUNKED_ZIPSTREAMING_LARGE', true ); to the wp-config.php file right above the *That's all, stop editing! Happy publishing* line.

Step 2: Run a new backup.

Option 3

Message in Snapshot log: snapshot_failed_SiteNotRespondedLargeFileError

Error: snapshot_failed_SiteNotRespondedLargeFileError

Step 1: Add define('SNAPSHOT4_FILE_ZIPSTREAM_LOG_VERBOSE', true); to the wp-config.php file right above the *That's all, stop editing! Happy publishing* line.

Step 2: Run a manual backup and check the log file to see where the backup fails. Exclude the reported file or folder and run a new backup.

File Renamed / Deleted

Message in Snapshot log: snapshot_failed_ZipstreamFileMissing

Error: snapshot_failed_ZipstreamFileMissing

Your backup may fail while attempting to send files to our API if a file is renamed or deleted during the backup process. If this happens, follow these steps:

  1. Add define('SNAPSHOT4_ZIPSTREAM_FLUSH_BUFFER', true); to your site’s wp-config.php file right above the *That's all, stop editing! Happy publishing* line.
  2. Run another backup.
  3. Check the log file for any folder(s) that contain files that are rapidly changing and exclude the folder(s) from subsequent backups.

Resource Limit

Message in Snapshot log: snapshot_failed_SiteNotRespondedError

Error: snapshot_failed_SiteNotRespondedError

If your backup fails with the snapshot_failed_SiteNotRespondedError error, it could be because you have reached your resources limit. The solution to this is to increase the memory limit and execution time, as seen below:

max_execution_time = 600
memory_limit = 512M

This can be added to your php.ini.

Nonce Desynchronization

Message in Snapshot log: snapshot_failed_nonce_failed

Error: snapshot_failed_nonce_failed

This error occurs due to desynchronization with the timestamp in the nonce saved in the database. If you receive this error message, you can resolve the issue by manually deleting the nonce using phpMyAdmin.

If your site is hosted with WPMU DEV, your database can be easily accessed from The Hub. First, navigate to your site’s Hosting tab and click Tools.

The tools menu on the Hosting screen

Then, click Manage Database to open phpMyAdmin.

Manage database from the Hub

Externally Hosted Sites

If your site is hosted externally, your webhost’s control panel may have phpMyAdmin pre-installed. Check out this article from WordPress for more information about phpMyAdmin.

In phpMyAdmin, navigate to and select the _options table.

Select the options table in phpMyAdmin

Search for or navigate to the entry with the option_name value wdp_un_hub_nonce, and then click Delete to delete the nonce.

Delete the nonce in phpMyAdmin

In the Snapshot interface, run another backup.

Output Buffer Stuck

On some hosts, with the default configuration, you may experience a snapshot_failed_SiteNotRespondedError error. In this case, it may be due to a problem with the output buffer which can be fixed by switching the configuration to flush the output buffer after each zipstream write. Do this by following these steps:

Step 1: Add define('SNAPSHOT4_ZIPSTREAM_FLUSH_BUFFER', true); to the wp-config.php file right above the *That's all, stop editing! Happy publishing* line.

Step 2: Run the backup again.

Server Resources

Message in Snapshot log: snapshot_failed_genericError

Error: snapshot_failed_genericError

Your backup may fail due to limited server resources. If this happens, try running another backup.

API Connection

Message in Snapshot log: snapshot_failed_HubInfoRespondedInvalidURI

Error: snapshot_failed_HubInfoRespondedInvalidURI

Your backup may fail due to the API connection with The Hub. If this happens, try running another backup.

Table Error

Message in Snapshot log: snapshot_failed_Wrapper_DBlistFetch

Error: snapshot_failed_Wrapper_DBlistFetch

Your backup may fail due to a problem iterating the database’s tables and building the table list. If this happens, try increasing the memory limit and execution time as follows:

max_execution_time = 600
memory_limit = 512M

This can be added to your site’s php.ini file.

Large Table(s)

Message in Snapshot log: snapshot_failed_TooLargeTableHanged

Error: snapshot_failed_TooLargeTableHanged

Your backup may fail while backing up a large table. If this happens, check the logs to identify the table in question, and then contact our support team to exclude the table from subsequent backups (if necessary).

Table Not Sent

Message in Snapshot log: snapshot_failed_Wrapper_TableZipstream

Error: snapshot_failed_Wrapper_TableZipstream

Your backup may fail while attempting to send a database table to our API. If this happens, try increasing the memory limit and execution time as follows:

max_execution_time = 600
memory_limit = 512M

This can be added to your site’s php.ini file.

Other

Message in Snapshot log: snapshot_failed_UnknownError

Error: snapshot_failed_UnknownError

Your backup may fail for some other unknown reason. If this happens, first try running another backup, and then contact our support team if the issue persists.

13.12.2 Backup Stuck

Link to chapter 12

IP Not Allowlisted

If you experience your backup being stuck at 0% with no log, it could be because our IPs are not allowlisted on your site. This can be addressed by adding our IPs to your allowlist:

35.157.144.199
34.196.51.17
18.204.159.253
54.227.51.40

Alternatively, if you are a member on our hosting, there could be a large queue and your backup will process ASAP.

Number of Files Too Large

If your backup is getting stuck at 13-14%, it could be related to having too many large files. These are often cached files and backup files from 3rd party plugins. To fix this, use your preferred FTP client to find your cache folder. Add this folder URL to your Global file exclusions field in the Snapshot Pro>Backups>Settings tab. Once this has been added, you can rerun the manual backup.

Easily Manage Your Files

Did you know that our hosting tools include a quick-access File Manager, straight from the Hub? No need for 3rd party FTP clients, just open the File Manager and start editing.

Zipstream Stuck

Backups that get stuck at 25% could be because of the zipstream getting stuck for small chunks of a large number of files. This can be helped by using your preferred FTP client to find your cache folder. Add this folder URL to your Global file exclusions field in the Snapshot Pro>Backups>Settings tab. Once this has been added, you can rerun the manual backup.

Large Files

Another reason that a backup may get stuck is because of large files. In this case, you can follow these steps:
Step 1: Add define( 'SNAPSHOT4_CHUNKED_ZIPSTREAMING_LARGE', true ); to the wp-config.php file right above the *That's all, stop editing! Happy publishing* line.
Step 2: Run the backup again

13.12.3 Backup Email Not Received

Link to chapter 12

WordPress Failed to Send Email

When the download backup email is not received, it is likely because your WordPress setup failed to send the email. This can usually be solved by installing and setting up an SMTP plugin.

13.12.4 API Connection Not Established

Link to chapter 12

IP Not Allowlisted

If you are struggling to establish a connection with the API, it may be an issue with our IPs. In a case like this, allowlist our IPs below and retry the connection.

35.157.144.199
34.196.51.17
18.204.159.253
54.227.51.40

Inactive Membership

Issues with establishing a connection with the API could be due to a problem with your membership status in the Hub. Be sure to verify your membership and ensure that it is active. If issues persist, contact our Support team who can check if there are any problems with your account.