- Fix: Larger backups at Google Drive don't complete
- Fix: Restoring from older snapshot versions fails
- Fix: Can't edit/update Destination settings
- Fix: Dashboard Destinations list not aligned correctly
- Add: Snapshot is not working with Google Team Drives
- Fix: Larger backups at Google Drive don't complete
- Fix: Restoring from older snapshot versions fails
- Fix: Can't edit/update Destination settings
- Fix: Dashboard Destinations list not aligned correctly
- Add: Snapshot is not working with Google Team Drives
- Add: Specify the backup type (Managed, Automate, Local)
- Improve: Apply coding standards
- Improve: Clean up old UI
- Fix: Pagination in Snapshots screen is broken after a Snapshot is deleted
- Fix: Scheduled backups are not performed when site admin is moved
- Fix: Files are not uploaded to Google Drive on some hosts
- Fix: Error in Managed Backup screen with specific time zones
- Fix: Error on snapshots in php 5.2
- Fix: Invalid link at WP admin top bar
- Fix: Regular snapshots limit
- Fix: Warning appears in logs when backup is created
- Fix: Snapshot says Gzip instead of Zip
- Add: GDPR - export user personal data
- Add: GDPR - erase user personal data
- Add: GDPR - insert plugin information to default "Private Policy" page
- Fix: Activating Snapshot shows 200 OK message
- Fix: PHP Warning with database backup using PHP v7.2
- Fix: Initial application of coding standards
- Fix: Scheduling too far in the future
- Fix: Disperse cron weekday/time starts when scheduling is not set
- Fix: Disperse start backup scheduling, auto reschedule
- Add: Recycle older snapshots on third party destinations
- Add: backups percentage communication between plugin and the Hub
- Add: Hub-initiated backup delete handler
- Fix: Upload status doesn't update in real time
- Fix: Debug info in admin
- Fix: Long Name overlaps with Type Icons
- Fix: Destination setup page for Amazon S3 is not showing options
- Fix: Google Drive Custom Path macro expansion
- Fix: Improvement to avoid timeout on large folders
- Fix: Number of snapshots to restore are limited to 6
- Fix: Not possible to set schedule time and day when WP Cron is disabled
- Fix: Total size of archives does not equal the total cloud storage used
- Fix: No message after clicking Restore Now
- Fix: MS Edge, storage used indicator is not positioned properly
- Fix: Reactivate managed backup without resetting key
- Fix: Success Message in Restoring files
- Fix: Warning if the SQL charset in shapshot and target are not same
- Fix: Update phpsec external library
- Fix: Update key in reset dialog save
- Add: one-click setup
- Add: optional backup via system calls
- Add: separate user- and automate- initiated backups
- Fix: allow extra chars in FTP passwords
- Fix: restore media issues on multisite
- Fix: rendering issues
- Fix: alignment issues
- Fix: PHP notice in snapshot restore
- Fix: scroll bar on log viewer window
- Fix: missing items when editing snapshot
- Fix: Backups now works properly when requested remotely from Automate (Hub)
- Fix: Re-added change destination directory feature.
- Fix: Minor UI error on dashbord and snapshot progress bar.
- Fix: Minor error on PHP 5.4.
- New: Snapshot now uses V2 of Dropbox API.
- New: Dropbox authentication uses OAuth 2 instead of OAuth 1, fallback system has been created for old destinations.
- Dropbox destination now requires PHP 5.5 or newer.
- Fix: Remove open basedir from Snapshot system check.
- Fix: Fatal error when restoring snapshot on PHP 7.0
- Fix: Remove PHP notice when restoring a Snapshot.
- Fix: AWS Destination not displaying AWS Secret Access Key value.
- Fix: AWS Destination not saving/updating Storage type/File permissions and Directory values.
- New: The Snapshot name is included in the generated archive filename, for easier identification
- New: An error message is displayed if uploading a Snapshot to a remote destination fails
- New: Snapshot filenames are displayed when viewing the Snapshot's information
- New: Display a single Snapshot overview after editing a Snapshot, rather than overview of all Snapshots
- Restored: Snapshots can be created from and restored to a specific subsite on WordPress multisite
- Fix: Minor UI enhancements and fixes
- Fix: Show log button not working when restoring a snapshot
- Fix: Prevent the storage limit for Managed Backups from being set to a negative number, and allow it to be set to 0 for unlimited
- Fix: Add link to the back button on the snapshot restore page
- Fix: Snapshot scheduling information not always saving correctly when editing Snapshot
- Fix: Restore hidden Snapshot settings.
- New: Display a message when backup log is empty.
- Minor UI improvements.
- Fix: Redirection bug to Snapshot dashboard, activation pathways restored.
- Fix: Redirections for all old snapshot URLs.
- Fix: Prevent backup progress bar from getting more than 100% in any case.
- Fix: PHP 7.1 errors.
- Fix: Some typos.
- Meet the brand new Snapshot Pro! We’ve given the admin interface a refresh and updated the overall user experience. Setting up and configuring your Snapshots & Backups has never been faster.
- - New: Welcome page to help configure your first backup in just a few seconds.
- - New: All-in-one dashboard.
- - New: Summary panel with last Snapshots/Backups status.
- - New: Clean Snapshots listing table with awesome filters.
- - New: Simple Snapshots creation wizard.
- - New: Awesome pre-flight requirements checker to make sure backups are going to run smoothly.
- - New: Less is better, no more confusing frequency settings, now you can choose run daily, weekly, monthly or once off.
- - New: Clean destinations listing table.
- - New: Easier managed backup activation flow.
- - New: User friendly Managed backup creation process with a brand new progress bar and log system.
- - New: A handy dashboard page for Managed Backups to manage existing backups and global backup settings.
- - New: Easy and clear one page for all plugin settings.
- - Fix: Multi-line manifest data parsing.
- - Fix: Mal-formatted JSON error handling.
- - Fix: Responsive issue with log watching link.
- - Fix: Better managed backups in restricted environments handling.
- Fix: Ensure managed backup pings service endpoint on completion
- New: large file detection in managed backups.
- Fix: updated remote API parameters.
- Fix: minor string fixes.
- New: add managed backups implicit logging.
- New: add managed backups log viewer.
- New: auto-expand failed preflight checks for restore.
- Fix: improve error conditions tracking.
- Fix: some minor markup fixes.
- Fix: improve start event (re)scheduling.
- Fix: issue with snapshot root folders change.
- Fix: improve the restore handler and script error reporting
- Fix: potential issues with backup rotation.
- New: Beta release of full managed cloud backups!
- New: add option to remove local snapshots after uploading
- Fix: protocol check for FTP destination
- Fix: update message string
- Fix: add option to store local archives
- Fixed PHP7 split deprecated
- Fixed plugin cannot be uninstalled
- Fixed Snapshot time fields disappearing
- Updated Google Destination instructions
- Various code improvements for Snapshot 2.5
- Added support to backup mu-plugins
- Fixed some issues with scheduling.
- Fixed support for WP_PLUGIN_DIR & WP_CONTENT_DIR
- Fixed listing Amazon S3 Buckets
- Removed GreenQloud destination
- Fixed issue with viewing logs timing out in FireFox.
- Added additional security prompts for Snapshot settings when backups folder can be accessed publicly.
- Improved restoring of sites on multisite installations where sites may be empty (e.g. restoring primary site to a new network).
- Fixed messages in translation file that were blocked from being uploaded.
- Fixed redirection issues.
- Security Update: Fixes possible WordPress XSS bug.
- == 220.127.116.11 ==
- - Fixed issue when importing a snapshot on another site (*_options table issue)
- Critical update:
- - Fixed a number of issues where using Snapshot together with Domain Mapping plugin.
- - Multisites improvements
- * Path names now resolve correctly and restoring is improved.
- * Improved restoring into another site (a new site within the network must be created first before doing this)
- - NOTE: If restoring a site on a folder based multisite and it appears that your links are broken,
- you will need to go to the site's Settings > Permalinks and click on 'Save Changes'.
- Fixed issue where WordPress core files have been placed in a different location as per http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory
- Fixed issue preventing some users to upgrade.
- Updated Google API client for Google Drive integration. Not a bad idea to re-authorize Google Drive destinations.
- Fixed issue with file paths causing problems with networks in sub-directories.
- Fixed issue with paths causing issue with Domain Mapping plugin.
- Fixed critical bug with 'local server' as the destination. Automatic backup restored.
- Corrected reported issues where media files on Windows server was not being included in archive creation.
- Corrected PHP warning for non-initialized variable shown sometimes on the restore screen.
- Corrected issues with the restore looping logic user for large tables.
- Changes to Google Drive destination logic. Moved loading of external Google SDK into destination init() function of destination class. See if this gets us past the reported library conflicts.
- Modified priority for 'cron_schedules' filter registration used within Snapshot to register custom backup intervals for WP_Cron. This is to help circumvent issues when other plugins tend to ignore the proper use of filters.
- Corrected reported issue where with one destination defined could not select Dropbox sync via snapshot files option.
- Added wrappers to prevent loading Google SDK classes if already loaded by another plugin.
- Added optional define 'WPMUDEV_SNAPSHOT_DESTINATIONS_EXCLUDE' which can be added to the wp-config.php to prevent certain destinations from being loaded. Possible values are SnapshotDestinationDropbox, SnapshotDestinationGoogleDrive, SnapshotDestinationAWS, SnapshotDestinationFTP, SnapshotDestinationGreenQloud. Multiple destinations can be included as a comma separated value.
- Added support for Google Drive as a destination.
- Added support for generic AWS/S3 type system like DreamObjects
- Corrected stray comma on restore SQL.
- Corrected reported issue where the site lookup was not functioning properly on the restore panel when using site ID under.
- Correctes reported issue where if the archive was in a sub-directory on the local server the restore init failed.
- Updated import panel to allow import or archives local server from alternate locations.
- Added support logic when using non-default destination directories. If move of the temp archive to final destination fails then the archive is moved to default snapshot archives folder instead of simply aborting.
- Corrected issue with WPEngine and Dropbox include paths for OAuth.
- Corrected to restore logic where non-WordPress tables are included.
- Reworked restore logic for global tables (users & usermeta) to be setup in segments like other tables.
- Corrected issue when restoring global tables when table has zero records.
- Added debug output on Dropbox chunked uploads to write to snapshot process log for investigation of reported issues.
- Correction to typo. get_siteurl() should be get_site_url()
- Update to migration logic. Added support logic to correct old style (pre-MU 3.5) image URLs stores in posts when restoring to new post MU 3.5 site. In pre-MU 3.5 the image URLs were formatted such http://www.site.com/files/2013/12/image.jpg while in 3.5 and new installs the image URLs are http://www.site.com/wp-content/uploads//2013/12/image.jpg. Prior versions of Snapshot only update the domain part of the URL. Reminder Migration logic is still considered beta.
- Testing for WordPress 3.8
- Update to WPMU DEV Dashboard Notifications library.
- Fixed reported issue on files restore. When selecting the 'Restore all files' option in some cases none or not all files were being restored.
- Fixed reported issue where blog lookup by ID was no longer functioning under Multi-domain configurations.
- Corrected reported issue of snapshot handing when ONLY Files to be included in archive and there are no files to add to the archive. The result is an empty archive containing only the manifest file.
- Under Multisite added support logic for Domain Mapper when selecting which sub-site to backup. Users can now enter full mapped domain instead of just the local sub-domain.
- Corrected PHP Strict Redefining already defined constructor for class error by moving old-style PHP4 class constructor function below PHP5 __construct() function.
- Corrected reported issue where files were not being included in manual archives when selecting 'common files'.
- Changed logic for handling files when building zip archives to cut down on zip archive overhead.
- Removed legacy support for hp sessions. Now using own containers to hold temporary variables.
- Updated instructions on Import page to help with any confusion between an import and restore
- Fixed some typos on labels.
- Corrected reported issue causing 'run now' option to not be available on regular WordPress sites.
- Corrected some PHP Notices and Warnings
- Added migration logic. This is still considered beta. Migration types supported are Regular to Multisite, Multisite to Multisite (same system or different), Multisite to regular. Using the migration logic you can even change the site URL. Note the destination blog must already be setup and working within WordPress.
- Added backup logic to include users and usermeta data related to the blog being archived. Only user who's primary blog is the archive blog.
- Rewrite of the import logic. You can now pull in external files from public URL instead of needing to upload the archive to your server first.
- Code cleanup on some of the archive logic.
- Corrected logic to Zip Compression setting on archive restore.
- Removed debug output.
- Fixed issue with reported phantom table queries when backup for main site within Multisite.
- Added support for scheduling backups when WP_CRON is disabled.
- Added output on System Info for OpenSSL installed and version.
- Added output on System Info for cURL installed, version and protocols supported.
- Fixed issue with blob lookup when using Multisite subdirectories
- Correction to FTP destination logic to include ftp_ssl_connect function which allows support for FTP with TSL/SSL
- Modifications to FTP destination screen to replace SSL dropdown with protocol option showing FTP, SFTP and FTP-ES.
- Correction to ZipArchive logic to strip off leading slashes of sql filenames which causes them to be hidden on Windows systems
- Added code to create empty file CACHEDIR.TAG at top uploads/snapshots directory to exclude snapshot archives from unix system backup tools.
- XSS prevention patches
- Correction to logic for purging local archive associated with remote destinations
- Added AWS destination region to Sydney
- Dropbox correction to filter out destination directories with multiple slashes
- Fixed issue where non-WordPress prefixed tables were not showing in tables listing
- Fixed issue with Dropbox missing slash on destination path for chunk send transactions commit.
- Fixed issue where users were using backslashes in in destination paths.
- Fixed page icon not displaying correctly on archives settings page.
- Fixed bug on archive purge when set to 1.
- Corrected issue with Dropbox reporting Bad OAuth Request
- Added some support logic to prevent abort on hosts where php_uname is disabled. The php_uname function is used for AWS Destinations library.
- Corrected issue with FTP Destination not setting timeout correctly.
- Adjusted display for Interval to not show percent transfer for all destinations.
- Cleanup some logic for setting/removing scheduled WP_CRON tasks on plugin deactivation and activation.
- Added blog lookup option on Add New Snapshot form. This replaces the previous blog dropdown used to select the backup target. Should work better for very large systems.
- Fixed but where phantom snapshot directories were being created under sub-site uploads directory tree.
- Fixed issue where Snapshot configurations are only initialized on the Network or primary site admin area.
- Added logic to support folder and file sync to Dropbox destination.
- Added logic to backup file sub-sections instead of attempting complete section. So instead of trying to submit the entire plugins folder. We are adding each plugin sub-directory, each theme sub-directory, each media year.
- Added logic to Abort currently running scheduled processes.
- Added better scheduled process locking notification.
- Added status column to main listing and archive showing Archive status and Destination count
- Added Destination/Sync progress output percentage to main listing.
- Added logic to show what is running Now and will show trailing log of process
- Added greenqloud as destination option.
- Fixed issue with new snapshot roles on plugin update.
- Added Selective Restore options. Similar to backup options. Lets you select to restore certain tables, File sets (Theme, Plugins, Media).
- Also on Restore made process more efficient by restoring sections instead of individual files per call. http://premium.wpmudev.org/forums/topic/snapshot-takes-40-minutes-to-restore-files
- Correct issue with Windows paths http://premium.wpmudev.org/forums/topic/site-restore-not-working
- Added role capabilities manage_snapshots_items, manage_snapshots_destinations, manage_snapshots_settings to allow fine tune of who can access Snapshot. This is Single WordPress sonly. On Multisite this is still only Network Admins. http://premium.wpmudev.org/forums/topic/snapshot-features-requests#post-309939
- Resolved http://premium.wpmudev.org/forums/topic/save-and-run-immediately-does-not-seem-to-work
- Resolved http://premium.wpmudev.org/forums/topic/changes-to-schedule-do-not-actually-change-schedule
- Resolved http://premium.wpmudev.org/forums/topic/delete-destination-bug
- Resolved http://premium.wpmudev.org/forums/topic/not-backing-up-to-s3-as-configured
- Added scheduling logic to allow specifying specific start time and interval to scheduling processing
- Added display logic to show when WP_CRON has been disabled by other plugins or in wp-config
- Corrected OAuth logic used in Dropbox to not intercept common query strings for other Dropbox plugins.
- Corrected issue with Amazon (AWS) remote destination when server is running open_basedir http://premium.wpmudev.org/forums/topic/plugin-doesnt-work-on-debian-squeeze-and-ispconfig-3
- New AWS library used that will handle non-US connections seamlessly.
- For Dropbox destinations moved include for Dropbox ZPI to be used only when needed instead of loading globally. Will reduce initial memory.
- Wrapper on session_start calls to check for existing session id.
- Fixed issue with enquing scripts that was effecting HTTPS on admin.
- Fixed issue on non-WP table selection for non-Multisite systems
- Corrected issue where other plugins are sub-classing $wpdb and snapshot assumed it was running under Multi-DB
- Corrected bad href on cancel button when adding a Destination http://premium.wpmudev.org/forums/topic/rogue-code-appearing-in-snapshot
- Corrected to logic when determining tables associated with blog. http://premium.wpmudev.org/forums/topic/snapshot-table-confusion
- Corrected issue on FTP Destination when using destination directory http://premium.wpmudev.org/forums/topic/snapshot-fails-to-put
- Corrected issue with Multi-DB integration. Now correctly selecting other databases. Works on restore as well. http://premium.wpmudev.org/forums/topic/snapshot-isnt-doing-anything
- Correct issue which was causing the previous plugin version options data not to be properly loaded on upgrades.
- Modified File archive logic. Previous logic added a file at a time to zip archive. This is too costly. Now adding files by section: Media, Plugins, Themes, etc.
- Added size of archive file to all listing panels. Added better size logic to provide better kb, M, G, etc. size display.
- Added Settings section for global file excludes. Previously excludes were only at snapshot level.
- Added Settings section for easier control or error abort and logging when performing backup or restores.
- Added WP version and WP database version to archive manifest information.
- Change global object to wpmudev_snapshot for branding and prevent collision with other plugins.
- Changed all public functions to be prefixed with 'snapshot_'.
- Wrapped all class with 'class_exists' code to prevent collisions.
- Updated inline Settings documentation and field instructions.
- Corrected issue displaying non-WordPress tables under WordPress single running BuddyPress
- Corrected label on main Snapshots table listing for core and non-core tables selected.
- Added last archive file size to the main Snapshots row output.
- Correct URL/Path issue on Dropbox authorization when running WordPress in sub-directory. Thanks Arun!
- Added clarification to the Remote Destination form fields on Dropbox, AWS and FTP.
- Support for files
- Support for remote destinations: FTP, Dropbox, Amazon S3
- Better support for large file handling
- Support for alternate destination folder on local server and remote destination
- Better WP cron management
- Support for exclusion of file.
- Support for custom remote destinations. More on docs coming
- Better main listing screen complete with standard WP functionality for paging/filtering
- Added secondary archive screen to list all archive for a specific snapshot. Similar pattern supporting paging
- Better log view via thickbox
- Minor bug fixes. Changed for PHP 5.4.x issues with lib panel and metabox calls. Corrected Add New dropdown when Multisite installed as sub-directory instead of sub-domain.
- Resolved issues with backup/restore not working when zlib compression it turned on. http://premium.wpmudev.org/forums/topic/need-to-turn-off-zlib-compression-for-it-to-work
- Corrected error on missing function when attempting to uninstall the plugin per the support thread http://premium.wpmudev.org/forums/topic/unable-to-delete-the-plugin
- Corrected issue on restore processing causing the previous snapshot files to become missing.
- Corrected error where table names were not properly escaped.
- Added Settings panel for Memory Limit control on backup/restore processing
- Added Error Handler logic to trap PHP fatal errors to backup/restore logs
- Added date or last Snapshot to the All Snapshots Archives column information
- Corrected issue on Directory display permissions on Settings > Server Info
- Added more PHP information to 'Server Info' Settings panel. This should help support and users get at information like the PHP timeout values, etc.
- Improved logging logic for new snapshots. Entry and logs now created at start of snapshot instead of on completion. This should allow for better debugging if the table backup aborts.
- Rewrite of core backup/restore logic. Should help Improve stability for users.
- Added Scheduling for automated snapshot creation.
- Dropped the Activity log. Each Snapshot nw contains the set of all archives.
- Logging for scheduling snapshots written to physical file. Should also help for debugging.
- As part of the backup/restore data is handled in 'segments'. The Segment Size can be controlled by a user setting. The segment size is the number of rows to backup/restore per request. So a table containing 80,000 rows can be split into 10,000 row requests. Much easier than trying to do this in one request.
- Time display - When setting the WordPress timezone to UTC values the time displayed remains GMT. See comment http://premium.wpmudev.org/forums/topic/new-release-snapshot#post-181304
- ables display - As Timothy point out http://premium.wpmudev.org/wp-content/uploads/2012/02/Screen-Shot-2012-02-11-at-11.05.13.png when adding a new snapshot on the primary site under Multisite the tables listed included all table. Not those just related to the viewed site.
- Uninstall - I had started on the delete plugin uninstall hook but left it unfinished. Now properly removing snapshot files and options entry. On Multisite this delete only occurs on the primary site since the sub-sites do not really have the ability to delete a plugin. http://premium.wpmudev.org/forums/topic/install-error
- 10 Gigabyte of WPMU DEV cloud storage!
- FTP/SFTP, S3, Dropbox or Google Drive
- Backup your entire site or specific files
- Automated daily, weekly or monthly backups
- WordPress and Multisite backup
- One-click backup and restore
Have you ever made a change that broke your site, or been hacked and wished you could go back in time?
Snapshot creates full site automated and on-demand backups to both local and cloud servers.
Schedule automated backups or run Snapshot before you change a line of code, update WordPress core or activate a plugin.
Restore points make it easy to try something new and jump back in a flash if it doesn’t work.
Hosted & Convenient
Local backups are fast and convenient for quickly undoing a change, but what if your server goes down or is hacked?
Your active WPMU DEV membership gives you secure hosted backups with 10GB of storage and one-click restoration from The Hub!
Mega Storage Upgrade, Lowest Prices Guaranteed
Are you a super-user with a bunch of sites or a huge network that needs more than the included 10GB? Get more space at the lowest prices in WordPress guaranteed.
Direct to the Cloud
Redundant snapshots give your site a new kind of security. Backup to your local server, the WPMU DEV Hub and your favorite cloud services.
Destinations make it easy to save directly to Dropbox, Amazon S3, and Google Drive or by FTP and SFTP.
Backup your entire site or use the file selector to choose specific files and save space.
Store as many Snapshots as you like or use rolling backups to remove the oldest backup when a new snapshot is created.
What about Multisite?
Snapshot can backup your entire network. It’s all the features you love on a single WordPress installation…but for Multisite.
One-click, on-demand, scheduled, local, third-party and WPMU DEV cloud backups.
Best backup system for WP. More importantly, the easiest restore system too!Burton Kent
Snapshot is a great plugin for Multisite admins to create snapshots of their entire database and all sites.martin_van_dijk
Snapshot pro is the flyest WP backup utility on the planet. Snapshot makes migration to and from Multisite a breeze. Thank you very much for the wizardry.christian
Security, plugins, themes, advice, support, community, education, performance, and now backups! You can't go wrong.Amused
Again WPMUDEV proves how much they value their members! Thank you for the generous 10 GB of free storage and what appears to be, a very elegant managed backup solution.Jonathan
It’s amazing to see a company that keeps improving things in a way we can focus more on our clients and less on daily tasks.Loremar Guimaraes
I didn’t realize how easy it was to restore a site with Snapshot Pro, until one day I actually needed it. I hit restore and everything was back to normal!matt_sawyers
Browse and restore snapshots from the WordPress dashboard, the WPMU DEV Hub or even manually restore from a ZIP backup.
Label snapshots so you can quickly find a specific backup point when you need it most.
He’s Got Your Back
Your WordPress site is valuable, often the accumulation of hours of work. Even well-maintained sites crash from hosting hiccups or faulty plugins.
Protect your site’s future with Snapshot and never get caught with your site’s backend exposed again!
Because Snapshot Pro features need the WPMU DEV super servers to function, access to pro features requires an active WPMU DEV membership. For more information see the API Access section in the terms of service.
Start by reading Installing plugins section in our comprehensive WordPress and WordPress Multisite Manual if you are new to WordPress.
Once installed and activated, a new menu item will appear in your admin area.
- When Network Activated on a WordPress Multisite, go to Network Admin > Snapshots > Settings.
- When activated on a single site install of WordPress, go to Snapshots > Settings.
Configuring the Settings
We need to first configure the folder where we want these backups done. Click on Settings now.
You can customize the name of the folder here, and change it to anything you like. We’ll move the files already backed up over for you. How cool is that!!
We will then want to set how many records are backed up per request. This is titled Database Segment Size.
The Segment Size can be defined as the number of rows to backup per table per request. The Segment Size controls the backup processing when you create a new snapshot.
During the backup process, Snapshot will make a request to the server to backup each table. You can see this in the progress meters when you create a new snapshot.
In most situations this backup process will attempt to backup the table in one step. But on some server configurations the timeout is set very low or the table size is very large and prevents the backup process from finishing.
To control this, the Snapshot backup process will breakup the requests into smaller ‘chunks of work’ requested to the server.
For example, let’s say you have a table with 80,000 records. This would take more than the normal 3 minutes or less most servers allow for processing a single request. By setting the segment size to 1000, the Snapshot process will break up the table into 80 small parts. These 1000 records per request should complete within the allowed server timeout period.
The next section, Server Info, displays everything you need to know about the particular configuration of your install. This can be very useful information indeed if you ever need to contact support with any issues.
We can then set a new memory limit. Keep in mind if your database is growing in size, then you will need more PHP memory to process that. If there isn’t enough, then PHP will time out with memory errors.
The next settings area allows you to specify files or directories that will be excluded automatically from all snapshot configurations.
You can also setup exclusions specific to a single snapshot via the configuration screen (see Starting A Snapshot below). The exclude logic uses pattern matching. So instead of entering the complete server pathname for a file or directory you can use simply use the filename of parent directory.
For example to exclude the theme twentyten you could enter this one of many ways: twentyten, themes/twentyten /wp-content/themes/twentyten, /var/www/wp-content/themes/twentyten. Regular Expression are not allowed at this time.
The Error Reporting section controls how Snapshot will handle an error condition during the backup / restore processing.
There are two columns for each type of error. The ‘stop’ column controls if Snapshot will abort the current process should that type of error be reached. The ‘log’ column controls if the type of error and details will be written to the processing log. In most cases you want to set ‘stop’ for Errors only. And set ‘log’ for all.
The final section lets you select which zip compression library to use.
The zip library is used during the backup and restore processing by Snapshot.
In most cases ZipArchive is built into PHP and generally faster than PclZIP. ZipArchive uses files whereas PclZIP uses memory for temporary storage when compressing large files.
That’s it for the settings — all done.
*BETA* WPMU DEV Hosted Backups
As of the most recent release, Snapshot can now integrate with our new backup service, which will allow you to store up to 10GB of backups in our cloud. It’s very important to note that this feature is still considered to be in beta, so expect a few bugs and quirks early on. Please report any issues you find in our support forums.
Using the hosted backup system is very simple. You’ll be up and running in a few clicks. You will need to have the WPMU DEV dashboard installed, and be an active subscriber in order to use the Snapshot hosted backup service.
Start by clicking the Full Backups item in Snapshot’s admin menu tab. This will bring you to the settings page. There are only three areas to be concerned with. In the left panel, you’ll see general information about your Snapshot schedule, and a list of all your current backup files, once you’ve created some backups.
In the right panel, you’ll see a box for creating a backup schedule, and one for settings.
In the settings box, you’ll need to enter your Snapshot secret key. There’s a link that will take you to the Hub on WPMU DEV, and you’ll be shown a pop up with your Snapshot key ready to copy. You can also access this by going to the My Websites tab in your Hub, then choosing the site you’d like to add Snapshot backups to, then selecting the Backups tab.
In the schedule box, choose between daily and weekly backups, and set a time when you’d like the backup process to start.
You can select the number of backups you’d like to store remotely in our cloud, and also choose to enable logging, a feature we’ve carried over from the other destinations in Snapshot.
Once you’ve successfully created your first Snapshot backup and it’s been successfully uploaded to our cloud, you may restore it at any time, from either the Snapshot archive on your site, or from the My Websites tab in the hub.
Easy as falling off a log.
Destinations are external locations where you can store your Snapshots so they’re secure and accessible even if your server crashes.
A destination is a remote system like Amazon S3, Dropbox, SFTP or GreenQloud. Simply select the destination type, then fill in the details. When you add or edit a Snapshot you will be able to assign it a destination.
When the snapshot backup runs, the archive file will also be sent to your selected destination.
To set up a destination, simply click the Add New button next to your preferred service, and follow the directions. Go ahead and set up a destination now for the next steps.
Note for Google Drive destinations: when setting up your destination at Google Drive, you may want to double-check under APIs & Auth > Consent Screen that Email Address & Product Name are filled in, otherwise you may get an error.
Note for Amazon S3 destinations: when setting up your destination at Amazon S3, you must set “Amazon S3 Full Access” permissions in the user policy of the user you are connecting with.
Starting A Snapshot
In the Snapshot menu, click on “Add New.”
Here we will want to give our Snapshot a name. It doesn’t really matter what you call it because it’s all relative to you. You can add some notes, as well as a reminder of what you’re performing with Snapshot.
In the next section, you can select which files to include or exclude from the Snapshot.
You can choose to not include any files, include only common files, or select specific files you want to include.
You can also list additional files to exclude from this snapshot. This is handy to exclude very large files like videos that are 2G in size that you may be hosting, but know you have a backup elsewhere.
Next we will want to decide what tables to take a Snapshot of. You have 3 basic options:
- Do not include database tables in this Snapshot.
- Include all blog database tables in this archive. This will automatically include new tables.
- Include selected database tables in this Snapshot.
Selecting the 3rd option will expand the section so you can select exactly which tables you want to include. The first set of options are for the default WordPress core tables — the ones for users, usermeta, and so on.
The next set of options are for the extra tables added by themes and plugins. Any tables added by WordPress, themes, or plugins are all optional, and you can choose which ones you need!
Now we need to tell the plugin when to run & archive the backup.
When selecting the Backup Interval, please note that the Snapshot scheduling process uses the WordPress Cron (WPCron) system. It should be understood that WPCron is not precise. If you schedule a Snapshot for a specific minute of the hour, WPCron may not execute at exactly that time. WPCron relies on regular front-end traffic to your website to kickoff the processing.
You can also specify the total number of local archives to keep for this snapshot. Once the archive limit is reached, older locally stored archives will be removed.
In common cases you may want to set the backup interval to once a week. Then set the number of archives to keep to 52 which would give you a year or backups. But keep in mind on a large site this will be a lot of extra disk space required.
Finally, select where you want to store your backup.
In the Backup Destination dropdown, you can select to archive your backup locally, or choose any of the Destinations you have already set up. If you need another, simply click Add More Destinations.
You can also use the optional Directory to override or supplement the selected destination directory value.
Once you are happy with all your choices here, then all that’s left to do is to click on the “Create Snapshot” button. … So let’s do it!
You’ll then see a new screen that shows you the backup progress as it’s working.
If you need to abort the backup at any time and start over again later, simply click the Abort button that appears next to each segment as it is being backed up.
And don’t be alarmed if this takes a while or if the backup does not appear instantly. These things take time you know. ;-)
Go grab yourself a beverage whilst you wait if you wish. :-)
Once it’s done, the plugin will let you know with a friendly notice:
Where Are My Snapshots? Can I Restore Them?
You will notice in the Snapshot menu there is an option for “All Snapshots.” Click on that, and you will get a list of all the Snapshots you have already archived. It really is that easy!
As you’ll notice on the page, you can edit, run, restore or delete a backup.
You can even view which core & optional tables you backed up by clicking the corresponding link:
At the far right of each snapshot listed, you’ll find links to download the snapshot to your computer or view the archive for that particular snapshot. You can also view or download the log of all actions performed during the backup.
How awesome is all that!!
Importing a Snapshot
If you have Snapshots stored on a remote server, or have manually uploaded them to to your local folder, you must import them first so the plugin will recognize and show the archive in the All Snapshots listing.
Note that if you are importing from a remote server, the remote archive must by publicly accessible as this import process does not yet support authentication.
Once you have successfully imported your remote archive or scanned your local folder, you’ll see a success message with the import results.
If you have set up the archive to save to an alternate directory, then enter the full server path to the directory where the archive resides in the URL field.
You can now select your imported archive, or perform operations on it, from the All Snapshots page.
If you’re stuck, need some help, or have a suggestion, then get involved with the community through our forums!
See you there!
Snapshot Pro is covered by the WPMU DEV Guarantee
We guarantee that...
- Snapshot Pro will work as advertised
- You will receive 24/7 365 expert support for any problem
- If you cancel your FREE trial, you can keep Snapshot Pro
- Snapshot Pro is secure, always updated and well coded
Money back guarantee!
While you have 30 days, no obligations risk-free trial of WPMU DEV if you become a paid member and are dissatisfied with any of the above we'll refund you, no questions asked.
Snapshot Pro Features
Just like a Time Machine for your website
- 10GB of WPMU DEV cloud storage
- The Hub backup manager
- Redundant backups
- Server info quick view
- Manage memory usage
- Multisite Global file exclusions
- Size segmenting eliminates timeouts
- Scheduled backups
- Set backup interval
- Manual backup
- Multisite compatible
- Backup entire site
- Include media files
- Exclude specific files
- Annotate snapshots
- Set custom backup folders
- Downloadable log files
- Simple one-click restore
- Utilize standard WP tables
- Mirror sync
- Set number of backups to store
- Automatically remove oldest backup
- Dropbox integration
- Amazon S3 integration
- FTP and SFTP integration
- Google Drive integration
Snapshot Pro in your language
- View all