How to Back Up WordPress by WHM Full Account Backups

admin

4 hours ago

How to Back Up WordPress by WHM Full Account Backups backup tutorial showing files database offsite storage and restore verification

How to Back Up WordPress by WHM Full Account Backups is for server owners, web hosts, resellers, and admins responsible for multiple cPanel accounts. Use this method when server-level protection and provider-managed restores when a WordPress site lives inside a larger cPanel account.

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

WHM full account backup configuration 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 WHM as an administrator and review Backup Configuration.
Choose a schedule that matches site change frequency, usually daily for active WordPress sites.
Confirm that account files and MySQL databases are included.
Set retention so old backups rotate before storage fills up.
Use a remote destination whenever possible so a server failure does not take the backups with it.
Run or wait for the next backup, then verify that the account appears in the restore interface.

Automated backups and cron

WHM backups are scheduled at the server level. They do not depend on WordPress traffic or WP-Cron, which makes them more reliable for low-traffic sites and overnight backups.

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

Restore from WHM or ask the hosting provider to restore the account, database, or files. For one WordPress site inside a multi-site account, restore carefully so you do not roll back unrelated domains or email.

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

Keeping backups only on the same disk as production.
Setting retention too high for available storage.
Restoring a whole account when only one database table or upload folder was needed.
Never testing that backups are actually restorable.

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 WHM full account backup configuration 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.