Back to blog
13 min read Video Lessons

How to Create a WordPress Website Backup and Restore It

A WordPress backup is useful only if you can restore the data you need. Before a CSV import, a bulk update, or a site-to-site sync, create a restore point, check that it completed, and understand what restoring it will replace.

This tutorial shows how to create a backup with UpdraftPlus, change three test page titles using Import Export by RockStarLab, and restore the original titles. You will also learn how to ask an AI agent to create, inspect and restore a database backup through MCP, then verify the recovered content.

Disclosure: the UpdraftPlus link below is an affiliate link. We may earn a commission if you purchase through it, at no extra cost to you.

What should a WordPress backup include?

Your database and your files serve different purposes. A database backup contains page content and settings; it does not contain the image files displayed on those pages. A files-only backup cannot recover the text of a post from the database.

Component What it protects When it matters
Database Posts, pages, titles, custom fields, users, terms, settings and plugin tables included in the backup Before imports, content updates and database changes
Uploads Uploaded images, documents and other files in the included uploads paths Before replacing, deleting or reorganizing media
Plugins and themes The included plugin and theme files Before code changes or updates, alongside a database backup
Other files Additional paths included by your backup configuration When your site depends on files outside the usual selections

For the title-change exercise below, a database backup is sufficient: only database content changes. For broader recovery, include the relevant file components too and inspect the configured exclusions. Do not describe a database-only backup as a complete copy of the website.

UpdraftPlus Free does not back up every part of a hosting account. WordPress core coverage, server configuration, DNS, mailboxes and files outside the selected paths need their own recovery plan. See the vendor’s manual recovery documentation for the distinction between reinstalling WordPress and restoring its backed-up content.

Before you start

  • Use a staging or local site for the deliberate change-and-restore exercise. Do not create an intentional mistake on a live store.
  • Install and activate UpdraftPlus Backup & Restore from Plugins → Add Plugin.
  • Use an account that can manage backups. Keep a way to sign into WordPress directly if your agent connection stops working.
  • Check available storage and keep a copy outside the web server for real recovery. Configure remote storage separately if required.
  • For the optional bulk-title demonstration, activate Import Export by RockStarLab PRO. UpdraftPlus can create and restore backups independently of that demonstration.

A database restore is not an undo button for three pages. It restores the selected database tables to the backup’s state. New orders, registrations, comments and edits made after that point can be lost. On a changing live site, plan the recovery window and preserve newer transactions before deciding to restore.

Step 1: Create a fresh database backup in UpdraftPlus

Open UpdraftPlus in the WordPress admin menu and select the Backup / Restore tab. Click Backup Now to open the component selection dialog.

  1. Leave Include your database in the backup selected.
  2. For this database-only exercise, clear Include your files in the backup. For a real operation that affects files, include the appropriate files instead.
  3. Check the remote-storage message. If no destination is configured, the archive stays on this server.
  4. Optionally protect this restore point from automatic retention cleanup using the manual-deletion checkbox.
  5. Click Backup Now inside the dialog.
UpdraftPlus Backup Now dialog with database selected and files excluded
Database-only backup settings for a controlled page-title rollback. The dialog also makes the absence of remote storage explicit.

Step 2: Confirm that the backup finished

Wait for UpdraftPlus to report that the backup succeeded and is complete. Then find the new entry under Existing backups. Match its timestamp and confirm that the Database component is present.

A queued task or an archive appearing in the list is not enough on its own. If the operation reports a warning or error, inspect the log before changing content. A backup that never finished should not be your planned recovery point.

UpdraftPlus reports a successful completed backup and lists its Database archive
The manual backup is complete and its database archive is available in Existing backups.

Use the component download controls to save a copy to a suitable external location when preparing a real recovery plan. Keep every archive part belonging to the selected backup set. A copy stored only beside the website can disappear with the same server failure that takes down the site.

Step 3: Make a controlled bulk update on a test site

You can skip this exercise if you only need a backup. For a visible before-and-after check, three pages begin as Delivery Information, Returns Policy and Customer Support. Convert their titles to uppercase, then restore them.

Open Import Export by RockStarLab → Content Updater, choose Pages and add an ID filter using In (comma-separated). Enter only the IDs of your disposable staging pages.

Refresh the item count and verify that it matches the intended selection. An empty filter targets all items of the selected content type, so do not proceed with the default selection when you intend to change only a small test set.

Content Updater 2.0 ID filter selects three page IDs
The filter limits the demonstration to three known pages before any title is changed.
  1. Continue to Select Fields and select only Title.
  2. On Field Transformations, click Assign Transformations for Title.
  3. Find Convert to Uppercase and add it.
  4. Enter a sample title in Test Value and click Test Pipeline.
  5. Confirm the preview, then click Apply Transformations.
  6. Continue to the summary. Confirm three items, one field and one transformation, then click Start Update.
Uppercase transformation preview changes Delivery Information to DELIVERY INFORMATION
Test Pipeline previews the exact transformation before the update starts.
WordPress Pages list shows CUSTOMER SUPPORT, DELIVERY INFORMATION and RETURNS POLICY
The three titles are now uppercase. Their unchanged reference content lets us find the same pages before and after restoration.

For broader workflows, see the WooCommerce CSV and Excel import tutorial and the product synchronization guide. Back up the destination before an operation that can overwrite existing data.

Step 4: Restore the database backup

Return to UpdraftPlus → Backup / Restore. Locate the backup taken before the title update and click its Restore button. Check the timestamp carefully, especially when several copies were created on the same day.

  1. Select Database as the component to restore.
  2. Click Next and allow UpdraftPlus to inspect and prepare the archive.
  3. Read the preparation result. Confirm that the backup belongs to the intended site.
  4. When ready to replace the database with this restore point, click Restore on the confirmation screen.
  5. Keep the restoration page open until it reports completion.
UpdraftPlus restore wizard with Database selected
Only the database is selected because the demonstration changed titles, not plugin, theme or upload files.

This walkthrough restores the site to the same URL. A move to another domain is a different operation with additional URL and environment considerations. The official same-site restoration guide explains the native wizard and recovery options.

UpdraftPlus restoration screen displays Restore successful
The native restoration finished successfully. The next step checks the content itself.

Step 5: Verify the restored content

Open the same pages after restoration. Compare titles, content, slugs and publication statuses with their original values, and check the rendered pages.

Pages list after restore shows original Customer Support, Delivery Information and Returns Policy titles
The original titles are back on the same records, rather than newly created replacement pages.

Adapt this check to the operation you are protecting. After a product update, inspect prices, stock and variations. After an ACF change, open the fields in the editor. After a media operation, load the actual images. A successful restore message does not replace these checks.

If sign-in is required again, use the credentials valid at the restore point. Database restoration can also revert settings used by integrations. Check the site before resuming imports or sync jobs.

How to create a WordPress backup with an AI agent

Import Export by RockStarLab exposes an optional UpdraftPlus integration through the WordPress Abilities API. An MCP-compatible agent can discover the available actions, submit a backup and check its status. UpdraftPlus still creates the archive; the agent coordinates the operation.

First follow our AI-agent connection guide. That article covers client configuration and authentication. You do not need a second connection tutorial here.

Enable the UpdraftPlus integration

With UpdraftPlus active, open Import Export by RockStarLab → Plugin Options → AI Agent Connection. Enable the main Abilities API switch and the separate Enable Abilities API for UpdraftPlus switch under Additional integrations. Use your existing authorized MCP connection to discover the backup actions.

AI Agent Connection screen has UpdraftPlus abilities enabled and describes restore compatibility
UpdraftPlus has its own opt-in switch. The interface also states the narrower compatibility requirements for agent-driven restoration.

Prompt 1: check support before making changes

Connect to my WordPress MCP server for the staging site.
Discover the UpdraftPlus abilities and read their input schemas.
Run rsl-ie/updraftplus-status with empty parameters {}.
Report the installed version, whether a native operation is busy,
and whether agent-driven restore is supported.
Do not create a backup or change content yet.

After updating Import Export by RockStarLab to 2.0.4, the status returned UpdraftPlus 1.26.13, no native operation in progress, and restore_supported: true. Version 2.0.4 accepts UpdraftPlus 1.26.8 or later; earlier plugin releases restricted restore to an exact version match.

Prompt 2: create and verify a database backup

Create a database-only UpdraftPlus backup on this staging site.
Keep it local for this test; do not send it to remote storage.
Use a unique request ID and the discovered backup-start schema.
Poll the returned job until it reaches a terminal status.
If it completes, inspect the resulting backup and report its ID,
components, archive size and whether the archive is available locally.
Do not start an import, update or restore.

For a database backup, call rsl-ie/updraftplus-backup-start with parameters such as:

{
  "request_id": "article-backup-20261025-01",
  "components": ["db"],
  "send_to_remote": false
}

Use a new request ID for a new backup. After an interrupted response, inspect the existing operation before starting another. Poll rsl-ie/updraftplus-backup-status, then inspect the completed archive with rsl-ie/updraftplus-backup-get.

Check Observed result
Backup ID 1792924519
Final status completed
Components db
Local archives 1
Archive size 515,125 bytes
Remote destination None in this example
UpdraftPlus Existing backups lists the agent-created database backup at 10:35
The newer entry is the database backup created through MCP. Its timestamp and archive match the agent result.

Restore the backup through your AI agent

Import Export by RockStarLab 2.0.4 accepts UpdraftPlus 1.26.8 or later for the supported same-site restore workflow. Check the integration’s restore requirements before proceeding.

The restore requires standard local archives, a single-site installation and direct filesystem access. Encrypted, incremental, foreign-site, multisite and remote-only restores remain outside this integration’s supported route. Keep WordPress admin and hosting access available.

Inspect the selected backup and check current restore support.
Prepare a database-only restore plan for that exact backup.
Show me the backup ID, timestamp, components and warning about replacing
newer data. Do not start restoration until I approve this exact plan.

The agent calls rsl-ie/updraftplus-restore-plan. The response contains a plan ID, an expiring confirmation token and a warning. Review the selected site and restore point before approving. A database restore can overwrite newer records and connection settings.

I approve the database-only restore of the backup and plan you just showed
on this staging site. Start that exact plan, then monitor restore-status.
Do not repeat the restore if the connection drops. Report the actual
terminal state and verify the restored page in the browser.

After approval, the agent calls rsl-ie/updraftplus-restore-start using the returned plan ID and token, a unique request ID and confirm: true. It polls rsl-ie/updraftplus-restore-status with the restore job ID. Tokens are specific to the plan; do not copy an example token or reuse an expired confirmation.

Check the restored content

Open the restored pages in the editor and on the frontend. Compare their titles and content with the backup you selected.

Rendered Delivery Information page after restoring the agent-created backup
The original heading and reference paragraph are visible after restoring the agent-created database archive through MCP.

Troubleshooting backup and restore workflows

Symptom What to check next
The agent cannot see UpdraftPlus actions Confirm the plugin is active, both relevant API switches are enabled, and the connected account has the required permission. Discover abilities again.
The backup stays queued Check WP-Cron or the configured system cron runner and the UpdraftPlus log. Queue acceptance is not backup completion.
An archive is listed but the operation failed Read the failure and log; do not use the presence of a history row as proof of a complete backup.
Agent restore is unsupported Use the dashboard route supported by UpdraftPlus. Check version and archive restrictions instead of forcing the operation.
The agent disconnects during recovery Sign into WordPress directly, inspect recovery state and recheck the connection settings. Never automatically replay an uncertain restore.
The page still looks unchanged after restoration Check the exact backup timestamp and component selection, then verify stored values and clear relevant caches before comparing the rendered page.
WordPress admin is unavailable This dashboard tutorial cannot run until access is recovered. Use hosting recovery or the vendor’s manual restoration instructions.

If only a few posts went wrong, you may not need a full restore. See How to Roll Back a Bad WordPress Import or Sync for removing posts an import created and restoring overwritten fields from a CSV.

Backups, exports and migrations solve different problems

A CSV export is useful for reviewing or moving selected records. It is not a complete database backup: it may omit settings, relationships, plugin tables and file contents. Conversely, restoring a database backup is often too broad when you only want to transfer one category or a handful of products.

Use our WooCommerce store-data migration guide when the task is moving supported store entities. Use the taxonomy import and export guide for terms and their hierarchy. For either workflow, a separate backup protects the destination’s pre-operation state.

Read-only exports generally do not overwrite your site’s content. The restore point is especially important before the subsequent import, update, deletion or synchronization that changes existing records.

Earlier video walkthrough

This earlier video uses the previous Import Export interface. The core exercise remains the same: create a database backup, change page titles, then restore them. Follow the updated written steps and screenshots above for the 2.0 interface and the AI workflow; the video is supplementary.

An AI agent can create and restore UpdraftPlus backups too, with your confirmation before any restore. See Letting an AI Agent Edit WordPress Content Safely for a tested backup, change and rollback.

Frequently asked questions

Do I need a backup before importing WordPress data?

Create a fresh backup before an import that can create or update important records. Verify completion and understand the scope of a restore before you start. A read-only export is different from an import that overwrites data.

Is a database backup a full WordPress website backup?

No. It protects the included database tables, but not uploaded image bytes, plugin files or theme files. Include the relevant file components and account for excluded paths and hosting configuration when planning broader recovery.

Can I restore only the database with UpdraftPlus?

Yes. Select Database in the restore wizard when that is the component you need. Restoring the database can replace newer orders, users and other records; it does not target only the pages used in this demonstration.

Can an AI agent create an UpdraftPlus backup?

Yes. Enable the UpdraftPlus abilities integration and configure MCP. An agent can start a database backup, monitor it and inspect the completed archive.

Can the agent restore a backup on UpdraftPlus 1.26.13?

Yes. Version 2.0.4 accepts UpdraftPlus 1.26.8 or later. The same-site, local-archive and other restore requirements still apply.

Does this tutorial verify remote backups or full file restoration?

This walkthrough covers local database backups and restoration. A full recovery plan also needs appropriate file components and independently stored copies.

Will restoring a backup undo newer orders or edits?

It can. Database restoration returns selected tables to an earlier state, so changes made after that backup can be lost. Plan the recovery window and preserve newer business data before restoring a live site.

Does a WooCommerce CSV export replace a backup?

No. A selected data export is a transfer or audit file, not a complete recovery copy of database tables, settings and website files. Use exports for their intended scope and keep a separate recovery backup.

Continue with the written import, export and sync tutorials, or use the agent setup guide to connect your own test site.

Dmitriy
About author

Dmitriy

WordPress Developer with 15+ years of commercial experience. Elite Author on ThemeForest and creator of custom WordPress plugins. Passionate about clean code, performance optimization, and building useful tools for the WordPress community.

JOIN THE CONVERSATION

Comments 0

Have a question or a tip to share? Leave it below.

Leave a comment

Your email address will not be published. Required fields are marked *

We store your name, email and comment to show and moderate it; your email is never published. Spam protection is provided by Cloudflare Turnstile and profile pictures by Gravatar. See our Privacy Policy.


Try the plugin with no risks!

New users get 1 month with access to all premium features. Experience the most powerful WordPress data engine today.

Download Now
Get PRO for FREE