Public Works and Government Services Canada
Symbol of the Government of Canada

Common menu bar links

Annex A1: Technical Specifications-Tier 3 (Archival, backup and near line) storage products

1.0 Categories: Standalone Tape Backup 2.0 Categories: Tape Autoloaders 3.0 Categories: Tape Libraries 4.0 Categories: Tape Media 5.0 Categories: Disk-based Storage

APPENDIX A: DETAILED SPECIFICATIONS

General


Specified capacities reflect the current generation of tape technologies at the time of RFSO release.  Occasionally the previous generation of drives (eg.  LTO3) may be required in order to maintain backward-compatibility with existing media.


1.0 Categories:Standalone Tape Backup

1.1 Tabletop model

The following describes a standalone tabletop tape backup device.


1.1.1  General

The tape backup device must include:

  1. a single tape drive within a tabletop enclosure;
  2. a power on/off switch;
  3. lights for power and activity;
  4. a method for setting the SCSI ID of the tape drive;
  5. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape backup device; and
  6. end user documentation along with one cleaning cartridge. 

1.1.2  Capacity and Performance

The tape backup device must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the device and on all accompanying documentation and certification reports.


1.1.3  Connectivity

The tape backup device must include one industry standard FC or high speed serial connection.


1.1.4  Power

The tape backup device must include power sufficient to operate the device. 


1.1.5 Software and Support

a)  The tape backup device must be directly supported by three of the following backup software packages: 

  1. Symantec NetBackup or Backup Exec;
  2. Tivoli TSM;
  3. EMC Legato Networker;
  4. Computer Associates BrightStor;
  5. HP Data Protector; and
  6. CommVault Simpana. 

b)  “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.

Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

1.2 Rackmount model

The following describes a 19” rackmount tape backup device.


1.2.1  General

The tape backup device must include:

  1. a single tape drive within an industry standard 19” rackmount enclosure;
  2. the enclosure must provide accommodation for a second optional tape drive of identical specification;
  3. a power on/off switch;
  4. lights for power and activity;
  5. a method for setting the SCSI ID of the tape drive;
  6. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape backup device; and
  7. end user documentation along with one cleaning cartridge.

1.2.2  Capacity and Performance

The tape backup device must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the device and on all accompanying documentation and certification reports.


1.2.3  Connectivity

 The tape backup device must include one industry standard FC or high speed serial connection.


1.2.4  Power

The tape backup device must include power sufficient to operate the device. 


1.2.5 Software and Support

  1. The tape backup device must be directly supported by three of the following backup software packages: 
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana.
  2.   “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

2.0 Categories: Tape Autoloaders

2.1 Small Tape Autoloader

The following describes a small tape autoloader.

2.1.1  General

The small tape autoloader must include:

  • i) a single tape drive;
  • ii) a minimum of eight (8) media slots;
  • iii) a power on/off switch;
  • iv) power and activity lights;
  • v) a method for setting the SCSI ID; 
  • vi) power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape autoloader; and
  • vii) end user documentation along with one cleaning cartridge.

2.1.2  Capacity and Performance

The small tape autoloader must include an industry standard LTO4 tape drive that provides:

  • i) a native capacity of no less than 800GB before compression;
  • ii) a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  • iii) a sustained transfer rate of no less than 432GB/hour; and
  • iv) a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the autoloader and on all accompanying documentation and certification reports.


2.1.3  Connectivity

 The tape backup device must include one industry standard FC or high speed serial connection.


2.1.4  Power

The small tape autoloader must include power sufficient to operate a fully populated system. 


2.1.5  Software and Support

  1. The small tape autoloader must be directly supported by three of the following backup software packages:
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana. 
  2. “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

2.2 Tape Autoloader

The following describes a tape autoloader with barcode reader.


2.2.1  General

The tape autoloader must include:

  1. a single tape drive;
  2. a minimum of fifteen (15) media slots;
  3. at least one (1) assignable load port or “mail slot”;
  4. a barcode reader;
  5. a power on/off switch;
  6. power and activity lights;
  7. a method for setting the SCSI ID;
  8. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape autoloader; and
  9. end user documentation along with one cleaning cartridge. 

2.2.2  Capacity and Performance

The tape autoloader must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the autoloader and on all accompanying documentation and certification reports.


2.2.3  Connectivity

 The tape backup device must include one industry standard FC or high speed serial connection.


2.2.4  Power

The tape autoloader must include power sufficient to operate a fully populated system. 


2.2.5  Software and Support

  1. The tape autoloader must be directly supported by three of the following backup software packages:
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana. 
  2. “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

2.2.6  Management

The tape autoloader must include:

  1. a local LCD management panel;
  2. web-based management capabilities;
  3. one ethernet port; and
  4. built in diagnostic capabilities.

3.0 Categories: Tape Libraries

3.1 Small Tape Library

The following describes a Small Tape Library.


3.1.1 General

The small tape library must include:

  1. a single tape drive with the capability to add a second tape drive;
  2. a minimum of twenty-one (21) media slots;
  3. at least one (1) assignable load port or “mail slot”;
  4. a barcode reader;
  5. a power on/off switch, power and activity lights;
  6. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape library;
  7. end user documentation must be provided along with one cleaning cartridge for each tape drive supplied.

3.1.2 Capacity and Performance

The small tape library must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the library and on all accompanying documentation and certification reports.


3.1.3 Connectivity

 The tape backup device must include one industry standard FC or high speed serial connection at minimum per tape drive installed into the system.


3.1.4 Power

The small tape library must include power sufficient to operate a fully populated system.


3.1.5 Software and Support

  1. The small tape library must be directly supported by three of the following backup software packages: 
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana. 
  2. “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

3.1.6 Library Management

The small tape library must include:

  1. a local LCD management panel;
  2. web-based management capabilities;
  3. one ethernet port; and
  4. built in diagnostic capabilities.

3.1.7 Library Expansion

  1. The small tape library must be capable of expansion.  Stackable modular units are acceptable in this Category. 
  2. In the event that multiple tape drive formats are supported within the small tape library, a price reduction option to reduce the number of tape drives, in increments of one, to zero tape drives and equal to the price of purchasing new drives must be included.

3.1.8    Robotics

The small tape library must include a robotic system for the handling of media that is addressable and controllable by the SCSI command set.


3.2 Medium Tape Library

The following describes a medium tape library.


3.2.1 General

The medium tape library must include:

  1. a single tape drive with the capability to accommodate an additional three (3) tape drives for a total of four (4);
  2. forty-two (42) media slots;
  3. at least two (2) assignable load ports or “mail slots”;
  4. a barcode reader;
  5. a power on/off switch;
  6. power and activity lights;
  7. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape library; and
  8. end user documentation must be provided along with one cleaning cartridge for each tape drive supplied.

3.2.2 Capacity and Performance

The medium tape library must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the library and on all accompanying documentation and certification reports.


3.2.3 Connectivity

The tape backup device must include two industry standard FC or high speed serial connections.


3.2.4 Power

  1. The medium tape library must include power sufficient to operate a fully populated system.
  2. This power must be fully redundant, allowing uninterrupted operation of the library  in the event of a power supply failure, until service can be performed.

3.2.5 Software and Support

  1. The medium tape library must be directly supported by three of the following backup software packages: 
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana. 
  2.   “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

3.2.6 Library Management

The medium tape library must include:

  1. a local LCD management panel;
  2. web-based management capabilities;
  3. one ethernet port; and
  4. built in diagnostic capabilities.

3.2.7 Library Expansion

  1. The medium tape library must be capable of expansion.  Stackable modular units are acceptable in this Category. 
  2. In the event that multiple tape drive formats are supported within the medium tape library, a price reduction option to reduce the number of tape drives, in increments of one, to zero tape drives and equal to the price of purchasing new drives must be included.

3.2.8 Robotics

The medium tape library must include a robotic system for the handling of media that is addressable and controllable by the SCSI command set. 


3.3 Large Tape Library

The following describes a large tape library.


3.3.1 General

The large tape library must include:

  1. a single tape drive with the capability to accommodate an additional five (5) tape drives for a total of six (6);
  2. eighty-four (84) media slots;
  3. at least four (4) assignable load ports or “mail slots”;
  4. a barcode reader;
  5. a power on/off switch;
  6. power and activity lights;
  7. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape library;
  8. end user documentation must be provided along with one cleaning cartridge for each tape drive supplied.

3.3.2 Capacity and Performance

The large tape library must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the library and on all accompanying documentation and certification reports.


3.3.3 Connectivity

The tape backup device must include two industry standard FC or high speed serial connections.


3.3.4 Power

  1. The large tape library must include sufficient power to operate a fully populated system.
  2. This power must be fully redundant, allowing uninterrupted operation of the tape library in the event of a power supply failure, until service can be performed.
  3. The large tape library must utilize fully redundant AC power inputs from multiple discrete AC power sources.

3.3.5 Software and Support

  1. The large tape library must be directly supported by three of the following backup software packages: 
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana. 
  2.   “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

3.3.6 Library Management

The large tape library must include:

  1. a local LCD management panel;
  2. web-based management capabilities;
  3. one ethernet port; and
  4. built in diagnostic capabilities.

3.3.7 Library Expansion

The large tape library must be capable of expansion.  Stackable modular units are acceptable in this Category. 

In the event that multiple tape drive formats are supported within the library, a price reduction option to reduce the number of tape drives, in increments of one, to zero tape drives and equal to the price of purchasing new drives must be included.

3.3.8    Robotics

The large tape library must include a robotic system for the handling of media that is addressable and controllable by the SCSI command set.


3.4 Small Enterprise Tape Library

The following describes an entry-level enterprise tape library.


3.4.1 General

The entry-level enterprise tape library must include:

  1. a single tape drive with the capability to accommodate an additional seven (7) tape drives, for a total of eight (8);
  2. all tape drives must be hot-swappable; 
  3. one hundred and sixty eight media slots;
  4. at least four (4) assignable load ports or “mail slots”;
  5. a barcode reader;
  6. a power on/off switch;
  7. power and activity lights;
  8. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape library;
  9. end user documentation must be provided along with one cleaning cartridge for each tape drive supplied.

3.4.2 Capacity and Performance

The entry-level enterprise tape library must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the library and on all accompanying documentation and certification reports.


3.4.3 Connectivity

The tape back-up device must either i). provide direct fibre channel connectivity, or ii). include a fibre channel router for connectivity.


3.4.4 Power

  1. The entry-level enterprise tape library must include sufficient power to operate a fully populated system.
  2. This power must be fully redundant, allowing uninterrupted operation of the tape library in the event of a power supply failure, until service can be performed.
  3. The tape library must utilize fully redundant AC power inputs from multiple discrete AC power sources.

3.4.5 Software and Support

  1. The entry-level enterprise tape library must be directly supported by three of the following backup software packages: 
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana. 
  2. “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

3.4.6 Library Management

The entry-level enterprise tape library must include:

  1. a local LCD management panel;
  2. web-based management capabilities;
  3. one ethernet port;
  4. built in component-level diagnostic capabilities
  5. SNMP capabilities

3.4.7 Library Expansion

The tape library must be capable of frame expansion.  Stackable modular units are not acceptable in this Category and will be deemed non-compliant with this requirement. 

In the event that multiple tape drive formats are supported within the library, a price reduction option to reduce the number of tape drives, in increments of one, to zero tape drives and equal to the price of purchasing new drives must be included.


3.4.8    Robotics

The tape library must include a robotic system for the handling of media that is addressable and controllable by the SCSI command set.


3.5 Enterprise Tape Library

The following describes an enterprise tape library in a data center enclosure.


3.5.1 General

The enterprise tape library must include:

  1. a single tape drive with the capability to accommodate an additional fifteen (15) tape drives, for a total of sixteen (16);
  2. ll tape drives must be hot-swappable;
  3. one hundred and sixty eight (168) media slots, with the capability to expand to six hundred and forty eight (648);
  4. at least eight (8) assignable load ports or “mail slots”;
  5. a barcode reader;
  6. a power on/off switch;
  7. power and activity lights;
  8. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape library;
  9. end user documentation must be provided along with one cleaning cartridge for each tape drive supplied.

3.5.2 Capacity and Performance

The enterprise tape library must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the library and on all accompanying documentation and certification reports.


3.5.3 Connectivity

The tape backup device must either i). provide direct fibre channel SAN fabric connectivity or ii). include an internal fibre channel router for direct SAN fabric connectivity. 


3.5.4 Power

  1. The enterprise tape library must include sufficient power to operate a fully populated system.
  2. This power must be fully redundant, allowing uninterrupted operation of the tape library in the event of a power supply failure, until service can be performed.
  3. The enterprise tape library must utilize fully redundant AC power inputs from multiple discrete AC power sources.

3.5.5 Software and Support

  1. The enterprise tape library must be directly supported by three of the following backup software packages:
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana. 
  2. “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
  3. The bidder must provide a list of backup software that is compatible with the enterprise tape library, including a list of the supported Operating Systems.

3.5.6 Library Management

The enterprise tape library must include:

  1. a local LCD management panel;
  2. web-based management capabilities;
  3. one ethernet port;
  4. built in component-level diagnostic capabilities
  5. SNMP alerting capabilities

3.5.7 Library Expansion

The enterprise tape library must be capable of frame expansion.  Stackable modular units will not be accepted in this Category and will be deemed non-compliant with this requirement. 

In the event that multiple tape drive formats are supported within the library, a price reduction option to reduce the number of tape drives, in increments of one, to zero tape drives and equal to the price of purchasing new drives must be included.


3.5.8    Robotics

The tape library must include a robotic system for the handling of media that is addressable and controllable by the SCSI command set.  The robotic system must provide redundancy such that, in the event of a failure, the library will continue operation with access to all media until such time as service is performed.


3.6 Large Enterprise Tape Library

The following describes a large enterprise tape library in a data center enclosure.


3.6.1 General

The large enterprise tape library must include:

  1. a single tape drive with the capability to accommodate an additional twenty-three (23) tape drives, for a total of twenty-four (24);
  2. all tape drives must be hot-swappable;
  3. one thousand four hundred and forty eight (1448) media slots, with the capability to expand to three thousand four hundred and ninety two (3492) or more;
  4. at least sixteen (16) assignable load ports or “mail slots”;
  5. a barcode reader;
  6. a power on/off switch;
  7. power and activity lights;
  8. power and data cables, terminators (if required) and any other ancillary items required for the operation of the tape library;
  9. end user documentation must be provided along with one cleaning cartridge for each tape drive supplied.

3.6.2 Capacity and Performance

The large enterprise tape library must include an industry standard LTO4 tape drive that provides:

  1. a native capacity of no less than 800GB before compression;
  2. a native transfer rate of no less than 120MB/s s for full-height drives and 80MB/s for half-height drives;
  3. a sustained transfer rate of no less than 432GB/hour; and
  4. a published MTBF specification of no less than 250,000 hours.

These minimum specifications must be achieved using current tape drive technologies and densities, which are tested and fully supported by the manufacturer, as defined by the name appearing on the library and on all accompanying documentation and certification reports.


3.6.3 Connectivity

 The tape backup device must either i). provide direct fibre channel SAN fabric connectivity or ii). include an internal fibre channel router for direct SAN fabric connectivity. 


3.6.4 Power

  1. The large enterprise tape library must include sufficient power to operate a fully populated system.
  2. This power must be fully redundant, allowing uninterrupted operation of the tape library in the event of a power supply failure, until service can be performed.
  3. The large enterprise tape library must utilize fully redundant AC power inputs from multiple discrete AC power sources.

3.6.5 Software and Support

  1. The large enterprise tape library must be directly supported by three of the following backup software packages: 
    1. Symantec NetBackup or Backup Exec;
    2. Tivoli TSM;
    3. EMC Legato Networker;
    4. Computer Associates BrightStor;
    5. HP Data Protector; and
    6. CommVault Simpana.
  2. “Directly supported” means that the tape backup device model must be listed as a supported product on the software publisher’s website or their published compatibility documentation.
Note to Offerors: To substantiate compliance with (a) and (b), the Offer must include a list of back-up software that is compatible with the proposed tape backup device, including a list of the Operating Systems with which the device is compatible. Also, with respect to (b), the Offeror must provide the url for the publisher’s website listing the tape back device model as a supported product, or must provide a copy of the software publisher’s compatibility documentation in its Offer.

3.6.6 Library Management

The large enterprise tape library must include:

  1. a local LCD management panel;
  2. web-based management capabilities;
  3. one ethernet port;
  4. built in component-level diagnostic capabilities
  5. SNMP alerting capabilities

3.6.7    Library Expansion

The enterprise tape library must be capable of frame expansion.  Stackable modular units will not be accepted in this Category and will be deemed non-compliant with this requirement. 

In the event that multiple tape drive formats are supported within the library, a price reduction option to reduce the number of tape drives, in increments of one, to zero tape drives and equal to the price of purchasing new drives must be included.


3.6.8 Robotics

The tape library must include a robotic system for the handling of media that is addressable and controllable by the SCSI command set.  The robotic system must provide redundancy such that, in the event of a failure, the library will continue operation with access to all media until such time as service is performed.


4.0 Categories: Blank Media

4.1 LTO4 Blank Media (blank tape)

Media for the libraries must be included in this Category.

All proposed media must be certified to have passed the LTO Ultrium format generation 4 data interchange compliance testing and must display the LTO Ultrium format generation 4 trademark on their LTO tape media products.


4.2 LTO3 Blank Media (blank tape)

Media for the libraries must be included in this Category.All proposed media must be certified to have passed the LTO Ultrium format generation 3 data interchange compliance testing and must display the LTO Ultrium format generation 3 trademark on their LTO tape media products.


4.3 SDLT600 Blank Media (blank tape)

Media for the libraries must be included in this Category.All proposed media must be certified to have passed the compliance testing and must display the SDLT trademark on the tape media products.  If requested, proof of certification must be provided.


4.4 LTO5 Blank Media (blank tape)

Media for the libraries must be included in this Category. 

All proposed media must be certified to have passed the LTO Ultrium format generation 5 data interchange compliance testing and must display the LTO Ultrium format generation 5 trademark on their LTO tape media products.


5.0 Categories: Disk-based Backup and Archiving

5.1 Small Disk-based Archival Storage

The following describes a small disk-based backup device. The device may be either a) block mode SAN; b) file mode NAS; or c) VTL with deduplication.

5.1.1 General

Each disk-based backup device must meet the following capacity and platform requirements:

  1. the hard disk drive technologies and densities must be commercially available, meaning that the Manufacturer is continuing to manufacture and ship them to customers generally;
  2. the hard disk drive technologies and densities must be tested and fully supported within the storage platform by the storage platform Manufacturer;
  3. it must include industry-standard Serial ATA (SATA) supporting 3Gb/s transfer rates, or serial attached SCSI (SAS) hard disk drives supporting 6Gb/s transfer rates, or low cost fibre channel (LCFC) hard disk drives supporting 4Gb/s transfer rates;
  4. the available drive options must include:
    1. 1TB areal drive densities at 7200RPM rotational speed;
    2.  b). 2TB areal drive densities at 7200RPM rotational speed and 1TB drives with 5400 RPM  rotational speed for energy efficient requirements may be offered as options, if available;
  5. it must accommodate a minimum of 12 hard disk drives;  
  6. it must offer a standard 19" rack mount form factor in addition to any default chassis style offered ; and
  7. it must include lights or an LCD panel for power, activity and fault indications; and
  8. it must include power cables and any other ancillary items required for the connection and operation of the disk-based backup as well as end user documentation.

5.1.2 Capacity and Performance

The unit must:

  1. include a minimum of twelve (12) industry standard Serial ATA (SATA), Serial Attached SCSI (SAS) or low-cost fibre channel (LCFC) hard disk drives with Redundant Array of Inexpensive Disks (RAID) enabled. units must provide a total storage capacity of no less than 12TB of storage capacity;
  2. include drives supplied with the storage platform that meet the following minimum requirements:
    1. SATA, SAS or fiber ATA;
    2. 16 MB onboard cache;
    3. 7200 RPM spin rates.
  3. include disk drives that are hot pluggable while the storage platform is operational and must utilize a canister system that allows easily inserting and removing the drives;
  4. include a built in hardware RAID controller that stripes data across all 12 disk drives and presents either; (a) logical drives, (b)file systems or (c) be virtualized to present standard tape drives, robotics and media slots to an attached host.
  5. include 128MB of write cache memory on the built in RAID controller to assist RAID operations.
  6. include a controller that  supports the following RAID types;
    1. RAID-4 or RAID-5 or RAID-6; and
    2. RAID-1 or RAID-1+0 or RAID-0+1
  7. For:
    • a) SAN units, allow configuration of 2 RAID sets comprised of any of the mandatory RAID types; or
    • b) NAS units,  RAID sets within the unit must not be visible to attached host systems as block devices, but rather must be presented as CIFS and NFS file systems; or
    • c) VTL, RAID sets within the unit must not be visible to attached host systems as block devices, but rather must be virtualized and presented as tape cartridges;
  8. for a) SAN or b) NAS units, allow the allocation of one hard disk drive as a global hot spare, which will automatically rebuild the contents of a failed hard disk drive in any fault tolerant RAID set. This process must be fully automatic upon detection of a disk failure in a fault tolerant RAID set.
  9. include hard drives that are fully hot pluggable while the storage platform is operational. There must be no loss of data or other impact to the storage platform in the event that a hard drive is removed, assuming the drive is part of a fault tolerant configuration in the platform.
  10. rebuild a replaced hard disk drive automatically when it is inserted, with no user intervention on the management console, assuming it is replacing a hard disk drive that was part of a fault tolerant configuration.
  11. include RAID functionality built in to the storage platform and must not require host based functionality for any RAID operations.

5.1.3 Connectivity

a) SAN units must utilize one of the following block mode interfaces for host connectivity:

  1. serial attached SCSI;
  2. 1Gb or 10Gb Ethernet with iSCSI or FCoE;
  3. 1 x 8Gb or 2 x 4Gb fibre channel

If the storage platform requires a proprietary host bus interface for proper operation it must be identified and included as part of the default configuration.

b) NAS units must include a micro-kernel operating system designed for providing file services to common internet file system (CIFS) and network file system (NFS) clients via included Ethernet interfaces. The micro-kernel operating system may be either a Windows (WSS), Linux or Unix-based operating system;

A minimum of 2x1Gb Ethernet interfaces must be provided.

c) VTL units must include fixed or variable block length deduplication at target and must be RAID protected.  At minimum RAID-5 must be supported.  RAID sets within the unit must not be visible to attached host systems as block devices, but rather be virtualized and presented as standard tape drives, robotics and media slots to connected hosts.   VTL units must utilize one of the following interfaces for host connectivity:

  1. 1Gb or 10Gb Ethernet with iSCSI;
  2. 1 x 8Gb or 2 x 4Gb fibre channel

If the storage platform requires a proprietary host bus interface for proper operation it must be identified and included as part of the default configuration.

NOTE: For both a) SAN and b) NAS units, the storage platform must support connectivity to standard Intel-based server platforms running Windows Server 2008.


5.1.4 Power and Cooling

The unit must provide the following power and cooling attributes:

  1. include power sufficient to operate a fully populated system;
  2. include redundant N+1 power and utilize hot swappable power supplies;
  3. provide sufficient cooling for a fully populated cabinet at the mandatory minimum storage capacity;
  4. all cooling for the system controller(s) as well as all hard disk drives must be redundant and monitored for failure by the storage platform hardware;
  5. include hot swappable cooling fans;
  6. the cooling system within the storage platform must be fully redundant. In the event of a component failure, the cooling system must allow continued operation of the storage platform until service can be performed.

5.1.5   Software and Management

The unit must include a menu driven configuration system for monitoring and configuring all aspects of operation. The menu system may be facilitated through a front mounted LCD panel, a character based terminal session or a GUI based software interface.

All required drivers and software for operation of the unit must be included.


5.2 Medium Disk-based Archival Storage

The following describes an intermediate disk-based archival storage platform. The device may be either a) block mode SAN; b) file mode NAS; or c) VTL with deduplication.


5.2.1 General

Each disk-based backup device must meet the following capacity and platform requirements:

  1. the hard disk drive technologies and densities must be commercially available, meaning that the Manufacturer is continuing to manufacture and ship them to customers generally;
  2. the hard disk drive technologies and densities must be tested and fully supported within the storage platform by the storage platform Manufacturer;
  3. it must include industry-standard Serial ATA (SATA) supporting 3Gb/s transfer rates, or serial attached SCSI (SAS) hard disk drives supporting 6Gb/s transfer rates, or low cost fibre channel (LCFC) hard disk drives supporting 4Gb/s transfer rates;
  4. the available drive options must include:
    1. 1TB areal drive densities at 7200RPM rotational speed;
    2. 2TB areal drive densities at 7200RPM rotational speed and 1TB drives with 5400 RPM  rotational speed for energy efficient requirements may be offered as options, if available;
  5. it must accommodate a minimum of 45 hard disk drives;  
  6. it must offer a standard 19" rack mount form factor in addition to any default chassis style offered ; and
  7. it must include lights or an LCD panel for power, activity and fault indications; and
  8. it must include power cables and any other ancillary items required for the connection and operation of the disk-based backup as well as end user documentation.

5.2.2 Capacity and Performance

The unit must:

  1. include a minimum of forty-five (45) industry standard Serial ATA (SATA), Serial Attached SCSI (SAS) or low-cost fibre channel (LCFC) hard disk drives with RAID enabled.  units must provide a total storage capacity of no less than 45TB of storage capacity.
  2. include drives supplied with the storage platform that meet the following minimum requirements:
    1. SATA, SAS or fiber ATA
    2. 16 MB onboard cache
    3. 7200 RPM spin rates
  3. include disk drives that are hot pluggable while the storage platform is operational and must utilize a canister system that allows easily inserting and removing the drives
  4. include a built in hardware RAID controller that stripes data across all 45 disk drives and presents either (a) logical drives, (b)file systems or (c) be virtualized to present standard tape drives, robotics and media slots to an attached host. to an attached host.
  5. include 256MB of write cache memory on the built in RAID controller to assist RAID operations.
  6. include a controller that  supports the following RAID types;
    1. RAID-4 –or- RAID-5 or RAID-6; and
    2. RAID-1 -or- RAID-1+0 -or- RAID-0+1
  7. For
    1. SAN units, allow configuration of a minimum of 4 RAID sets comprised of any of the mandatory RAID types and must simultaneously support different RAID types;
    2. NAS units,  RAID sets within the unit must not be visible to attached host systems as block devices, but rather must be presented as CIFS and NFS file systems;
    3. VTL units, RAID sets within the unit must not be visible to attached host systems as block devices, but rather must be virtualized and presented as tape cartridges;
  8. for a) SAN and b) NAS units, allow the allocation of three (3) hard disk drives as global hot spares, which will automatically rebuild the contents of a failed hard disk drive in any fault tolerant RAID set. This process must be fully automatic upon detection of a disk failure in a fault tolerant RAID set;
  9. include hard drives that are fully hot pluggable while the storage platform is operational. There must be no loss of data or other impact to the storage platform in the event that a hard drive is removed, assuming the drive is part of a fault tolerant configuration in the platform;
  10. rebuild a replaced hard disk drive automatically when it is inserted, with no user intervention on the management console, assuming it is replacing a hard disk drive that was part of a fault tolerant configuration;
  11. include RAID functionality built in to the storage platform and not require host based functionality for any RAID operations.

NAS units that are comprised of a clustered file system of 4 nodes providing RAID1 and RAID5/6-type protection at the filesystem level may be proposed in this Category.  The clustered filesystem must allow read/write (R/W) access to all NAS nodes. As configurations of this type provide an alternate form of data protection, they will not be required to meet the hardware RAID controller requirements specified at iv), v), vi), vii), viii) or x) above but must meet the requirements specified at ix) and xi).


5.2.3 Connectivity

  1. SAN units must utilize one of the following block mode interfaces for host connectivity:
    1. 1Gb or 10Gb Ethernet with iSCSI or FCoE;
    2. 8Gb Fibre Channel;

      The unit must provide 2 host-facing block mode interfaces.

      Also, if the storage platform requires a proprietary host bus interface for proper operation it must be identified and included as part of the default configuration.

  2. NAS units must include a micro-kernel operating system designed for providing file services to common internet file system (CIFS) and network file system (NFS) clients via included Ethernet interfaces. The micro-kernel operating system may be either a Windows (WSS), Linux or Unix-based operating system;

    A minimum of 4x1Gb or 2x10Gb Ethernet interfaces must be provided.

  3. VTL units must include fixed or variable block length deduplication at target and must be RAID protected.  At minimum RAID-5 must be supported.  RAID sets withi the unit must not be visible to attached host systems as block devices, but rather be virtualized and presented as standard tape drives, robotics and media slots to connected hosts.   VTL units must utilize one of the following interfaces for host connectivity:
    1. 1Gb or 10Gb Ethernet with iSCSI;
    2. 8Gb Fibre Channel;

      If the storage platform requires a proprietary host bus interface for proper operation it must be identified and included as part of the default configuration.

      NOTE: For both a) SAN and b) NAS units, the storage platform must support connectivity to standard Intel-based server platforms running Windows Server 2008.


5.2.4 Power and Cooling

The unit must provide the following power and cooling attributes:

  1. include power sufficient to operate a fully populated system for both the controller(s) as well as any shelves used to contain the drives. 
  2. include redundant N+1 power and utilize hot swappable power supplies;
  3. provide sufficient cooling for a fully populated cabinet at the mandatory minimum storage capacity;
  4. all cooling for the system controller(s) as well as all hard disk drives must be redundant and monitored for failure by the storage platform hardware;
  5. include hot swappable cooling fans;
  6. the cooling system within the storage platform must be fully redundant. In the event of a component failure, the cooling system must allow continued operation of the storage platform until service can be performed.

5.2.5   Software and Management

The storage platform must include the following software and management capabilities:

  1. all drivers, software and licenses required for operation of the unit must be included. If the storage platform utilizes iSCSI-based connectivity in the base configuration, the appropriate iSCSI initiator for Windows-based clients must be provided.
  2. the storage platform must include a comprehensive GUI-based management system that allows real-time monitoring of all components in the platform and reports failures or degraded components.
  3. the GUI interface for the storage platform must be a Windows-based application or may be a WEB or Java-based embedded function accessible via a standard browser.
  4. the storage platform must include components required for connectivity to an IP based network, either through a direct Ethernet connection on the platform or through an in-band connection via a fibre-attached host.
  5. the storage platform must issue SNMP traps, SMTP mail or dial out to a pager in the event of a storage platform device degradation or failure.
  6. the GUI interface for the storage platform must offer complete visibility of all installed hardware and it's current operational status.
  7. the GUI interface for the storage platform must allow configuration of all aspects of the storage platform.
  8. if the array presents block storage as LUNs, the storage platform must include array-based LUN masking that allows assigning explicit permissions between specific logical drives and specific SAN attached hosts. This must be configured and enforced at the storage array.
  9. the storage platform must have an array-based ability to expand RAID sets or logical units presented to hosts. This facility must be available through the GUI interface for the storage platform as part of the RAID and logical unit  management capabilities. Please note this is referring to the ability to expand the size of the RAID sets and Logical Unit Numbers (LUN's) at the hardware level and does not require a utility on the host to manipulate this space at the operating system level.

5.3 Large Disk-based Archival Storage

The following describes a large disk-based archival storage platform.  The device may be either a) block mode SAN; b) file mode NAS; or c) VTL with deduplication.


5.3.1  General

Each disk-based backup device must meet the following capacity and platform requirements:

  1. the hard disk drive technologies and densities must be commercially available, meaning that the Manufacturer is continuing to manufacture and ship them to customers generally;
  2. the hard disk drive technologies and densities must be tested and fully supported within the storage platform by the storage platform Manufacturer;
  3. it must include industry-standard Serial ATA (SATA) supporting 3Gb/s transfer rates, or serial attached SCSI (SAS) hard disk drives supporting 6Gb/s transfer rates, or low cost fibre channel (LCFC) hard disk drives supporting 4Gb/s transfer rates;
  4. the available drive options must include:
    1. 1TB areal drive densities at 7200RPM rotational speed;
    2. 2TB areal drive densities at 7200RPM rotational speed and 1TB drives with 5400 RPM  rotational speed for energy efficient requirements may be offered as options, if available;
  5. it must accommodate a minimum of 90 hard disk drives;
  6. it must offer a standard 19" rack mount form factor in addition to any default chassis style offered ; and
  7. it must include lights or an LCD panel for power, activity and fault indications; and
  8. it must include power cables and any other ancillary items required for the connection and operation of the disk-based backup as well as end user documentation.

5.3.2 Capacity and Performance

The unit must:

  1. include a minimum of ninety  (90) industry standard Serial ATA (SATA), Serial Attached SCSI (SAS) or low-cost fibre channel (LCFC) hard disk drives with RAID enabled. units must provide a total storage capacity of no less than 90TB of storage capacity.
  2. include drives supplied with the storage platform that meet the following minimum requirements:
    1. SATA, SAS or fiber ATA
    2. 16 MB onboard cache
    3. 7200 RPM spin rates
  3. include disk drives that are hot pluggable while the storage platform is operational and must utilize a canister system that allows easily inserting and removing the drives
  4. include a built in hardware RAID controller that stripes data across all 90 disk drives and presents either ; (a) logical drives, (b)file systems or (c) be virtualized to present standard tape drives, robotics and media slots to an attached host.
  5. include 512MB of write cache memory on the built in RAID controller to assist RAID operations.
  6. include a controller that  supports the following RAID types;
    1. RAID-4 –or- RAID-5 or RAID-6; and
    2. RAID-1 -or- RAID-1+0 -or- RAID-0+1
  7. The storage platform must offer an option for redundancy such that controller subsystem failures will be recovered by a surviving controller and service to the attached host(s) is continued without disruption.
  8. For a) SAN units, allow configuration of a minimum of 10 RAID sets comprised of any of the mandatory RAID types and must simultaneously support different RAID types; For b)  NAS units,  RAID sets within the unit must not be visible to attached host systems as block devices, but rather must be presented as CIFS and NFS file systems; For c) VTL units,  RAID sets within the unit must not be visible to attached host systems as block devices, but rather must be virtualized and presented as tape cartridges;
  9. For a) SAN and b) NAS units, allow the allocation of six (6) hard disk drives as global hot spares, which will automatically rebuild the contents of a failed hard disk drive in any fault tolerant RAID set. This process must be fully automatic upon detection of a disk failure in a fault tolerant RAID set;
  10. include hard drives that are fully hot pluggable while the storage platform is operational. There must be no loss of data or other impact to the storage platform in the event that a hard drive is removed, assuming the drive is part of a fault tolerant configuration in the platform;
  11. rebuild a replaced hard disk drive automatically when it is inserted, with no user intervention on the management console, assuming it is replacing a hard disk drive that was part of a fault tolerant configuration;
  12. include RAID functionality built in to the storage platform and not require host based functionality for any RAID operations.

5.3.3 Connectivity

  1. SAN units must utilize one of the following block mode interfaces for host connectivity:
    1. 1Gb or 10Gb Ethernet with iSCSI or FCoE;
    2. 8Gb Fibre Channel;

      The unit must provide 4 host-facing block mode interfaces. 

      Also, if the storage platform requires a proprietary host bus interface for proper operation it must be identified and included as part of the default configuration.

  2. NAS units must include a micro-kernel operating system designed for providing file services to common internet file system (CIFS) and network file system (NFS) clients via included Ethernet interfaces. The micro-kernel operating system may be either a Windows (WSS), Linux or Unix-based operating system;

    A minimum of 4x1Gb or 2x10Gb Ethernet interfaces must be provided.

  3. VTL units must include fixed or variable block length deduplication at target and must be RAID protected.  At minimum RAID-5 must be supported.  RAID sets within the unit must not be visible to attached host systems as block devices, but rather be virtualized and presented as standard tape drives, robotics and media slots to connected hosts.   VTL units must utilize one of the following interfaces for host connectivity:
    1. 1Gb or 10Gb Ethernet with iSCSI;
    2. 8Gb Fibre Channel;

If the storage platform requires a proprietary host bus interface for proper operation it must be identified and included as part of the default configuration.

NOTE: For both a) SAN and b) NAS units, the storage platform must support connectivity to standard Intel-based server platforms running Windows Server 2008.

The storage platform must support connectivity to a minimum of 20 standard Intel-based server platforms running Windows Server 2008.


5.3.4 Power and Cooling

The unit must provide the following power and cooling attributes:

  1. include power sufficient to operate a fully populated system for both the controller(s) as well as any shelves used to contain the drives.
  2. include redundant N+1 power and utilize hot swappable power supplies;
  3. provide sufficient cooling for a fully populated cabinet at the mandatory minimum storage capacity;
  4. all cooling for the system controller(s) as well as all hard disk drives must be redundant and monitored for failure by the storage platform hardware;
  5. include hot swappable cooling fans;
  6. the cooling system within the storage platform must be fully redundant. In the event of a component failure, the cooling system must allow continued operation of the storage platform until service can be performed.

5.3.5 Software and Management

The storage platform must include the following software and management capabilities:

  1. all drivers, software and licenses required for operation of the unit must be included. If the storage platform utilizes iSCSI-based connectivity in the base configuration, the appropriate iSCSI initiator for Windows-based clients must be provided.
  2. the storage platform must include a comprehensive GUI-based management system that allows real-time monitoring of all components in the platform and reports failures or degraded components.
  3. the GUI interface for the storage platform must be a Windows-based application or may be a WEB or Java-based embedded function accessible via a standard browser.
  4. the storage platform must include components required for connectivity to an IP based network, either through a direct Ethernet connection on the platform or through an in-band connection via a fibre-attached host.
  5. the storage platform must issue SNMP traps, SMTP mail or dial out to a pager in the event of a storage platform device degradation or failure.
  6. the GUI interface for the storage platform must offer complete visibility of all installed hardware and it's current operational status.
  7. the GUI interface for the storage platform must allow configuration of all aspects of the storage platform.
  8. if the array presents block storage as LUNs, the storage platform must include array-based LUN masking that allows assigning explicit permissions between specific logical drives and specific SAN attached hosts. This must be configured and enforced at the storage array.
  9. the storage platform must have an array-based ability to expand RAID sets or logical units presented to hosts. This facility must be available through the GUI interface for the storage platform as part of the RAID and logical unit management capabilities. Please note this is referring to the ability to expand the size of the RAID sets and Logical Unit Numbers (LUN's) at the hardware level and does not require a utility on the host to manipulate this space at the operating system level.

5.4   Virtual Tape

The following describes a “virtual” tape backup device including fixed or variable block length deduplication of data at target.


5.4.1  General

The virtual tape device must:

  1. provide emulation of industry standard tape drives, robotics and media slots and must appear to fibre-connected hosts as a fibre-attached tape library;
  2. be a currently shipping factory-built product that has been designed, tested, assembled and is supported by a single manufacturer for warranty, support and service. An integration of third party components in order to provide the mandatory functionality described herein will be deemed non-compliant;
  3. must provide a minimum of 45TB of raw storage. This minimum must be achieved using current hard disk drive technology and densities, which are tested and fully supported within the storage platform by the storage platform manufacturer;
  4. be provided in a standard 19" rack mount chassis;
  5. include lights or an LCD panel for power, activity and fault indications
  6. include power cables and any other ancillary items required for the connection and operation of the disk-based backup unit as well as end user documentation.  

5.4.2 Capacity and Performance

The unit must:

  1. include a minimum of forty-five  (45) industry standard Serial ATA (SATA), Serial Attached SCSI (SAS) or low-cost fibre channel (LCFC) hard disk drives with RAID enabled. units must provide a total storage capacity of no less than 45TB of storage capacity.
  2. include drives supplied with the storage platform that meet the following minimum requirements:
    1. SATA, SAS or fiber ATA
    2. 16 MB onboard cache
    3. 7200 RPM spin rates
  3. include disk drives that are hot pluggable while the storage platform is operational and must utilize a canister system that allows easily inserting and removing the drives
  4. include a built in hardware RAID controller that stripes data across all 45 disks ;
  5. be RAID-protected. At minimum RAID-5 must be supported. RAID sets within the unit must not be visible to attached host systems as block devices, but rather be virtualized and presented as standard tape drives, robotics and media slots and must appear to fibre-connected hosts as a fibre-attached tape library.
  6. include 256MB of battery-protected write cache memory on the RAID controller to assist RAID-5 operations;
  7. allow the allocation of two (2) hard disk drives as global hot spares, which will automatically rebuild the contents of a failed hard disk drive in any fault tolerant RAID set. This process must be fully automatic upon detection of a disk failure in a fault tolerant RAID set;
  8. include hard drives that are fully hot pluggable while the storage platform is operational. There must be no loss of data or other impact to the storage platform in the event that a hard drive is removed, assuming the drive is part of a fault tolerant configuration in the platform;
  9. rebuild a replaced hard disk drive automatically when it is inserted, with no user intervention on the management console, assuming it is replacing a hard disk drive that was part of a fault tolerant configuration;
  10. include RAID functionality built in to the storage platform and not require host based functionality for any RAID operations;
  11. provide data deduplication at the target.
  12. provide IP-based Asynchronous replication of deduplicated data.

5.4.3 Connectivity

The device must utilize one of the following block mode interfaces for host connectivity per controller:

  1. 1 Gb or 10Gb Ethernet with iSCSI or FCoE
  2. 4Gb or 8Gb Fibre Channel.

The unit must provide 2 host-facing block mode interfaces.

If the storage platform requires a proprietary host bus interface for proper operation it must be identified and included as part of the default configuration.

 The storage platform must support connectivity to a minimum of 5 standard Intel-based server platforms running either Windows 2008, Windows 2003, Solaris, HPUX, AIX or Linux.


5.4.4 Power and Cooling

The unit must provide the following power and cooling attributes:

  1. include power sufficient to operate a fully populated system for both the controller(s) as well as any shelves used to contain the drives.
  2. include redundant N+1 power and utilize hot swappable power supplies;
  3. provide sufficient cooling for a fully populated cabinet at the mandatory minimum storage capacity;
  4. all cooling for the system controller(s) as well as all hard disk drives must be redundant and monitored for failure by the storage platform hardware;
  5. include hot swappable cooling fans;
  6. the cooling system within the storage platform must be fully redundant. In the event of a component failure, the cooling system must allow continued operation of the storage platform until service can be performed.

5.4.5   Software and Management

The storage platform must include the following software and management capabilities:

  1. all drivers, software and licenses required for operation of the unit must be included. If the storage platform utilizes iSCSI-based connectivity in the base configuration, the appropriate iSCSI initiator for Windows-based clients must be provided.
  2. the storage platform must include a comprehensive GUI-based management system that allows real-time monitoring of all components in the platform and reports failures or degraded components.
  3. the GUI interface for the storage platform must be a Windows-based application or may be a WEB or Java-based embedded function accessible via a standard browser.
  4. the storage platform must include components required for connectivity to an IP based network through a direct Ethernet connection on the platform.
  5. the storage platform must issue SNMP traps, SMTP mail or dial out to a pager in the event of a storage platform device degradation or failure.
  6. the GUI interface for the storage platform must offer complete visibility of all installed hardware and it's current operational status.
  7. the GUI interface for the storage platform must allow configuration of all aspects of the storage platform including all controllers, cache, interfaces, drives, RAID configurations and logical drives as well as permissions to logical drives .
  8. the storage platform must have an array-based ability to expand RAID sets or logical units presented to hosts. This facility must be available through the GUI interface for the storage platform as part of the RAID and logical unit  management capabilities. Please note this is referring to the ability to expand the size of the RAID sets and Logical Unit Numbers (LUN's) at the hardware level and does not require a utility on the host to manipulate this space at the operating system level.
  9. the virtual tape device must be directly supported by three of the following backup software packages:  Symantec NetBackup or Backup Exec, Tivoli TSM, Legato Networker, Computer Associates BrightStor, HP Data Protector and CommVault Simpana.  The virtual tape device model must be listed as a supported product on the software bidder's website or published compatibility documentation.
  10. The bidder must provide a list of backup software that is compatible with the tape library, including a list of the supported Operating Systems.

5.5 Grid-based Storage

The following describes a disk-based archival or backup system based on a scalable grid of multiple discrete storage nodes, with both data and parity distributed across the nodes.   


5.5.1    General

  1. The platform must provide a scalable grid of discrete nodes for the purposes of archiving or backup of the data.
  2. The nodes must be shipping factory-built products that have been designed, tested, assembled and supported by a single manufacturer for warranty, support and service. An integration of third party components to provide the mandatory functionality described herein will be deemed non-compliant.
  3. All capabilities described must be native capabilities of the storage nodes and may not be supplemented or provided through an external application.
  4. Each storage node must contain its own storage medium, microprocessor, indexing capability, and management layer.
  5. The nodes must interface directly with archival or backup software through an API or by using a driver set supplied with the unit or with the operating system. If an additional external application is required for the purposes of archiving or backup, this must be identified clearly in the bid response.
  6. The unit must utilize a smart content storage algorithm that stores redundant archived data in a single instance such that the same content is only written to the storage once reducing space requirements. A storage device that includes Point in Time snapshots, such that unchanged data over multiple snapshots is stored once, reducing space requirements, is acceptable.
  7. The unit must provide the ability to store data in a Write-Once-Read-Many (WORM) format, or allow the data to be read many times while preventing writes to the data.
  8. The unit must provide the ability to flag stored data using specific retention periods or priorities such that it may be stored and ultimately destroyed if required based on policies.

5.5.2 Capacity and Performance

The unit must:

  1. include a minimum of 4 nodes with a minimum of 4 hard disk drives per node;
  2. provide a total storage capacity of no less than 16TB of raw storage capacity based and must be scalable to a minimum of 64TB raw capacity;
  3. utilize a scalable “grid” architecture that allows the addition of nodes including disk capacity on the fly without disrupting operations. These additional grid members must automatically join the existing storage environment and extend the usable capacity without administrator intervention;
  4. include drives supplied with the storage platform that meet the following minimum requirements:
    1. SATA, SAS or fiber ATA
    2. 16 MB onboard cache
    3. 5400 RPM spin rates
  5. include multiple self-contained storage nodes interconnected for high availability (HA) so that any node can communicate with any other node;
  6. RAID sets and their capacity within the storage grid must not be visible to attached host systems.  Capacity must be abstracted such that all associated management functions take place within the storage grid.
  7. nodes must be fully hot pluggable while the storage platform is operational. There must be no loss of data or other impact to the storage platform;
  8. replace a node with no user intervention on the management console;
  9. provide all RAID functionality or provide all data parity and protection within the storage grid and must not require host-based functionality for data protection operations.

5.5.3    Connectivity

The device must:

  1. utilize a minimum of  2x1Gb Ethernet interfaces for connectivity;
  2. Include a redundant switching network for the interconnection of grid elements and for back end internal communication.

5.5.4    Power

The unit must provide the following power and cooling attributes:

  1. include power supplies sufficient to operate a fully populated system;
  2. include redundant N+1 power and utilize hot swappable power supplies;
  3. provide sufficient cooling for a fully populated cabinet at the mandatory minimum storage capacity;
  4. all cooling for the system controller(s) as well as all hard disk drives must be redundant and monitored for failure by the storage platform hardware and must report a failure status through the front mounted indicators or through software alerting;
  5. include hot swappable cooling fans;
  6. the cooling system within the storage platform must be fully redundant. In the event of a component failure, the cooling system must allow continued operation of the storage platform until service can be performed.

5.5.5 Software and Support

The storage platform must be certified to operate with one of the following applications :

  1. Symantec NetBackup, Enterprise Vault or Backup Exec;
  2. Tivoli TSM;
  3. EMC Legato Networker;
  4. Computer Associates BrightStor;
  5. HP Data Protector;
  6. CommVault Simpana.

5.5.6    Management

The storage platform must include the following software and management capabilities:

  1. all drivers (unless included on the host OS), software and licenses required for operation of the unit must be included.
  2. grid elements must be presented and managed as a single storage pool;
  3. the storage platform must include a comprehensive GUI-based management system that allows real-time monitoring of all components in the platform and reports failures or degraded components. 
  4. the GUI interface for the storage platform must be a Windows-based application or may be a WEB or Java-based embedded function accessible via a standard browser.
  5. the storage platform must include components required for connectivity to an IP based network, either through a direct Ethernet connection on the platform or through an in-band connection via a fibre-attached host.
  6. the storage platform must issue SNMP traps, SMTP mail or dial out to a pager in the event of a storage platform device degradation or failure.
  7. the GUI interface for the storage platform must offer complete visibility of all installed hardware and it's current operational status.
  8. the GUI interface for the storage platform must allow configuration of all aspects of the storage platform.
  9. if the array presents block storage as LUNs, the storage platform must include array-based LUN masking that allows assigning explicit permissions between specific logical drives and specific SAN attached hosts. This must be configured and enforced at the storage array.

The storage platform must allow expansion of storage pools by adding nodes dynamically and online.