Care / FIELD NOTES

DEVBD JOURNAL / PRACTICAL ADVICE

A WordPress backup you can actually restore.

Build a practical maintenance routine around complete backups, safe updates, and a tested way back.

A useful place to start · YOUR SITE, IN GOOD HANDS.

Build a practical maintenance routine around complete backups, safe updates, and a tested way back.

Care / FIELD NOTES

ONE LESS THING TO REMEMBER

M

✓

T

✓

W

✓

T

✓

F

✓

S

✓

S

✓

ILLUSTRATIVE CARE CHECKLIST

A PLAIN MONTHLY REPORT

READ IT. USE IT. GET ON WITH YOUR DAY.

ILLUSTRATIVE GUIDE

4 min

A practical read

Care

The topic

Plain

English. Clear steps.

DEVBD / UPDATED 27 OCTOBER 2026 / CARE

A green backup notification is useful, but it does not tell you whether you can get your business back online. I want three clear answers: what was saved, where it is stored, and how it will be restored. You do not need an elaborate system to start. You need a routine that someone owns and checks.

Choose how much recent work you can lose

A brochure site changed once a month has different needs from a shop taking orders all day. Decide how much lost work would be acceptable, then choose a backup schedule that reflects it. Daily backups may suit a quieter site; a busy store may need much more frequent protection. Ask your host or backup provider what its schedule actually covers, rather than assuming every change is saved immediately.

Save both parts of WordPress

A normal WordPress site needs its files and its database. Files include themes, plugins, uploads, and configuration. The database holds content, settings, and other records. Downloading the WordPress folder alone usually does not capture that database. Keep the two parts together as a dated backup set. The official WordPress backup handbook explains the difference.

Keep several restore points and a copy away from the live hosting account. Confirm that you can access it if the website or hosting login stops working. Protect backup access as carefully as the site itself: the archive may contain customer information and configuration secrets.

Test a restore away from the live site

Ask your host for an isolated test environment, or have your developer create one. Follow the backup tool's restore instructions and use the matching files and database. For manual database restores, WordPress documents the import process in Backing Up Your Database. Do not experiment by overwriting your working production database.

Open important pages, check images, log in, and test the functions your business relies on. Keep customer emails, payment actions, and external automations disabled in the test copy. Record how long recovery took and anything missing. WordPress.com's staging guide describes the principle of a separate testing copy; the controls available on your host may differ.

Make updates a checked process

Before a significant update, confirm that you have a current backup and a recovery path. Review compatibility notes, test changes on a staging copy where available, then check the live site's important journeys. Forms, checkout, bookings, and account access deserve more attention than the dashboard's update count. The official WordPress update instructions recommend a backup before updating.

Know what a rollback would replace

A database restore takes records back to the selected point. Orders, enquiries, accounts, or edits created afterwards may be lost if they are not separately preserved. Agree the recovery point before restoring a busy site and ask for help reconciling new transactions. If a hack caused the problem, restoring an old copy does not by itself fix the original weakness.

Keep a short maintenance record

  • Last successful backup and last tested restore.
  • Updates applied and important functions checked.
  • Any failure, who owns it, and the next action.
  • Where recovery instructions and support contacts are stored.

Review access, monitoring, and recovery responsibilities with your host. The WordPress hardening handbook treats security as reducing risk, with preparation and monitoring as part of the work.

Prefer to have the routine handled? DevBD care plans start at $79/month, with daily offsite backups, updates, monitoring, and a plain monthly report.

← All field notes

§ ✱

YOUR FREE SITE CHECK

Free WordPress Site Check: Find Out What Is Holding Your Site Back

Send me your website address. I look at your security, plugins, mobile speed, forms and basic SEO. Within 24 hours you get a short written report in your client portal. It lists the top 3 problems, with screenshots, in plain English.

You decide what happens next. There is no pressure and no sales call. Site hacked or down? Choose urgent help and I will reply within 4 hours.

24h

STANDARD REPLY

4h

URGENT REPLY

$0

SITE CHECK

Prefer email? [email protected] ↗

DevBD Audit

NEW REQUESTREPLY WITHIN 24H