• 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.

You can also select the user that will run the backup job. Click on the gear icon and add the setting if necessary.

Aside from these options, there is an additional settings window available through the More settings… link where you can define detailed backup configurations. Please be aware that the recommended settings are already configured. If you make changes, please ensure that you understand their purpose and consequences.

For PostgreSQL, the following options are available:

• Dump file format. Allows you to specify the format of the backup file. The possible options are:
  
  • Plain— Creates a .sql file for database reconstruction. This is an open format that can be opened and edited.
  • Custom— Creates a backup in a special format that can be passed to pg_restore for database restoration. This format type performs compression on-the-fly, and the resulting backup will be compressed immediately.
  • Tar — Creates an archive in .tar format, which can be unpacked using the corresponding utility. The unpacked table data will be stored in separate files.
• Dumps only the data, not the schema. Specifies that SQL instructions for creating tables and indexes should not be included in the backup. This option can be useful for minor space savings if schema changes to the database are not possible.
  
• Dump only the object definition (schema), not data. Only the schema definitions of the data will be included in the backup, without the contents of the tables.
  
• Lock wait timeout. This parameter sets the amount of time to wait if the database is found to be locked at the start of the backup creation.
  
• Clean database objects prior creating them. The backup will include instructions to delete the database objects before creating them during restoration.
  
• Use conditional commands when cleaning database objects. If a database with the same name already exists during restoration, the tables in this database will not be recreated. Therefore, existing data will remain, and the data from the backup will be appended additionally. This option will not affect restoration through SQLBackupAndFTP because the application always clears the database before restoration.
  
• Begin the output with a command to create the database. The command CREATE DATABASE will be added to the beginning of the dump file.
• Do not output command to set ownership of objects. The backup will not include commands to specify the owners of these objects.
  
• Prevent dumping of access privileges. User permissions for objects in the restored database will not be included in the backup. It is recommended not to disable this option, as it could significantly complicate database restoration in the event of a crash.
  
• Extra command line parameters. In this box, you can specify any pg_dumpparameters, which will be inserted when the utility is launched to create the backup.