- Accounts incremental – Backup cPanel accounts incrementally. The accounts will be copied in full (same as “/scripts/pkgacct”), uncompressed to the specified backup destination.
- Accounts databases – This will only backup account’s databases. Any databases that is not assigned to a cPanel account will not be backed up.
- Accounts incremental cron jobs – This will only backup cPanel account’s cron jobs. Backup is created incrementally.
- Accounts incremental emails – This will only backup cPanel account’s emails (email contents + mailbox settings). Backup is created incrementaly.
- Accounts incremental DNS zones – this will only backup cPanel account’s dns zones (all zones on the cPanel account). Backup is created incrementaly.
- Directories incremental – Backup any folder / files on the server (doesn’t have to be related to a cPanel account) incrementally to the specified destination.
- Replicate – Copy entire folder “as is” to the specified destination.
What’s the difference between “Directories incremental” and “Replicate” ?
The “Directories incremental” job will backup the files keeping a “snapshots” based files structure, so you can have several backup retention of this backup, on supported destinations (SSH / Local / Amazon).
The “Replicate” job, will take the folder “as is”, and cannot save backup retentions. Since we are using rsync, the backup process is optimized and only changes from the last full backup will be copied, but you will not be able to have a backup retention and to create a “backup history” of your files / folders.
Optimizing your backups on supported destinations.
Remote SSH & Local backup can create a “point-in-time incremental backups”. If you activated “backup rotation” – JBM will create a snapshot, in which will use as little space as possible (using hardlinks). So a 30 days backup rotation, of a 2GB cPanel account, will only consume 2GB + 30 Days of new / changed files, and not 2GB x 30.
At the moment, mysql is fully gzipped & dumped, as it doesn’t support incremental backups.