Secure FTP Replication Target Configuration
The settings for a Secure FTP replication target are nearly identical to those for an FTP replication target, with these differences:
- The server to be configured is an SFTP server.
- The default port is 22.
- There is only one advanced option: Compressed Transfer.
Basic settings:
- Name (Required): The name of the replication target.
- Description: An optional description of the replication target.
- SFTP Server (Required): URL of the FTP server (for example, ftp://ftp.ingeniux.com).
- Port: This field holds a default value of 22.
- User Name: User name for establishing the FTP session.
- SFTP Authorization: Select one of the following from the drop-down list:
- Username/Password: This option requires you to provide a password in the Password field.
- Private Key: This option requires a private key in the Key Location field. Provide an absolute path to the key file (e.g., C:/keyfile/key.ppk).
- Private Key/Password: This option requires you to provide a private key path in the Key Location field and a passphrase in the Password field. In the Key Location field, provide an absolute path to the key file (e.g., C:/keyfile/key.ppk).
Note: To ensure that they're valid, keys should be made with a key generator like PuTTY (download the key generator here).
- Password: Password for establishing the FTP session.
- Root Path: Server location to which files will be replicated. The root path begins at the root of the FTP site and uses forward slashes as delimiters.
- Disabled: Disables the replication target. This is useful for testing purposes, because you can temporarily remove a target without deleting it.
Advanced settings:
- Compressed Transfer: Enables on-the-fly data stream compression. Data is then decompressed on the FTP server. Turning on compressed transfer can speed up file transfer in some cases. For example, some text and image files may be transferred more quickly. But for .jpg files, .zip files, and large movies, the process won't be noticeably faster. Compressed transfer can cause a bottleneck, so use it with caution.