SBR Simple Backup & Restore is built for site owners who want a direct backup workflow without extra services, scheduling screens, or unnecessary settings.<\/p>\n\n
Create a backup, upload a backup file, keep backups in one list, and restore only when you choose.<\/p>\n\n
Main features:<\/p>\n\n
The plugin is focused on local backup and restore. It does not include cloud storage, scheduling, tracking scripts, remote services, or third-party libraries.<\/p>\n\n
Developed by The Road Agency.<\/p>\n\n\n
Yes. A backup created by the plugin contains the WordPress files and a database export inside one ZIP file.<\/p><\/dd>\n
No. Upload is save-only. Uploaded backups appear in the saved backups list, where you can restore them manually.<\/p><\/dd>\n
Creating and downloading a backup does not require it, because the plugin writes\nthe archive itself. Uploading and restoring a backup do require the PHP zip\nextension, because those steps read an existing ZIP file.<\/p><\/dd>\n
No, on purpose. A restore never writes wp-config.php back, so including it would\nonly place the database credentials inside a file you may download or move\naround. Keep a separate copy of wp-config.php for a bare-metal rebuild.<\/p><\/dd>\n
No. A restore only runs recognised statements, and only against tables whose\nnames start with this installation's table prefix. Anything else is skipped and\nreported as a warning.<\/p><\/dd>\n
A backup records a checkpoint after every chunk and resumes from it, discarding\nany partly written data. A restore reports progress per step; if the browser is\nclosed during the database import, reopen the plugin screen and start the restore\nagain from the same backup.<\/p><\/dd>\n
No. The plugin does not call external APIs, does not include tracking, and does not send backup data to a remote service.<\/p><\/dd>\n
Yes. The plugin code and included assets are licensed under GPLv2 or later unless another GPL-compatible license is explicitly stated.<\/p><\/dd>\n\n<\/dl>\n\n\n
Correctness and safety release. Verified end to end against WordPress 6.8 and\nMariaDB 10.11, including a cross-prefix, cross-address migration.<\/p>\n\n
Data integrity:\n* Fixed values being written to the database export through an escaping helper that also applies WordPress's internal placeholder escaping. Backslashes could be dropped and binary data could change length.\n* Binary and non-UTF-8 values are now exported as hex literals, so blob columns are reproduced byte for byte.\n* Fixed address replacement inside nested serialized data. A serialized string stored inside a serialized array kept its old length prefix and could no longer be unserialized.\n* Fixed a table whose first primary key is 0 having its DROP and CREATE written twice, which discarded rows already exported.\n* Fixed the database export using the per-site table prefix, which left the shared users and site tables out of a multisite backup.\n* The database export now uses a quote-aware statement reader, so a semicolon inside a value cannot split a statement.<\/p>\n\n
Reliability:\n* Fixed two workers advancing the same backup at once. Progress is now guarded by a file lock, and only one place schedules the follow-up run.\n* Backup archives are written by an append-only writer instead of reopening and rewriting the whole ZIP on every chunk, which prevented large sites from ever finishing. ZIP64 is supported for archives over 4 GB or with more than 65535 entries.\n* Fixed an upload chunk that was retried after a lost response being appended twice and corrupting the uploaded ZIP. Chunks are now written at an explicit byte offset.\n* Fixed a restore hanging forever when a value matched the old address case-insensitively but was not changed by a case-sensitive replacement. Replacement now advances by primary key.\n* A job that stops making progress is reported as stalled and can be cancelled, instead of showing \"running\" indefinitely.\n* Progress is driven from the status request when neither the originating request nor WP-Cron is able to continue the job.\n* Files that change size or disappear while being packed are skipped and reported, instead of failing the whole backup.<\/p>\n\n
Safety:\n* A restore only executes recognised statements, and only against tables carrying this installation's prefix. Anything else is skipped and reported.\n* wp-config.php is excluded from backups, so database credentials are not carried inside a downloadable archive.\n* Symbolic links are neither archived nor written back during a restore.\n* Restoring now asks for a typed confirmation, because it cannot be undone.\n* Finished archives are opened and checked before they are published to the backups list.\n* Directory protection files now cover both Apache 2.2 and Apache 2.4 syntax.<\/p>\n\n
Interface:\n* Progress bars are now driven per animation frame instead of jumping only when a step reports in, so a running job no longer looks frozen between updates.\n* The bar carries a moving highlight while a job is active, and turns green on success or red on failure.\n* Job status is polled more often at the start and then backs off, so the first feedback arrives quickly without adding load for the rest of the job.\n* The bar can drift a few points ahead of the last confirmed value to stay in motion, but it is capped short of the finish line and never displays 100% before the job actually completes.\n* Motion is reduced automatically when the operating system asks for it.<\/p>\n\n
Other:\n* Creating a backup no longer needs the PHP zip extension.\n* Home and site addresses are rewritten separately, which fixes installations living in a subdirectory.\n* Scheduled events are cleared on deactivation.<\/p>\n\n