Ownership
How to take a full site backup
Export the files, the database and the DNS zone, store them somewhere your host does not control, and restore one to a test environment. A backup you have never restored is a hypothesis, not a backup.
Before you start
- Hosting control panel access
- Somewhere off-host to store the archive
The steps
-
Step 1: Download the files
Via cPanel File Manager, FTP or SSH. The whole document root, including hidden files such as .htaccess.
-
Step 2: Export the database
phpMyAdmin → Export → SQL, or mysqldump over SSH. A file backup without the database restores an empty site.
-
Step 3: Export the DNS zone
From your DNS provider. Rebuilding records from memory after a failure is slow and error-prone.
-
Step 4: Record the credentials list
Registrar, host, DNS, email, payment gateway, analytics. Not the passwords — where they live and who controls them.
-
Step 5: Store it off-host
Your own machine plus cloud storage. A backup on the same server as the site is not a backup.
-
Step 6: Restore it somewhere
A local environment or a staging subdomain. This is the step that reveals whether the backup is actually complete.
-
Step 7: Automate and verify
Scheduled backups, with a calendar reminder to test a restore quarterly.
Why host backups are not enough
They protect against your mistakes, not against losing the account. A billing failure, a terms dispute or a provider going under takes the site and the backups together — which is precisely the scenario a backup exists for.
What a static site simplifies
There is no database, and the source lives in version control. The backup is the repository, which is already off-host and already versioned. It is one of the underrated operational benefits of static generation.
The background behind this
Who actually owns your website — a checklist you can verify today covers the reasoning in about 3 minutes — free, ungated, written from client work.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada, Ireland and Pakistan. These procedures are the ones I run on client work, written down rather than invented — including the ones where the honest answer is that the fix is not available on your current hosting.