NOTICE: This Documentation is for JetBackup 4 for Linux.

Please CLICK HERE for the latest JetBackup 5 for Linux Documentation.


The File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files from one host to another host over a TCP-based network, such as the Internet. JetBackup supports remote FTP backups. This destination is used to copy files/folders from your local server to a remote FTP location.

An example configuration page for the destination:

create FTP destination

Destination Name

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.

Backup Directory

This will be our starting point when accessing this destination.
The path is relative to the remote user's home dir.
/home/USERNAME will be your starting point.
Write your path to where you want the backup to be stored.

Please make sure that your destination path is secure and has the appropriate privileges.
For more information click on How To Secure Local Backup Storage.

Remote Host

A simple hostname or IP address to access the remote backup server.


Your remote port. Default port is 21.

Remote Username

The remote user to login with. It is recommended to create a dedicated user for backups and not use root user.

Remote Password

Password for the provided ssh user.
JetBackup will create all necessary keys for remote login on the remote server.

Connection Timeout

Timeout for the connection. The default value is 30 (The connection time out in seconds), you can increase this if the connection to the remote server is poor and you might face longer timeout issues.

Maximum connection retries

The maximum number of failed connections attempts (Insert 0 for unlimited).

Maximum concurrent connections

The maximum number of connections at the same time (Insert 0 for unlimited).

Secure SSL-FTP connection

Opens an explicit SSL-FTP connection.

Passive FTP

In an active mode configuration, the server will attempt to connect to a random client-side port. So chances are, it will be blocked by the firewall. Usually, a passive configuration will not pose a problem and it's the default one.