fastcopy-file-transfer-tool

Use turbo mode with a high stream count, such as fastcopy /source /dest --mode turbo --streams 64 --buffer 512. Test different stream counts (8, 16, 32, 64) to find the best throughput for your hardware, and skip verification with --no-verify when speed matters more than integrity.

Create a YAML profile with a schedule block using type cron and an expression like "0 2 * * *" for daily 2 AM runs. Execute it with fastcopy --profile scheduled-backup.yaml, optionally adding hooks for start, completion, and error notifications.

Yes, FastCopy supports SHA-256 and CRC-32 integrity verification when you pass the --verify flag or set verify: true in a profile. Verification failures can be logged to a report file and retried automatically with --retry.

FastCopy resumes interrupted transfers when configured with --resume always or resume: on_failure in a profile. You can also manually resume a specific transfer using its transfer ID with fastcopy --resume-transfer <id>.

High CPU usage comes from too many parallel streams or large buffers. Reduce streams to 4, lower buffer_size_mb to 64, set io_priority to low, or pin the process to specific cores using the cpu_affinity setting in the performance section.

Define include and exclude filters in a YAML profile, such as including "**/*.mp4" while excluding "**/draft/**" and temporary files. You can also constrain transfers with min_file_size_mb and max_file_age_days options for selective synchronization.