Restore backups to Staging
The Staging page can create a staging site from a backup or replace an existing staging site with a backup.
Server repository backups
When production backups exist on the same hosting node, the Panel lists those backups directly. Selecting Create Staging from Server Backup or Restore Server Backup keeps the archive on the hosting node; it does not download the backup through the browser or Panel and upload it again.
Only backups belonging to the managed production site are exposed by this selector.
Uploaded backup packages
The upload workflow accepts supported Webcore, Plesk and WP Toolkit WordPress backup packages. The package is inspected and normalized through the managed import workflow before it is applied to Staging.
Restoring over existing Staging
Before an existing staging site is replaced, Webcore creates a before-backup-restore safety snapshot containing the current staging files and database.
After import, the Panel reapplies staging URL rewriting and protections, including mail suppression, WP-Cron suppression, noindex behaviour and cache cleanup. If the restore fails, Webcore attempts to roll back to the pre-restore snapshot automatically.
Creating Staging from a backup
When no staging copy exists, Webcore provisions a new isolated staging site first and restores the selected backup into it. If the import fails, the incomplete staging site is removed where possible.
Moving the restored backup to production
There is intentionally no direct backup to production action inside the Staging workflow. The safer recovery path is:
- restore the backup to Staging
- inspect the site and WP Admin
- verify important pages and application behaviour
- use Push to Live
- retain the production safety snapshot until the restored production site has been verified
This makes a backup restore testable before it becomes a production change.