NOTICE: This Documentation is for JetBackup 4 for Linux.

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


This guide shows how to set up a connection from your JetBackup server to a MySQL database.


  1. MySQL server installed on the database server.
  2. MySQL client installed on the JetBackup server.
  3. For databases on a WAN IP, make sure you have access to the database port.
  4. User with all privileges for all databases.

Create database Connection

  1. Specify "Type" as "MySQL".
  2. Enter a name for your MySQL Database Connection.
  3. Enter your remote database hostname and your database username and password.
  4. Click the "save" button.

An example configuration page for the database connection:

mysql database connection

Database Name

A generic name for your internal ease of use, so it will be easier to recognize the database connection in case you have more than one. Max length is 40 characters.


The hostname/ip where the MySQL database is hosted.


Your remote database port (default port is 3306 - you must specify this even if it's 3306).

Please make sure that the port you are using for MySQL database connection is open in your database server firewall.


Name of the MySQL database user.


Password of the MySQL database user.

Dump gtid purged

This option enables control over global transaction ID (GTID) information written to the dump file, by indicating whether to add a SET @@GLOBAL.gtid_purged statement to the output. This option may also cause a statement to be written to the output that disables binary logging while the dump file is being reloaded.

Dump max allowed packet

The maximum packet length to send to or receive from server

Dump force flag

Continue even if we get an SQL error

Dump opt flag

Same as --add-drop-table, --add-locks, --create-options, --skip-opt.

Dump skip lock table flag

This option tells the mysqldump utility not to issue a LOCK TABLES command before obtaining the dump which will acquire a READ lock on every table.

Dump single transaction flag

This option sets the transaction isolation mode to REPEATABLE READ and sends a START TRANSACTION SQL statement to the server before dumping data. It is useful only with transactional tables such as InnoDB, because then it dumps the consistent state of the database at the time when START TRANSACTION was issued without blocking any applications.