1) ADDITIONAL INFORMATION

Transcription

1 TORONTO TRANSIT COMMISSION ADDENDUM NO._4_ MATERIALS AND PROCUREMENT DEPARTMENT 900 YONGE STREET PAGE OF TORONTO, ONTARIO M4S Z PROPOSAL NO.: P5CE69 TITLE: PROVISION THE SUPPLY AND INSTALLATION OF ENTERPRISE DATA STORAGE This addendum forms part of the Proposal Documents and amends the original Proposal Documents as noted below: ) ADDITIONAL INFORMATION The Terms of and Proponent Response Table have been changed. Refer to the attached pages, which replace the former pages in their entirety: - Terms of (pages 4, 5, 7, 3 & 4) - Proponent Response Table (Appendix A - pages, 0,, 3, 4 & 5) The Proponent shall note in the Proposal Form the number of addenda received during the Proposal period, to acknowledge that the contents form part of its Proposal.

2 Information Technology Services Department P5CE69 Terms of Enterprise Storage and Data Protection HDS toolset Command Suite 7.x Storage Navigator Storage Navigator Modular Device Manager 7.x Tuning Manager 7.x NetApp toolset FilerView CLI OnCommand 5.x System Manager.x NetApp Management Console 3.x Snapshots SnapMirror (pointed out in FIG. ) SnapVault (pointed out in FIG. ) SnapLock (pointed out in FIG. ) SnapDrive SnapManager (SQL/SharePoint) Operations Manager 5.x Protection Manager 5.x Symantec NetBackup 7.x (earlier versions exist on some clients) Symantec Enterprise Vault 0.x Veritas Storage Foundation CA VM:Backup HiDRO.0. Existing FC ports configuration Davisville Path A Switch Total ports Ports Used Ports Free 5300 Corvette Miata Total Davisville Path B Switch Total ports Ports Used Ports Free 5300 Mustang Viper Total 70 4 Hillcrest Path A Switch Total ports Ports Used Ports Free 3900 Yugo of 6 ADDENDUM NO PM-04-0

3 Information Technology Services Department P5CE69 Terms of Enterprise Storage and Data Protection Hillcrest Path B Switch Total ports Ports Used Ports Free 3900 gremlin The Brocade 400s and 3900s are to be replaced as part of the scope of work. Hosts are attached to SAN Fabric using 4 or 8 Gb Emulex HBA (i.e. LPe 50 4 Gb or LPe 00 8 Gb). NIC ports are, or will be made available for an iscsi SAN Fabric if to be implemented as part of the solution. For example each VMware host has: HBA configured as Multipathing. 4 available Gb iscsi initiator NIC ports. Also NetApp Filers use NIC ports for data replication, and FC ports for host access to LUNs and for NDMP dumps to Tape. Below is a detailed description of the port configurations; NAS, NAS FC ports make, model Fibre Channel Host Adapters QLogic 43 All 8 FC ports in use, 0 available speed of HBAs or 4 Gbit NIC ports - make, model Internal BGE 0/00 Ethernet Controller BGE 0/00/000 Ethernet Controller Dual 0/00/000 Ethernet Controller G0 All 5 NIC ports in use, 0 available NAS3 FC ports make, model Fibre Channel Host Adapters QLogic 43 6 FC ports in use, available speed of HBAs or 4 Gbit NIC ports - make, model and speed Internal BGE 0/00 Ethernet Controller BGE 0/00/000 Ethernet Controller Dual 0/00/000 Ethernet Controller G0 All 5 NIC ports in use, 0 available ADDENDUM NO of 6 PM-04-0

4 Information Technology Services Department P5CE69 Terms of Enterprise Storage and Data Protection S-005 S-006 All components of the solution must be certified as compatible with the entire following host Operating Systems; ESX(i) versions 4.x and 5.x, Windows Server version 003 and 008, and HP-UX.3. All components of the solution must be certified as compatible with all of the following applications; vsphere version 4.x and 5.x, Symantec OST, NetBackup version 7.x, Exchange version 00, SharePoint version 00, SQL (including SQL cluster) versions 005, and 008, Oracle versions 9.x, 0.x, and.x, Oracle RAC, ASM, RMAN and Oracle Data Guard. S-007 S-008 S-009 S-00 The Company must provide support for all the products delivered as part of the solution for duration of 3 years. TTC must have access to obtain support via a toll-free phone call 4x7. The support must be at no additional cost. The Company is to provide on-site support (next business day) to assist with any support issues that are not resolvable over the phone for a duration of 90 days after the completion of the work at no additional cost. Management interfaces for all new components would be preferable to be integrated with vsphere client as a "plug-in" Management interfaces for all new components ideally would to be integrated and/or consolidated within a single management console (a.k.a. "single pane of glass")..03 DISK SUBSYSTEM COMPONENT REQUIREMENTS Specific Disk subsystem component requirements include the followings: Req.# Requirement Description Priority DS-00 DS-00 DS-003 DS-004 DS-005 The disk subsystems must be able to store VMware data for vsphere 4.x and 5.x, and must offer integrated protection (subsystem snapshots) that are VMware consistent by way of automated integration with VMware snapshots. The Davisville disk subsystem must have enough usable capacity to be able to store 500 virtual servers (mostly Windows 008 R) with an average vmdk file size of 00 GB in addition to all other capacity requirements. NOTE: all capacity based requirements allow for initial implementation and anticipated growth for one year. The Hillcrest disk subsystem must have enough usable capacity to be able to store 300 virtual servers (mostly Windows 008 R) with an average vmdk file size of 00 GB in addition to all other capacity requirements. NOTE: all capacity based requirements allow for initial implementation and anticipated growth for one year. Each of the two () disk subsystems must have enough usable capacity to be able to provide block based storage of at least 0 TB usable in addition to the VMware capacity listed above (whether block based or file based). NOTE: all capacity based requirements allow for initial implementation and anticipated growth for one year. The Disk Subsystem Component must integrate with vsphere Client to allow for storage provisioning to ESX hosts ADDENDUM NO of 6 PM-04-0

5 Information Technology Services Department P5CE69 Terms of Enterprise Storage and Data Protection SAN-00 SAN-003 SAN-004 SAN-005 SAN-006 The SAN Fabric solution must ensure that both datacentres are fully compatible with each other and that storage replication and cross-site storage visibility is fully supported. The SAN Fabric solution must ensure that all hosts connected to it are capable of utilizing 8Gbs, and have fault tolerant paths. The SAN Fabric solution must completely replace the following existing SAN Fabric hardware currently at TTC, specifically;a. Brocade 3900s located at the Hillcrest datacentreb. Brocade 400s located at the Davisville datacentre The SAN Fabric solution (once implemented) must ensure that there is available port capacity of at least 0 free ports per path, per SAN Fabric type (i.e. FC or iscsi) and per datacentre. NOTE this is to be based on post implementation of all Components included in the RFP. All new SAN Fabric implemented ideally must be integrated with existing FC SAN Fabric at Davisville center..05 DISK-BASED BACKUP SYSTEM REQUIREMENTS Disk-based backup system requirements include the followings: Req.# Requirement Description Priority DB-00 The Disk-Based Backup System must be compatible with NetBackup version 7.x and Symantec OpenStorage (OST) DB-00 The Disk-Based Backup System must allow for Inline Deduplication or a form of Deduplication that does not require any more then 30% free space of the total capacity in order to store backed up data prior to the Deduplication process. DB-003 The Disk-Based Backup System solution must allow for backups of NetApp CIFS volumes directly from NetApp Filers to the disk target in a way that only moves the data over a SAN Fabric (FC or IP) and not over a client/server based corporate IP network segment. DB-004 The Disk-Based Backup System must include the ability to copy backed-up data from the disk target at Davisville to conventional Tape using the TTC's existing Tape Library and Drives. DB-005 The Disk-Based Backup System must allow Active/Active use of both disk targets (one at each datacentre). DB-006 The Disk-Based Backup System must include bi-directional replication between both disk targets (one at each datacentre). The solution must allow for data replication of at least 50% capacity of the smaller Disk-Based Backup System (of the two). DB-007 All replication between both disk targets must be efficient whereby after the initial seeding (initial synchronization copy) has been completed; only incremental deduped changes are replicated. DB-008 The Disk-Based Backup System must allow for replication of data between the two disk targets natively over IP. The replication ports must be redundant ( or more) and must work as a team in an active/active configuration. ADDENDUM NO of 6 PM-04-0

6 Information Technology Services Department P5CE69 Terms of Enterprise Storage and Data Protection DB-009 DB-00 DB-0 DB-0 DB-03 DB-04 DB-05 DB-06 DB-07 DB-08 DB-09 DB-00 The Disk-Based Backup System must be compatible with the TTC's existing SAN Fabric, as well as the SAN Fabric proposed with the RFP. All disk targets must allow for at least 8Gbs connectivity. The Disk-Based Backup System must be able to backup at least TB per hour at each disk target. The Disk-Based Backup System must provide end-to-end data verification and error correction. The Disk-Based Backup System disk targets must allow for nondisruptive (a.k.a. no downtime larger than hours and no forklift upgrades) hardware and software upgrades; including the addition of new disk, replacement of controllers, replacement of ports/interfaces, upgrading of controller firmware, and upgrading the controller operating system. The Disk-Based Backup System must provide comprehensive Monitoring, Reporting, and Alerting capabilities that gives TTC's backup administrators with ease of access to understand the health and availability of the system. The toolset must be capable of integrating with CA NSM The Disk-Based Backup System must provide 3 TB of usable capacity at both datacentres. NOTES:. This is the actual usable capacity, not the deduplicated capacity.. All capacity based requirements allow for initial implementation and anticipated growth for one year. The Disk-Based Backup System must allow for the non-disruptive addition of 96 TB of usable capacity (not via deduplication or compression) without the need to add or change disk controllers, cache, ports, or other storage hardware. The capacity expansion must only require the addition of disk and any required licensing. The Disk-Based Backup System must provide secured management protocols such as SSH and/or HTTPS, and must include dedicated management ports that are not shared for backing up data. The Disk-Based Backup System must provide automated alerting of failures to both the vendor and to the TTC's backup administrators, via Home Calls at no additional cost. The Disk-Based Backup System must provide continuous protection against any data loss not yet committed to physical disk in the event of a power outage of up to 48 hours. The Disk-Based Backup System's disk target must provide a feature whereby individual disks are monitored for predictive failure and are proactively removed from service prior to an actual disk failure that could cause a loss of data. Authentication to the Disk-Based Backup System's administration tools would be preferable to be based on Active Directory. Integrated (SSO) access is preferred, but if not achievable, then a secure method of authentication is mandatory. 4 of 6 ADDENDUM NO PM-04-0

7 Information Technology Services Department P5CE69 Terms of Enterprise Storage and Data Protection DB-0 DB-0 DB-03 DB-04 DB-05 DB-06 The Disk-Based Backup System would be preferable to be able to utilize existing SAN attached disk subsystems, but only if the solution allows for the replication of all backed up data to the other datacentre. The Disk-Based Backup System (hardware and software as implemented) ideally would support integrated backup and restores of SharePoint 00. The Disk-Based Backup System (hardware and software as implemented) ideally would be preferable to support integrated backup and restores of Exchange 00. The Disk-Based Backup System (hardware and software as implemented) ideally would support integrated backup and restores of VMware. The Disk-Based Backup System (hardware and software as implemented) ideally would support integrated backup and restores of Oracle. The Disk-Based Backup System must offer VTL capability, including emulation of up to Virtual Tape Libraries, emulation of up to 8 Virtual Tape Drives, and emulation of up to 0,000 Virtual Tape Cartridges..06 TRAINING REQUIREMENTS Training requirements include the followings: Req.# Requirement Description Priority Transfer Knowledge TTC On-site training transferring the knowledge, conducted by the TK-00 Company, over the course of 5 days, complete with reusable, printable, editable as built and admin guides. Transfer knowledge must be conducted after all implementation TK-00 services have been successfully completed TK-003 Transfer knowledge materials must be in printable format. Product Manufacturer recommended Administrative Training of products delivered PT-00 Training must be offered for each new product implemented. The training must be performed by a certified training partner of the PT-00 product manufacturer The training must be either publicly offered administrative training, PT-003 or if customized, must be endorsed by the vendor as an acceptable level of training for product administrators Administrative product training needs to be either instructor led either at TTC offices, or within the GTA, or online based training. All Administrative level training must allow the TTC Storage and PT-004 Backup Administrators to be in a position to successfully execute routine day-to-day administrative tasks for all new products implemented and for all existing products that are reconfigured. ADDENDUM NO of 6 PM-04-0

8 Provision for the Supply and Installation of Enterprise Data Storage P5CE69 Proponent Response Table APPENDIX A Item # Requirement TTC Priority TTC Terms of Section Qualifier Proponent Response S 007 The Proponent must provide support for all the products delivered as part of the solution for duration of 3 years. TTC must have access to obtain support via a toll free phone call 4x7. The support must be at no additional cost. 3. S 008 Proponent to provide on site support (next business day) to assist with any support issues that are not resolvable over the phone for a duration of 90 days after the completion of the work at no additional cost. 3. S 009 Management interfaces for all new components would be preferable to be integrated with vsphere client as a "plug in" 3. S 00 Management interfaces for all new components ideally would to be integrated and/or consolidated within a single management console (a.k.a. "single pane of glass"). 3. DS 00 DS 00 DS 003 DS 004 Disk Subsystem Component The disk subsystems must be able to store VMware data for vsphere 4.x and 5.x, and must offer integrated protection (subsystem snapshots) that are VMware consistent by way of automated integration with VMware snapshots. The Davisville disk subsystem must have enough usable capacity to be able to store 500 virtual servers (mostly Windows 008 R) with an average vmdk file size of 00 GB in addition to all other capacity requirements. NOTE: all capacity based requirements allow for initial implementation and anticipated growth for one year. The Hillcrest disk subsystem must have enough usable capacity to be able to store 300 virtual servers (mostly Windows 008 R) with an average vmdk file size of 00 GB in addition to all other capacity requirements. NOTE: all capacity based requirements allow for initial implementation and anticipated growth for one year. Each of the two () disk subsystems must have enough usable capacity to be able to provide block based storage of at least 0 TB usable in addition to the VMware capacity listed above (whether block based or file based). NOTE: all capacity based requirements allow for initial implementation and anticipated growth for one year DS 005 The Disk Subsystem Component must integrate with vsphere Client to allow for storage provisioning to ESX hosts 3.3 ADDENDUM NO.4 Page of 5

9 Provision for the Supply and Installation of Enterprise Data Storage P5CE69 Proponent Response Table APPENDIX A Item # SAN Fabric Component Requirement TTC Priority TTC Terms of Section Qualifier Proponent Response SAN 00 The SAN Fabric solution must ensure complete MultiPath IO (MPIO) to ensure no data or service loss due to any single point of hardware failure. 3.4 SAN 00 The SAN Fabric solution must ensure that both datacentres are fully compatible with each other and that storage replication and cross site storage visibility is fully supported. 3.4 SAN 003 The SAN Fabric solution must ensure that all hosts connected to it are capable of utilizing 8Gbs, and have fault tolerant paths. 3.4 SAN 004 The SAN Fabric solution must completely replace the following existing SAN Fabric hardware currently at TTC, specifically; a. Brocade 3900s located at the Hillcrest datacentre b. Brocade 400s located at the Davisville datacentre 3.4 SAN 005 The SAN Fabric solution (once implemented) must ensure that there is available port capacity of at least 0 free ports per path, per SAN Fabric type (i.e. FC or iscsi) and per datacentre. NOTE this is to be based on post implementation of all Components included in the RFP. 3.4 SAN 006 All new SAN Fabric implemented ideally must be integrated with existing FC SAN Fabric at Davisville center.the SAN Fabric solution ideally would be able to be managed from a single administration console. Disk Based Backup System 3.4 DB 00 The Disk Based Backup System must be compatible with NetBackup version 7.x and Symantec OpenStorage (OST) 3.5 DB 00 The Disk Based Backup System must allow for Inline Deduplication or a form of Deduplication that does not require any more then 30% free space of the total capacity in order to store backed up data prior to the Deduplication process. 3.5 ADDENDUM NO.4 Page 0 of 5

10 Provision for the Supply and Installation of Enterprise Data Storage P5CE69 Proponent Response Table APPENDIX A Item # Requirement TTC Priority TTC Terms of Section Qualifier Proponent Response DB 0 The Disk Based Backup System must provide end to end data verification and error correction. 3.5 DB 0 The Disk Based Backup System disk targets must allow for non disruptive (a.k.a. no downtime larger than hours and no forklift upgrades) hardware and software upgrades; including the addition of new disk, replacement of controllers, replacement of ports/interfaces, upgrading of controller firmware, and upgrading the controller operating system. 3.5 DB 03 The Disk Based Backup System must provide comprehensive Monitoring, Reporting, and Alerting capabilities that make available TTC's backup administrators with ease of access to understand the health and availability of the system. The toolset must be capable of integrating with CA NSM 3.5 DB 04 The Disk Based Backup System must provide 3 TB of usable capacity at both datacentres. NOTES:. this is the actual usable capacity, not the deduplicated capacity.. all capacity based requirements allow for initial implementation and anticipated growth for one year. 3.5 DB 05 The Disk Based Backup System must allow for the non disruptive addition of 96 TB of usable capacity (not via deduplication or compression) without the need to add or change disk controllers, cache, ports, or other storage hardware. The capacity expansion must only require the addition of disk and any required licensing.each disk target must allow for the addition of 96 TB of usable capacity (not via deduplication or compression) without the need to add or change operating system, disk controllers, cache, ports, or other hardware or software resources other than disk and licensing. 3.5 DB 06 The Disk Based Backup System must providesupport secured management protocols such as SSH and/or HTTPS, and must include dedicated management ports that are not shared for backing up data. 3.5 DB 07 The Disk Based Backup System must provide automated alerting of failures to both the vendor and to TTC's backup administrators, via Home Calls at no additional cost. 3.5 DB 08 The Disk Based Backup System must provide continuous protection against any data loss not yet committed to physical disk in the event of a power outage of up to 48 hours. 3.5 ADDENDUM NO.4 Page of 5

11 Provision for the Supply and Installation of Enterprise Data Storage P5CE69 Proponent Response Table APPENDIX A Item # Requirement TTC Priority TTC Terms of Section Qualifier Proponent Response DB 09 The Disk Based Backup System's disk target must provide a feature whereby individual disks are monitored for predictive failure and are proactively removed from service prior to an actual disk failure that could cause a loss of data. 3.5 DB 00 Authentication to the Disk Based Backup System's administration tools would be preferable to be based on Active Directory. Integrated (SSO) access is preferred, but if not achievable, then a secure method of authentication is mandatory. 3.5 DB 0 The Disk Based Backup System would be preferable to be able to utilize existing SAN attached disk subsystems, but only if the solution allows for the replication of all backed up data to the other datacentre. 3.5 DB 0 The Disk Based Backup System (hardware and software as implemented) ideally would support integrated backup and restores of SharePoint DB 03 The Disk Based Backup System (hardware and software as implemented) ideally would be preferable to support integrated backup and restores of Exchange DB 04 The Disk Based Backup System (hardware and software as implemented) ideally would support integrated backup and restores of VMware. 3.5 DB 05 The Disk Based Backup System (hardware and software as implemented) ideally would be preferable to support integrated backup and restores of Oracle. 3.5 DB 06 The Disk Based Backup System must offer VTL capability, including emulation of up to Virtual Tape Libraries, emulation of up to 8 Virtual Tape Drives, and emulation of up to 0,000 Virtual Tape Cartridges. 3.5 ADDENDUM NO.4 Page 3 of 5

12 Provision for the Supply and Installation of Enterprise Data Storage P5CE69 Proponent Response Table APPENDIX A Item # Training Transfer Knowledge Requirement TTC Priority TTC Terms of Section Qualifier Proponent Response TK 00 TTC On site training transferring the knowledge, conducted by the Proponent, over the course of 5 days, complete with reusable, printable, editable as built and admin guides. 3.6 TK 00 Transfer knowledge must be conducted after all implementation services have been successfully completed 3.6 TK 003 Transfer knowledge materials must be in printable format. 3.6 Product Manufacturer recommended Administrative Training of products delivered PT 00 Training must be offered for each new product implemented 3.6 PT 00 The training must be performed by a certified training partner of the product manufacturer 3.6 PT 003 The training must be either publicly offered administrative training, or if customized, must be endorsed by the vendor as an acceptable level of training for product administrators 3.6 PT 004 Administrative product training need to be either instructor led either at TTC offices, (on site or off but within the GTA), or online based training. All Administrative level training must allow TTC Storage and Backup Administrators to be in a position to successfully execute routine day to day administrative tasks for all new products implemented and for all existing products that are reconfigured. 3.6 ADDENDUM NO.4 Page 4 of 5

13 Provision for the Supply and Installation of Enterprise Data Storage P5CE69 Proponent Response Table APPENDIX A Item # Implementation Requirement TTC Priority TTC Terms of Section Qualifier Proponent Response I 00 The solution's implementation services must include a total of 0 hosts 5 at each datacentre specifically ESX hosts, Windows hosts, and UNIX host. 3.7 I 00 The solution must include the implementation of VMware Site Recovery Manager (SRM) with integrated storage management via a vcentre plug in, and must include at lease one datastore and test virtual Windows machines in a proof of concept. 3.7 ADDENDUM NO.4 Page 5 of 5