Backup manager -> Backup Destinations -> (next screen) Click the “Add new destination”.
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.
Choose Backup Engine
JBM Will need to index and read files from this destination. Since each backup engine has it’s own file structure, we will need to know what we are looking for in the destination when we are indexing.
Backups this destination is going to contain
As continues to the backup engine, it will be easier if you can specify what file types are going to be stored there. If for example you are only going to store full account compressed tar.gz files, there is no need for JBM to look for extra backups, and incremental backups – so the indexing will run faster, with less IO.
Download onTheFly limit.
An end user can download his backups from the backup server to his computer. Since we will need to fetch the backups from the destination & prepare them for download, it can take some time, sometimes more then a reasonable “php session” time.
When disabled (set 0 or blank), a download request will be sent to the jobs queue and processed in the background. User is notified once the download is ready.
When enabled, a backup size is required. If for example we set it for 50mb, and the account backup is lower – download job will be processed immediately and not sent the the queue. Backups above 50mb, will be sent to the jobs queue and processed in the background.