Museder RestoreOne vs WP STAGING – WordPress Backup, Restore, Migration & Clone

Museder RestoreOne lets you create complete WordPress backups (database + wp-content) as a single archive, and restore them in a guided 3-step wizard. It is designed for shared hosting environments and uses WordPress APIs for database backup/restore, with archive compression handled by ZipArchive or WordPress’ bundled PclZip. Key features One-click full-site backup Export the database, meta.json, and wp-content/ into a single archive you can download or restore later. Restore Center wizard A clear 3-step flow: upload & analyze → review summary & options → start restore with real-time progress and logs. Chunked uploads with validation Bypass upload_max_filesize / post_max_size limits by uploading your archive in small chunks, with retries and integrity checks. Shared-hosting friendly Uses pure PHP + WordPress APIs for database backup/restore, and falls back from ZipArchive to PclZip compression when needed. Schedules and logs Create one or more automatic backup schedules (or run backups manually), then inspect, download, or clean up structured backup and restore logs. Neo-glass admin UI Modern Dashboard, Backups, Restore, Schedules, Logs and Settings screens with clear calls-to-action, status messages, and responsive layout. Multisite This release is not formally tested on WordPress Multisite. For predictable results, use RestoreOne on standard single-site installs (one site per admin context). If you run a network, treat use as experimental until you have verified backups and restores on a staging clone. External services This plugin does not use external services. The only programmatic outbound HTTP the base plugin performs by default is an optional, short non-blocking request to your own site’s wp-cron.php (same host / local loopback) to encourage scheduled tasks to run. No third-party API is called for backups or restores. All admin JavaScript and CSS for RestoreOne are loaded from files shipped under this plugin’s assets/ directory (including vendored libraries under assets/vendor/). Optional add-ons, if you install them separately, may introduce their own network behavior; see each add-on’s readme. See the FAQ for more on the local wp-cron.php nudge. Privacy What this plugin stores on your server Backups — Complete-site archives are written under your WordPress uploads area (typically wp-content/uploads/museder-restoreone/backups/ or the path shown on the Backups screen). Each archive contains a database export (database.ndjson), meta.json, and a copy of wp-content/ from your site at backup time. Logs — Text logs for backup, restore, and related operations are stored under wp-content/uploads/museder-restoreone/logs/ (see the Logs admin screen). Restore reports — When you generate a restore report, files are stored under wp-content/uploads/museder-restoreone/reports/ (or the path configured for reports on your install). Schedules and settings — Options and scheduled events are stored in your WordPress database like other plugins. Diagnostics Version / build heartbeat — After an upgrade, the plugin may write a one-line informational entry to the local Logs directory (same server, no remote host) noting the active plugin version and build id. This is for support troubleshooting only. Exact folder names may vary with your uploads path or custom content directory; nothing is sent to a fixed external hostname by this plugin. The plugin resolves these locations using WordPress APIs (for example wp_upload_dir() and path helpers derived from your install) rather than hard-coded internal constants, so custom wp-content or uploads layouts can be reflected correctly where your host allows. Third parties The free plugin does not upload your backup contents, database, or logs to third-party APIs or clouds. That statement matches External services above and the FAQ entries on external data and local wp-cron loopback. Optional add-ons (separate plugins or extensions, if you install and activate them) could send specific categories of data to remote storage or services only when you enable and configure those extensions; the base RestoreOne plugin does not do that on its own. Retention and deletion You can delete backup archives from the Backups screen, remove or download logs from Logs, and adjust retention-related options where provided. Uninstall (uninstall.php) removes plugin-owned options, transients (including timeout rows), dynamic job-lock option rows, and scheduled cron hooks whose names start with museder_restoreone_. It does not delete backup ZIP archives, log files, restore reports, or other files under your uploads/storage tree; delete those manually from the Backups / Logs UI or your host if you no longer need them. On Multisite, uninstall walks sites in batches (100 IDs per query) instead of loading the entire network at once. Very large networks should still use a maintenance window so uninstall is not interrupted by web-server timeouts. Developer Development source of truth is the public GitHub repository: https://github.com/artherslin-source/museder-restoreone Contributors and release maintainers should follow the Modification & Release SOP (docs/SOP-PLUGIN-DEVELOPMENT-AND-RELEASE.md in the repo). Summary: Branching: work on fix/, feature/, or agent/ branches from current main; avoid long-lived dirty main. WordPress.org Lite: fully functional, GPL, no license gates, trialware, or bundled Add-on/PRO code in the Lite package or SVN. Security: every sensitive AJAX/REST/form handler needs capability checks, nonces, sanitize/validate input, and escaped output. Release version sync (six fields, same version): museder-restoreone.php Version, MUSEDER_RESTOREONE_VERSION, MUSEDER_RESTOREONE_BUILD_ID, readme.txt Stable tag, new Changelog block, and new Upgrade Notice block (easy to forget — WP.org shows the notice to updaters). Package Lite ZIP: use create-package.sh or tools/package-lite-windows.ps1 only; require BOUNDARY_CHECK=PASS. Do not use PowerShell Compress-Archive. Lite ZIP must not include docs/, tools/, .cursor/, .github/, logs/, or museder-restoreone-pro/. GitHub release: after explicit approval, tag vX.Y.Z on main; GitHub Actions builds release artifacts. WordPress.org SVN: commit Lite source files only (no zip); copy trunk to tags/X.Y.Z; fill docs/RELEASE-X.Y.Z-SVN-HANDOFF.md from the template before SVN commit. Checklists: docs/RELEASE_CHECKLIST.md, docs/PACKAGING.md, docs/WORDPRESS_ORG_DEVELOPMENT_GUIDE.md, AGENTS.md.

WordPress Backup, Restore, Staging, Cloning & Migration — All in One WP STAGING is the all-in-one WordPress backup, staging, cloning, and migration plugin, built for professional workflows with 100% unit-tested code, thousands of automated tests, and extensive end-to-end testing across supported PHP versions. Create a full backup or an exact clone or copy of your website in minutes. Use it to duplicate your site, test plugin and theme updates safely, restore your site when needed, move or migrate WordPress to another server, transfer your site to a new host, or build a staging copy before making changes. WP STAGING reliably backs up, clones, and migrates WooCommerce stores too, including orders, products, and customer data. WP STAGING is developed in Germany and designed for agencies, developers, and businesses that need reliable WordPress backup, recovery, staging, restore, and migration workflows. WP STAGING | PRO also includes advanced workflows such as Remote Sync, which lets you pull a WordPress site securely from one server to another using an API key, and WP STAGING CLI, which can turn a WP STAGING backup into a local Docker-based development site. All data stays on your server unless you choose a transfer or remote storage workflow. WP STAGING is designed for speed, reliability, and low-resource environments, including shared hosting. WP STAGING automatically performs search and replace for links and paths during cloning, backup, restore, and migration workflows. This staging and backup plugin can clone your website quickly and efficiently, even if it is running on a weak shared hosting server. WP STAGING FREE – BACKUP & STAGING FEATURES Clone the entire production site into a subdirectory like example.com/staging-site. High-performance backup and cloning, even for websites with very large databases. Create full or partial backups — full-site backup, database-only, or files-only backups. Scheduled backups with automatic daily backups. Easy to use: create a clone or backup in one click. Efficient background processing without slowing down your website. No Software as a Service and no external account required. All your data stays on your server. Your data belongs to you only. No server timeouts on huge websites or weak servers. Fast backup, clone, and restore workflows depending on site size and server resources. Use the clone as part of your backup and update strategy. Only administrators can access the cloned or backup website. SEO-friendly staging sites with login protection and no-index handling. The admin bar on the staging / backup website is orange colored and shows when you work on the staging site. Extensive logging features. Supports Apache, Nginx, Microsoft IIS, and LiteSpeed Server. Every release passes extensive automated tests to keep the plugin robust, reliable, and fast. Fast and professional support team. WP STAGING | PRO – BACKUP & STAGING FEATURES The features below are available in WP STAGING | PRO. Remote Sync – Pull a WordPress site securely from one server to another. WP STAGING CLI – Turn a backup into a local Docker-based development site. Migrate and transfer WordPress to another host or domain. Push staging changes to production (staging to live), including plugins, themes, and media files, with one click. Clone a backup or staging site to a separate database. Choose a custom directory for a backup or cloned site. Select a custom subdomain destination like dev.example.com. Define user roles for accessing the clone or backup site. This can be clients or external developers. Multisite support for migration, backup, and cloning. Schedule recurring backups by time and interval. Download and upload backups to another server for migration and transfer. Backup retention settings. Custom backup names. Email notifications if a backup cannot be created. Backup for WordPress multisites. Cloud backup, offsite backup, and remote backups to external storage providers. Backup to Google Drive. Backup to Amazon S3. Backup to (S)FTP. Backup to Dropbox. Custom backup folder destinations for cloud storage providers. Priority support. DOCUMENTATION How to Backup and Restore WordPress Backup and Restore WordPress Backup & Transfer WordPress Site to Another Host How to Migrate Your WordPress Site to a New Host Remote Sync Pull a WordPress Site from One Server to Another Local Docker Development with WP STAGING CLI WP STAGING CLI – Upgrade Now All Backup Guides All Backup Guides Working with Staging Sites Working with Staging Sites FAQ for Backup & Cloning FAQ for Backup & Cloning Troubleshooting Backup & Cloning Troubleshooting Backup & Cloning WP STAGING BACKUP & CLONING TECHNICAL REQUIREMENTS & INFORMATION Works on latest version of WordPress Minimum Supported WordPress Version 3.8 Cloning and Backup work on all webhosts No extra libraries required Backup & cloning supports huge websites Custom backup format is much faster and smaller than any tar or zip compression Backup & cloning works in low memory & shared hosting environments SUPPORT WP STAGING Backup & Cloning