Data Replication
This agnostic view of whether a data service is a producer or consumer lends itself to data replication. One storage system can provide a data stream that is consumed by an identical storage system, and the data is copied from one system to another.
In the original versions of NDMP, only one data stream was allowed in the transaction between producers and consumers. In Version 5, that requirement has been loosened with the invention of the Translate Service, which sits between producers and consumers and can multiplex data streams. Although it may open up the possibility for all kinds of intermediate translation, its immediate goal was greater efficiency, allowing the faster side of what had been a single producer/consumer pair to chew data from several sources at once.
In an NDMP session, there is always one TCP/IP connection between each service and the software that centrally manages the network’s backup and recovery operations, which is the data management application. NDMP is geared toward facilitating centralized control of backup and recovery operations. The client initiates contact with services via a well-known TCP/IP port and then follows up with a standard command-and-response dialogue, which is effectively a state machine, with the state maintained on the client. The data services are moved through states with names such as “Idle,” “Listen,” “Active” and “Halted.”
Although the basic paradigm for all communication, both control and data, is via TCP/IP, the door is left open for services to realize local efficiencies, such as when a backup device is attached locally or if a system happens to be on a high-speed storage-area network. Up through Version 4, there were several standard network configurations for NDMP backup and restore sessions. In one, the client sits on a server of its own and commands a network file server to back up to a locally attached storage device. In another, the client again sits on a server of its own and commands a file server to back up, but this time to a storage device located elsewhere on the network. The standard configurations for restore are identical, except the data flow goes in the other direction.
Version 5 is concerned with Internet issues, such as security authorization and networks that exist across the Web (which is one of the reasons the NDMP working group has migrated from the Storage Networking Industry Association to the Internet Engineering Task Force). (The End)
翻譯：
虛網(wǎng)絡數(shù)據(jù)管理協(xié)議(2)
數(shù)據(jù)復制
數(shù)據(jù)服務是生產者還是消費者的不可知性有助于數(shù)據(jù)復制。一個存儲系統(tǒng)可以提供數(shù)據(jù)流，供同一存儲系統(tǒng)消費，這樣數(shù)據(jù)就從一個系統(tǒng)拷貝到另一系統(tǒng)。
在最初的NDMP版本中，生產者和消費者之間的交易中只允許一個數(shù)據(jù)流。在第5版中，隨著“翻譯服務”的發(fā)明，這個要求放寬了，此服務在生產者和消費者之間，能實現(xiàn)數(shù)據(jù)流的多路傳輸。雖然它有可能開放所有種類的中間翻譯，但它直接的目標是提高效率，以發(fā)揚單一的生產者/消費者對速度較快的優(yōu)勢，同時處理多個來源的數(shù)據(jù)。
在NDMP會話中，每個服務和集中管理網(wǎng)絡備份和恢復操作的軟件之間總是有一個TCP/IP連接，這就是數(shù)據(jù)管理應用。NDMP是用來方便集中控制備份和恢復操作的?？蛻敉ㄟ^的TCP/IP口啟動與服務的接觸，隨后就是標準的命令和響應對話，實際上這就是狀態(tài)機，在客戶端維持此狀態(tài)。數(shù)據(jù)服務在各種狀態(tài)（如空閑、監(jiān)聽、便用和暫停等）之間進行移動的。
雖然所有的（包括控制和數(shù)據(jù)）通信的基本模式都是通過TCP/IP，但服務的大門是開放著的，以便在諸如備份設備本地連接時或者系統(tǒng)剛好是一個高速存儲區(qū)域網(wǎng)時，實現(xiàn)本地的高效率。一直到第4版，NDMP備份和恢復會話有幾種標準的網(wǎng)絡配置。其中一個就是，客戶位于自己的服務器上，并命令網(wǎng)絡文件服務器備份到本地連接的存儲設備。另一種是，客戶還是在自己的服務器上，命令文件服務器進行備份，但這時是在位于網(wǎng)絡某處的存儲設備上備份?；謴偷臉藴逝渲贸藬?shù)據(jù)流是相反方向外，其他都是一致的。
第5版與互聯(lián)網(wǎng)的問題有關，如安全認證和存在于Web上的網(wǎng)絡等（這就是NDMP工作小組從存儲網(wǎng)絡工業(yè)協(xié)會轉到互聯(lián)網(wǎng)工程任務組的理由之一）。
This agnostic view of whether a data service is a producer or consumer lends itself to data replication. One storage system can provide a data stream that is consumed by an identical storage system, and the data is copied from one system to another.
In the original versions of NDMP, only one data stream was allowed in the transaction between producers and consumers. In Version 5, that requirement has been loosened with the invention of the Translate Service, which sits between producers and consumers and can multiplex data streams. Although it may open up the possibility for all kinds of intermediate translation, its immediate goal was greater efficiency, allowing the faster side of what had been a single producer/consumer pair to chew data from several sources at once.
In an NDMP session, there is always one TCP/IP connection between each service and the software that centrally manages the network’s backup and recovery operations, which is the data management application. NDMP is geared toward facilitating centralized control of backup and recovery operations. The client initiates contact with services via a well-known TCP/IP port and then follows up with a standard command-and-response dialogue, which is effectively a state machine, with the state maintained on the client. The data services are moved through states with names such as “Idle,” “Listen,” “Active” and “Halted.”
Although the basic paradigm for all communication, both control and data, is via TCP/IP, the door is left open for services to realize local efficiencies, such as when a backup device is attached locally or if a system happens to be on a high-speed storage-area network. Up through Version 4, there were several standard network configurations for NDMP backup and restore sessions. In one, the client sits on a server of its own and commands a network file server to back up to a locally attached storage device. In another, the client again sits on a server of its own and commands a file server to back up, but this time to a storage device located elsewhere on the network. The standard configurations for restore are identical, except the data flow goes in the other direction.
Version 5 is concerned with Internet issues, such as security authorization and networks that exist across the Web (which is one of the reasons the NDMP working group has migrated from the Storage Networking Industry Association to the Internet Engineering Task Force). (The End)
翻譯：
虛網(wǎng)絡數(shù)據(jù)管理協(xié)議(2)
數(shù)據(jù)復制
數(shù)據(jù)服務是生產者還是消費者的不可知性有助于數(shù)據(jù)復制。一個存儲系統(tǒng)可以提供數(shù)據(jù)流，供同一存儲系統(tǒng)消費，這樣數(shù)據(jù)就從一個系統(tǒng)拷貝到另一系統(tǒng)。
在最初的NDMP版本中，生產者和消費者之間的交易中只允許一個數(shù)據(jù)流。在第5版中，隨著“翻譯服務”的發(fā)明，這個要求放寬了，此服務在生產者和消費者之間，能實現(xiàn)數(shù)據(jù)流的多路傳輸。雖然它有可能開放所有種類的中間翻譯，但它直接的目標是提高效率，以發(fā)揚單一的生產者/消費者對速度較快的優(yōu)勢，同時處理多個來源的數(shù)據(jù)。
在NDMP會話中，每個服務和集中管理網(wǎng)絡備份和恢復操作的軟件之間總是有一個TCP/IP連接，這就是數(shù)據(jù)管理應用。NDMP是用來方便集中控制備份和恢復操作的?？蛻敉ㄟ^的TCP/IP口啟動與服務的接觸，隨后就是標準的命令和響應對話，實際上這就是狀態(tài)機，在客戶端維持此狀態(tài)。數(shù)據(jù)服務在各種狀態(tài)（如空閑、監(jiān)聽、便用和暫停等）之間進行移動的。
雖然所有的（包括控制和數(shù)據(jù)）通信的基本模式都是通過TCP/IP，但服務的大門是開放著的，以便在諸如備份設備本地連接時或者系統(tǒng)剛好是一個高速存儲區(qū)域網(wǎng)時，實現(xiàn)本地的高效率。一直到第4版，NDMP備份和恢復會話有幾種標準的網(wǎng)絡配置。其中一個就是，客戶位于自己的服務器上，并命令網(wǎng)絡文件服務器備份到本地連接的存儲設備。另一種是，客戶還是在自己的服務器上，命令文件服務器進行備份，但這時是在位于網(wǎng)絡某處的存儲設備上備份?；謴偷臉藴逝渲贸藬?shù)據(jù)流是相反方向外，其他都是一致的。
第5版與互聯(lián)網(wǎng)的問題有關，如安全認證和存在于Web上的網(wǎng)絡等（這就是NDMP工作小組從存儲網(wǎng)絡工業(yè)協(xié)會轉到互聯(lián)網(wǎng)工程任務組的理由之一）。