Every hosting provider claims to offer backups, but few website owners actually know how to use them until disaster strikes — a hacked site, a bad plugin update, an accidental deletion. Understanding the process before you need it saves critical time during an actual emergency.

Types of Backups in cPanel

  • Full account backup: everything — files, databases, email accounts, settings — in one archive, typically the largest and slowest to generate.
  • Home directory backup: website files only, without databases or email.
  • Database backup: just the MySQL/MariaDB databases, useful for quick content-only recovery.
  • Automated provider backups: many hosts run daily or weekly backups automatically — confirm your provider's specific schedule and retention.

Creating a Manual Backup

  1. Log into cPanel and open the "Backup" or "Backup Wizard" section.
  2. Choose a full or partial backup depending on your need.
  3. Download the resulting archive to your own computer or cloud storage — never leave the only copy on the same server being backed up.

Restoring From a Backup

  1. For a full disaster recovery, use the Backup Wizard's restore function and upload your saved archive.
  2. For a database-only issue, restore just the database via phpMyAdmin's import function.
  3. For file-only issues, use File Manager or FTP to restore specific files from your backup archive.
  4. Always test the site thoroughly immediately after any restore.

A Real Disaster Recovery Walkthrough

Consider a WordPress site where an incompatible plugin update produces a white screen with no visible error. The fastest recovery path: log into cPanel Backup Wizard, confirm the most recent automated backup predates the update, and restore the home directory (files only, since the database is unaffected) — this reverts the plugin files to their pre-update state without touching orders, posts or settings stored in the database. Total time from discovery to a working site again, with a same-day automated backup available, is typically under twenty minutes: the actual restore runs in the background while you confirm the correct backup date, and the site is testable as soon as it completes. This is the specific scenario a daily backup schedule is designed to make routine rather than stressful.

Building a Real Backup Strategy

  • Do not rely solely on your host's automated backups — verify what their actual retention window is.
  • Keep at least one backup copy stored completely off the hosting server.
  • Schedule backups more frequently for actively updated sites (e-commerce, active blogs) than for static brochure sites.
  • Actually test a restore occasionally — an untested backup is not a reliable backup.

Automating Off-Site Backups

Beyond whatever your host provides, a second, independent backup layer meaningfully reduces risk — if the hosting account itself is ever compromised, an attacker with account access could in theory affect on-server backups too. WordPress plugins like UpdraftPlus can schedule automatic backups directly to Google Drive, Dropbox, or Amazon S3 on a recurring interval, completely independent of the host's own backup system. For custom applications, a simple scheduled cron job running a database dump and an off-server upload (via rclone or a similar tool) achieves the same independence with a few lines of script. The specific tool matters less than the principle: your most important backup copy should not live only on the server it is protecting against.

Frequently Asked Questions

How long does my host keep automated backups?

This varies significantly by provider and plan tier — ask directly rather than assuming, since retention windows are often shorter than expected.

Can I automate my own backups beyond what the host provides?

Yes — several WordPress plugins and cPanel-compatible tools can schedule automatic backups to external cloud storage independent of your host's own backup system.

What is the difference between a backup and a snapshot?

In hosting contexts the terms are often used loosely, but a "snapshot" (common on VPS/cloud hosting) typically captures the entire server state at a point in time, while a "backup" more often refers to a portable archive of files and databases — both serve recovery purposes, but a snapshot usually restores faster while a backup archive is more portable between providers.

Should I keep more than one backup copy at a time?

Yes — keeping only the single most recent backup means a slow-developing problem (like a gradual database corruption) can quietly get backed up too, overwriting your last clean copy. A rolling history of several recent backups protects against that.

Need help with backups or disaster recovery? See our hosting plans or ask our support team about our backup policy.