TARRANT COUNTY PURCHASING DEPARTMENT

Transcription

1 JACK BEACHAM, C.P.M. PURCHASING AGENT TARRANT COUNTY PURCHASING DEPARTMENT FEBRUARY 28, 2012 RFP NO ROB COX, C.P.M., A.P.P. ASSISTANT PURCHASING AGENT RFP FOR ENTERPRISE STORAGE PRODUCTS AND PROFESSIONAL SERVICES 1. Reference: Page 8 II Enterprise Storage Group 1.A.2 How many fiber ports are required for the remote site? It depends on the solution provided. System must meet the goals and business objectives of the RFP. 2. Reference: Page 8 II Enterprise Storage Group (General Question) From the pre-bid conference, Data Migration from existing storage to new storage is required. How much data will be Open Systems and how much will be Mainframe? 3. Installed Usable Allocated DMX4 Unit #1 DMX4 Unit #2 Clariion CX3-80 Clariion CX700 Celerra NS TB 22.7 TB 30.1 TB 26.0 TB 49.1 TB 50.9 TB* 16.4 TB 21.3 TB 21.9 TB 38.2 TB 40.5 TB TB 8.2 TB 24.0 TB *3.5 TB of the usable capacity is configured as BCV s Installed Usable DL740A DL740B DL742A DL742B DL TB 44.3 TB 34.4 TB 34.4 TB TB Avamar Grid #1 Avamar Grid #2 8.1 TB 8.1 TB 40.7 TB 36.9 TB 28.5 TB 28.8 TB 96.4 TB 4.9 TB 4.9 TB Allocated 40.7 TB 36.9 TB 28.5 TB 28.8 TB 96.4 TB 2.8 TB 2.6 TB TARRANT COUNTY ADMINISTRATION BUILDING, SUITE E. WEATHERFORD, FORT WORTH, TEXAS (817) , (817)

2 3. What data or applications is storage QoS important for? How are you using QoS today and for what specific purposes? QoS is not currently licensed on the County s storage arrays. The requirement for QoS on the new ESA is to guarantee our ability to provide appropriate performance for any of the applications that depend on the share storage array: SAP, VMware; SQL, etc. 4. What data or applications is encryption used for on the existing storage arrays and how is this implemented (meaning is encryption a fabric based service, host based service, i.e. via PowerPath, etc.)? Enterprise Storage Array must be capable of at rest data encryption. 5. Centera What software licenses are employed on the Centera and is the Centera replicated? Centera Standard License. We are not licensed for Compliance or Governance Editions. Yes, the Centera is replicated. 6. Networker and Avamar Are you leveraging Networker as a single pane of glass to control both Networker backups and Avamar backups, or are Networker and Avamar maintained as independent platforms with separate management interfaces, backup configuration, etc? Networker and Avamar are currently operated as independent data protection products. 7. RFP IV Group 3 Backup to Disk - page 13: A11 states the VTL solution must store a minimum of 30 days of backup data, but page 15 B12 of the same section states retention period for all VTL is fourteen (14) days. Please reconcile these two different retention periods. In the current environment, Networker is configured to retain fourteen (14) days of open systems data on the VTLs. When the new Backup to Disk unit has been integrated into the backup environment, our intent is to retain thirty (30) days of mainframe, open systems data, as well as NDMP NAS data, on the unit. 8. Will Tarrant County be using Texas DIR-1364 Contract for financing or using the Lessor's Financing Agreement? Tarrant County will use whichever provides the best arrangement. 9. What is the approximate delivery, installation, and acceptance of Assets noted in the RFP? Determined by respondents abilities and agreed schedule. RFP No PAGE 2 OF Q&A 02/28/2012

3 10. Tarrant County states NO Opinion of Counsel if purchase exceeds $3Million, how will Tarrant County indemnify and warrant its actions in a financing agreement? Tarrant County may not indemnify another entity. 11. RFP Statement of Work, 1.A.2 "reasonable assurances and financial guarantees"; Please clarify if this refers to a performance bond or does the County need a copy of a form 10K to show that the supplier is a financially viable company? This refers to the respondents guarantee (including financial penalties) that the proposed system will perform as required. 12. There are references to professional services, project plan, and project implementation in several areas of the RFP. Please clarify the extent of professional services desired for this opportunity. The County expects the vendor awarded a particular group to implement all business objectives for that group including: project management, implementation schedules, installation, configuration, integration, administration, monitoring, migration, knowledge transfer, disposition of replaced hardware etc. i.e. all inclusive, end to end, complete turnkey, fully operational, fully documented, new operational policies and procedures defined and documented, personnel trained, before final signoff and payment. Proposed solution must be fully operational for a minimum thirty (30) days before project signoff. 13. RFP Statement of Work, Sections II, III, IV, V, VI, Section C. Deliverables, #1. Statement of Work: Please describe in detail what is required. Statement of Work is a binding contract for the delivery of a fully operational system (including hardware, software, and professional services). See Question 12 and Deliverables section from each group for details. 14. What is the current operating system? RFP provides required OS information. RFP No PAGE 3 OF Q&A 02/28/2012

4 15. Will there be a change to the operating system as a part of this migration? No, OS version changes are anticipated for any of the open system hosts. Driver updates and/or agent installations to hosts can be made if required by the solution. Any required updates or reconfigurations of the OS and/or existing installed software should be explicitly noted in the proposal. 16. What is the primary application? The ESA supports many applications and systems. 17. What cluster software is being used, if any? The Windows clusters use native clustering software included in the operating system. ESX hosts use VMware clustering. 18. Is a Logical Volume Manager in use? If so which version? Windows hosts use the native Microsoft Logical Disk Manager, version appropriate to the host OS. Tarrant County uses EMC PowerPath version 5.5 for multipathing for all Windows hosts. ESX hosts use native volume management and either Round-Robin (DMX attached) or MRU (Clariion attached) path selection policies. 19. Will LUN sizes be changed between source and target arrays? No. It is expected that the ESA will be capable of expanding LUNs non-disruptively after they have been migrated if the need arises. Please indicate if the proposed ESA solution is not capable of non-disruptive LUN expansion for open system hosts. Tarrant County would like to have the mainframe devices re-organized into fewer, larger devices. Details will be provided after contract award. 20. Number of Sites by location and address? Two (2) sites: 200 Taylor Street and 100 E. Weatherford Street. RFP No PAGE 4 OF Q&A 02/28/2012

5 21. Will the migration be performed during business hours? The primary concern is for safe and minimally disruptive migrations. In some cases, existing SLA s require that maintenance be performed outside of traditional business hours. Tarrant County IT staff will be available for all migration activities. 22. What is the Total Amount of Data to be migrated? Depends on the solution provided. See question What portion of the data is actively used? All data is considered active. 24. Will migration be online or offline? Migrations should be minimally disruptive with a strong preference of online migrations. The migration strategy included in the deliverable section should clearly indicate strategy and expected downtime by host-type: stand-alone Windows host, Windows cluster, ESX host, and mainframe. The effects of original storage array model (DMX, Clariion) on migration-related down time, if any exist, should be explicitly noted as well. 25. What are the plans for data backup after the migration? All backup policies/schedules should remain active and unchanged. 26. Please list San Fabric (i.e. Cisco or Brocade) and models? See Item II B. 2. page 10 of the RFP for storage fabric hardware. 27. RFP Proposal Signature Form and Proposal/Forms Document Checklist: If vendor needs to add qualifying statements in these forms, please advise how we should do that considering the forms limit content input in defined fields only and the RFP states vendors may not retype the forms? Page 34 of the RFP package, Deficiencies and Deviations Form, is to be used for this type of information. RFP No PAGE 5 OF Q&A 02/28/2012

6 28. What specific software for snap and clone technologies are used today for each array? Timefinder/Clone is available on DMX4 Unit 1. Snapview is available on both Clariion Arrays. 29. What snap and clone technologies are used for the mainframe? If Flash Copy in use on mainframe? None. No. 30. It was stated in the meeting that the total amount of data on LTO3 media was 1.1PB. Please confirm and explain if that is a compressed or uncompressed figure? There is 1.18PB of recoverable data reported by the backup application (Networker) on LTO3 media. Hardware compression is enabled in the ADIC Library, but the recoverable data figure is the uncompressed amount. 31. How many total LTO3 cartridges are in inventory for this data store? There are 3,440 LTO3 cartridges. 32. What is the total amount of data stored on the native tape (Native 20GB 9840), and is this a compressed or uncompressed figure? Approximately 3.6TB compressed. 33. Is any of the data duplexed on to two 9840a cartridges? (If so, how much - the entire inventory or how much% of the inventory) No. 34. If duplexed data exists, does the total data stored amount asked for above include the duplexed data as well? N/A. 35. How many total Native 9840a cartridges are in inventory for this Native data store? There are three hundred and fifty (350) tapes in the native pool. 36. Please explain what type of Mainframe application is being directed to the Native 20GB 9840? - such as dfhsm, ABARs, DB2, SAR or some unique proprietary application. Examples of data that is sent to native tape include manifests for offsite copies of VTSS volumes, DFSMSdss full volume backups, Mobius/Document Direct content, and weekly backups of Unix System services. RFP No PAGE 6 OF Q&A 02/28/2012

7 37. Is any of this data vaulted or sent offsite? If so, approximately how much data is vaulted for Native per business day? Approximately 50GB per day, or 7 MVC s, is sent offsite daily. 38. How many VSM3s are being used (1,2, or...)? One (1). 39. Does the VSM3 utilize the 9740 silo for his back end drives (RTDs) and tapes (MVCs)? If not, where do the VSM3 physical back end tapes (MVCs) and drives (RTDs) reside? The VSM uses the 9740 to backup VTV s. 40. Please explain what type of Mainframe application is being directed to the VSM3? - such as dfhsm, ABARs, SAR, DB2, or some proprietary application Examples of applications that are directed to the VSM3 include DFSMS volume and dataset backups, selected CA products, IMS journals and dataset backups, DB2 journals and dataset backups, existing Mobius/Data Direct content (Mobius/Data Direct application no longer resides on mainframe). 41. How much total data does the VSM3 manage, not including any duplex copy data amounts? Total virtual tape data is 4.210TB uncompressed, not counting duplex. Nearly all of it is duplexed to two MVC s. 42. How many total MVCs are in inventory and managed by the VSM3? There are 318 MVC s are in use. Currently, one hundred fifty-seven (157) of them are in the silo. Backups are duplexed, and the MVC s that hold duplicate copies go offsite. 43. What drive type are the RTDs behind the VSM3 (9840a/b/c/d or 9940a/b, or...)? The backing drives are 9840 s identical to the native drives. RFP No PAGE 7 OF Q&A 02/28/2012

8 44. Is any of the VSM3 data vaulted or sent offsite? If so, approximately how much data is vaulted from the VSM3 per business day? Nearly all of the VSM3 data is duplexed, and the MVC s that hold duplicate copies go offsite, along with the native manifest tapes that describe what s in the MVC s. 45. Does the county have a mandate that the backups must use physical tape? Yes. All data must be recoverable from media that is kept at an offsite location. 46. Does the county have a mandate to ship tapes to an offsite vaulting facility? If so, how often (once a business day, everyday, or...)? Yes. Tape media is sent offsite seven (7) days a week, three hundred sixty-five (365) days a year. 47. Is there any data on either LTO3 or on the mainframe older than standard 14 day retention? If yes, please explain. Yes. Open Systems backup data is initially sent to Virtual Tape Libraries. All Open Systems backup data is cloned/copied within twenty-four (24) hours of the completed backup via Networker to physical media, which is then sent offsite. Physical media is kept offsite for the full retention period which ranges from two weeks to five years. Open Systems data that is on virtual tape is currently retained for fourteen (14) days and then deleted. Mainframe system journal backups are kept for one month, as are database backups and database journals. Source library backups are retained for one (1) year. Some Mobius data has a retention policy of thirty (30) years. 48. If we are to provide migration services, what is the total amount of data? Depends on the solution provided. See question 2. RFP No PAGE 8 OF Q&A 02/28/2012