ascp: Transferring from the Command Line |
Policy | Command template |
---|---|
Fixed |
--policy=fixed -l target_rate |
Fair |
--policy=fair -l target_rate -m min_rate |
High |
--policy=high -l target_rate -m min_rate |
Low |
--policy=low -l target_rate -m min_rate |
The policies have the following characteristics:
On the client machine, start a transfer with fixed bandwidth policy. Start with a lower transfer rate and gradually increase the transfer rate toward the network bandwidth (for example, 1 MB, 5 MB, 10 MB, and so on). Monitor the transfer rate; at its maximum, it should be slighly below your available bandwidth:
$ ascp -l 1m source-file destination
To improve the transfer speed, also consider upgrading the following hardware components:
Component | Description |
---|---|
Hard disk | The I/O throughput, the disk bus architecture (such as RAID, IDE, SCSI, ATA, and Fiber Channel). |
Network I/O | The interface card, the internal bus of the computer. |
CPU | Overall CPU performance affects the transfer, especially when encryption is enabled. |
Corruption or deletion of the .asp-meta file associated with an incomplete transfer will often result in a permanently unusable destination file even if the file transfer resumed and successfully transferred.
Interaction with resume policy (-k): If the overwrite method is diff or diff+older, difference is determined by the resume policy (-k {0|1|2|3}). If -k 0 or no -k is specified, the source and destination files are always considered different and the destination file is always overwritten. If -k 1, the source and destination files are compared based on file attributes (currently file size). If -k 2, the source and destination files are compared based on sparse checksums. If -k 3, the source and destination files are compared based on full checksums.