Web Plura

Problem

WordPress Database-Only Backup Guide

Use a database-only WordPress backup when content, settings, orders, users, or plugin tables need a focused rollback point without replacing site files.

WordPress backup and recovery guideFiles-only backup guide

Problem, cause, fix, verify

Problem

A database-only backup may be the right rollback point for content and settings work, but it can also create false confidence if files, uploads, plugins, and schema changes are ignored.

Audience

WordPress administrators, WooCommerce operators, agencies, and developers planning a reversible database change.

First check

Database-only backups are useful before reversible content, settings, user, menu, option, taxonomy, or WooCommerce configuration changes. They are smaller and faster than full-site backups, but only when the risk is actually database state.

Verify

WPlura Backup & Restore Manager can help organize backup evidence and restore-point review inside WordPress, while Diagnostics can help document the operational context before a risky change.

Editorial trust

Published
Updated
Content type
Problems
Review editorial policy

On this page

Symptom

A database-only backup may be the right rollback point for content and settings work, but it can also create false confidence if files, uploads, plugins, and schema changes are ignored.

For: WordPress administrators, WooCommerce operators, agencies, and developers planning a reversible database change.

Diagnosis

What to check before changing the site

When Database-Only Is Useful

Database-only backups are useful before reversible content, settings, user, menu, option, taxonomy, or WooCommerce configuration changes. They are smaller and faster than full-site backups, but only when the risk is actually database state.

What It Does Not Protect

This backup type does not protect media files, plugin files, theme files, mu-plugins, uploads, cache files, server rules, or CDN settings. If the change touches those layers, use a full backup path instead.

WooCommerce Caution

A WooCommerce database restore can overwrite orders, payment notes, stock changes, customers, coupons, and refunds created after the backup. Treat restore as an operational decision, not a quick undo button.

Restore Evidence

A useful backup has owner, timestamp, table scope, storage location, retention window, and restore method. Without that evidence, the team may discover during an incident that the backup is incomplete or inaccessible.

WPlura Fit

WPlura Backup & Restore Manager can help organize backup evidence and restore-point review inside WordPress, while Diagnostics can help document the operational context before a risky change.

Backup and RecoverySeverity: HighLast reviewed: 2026-09-16

Diagnosis

Symptoms, causes, checks, and fixes

Symptoms

  • The team is about to change content, menus, options, users, WooCommerce settings, coupons, products, or plugin configuration.
  • A full file backup is available somewhere, but the immediate risk is database state.
  • Nobody knows whether the backup includes custom tables, WooCommerce order data, serialized options, or recent transactions.

Most Common Causes

  • WordPress stores posts, pages, users, options, comments, taxonomy, and many plugin settings in the database.
  • WooCommerce and other plugins may add tables or store operational records that must be captured with the same timestamp as the change.
  • A database-only backup does not protect media uploads, plugin files, theme files, mu-plugins, drop-ins, or server configuration.

How To Confirm The Cause

  • Name the exact change that needs rollback protection and decide whether database-only coverage is enough.
  • Confirm the database name, table prefix, multisite scope, WooCommerce order window, and any plugin-specific tables involved.
  • Record the backup timestamp, storage location, retention owner, and restore permission before making the change.

Fixes

  • Create the database backup immediately before the risky content or settings change.
  • Use a full backup instead when the work changes files, plugins, themes, uploads, translations, build assets, or server rules.
  • Do not restore a database backup over new live orders, form submissions, users, comments, or content without an owner-approved recovery plan.

How To Verify The Fix

  • Confirm the backup file exists, is readable, and contains the expected tables.
  • Check that the backup timestamp is close enough to the planned change window.
  • For WooCommerce, reconcile whether new orders or payments occurred after the backup before any restore decision.

When To Contact Support

Escalate when database restore may overwrite orders, customers, payments, memberships, subscriptions, learning records, form entries, or other business data created after the backup.

References

Official references

WordPress backup documentationWordPress hardening documentation