Definition
A backup is a stored copy of a website's files and database, kept somewhere other than the live server, that lets you restore the site if it is lost, hacked, broken by a bad deploy or accidentally deleted. A complete backup covers the file tree (themes, plugins and uploads on WordPress, or the build artefact on Jamstack) plus a current database dump, since files without data cannot rebuild a working site. Snapshot systems capture the whole disk at once, good for full-server recovery but harder to restore selectively. Production hosting plans should run automated backups at least daily, keep 7 to 30 days of retention, and store copies off the production server, ideally in a different region, so a provider-wide outage cannot take out both the site and its backups. Managed hosts and major cloud platforms include this as standard. On unmanaged VPS or dedicated servers, setting it up yourself, with BorgBackup, restic, Duplicati or a host snapshot tool, is your responsibility and the most important task.
How it works
A complete backup includes the website files (themes, plugins, uploads on WordPress; the deployment artefact on Jamstack) and a current database dump. Snapshot-based backups capture the whole disk state at a point in time; file-and-DB backups are smaller and easier to restore selectively.
Why it matters
Sites are lost to hacks, bad updates, mistyped commands and provider outages every day. A working backup, regularly tested by actually restoring it somewhere, is the difference between a few hours of disruption and losing the site. Untested backups are not backups.