STORAGE AREA NETWORK REPLACEMENT. QUESTIONS AND ANSWERS. 2
pages of questions and answers. 1) Attachment C referenced in Section 1, part ...
RFP 00059293 STORAGE AREA NETWORK REPLACEMENT QUESTIONS AND ANSWERS 2 pages of questions and answers 1) Attachment C referenced in Section 1, part (B)(1) of the RFP appears to be missing from the RFP information on http://www.michiganbusiness.org/2013‐san/. Please supply the existing SAN topology map. ANSWER: See Appendix C posted to the RFP website. 2) Please verify that when “TB” is used in the RFP that “TB” represents the amount of available storage is measured in terabytes (1 TB = 1000000000000 bytes = 10^12 bytes = 1000 gigabytes) or does “TB” represent tebibytes (1 tebibyte = 2^40 bytes = 1099511627776 bytes = 1024 gibibytes). ANSWER: 1TB = 2^40 = 1,099,511,627,776 bytes 3) Please confirm that the requested minimum of 30 TB of available space, section (B)(3)(c), of the SAN RFP combines the existing CLARiiON CX3‐20 block storage and the HP ProLiant DL320 NAS storage. ANSWER: From section B. 1. Background – 1st paragraph ‐ The MEDC currently uses a functioning EMC CLARiiON CX3‐20 SAN with approximately 11TB of 15TB in use. The MEDC also has an HP ProLiant DL320 6G NAS with approximately 1.25 TB of 2.25 TB in use. 4) Section (B)(4)(e) requests migration of the data from the HP DL320 NAS to the new SAN. Will you require the new SAN to provide NAS file services or only block storage? ANSWER: On our current SAN, we have a Shared Drive mapped from a virtual server for all users. We will move the data from the NAS to the SAN. This data will be incorporated into the existing Virtual Server that manages the Shared Drive. Access permissions will need to be applied to the NAS data as it resides on the new SAN. 5. What RAID level(s) does MEDC expect to use for the usable storage? The intended percentage of overall capacity by RAID level is requested in order to calculate the usable TB of storage. ANSWER: MEDC will use RAID levels that are within the best practices and recommendations of the Vendor and Manufacturer for the proposed SAN. 6. Regarding the IOPS stated in (B)(3)(a), are there further performance goals (in either IOPS or MB/s) that MEDC wants to achieve with each of the three (SSD, SAS 2.5”, SAS 3.5”) tiers of storage? If so, what are they, and what kind of test parameters are to be used for calculations, such as random 8K block read/write, 60% read / 40% write, with 15 ms latency. ANSWER: MEDC did not specify any latency requirements in the initial RFP document. Each vendor should propose a solution that keeps latency within industry standards for their proposed SAN solution. 7. Regarding data replication, (B)(3)(h), please confirm that you wish the bidder to include a data replication license to enable copying of the entire proposed usable storage to a secondary (remote) location. ANSWER: MEDC confirms that they wish the bidder to include a data replication license to enable copying of the entire proposed usable storage to a secondary (remote) location. The bidder can also include other options that they feel would be advantageous to the MEDC. Other options should be clearly marked Options and not an additional part of the overall bid. Page 1
8. Regarding removal of the old SAN, (B)(4)(l), will MEDC perform data sanitization of the existing CLARiiON storage and HP DL320 NAS storage prior to removal or is this to be done by the replacement vendor? ANSWER: MEDC will perform the sanitization of the existing CLARiiON storage and HP NAS storage devices. Of course, any recommendations from the Vendor on how to perform that task would be greatly appreciated. 9. A clarification of (C)(9) is requested. Will MEDC require data migration activities to occur during non‐ business hours, weekend and/or holiday(s)? ANSWER: Most of the MEDC Data resides on Virtual Servers. It is our belief that the migration of the virtual servers to the new SAN can occur without any down time. The NAS data can be migrated to the new SAN during work hours – communication to the affected users will be handled by the MEDC Infrastructure Services Team. The SQL server migration will be handled during work hours – communication to the affected users will be handled by the MEDC Infrastructure Services Team. If the Vendor proposes a new SAN Networking Infrastructure that will require down time, then yes, that down time would be performed during the times defined in (C) (9). MEDC will not expect vendors to work holidays or holiday weekends. 10. Does the CLARiiON CX3‐20 have working connectivity to a fibre channel SAN fabric? What are the details (fibre channel switch vendor and model, number of FC ports (in‐use vs. free), and FC port speed) of the existing fibre channel SAN connectivity? ANSWER: No, the CLARiiON CX3‐20 does not have connectivity to a fibre channel SAN fabric. 11. Does MEDC want the replacement SAN to have fibre channel SAN connectivity? ANSWER: MEDC is interested to know the pricing of using fibre channel SAN connectivity, but it is not a requirement for the RFP. 12. Please confirm if the existing SAN network topology consists of only 1Gb Ethernet connectivity. Does any SAN device have 10 Gb connectivity today and is it in use? ANSWER: The existing SAN Network topology consists of only 1Gb Ethernet connectivity. The existing SAN device does not have 10Gb connectivity. 10Gb connectivity is not in use in any of our Data Center equipment. 13. In (B)(3)(I), are you requiring a dedicated chip for thin provisioning or simply asking if the array can do thin provisioning? ANSWER: The proposed SAN must be capable of thin provisioning. How that is achieved is up to the Vendor.
Page 2
