GICT knowledge base
Create and Restore WordPress Backups with UpdraftPlus
Published
UpdraftPlus can create WordPress component backups, schedule them and restore a selected backup set. It is not a guarantee of instant recovery, universal encryption or a clean site after compromise. Review the current installed edition and recovery requirements before relying on it.
Install the intended plugin
Use Plugins > Add New in an authorized WordPress administrator session, confirm the official UpdraftPlus publisher and compatibility, then install/activate through your normal change process. An active-installation count alone is not a reliable identity or security check.
Configure scope, schedule and storage
- Open Settings > UpdraftPlus Backups, or its equivalent current entry, and inspect Settings.
- Choose file and database schedules and retention according to actual change frequency. Review which components and exclusions the selected edition covers.
- Choose an approved supported remote destination. If authorizing Dropbox or another provider, inspect the account, permission request and callback before completing setup.
- Save and run Backup Now for the intended components, including the remote-send option where required.
- Inspect the completed set and logs, then verify that every expected component actually exists at the remote destination.
Remote authorization is not proof of a completed upload. Protect destination access, recovery credentials and encryption material separately. Database encryption, multiple destinations, pre-update backups and other advanced features are edition-dependent; do not assume that every archive or all sensitive content is encrypted automatically.
Restore without deleting the only remaining copy
The old instruction to delete everything from WordPress before recovery is withdrawn. Preserve current files, database and incident evidence before a destructive change. In a compatible isolated destination, upload or rescan the trusted backup set as appropriate, select Restore beside the correct set and review the components before confirmation.
If the original dashboard is unavailable, follow the documented compatible fresh-install/recovery route with the backup safely preserved elsewhere. Do not overwrite the only archive while preparing the destination. Review post-backup orders, comments and other changes before a production rollback.
Validate the recovered application
Check administrator access, content, media, plugin behavior and application-specific workflows, with outgoing mail/payment/cron side effects contained. A restored login does not establish malware removal. Recheck the original entry point and account/session security if compromise prompted recovery.
Cloning to another URL or server is a separate operation requiring URL/configuration and compatibility checks, not a guaranteed seconds-long transfer. Plugin capability is not an InterServer migration-service promise: matching-panel web-hosting moves only; no VPS/dedicated migrations.
Reference: official UpdraftPlus features, edition distinctions and support links.
Reviewed October 15, 2026. Documentation review; no plugin installation, cloud authorization, customer backup or restore was executed.
Related guides
7 Common Hosting Mistakes Beginners Make (And How to Avoid Them)
7 common hosting mistakes beginners make in 2026: no backups, ignored updates, bad host choice, weak passwords, single point of failure, no staging. With fixes for each.
WordPressWebsite Migration Backup Checklist: What to Save and How to Test
Prepare a website migration backup: inventory files, databases, email and DNS, check archive integrity, test recovery and plan a safe final synchronization.
WordPressCore Web Vitals in 2026: A Practical Fix Guide for Site Owners
Core Web Vitals 2026: practical fixes for LCP, INP, and CLS. Real root causes, what to measure, common misconceptions, and a priority order of fixes for site owners.
WordPressFixing the WordPress “Death Loop”: When Missing Files slow down your site
You’ve just launched your new WordPress site or pushed a big update. In your staging environment, everything ran perfectly.
