DIRECTORATE OF CONTRACTING; 30 N. WOLFE AVENUE; EDWARDS AFB, CA 93524-6351

70 -- DATA STORAGE FOR NETWORK (MODIFICATION #2) SOL F0470099Q1782 DUE 092899 POC Michele Cameron WEB: DIRECTORATE OF CONTRACTING, http://bsx.org/edwards/bus_ops. E-MAIL: DIRECTORATE OF CONTRACTING, michele.cameron@edwards.af.mil. DESC: A combined solicitation/synopsis was originally posted on 23 Aug 99. The questions listed below were received from various vendors in response to the original posting and modification #1 posting of this solicitation. Answers to questions are provided below and cross-referenced in the Minimum Salient Characteristics list. Please refer to the previous postings for all other pertinent information. Follow all instructions when submitting a bid. Bidders must be registered with the Central Contractor Registration and be able to provide Certs and Reps to this office. Interested parties have until midnight PST on 28 Sep 99 to submit bids. The anticipated award date is on or about 30 Sep 99. Electronic responses are allowed. FAX number 805-275-7808. EMAIL: michele.cameron@edwards.af.mil. *********************************************** Minimum Salient Characterist ics Purchase a data storage / storage area network and backup solution for Windows NT and UNIX servers. The solution must meet the following specifications: 1. The Storage Area Network (SAN) must provide the following core services: -Full Fibre-Channel Support -Cross-Platform Support (Windows NT, UNIX) -Protection against loss of data stored in cache. -Multiple concurrent RAID level (0, 1, 0+1, 5) support. -Multiple stripe depth support. -Dual active/active RAID controllers. -Dynamically adjusted look-ahead read cache. -Multiple independent processors per RAID controller. -Mirrored/synchronized write cache (Dedicated 100MB/sec cache bus. -Fibre Channel host interface (100MB/sec). Connected via Fibre channel. (See Question 9) 2. The SAN must provide volume mapping. This mechanism protects valuable data from accidental or inappropriate access by numerous hosts. -Volume mapping allocates storage volumes to specific hosts via world wide host names. -Host systems see only the volumes to which they are assigned. -Volume mapping provides an absolutely secure method of controlling host access to data. -Allows storage volumes to be dynamically re-all ocated among host systems. -Must be implemented in upgradeable array firmware which: -Provides a single point of control for host access to volumes of storage. -Supports one-to-one and many-to-one configurations. -Requires no host-base software. 3. The SAN must provide extended checksum data with each sector to confirm that error-free data is returned to the host. 4. The SAN must contain a process that logs all write transactions to a nonvolatile log to ensure that all writes are completed even in the event of a power interruption. Transactions are to be stored until data has been safely written and verified to storage. (See Question #23) 5. Upon power interruption, the SAN must contain a feature that copies cache contents, including mirrored data and array error logs to a special dedicated hard disk drive mounted directly on each RAID controller. Upon power restoration, the cache contents are restored, incomplete writes are reconstructed and written to disk, and normal operation resumes even with a controller or drive failure. 6. The SAN must perform Data Consistency Checks. Data consistency checking (DCC) continually monitors the disk drives for bad blocks and automatically relocates data to circumvent potential data corruption or loss. (See Question #22) 7. The SAN must perform duplexed cache writes. This process writes incoming data into two separate caches simultaneously in one operation. It improves write cache operation by eliminating overhead. No write cache performance penalties can be experienced in active/active controller configurations. 8. The SAN must allow user configuration of the following items: -Array group width (number of drives in a group) up to 16. -Stripe depth selectable per array group. -Stripe depth from 1 to 96 blocks. -Stripe depth to match application I/O profiles for peak performance. -RAID level per array group. -Logical volumes (Up to 32). -Volume size selectable in blocks, megabytes or gigabytes. -Pooled hot spares. 9. The SAN must contain a dynamically adjusted write-gathering cache algorithm that allows the SNA to behave like a RAID 3 system when dictated by data or process type. (This is extremely important when doing database loads, database restores, or sequential writes.) A RAID product that provides actual RAID 3 will meet this requirement if the pr oduct satisfies the requirement to dynamically adjust write-gathering memory dictated by data or process type for execution of database loads, database restores, or sequential writes. (See Question #21) Oracle and SQL Server databases, graphical images, html reports, office automation files and application executables will be stored on the RAID. (See Question #27) 10. CIFS and NFS file services must be fully supported. 11. The network attached storage devices must integrate with the existing fast Ethernet and CDDI networking infrastructure. Please disregard this requirement as stated. The intent on item 11 was to ensure that the host bus adapters for the SAN would coexist and operate with the fast ethernet and Copper Data Distribution Interface (CDDI) network interface cards presently in the servers. (See Question #1 and #6) 12. The solution must include centralized monitoring and statistic retrieval software/hardware. 13. The backup solution must consist of a DLT7000 tape jukebox with a minimum of 4 drives expandable to 7 drives. The backup and restore software must be capable of execution on a Windows NT server with agents for Windows NT, UNIX, Orac le Database, and SQL Server. Data backups and restoration must be performed directly from the SAN via Fibre-channel and Ethernet. Yes, the SAN solution is required to have agents capable of backing up online Oracle and SQL Server databases (See Question # 4) The on-line (hot) backups are to be performed over the SAN (private network). Six to 12 hour window per day (24 hour) period. (See Question #24) The SAN will function as the data storage for the servers and the SAN and Oracle / SQL Server databases agents will utilize the DLT 7000s for online backups. (See Question #7) Total number of disk drives and spindle size is as follows: 36 disk drives and 18-36 GB per drive (See Question #13) Total number of slots for DLT media in the library is as follows: Four DLT 7000 in a unit scalable to 7 drive units. (See Question #14) Total number of required DLT media is as follows: Ninety 35/70 GB cartridges (See Question #15 Posted 09/21/99 (D-SN382680). (0264)

Loren Data Corp. http://www.ld.com (SYN# 0301 19990923\70-0019.SOL)