by
rebuzz
0 (0 reviews)
ReBuzz Backup and Restore
Full-site backup and restore for WordPress, built to work within the tight PHP time and memory limits of shared hosting.
ReBuzz Backup and Restore ranks #62,575 among WordPress.org plugins with 0+ active installations, is #579 of 646 in the Multisite category, and was last updated Oct 7, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.3
v1.8.0
Current Version v1.8.0
Updated 2 weeks ago
Last Update on 07 Oct, 2026
Refreshed 10 hours ago
Last Refreshed on
#579 of 646 in Multisite
Actively maintained
Rank
#62,575
—
No change
Active Installs
0+
—
No change
KW Avg Position
N/A
—
No change
Downloads
340
+4 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
30,973
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#62,575
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.8.0
- Last Updated
- Oct 07, 2026
- Requires WP
- 5.8+
- Tested Up To
- 7.1.3
- PHP Version
- 7.4 or higher
- Author
- rebuzz
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,762
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,018
UpdraftPlus: WP Backup & Migration Plugin
3M+ installs
#14
WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager
3M+ installs
#19
All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)
2M+ installs
#22
MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)
2M+ installs
#24
Code Snippets
1M+ installs
#32
MainWP Child - Securely Connects to the MainWP Dashboard to Manage Multiple Sites
700K+ installs
#86
LightStart - Maintenance Mode, Coming Soon and Landing Page Builder
400K+ installs
#134
BackWPup – WordPress Backup & Restore Plugin
400K+ installs
#136
Frequently Asked Questions
Common questions about ReBuzz Backup and Restore
That is what it was built for. Every step is chunked and resumable, so the plugin works inside short execution-time and memory limits instead of asking you to raise them.
Before a restore begins the plugin writes a few megabytes and creates some test files in its own folder. If that fails, your hosting account has hit its storage quota or its file-count (inode) limit, and the restore would have failed part-way through anyway - so it stops first and says so. Both figures are in your hosting control panel; cPanel shows the second as "File Usage" or "Inodes". The test is deliberately smaller than the first batch of a real extraction, so it will not refuse a restore that would have worked, but if it ever misfires you can switch it off with define('WPCB_RESTORE_PROBE_FILES', 0); in wp-config.php.
By default in wp-content/uploads/rebuzz-backup-and-restore/backups/. The plugin writes .htaccess and web.config rules there, but those only apply on Apache and IIS - on Nginx they are ignored and the archive is served as an ordinary static file to anyone who knows its name. Because of that the plugin actively tests the folder before every backup: it requests a temporary file from it over HTTP with no login. If the server hands that file over, the backup is refused rather than created and left downloadable - a backup contains your whole database, so the plugin will not produce one it cannot keep private. Some hosts block a site from making requests to itself, so the test cannot run. Backups are refused then too: the server's name cannot settle it, because many hosts put Nginx, which ignores .htaccess, in front of Apache. To fix it, move backups out of the web root by adding this to wp-config.php: define( 'WPCB_BACKUP_DIR', '/full/path/outside/public_html/rebuzz-backups' ); The path must be absolute and writable by PHP, and should sit outside the folder your web server serves. Archives already in the old location are not moved automatically - the Backups tab will tell you they are there so you can move them yourself.
Put the ZIP in wp-content/uploads/rebuzz-backup-and-restore/backups/ using FTP or your host's file manager. It appears in the restore list automatically and skips the browser upload limit entirely. The exact path is also shown on the ReBuzz Backup screen, under the backups list.
Yes. A network administrator can back up the whole network, while an individual site admin gets only their own site. Restores enforce the same boundary.
Every file and the database dump is hashed with SHA-256 when the backup is made, and those hashes are re-checked before the restore writes anything. If one doesn't match, the restore stops rather than continuing with a corrupt archive.
WordPress's scheduler (WP-Cron) starts the backup at the hour you picked. The site then asks itself for each step in turn, the same small steps a manual backup takes, so the same time and memory limits apply. If those requests are blocked by the host, WP-Cron carries the backup on by itself every few minutes, and a backup that stops making progress for ten minutes is marked failed and reported.
WP-Cron only runs when someone visits the site, so on a quiet site a backup can start a little late. If your host offers real cron jobs, point one at wp-cron.php every few minutes. If DISABLE_WP_CRON is set in wp-config.php, scheduled backups only run when your host runs wp-cron.php for you - the Schedule tab tells you when that's the case.
No. Only backups the schedule made on this site are ever deleted to keep the number you chose. Backups you create yourself, and ones you upload or copy in, are never deleted automatically. I'm not receiving the emails. Use Send test email on the Schedule tab. If that email doesn't arrive either, WordPress on your host can't send mail yet - an SMTP plugin usually fixes it. Check the spam folder too.
Amazon S3 and services with the same API - Backblaze B2, Cloudflare R2, DigitalOcean Spaces, Wasabi, or any other S3-compatible storage you give an endpoint for - and Dropbox. Set them up on the Storage tab; Test connection writes a small file and deletes it again, so you know uploads will work before the first backup. Google Drive is planned for a later version.
