How to Back Up WordPress by JetBackup in cPanel or Hosting Panels

admin

4 hours ago

How to Back Up WordPress by JetBackup in cPanel or Hosting Panels backup tutorial showing files database offsite storage and restore verification

How to Back Up WordPress by JetBackup in cPanel or Hosting Panels is for hosting customers and providers where JetBackup is installed in cPanel, DirectAdmin, Plesk, or another supported panel. Use this method when provider-managed daily backups, self-service restores, database restores, file restores, and migration safety nets.

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

JetBackup 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 the hosting control panel and open JetBackup.
Review available backup types such as full account, home directory, files, databases, and email depending on host configuration.
Check the backup dates and retention window before making changes to WordPress.
Download a backup or create an on-demand backup if your host allows it.
For WordPress recovery, identify both the site files and database backup.
Use restore options carefully and confirm whether the restore affects one file, one database, or the full account.

Automated backups and cron

JetBackup schedules are usually controlled by the hosting provider or server admin. Customers should know the retention window, backup frequency, and whether on-demand backups are allowed.

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 the appropriate JetBackup section. For a WordPress site, a database-only restore may roll back posts/orders/forms while files remain current, so match restore scope to the incident.

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

Assuming JetBackup exists on every cPanel server.
Not knowing the retention window until after an incident.
Restoring the database without warning WooCommerce about lost orders.
Never downloading a critical backup before a risky update.

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 JetBackup 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.