SPECIAL NOTICE
99 -- HSN SAN RFI
- Notice Date
- 8/18/2015
- Notice Type
- Special Notice
- Contracting Office
- P.O. Box 190022, North Charleston SC 29419-9022
- ZIP Code
- 29419-9022
- Solicitation Number
- N65236_SNOTE_000BED02
- Archive Date
- 8/25/2015
- E-Mail Address
-
Contract Specialist
(audrey.orvin@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- Document Type: Special Notice Solicitation Number: DON-SNOTE-00000000 Title: Object Based Hierarchical Storage Management (HSM) Storage Area Network (SAN) Posted Date: 08/18/2015 Archive Date: 08/25/2015 Responsible Command: N65252 NAICS Code: N/A Contracting Office Address P.O. Box 190022, North Charleston SC 29419-9022 Description Request for Information (RFI) HSM STORAGE AREA NETWORK DUE: AUGUST 25, 2015 The Space and Naval Warfare Systems Center (SPAWARSYSCEN) Atlantic, Naval Command Centers IPT is seeking information from potential manufacturers to aid in the development of an Object Based Hierarchical Storage Management (HSM) Storage Area Network (SAN). Once eligible products have been identified, additional information may be requested. The current system uses Storage and Archive Manager Quick File System (SAM-QFS) functionality which allows frequently-used data files to be stored on disk drives and can also be moved to tape based upon their age, administrator-defined access rules, or users actions. These files then remain on the file system as stubs or shortcuts providing the end-users a view that all files are still available on the disk systems when they actually reside on archive tape. When an archived file is accessed, the system automatically retrieves the original file from tape and places it on the disk system with limited delay to the end-user. The key advantage is the total amount of stored data can be much larger than the capacity of the disk storage available. Since only rarely-used files are on tape, it will be rare that users will experience a retrieval slowdown. The current system, utilizes shared QFS file systems that are available to users on shared QFS Solaris and Linux clients. Users access files via the Network File System (NFS) on Linux clients and via Samba on Windows. The use of Samba is standard, but it adds to the overhead and causes a file transfer speed reduction for Windows users. This is not ideal, and the Government would like a solution that doesnt require Samba. The system must be able to operate with the current four StorageTek SL3000 tape library units, using T10K-D type drives. All data residing on the older StorageTek tapes will need to be migrated to the new tape medium, specifically T10K-T2 tapes. The System will operate under the Department of Navy (DON) and Department of Defense (DoD) policies and constraints for network-operational equipment. Such systems are required to be certified under, but not limited to, meeting Common Criteria Recognition Arrangement (CCRA), or National Information Assurance Partnership (NIAP) qualifications. Where applicable, Security Technical Implementation Guides (STIGs) are implemented. Manufacturers will provide applicable DoD deployed solutions precedence or system certification acceptance that cover proposed system solutions. The following list describes the typical operating guidelines for the intended systems solution. 19' IEC rack-compliant (17.6') wide with a 24' (26.5' w/cable management) depth Operating temperature, altitude, and relative humidity 10 C to 40 C (50 F to 104 F); at <= 3,000 m (at <= 10,000' feet) elevation; 20% to 80% relative humidity, noncondensing (28 C wet bulb temperature) Non-operating temperature and relative humidity -40 C to 65 C (-40 F to 149 F); 5% to 95% relative humidity, noncondensing Operating acoustic noise 61 dBA sound pressure (LpA) @ normal operating conditions (at 22C and at sea level) Compliance(s) where appropriate to RoHS-compliant, Safety/Emissions/Immunity Safety: EN 60950, CE, CSA 60950, UL 60950, CB IEC60950-1 (all national deviations), EN60825-1, IRAM, GOST-R, BSMI, SONCAP, NRCS LOA (South Africa), and Emissions/Immunity: FCC Part 15 Class A, ICES-03, CE, KCC, VCCI, AS/NZS CISPR 22, EN55022, EN55024, EN61000-3-2, EN61000-3-3, BSMI Manufacturer Criteria These critical requirements must be reviewed by the potential manufacturer. Any manufacturer not meeting the critical items listed below will not be considered as a viable option. Table Error! No text of specified style in document. 1. Manufacture Criteria Item Priority Criteria Description 1 Critical T10KT2 tape compatibility/StorageTek T10000D solution support StorageTek SL3000 Archive will not be replaced. Selected solution must support and operate with this archive library 2 Critical Object-oriented File Controls/Object Based File System Current processes utilize auto tearing and stubbing of production files. Native or available add-on HSM functionality must be supported and must be imported or migrated from current archived tape 3 Critical User Accessible Stubbing Controls Current processes utilize user Access Control Lists (ACLs) to provide access to stubbing controls as long as users have read privilege. Can users, such as super-users, access stubbing controls without administrative privileges 4 Critical SAM Import or Migration Tools Export/Import or Migration is important as it determines the time required to place tape archive completely operational. has a combined 1.7PB of archive storage that must be imported or migrated into the new system Migrations of all production and archived data from SAM-QFS file systems to selected file system in a non-disruptive active-active migration. 5 Critical NFS Protocol Support Native NFS communication must be supported. has a large base that accesses the SAN via NFS 6 Critical High Availability Target of 99.99% uptime. System upgrades must not take system down 7 Critical IPv6 support Must support IPv6 in GA. DoD requirement 8 Critical DoD Installed Does solution have prior performance/installation history in a DoD environment 9 Critical Auto Restore of Touched File Stubs Automatically restore of archived files once the file stubs are touched 10 Critical No Silent Data Corruption Must provide mechanism(s) to prevent silent data corruptions provides for historical lifetime storage of selected data they produce and acquire 11 Required 1Gb/10Gb Ethernet Support Solution shall provide connectivity for 1Gb and 10Gb Ethernet for clients 12 Required Improved Overall Performance than Current Incumbent System Solution shall provide better overall performance than the current incumbent system 13 Desired Unified File System Unified file system provides for a simpler management of growth, performance and scalability of the system 14 Desired CIFS Protocol Support Native connectivity would simplify operations considerably has a growing base of Windows systems that must rely on Samba for NFS connectivity 15 Desired Win Client Driver Solution shall provide an option for software driver for Windows native file access of SAN system. Some solutions, such as IBM GPFS, have native client drivers to provide a non-native OS (i.e. Windows) native file access 16 Desired Large Data Dump Friendly System solution should facilitate large data sets ingested Examples are fleet ship data and Fleet Survey Team (FST) or Light Detection and Ranging (LIDAR) data 17 Desired Single Mgmt. Storage The system shall provide a single management interface for storage space and volume control. 18 Desired Single Mgmt. HSM The system shall provide a single management interface for the HSM of tiered storage. 19 Required Monitoring Tools All systems must have performance monitoring tools to provide trending and real time monitoring, log captures, and report generation of administered systems or selected queried systems. This system shall include but not be limited to: StorageTek Tape Analytics (STA) or an equivalent tool must be implemented for health monitoring and to provide for preemptive tape retirement due to media degradation. An analytics or equivalent tool shall provide the highest level of tape archive integrity. Disk SMART drive monitoring or equivalent tool must be implemented for health monitoring and pre-emptive action control on all disk systems. All single point of failure systems components must have an active/passive or active/active fail over to prevent loss monitoring and or logging. All information received will be treated as public knowledge and may be used in development of an Object Based Hierarchical Storage Management (HSM) Storage Area Network (SAN); therefore, Manufacturers should not submit proprietary information in response to this RFI. Specific information sought includes: 1. Company information, including name, address, and website; 2. Whether the company is a manufacturer or distributor; 3. A point of contact for follow-up information, and the point of contacts phone number and e mail address; and 4. Product name as well as information on the product, including type (e.g., law enforcement use or fire service use); MSRP; resolution, and display type. The submitted information will be evaluated for inclusion in in development of an Object Based Hierarchical Storage Management (HSM) Storage Area Network (SAN). If an Object Based Hierarchical Storage Management (HSM) Storage Area Network (SAN) project is developed on this type of equipment is executed, the equipment selection will be based upon a number of factors, including; table 3.3 (above), emergency responder surveys and responder focus group inputs. Consequently, follow-up requests for feedback should not be made through the Federal Business Opportunities posting agency. Manufacturers will be contacted following submission for more detailed product information. Manufacturer-provided information may be reformatted for publication in Program documents. Submissions A microsoft Word document with this same announcement is located on SSC LANT's e commerce website: https://e-commerce.sscno.nmci.navy.mil. The technical point of contact is Mark Hartgrove (mark.hartgrove@navy.mil). Please submit all documentation to Mr. Hartgrove. Manufacturer information constitutes consent to publication of that information in Program(s) documentation. A NOTE REGARDING THIS RFI: This RFI is for information gathering and planning purposes only and should not be construed as a Request for Proposal (RFP) or solicitation of an offer. The Government DOES NOT intend to award a contract on the basis of this RFI or otherwise pay for the information solicited. E-mail your non-technical, contract-related questions to the Contracting Officer at Jackie.luna@navy.mil.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/ec7b6c25a85fb474474dfc2dd0e1402f)
- Record
- SN03843717-W 20150820/150818235959-ec7b6c25a85fb474474dfc2dd0e1402f (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |