Local folder destination will be the fastest destination if there is no remote/local network involved.
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 than one. Max length is 40 characters.
JetBackup will need to index and read files from this destination. Since each backup
engine has it's own file structure, JetBackup will need to know what to look for
in the destination when indexing the backups.
Selecting cPanel as the Backup Engine allows JetBackup to index cPanel generated backups
on the destination which allows you and your clients access and restore from these backups
through the JetBackup interface. For full incremental backups generated with the cPanel Engine,
JetBackup intelligently indexes these backups to its appropriate parts(Databases, Emails etc.)
allowing you and your clients to restore full and individual parts of the backup.
With this option selected, you can schedule when to reindex the destination for backups.
It is recommended to schedule it after the cPanel backup is done to ensure the most accurate data.
Please note that this does not let JetBackup generate backups using the cPanel Engine.
This will be our starting point when accessing this destination.
Make sure to start with "/".
Always use the absolute path, for example, /path/to/backupfolder.
If you are setting up a local Destination pointing to a directory mounted with NFS, only NFSv3 and NFSv4.1 are supported. Please note that custom NFS/Mount configurations can cause issues with JetBackup. Due to the many custom NFS/mount configurations available, we only provide support for NFS v3 or v4.1 mounted with default options.
This option checks if the destination's disk space has reached the specified limit before it executes the backup. When enabled, JetBackup will not perform the backup when the used disk space is over the specified limit.
Limit rsync bandwidth.