Millions of tiny files
Copying hundreds of thousands — or hundreds of millions — of small files punishes SMB with per-file protocol overhead. TCP RTA keeps the pipeline full through parallel channels, so file count stops being the bottleneck.
Enterprise Edition · TCP RTA
High-performance Windows-to-Windows file transfers — over any network.
TCP RTA (TCP Copy) is the Remote Transfer Agent built into GS RichCopy 360 Enterprise. Purpose-built to move millions of small files between Windows servers — across the same LAN, a WAN circuit, a VPN tunnel, or the open internet — through a single firewall-friendly TCP port.
TCP RTA · Active Transfer
PORT 8008
~91%
Less copy time vs SMB/UNC*
1·port
Single firewall-friendly TCP port
AES 256
In-flight, hardware-offloaded
Δ delta
Send only what changed
How it works
A simple, enterprise-friendly architecture
GS RichCopy 360 Enterprise sits on the source. The Remote Transfer Agent (RTA) sits on the destination. They open a single multi-channel TCP connection, parallelize the copy stream, and finish the job — fast.
Source
GS RichCopy 360 Enterprise
Destination
Remote Transfer Agent
Transport
Multi-channel TCP, one port
Default port
8008 (configurable)
When TCP RTA wins
Where SMB/UNC struggles, RTA delivers
Legacy SMB transfers lose minutes — sometimes hours — to protocol overhead, latency, and per-file chatter. TCP RTA is purpose-built for the scenarios where copy jobs fall apart.
WAN, VPN & the internet
At 5 ms+ of latency, SMB collapses under round-trip stalls. RTA holds throughput high across WAN circuits, VPN tunnels, and public internet paths — one firewall port, encrypted end-to-end, compressed on the wire.
NAS-to-NAS over WAN
A client near the source reads the SMB share; the RTA writes to the destination natively. SMB chatter stays local on both ends — only the optimized RTA stream crosses the WAN. Two agents, one wire.
Engine capabilities
Built for security and speed at the same time
Four engineering decisions — encryption with hardware offload, in-flight compression, delta copy, and two-sided local validation — are what separate TCP RTA from generic file transfer tools.
AES 128 / 256 encryption
Encrypt every byte on the wire with AES 128 or AES 256. Combined with the single-port design, RTA is purpose-built for secure file transfers across untrusted networks — including the open internet.
Encryption is offloaded to the CPU's native AES instruction set, so throughput stays high even with full encryption enabled.
FIPS-aligned cryptography. Where the operating system supports it,
FIPS-validated cryptographic modules are used.
In-flight compression
RTA can compress data while it streams. For compressible datasets — text, source code, XML, logs, uncompressed images — payloads can shrink by as much as 95%, cutting transfer time and conserving WAN bandwidth.
Compression gains vary by file type. Already-compressed formats (ZIP, JPEG,
MP4, encrypted archives) will see minimal additional reduction.
Delta copy
Instead of re-sending an entire file when a few bytes change, RTA transfers only the modified blocks. Ideal for large files with small edits, iterative migration waves, and recurring sync jobs against databases, VHDs, archive containers, and design files.
Combined with compression and encryption, delta copy is what makes RTA practical for nightly cross-site replication.
Multi-channel TCP transport
One TCP port — default 8008, fully configurable — carries multiple simultaneous copy streams. Network and firewall teams get a single rule. The transfer engine gets the parallelism it needs to keep CPUs and pipes saturated.
Friendly to DMZs, hardened firewalls, NAT environments, and split-tunnel VPNs.
Faster every time
Two agents. Local checks on both sides. One short conversation.
On reruns, the client inventories the source locally and the RTA inventories the destination locally — both at native disk speed. Then they compare notes over the wire. It is the closest thing to having two people on the phone, one on each side, agreeing only on what needs to move.
Source side
The client checks the source locally
- 1Walks the source tree directly — no SMB round trips across the WAN
- 2Inventories sizes, timestamps, attributes, and block-level checksums
- 3Builds a candidate change list at native filesystem speed
Destination side
The RTA checks the destination locally
- 1Walks the destination tree natively — no remote SMB enumeration
- 2Reports its inventory back to the client over the single TCP port
- 3Both sides agree on what to update, replace, or delta-patch
The result: dramatically less network traffic, dramatically faster reruns, and a sync window that holds steady as the dataset grows.
Benchmark
1,000,000 files. 1 GB total. Low latency.
A representative test of the workload TCP RTA was built for: enormous file counts at small average sizes. SMB chokes on per-file overhead. RTA parallelizes through it.
| Transfer method | Example time | Time savings vs SMB |
|---|---|---|
| SMB / UNC copy | 8 hours | — |
| TCP RTA (TCP Copy) | 45 minutes | ~91% less time |
Result: TCP RTA reduced copy time from 8 hours to 45 minutes
for 1,000,000 files totaling 1 GB on a low-latency network — roughly a 91%
reduction in time-to-complete.
Real-world positioning: Over WAN connections (5 ms+ latency), untrusted networks, and internet links, TCP RTA is commonly positioned as up to ~85% faster time-to-complete than SMB/UNC — driven by multi-channel transport, optional compression and encryption, delta copy, and two-sided local validation on reruns.
* Example results reflect a low-latency test. Actual performance varies based on file size distribution, disk I/O, CPU, endpoint performance, network bandwidth and latency, and configuration (channels, compression, encryption, delta settings).
Security posture
Designed for regulated, enterprise, and FIPS-aligned environments
RTA inherits the security architecture of GS RichCopy 360 Enterprise: direct data paths, platform-provided cryptography, and a deliberately small dependency surface.
Platform cryptography
AES 128 / 256 with hardware acceleration. FIPS-validated modules are used where the underlying OS supports them.
Direct data path
Data moves directly between source and destination. No customer data transits GuruSquad infrastructure.
Minimal attack surface
Core operations are implemented natively without third-party libraries, reducing supply-chain risk and external dependencies.
Move your files. Not your weekends.
Try GS RichCopy 360 Enterprise with TCP RTA free. Install on a source server, drop the RTA on a destination, open one TCP port, and benchmark it against your current copy job.