JetBackup can restore WordPress safely when you understand what it will overwrite. This method is best for granular file, database, email, DNS, and account recovery without rolling back more than necessary.
Audience: hosting customers and providers whose cPanel or hosting panel includes JetBackup. Use this with the matching backup method whenever possible. If you did not create the backup yourself, verify the backup date, scope, and site path before restoring production.
Before restore
- Check the available restore-point dates.
- Identify whether the issue is files, database, or the whole account.
- Export new ecommerce or form data before database restore.
Restore steps
- Open JetBackup from the hosting panel.
- Choose the restore type: files, database, full account, or another available scope.
- Select the recovery point.
- Preview or select the specific file/folder/database where possible.
- Start the restore and watch job status.
- Clear cache and validate WordPress.
Post-restore verification
Confirm the restored component fixed the issue without rolling back unrelated data. Check admin login, media, forms, checkout, email, and logs.
Also check server and application logs, cache layers, CDN behavior, SSL, redirects, and whether scheduled tasks still run. A restore is not complete just because the home page loads.
Restore risks
- Restoring the whole account when one file was enough.
- Choosing the wrong database.
- Assuming every host exposes every JetBackup restore feature.
Rollback planning
Before restoring, keep the current state long enough to recover anything the restore might erase. For stores and membership sites, that means orders, subscriptions, users, payments, form submissions, bookings, and logs. For agencies and hosts, it also means customer communication and a timestamped maintenance note.
Fix I.T. Phill recommendation
Use JetBackup when it matches how the backup was created. If the restore tool is not available, fall back to files plus database restore, but test on staging first. After restore, update the backup plan so the next recovery is easier.
Related Fix I.T. Phill Guides
- How to Restore WordPress: Complete Recovery Methods Guide
- How to Restore WordPress by cPanel Backup Wizard
- How to Restore WordPress by File Manager and phpMyAdmin
- How to Restore WordPress by WHM Full Account Restore
- How to Restore WordPress by cPanel WP Toolkit
- How to Restore WordPress by Plesk WP Toolkit
- How to Restore WordPress by Plesk Backup Manager
- How to Back Up WordPress: Complete Methods Guide
- How to Back Up WooCommerce Without Losing Orders
- How to Test a WordPress Backup Restore Before an Emergency
- Disable WordPress plugins with phpMyAdmin when wp-admin is broken
