Template Version: @(#)onepager.txt 1.30 06/09/28 SMI Copyright 2006 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: NDMP service 1.2. Name of Document Author/Supplier: Reza Sabdar (Reza.Sabdar@Sun.COM) 1.3. Date of This Document: 12/21/06 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Beverly Crair (Beverly.Crair@Sun.COM) 1.4.4. The name of your business unit: Software 1.5. Email Aliases: 1.5.1. Responsible Manager: Alan.M.Wright@Sun.COM 1.5.2. Responsible Engineer: Reza.Sabdar@Sun.COM 1.5.3. Marketing Manager: 1.5.4. Interest List: ndmp-interest@Sun.COM 2. Project Summary 2.1. Project Description: This project covers the implementation of a Network Data Management Protocol (NDMP) service on Solaris. The code will be ported from Sun's non-Solaris NAS. NDMP is an open protocol intended for enterprise-wide, network-based data management, including backup, restore and transfer between primary and secondary storage. This project will support versions 2, 3 and 4 of the NDMP protocol. 2.2. Risks and Assumptions: The NDMP service will run as a user space service and requires no changes to existing Solaris interfaces. It will operate on any regular file system and with a range of standard SCSI or FC tape devices and tape libraries. No specific risks have been identified. 3. Business Summary 3.1. Problem Area: NDMP provides a scalable and flexible backup solution for servers in an enterprise. One of the main advantages of NDMP is that it allows a backup agent/client to coordinate backup over the network but the data being backed up does not need to cross the network. NDMP support would enable Solaris to participate in a centralized or distributed NDMP infrastructure, with support for various backup and restore policies (full, incremental etc) and roles. An NDMP server can be assigned the backup role, in which it receives NDMP remote data from data servers, or the data role, in which an NDMP server forwards data, using NDMP, to a remote backup server. NDMP also provides services such as disk-to-disk and tape-to-tape copy. In a future release, the NDMP snap management extensions will provide support for creation, replication and restoration of file system snapshots on the server, assuming a file system with snapshot support. 3.2. Market/Requester: Customers with existing NDMP infrastructure would be potential customers for this project. Current NDMP backup solution providers include Symantec, IBM, Legato, Bakbone, Computer Associates and Syncsort. NDMP is very often a checklist item in the NAS market. 3.3. Business Justification: NDMP will expand the file server business for Sun by adding an open, industry standard, enterprise level backup solution to Sun's portfolio. Certifying Solaris with third party NDMP application vendors will increase the sales opportunities by addressing the needs of potential customers already using NDMP. 3.4. Competitive Analysis: NDMP is integrated in many of NAS solutions, including the current non-Solaris based NAS available from Sun, and is often a checklist item on NAS sales bids. Sun's main competitors in the NAS space (Network Appliance, EMC, Microsoft) all provide NDMP services. 3.5. Opportunity Window/Exposure: There is currently no open source NDMP implementation available. Sun has an opportunity to provide the first operational NDMP service reference implementation via Open Solaris. 3.6. How will you know when you are done?: The NDMP service will enable a Solaris system to perform NDMP backup and restore of Solaris file systems using versions 2, 3 and 4 of the NDMP protocol, in both two-way and three-way configurations, using a set of backup applications and tape libraries. 4. Technical Description: 4.1. Details: NDMP is an open, industry standard communication protocol, used to control data backup and recovery between primary and secondary storage in a heterogeneous network environment. The protocol is ONC RPC based and is being developed by the NDMP Task Force (www.ndmp.org) and the Storage Networking Industry Association (SNIA) NDMP Working Group (www.snia.org). NDMP specifies a common architecture for network file server backup and restore coordinated by centralized agents, potentially running on different platforms. One of the main benefits of NDMP is the separation of the control and data paths. The NDMP server and agent communicate via the control path using ONC RPC. The backup and/or restore operations are performed on the NDMP server using SCSI or FC to communicate with tape drives and/or tape libraries. A pass-through mode is also supported to allow an NDMP agent to communicate directly with the tape drives and libraries to load and position tapes. Thus NDMP minimizes demands on network resources by performing backup and restore operations locally but managed by a centralized application. The code will be ported from Sun's non-Solaris NAS and will provide support for NDMP versions 2, 3 and 4 on Solaris. 4.2. Bug/RFE Number(s): 6242615 - Need support for NDMP v4 6433372 - Add NDMP v4 extensions: NetApp Snapshot and Snapvault 4.3. In Scope: NDMP v2, v3, v4, disk-to-disk copy and tape-to-tape copy. 4.4. Out of Scope: V4 extensions: the restartable backup extension and the snapshot management extensions. 4.5. Interfaces: The NDMP services listens on TCP port 10000, which is the default port assigned to the NDMP protocol. 4.6. Doc Impact: Manual pages and administration guides will be impacted by this project. NDMP documentation will be required. 4.7. Admin/Config Impact: New CLI commands will be added to support NDMP configuration and administration. 4.8. HA Impact: This NDMP project will not provide SunCluster support. 4.9. I18N/L10N Impact: The NDMP service supports ASCII and UTF-8 character encodings. No I18N/L10N impact is anticipated. 4.10. Packaging & Delivery: This project will deliver one new package, likely named SUNWndmp. This packages may be considered for inclusion in existing clusters. No impact is anticipated on install/upgrade. 4.11. Security Impact: The NDMP service makes use of MD5 for password hashing. The NDMP service does not expose any security API's. 4.12. Dependencies: This project uses the USCSI and MTIO interfaces for communication with secondary storage. Changes to those API's may affect this service. 5. Reference Documents: NDMP Version 2 http://www.ndmp.org/download/sdk_v2/index.shtml NDMP Version 3 http://www.ndmp.org/download/sdk_v3/index.shtml NDMP Version 4 http://www.ietf.org/proceedings/01dec/I-D/draft-skardal-ndmpv4-03.txt http://www.ndmp.org/download/sdk_v4/index.shtml NDMP Version 4 Extensions http://www.ndmp.org/download/sdk_v4/extensions.shtml Storage Networking Industry Association (SNIA) NDMP Working Group http://www.snia.org 6. Resources and Schedule: 6.1. Projected Availability: Q1CY07 6.2. Cost of Effort: 1 development engineers - 12 months 1 test engineer - 3 months 1 technical writer - 2 months 6.3. Cost of Capital Resources: Existing AMD-based Solaris systems will be used for development. 1 Sparc-based Solaris system required for development. 1 AMD-based Solaris system required for testing. 1 Sparc-based Solaris system required for testing. Access to test systems and tape drives and libraries. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: ON 6.4.3. Type of CPT Review and Approval expected: Standard 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: N/A 6.4.7. Target RTI Date/Release: Q1CY07 Nevada 6.4.8. Target Code Design Review Date: Q1CY07 6.4.9. Update approval addition: This project does not have prior Solaris PAC approval for a Marketing Release. This project will request approval to ship as part of Nevada. 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: NDMP service prototype demonstrated on Solaris in July 2006. 7.2. Prototype Cost: N/A