Creating new backup job

Creating new backup job

At the following screen press “Add new job”.

Creating new backup job

After clicking “Create new job” button, you should get this result:

Creating new backup job

Job Name

A generic name for your internal ease of use, so it will be easier to recognize the backup destination roll, in case you have more then one.

Job Type

Choose the most suitable type for this job: Accounts incremental, Accounts Databases, Directories incremental, replicate.

Click here for more information about the job types ->

Destination

Choose a backup destination in which the backups will be copied to.

Click here for adding a destination guide ->

Remote folder on destination

Files will be copied to this folder on the remote destination.
Can be useful to separate each job to it’s own folder if using several jobs in one destination.

Backup suspended accounts

YES – Will backup cPanel suspended accounts

NO – Will skip suspended accounts

Accounts

Choose which accounts to backup, or specify certain criteria ( click here for more information about accounts backup -> )

Directories and files to exclude

This exclude list will be piped to rsync. As rsync’s exclude option doesn’t really support regex, it’s more of a shell globbing pattern matching.

You can review our recommended exclude list here.

Each exclude should be separated with new lines.

Schedule type

Choose how to schedule this job to run: Daily, Weekly, Monthly, After other job is done, After cPanel backup job is done, manually.

Click here for more information about schedule types ->

Backup Retention

How many backups to save ? JBM Will use hardlinks on supported destinations to save space & IO.

For example, For a daily backup with 14 backup retantion, you should choose –
Daily, Run on all days of the week, 14 days retantion.

Schedule Time

Choose your prefered time for the job to be executed.

You can also limit the backup time, Meaning a job can start at 01:00, and will end at 04:00. When the ending time limit reached, the backup will stop the backup job, and will continue from this point in the next run. This can be very useful on heavy loaded servers when you must control the backup times. On tight schedule times, you might not backup all the accounts, but since JBM knows how to continue from the last point, you can assure each account will get his backup over time.

Index backup files (clear cache)

You can choose to clear the index cache before / after the backup runs.
Default clear cache settings can be set under “Settings” -> “General settings”

Performance overide

Override JBM default performance settings for this specific job. Performance settings can be set at “Settings” -> “Performance settings“.

With our native CloudLinux support, you can put the backup process inside LVE. For servers without CloudLinux, you can still optimize the backup process using rsync’s IO limit, and re-prioritize using NICE & RENICE.

Health Check

Notify me if the backup’s job last run is greater then X days. Can be useful to track faulty backups that from some reason didn’t run.

Pre-Job Scripts

Bash scripts to run before this job start.
Separated with new line. Example –
/scripts/pre-backup.sh

Post-Job Scripts

Bash scripts to run after this job start.
Separated with new line. Example –
/scripts/post-backup.sh