A website recovery plan has two halves: backups you make before anything breaks, and a written sequence your team follows when something does. Hacking, human error, software conflicts, hardware failure and hosting trouble can all take a site down.
Step 1: List everything that needs a copy
- Site files: every PHP, HTML, CSS and JavaScript file, plus images and other media.
- Database: content, user data, orders and settings.
- Email: include it when it lives on the same server as the site.
- Configuration: document server settings, SSL certificates and DNS records.
Step 2: Follow the 3-2-1 rule
Keep 3 copies of your data, meaning the original and 2 backups. Use 2 storage types, such as the server plus cloud storage or an external drive, and keep 1 copy off-site, away from that server and its data center.
Step 3: Automate the schedule
Daily automated backups are the minimum, and stores or busy sites should run them every few hours. These tools can handle it:
- cPanel backups: built into most hosting plans, with automated daily options.
- UpdraftPlus: a free WordPress plugin that sends backups to cloud storage on its own.
- ServerPilot and RunCloud: managed server panels with backups built in.
- Custom scripts: cron jobs that build compressed archives and upload them to the cloud.
Step 4: Test a restore every month
Restore a backup to a staging environment once a month. Confirm that pages load, forms submit, database queries return the right data and media files display, because a backup you have never restored is one you cannot trust.
AppWT applies the same rule to its own site. Before any file on appwt.com is edited, a backup copy is taken, restored to a scratch folder and compared byte for byte with the original, and a guard refuses the edit until that backup exists.
Step 5: Write the recovery sequence down
Document the steps so anyone on your team can carry them out:
- Assess what failed and why.
- Update customers through a status page or social media.
- Restore the most recent clean backup.
- Test every critical feature to confirm the site works.
- Find the root cause so the failure does not repeat.
- Record what happened and what the team did.
Need backups set up? Contact us about server management support.
Tags
Frequently Asked Questions
How often should the backup step run?
Every business site needs automated backups at least once a day. Online stores and sites that change often should back up every few hours, and 30 days of history lets you return to any point in the past month.
Where should each backup copy live?
Use the 3-2-1 rule: 3 copies on 2 types of storage, with 1 kept off-site. A typical setup pairs the server with a separate cloud service such as Amazon S3, Google Cloud or Dropbox, plus optional local storage, and never relies on the website server alone.
How do I run the monthly restore test?
Load a backup onto a staging environment and check that every page opens, forms work, database queries return the correct data and media files appear. If a backup has never been tested, treat it as untrusted.
Enjoyed this article?
Share it with your network









