Understanding NDMP (Network Data Management Protocol): Concepts, Backup Principles, Versions, and Implementations
The article provides a comprehensive overview of the Network Data Management Protocol (NDMP), explaining its architecture, core concepts, backup mechanisms, version differences, supported backup software, and various network topologies such as 2‑way, 3‑way, and remote configurations for efficient NAS data protection.
NDMP (Network Data Management Protocol) is an open, enterprise‑grade protocol designed to control backup, restore, and data transfer between primary and secondary storage devices over a network.
The protocol was originally co‑developed by Network Appliance and Legato Systems and has been continuously enhanced; the SNIA working group is finalizing version 5.
Key components include NDMP services (data, tape, and SCSI path‑through services), NDMP servers that host one or more service instances, NDMP sessions that bind a DMA (Data Management Application) with two NDMP services, and the mover that transfers data between tape and the data stream.
Backup operations rely on a client/server model where the DMA initiates a session, controls the backup flow, and manages state, while a control connection (bidirectional TCP/IP) links the DMA to each NDMP service.
NDMP offers LAN‑free and server‑free advantages, eliminating the need for backup client agents on NAS devices and allowing direct data transfer to tape libraries or backup servers, which reduces network traffic and server load.
Version 4 introduced modular services, SAN/NAS support, snapshots, and restartability; version 5 added multiplexing, a translate framework for vendor‑specific extensions, and a clear separation of control and data flows, improving compatibility and extensibility.
Major backup products supporting NDMP include NetBackup, Networker, CommVault (Simpana), and IBM TSM, each employing a three‑tier architecture of clients/agents, master/media servers, and storage agents.
Common NDMP deployment topologies are:
2‑Way: NAS connects directly to a tape library, bypassing a backup server for higher performance but limited to a single NAS.
3‑Way: NAS devices share a tape library via a dedicated backup network, enabling multi‑NAS sharing at the cost of bandwidth constraints.
Remote: Backup software mediates between NAS and tape library, reducing NAS requirements and allowing shared tape resources, though with increased network traffic and server load.
The article concludes with references to further reading and a reminder to follow the ICT_Architect channel for more technical content.
Architects' Tech Alliance
Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.