WordPress backups: protect files and the database

A WordPress backup is useful only if it covers the right information and can be recovered. A successful backup notification does not tell you exactly what was included.

What needs to be backed up?

A complete backup needs both website files and the database. Content and settings are stored in the database, while uploaded images and extensions are among the files. A WordPress content export alone is therefore not a complete website backup.

Ask these questions

• When was the last complete backup?
• Were files and the database captured in the same backup process?
• Where is the copy stored and who can access it?
• How long are earlier versions retained?
• Who can perform a restore?

Choose a suitable frequency

Consider how much work you could afford to lose. An occasional information page differs from a site receiving daily orders. Maintenance appointments and backup schedules need not match. Have a recent recovery point before major changes.

Include a recovery test

Ask your provider to test a restore in a separate environment. Check pages, images and important functions there. Record the steps and time needed. A backup stored only on the same server does not cover every failure of that server; discuss separate, access-protected storage.

Before restoring

A restore may overwrite newer content or enquiries. Confirm the date and expected data loss before proceeding. Following a security incident, check whether the selected backup was already affected. Protect stored backups from unauthorised access to any customer information they contain.

Help with your website

If you cannot confidently identify the cause, tell us what happened and what changed recently. We will discuss the next appropriate step with you. Request WordPress help.

Tailored WordPress maintenance from €49/month excluding VAT

Further official documentation: WordPress.org.

More practical WordPress guides