Skip to content

Page index

  1. What a website backup is and what it contains

    What gets saved when someone says they have a website backup, covering the files and the database, and why both halves matter for a restore.

  2. Website files and the database: the two halves of a backup

    Why copying your site's files isn't enough, what the database holds, and how an exported database file fits beside your file backup.

  3. How often a website should be backed up

    How to choose between daily, weekly and before-every-change backups, using what WordPress, NCSC and CISA guidance say about frequency.

  4. Where backup copies should be stored

    Why a backup on the same server as your site isn't enough, and how the 3-2-1 rule and offline copies spread the risk.

  5. Host backups versus backups you keep yourself

    Your host may make backups, but you may still want your own. What one host's documentation says about retention, and how the two compare.

  6. How a restore works, step by step

    What happens when you put a website backup back, in what order, and the usual snags, using WordPress and cPanel documentation.

  7. Testing that a backup actually restores

    How to check a website backup works before you need it, using advice from CISA, the NCSC and the WordPress handbook.