FXP Server To Server

API

• TransferFile() - Transfer the specified file from the source FTP Server to the destination FTP Server using the FXP protocol. Returns FtpStatus to indicate success, skipped or failed. Exceptions are thrown for critical errors. Supports very large files since it uploads data in chunks. Optionally verifies the hash of a file & retries transfer if hash mismatches. Provides detailed progress tracking and metrics via callbacks by sending an FtpProgress object.

• TransferDirectory() - Transfers the specified directory from the source FTP Server onto the remote FTP Server using the FXP protocol. You will need to create a valid connection to your remote FTP Server before calling this method. If any rules are provided then we only upload the files and folders matching all the rules. Returns one FtpResult per file or folder, containing its detailed transfer status. All exceptions during uploading are caught, and the exception is stored in the related FtpResult and uploading continues. Optionally verifies the hash of the files & retries transfer if hash mismatches. Provides detailed progress tracking and metrics via callbacks by sending an FtpProgress object.

Settings

• All the file transfer settings are also applicable for FXP transfers.

• FXPDataType - Controls if the FXP server-to-server file transfer API uses Binary or ASCII mode. Default: Binary.

How does FXP transfer work?

FXP works by creating a data connection between two FTP servers. FluentFTP can then instruct the source server to start transferring the file and instruct the target server to receive and store it.

You need to call the API in this order:

1. You need to create an FtpClient instance and connect to the source server
2. You need to create an FtpClient instance and connect to the target server
3. Call source.TransferFile or source.TransferDirectory on the source FTP client and provide the target server's FtpClient to make an FXP connection between them

How is FXP implemented internally?

The order of FTP commands is as follows:

1. We connect to the source server
2. We clone the connection of the target server (and reconnect to it)
3. Internally, we open a passive FXP connection between the source server and target server
4. We maintain an FtpFxpSession object used to track the active FXP connection between 2 servers
5. Internally, we instruct the source server to send the file, using the RETR FTP command
6. Internally, we instruct the target server to store the file, using the STOR FTP command
7. If the transfer is interrupted or disconnected midway, we resume transfer by instructing the source server to resume using REST and RETR FTP command and the target server to store append the file using APPE FTP command
8. We can only check the file transfer progress by constantly sending the SIZE command on the target server to check how many bytes have transferred
9. At the end of transferring the file we optionally verify the file using any mutually supported hash method and then call GetChecksum() on the source and target server and check if the hash matches
10. Finally, we disconnect from source and target servers and the FtpFxpSession is disposed off

How do I tell if some files failed to transfer?

See this Folder Transfer FAQ for info on the FtpResult object.

What kinds of rules are supported and how do rules work?

See the Rules page for info and code examples.

How can I track the progress of folder transfers?

See this File Transfer FAQ for basic information on progress tracking. In addition to the basic properties you can access these properties in the FtpProgress object to find out which file is being transferred:

• progress.LocalPath
• progress.RemotePath
• progress.FileIndex
• progress.FileCount