Prepare a WordPress files-and-database backup checklist

Direct answer

A useful backup checklist identifies the components, the responsible person, a restore target and the evidence to retain.

Keep application files, database and configuration in the same recovery conversation.

Illustrative example

Illustrative example: before a theme change, an agency records the media directory, database export method, configuration values held outside the theme, and the person who can judge the restored site.

Work through the decision

1. List the WordPress files, themes, plugins, uploads, configuration and database that the application needs together.
2. Record the backup time, tool version and destination owner without putting secrets in the record.
3. Restore into an isolated target before relying on the backup for a change.
4. Check login, media, forms and the client’s most important public journey.

What this does not establish

A database export and a file copy can have different consistency boundaries; do not call either a full recovery until the compatible set has been tested.

Technical reference: WordPress backup documentation. Check the installed software and operating context before applying any command or change.