Subject: Request for Proposals: Enterprise Systems Backup Solution, # FIT Due: May 14, 2013 at 2:00 PM EST

Transcription

1 NOTICE OF ADDENDUM ADDENDUM #4 May 7, 2013 Subject: Request for Proposals: Enterprise Systems Backup Solution, # FIT Due: May 14, 2013 at 2:00 PM EST Dear Sir or Madam: The Columbus Regional Airport Authority hereby issues addenda to the subject solicitation: Answers to questions regarding the solicitation (attached below). The addition of Appendix C Requirements Compliance Table to be submitted with all proposals (attached below), and the modification of Section on Page 19 of the subject RFP to reflect this. This Section is hereby corrected to read as follows: A narrative description of the Proposer s understanding of the need; quality and feasibility of the solution; compliance with all specifications provided to best suit the needs of the Authority; and support services in the form of response time and resources proposed to meet the initial and on-going needs for the Authority from award through delivery and on-going maintenance, if applicable. Include a description of the Proposer s anticipated schedule and milestones from award through delivery and any testing and training. All software and service information should be included in this Proposal Section (i.e. license agreement(s), maintenance agreement(s), etc.). Include a completed Appendix C Requirements Compliance Table. The correction of a typo in Section This Section is hereby corrected to read as follows: A completed Proposal/Pricing Form (see Appendix B).

2 Additional addenda will be issued as soon as possible to address other questions that CRAA received during and following the Pre-Proposal Meeting. Unless otherwise stated, your response shall be considered as including this addendum. Should you have any questions or need additional information, please contact Katie Heisler, at Thank you for your interest in doing business with the Columbus Regional Airport Authority. Sincerely, Katie Heisler Katie Heisler, CPPB Contract and Procurement Specialist Office of Contract and Procurement cc: file

3 ADDENDUM #4 Subject: Request for Proposals: Enterprise Systems Backup Solution, # FIT Due: May 14, 2013 at 2:00 PM EST QUESTION 1. Section 3.1.4: Is cloud storage a requirement for your solution? ANSWER 1. No, it is not a requirement. It is mentioned only to set CRAA s expectations if a cloud solution is proposed. QUESTION 2. Section states a minimum of 200TB, but Appendix A states 70TB. Can you please advise which number we should use for sizing and pricing? ANSWER TB is the current footprint for CRAA s datasets. The solution must support a minimum requirement of 200 TB and should ideally scale up to 1PB. QUESTION 3. What estimate calculations comprise the 200TB requirement? 10-15% growth over the next three (3) years, plus six (6) months retention? Has CRAA accounted for the data that drops off after six (6) months and therefore frees up space? ANSWER 3. CRAA has not calculated retention requirements. CRAA needs to retain 80% of backups for 30 days, 10% for 60 days, and 10% for 180 days. QUESTION 4. Regarding Section 3.3.3: Does CRAA need licensing to support the 200 TB or 1PB? Does CRAA want a traditional versus capacity licensing model? How many clients would need to be included in licensing? ANSWER 4. The solution must offer licensing geared to 70 TB, but CRAA would like an a la carte option on licensing for more. The number of client systems is addressed in Addendum 1. If there is a significant savings between a capacity or client licensing model, CRAA would like to see those options.

4 QUESTION 5. We would like to verify that due to dynamic growth and ever-changing infrastructure for Columbus Airport Authority that you would like to have a flexible licensing model that is designed around your capacity needs/growth and offers unlimited licenses for the storage infrastructure. Is our assumption correct? ANSWER 5. Yes; that assumption is correct. QUESTION 6. Can LCK be a replication site for data? ANSWER 6. No, storage limitations do not allow for replication of all critical data. QUESTION 7. Can the proposed solution reuse current CRAA tape, or does new tape need to be provided? ANSWER 7. If tape is part of the proposal, CRAA prefers new tape as the current tape is end-of-life. QUESTION 8. Does the solution have to offer backup to disk or tape? ANSWER 8. CRAA has not required a specific media that must be used. This is open to Proposers. QUESTION 9. Is archiving a requirement of the solution? ANSWER 9. No, archiving is out of scope for the subject RFP. QUESTION 10. Where can a second set of data be placed since it is best practice to keep a copy of deduplicated data? ANSWER 10. Unless storage limitations are addressed as part of the solution, a second copy of data is not feasible.

5 QUESTION 11. Is everything backed up to NetApp or other storage; direct attached storage versus SAN storage? Are those physical or virtual servers? ANSWER 11. CRAA estimates that 90% is backed up on the NetApp storage, 10% is backed up to locally attached physical storage. QUESTION 12. Is CRAA licensed for Snapshot, SnapVault or SnapMirror on NetApp? ANSWER 12. Yes; CRAA is licensed for all of these. QUESTION 13. Regarding Section 3.1.3: Should data be encrypted at rest or in flight? Does all 70 TB of data need to be encrypted? ANSWER 13. All data should be encrypted at rest, but if the solution is cloud-based then data must be encrypted in flight. QUESTION 14. Is Rickenbacker Airport (LCK) a disaster recovery site or does data reside there only? ANSWER 14. Data resides at LCK; it is not CRAA s disaster recovery site. QUESTION 15. Are both Port Columbus (CMH) and Rickenbacker (LCK) locations for data backup? Can CRAA provide a breakdown of data types at each location? ANSWER 15. Yes, both locations are used for data backup. CRAA currently backs up file servers, virtual servers, and databases at LCK, which comprise less than 10% of the total backup needs, and all backups reside at CMH. QUESTION 16. How is CRAA using tape today? What is your offsite strategy? ANSWER 16. We use tape (LTO 4 drives) to offer continuous backup for file server and physical systems. Offsite strategies speak more to disaster recovery rather than the actual backup solution. CRAA is not considering off site strategies at this time.

6 QUESTION 17. What is CRAA s current backup schedule by system and data type, and does it currently meet your backup window? ANSWER 17. Virtual servers are backed up weekly with a full and incrementals nightly in between. Databases are backed up multiple times daily, with TLog backups to give up to single transaction recovery. Exchange is backed up daily, with Tlogs. File systems are backed up multiple times daily, to provide recovery to within hours. QUESTION 18. Regarding Section 3.4.1: Will CRAA hit 1PB within three (3) years? ANSWER 18. It is unknown if CRAA will require 1PB of storage within three years. It depends on the growth rate of data, and whether or not our internal business partners require additional data protection that we currently do not offer. QUESTION 19. What types of data does CRAA backup, or expect to backup in the future (image, video, structured, unstructured, etc.)? ANSWER 19. Virtual servers, Databases (SQL, Exchange, Sharepoint), file servers, and possibly HD video in the future. The data is largely unstructured. QUESTION 20. If a new solution is proposed, how many people in CRAA will need training? ANSWER 20. Three (3) to six (6) people may require training, and will depend on how Section on Page 15 of the subject RFP is addressed. QUESTION 21. Regarding Section 3.4.3: Do your migration tools need to support tape or disk backups? ANSWER 21. If data needs to be imported from the old storage mediums, then yes.

7 QUESTION 22. Regarding section 3.3.1: Is CRAA opposed to a non-windows backup appliance? ANSWER 22. CRAA is open to any solution that meets the requirements of the RFP. Section is hereby changed to a SYSTEM/STORAGE - PREFERRED REQUIREMENT, and is corrected to read as follows: The solution should function on Windows Server 2008 R2 or better as it will be installed on CRAA Windows Server 2008 R2, or a more current version. QUESTION 23. What UNIX-based system(s) does CRAA currently have? ANSWER 23. CRAA has no Unix systems. Linux varieties are all that we currently have deployed in the environment. Section is hereby corrected to read as follows: The solution must be able to backup and restore all Microsoft Windows operating system versions, from 2000 forward, and variants of Linux. QUESTION 24. Can CRAA provide details regarding its disaster recovery site topology, location and connectivity? For disk-based solution can you provide a replication target? What is the speed of the network link between CMH and LCK? ANSWER 24. CRAA will not be replicating backup data to a disaster recovery site at this time. Disaster recovery sites and options are currently under review in a separate initiative and are not being considered as part of the backup solution scope. Due to current storage limitations, backup data replication may not be possible. The link speed between LCK and CMH is 500MB. QUESTION 25. Is CRAA supplying backend connectivity, or is the selected vendor supplying it? ANSWER 25. CRAA will provide back end connectivity. The network backplane is 10G with 1 and 10G interconnects.

8 QUESTION 26. Regarding Section 5.3.1: Would a subcontractor s experience count towards the requirement for three (3) years of experience? ANSWER 26. Proposers may submit subcontractor experience as part of the requirement, but such experience will be evaluated by the CRAA selection team in relation to the proposed solution and scope of work. However, this may result in a lower technical score for the Proposer. QUESTION 27. Is all data currently backed up? ANSWER 27. No; CRAA is not backing up all the data, but all critical data is backed up. Storage estimates are set to cover all critical data to be backed up. QUESTION 28. How is CRAA currently backing up the Linux-based systems? ANSWER 28. CRAA is using local backup jobs to the servers.

9 SECTION APPENDIX C - REQUIREMENTS COMPLIANCE TABLE (indicate Y=yes or N=no, for the solution's ability to meet each requirement listed) BACKUP/RESTORE MANDATORY REQUIREMENTS REQUIREMENT A single solution must provide enterprise-wide backup and restore capability for the following: Virtual Servers, Physical Servers, MS SQL Server Databases (2000, 2005, 2008 or greater), MS Exchange 2010 or greater, MS SharePoint 2010 or greater. The solution must have the ability to restore individual data files. This refers to general data files; special considerations for Exchange, SharePoint, etc. are addressed in separate requirements. Each backup must be encrypted. For cloud-based storage proposals, the backup solution must provide a local copy, in case the connection to the remote site is degraded/lost. The solution must provide streaming capability. The solution must be capable of restoring SharePoint to a point in time. The solution must be able to restore individual SharePoint objects. The solution must be able to backup Exchange 2010 or greater in a clustered environment. The solution must be able to restore Exchange mailboxes to the individual level. The solution must permit backup to multiple mass storage and media types. The solution must allow for the backup of open/locked files. The solution must allow for multi-domain/multi-forest level setups. The solution must have the ability to backup and restore Microsoft Active Directory. BACKUP/RESTORE PREFERRED REQUIREMENTS The solution should provide file compression. The solution should provide data de-duplication (not backing up duplicate data). Backups should be policy-based. The solution should have the capability for a bare metal restore. SYSTEM/STORAGE COMPATIBILITY MANDATORY REQUIREMENTS The solution should function on Windows Server 2008 R2 or better as it will be installed on CRAA Windows Server 2008 R2, or a more current version. NOW A PREFERRED REQUIREMENT PER ADDENDUM # 4. The solution must be able to backup and restore all Microsoft Windows operating system versions, from 2000 forward, and variants of Linux. The solution must be able to backup a minimum of 200TB (terabytes) of data (see Appendix A for more information). SYSTEM/STORAGE COMPATIBILITY PREFERRED REQUIREMENTS The backup solution should be scalable to 1 PB (petabyte). The solution should use Microsoft Active Directory for authentication/credentials. The solution should provide migration tools for existing data sets. MANAGEMENT/MONITORING MANDATORY REQUIREMENTS The solution must be managed from a single interface. A single pane of glass (one console) will be used to monitor backup status, notifications, and any reporting for all backup types. The solution must include a dashboard with real-time reporting that provides a health check view for all backups. The solution must provide the ability to send alerts via multiple notification methods. The solution must provide time-based reporting (daily, weekly, and annually). All backup media and catalogs must be importable and searchable. MEETS? (Y/N)

10 MANAGEMENT/MONITORING PREFERRED REQUIREMENTS The solution should provide the ability to create configurable reports. DELIVERY AND IMPLEMENTATION OF THE SOLUTION The solution software, and any required hardware, must be delivered and an accurate invoice submitted to CRAA no later than November 30, It is CRAA s goal that the implementation of the solution will be completed by the end of Implementation costs shall be invoiced separately from the solution software costs, and any required hardware costs. EXPERIENCE AND PAST PERFORMANCE The Proposer must submit with the response proof documenting at least three (3) years of experience in providing the subject goods and/or services, including information comprised of descriptions/examples of goods and/or services rendered. The Proposer must submit with the response proof documenting client contacts for at least three (3) previous contracts preferably Ohio-based that the Proposer has completed, including: Client Company name, Client Company address, Client contact person name, phone number and , Contract Title, Scope of Services. 3.9 PROJECT MANAGER AND PROJECT SCHEDULE If services are a component of the Proposer s solution, then the following guidelines shall apply: The selected Proposer shall provide a Project Manager with the necessary expertise to oversee and perform the tasks required to ensure the successful and timely implementation of the Solution. The selected Proposer s Project Manager will collaborate with the CRAA Project Manager to develop one (1) comprehensive Project Plan (schedule). The selected Proposer s Project Manager shall submit an updated Project Plan to the CRAA Project Manager at regular intervals, and as project events may require. The detailed Project Plan must set forth the various Project phases with definitive starting and completion dates to be approved by the CRAA. The Project Plan shall include, but not be limited to, the following deliverables: Specifications of all necessary software modifications and/or hardware requirements, Hardware / software installation, Configuration / Testing, Delivery of documentation, Training schedules, System acceptance. Upon Project commencement, the Contractor s Project Manager shall provide a weekly written status report to the CRAA Project Manager. This report shall document the Project's status, identify tasks not on schedule, report problems, and specify how and when problems will be solved SOLUTION IMPLEMENTATION / CONFIGURATION / TESTING The Proposer shall provide an implementation approach, to be approved by the CRAA, along with a To Be logical diagram, noting any equipment that will be retained from the current CRAA environment. The Proposer shall provide a configuration/testing process for the solution, and shall assist CRAA with the configuration/testing phase if needed MIGRATION STRATEGY The Proposer should provide a strategy for migrating the backups to the proposed solution The Proposer should provide a strategy for migrating the existing data sets to the proposed solution.

11 TRAINING The Proposer shall provide a description of solution training proposed for system administrators, user personnel, and/or systems support staff, as applicable. Training must assure that the CRAA users will be capable of continued operation of the software and that CRAA systems development staff will be capable of maintaining the software and handling the diagnosis of software problems. The training description must include a breakdown of related costs and materials, i.e. Reference Guides, Tutorials and Related CDs, etc. DOCUMENTATION The Solution must be fully documented prior to acceptance of the Solution by the Authority. The Authority shall maintain the right to make a sufficient number of copies of all documentation for its own internal use. Documentation must include: Management Overview, Detailed user instructions, Technical Components, programs, files, procedures, etc WARRANTIES Software Warranty. The selected Proposer shall provide a software warranty of at least twelve (12) months as a part of any software license agreement. The warranty must warrant that the software is free of major defects, operates in accordance with vendor documentation, and provides functions and performance as required by these specifications. The software warranty shall commence after acceptance of the software by CRAA. Acceptance of the software shall mean the completion of the testing phase and the software is live in the production environment. Hardware Warranty. The selected Proposer shall provide a hardware warranty of at least twelve (12) months for any proposed hardware. The warranty must warrant that the hardware is free of major defects and operates in accordance with vendor documentation. The hardware shall commence after acceptance of the hardware by CRAA. Acceptance of the hardware shall mean the completion of the testing phase. MAINTENANCE / SUPPORT The first year of any maintenance agreement will commence after acceptance of the software, or acceptance of the hardware, as applicable. The Proposer shall include one (1) year of service support at no additional charge. Year 1 support shall begin after the completion of the testing phase and approval of the final payment. The Proposer shall include estimated costs for annual support for two (2) to ten (10) years. The Proposer shall provide SLA (Service Level Agreement) option details and associated costs for support services. Support must be provided by trained, experienced personnel. The Proposer shall provide evidence of a change management policy, i.e. software patch and release cycles, upgrade path, change to product code. SECURITY The Proposer shall provide evidence of a Security Incident Response Plan that includes customer notification and priority levels. If the solution is cloud-based, the Proposer shall provide exact network communications diagrams for the proposed solution to (at least) the protocol and port level prior to acceptance of the Agreement, and as a condition of Agreement execution If the solution is cloud-based, the Proposer shall provide evidence of its Business Continuity / Disaster Recovery Plan.

12 FILE BACKUP / FILE RECOVERY The Proposer shall provide procedure(s) for adequate backup and recovery of files related to the proposed software. The procedure(s) must assure to a reasonable degree that upon software failure, disk failure, or other system component failure that system databases are restored to their pre-failure status and that data integrity is maintained. HARDWARE / SYSTEM SOFTWARE RECOMMENDATIONS If applicable, the Proposer shall provide hardware recommendations with capacity requirements for the proposed software solution. If applicable, the Proposer shall itemize all required and recommended additional system software to make the proposed software operate in the most efficient manner.