A dependable backup is a recoverable copy of the website at a known point in time. It protects more than your latest article: your database, media, settings and store records may all be involved. This guide explains what a complete backup needs and why a restore should be planned around changes made since that backup was created.
Understand what must be included A typical WordPress website needs both its database and its files to be restored fully. The database contains content, settings and many operational records. Files include uploads, themes, plugins and configuration. Copying only the WordPress directory does not normally capture the separate database.
A WordPress content export is useful for moving supported content, but it is not a complete site backup. Page revisions are also not a substitute. Your hosting account, mailboxes, DNS and third-party services may need separate arrangements beyond the website backup itself.
Identify your actual backup system Your backup tool may be in the hosting control panel, an approved plugin or a managed service. There is no universal WordPress-core Back Up Now button. Read the handover to identify the provider, schedule, retention and restore contact.
If you cannot locate those details, ask Digital Rebellion to confirm them before you undertake a major change. An assumption that “the host probably does backups” is not a usable recovery plan. Confirm what your actual service agreement includes.
- Include database and files
- Verify completed backup
- Account for newer activity
- Test recovery separately
Check the schedule and retention Choose frequency according to how much data your business could afford to recreate. A mostly static brochure site and a store receiving orders all day have different recovery needs. An overnight backup can still lose today’s orders if it is restored at the end of the day.
Check recent successful backup timestamps, storage location and any failure notices. Keep independent copies according to the agreed plan, with access restricted because backups can contain personal data and secrets. Avoid leaving downloadable backup archives in a public website folder.
Create a pre-change recovery point Before a significant update or structural change, use the approved system to create a fresh backup that includes the required files and database. Wait for completion and inspect the recorded result. A job that has started is not the same as a finished, usable backup.
Record the timestamp, reason and person responsible for the change. Confirm who can restore it if dashboard access is lost. Access to a backup tool only inside the broken website may be insufficient in an emergency.
Plan a restore before pressing the button Identify the problem and the last known good point. Determine whether you need a full restore, a file recovery or a more targeted correction. A full database restore can overwrite newer orders, customer accounts, form entries and content changes.
For a live store, coordinate maintenance and data reconciliation with Digital Rebellion before rolling back. Preserve current data and identify transactions made since the recovery point. Do not assume an old backup can be restored without affecting current business activity.
Test recovery in a safe environment An authorised restore test on a separate environment is stronger evidence than a successful-backup label. Check pages, images, login and important workflows. Isolate test emails and payment behaviour, and restrict access to any copied customer data.
After a real restore, verify the public website, forms, checkout, order records and scheduled tasks. Confirm the backup schedule is still functioning. Keep a short incident record explaining what was restored and what needed reconciliation.
Frequently asked questions Can I restore just one photograph? Some systems support file-level recovery. Use that narrower option when it solves the problem safely.
Does my maintenance package include restores? The scope depends on your agreement. Confirm the service and available recovery points rather than assuming coverage.
