CORRIGENDUM 2. Ref. No.: GAIL/ND/C&P/BIS/ / / February 23, Tender no. : GAIL/ND/C&P/BIS/ /

Transcription

1 CORRIGENDUM 2 Ref. No.: GAIL/ND/C&P/BIS/ / / February 23, 2009 Tender no. : GAIL/ND/C&P/BIS/ / Name of Work : TENDER FOR UPGRADATION, CONSOLIDATION, DISASTER RECOVERY (DR) & ARCHIVAL OF SOLUTION AND UPGRADATION OF ACTIVE DIRECTORY WITH BUYBACK OF OLD SERVERS The clauses of Tender Document referred above are modified to the extent as indicated below: Revised Dates: Due date and time for Submission of Bid : 1400 Hrs on Due date and time for Opening of Technical Bid : 1500 Hrs on Section 4 (SCC) Annexure A : Item No. A.12, A.13, A.14, A.15, A.17, A.19, A.20, B.3, C.6, C.7 Please Read Chipset - Intel 5000P / 7300 Chipset Processor - Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above In place of Chipset - Intel 7300 Chipset Processor - Min. 2 * Quad Core Intel Xeon (2.66 GHz, 1333 FSB) or above Section 4 (SCC) Annexure A : Item No. A.16, A.18 Please Read Processor - Min. 4 * Quad Core Intel Xeon (2.4GHz, 1066 FSB) or above In place of Processor - Min. 4 * Quad Core Intel Xeon (2.66 GHz, 1333 FSB) or above The Corrigendum s shall form an integral part of the tender document and shall be signed/stamped and submitted along with the bid. 1

2 With the incorporation of above corrigendum Annexure A (Item & Its ) have been revised and the same are enclosed below. Bidder has to submit compliance as per the revised compliance sheets duly filled, digitally signed and uploaded as given below: Annexure A (Item ) SN Items & its Qty Meet A AD & Exchange A.1 Windows Svr Std 2008 Sngl OLP D ( for sites ) Note: Bidder can provide S/w Licenses in Electronic/Paper form. A.2 Windows Svr Ent 2008 Sngl OLP D Note: Bidder can provide S/w Licenses in Electronic/Paper form. A.3 Exchange Svr Ent 2007 Sngl OLP D Note: Bidder can provide S/w Licenses in Electronic/Paper form. A.4 Exchange Svr Std 2007 Sngl OLP D Note: Bidder can provide S/w Licenses in Electronic/Paper form. A.5 Exchange Standard CAL 2007 Sngl OLP D User CAL Note: Bidder can provide S/w Licenses in Electronic/Paper form. A.6 Windows Server CAL 2008 Sngl OLP D User CAL Note: Bidder can provide S/w Licenses in Electronic/Paper form. A.7 SQL Svr Standard Edtn Win32 Sngl Lic/SA Pack OLP D Note: Bidder can provide S/w Licenses in Electronic/Paper form. A.8 Windows Svr Std bit/x64 English Disk Kit MVL DVD Note: Software media can be provided either in the form of OEM Media or after download from OEM Website. A.9 Windows Svr Ent bit/x64 English Disk Kit MVL DVD Note: Software media can be provided either in the form of OEM Media or after download from OEM Website. 2

3 SN Items & its Qty Meet A.10 Exchange Svr 2007 English Disk Kit MVL 1 DVD Note: Software media can be provided either in the form of OEM Media or after download from OEM Website. A.11 Exchange Svr Ent 2007 English Disk Kit MVL DVD Note: Software media can be provided either in the form of OEM Media or after download from OEM Website. A.12 Root Domain Controller 1 1 Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 8 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots. Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission 3

4 SN Items & its Qty Meet Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. A.13 Additional Domain Controller 2 Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 8 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor 4

5 SN Items & its Qty Meet Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. 14 Exchange 2007 CAS Noida DMZ (64 bit) 1. Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 8 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). 5

6 SN Items & its Qty Meet Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission Ports Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. A.15 Exchange 2007 CAS & Hub Transport Server (64 bit) 2 Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 8 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots 6

7 SN Items & its Qty Meet HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller with 64 MB cache (capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. A.16 Exchange 2007 Mailbox Server (64 bit) 4 Processor Min. 4 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 32GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC 7

8 SN Items & its Qty Meet configurable as Teamed NIC for network load-balancing. Min. 2 No.s 1/2/4 Gbps Fibre Channel Cards for SAN connectivity IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Either Blade Form Factor OR Rack Mount with OEM Rack Mounting Kit and Internal DVD R/W Drive & LTO 4 Tape Drive Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. A.17 Exchange 2007 Edge Transport Server (64 bit) 2 Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset 8

9 SN Items & its Qty Meet Cache Min. 2 X 6 MB L2 Cache Memory Min. 8 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. A.18 Exchange 2007 Mailbox Server (SCR Target) DR (64 bit) 2 Processor 9

10 SN Items & its Qty Meet Min. 4 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 32GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Mbps NIC configurable as Teamed NIC for network load-balancing. Min. 2 No.s 1/2/4 Gbps Fibre Channel Cards for SAN connectivity IO Expansion Slots Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Either Blade Form Factor OR Rack Mount with OEM Rack Mounting Kit and Internal DVD R/W Drive & LTO 4 Tape Drive Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/

11 SN Items & its Qty Meet Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. A.19 Exchange 2007 Edge Transport 1 Server DR (64 bit) Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 8 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities 11

12 SN Items & its Qty Meet OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. A.20 Exchange 2007 CAS & Hub Transport Server - For DR (64 bit) 2 Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 8GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front 12

13 SN Items & its Qty Meet panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows Server 2003/2008 B Note: All the necessary cables ethernet/fibre/usb/power(indian Style) etc. required for making the system operational, shall be provided by the bidder. RMS B.1 Win Rghts Mgt Svc CAL 2008 Sngl OLP D Device CAL Note: Bidder can provide S/w Licenses in Electronic/Paper form. B.2 SQL CAL Sngl Lic/SA Pack OLP D Device CAL Note: Bidder can provide S/w Licenses in Electronic/Paper form. B.3 RMS Server Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 8 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD 13

14 SN Items & its Qty Meet Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. C Archival and Journaling C.1 Enterprise Journaling solution for compliance purposes compatible with WORM Storage The solution should support archiving from the following MS Exchange 2003/2007 mail servers. 2. The solution should support Exchange Message Journaling as well as Exchange Envelope Journaling without any additional agent software on the Exchange server 3. The solution must support "Agentless" archiving of messages. There should be no need to deploy any agent for archiving of journal 14

15 SN Items & its Qty Meet messages. 4. The solution should support capturing of BCC data during archiving a mail. 5. The solution must support search for mails based on undisclosed recipients criteria 6. The solution should support distribution list expansion while archiving s to ensure that user names are captured instead of just list names. 7. The solution should support manually initiated archival of mails from MS Outlook as well as Outlook Web Access. 8. The solution should support archiving based on either any or a combination of the Item Type (message, calendar etc.), Date, Size, Attachment only and User. 9. The solution should also support creation of "filter-rules" to configure more sophisticated archiving policies 10. The solution should not be dependent on journaling for archiving mails from identified user mailboxes. The two solu should work independent of one another. 11. Customized access to archiving features at the client end (Outlook / OWA) based upon organiza policy. 12. The solution should be able to selectively mark old archived data as "read-only". E.g.. Quarterly archived data should me marked as read-only. 13. The solution shall facilitate migra of outlook PSTs to archive with an automated 15

16 SN Items & its Qty Meet mechanism of discovering the PSTs associated with an Outlook profile and migrating the contents to archives. 14. Migration of PSTs to archives should facilitate keeping the folder structure of the shortcuts same as that of PSTs. 15. The solution should do Single- Instance of same messages on its own without the need of any 3rd party software/storage feature 16. The solution must allow users / administrators to access their respective archived content from a web based interface 17. The solution should provide a client side plug-in. 18. The solution should support creation of shortcuts for every item which is archived. 19. The solution must support removal / deletion of shortcut from the mailbox based upon expiration / deletion of the mail. 20. The solution should allow an administrator to choose to create a shortcut at either the time of archiving or later as well. 21. The solution should allow administrators to push out folders to users that have defined Retention Categories (e.g., a folder that shows up in Outlook called "Financial Filings") under which users can drag / drop relevant mails. 22. The solution should support increasing the retention period of archived items. 23. The solution should allow archival of messages in the native format. 24. The solution should allow users to 16

17 SN Items & its Qty Meet view their archived s irrespective of the underlying client version (Outlook 2000 / 2003 / XP / 2007 etc.) 25. The solution should provide Single Instancing of items irrespective of the underlying storage hardware or any third party technology 26. The solution should support tiered storage concept. Archived items can be moved from one set of disks to another based upon criteria specified by the administrator. This should also be seamlessly accessible by the user for search / retrieval. 27. The solution should support compression of messages as well as attachments with an overall compression ratio of 50 to 60% 28. The solution should have the capability to archive messages from multiple vers of exchange into the same repository. 29. The solution should support full indexing of messages based on metadata, message bode, attachment, and should allow users to search using keywords and phrases. 30. The solution should be capable of indexing around 70+ different file types. 31. The solution should facilitate retrieval of archived item in case the primary application, Exchange 2007 is no longer available 32. The solution should provide out of the box reporting and also provide integration with third party reporting tools. E.g. Crystal reports. 33. The solution should provide application logs on its system status and opera. Some 17

18 SN Items & its Qty Meet examples of these events are: Status of services/tasks (stop/start), Archive task (when archiving of mailboxes start), Failures (retrieval, expand distribution list, etc), Conflicts (Permission, storage device unavailable, etc) 34. The solution should provide a web based operation manager to allow administrators to keep track of events and activities. 35. The solution should provide an inbuilt mechanism to prevent users from tampering with the archive or items in the archive and should not be dependent on any kind of Hardware or Storage for the same. 36. The solution should enable users to access the archived items to which they have permiss, and prevent them from accessing anything else. 37. The solution should support users that have shared mailboxes. 38. The solution should be clusteraware and should be clusterable using clustering solu on windows 39. The solution should also facilitate a cold standby on which the archiving services can be quickly failed over. Note: Bidder can provide S/w Licenses in Electronic/Paper form. C.2 Operational Archiving for Mail Optimization Capture and Management 1. The solution should support archiving from the following MS Exchange 2003/2007 mail servers. 2. The solution should support Exchange Message Journaling as 18

19 SN Items & its Qty Meet well as Exchange Envelope Journaling without any additional agent software on the Exchange server 3. The solution must support "Agentless" archiving of messages. There should be no need to deploy any agent for archiving of journal messages. 4. The solution should support capturing of BCC data during archiving a mail. 5. The solution must support search for mails based on undisclosed recipients criteria 6. The solution should support distribution list expansion while archiving s to ensure that user names are captured instead of just list names. 7. The solution should support manually initiated archival of mails from MS Outlook as well as Outlook Web Access. 8. The solution should support archiving based on either any or a combination of the Item Type (message, calendar etc.), Date, Size, Attachment only and User. 9. The solution should also support creation of "filter-rules" to configure more sophisticated archiving policies 10. The solution should not be dependent on journaling for archiving mails from identified user mailboxes. The two solu should work independent of one another. 11. Customized access to archiving features at the client end (Outlook / OWA) based upon organiza policy. 19

20 SN Items & its Qty Meet 12. The solution should be able to selectively mark old archived data as "read-only". E.g.. Quarterly archived data should me marked as read-only. 13. The solution shall facilitate migra of outlook PSTs to archive with an automated mechanism of discovering the PSTs associated with an Outlook profile and migrating the contents to archives. 14. Migration of PSTs to archives should facilitate keeping the folder structure of the shortcuts same as that of PSTs. 15. The solution should do Single- Instance of same messages on its own without the need of any 3rd party software/storage feature 16. The solution must allow users / administrators to access their respective archived content from a web based interface 17. The solution should provide a client side plug-in. 18. The solution should support creation of shortcuts for every item which is archived. 19. The solution must support removal / deletion of shortcut from the mailbox based upon expiration / deletion of the mail. 20. The solution should allow an administrator to choose to create a shortcut at either the time of archiving or later as well. 21. The solution should allow administrators to push out folders to users that have defined Retention Categories (e.g., a folder that shows up in Outlook called "Financial Filings") under which users can drag / drop relevant mails. 20

21 SN Items & its Qty Meet 22. The solution should support increasing the retention period of archived items. 23. The solution should allow archival of messages in the native format. 24. The solution should allow users to view their archived s irrespective of the underlying client version (Outlook 2000 / 2003 / XP / 2007 etc.) 25. The solution should provide Single Instancing of items irrespective of the underlying storage hardware or any third party technology 26. The solution should support tiered storage concept. Archived items can be moved from one set of disks to another based upon criteria specified by the administrator. This should also be seamlessly accessible by the user for search / retrieval. 27. The solution should support compression of messages as well as attachments with an overall compression ratio of 50 to 60% 28. The solution should have the capability to archive messages from multiple vers of exchange into the same repository. 29. The solution should support full indexing of messages based on metadata, message bode, attachment, and should allow users to search using keywords and phrases. 30. The solution should be capable of indexing around 70+ different file types. 31. The solution should facilitate retrieval of archived item in case the primary application, Exchange 2007 is no longer available 21

22 SN Items & its Qty Meet 32. The solution should provide out of the box reporting and also provide integration with third party reporting tools. E.g. Crystal reports. 33. The solution should provide application logs on its system status and opera. Some examples of these events are: Status of services/tasks (stop/start), Archive task (when archiving of mailboxes start), Failures (retrieval, expand distribution list, etc), Conflicts (Permission, storage device unavailable, etc) 34. The solution should provide a web based operation manager to allow administrators to keep track of events and activities. 35. The solution should provide an inbuilt mechanism to prevent users from tampering with the archive or items in the archive and should not be dependent on any kind of Hardware or Storage for the same. 36. The solution should enable users to access the archived items to which they have permiss, and prevent them from accessing anything else. 37. The solution should support users that have shared mailboxes. 38. The solution should be clusteraware and should be clusterable using clustering solu on windows 39. The solution should also facilitate a cold standby on which the archiving services can be quickly failed over. Note: Bidder can provide S/w Licenses in Electronic/Paper form. C.3 Windows Svr Ent 2008 Sngl OLP D 4 22

23 SN Items & its Qty Meet Note: Bidder can provide S/w Licenses in Electronic/Paper form. C.4 SQL Svr Enterprise Edtn Win32 Sngl 2 Lic/SA Pack OLP D Note: Bidder can provide S/w Licenses in Electronic/Paper form. C.5 SQL Svr Enterprise Edtn Win32 Sngl Lic/SA Pack OLP D 1 Proc Lic Note: Bidder can provide S/w Licenses in Electronic/Paper form. C.6 Archival Server 2 2 Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 16 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically and blindmate with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front 23

24 SN Items & its Qty Meet panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. C.7 Index Database Server for Archival Server 2 Processor Min. 2 * Quad Core Intel Xeon (2.4 GHz, 1066 FSB) or above Chipset Intel 5000P / 7300 Chipset Cache Min. 2 X 6 MB L2 Cache Memory Min. 16 GB DDR2 with ECC expandable up to 32 GB (Fully buffered DIMM at 667/800 MHz). Min. 8 Full buffered DIMM Slots Network Controller Min. 2 No.s 10/100/1000 Gigabit NIC configurable as Teamed NIC for network load-balancing. IO Expansion Slots Min. Two I/O expansion slots HDD Min. 2*146 GB 10K RPM SAS Hot Swappable disk drives or Min. 2*146 GB Internal SSD (Solid State Drives). Hardware Raid Controller Integrated Hardware Raid Controller (Capable of doing RAID 0, 1) Form Factor Blades Form Factor/Should plug vertically 24

25 SN Items & its Qty Meet and blindmate with the Blade enclosure backplane for both data and power transmission Ports Min. Two USB 2.0 bootable ports on front panel for floppy, CD/DVD, memory key, keyboard/mouse either on board or via dongle cable (To be provided by the bidder) Management Tools/Utilities OEM Management software tools with virtual KVM and graphical remote console. OS Support Windows 2003/2008 Note: All the necessary cables ethernet/fibre/usb/power (Indian Style) etc. required for making the system operational shall be provided by the bidder. D SAN D.1 SAN Storage Primary Min. 2TB usable (Upgradable up to Min. 5 TB) capacity using FC/SAS Disks with RAID-10 or better like RAID 4/6+Mirroring and Min. 2 no s of Hot Spares FC/SAS Disks Min. 2.5TB usable (Upgradable up to Min. 10 TB) capacity using SATA Disks with RAID-10 or better like RAID 4/6+Mirroring and 2 no s of Hot Spare SATA Disks SAN Controller The Proposed SAN Array should be configured with Dual Controllers for redundancy and NSPOF. Minimum 4 x 4- Gbps FC Front End Host / FC Switch Ports. Support for minimum 4 x 1-Gbps iscsi Front End Host / LAN Switch Ports across Dual controllers. SAN Controller Cache The Proposed SAN Array should be configured with minimum 4-GB cache across dual controllers with dual cache mirror interconnect paths. In case of power failure, the SAN array must be provided with cache protection 25

26 SN Items & its Qty Meet mechanism to ensure no loss of data in cache for minimum 72 hrs. SAN Scalability Support The Proposed SAN Array should be able to support minimum of 90 Drives in the array supplied from Day One and should be expandable in future. Maximum Expansion to be specified in the Remarks Section. In addition the array should support 8-Gbps FC Front End Host / FC Switch Ports without any Forklift Upgrade or any change in SAN Controllers. SAN Array Capacity The Proposed SAN Array should be configured with Min. 2TB usable (Upgradable up to Min. 5 TB) capacity using FC/SAS Disks with RAID-10 or better like RAID 4/6+ Mirroring and Min. 2 no s of Hot Spares FC/SAS Disks For Exchange Min. 2.5TB usable (Upgradable up to Min. 10 TB) capacity using SATA Disks with RAID-10 or better like RAID 4/6+ Mirroring and 2 no s of Hot Spare SATA Disks For Archival SAN Management Software The SAN Management software should be array based and provide GUI / web based management with Audit Logging and complete Reporting features like LUN Usage, Empty Space etc. Alternately the SAN management console should be offered in high availability mode so as to ensure that failure of the console does not impact the ability to manage the SAN storage array. Software/Utilities for enabling Multipathing etc. between Servers, SAN Switch and Storage shall be provided along with the SAN Storage. SAN Connectivity and SAN Switch The Proposed SAN Array should be able to connect to minimum 16 hosts on Fiber Channel through 4 Gbps FC Switches with requisite 10 Mtr. LC-LC Cables & Accessories (required in pair). 26

27 SN Items & its Qty Meet RAID Groups The Proposed SAN Array should support industry standard RAID Levels like 0, 1, 1/0, and 5 or higher. SAN Based Local Snapshot / Full Copy Clone Functionality The Proposed SAN Array should support pointer based snapshot copies as well as full physical copies of Production LUNs. SAN Based Remote Replication Functionality The Proposed SAN Array should support Array Based Data Replication in both Synchronous & Asynchronous modes with consistent copy of replicated volumes at target site. The replication capability should be bidirectional with ability to fail back. OS Support Support for Windows 2000/2003, HP-UX, IBM AIX, LINUX, Solaris OS Redundancy There should not be any single point of failure in the system. All the hardware components provided should be redundant for high availability. Remote Diagnostics The Proposed SAN Array should support Web based, facility for remote service & also support dial-in / dial-out to report errors and warnings Rack Mount The Proposed SAN Array must be rack mounted (19 President Rack Space shall be provided by GAIL). OEM Rack mounting kit to be provided. Note All the required cables/equipments necessary for making the system operational shall be provided by the bidder. D.2 Fibre Channel Switch Min. 8 ports 2 Min. 8 x 4 Gbps FC Ports Active Per Switch with expansion possibility of 8 Additional Ports of 4 Gbps FC 27

28 SN Items & its Qty Meet All Ports Should be autosensing 1, 2, 4 and 8 Gbit/sec (in future) Fibre Channel Native E_Port switch Interoperability Should support Media types like Small Form-factor Pluggable (SFP) laser, Shortwave up to 500 meters (1640 feet) and Long-wave up to 10 kilometers (6.2 miles) Note All the required cables/equipments necessary for making the system operational shall be provided by the bidder. D.3 SAN Storage Primary Min. 2TB usable (Upgradable up to Min. 5 TB) capacity using FC/SAS Disks with RAID-10 or better like RAID 4/6+Mirroring and Min. 2 no s of Hot Spares FC/SAS Disks Min. 2.5TB usable (Upgradable up to Min. 10 TB) capacity using SATA Disks with RAID-10 or better like RAID 4/6+Mirroring and 2 no s of Hot Spare SATA Disks SAN Controller The Proposed SAN Array should be configured with Dual Controllers for redundancy and NSPOF. Minimum 4 x 4- Gbps FC Front End Host / FC Switch Ports. Support for minimum 4 x 1-Gbps iscsi Front End Host / LAN Switch Ports across Dual controllers. SAN Controller Cache The Proposed SAN Array should be configured with minimum 4-GB cache across dual controllers with dual cache mirror interconnect paths. In case of power failure, the SAN array must be provided with cache protection mechanism to ensure no loss of data in cache for minimum 72 hrs. SAN Scalability Support The Proposed SAN Array should be able to support minimum of 90 Drives in the array supplied from Day One and should 28

29 SN Items & its Qty Meet be expandable in future. Maximum Expansion to be specified in the Remarks Section. In addition the array should support 8-Gbps FC Front End Host / FC Switch Ports without any Forklift Upgrade or any change in SAN Controllers. SAN Array Capacity The Proposed SAN Array should be configured with Min. 2TB usable (Upgradable up to Min. 5 TB) capacity using FC/SAS Disks with RAID-10 or better like RAID 4/6+ Mirroring and Min. 2 no s of Hot Spares FC/SAS Disks For Exchange Min. 2.5TB usable (Upgradable up to Min. 10 TB) capacity using SATA Disks with RAID-10 or better like RAID 4/6+ Mirroring and 2 no s of Hot Spare SATA Disks For Archival SAN Management Software The SAN Management software should be array based and provide GUI / web based management with Audit Logging and complete Reporting features like LUN Usage, Empty Space etc. Alternately the SAN management console should be offered in high availability mode so as to ensure that failure of the console does not impact the ability to manage the SAN storage array. Software/Utilities for enabling Multipathing etc. between Servers, SAN Switch and Storage shall be provided along with the SAN Storage. SAN Connectivity and SAN Switch The Proposed SAN Array should be able to connect to minimum 16 hosts on Fiber Channel through 4 Gbps FC Switches with requisite 10 Mtr. LC-LC Cables & Accessories (required in pair). RAID Groups The Proposed SAN Array should support industry standard RAID Levels like 0, 1, 1/0, and 5 or higher. SAN Based Local Snapshot / Full Copy Clone Functionality 29

30 SN Items & its Qty Meet The Proposed SAN Array should support pointer based snapshot copies as well as full physical copies of Production LUNs. SAN Based Remote Replication Functionality The Proposed SAN Array should support Array Based Data Replication in both Synchronous & Asynchronous modes with consistent copy of replicated volumes at target site. The replication capability should be bidirectional with ability to fail back. OS Support Support for Windows 2000/2003, HP-UX, IBM AIX, LINUX, Solaris OS Redundancy There should not be any single point of failure in the system. All the hardware components provided should be redundant for high availability. Remote Diagnostics The Proposed SAN Array should support Web based, facility for remote service & also support dial-in / dial-out to report errors and warnings Rack Mount The Proposed SAN Array must be rack mounted (19 President Rack Space shall be provided by GAIL). OEM Rack mounting kit to be provided. Note All the required cables/equipments necessary for making the system operational shall be provided by the bidder. D.4 Fibre Channel Switch Min. 8 ports 2 Min. 8 x 4 Gbps FC Ports Active Per Switch with expansion possibility of 8 Additional Ports of 4 Gbps FC All Ports Should be autosensing 1, 2, 4 and 8 Gbit/sec (in future) Fibre Channel Native E_Port switch Interoperability 30

31 SN Items & its Qty Meet Should support Media types like Small Form-factor Pluggable (SFP) laser, Shortwave up to 500 meters (1640 feet) and Long-wave up to 10 kilometers (6.2 miles) Note All the required cables/equipments necessary for making the system operational shall be provided by the bidder. D.5 SAN Storage - DR 1 Min. 2TB usable (Upgradable up to Min. 5 TB) capacity using FC/SAS Disks with RAID-10 or better like RAID 4/6+Mirroring and Min. 2 no s of Hot Spares FC/SAS Disks Min. 2.5TB usable (Upgradable up to Min. 10 TB) capacity using SATA Disks with RAID-10 or better like RAID 4/6+Mirroring and 2 no s of Hot Spare SATA Disks SAN Controller The Proposed SAN Array should be configured with Dual Controllers for redundancy and NSPOF. Minimum 4 x 4- Gbps FC Front End Host / FC Switch Ports. Support for minimum 4 x 1-Gbps iscsi Front End Host / LAN Switch Ports across Dual controllers. SAN Controller Cache The Proposed SAN Array should be configured with minimum 4-GB cache across dual controllers with dual cache mirror interconnect paths. In case of power failure, the SAN array must be provided with cache protection mechanism to ensure no loss of data in cache for minimum 72 hrs. SAN Scalability Support The Proposed SAN Array should be able to support minimum of 90 Drives in the array supplied from Day One and should be expandable in future. Maximum Expansion to be specified in the Remarks Section. In addition the array should support 8-Gbps FC Front End Host / FC Switch Ports without any Forklift Upgrade or any change in SAN Controllers. 31

32 SN Items & its Qty Meet SAN Array Capacity The Proposed SAN Array should be configured with Min. 2TB usable (Upgradable up to Min. 5 TB) capacity using FC/SAS Disks with RAID-10 or better like RAID 4/6+ Mirroring and Min. 2 no s of Hot Spares FC/SAS Disks For Exchange Min. 2.5TB usable (Upgradable up to Min. 10 TB) capacity using SATA Disks with RAID-10 or better like RAID 4/6+ Mirroring and 2 no s of Hot Spare SATA Disks For Archival SAN Management Software The SAN Management software should be array based and provide GUI / web based management with Audit Logging and complete Reporting features like LUN Usage, Empty Space etc. Alternately the SAN management console should be offered in high availability mode so as to ensure that failure of the console does not impact the ability to manage the SAN storage array. Software/Utilities for enabling Multipathing etc. between Servers, SAN Switch and Storage shall be provided along with the SAN Storage. SAN Connectivity and SAN Switch The Proposed SAN Array should be able to connect to minimum 16 hosts on Fiber Channel through 4 Gbps FC Switches with requisite 10 Mtr. LC-LC Cables & Accessories (required in pair). RAID Groups The Proposed SAN Array should support industry standard RAID Levels like 0, 1, 1/0, and 5 or higher. SAN Based Local Snapshot / Full Copy Clone Functionality The Proposed SAN Array should support pointer based snapshot copies as well as full physical copies of Production LUNs. SAN Based Remote Replication Functionality The Proposed SAN Array should support 32

33 SN Items & its Qty Meet Array Based Data Replication in both Synchronous & Asynchronous modes with consistent copy of replicated volumes at target site. The replication capability should be bidirectional with ability to fail back. OS Support Support for Windows 2000/2003, HP-UX, IBM AIX, LINUX, Solaris OS Redundancy There should not be any single point of failure in the system. All the hardware components provided should be redundant for high availability. Remote Diagnostics The Proposed SAN Array should support Web based, facility for remote service & also support dial-in / dial-out to report errors and warnings Rack Mount The Proposed SAN Array must be rack mounted (19 President Rack Space shall be provided by GAIL). OEM Rack mounting kit to be provided. Note All the required cables/equipments necessary for making the system operational shall be provided by the bidder. D.6 Fibre Channel Switch Min. 8 ports 2 Min. 8 x 4 Gbps FC Ports Active Per Switch with expansion possibility of 8 Additional Ports of 4 Gbps FC All Ports Should be autosensing 1, 2, 4 and 8 Gbit/sec (in future) Fibre Channel Native E_Port switch Interoperability Should support Media types like Small Form-factor Pluggable (SFP) laser, Shortwave up to 500 meters (1640 feet) and Long-wave up to 10 kilometers (6.2 miles) Note All the required cables/equipments 33

34 SN Items & its Qty Meet necessary for making the system operational shall be provided by the bidder. D.7 WORM Storage for Archival for Compliance [Min 2.5 TB usable (upgradable up to Min. 15 TB) with RAID10 OR better like RAID 4/6+ Mirroring OR Content Mirroring under RAIN with Hot spare capacity] 1 WORM 1. The system should warn when the archive fills to a high water mark, and let additional capacity be added seamlessly. 2. The system should support Write Once Read Many (WORM) capabilities. 3. The system should support any stored object placed in the Archive in such a way that its content is immutable and upon retrieval, verified that the content is exactly the same as when it was stored. Absolutely no possibility of modification or forgery. This authentication should be used within the archive as well as by any application that retrieves the object OR There should be a mechanism to verify the archive by mounting the data on a different system with required software. 4. The system should support continuous archive verification by the state of an object. Media should be scrubbed to validate its ability to hold the information without change or errors. In the event there is an error, the data should be automatically reconstructed from its mirror copy (in the archive) and the bad media should be fenced off and eventually replaced. There should be no surprises due to worn out or aged media. The archive must 34

35 SN Items & its Qty Meet automatically protect the objects to insure reliable retrieval at any time during the objects retention period. There should also be a provision to ensure a hold on deletion for expired objects in case of litigation, without the need to artificially change the system clock or the retention settings OR In case of a hardware failure e.g. disk, controller or fan, there should be a provision to replace only the affected component without impacting other parts in a system. 5. The archive should allow retrieval of a piece of an object. For example, an object may be the collected songs of a musical artist or a month check images for a checking account. The archive should allow a single song or check image to be retrieved. The entire collection of songs or check images should not have to be retrieved 6. The archive should allow the object to be stored exactly as it was presented to the archive. It should also allow for additional meta data to be saved with the archive. The meta data should carry some standard information, such as the date and time that the object was stored; the retention period for keeping the object; the object size; etc. The archive should also all meta data provided by the storing application to be associated and stored with the object. The meta data format should be flexible using a protocol such as XML to define its structure and content OR It should use an inbuilt system clock along with the specified retention period of the data to set the life of the data. 7. The nature of a long term archive requires that fixed content must 35

36 SN Items & its Qty Meet be stored for years, decades and even a century. This leads to large amounts of information being accumulated. The archive should be able to meet the scalability requirements without impacting the existing data. 8. Adding more capacity to the archive should occur without impact to the application processes that are storing and retrieving objects in the archive. The archive should always be available with the expansion process occurring non-disruptively. There should be no outages required to expand. There should be no need to reconfigure the existing archive. There should be no file systems to rebuild or resize. There should be no mount points to manage. There should just be more capacity. OR There should be a flexibility to add the minimum capacity to the WORM device which could even be a single disk at a minimum. 9. All information in the archive should be accessible on-line. There should be no off-line component requiring human intervention (such as inserting a tape of optical platter into a library or drive). 10. The archive should be capable of providing Internet Response Time for any retrieval. The time to first byte of data retrieve should be within a few seconds or less than a second, for any and ALL object retrievals. There should be no delay to the object being unavailable in the archive. The archive should scale in performance as it scales in size, to insure that second to sub-second response can be maintained. The application should not have to wait minutes, hours or even days for retrieval of an object. 36

37 SN Items & its Qty Meet 11. The archive should protect itself and the content in the array. There should be no risk of data loss due to hardware failure or power loss. It should be able to withstand component failure, while protecting the objects. In the event a redundant copy of an object is compromised by a component failure, a new copy of the object should be automatically be generated from the good copy, to insure continued protection of the object. The failed component or media should be fenced off, preventing use of that component / media, until the physical repairs have been made. The archive should still function with minimal or no degradation in performance while awaiting repairs of the hardware. 12. The archive should have the capability to enforce retention periods. When a retention period is set, the data cannot be deleted prior to expiration of that retention period. There should be enforceable in the same manner as Write Once Read Many (WORM optical) technology provides. There should be an enforceable mode where retention periods cannot be shortened or removed. Retention periods can be lengthened in enforced mode, not reduced nor eliminated. 13. The archive should protect the data stored in it, with regard to retention periods. However upon expiration of the retention period, the archive should allow the application to delete and destroy the object. The space used by the object should be reclaimed, for use in storing new objects. 14. The array should recognize instances of the same object and only store that object once. This can result in a significant reduction in the amount of space required to 37

38 SN Items & its Qty Meet archive information. For example, if electronic mail messages are being journaled or archived, the archive should recognize the same attachment being stored by several users (the same spreadsheet or document attached to the same , received by multiple recipients). There should be reference pointers to the single instance of the object, allowing each reference point to be treated as if it were the only instance of the object. The referenced object would have its own meta data associated and even its own retention period. The actual object would not be deleted until all references to the object are deleted. References to an object can only be deleted by the application storing the object and after the retention period for that reference has expired. OR The device should support Single Instance Archival Software. 15. The archive should be easy to install and upgrade. Capacity should be added in a manner that the archive self discovers the new capacity and makes it available to all applica interfacing with the archive. There should be no need for a highly trained engineer to manage the archive. It should be viewed as an appliance, with initial installation occurring in a half day or less. 16. The archive should allow for the introduction of new technology in a non-disruptive, transparent manner. The applica using the archive should not know about the technology used in the archive. They should just see it as having capacity with the functionality store, protect and retrieve objects. The array should allow inclusion of new technology, mixed with the older existing technology. It should not require any service outage to the applica that 38