TCP RTA (TCP Copy) – High-Performance File Replication for Windows
TCP RTA (TCP Copy) is purpose-built for fast, reliable file replication between two Windows machines—especially when you're moving massive numbers of files, working across challenging networks, or need secure transfers over the internet.
How it Works (Simple, Enterprise-Friendly Architecture)
- GS RichCopy 360 Enterprise is installed on the source Windows machine.
- The RTA (Remote Transfer Agent) is installed on the destination Windows machine.
- Source and destination communicate over a single TCP port using a multi-channeled connection, enabling multiple simultaneous copy streams for higher throughput and faster completion.
- Default port: TCP 8008 (fully configurable to align with your network and firewall requirements).
Why TCP RTA Wins Where Traditional SMB/UNC Struggles
1) Built for Millions (or Hundreds of Millions) of Small Files
Copying millions of small files is where legacy SMB/UNC transfers often slow down dramatically due to protocol overhead and per-file operations. TCP RTA is optimized specifically for high file-count workloads, keeping transfer pipelines busy through parallelization.
2) Designed for Latency, Untrusted Networks, and Internet Transfers
TCP RTA is an excellent fit for:
- Cross-site transfers (WAN / 5ms+ latency)
- Untrusted networks
- Internet-based copies
- Secure, controlled, high-throughput file movement using a single, firewall-friendly port
Security & Efficiency Features That Differentiate TCP RTA
AES 128/256 Encryption In Transit
TCP RTA supports AES 128/256 encryption for data while it's moving. Combined with the single TCP port design, this makes it a strong option for secure file transfers across the internet and other untrusted paths.
- No meaningful encryption penalty: encryption can be offloaded to the CPU instruction set, helping maintain high performance even when encryption is enabled.
In-Flight Compression (Up to 95% for Compressible Data)
TCP RTA can optionally compress data during transfer. Some datasets can compress by as much as 95%, which can reduce total transfer time, alleviate pressure on the network link, and conserve bandwidth.
- Note: Compression gains vary by file type. Already-compressed formats may see minimal reduction.
Delta Copy (Transfer Only What Changed)
Instead of re-sending an entire file, TCP RTA can perform delta copy—transferring only the changed portions of an updated file. This is ideal for large files with small edits, iterative migration waves, and recurring sync jobs.
Faster Reruns Through Local Validation
Subsequent job reruns complete much faster because:
- The client checks the source locally
- The RTA checks the destination locally
- Both sides exchange only what needs to be updated or replaced
This reduces unnecessary network traffic and dramatically speeds up repeat runs.
Benchmark Table (Low Latency Example)
Scenario: 1,000,000 files • 1 GB total • Low-latency network
| Transfer Method | Example Time | Time Savings vs SMB |
|---|---|---|
| SMB/UNC Copy | 8 hours | — |
| TCP RTA (TCP Copy) | 45 minutes | ~91% less time |
Result Summary (Low Latency): TCP RTA reduced copy time by ~91% (8 hours → 45 minutes) for 1,000,000 files (1 GB total).
Real-World Performance Positioning (Where TCP RTA Shines Most)
Depending on workload and environment, TCP RTA can deliver major time-to-completion improvements over SMB/UNC—especially in scenarios involving:
- Massive numbers of small files
- WAN connections (5ms+ latency)
- Untrusted networks
- Internet transfers
In these tougher scenarios, TCP RTA is commonly positioned as being up to ~85% faster time-to-complete than SMB/UNC, driven by multi-channel transfer, optional encryption/compression, delta copy, and local validation on reruns.
Footnote: Example results shown (low-latency test). Actual performance varies based on file size distribution, disk I/O, CPU, endpoint performance, network bandwidth/latency, and configuration (channels, compression, encryption, delta settings).