Removes the size limits on backup and restore: backups are split into volumes, the database is streamed, and both a background backup and a background restore now resume automatically if the host interrupts them, so neither file size, PHP memory, nor a host timeout caps the site size. Keep all volumes of a backup together. Includes a security fix for crafted archives. Requires WordPress 6.2+.<\/p>","0.3.1":"
Important fix: selected-folder backups now preserve plugin folder paths, so backup plugin code is included while backup archives remain excluded. Also cleans missing active plugin references after restore.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3664244,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3664244,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3664244,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3664244,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.5.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3664270,"resolution":"1","location":"assets","locale":"","width":1147,"height":736},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3665376,"resolution":"2","location":"assets","locale":"","width":1211,"height":1088},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3664270,"resolution":"3","location":"assets","locale":"","width":1138,"height":806},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3664270,"resolution":"4","location":"assets","locale":"","width":674,"height":888},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3664270,"resolution":"5","location":"assets","locale":"","width":1130,"height":1278},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3664270,"resolution":"6","location":"assets","locale":"","width":641,"height":657}},"screenshots":{"1":"Backup tab \u2014 create a full or custom backup, and download, check, restore, or delete the backups you already have.","2":"Daily Backup tab \u2014 schedule one automatic backup a day and get an email when it succeeds or fails.","3":"Restore tab \u2014 restore from an uploaded zip or from one already on the server, with automatic URL detection for migrations.","4":"Every restore is confirmed first \u2014 what will change, how to recover if it fails, and a required acknowledgement.","5":"Status tab \u2014 system readiness, storage and rollback diagnostics, and safe maintenance tools.","6":"Destructive actions ask twice \u2014 Master Reset requires both a backup acknowledgement and typing RESET."}},"plugin_section":[],"plugin_tags":[151,10718,4155,152,23756],"plugin_category":[59],"plugin_contributors":[277314],"plugin_business_model":[],"class_list":["post-332373","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-database-backup","plugin_tags-migration","plugin_tags-restore","plugin_tags-site-migration","plugin_category-utilities-and-tools","plugin_contributors-srjdev","plugin_committers-srjdev"],"banners":{"banner":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/banner-772x250.png?rev=3664244","banner_2x":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/banner-1544x500.png?rev=3664244","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/icon-128x128.png?rev=3664244","icon_2x":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/icon-256x256.png?rev=3664244","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/screenshot-1.png?rev=3664270","caption":"Backup tab \u2014 create a full or custom backup, and download, check, restore, or delete the backups you already have."},{"src":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/screenshot-2.png?rev=3665376","caption":"Daily Backup tab \u2014 schedule one automatic backup a day and get an email when it succeeds or fails."},{"src":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/screenshot-3.png?rev=3664270","caption":"Restore tab \u2014 restore from an uploaded zip or from one already on the server, with automatic URL detection for migrations."},{"src":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/screenshot-4.png?rev=3664270","caption":"Every restore is confirmed first \u2014 what will change, how to recover if it fails, and a required acknowledgement."},{"src":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/screenshot-5.png?rev=3664270","caption":"Status tab \u2014 system readiness, storage and rollback diagnostics, and safe maintenance tools."},{"src":"https:\/\/ps.w.org\/restorepilot-backup-migration\/assets\/screenshot-6.png?rev=3664270","caption":"Destructive actions ask twice \u2014 Master Reset requires both a backup acknowledgement and typing RESET."}],"raw_content":"\n
RestorePilot Backup & Migration is a straightforward backup and restore plugin for WordPress site owners, developers, and small agencies.<\/p>\n\n
It creates a downloadable backup package containing this site's WordPress database tables and, optionally, the Most backup plugins are tested by how well backups work. Restores get tested less, and that is the moment you actually need one to work.<\/p>\n\n Backup<\/strong><\/p>\n\n Restore & Migrate<\/strong><\/p>\n\n Downloads<\/strong><\/p>\n\n Scheduled backups & notifications<\/strong><\/p>\n\n Logs & diagnostics<\/strong><\/p>\n\n WP-CLI<\/strong><\/p>\n\n Security & compatibility<\/strong><\/p>\n\n This is an early release. Always test restores on a staging site before using RestorePilot on a production site.<\/p>\n\n RestorePilot creates backup files that may contain personal data from your WordPress database, media library, themes, plugins, and uploaded files. Backups are stored locally on your own server inside the WordPress uploads directory unless you manually download or move them elsewhere. RestorePilot does not send backup data to the plugin author or to any third-party service.<\/p>\n\n\n Yes. RestorePilot stores the source site URL in the backup manifest and replaces it with the current site URL during restore \u2014 automatically.<\/p><\/dd>\n No. Auto-detect is on by default. Manual URL fields are available in Advanced restore settings for edge cases.<\/p><\/dd>\n Yes. URL replacement is applied after unserializing values where possible, then the values are serialized again. Incomplete PHP classes are safely skipped.<\/p><\/dd>\n Under the WordPress uploads directory in a protected RestorePilot excludes the backup archives<\/em> created by other plugins (UpdraftPlus, Duplicator, BackupBuddy, WP Staging, etc.) to avoid including huge backup zips inside your backup. The backup plugins themselves<\/em> (their code inside Deleting the plugin removes all RestorePilot backups, logs, temporary download files, background job data, backup locks, and scheduled events.<\/p><\/dd>\n Two options: (1) RestorePilot automatically splits large uploads into chunks if you upload a single zip larger than the server limit. (2) Upload the zip into this site's WordPress uploads directory via FTP\/SFTP and use Advanced restore settings \u2192 Server backup path<\/strong> during restore.<\/p><\/dd>\n Many hosts refuse to create a file beyond a fixed size \u2014 the write fails with \"File too large\" no matter how much free disk space there is. RestorePilot therefore writes a backup as a set of volumes of up to 1 GB each: Keep the whole set together. To restore, place every volume in the same folder \u2014 RestorePilot reads them as one backup, and refuses to start if any volume is missing rather than restoring part of your site. If your host has a lower file size limit, a developer can reduce the volume size with the You never need to handle the volumes yourself: \"Download Full Backup\" always gives you a single file, even when the backup behind it is stored as several volumes \u2014 RestorePilot reassembles them into one download automatically. The individual volumes are still available under \"Download volumes individually\" if you ever need to retry just one piece.<\/p><\/dd>\n Yes. A background backup or restore runs in short chunks rather than one long process, so a host execution-time limit, a proxy or CDN timeout, or anything else that cuts the process short cannot lose progress \u2014 the next chunk simply continues from exactly where the last one stopped, including partway through a single large database table during a restore. On a large site this can mean several chunks before the job finishes, which is expected and does not mean anything went wrong. A scheduled (cron) daily backup is unaffected and still runs as a single process.<\/p><\/dd>\n Yes. Click Health Check<\/strong> next to any backup. RestorePilot verifies the zip structure, manifest, database export, and file paths.<\/p><\/dd>\n The free version keeps the newest 2 backups total. Manual backups and daily automatic backups share the same limit; older backups are removed automatically.<\/p><\/dd>\n Yes. Use RestorePilot stops immediately, removes maintenance mode, and writes the full error to the Logs tab. A pre-restore rollback point may be available, but you should review the logs and verify the site before retrying.<\/p><\/dd>\n\n<\/dl>\n\n\nwp-content<\/code> files. During restore, RestorePilot automatically detects the source URL from the backup manifest and replaces it with the current site URL using serialized-safe replacement \u2014 no manual search-and-replace needed.<\/p>\n\nWhy RestorePilot<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
\n
\n
\n
\n
\n
wp restorepilot backup<\/code> \u2014 create a full backup.<\/li>\nwp restorepilot backup --db-only<\/code> \u2014 database-only backup.<\/li>\nwp restorepilot health<\/code> \u2014 check the newest backup.<\/li>\n<\/ul>\n\n\n
.htaccess<\/code> and index.php<\/code>.<\/li>\nImportant note<\/h4>\n\n
Privacy & data<\/h4>\n\n
From your WordPress admin (most common)<\/h4>\n\n
\n
Manual install (if you downloaded the zip separately)<\/h4>\n\n
\n
restorepilot-backup-migration<\/code> folder to \/wp-content\/plugins\/<\/code>, or upload the zip directly via Plugins \u2192 Add New Plugin \u2192 Upload Plugin<\/strong>.<\/li>\n\n
Does RestorePilot support migrations to a different domain?<\/h3><\/dt>\n
Do I need to enter old and new URLs manually?<\/h3><\/dt>\n
Does it handle serialized WordPress data?<\/h3><\/dt>\n
Where are backups stored?<\/h3><\/dt>\n
restorepilot-backup-migration<\/code> folder. The folder is excluded from future RestorePilot backups.<\/p><\/dd>\nAre other backup plugins' files excluded from the backup?<\/h3><\/dt>\n
wp-content\/plugins\/<\/code>) are included normally.<\/p><\/dd>\nWhat happens when I delete the plugin?<\/h3><\/dt>\n
My backup is larger than the browser upload limit. What do I do?<\/h3><\/dt>\n
Why is my backup split into several files?<\/h3><\/dt>\n
your-backup.zip<\/code>, your-backup-v002.zip<\/code>, and so on. A small site produces a single file and looks exactly as before.<\/p>\n\nrestorepilot_backup_volume_bytes<\/code> filter.<\/p>\n\nMy backup or restore shows \"continuing in the background\" instead of finishing right away \u2014 is that normal?<\/h3><\/dt>\n
Can I check a backup before restoring?<\/h3><\/dt>\n
How many backups does RestorePilot keep?<\/h3><\/dt>\n
Can I run backups from WP-CLI?<\/h3><\/dt>\n
wp restorepilot backup<\/code> for a full backup, wp restorepilot backup --db-only<\/code> for database only, and wp restorepilot health<\/code> to check the newest backup.<\/p><\/dd>\nWhat happens if a restore fails?<\/h3><\/dt>\n
0.5.0<\/h4>\n\n
\n
restorepilot_backup_volume_bytes<\/code> filter.<\/li>\n.zip<\/code> file in wp-content), which could have omitted legitimate content while still reporting success.<\/li>\nhome<\/code> option could each be left in a broken state; both are now handled correctly.<\/li>\n%<\/code>-containing values passed through $wpdb->prepare()<\/code>, which could prevent this plugin's own leftover lock and job cleanup from finding what it needed to remove.<\/li>\n$wpdb->prepare()<\/code>'s %i<\/code> placeholder rather than manual escaping, which raises the minimum required WordPress version to 6.2.<\/li>\n0.4.0<\/h4>\n\n
\n
https:\\\/\\\/<\/code>) was missed during URL replacement after migration.<\/li>\nrp_tmp_<\/code> and rp_old_<\/code> tables left by an interrupted restore were not cleaned up before the next restore run.<\/li>\nCREATE TABLE<\/code> statements were not validated, allowing a malformed backup to inject arbitrary SQL.<\/li>\naddFile()<\/code> threw an exception.<\/li>\nwp_enqueue_style<\/code> \/ wp_enqueue_script<\/code> instead of being inlined in the page output.<\/li>\n<\/ul>\n\n0.3.1<\/h4>\n\n
\n
plugins\/updraftplus<\/code>, plugins\/duplicator<\/code>, and similar plugin code folders are included correctly.<\/li>\n0.3.0<\/h4>\n\n
\n
old.com<\/code>) that could corrupt email addresses and sibling domain names. Replacement now only matches full scheme-prefixed URLs (https:\/\/<\/code>, http:\/\/<\/code>, \/\/<\/code>).<\/li>\nadd_directory_to_zip<\/code> used str_replace($dir, $path)<\/code> which could strip the directory name multiple times. Replaced with substr<\/code>.<\/li>\nforce_release_backup_locks<\/code> checked stale status using the lock start time instead of the job's last-updated time, which could release locks on long-running but active backups.<\/li>\ncli_init<\/code> hook.<\/li>\nenforce_backup_retention()<\/code> was called during restore when no new backup had been created.<\/li>\nbackup-<\/code> and backup_<\/code> folder prefix rules in the skip list could exclude legitimate plugins and themes named with those prefixes.<\/li>\n.gz<\/code> extension in the skip list excluded pre-compressed asset files. Now only .sql.gz<\/code> and .tar.gz<\/code> are excluded.<\/li>\nshould_skip_file()<\/code> now pre-compiles lookup tables once per PHP process, reducing string comparisons by ~60% on large file sets.<\/li>\n_get_cron_array()<\/code> with the public wp_clear_scheduled_hook()<\/code> API (safe since WordPress 5.1).<\/li>\n0.2.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n