SQL Backup Master Help

SQL Backup Master supports the use of an FTP Server for database backup purposes.

 

To create a Google Drive backup destination within SQL Backup Master, click the Add toolbar button in the Destinations section of the Database Backup Editor window. When prompted to choose a destination, select FTP Server and click the Select button.

 

General Settings

 

The following settings are required in order to locate and authenticate to your FTP server:

 

•Server - The host name or IP address of the computer providing FTP services.

•Protocol - Choose from one of the following:

oFTP - Standard File Transfer Protocol (default port 21).

oFTPS - FTP Over Implicit TLS/SSL (default port 990).

oFTPES - FTP Over Explicit TLS/SSL (default port 21).

oSFTP - SSH File Transfer Protocol (default port 22).

•Port - This can be specified only when using a standard (non-encrypted) FTP protocol.

•Auth type - When using SFTP protocol, allows you to choose between password and private key authentication types.

•Username - The username of your FTP server account.

•Password - The password of your FTP server account. When using the private key authentication type, optionally enter the key password.

•Private key - When using the private key authentication type, allows for entry of private key file path.

•Upload limit - Provides a means of throttling the upload speed. Use this option if you wish to conserve outgoing bandwidth.

•Timeout - Maximum amount of time (in seconds) to await a single server response.

 

Common Settings

 

•Remote dir - By default, SQL Backup Master will upload database backup files into your FTP user account root. Here, you can specify a directory name (e.g. "SQL Backups" or something similar) to use instead. If the directory doesn't already exist, it will be created. You can also specify multiple sub-directories by separating them with a forward slash (e.g. "Apps/SQL Backups").

•Emergency destination - When this option is enabled, the associated backup destination will be used only if all other backup destinations fail.

•Delete backups older than - See Cleanup sub-topic below.

 

FTP/FTPS Protocol Options

 

The following options are available ONLY when using FTP or FTPS protocols.

 

•Connect using passive mode - Uncheck this option if you need to use an active FTP connection (e.g. due to firewall configuration, etc.).

•Connect using extended passive mode - Enable to support extended passive mode connections.

•Accept all TLS/SSL certificates - Use this switch to bypass validation of your FTP server's security certificate.

•Enable keep-alive - When enabled, sends periodic NOOP commands during file transfers.

•Allow SSL/TLS Versions - Enable the SSL/TLS security protocols (and versions) eligible for securing connections.

 

More Options

 

•Write FTP commands to backup log (verbose) - Records all FTP command interactions to the backup log. Should be used only for brief diagnostic periods.

•Attempt to resume broken uploads - Using this option will cause the automatic upload retry mechanism to attempt to resume broken uploads. This is done by reconnecting to the FTP server and checking to see if a partial file already exists; if so, it will be appended for improved performance.

•Use large buffers - This option uses larger buffer sizes during file transfers, which can improve performance in some scenarios. Consider disabling this option for very slow network connections where large block transfers may take an excessive amount of time.

 

Proxy Configuration

 

Use the optional proxy configuration fields to indicate the host, port, and authentication credentials to be used to proxy FTP connections. Note that numerous proxy type option changes depending upon whether you're using standard or secure FTP protocols.

 

Cleanup

 

Each time SQL Backup Master successfully uploads a database backup to a destination, it executes a clean-up procedure.

 

This allows you to automatically remove database backup files that are older than a specified number of days and/or hours.

 

Important: Cleanup operations for a given destination will only affect the database backup files associated with that destination.