Once you have finished with the JetBackup 5 Installation, it is time to setup the software for the first time!
Log in to your Admin Panel and navigate to JetBackup. When you open Jetbackup for the first time, you will be greeted with the JetBackup End User License Agreement. Once you have reviewed and agree to the terms in our EULA, select "I agree to those terms" to accept the EULA agreement and proceed with the initial setup.
The JetBackup for Linux Panel can be accessed at https://{hostname/ip}:3035
with the same login as root. Please also ensure that Port 3035 is open on the server.
If you are here to recover from a disaster (re-installing JetBackup after an entire data loss event), please visit Disaster Recovery for subsequent steps.
If you have an existing Jetbackup configuration on your server, please click on "Exit DR" to keep you exisiting configuration.
OTHERWISE, select "New Installation" to login to your JetBackup panel with a clean installation and default configuration.
Once in the Dashboard area, you can start adding a backup destination. This will serve as the storage location(s) for your backups.
Next, we highly recommend enabling Export JB Config on a destination to backup you JetBackup configurations and settings which allows for a more seamless Disaster Recovery.
Now you can start creating your backup job. To know what is right for you, you will need to characterize the type of backup you want.
Here are some common backup types:
Take time to review your JetBackup Settings to further adjust and finetune JetBackup to your needs! Here is a shortlist of settings we recommend for you to check out:
Our best recommended setup is as follows:
Local to remote backups, using "SSH" as your storage destination. At first run, JetBackup will create a full backup for all accounts and on subsequent runs, only new or modified file changes will need to be backed up. Furthermore, If you activate "backup retention" - JetBackup will create "point-in-time incremental backups" which uses as little space as possible (using hardlinks).
So for a 30 day backup retention of a 2GB account, it will only consume 2GB + 30 Days of new/changed files (** At the moment, mysql is fully dumped as it doesn't support incremental backups).