NOTICE: JetBackup For Linux is in ALPHA testing stage. Please handle with caution. Any information on this document is subject to change as we continue to develop and make changes.

Getting Started

Your installation is finished. Now you need to setup the product for the first time!

Your first step? Log in to your JetBackup for Linux (with root username and password) by going to https://{hostname/ip}:3030


If you are here to recover from a disaster, please visit Disaster Recovery for the steps.

Then click on "Fresh Installation" to login to your JetBackup panel.

Fresh Installation

Once in the dashboard area, you can start adding a Backup Destination and Database Connections.

We also highly recommend to check out and enable Export JB Config.

Done that? Now you can create 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:

  1. Local to remote - Files/Folders are copied to a remote folder, no local backups are left behind.
  2. Local to local - Files/Folders are copied to a specified local folder.
  3. General files backup - Only backup files (any file on the server).
  4. Database backups - backup you server's databases.

JetBackup can create your backup using its own internal backup engine.

How efficient would you like your backups?

Our best recommended setup is as follows -

Local to remote backups, using "SSH" as a destination. At first run, JetBackup will create a full backup for all accounts. From the second backup job run and on, only new or modified file changes will need to be backed up. Furthermore, If you activated "backup retention" - JetBackup will create "point-in-time incremental backups", in which case it will use as little space as possible (using hardlinks). So for a 30 day backup retention of a 2GB file/directory backup, 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).

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).

Don't have CloudLinux? You can still optimize the backup process using rsync's IO limit, and re-prioritize using NICE & RENICE.