How do I create a backup job?
Open Backup jobs, choose + New job, pick the source, destination and accounts, choose what to include, and create the job. The Add schedule dialog then opens so you can set when it runs. Encryption is a per-job switch that is off by default.
Create the job
- Open Backup jobs and choose + New job.
- Fill in:
- Job name, for example
nightly-all. - Source: "Panel accounts (cPanel / DirectAdmin / Plesk)" (the default), "MongoDB (standalone databases)" or "Directory / system files". See Directory and MongoDB jobs.
- Panel type: the panel on this server (cPanel / WHM, DirectAdmin or Plesk). This field is not shown for MongoDB and Directory sources.
- Destination: where the backups go. The console form picks a single destination.
- Accounts: "All accounts", "Selected accounts" or "All accounts except…".
- Content to back up: Files & directories, MySQL databases, Email accounts, DNS zones, SSL certificates. All are on by default.
- Exclude files & folders (optional): one pattern per line, relative to the account's home folder, for example
public_html/cache/*. See Exclude files and folders. - Email a status report for this job (optional): see Alerts and notifications.
- Encrypt backup data (optional, off by default): see below.
- Job name, for example
- Choose Create job. The Add schedule dialog opens by itself. See Schedules and retention.
A job with no schedule runs only when you start it, and then it is always a Full backup.
Choosing accounts
- All accounts includes every account on the server, including ones created later.
- Selected accounts takes only the ones you tick.
- All accounts except… takes everything but what you tick.
- Account filters can also use reseller, package and suspended state. A suspended account is backed up and restored properly.
On a server with no panel, every first-level folder of /home is an account. See Servers with no control panel.
Encrypt backup data
With Encrypt backup data on, file contents, databases, mail, SSL private keys, password hashes and crontabs are sealed with AES-256-GCM before they reach the destination. Turn it on when you create the job. If you switch it on later, it applies to new backup points only; files that have not changed are carried over from earlier points and can stay unencrypted until those points are removed. To be sure everything is encrypted, create a new job with the option on. Encrypted backups can be restored only with this server's master key, so set up Disaster Recovery first. See Encrypt your backups.
Good to know
- The first backup of an account reads everything. Later backups read only what changed.
- If you switch off SSL certificates, SSL private keys are not stored. Without encryption, a job's manifests hold SSL private keys and password hashes in the clear.
- Switching Files & directories off backs up no home files.
- Only one backup runs per server at a time; other jobs wait.