To automate cPanel backups, you have two routes: schedule the backup on the server (a cron job that creates a backup and sends it to a remote FTP or SCP server, if your host allows it), or schedule a program on your own computer to pull your site files over FTP or SFTP and your MySQL databases every night. cPanel's built-in Backup and Backup Wizard pages are manual: they create an archive when you click a button, and nothing happens again until you click it again.
This guide explains what the cPanel tools give you, the server-side and PC-side ways to automate them, and how to keep the copies safe.
What cPanel's backup tools actually do
Most cPanel accounts have two backup pages under Files: Backup and Backup Wizard. They offer the same options in different layouts.
| Backup type | What it contains | Restore it yourself? |
|---|---|---|
| Full account backup | Everything in the account: home directory, databases, email, DNS zones and settings, as one compressed archive | Usually not on shared hosting. It is meant for moving or restoring a whole account, which the host does. |
| Home directory | Your files, including public_html | Yes, from the Backup page |
| MySQL database | One database as a compressed .sql file | Yes, from the Backup page or phpMyAdmin |
| Email forwarders and filters | Forwarding and filter rules | Yes |
When you create a full backup, cPanel lets you choose a destination: your home directory, a remote FTP server, or a remote server over SCP, and it can email you when the archive is ready. That is useful, but it is still a one-off. The tools have no schedule.
Does your host already back up your account?
Often, yes. Many hosts run their own daily or weekly backups, and some add a restore tool to cPanel. Before you build your own system, find out:
- How often the host backs up and how many days it keeps.
- Whether you can restore files and databases yourself, or need to open a ticket.
- Whether backups are included in your plan or depend on account size.
- Where the backups are stored. A copy on the same server, or with the same company, can disappear along with the account.
Host backups are a good safety net. They are not a substitute for your own copy, because you do not control their retention, and if your account is suspended, hacked or closed, you may not be able to reach them.
Option 1: schedule a full backup on the server
cPanel exposes its backup functions through UAPI, its command-line interface, and many hosts let you call it from a cron job. If your host supports it, you can create a cron job under Advanced → Cron Jobs that runs a command such as:
uapi Backup fullbackup_to_ftp variant=passive host=backup.example.com username=user password=secret directory=/backups email=you@example.com
Points to check before relying on it:
- Host permission. Some hosts disable this or limit how often full backups can run, because they are heavy on the server.
- Credentials in plain text. The FTP password sits in your crontab. Use an account that can only write to the backup folder.
- Old copies. Nothing deletes old archives on the remote server, so it fills up unless you clean it.
- Silent failure. If the job stops working, you only find out if you read the emails.
An alternative is a database-only cron job using mysqldump, covered in our guide to automatically backing up a MySQL database. It is lighter, but the copies still live on the server until you move them.
Option 2: pull backups to your own computer on a schedule
The other approach turns the problem around. Instead of asking the server to push backups somewhere, a program on your PC connects to the hosting account and pulls the files and databases down to storage you own.
Rocket Backups does this. It backs up website files over FTP or SFTP and MySQL databases from your hosting account on a schedule, and its website backups are designed to work with cPanel hosting. A typical job:
- In cPanel, create an FTP account (or use your SFTP login if your host supports SSH) with access to your site's folder, and note the MySQL database name, user and password from your site's configuration file.
- In Rocket Backups, create a website backup job and enter the connection details.
- Choose the destination: an external drive, NAS, a second internal drive or your own cloud storage. You can send the same backup to two places.
- Set the schedule, for example nightly at 3 a.m., and how many versions to keep, such as 30 daily and 12 monthly.
- Turn on encryption and email alerts, then run the job once by hand to check it.
After the first run, only changed files are copied, so nightly jobs are quick even for large sites. Every night's files and database dump are kept together, so you can restore a matching pair from any date. Rocket Backups verifies each backup and emails you if a job fails, which is what server-side cron jobs usually lack.
Your PC needs to be on at backup time. If it is off, Rocket Backups catches up the missed backup the next time it starts. If the PC is rarely on overnight, pick a time when it is usually running, such as lunchtime.
Which option is right for you?
| Server cron (full backup) | Pull to your PC | |
|---|---|---|
| Needs host support | Yes, for UAPI in cron | Only FTP/SFTP and database access |
| Contains email and DNS | Yes | Files and databases only |
| Restore it yourself | Usually through the host | Yes, upload files and import the database |
| Old copies cleaned up | Manual | Automatic, by your rules |
| Failure alerts | Completion email only | Email on failure, tray status |
| Independent of the host | If sent off-server | Yes |
Many site owners use both: the host's own backups or a monthly full archive for email and DNS, plus nightly pulled copies of files and databases for fast, self-service restores.
Restoring from your copies
- Pick the date you want, usually the last one from before the problem.
- Upload the files to
public_html(or the site's folder) with an FTP client or cPanel's File Manager. - In cPanel, open phpMyAdmin, select the database, and import the .sql file. For a fresh database, create it and its user first under MySQL Databases.
- Check the site's configuration file still has the right database name, user and password.
If the reason you are restoring is an attack, follow the extra steps in our guide to restoring a website after a hack before you put the site back online.
Good habits for cPanel backups
- Nightly for any site that changes, plus a manual backup before updates.
- At least 30 days of history. Hacks and broken plugins are often found late.
- Two locations, such as a local drive and a NAS or cloud folder, in line with the 3-2-1 backup rule.
- Encrypt backups, because databases contain user data and password hashes.
- Test a restore to a staging site or local server a couple of times a year.
Frequently asked questions
Does cPanel back up my site automatically?
It depends on your host. Many hosts run their own backups, but how long they keep them and whether you can restore them yourself varies by plan.
What is the difference between a full and partial cPanel backup?
A full backup is an archive of the whole account for moving or restoring an account. Partial backups let you download the home directory or individual databases.
Can I restore a full cPanel backup myself?
Usually not on shared hosting. Full account backups are normally restored by the host, while home directory and database backups can be restored from cPanel.
