MySQL Server (TCP/IP)

• Place the backups for each database into its own subfolder. By default, backup files are placed in the directory specified as the destination. If this option is enabled, for each database backup or folder backup, a separate directory will be created with the name matching the database (or folder), and the corresponding backups will be stored in this directory.
• Backup one DB, send, repeat (as opposed to backup all, then send all). By default, SQLBackupAndFTP first creates backups of all databases in a temporary folder and then moves the backups from the temporary folder to the selected destinations. If this option is enabled, each backup will be immediately sent to the destinations after it is created. This option is useful if you have limited space for temporary local backup storage.
• Structure. Specifies whether to back up the metadata of the database, such as table definitions and field descriptions within these tables
  
• Data. Specifies whether to include the contents of tables in the backup.

Note, that the Structure and Data options do not contradict each other, and for a classic backup, it is better to leave them enabled.

You can also choose the user under which a backup job will be run. Simply click on the gear icon and add the setting if needed.

In addition to these options, there is an additional settings window accessible via the More settings… link where you can define backup specifics in detail. Please note that recommended settings are already configured. If you make changes, please ensure that you understand their purpose and impact.

Particular attention should be given to these settings:

• Enclose export in a single transaction. If this option is enabled, a separate transaction will be opened to create the backup. This option ensures transactional consistency during backup creation. If any data changes occur during the backup process, these changes will not be included in the backup. The database will appear frozen at the start of the backup, but it will continue to function normally. However, this option only works as described above with tables using the InnoDB engine. InnoDB is the default table engine; we recommend enabling this option if you did not explicitly specify table engines during creation.
• Lock all tables before dumping them. During the backup process, the application will lock all tables to ensure transactional consistency of the backup. If you are using InnoDB for all tables, it is preferable to use the Enclose export in a single transaction option instead of this one.
• Generate statistic histogram. This option adds the flag --column-statistic to the backup creation. However, the ability to specify this parameter was introduced in MySQL relatively recently, and by default, this option is enabled for new versions of mysqldump. However, the database may not support this functionality at all. Therefore, if you encounter an error related to column statistics, try changing this option to No or Default.
• Extra command line parameters. In this field, you can specify any mysqldumpparameters, which will be used when the utility is launched to create the backup.