How to Back Up WordPress by cPanel Backup Wizard

admin

4 hours ago

How to Back Up WordPress by cPanel Backup Wizard backup tutorial showing files database offsite storage and restore verification

How to Back Up WordPress by cPanel Backup Wizard is for shared-hosting users, small businesses, and anyone who has cPanel but does not want to install another WordPress plugin. Use this method when before core, plugin, theme, PHP, or DNS changes when you want a panel-level backup you can download.

A good WordPress backup includes the website files and the database. The files carry themes, plugins, uploads, configuration, and custom code. The database carries posts, pages, users, settings, WooCommerce orders, booking records, form entries, menus, and plugin data. Before you change WordPress core, PHP, DNS, plugins, themes, checkout, or a page builder, make sure you know which backup contains both halves.

When this backup method makes sense

cPanel Backup Wizard is a good fit when you already have that tool available and need a practical restore path. It is especially useful before updates, redesign work, hosting migrations, malware cleanup, PHP changes, database work, and plugin troubleshooting.

Before you begin

Confirm the WordPress URL and document root so you back up the right site.
Find the database name in wp-config.php or the hosting panel.
Check free disk space; many backup failures start with a full account.
Pause risky work until the backup finishes and you can see the file.
For stores and booking sites, note the last order, booking, or form entry before the backup.

Backup steps

Log in to cPanel and open Backup Wizard under Files.
Choose Back Up, then decide whether you need a Full Backup or partial backups.
For a WordPress-only safety copy, download the Home Directory backup and the matching MySQL database backup.
If you generate a Full Backup, save it off the server after cPanel finishes creating the tarball.
Write down the database name from wp-config.php so you know which SQL file belongs to the site.
Store the backup somewhere outside the hosting account, then verify that the archive opens on your computer.

Automated backups and cron

cPanel Backup Wizard is mainly a manual safety-backup tool. If you need scheduled backups, use WHM backup configuration, JetBackup, Softaculous, Installatron, a WordPress backup plugin, or your hosting provider backup system.

For WordPress plugin backups, remember that WordPress scheduled tasks often depend on WP-Cron. WP-Cron runs when WordPress receives traffic and notices a task is due. That is fine for many small sites, but low-traffic sites can run late. For business-critical sites, pair plugin schedules with a real server cron, hosting-panel backups, or provider backups where available.

How to test restore readiness

A cPanel Full Backup is usually restored by the hosting provider or WHM, not automatically from inside normal cPanel. Partial backups can restore home directory files or MySQL databases, but test carefully because restoring the wrong database can overwrite newer content.

Do not test your only restore for the first time during an outage. Use a staging copy, temporary subdomain, local development environment, or provider restore preview when available. After restore, check login, home page, important pages, media, forms, checkout, email delivery, permalinks, and cache behavior.

Common mistakes

Only downloading files and forgetting the database.
Leaving the only backup inside the same hosting account.
Assuming a cPanel Full Backup can always be self-restored from regular cPanel.
Trying to back up while the account is over disk quota.

Where to store the backup

Keep at least one copy outside the web server. Good destinations include your own Google Drive, Dropbox, OneDrive, S3-compatible storage, Backblaze B2, Wasabi, SFTP, a provider backup vault, or a secure internal backup server. The exact tool matters less than the restore test, retention policy, and separation from the production account.

Fix I.T. Phill recommendation

Use cPanel Backup Wizard as one layer, not the whole plan. Keep a second backup path for important sites, especially WooCommerce, bookings, memberships, and agency-managed sites. Before major updates, take a fresh manual backup even if automatic backups are already scheduled.