NOTICE: THIS IS OLD LEGACY DOCUMENTATION FOR JETBACKUP 3.1 (EOL), FOR THE NEWER MOST UPDATED DOCUMENTATION PLEASE VISIT: http://docs.jetbackup.com
Your installation is finished, and you need to setup the product for the first time !
To know what is right for you, You will need to characterize the type of backup you want.
Here are some common backup types –
- Local to remote – cPanel accounts are copied to a remote folder, no local backup are left behind.
- Local to local – cPanel accounts are copied to a specified local folder.
- General files backup – Only backup files (any file on the server, doesn’t have anything to do with cPanel accounts).
- Mysql backups – backup cPanel accounts databases.
JBM Can create your backup using his own internal backup engine. You can also restore from backups created with cPanel’s backup system (legacy backups are not supported), and some other 3rd party backup engines.
How efficient would you like your backups ? Our best recommended setup is as follows –
Local to remote backups, using “SSH” as destination. At first run JBM will create full backup for all accounts, second and after – will copy only changes. Furthermore, If you activated “backup rotation” – JBM will create a “point-in-time incremental backups”, 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 (** At the moment, mysql is fully gzipped & dumpped, as it doesn’t support incremental backups).
What about saving IO & CPU ?
Well, with our native CloudLinux support, you can put the backup process inside LVE. We’ve tested it on crowded servers during peak hours, and it was hardly noticeable (will cost you backup time, as it will run slower – but worth the trouble).
Doesn’t have CloudLinux ? You can still optimize the backup process using rsync’s IO limit, and re-prioritize using NICE & RENICE.