Data-Movement Glossary — Key Data-Transfer Terms

Air-gapped transfer: Moving data within disconnected or classified networks with no external connectivity. Zettar runs on-premises with no call-home dependency, so it operates in air-gapped and accredited enclaves. See Aerospace & Defense.
ALCOA+ / data integrity: The data-integrity principles regulated life-sciences pipelines must uphold — Attributable, Legible, Contemporaneous, Original, Accurate, and more. Zettar's unconditional end-to-end checksums give provable integrity in transit. See Life Sciences.
Append streaming: Moving live, fast-growing data as it is produced (for example from high-speed instruments) instead of waiting for a complete dataset. See zx Streaming.
Burst buffer: A fast NVMe staging tier between production storage and the network that absorbs I/O bursts and decouples storage from the WAN — a key building block of high-speed data-movement architecture.
Checkpoint / model weights: The large state files AI training writes and reads — checkpoints and weights — that must move fast between storage, clusters, and regions to keep GPUs from idling. See AI & Datacenters.
Checksum / end-to-end integrity: Verifying that every byte arrives exactly as it was sent. Zettar applies unconditional end-to-end checksums on every transfer, so data is provably intact.
Cloud egress fees / cloud tax: The cost and 30-50% performance penalty of moving data in and out of public clouds through standard paths. Zettar's co-designed path bypasses the penalty. See Hybrid-Cloud Movement.
Co-design (hardware-software co-design): Engineering the data mover, host, storage, and network together as one system instead of optimizing each in isolation. Co-design is why Zettar realizes throughput that general-purpose tools leave on the table — the network is rarely the only bottleneck.
Congestion control: The TCP algorithm (CUBIC, BBR, Reno) that governs how fast a sender transmits. On well-provisioned research and education networks the choice barely matters; Zettar performance is largely insensitive to it.
Cryo-EM (cryo-electron microscopy): Imaging that produces multi-terabyte datasets per session, which must move to HPC and the cloud. Zettar moved a KEK cryo-EM dataset 5.9× faster than aws-cli. See Life Sciences.
Data gravity: The tendency of large datasets to attract applications and compute to wherever the data already lives. Fast data movement lets you put compute where it is cheapest instead of being pinned by data gravity.
Data migration: A one-time or phased move of data to new storage, a new system, or the cloud. With Zettar, petascale migration is measured in hours, not weeks. See Migration.
Data movement: The discipline of moving large volumes of data between storage, systems, sites, and clouds — efficiently, securely, and verifiably. At terabyte-to-petabyte scale, data movement (not compute) is often the real bottleneck. See the zx Appliance.
Data mover: Software or an appliance purpose-built to move data fast and reliably at scale. Zettar zx is a unified, scale-out data mover for file, object, and streaming.
Data replication & sync: Keeping copies of data consistent across sites or clouds for disaster recovery and collaboration, within tight RPO/DR windows. See Replication & Sync.
Data sovereignty: Keeping data under a nation's or organization's own jurisdiction and control. Zettar runs on-premises on hardware you choose, with no forced cloud, so sovereign-AI and regulated data stay in-country. See Sovereign AI.
Data transfer: Sending data from one location to another over a network. High-speed data transfer at scale needs the parallelism, tuning, and integrity checking that general-purpose tools (rsync, scp, FTP) were never built for.
Data Transfer Node (DTN): A server dedicated to high-speed data transfer, common in research and HPC environments. Zettar turns DTNs into a turnkey, pretuned appliance. See Research & Academia.
DPU / IPU: A data-processing (or infrastructure-processing) unit such as NVIDIA BlueField that offloads networking and storage from the host CPU. Zettar zx can run on DPUs for denser, more power-efficient data movement.
File transfer vs. object transfer: File transfer moves files and directories; object transfer moves objects in systems like Amazon S3. Zettar moves both — and between them, with no format wrappers. See zx File and zx Object.
Full-motion video (FMV): Continuous video from ISR sensors, aircraft, and drones — high-volume streams that must move from collection to exploitation fast and intact. See Aerospace & Defense.
Goodput / link utilization: The share of a link's capacity actually used to deliver data. Zettar sustains high utilization — over 96% in the SLAC/ESnet record — where general-purpose tools stall at a fraction of the link.
Ground station / downlink: Where satellite data is received from orbit. Downlinked imagery must move from globally distributed ground stations to cloud, archive, and processing. See Earth Observation.
Hybrid-cloud / multi-cloud data movement: Moving data between on-premises, hybrid, and multiple public clouds. Zettar bypasses the 30-50% cloud-stack penalty that slows standard cloud transfer paths. See Hybrid-Cloud Movement.
Latency-insensitive: Performance that holds up over long distances. Zettar has moved data over 5,000- and 12,375-mile paths with no throughput collapse — distance does not wreck the transfer.
Line rate: The full usable rate of a network link. Zettar runs at line rate — sustaining roughly 90%+ of whatever bandwidth your end-to-end path can deliver, even on a shared link — so the network, not the software, is the limit.
Managed file transfer (MFT): Enterprise software for secure, governed file transfers. Zettar focuses on at-scale, high-speed movement that legacy MFT — and tools like Aspera or Globus — cannot match at petascale. See Why Zettar.
Object storage (S3): Storage that manages data as objects through an API, such as Amazon S3. High-speed object data movement within and across clouds is a core zx capability. See zx Object.
PACS / VNA: Picture Archiving and Communication System / Vendor-Neutral Archive — medical-imaging stores holding petabytes of radiology and pathology studies that must move between sites, to the cloud, and into AI. See Healthcare.
Parallel file system: High-performance storage (Lustre, BeeGFS, GPFS) that stripes data across many servers for throughput. BeeGFS was the storage used in Zettar's 1 PB world-record transfer.
Petascale / petabyte (PB): A petabyte is 1,000 terabytes. Petascale data movement means reliably moving data at the petabyte scale — Zettar moved 1 PB in 29 hours with SLAC and ESnet.
RDMA / zero-copy: Techniques that move data with minimal CPU involvement (RDMA, kernel bypass) to reach high throughput. zx uses the host efficiently so the CPU is not the bottleneck.
RPO / RTO: Recovery Point Objective and Recovery Time Objective — how much data you can afford to lose and how fast you must recover. Wire-speed replication helps hit tight RPO/RTO windows at petascale. See Replication & Sync.
S3 multipart transfer: Splitting large objects into parts moved in parallel for S3-compatible object storage, so one big object never caps throughput — a core zx Object capability. See zx Object.
Scale-out (symmetric, peer-to-peer): An architecture where every node both sends and receives and clusters self-organize, so aggregate throughput grows as you add nodes — with no software-imposed bandwidth ceiling. The network fabric, not the data mover, sets the limit.
Seismic data: Subsurface survey data, often petascale, that moves from remote fields and vessels to processing centers and HPC. See Energy.
Sequencer / NGS data: Next-generation sequencers output terabytes to petabytes of genomic data per run that must move to analysis fast. See Life Sciences.
Storage tiering: Moving data between performance and cost tiers (for example file to object) transparently and in native formats, with no lock-in. See Transparent Tiering.
Tape-out: The final chip-design data handed from designers to a foundry — large files that move between design centers and fabs worldwide, where IP must stay encrypted and intact. See Semiconductor & EDA.
Throughput: The actual rate of data delivered. zx runs at line rate — filling the bandwidth your end-to-end path can sustain — and scales out across servers with no software ceiling.
Wire speed: Moving data at the full rated capacity of the underlying network link, with minimal overhead. Wire-speed transfer means the software — not the network — is no longer the limit.

Data-movement glossary.

Move your data at wire speed.