How to Recover a Site When the Host Deletes Your Backup
If your host deleted your backup, your own copy is now the primary source, and the host's infrastructure is only a secondary one. Recover in this order: stop writes to the live site, capture evidence of the deletion, then work outward from your own copies to caches, mail, DNS, and finally the host's raw storage. The phrase "the host deleted my backup" usually means the retention window on their side expired or an account action purged it, so assume nothing on their side is recoverable until you have proof otherwise.
First, freeze the site and capture evidence that the host deleted your backup
Every write to the live filesystem or database reduces what is left to recover. Put the site into maintenance mode, or at minimum revoke write access from the application user, before you do anything else. If the site is still serving, take a filesystem snapshot at the provider level if that option exists, and a database dump if the database is still reachable.
Then collect evidence. Open a support ticket in writing, not chat, and ask three specific questions: what backup jobs ran against this account, what the retention policy was at the time, and whether any copy exists in cold storage or offsite replication. Ask them to confirm the deletion in writing. That confirmation matters later if you need to escalate, and it also tells you whether to keep digging on their side or move on.
Pull what you can from your own records. Your control panel or API may expose a backup listing endpoint. If the provider has an API, query it and save the JSON response with a timestamp. If you have shell access, check for any local archives before they are cleaned up:
find / -xdev \( -name "*.tar.gz" -o -name "*.sql.gz" -o -name "*.zip" \) -mtime -90 2>/dev/null | head -50
# typical output:
# /home/site/backups/db-2024-11-02.sql.gz
# /var/backups/account-export.tar.gz
Save that listing to a file outside the account. Even an empty result is evidence that no local copy survived.
Work outward from your own copies before touching the host again
Most recoveries succeed here, not with the host. Start with developer machines and any staging environment. Search for database dumps and archived site roots by name and modification time. Check version control: if the site root was ever committed, even partially, the repository gives you templates, configuration and often the theme or plugin code, which is the slowest part to rebuild by hand.
Next, the caches. A full page cache or CDN edge cache can hold rendered HTML, and sometimes static assets, for every URL that was requested recently. If the CDN exposes a cache purge or listing API, enumerate cached URLs and fetch them before purging anything. Rendered HTML will not restore your database, but it recovers content, structure and copy quickly.
Then check your own mail and notes. Many hosts email a backup link or attach an export when an account is migrated or closed. Search for the domain name across mail archives and download anything you find. Also check whether a search engine still serves cached copies of key pages, and whether the Internet Archive has snapshots; both help with content, neither with application state.
Finally, DNS. If the domain still resolves, the zone file tells you the original record set, which is useful when rebuilding. Pull it if your registrar allows a zone transfer or an export:
dig +short AXFR example.com @ns1.example.net
# or, if AXFR is refused, export from the registrar panel:
# example.com. 3600 IN A 203.0.113.10
# www 3600 IN CNAME example.com.
# @ 3600 IN MX 10 mail.example.com.
Record the current TTLs and addresses before you change anything, so you can rebuild the zone faithfully.
Ask the host the right technical questions about retention
When you go back to the host, be specific about mechanisms rather than asking vaguely for "the backup." Backups usually live in one of a few places: object storage buckets with lifecycle rules, snapshot volumes attached to the instance, or a separate backup appliance. Each has a different recovery path, and support staff often only see the first.
Ask whether the account's object storage bucket still holds backup objects under a lifecycle policy that has not yet purged them, and whether deleted objects are recoverable from versioning or a trash area. Ask whether block storage snapshots still exist even if the filesystem was wiped. Ask whether the database server keeps binary logs or point in time recovery archives outside the account. On a managed database, binary logs are frequently retained separately from the customer backup schedule, and a binlog plus one base dump is enough to replay to the moment before deletion.
If the host confirms nothing exists, ask for the retention policy text that applied to your plan. That document tells you whether the deletion was within policy or a mistake. If it was a mistake, you have a stronger case for escalation to a supervisor or a formal complaint; if it was within policy, the answer is to rebuild and change your own process.
Rebuild with the backup problem fixed permanently
Once you have any base copy, restore it somewhere isolated, not over the live site. Verify the database imports cleanly, check that file ownership and permissions match the application user, and confirm the application boots before pointing traffic at it.
The durable fix is to stop treating the host's backup as a backup. Keep at least one copy entirely outside the provider's account, in storage you control, written by a scheduled job that you can verify. A simple pattern is a nightly dump, an encrypt step, and an upload to separate object storage under a different account:
pg_dump -Fc appdb | gpg --encrypt --recipient [email protected] \
| aws s3 cp - s3://offsite-backups/appdb/$(date +%F).dump
# then verify the object exists and is non-trivial in size
aws s3 ls s3://offsite-backups/appdb/ | tail -3
Test a restore from that copy on a schedule. A backup you have never restored is a guess, and the whole point of this exercise is to never again depend on someone else's retention window.
What to do next: open the written ticket today and ask the three retention questions before anything else changes, then run the local archive search and the offsite copy check in parallel. If the host confirms deletion, restore your best base copy into a staging environment, verify it, and only then cut over. Keep every written reply from the host; it is your record if you need to escalate.
