Annexure - I RFP for a Purpose Built Backup Appliance (PBBA) for IUCAA

Transcription

1 I. Introduction Annexure - I RFP for a Purpose Built Backup Appliance (PBBA) for IUCAA IDC (International Data Corporation) defines a purpose-built backup appliance (PBBA) as a standalone disk-based solution that utilizes software, disk arrays, server engine(s), or nodes that are used for a target for backup data and specifically data coming from a backup application software (CommVault, DataProtector, NetWorker, NetBackup etc.) or can be tightly integrated with the backup software to catalogue, index, schedule, and perform data movement. IUCAA's IT infrastructure (Annexure-II) consists of virtual desktop/server environments and NFS / CIFS shared filesystems mounted on Linux/VDI desktop hosts serving academic and administrative staff respectively. Apart from that, important application servers such as /dns/dhcp/ldap/ad and IUCAA office automation software (ioas) server etc. need to be backed up routinely. Most of our servers are being served from VMWARE based virtualized environment tightly coupled with 3PAR common storage. II - Objective 1) The purpose behind issuing this RFP is to invite technical and commercial bids for identifying a service provider who would offer best in class Backup Solution. 2) Keeping in view the existing and future requirement of IUCAA, the proposed solution should be Scalable & Highly Available. 3) The bidder is expected to implement the solution at the old Datacentre (DC), IUCAA and it should be capable of supporting replication process to be done at a proposed DC, located a Kilometre away from the existing one, when it is ready. 4) The selected bidder is expected to maintain the PBBA for 5 years. Patch upgrade on a regular basis is mandatory. 5) It may also be noted that all the activities in the IT operation are subjected to audit inspection by Security Auditors. Selected bidder must take the same into consideration while delivering the desired services. 6) The bidder has to implement suitable solution which will ensure that backup is done in a fast, efficient & reliable manner without putting much load on the existing infrastructure. 7) The solution should be for automating backup, including latest features such as data encryption etc. III - Features expected in a PBBA: 1) The Disk to disk proposed PBBA shall be modular in design i.e. allow capacity increase to enhance its performance. 2) The proposed device shall be scalable to more than 150TB usable capacity. The bidder is expected to refer to Annexure-III and to propose a suitable sizing taking into consideration the retention policy mentioned in the same. It should provide adequate scalability to handle a projected Data 20% per year for 3 years in the same system. Please note that the amount of storage required is driven by the degree of deduplication efficiency offered by the appliance. For the same amount of data & retention, some vendor may require more usable capacity than the other. Deduplication percentage defines the actual storage requirement. Therefore the calculation on sizing of the appliance should be explained with appropriate charts. 3) The proposed device shall be protected with hardware RAID 6 from the factory. 4) The proposed device shall support VTL/Deduplication Disk. i.e. providing multiple types of workloads (backup, replication) and interfaces (NFS, CIFS, VTL, OST) to a single deduplication system.

2 5) The proposed device shall have the capability to deliver selective restore from disk Library itself. 6) The proposed device shall have integrated de-duplication license for the suggested capacity for VTL / Deduplication disk as well as NAS and shall have support for replication to remote location in a low bandwidth mode. 7) The proposed device shall support intelligence to understand Source based (at client application level, backup server level and media server level) de-duplication so that only unique non duplicated data is copied to the proposed device. 8) The proposed device shall support receiving non duplicated data from remote locations or branch office directly from the application servers / client servers in low bandwidth mode without using any backup or replication based device at remote location / Branch office. Please attach bandwidth calculation sheet. 9) The proposed device shall have the ability to flexibly emulate tape drive/ tape formats LTO- Gen4 to LTO-Gen7 or the latest generation or it should have the ability to configure deduplicated disk. In case of deduplicated disk, it should offer mechanism for taking the backup on a physical tape library from the appliance / management console seamlessly without additional license or overhead. In case of deviation, please elaborate how it is done with your proposed solution. Please provide the flow diagram. 10) The proposed device shall have a minimum of 4 x 8Gbps Fibre Channel connections and a minimum of 2 x 10Gbps ISCSI / Ethernet connections. 11) The proposed disk based backup device shall also support encryption functionality. To ensure data security, the solution should support data encryption in flight and at rest. The solution should offer data encryption in the physical tape library as well when implemented. 12) The proposed disk based backup appliance shall have flexibility to enable or disable the deduplication for a given virtual tape library or NFS / CIFS share or deduplicated disk. 13) The proposed disk based backup appliance shall support VLAN tagging. The proposed IP ports shall also support Port bonding in Adaptive Load balancing, LACP and as well as in Active-backup mode. 14) The proposed solution shall support root cause analysis and charge back reporting of backup & replicated data. It shall offer real time centralized management, monitoring and analysis for all sites. It shall support automated real time notification and SNMP alerts. In case of deviation, please give justifying reasons for the absence of this feature in your proposed solution with supporting documents. 15) The proposed device shall support rated write performance of at-least 7TB (+/- 10%) per hour and when enabled with source level de-duplication, shall have rated performance of at least 20 TB/hr (+/- 10%). In case of deviation, please provide the rated performance metric for the proposed PBBA. It should be able to offer restore performance for operation recovery to less than 12hrs. It should be able to keep the backup window under 15hrs over 3 years, taking into account the projected data growth. It shall offer performance without compromising on the global deduplication i.e within a single dedupe pool or without any performance penalty arising due to concurrent activities on the appliance such as backup, restoration, replication and housekeeping.

3 IV - The proposed Backup software (SW) 1) The proposed backup SW solution should be available on various OS platforms such as Windows, Linux and UNIX platforms (AIX/HP UNIX/Solaris). 2) The proposed backup SW solution shall support industry leading cluster solution such as MSCS, HP Service Guard and Veritas Cluster. 3) The proposed backup SW solution shall have same GUI across heterogeneous platform to ensure easy administration. 4) The proposed backup SW solution should support tape mirroring of the same job running concurrently with primary backup. 5) The proposed backup SW solution should allow creating tape clone facility after the backup process. 6) The proposed backup SW solution should be configured in such a fashion that no extra license for client and media servers is required while moving from LAN to SAN based backup. 7) The proposed backup solution shall be configured with unlimited client and media licenses for both SAN based backup and LAN based backup. 8) The proposed backup solution must not require separate licensing when upgrading from a lower end server (1-2 CPU-based server) to higher end server (4-and CPU-based server). 9) The backup software shall support either the Capacity based model or Application based model of licensing The backup software should be able to support up to 40 Million (+/- 10%) files per directory. In case of deviation, please mention the supported number of files per directory by your proposed software. 10) The proposed backup solution shall support the capability to write up to 32 (+/- 10%)data streams. In case of deviation, please mention the supported number of streams. 11) The proposed backup solution shall support de-multiplexing of data cartridges to another set of cartridges for selective set of data for faster restore operation to client/servers. 12) The proposed backup solution should have in-built media management. It also shall support cross platform device and media sharing in SAN environment. It shall provide a centralized scratch pool thus ensuring backups never fail for media. 13) The proposed backup solution shall have in-built frequency and calendar based scheduling system. 14) The proposed backup solution shall have certified hot-online backup solution for different type of Enterprise databases and applications. 15) The proposed backup solution shall also support granular recovery for VMWare, Exchange server, Share point Portal.

4 16) The backup software should support Non Staged Granular recovery in VMWare. 17) The proposed backup software should use the same API for software and hardware deduplication. 18) The proposed backup software should be IP v6 compliant. V- Hardware Warranty & Support The solution must include comprehensive on-site warranty, covering all parts, for a minimum 5 year period starting from the date of installation and acceptance of the system by IUCAA on 24*7*365 basis. This includes installation of latest updates/patches of firmware/software as and when released by the bidder. The bidder shall be fully responsible for the warranty of all equipment, accessories, spare parts, software, etc. against any defects arising from design, material, manufacturing, workmanship or any act or omission of the manufacturer and/or bidder any defect that may develop under normal use of supplied equipment during warranty period. During the warranty period of equipment, the bidder shall not assign any kind of maintenance like hardware, software, upgradations etc. related to these equipment to any third party. Warranty should not become void if the purchaser buys any other supplemental hardware from third party and install it with/in these machines. However, the warranty will not apply to such hardware items installed. The complaint should be resolved at the earliest with following uptime and conditions Complaint must be rectified at the earliest of receipt of complaint to maintain uptime of 99.5% per month. Warranty should cover updates/maintenance patches/bug fixes (available from the original software bidder) for system software & firmware patches/bug fixes, signatures, if any, for hardware. The bidder should provide onsite preventive maintenance on a quarterly basis. The bidder is required to provide sound after-sales service/support by arranging timely attending of calls received from IUCAA and problem rectification through competent service engineers within 4 Business Hours. To meet uptime the bidder has to maintain sufficient inventory of spare parts/equipment at all the support centres to avoid unnecessary delay in obtaining the spare parts/equipment. The bidder must supply the details of its service/support infrastructure meant for registering the complaints along with the contact numbers like mobile nos., phone nos., electronic mail addresses and names etc. of its service engineers. VI - PBBA Hardware Requirement Sr. No Description Data Remark Input for Backup sizing and capacity planning 1 Volume of Source Data 70 TB Backup appliance will be hosted in 2 Daily Data Change Ratio (%) 5 % the old datacentre. Replication shall 3 Annual Storage Growth 20% be possible for hosting the DR in a cloud or co-locating a virtual appliance / a PBBA in a remote place.

5 Average Retention Requirements in numbers 4 Data Retention for daily incremental (weeks - 6 inc. a week Mon-Sat) 5 Retention for weekly full backups(weeks) 4 6 Retention for monthly full backups (months) 3 7 Retention for yearly full backup (years) 1 6 PBBA with the size to be calculated based on the comprehensive backup schema provided in Annexure-III For Zimbra data, the retention is quite different. Deduplication Parameters in percentage (%). 8 Expected deduplication ratio for the initial backup This should be demonstrated. 20% 9 Expected deduplication ratio for the daily incrementals payment will be made after a successful demonstration of backup 10 Expected deduplication ratio for the weekly full backups Expected deduplication ratio for the Monthly full backups Expected deduplication ratio for the Yearly full backups process for a period of one month. Please size the PBBA (including storage and Server) requirements for 3 years as follows: Year1 Year2 Year3 Estimated storage requirements after retention period in TB Proposed solution should be scalable i.e. it should be possible to add CPU, disks, RAM etc in order to support future expansion of PBBA. Since the solution varies with the vendor, please give the detailed Bill of materials in terms of hardware (PBBA, management console (server)), software and licensing cost. If the cost is right, IUCAA may opt for the solution needed for 3 years in the beginning or it would procure in stages ie every year by signing a rate contract. Therefore please give your year wise expansion option with price proposed for 3 years. Vendors are expected to do a site survey/discussion before the tender submission date to understand the site better. VII- Bid Evaluation Methodology 1. Introduction The objective of evaluation methodology is to identify a suitable technically superior solution at an optimal cost. The proposed evaluation process of the bids to be adopted by IUCAA is indicated below. The purpose of it is only to provide the bidder an idea of the evaluation process that IUCAA may adopt. IUCAA reserves the right to modify the evaluation process at any time during the tender process (before submission of technical and commercial responses by the prospective bidder), without assigning any reason, whatsoever, and without any requirement of intimating the bidders of any such change. Any time during the process of evaluation IUCAA may seek specific clarifications from any or all the bidder. It may please be noted that IUCAA reserves the right to reject any proposal in case the same is found incomplete or not submitted in the specified format given in this RFP document. The details of Minimum Eligibility Criteria, provided by the vendor in its response to this RFP, will be evaluated first, based on the criteria described in section 2. The technical and commercial responses to this RFP will be considered further only for those vendors who meet the Minimum Eligibility Criteria. Vendors must provide their responses to the table specific to bidder information in the format given in the RFP. The technical and commercial response evaluation will be based on the criteria described in the following section onwards. 2-Minimum Eligibility Criteria Proposals not complying with the minimum eligibility criteria are liable to be rejected and will not be considered for evaluation of technical bid. The proposal should adhere to the following minimum eligibility criteria.

6 The bidder should preferably be an OEM/Authorized System Integrator Company incorporated in India and should have 5 year experience in implementation of Backup solution. The bidder should have sufficient experience in successfully implementing SAN based Backup Solution in at least three Govt funded research institution/banks/psu/any organization in India. The bidder should submit details like name of contact person, along with his/her phone number for above projects. The bidder should provide a list of 3 reference sites with purchase orders, contact details ( , phone) of the reference customers. The bidding Company / OEM should have a valid ISO 9001 or ISO certificate. The backup software solution proposed by the bidder should be listed in the latest/current Gartner s Magic Quadrant report / IDC report or any report from non-partisan reviewing agency for backup software / PBBA solutions. The bidder should have direct support office in Pune and should be able to provide support and maintenance for the offered solution. Documentary proof (Office registration details etc.) to be submitted along with the bid. Vendor should submit documentary evidence in respect to all above mentioned criteria (For example Purchase order) while submitting the proposal. Proposal of vendor who do not fulfill the above criteria or who fail to submit documentary evidence thereon would be rejected. Bidders fulfilling all Minimum Eligibility Criteria will only be considered for further technical evaluation. 3- General Terms and Conditions (Technical): 1) The bidder should be an Original Equipment Manufacturer (OEM)/Authorized system integrator (SI) of the OEM and a Letter of Authorization from the OEM, specific to this tender should be enclosed by the bidder. 2) One OEM can authorize maximum two SI for the execution of the PBBA solution. 3) One SI can represent only one OEM for the execution of this project. 4) The OEM will be responsible for the installation and functioning of the proposed PBBA during the warranty period. 5) The entire solution should be validated and certified by the OEM. 6) The OEM along with the SI(s) must attend the Technical Evaluation Committee (TEC) meeting to clarify the technical queries raised by TEC. 7) The bidder is expected to submit a detailed solution architecture showing the proposed major components such as backup appliance, backup management console, backup software etc. and the SAN/10G connectivity based on the IUCAA IT infrastructure diagram provided in Annexure-II. 8) Any other hardware or software and any other component that is not included in the tender but is required for the completion of the project, is to be listed by the bidder. 9) IUCAA reserves the right to accept / reject or increase/decrease quantity of any or part of the offer without prior intimation. It also reserves the right to impose any further terms and conditions if deemed necessary. 10) The licensed software stack quoted for the backup solution should be perpetual in nature and preferably from the same vendor. 3. Evaluation of Technical Bids Minimum Eligibility Criteria bids received from the bidder will be opened in the presence of representatives of the bidders who choose to be present as per the schedule stipulated by IUCAA. A detailed analysis will be subsequently carried out by IUCAA. The technical bid will be analyzed and evaluated, based on which the Relative Technical Score (RTS) shall be assigned to each bid. Technical Bids receiving a RTS greater than or equal to a score of 75 (cut-off marks) will be eligible for consideration in the subsequent round. The Parameters of the Technical evaluation are broadly as follows:

7 4. Mark Distributions Maximum Points 100 Expectations Criteria Points (Max Marks) The bidder should have implemented minimum 1 Backup solution (SAN connected), (Only last 3 years contracts will be considered for awarding points) (LC stands for Large Corporate Corporate having at least 25 offices across the country, FI stands for financial institution) For 3 or more in Govt. Sector / PSU/Banks/FIs/LC in India For 1 Govt. Sector / PSU/Banks/FIs/ LC in India The offered backup software solution/pbba is amongst top 5 solutions as per current/latest Gartner / IDC /Forrester Report. Please submit the documentary evidence. Yes No Satisfactory Services Certificate by at least one Client where Backup implementation project was carried out (Should be current and valid) (Specific to SAN Based Backup; 1 per year for the last 3 years) Satisfactory Services Certificate from 3 Clients Satisfactory Services Certificate from 2 Clients Implementation of Backup solution on Windows Server 2008 platform or greater,/ Linux (Only last 3 years contracts will be considered for awarding points) Backup size 50 TB and above Backup size TB Backup size 1-25 TB The bidder is expected to carry out a Proof of Concept for the proposed solution as per the instructions given in Annexure-IV and to submit the result by repeating the backup and restore processes 3 times. The result submitted should be successfully demonstrated during the installation by the successful bidder within +/-3% deviation. Based on the performance top 3 vendors will be graded. Stood first in the POC conducted. Stood second in the POC conducted. Stood third in the POC conducted. Marks to be given for the response for the questionnaire (Annexure-V) and rank them based on the features offered. Best Better Good Max Marks 05 Max Marks 15 Max Marks 10 Max Marks 20 Max Marks 30 Max Marks 20 Bidders have to provide copies of supporting documents against each criteria mentioned above, without which bid may be rejected. The minimum qualification score for the Technical Bid would be 75.

8 5. Financial Bid Only firms successfully qualifying the requisite criteria of the Technical Bid process would be considered eligible for the Financial Bid Round. The evaluation of the Financial Bids would be as follows: The lowest bid will be assigned the maximum Financial Score of 100 points. The Financial Scores of the other Financial Bids will be computed relative to the lowest evaluated Financial Bid. The Financial Score computing methodology is as follows: 100 X Price (Lowest Bid) Financial Score (for bid under consideration) = Price (Bid under consideration) 6. Final Processing Proposals would be ranked according to their Final Score arrived at by combining Technical and Financial Scores as follows: Final Score = Technical Score x T + Financial Score x F (T - Weightage given to the Technical Bid, F - Weightage given to the Financial Bid, T + F = 1) Weightage for the bids are as follows: I. Technical Bid T 60% II. Financial Bid F 40% Total Weightage 100% The firm achieving the highest combined Technical and Financial Score will be invited for negotiations. IUCAA reserves the right to revise the evaluation criteria, methodology, distribution points and weightage; if it finds it necessary to do so.