WordPress
WordPress backup restore: what has to come back?
A WordPress backup is only useful if it contains the state needed to reconstruct the site. The database and filesystem carry different parts of that state, which is why saving only one side can produce an incomplete recovery.
The database contains the changing application state
Posts, pages, users, settings, plugin data, WooCommerce orders, comments, and many relationships live in the database. A file-only backup does not protect those records.
The filesystem contains code and uploaded content
Themes, plugins, media uploads, custom code, configuration, and sometimes generated assets live on disk. Some components can be reinstalled, but user uploads and custom changes may be irreplaceable.
Restore into a safe environment first when possible
A test restore proves the archive is readable, the database imports, credentials can be adjusted, and the site can start. It also gives you a place to confirm the restore point before replacing a live site.
Verify application behaviour after restore
Test login, media, forms, email, permalinks, scheduled tasks, ecommerce flows, and any integrations. A restored homepage is evidence that the web server works, not proof that the whole WordPress application recovered.