Restore
Restore a verified backup with an automatic safety snapshot.
What it does
Restore puts a verified backup back onto the site. Admin restores always create a safety snapshot of the current site first so you have a way back if something goes wrong.
How it works
- Pick a verified backup from Restore or history — or Import a backup zip (cloud / another site download) so it appears in the list after verification.
- Confirm restore. Stalza queues a matching safety backup.
- When the safety backup verifies, the restore job runs (database and/or files depending on mode).
- Keep the admin page open while jobs run.
Imported zips must be Stalza Backup archives (manifest.json + expected contents). They are verified on upload before restore is offered.
CLI may use --skip-safety for local smoke tests only. Never skip safety on production from the admin UI.
Modes
- Full — database and files
- Database — SQL only
- Files — themes/plugins/uploads paths from the archive
wp-config.php is never overwritten from an archive.
Site-to-site restores
When the backup’s table prefix or site URL differs from the destination, restore automatically:
- Rewrites SQL table names to the destination
$table_prefix - Runs a serialize-safe search/replace so
siteurl/home(and matching URLs in options/meta) become the destination domain
Same-site restores (matching prefix and URLs) skip remapping. Destination wp-config.php stays in place.
After a successful restore, the admin UI shows a Restore completed dialog. Sign in again (sessions are usually reset when the database is restored).
If restore fails
The safety backup remains in history. Fix the error, then restore from the safety uuid if needed. See Restore failed.