ctbto mass storage system replacement 2009 and ......12 sam-fs 4.6.49, rev = 5.9.2006.02.23, license...

Terms of Reference

FOR

CTBTO Mass Storage System

Replacement 2009 and

Maintenance

www.ctbto.org

This document contains the Terms of Reference for the procurement of a new system to replace the current

StorageTek Mass Storage System which is the main repository of all verification-related data and IT

infrastructure backup data for the Provisional Technical Secretariat of the Comprehensive Nuclear Test-Ban-

Treaty Organization.

Terms of Reference: CTBTO Mass Storage System Replacement 2009 and Maintenance

of 32

Table of Contents

1. INTRODUCTION............................................................................................................................... 3

2. BACKGROUND INFORMATION ........................................................................................................ 3

3. CURRENT STATUS ........................................................................................................................... 4

3.1 MSS HARDWARE AND SOFTWARE COMPONENTS .............................................................................................. 5 3.2 SAN ENVIRONMENT.................................................................................................................................... 7

4. CURRENT BACKUP AND ARCHIVING SCHEME ................................................................................ 8

4.1 ARCHIVING ................................................................................................................................................ 8 4.2 BACKUP .................................................................................................................................................... 8

5. NEW BACKUP AND ARCHIVING CONCEPT .................................................................................... 10

5.1 ARCHIVE: ................................................................................................................................................ 10 5.2 BACKUP: ................................................................................................................................................. 11

6. MASS STORAGE SYSTEM REPLACEMENT SERVICES - TECHNICAL REQUIREMENTS AND

CONSIDERATIONS…………………………………………………………………………………………………………………………….13

6.1 HARDWARE AND SOFTWARE REQUIREMENTS ..................................................................................... 13

6.1.1 Mandatory items: ............................................................................................................................... 17 6.2 ENVIRONMENTAL CONSIDERATIONS ................................................................................................... 20 6.3 SERVICE CONSIDERATIONS ................................................................................................................... 21

6.3.1 Mandatory items: ............................................................................................................................... 21 6.3.2 Preferred items: .................................................................................................................................. 22

6.4 EQUIPMENT TRADE-IN ......................................................................................................................... 22

7. MASS STORAGE SYSTEM MAINTENANCE SERVICES………………………………………………………………….23

8. WORK TASK REVIEW .................................................................................................................... 24

APPENDIX AND GLOSSARY .................................................................................................................... 25

TABLE E: SERVER INFRASTRUCTURE ...................................................................................................... 26


of 32

1. INTRODUCTION

The Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty Organization

(hereinafter referred to as the “Commission”) is the international organization established to

carry out the effective implementation of the global verification system foreseen under the

Comprehensive Nuclear-Test-Ban Treaty (CTBT), which is the Treaty banning any nuclear

weapon test explosion or any other nuclear explosion. The Treaty provides for a global

verification regime, including a network of 337 stations worldwide, a communications

system, an international data center and on-site inspections to monitor compliance.

The Headquarters and the International Data Center (IDC) of the Preparatory Commission

are in Vienna (Vienna International Center of United Nations).

One fundamental task of the IDC is to provide States Parties with equal, open, timely and

convenient access to agreed products and services to support their national CTBT

verification requirements. To meet this task, the IDC performs a large fraction of the

computationally intensive technical work required by most States Parties. This includes

collecting and archiving data to a Mass Storage System (MSS) from the International

Monitoring System (IMS) sensors and other sources. Advanced technologies have been

incorporated to allow the IDC to perform its work with as high a degree of automation, cost-

efficiency, security and reliability as possible.

All data processing and archiving for the above mentioned tasks are performed in a

UNIX/Linux environment. The UNIX/Linux hardware platform deployed by the Commission

runs the IDC Application Software. In addition to this, a range of other services using the

UNIX platform were installed. Among these are Internet Services (e.g. Web-Servers, DNS,

Mail system, Firewall, etc.), Storage Area Network (SAN), Network Management Services,

and Database Services to support application software.

2. BACKGROUND INFORMATION

The Commission desires to engage a contractor (hereinafter referred to as the “Contractor”)

to provide services regarding the implementation and maintenance of a new Mass Storage

System (MSS) (hereinafter referred to as the “Work” or “Services” ).

The current MSS was built around the StorageTek PowderHorn 9310 tape library system and

has been in use for the last seven (7) years to archive the International Monitoring System

(IMS) data and to store system data backups. The configuration of the new MSS is depicted

in the diagram MSS Environment. Due to impending end-of-service-life (EOSL) of the current

MSS and ever increasing demands for higher performance and storage capacity, a new MSS

is urgently required and shall be implemented by the first quarter of 2010(non-binding time).

Furthermore, the Contractor needs take into consideration several critical issues and

challenges which shall be addressed in the design of the new MSS:

1) Constant increase in data volume demands more efficient use of system resources

(disk space and tapes). The need for highly available hierarchical storage

management functionality arises as data lifecycle management mechanisms are

considered for the future.


of 32

2) Availability requirements of the verification and non-verification related data are

expected to meet the same criteria for restoration, recovery and access response

times.

3) Optimization of backup/restore mechanisms to reduce backup time windows and

ability to start restore instantaneously.

4) Currently, Legato Networker is not configured to perform backup for machines

outside the firewall due to security risks of having too many open ports through the

firewall. The proposed solutions should also address the backup for both servers with

local storage and servers directly attached to the SAN outside the firewall.

5) Adopting Open Source software platforms needs particular attention and test

qualification from system vendors and manufacturer when it comes to the

compatibility matrix and the subsequent support.

6) During the last few years a policy decision has driven the CTBTO into a direction to

use Open Source software platforms for the processing of verification related data.

Red Hat Enterprise Linux 5 (hereinafter RHEL5) is the currently used platform. The

compatibility between the operating systems of the server clusters (being Open

Source powered) and the storage elements with their own proprietary set up has

proven in some aspects to be a challenge.

7) The new generation tape system could coexist with the legacy STK9310 for the time

period until all data is migrated to the new MSS. However, due to floor space

limitations, complete removal of the old MSS is preferred in order to provide

adequate space for the new MSS. This approach, if technically feasible, should be

undertaken with the least disruption to the continuous operation of archiving and

backup processes. This transitional period, while having a top priority to ensure data

integrity of the migration, requires compatibility for existing servers and OS platforms

with the new MSS and data management system.

8) From a long term perspective, the operating system, hardware platform, backup

system compatibility and support are seen as potential risks. The new MSS and data

management system requires current up to date support plans for complete

heterogeneous systems supportability.

3. CURRENT STATUS

Data backup and archiving is performed over the network on the StorageTek Mass Storage

System (MSS) which provides data protection and recovery path in case of data loss or

corruption in the main site data centre.

The CTBTO UNIX Environment has 121 servers, mostly SAN attached storage. As shown in

Table E: Server Infrastructure, the CTBTO Unix computing infrastructure mainly consists of:

1) Operations (OPS) and Testbed (TST) networks currently consist of Sun/SPARC servers.

These systems are expected to be replaced with virtual machines running on RHEL

clusters approximately within a year.


of 32

2) A Development network (DVL) is composed of 2 Sun/SPARC servers and several

Opteron based servers.

3) The entire infrastructure is also composed of several other networks as IMS, OSI,

Infra, etc.

4) The network backbone is a switched Gigabit Ethernet

5) Most of Sun servers are running RHEL5 while some older systems still run Solaris 9

and 10.

6) Database servers are running Oracle 9i – 9.2.0 and 10g.

Refer to Table E: Server Infrastructure on pg. 26-31 of this document for complete server and

applications information.

Figure 1: Current MSS Environment

3.1 MSS Hardware and Software Components

The Table A below shows a list of the hardware and software components currently installed.

L600

STK

STK

MSS Server Sun E4900 SAM-FS/Legato

SE9

Serial SCSI

9840

LMU

FC

ASCLS Server Sun V240

9840

9840

9840

9840

9840

9940B

9940B

9940B

9940B

FC STK 9310

SE 9980V


of 32

Table A: Hardware and Software Components

No. Item Description

Hardware

1 PowderHorn 9310 S/N 4000011845, Library Storage Module

2 Stand Alone LMU S/N 21600003008, Library Management Unit

3 LCU S/N 008000011922, Library Control Unit

4 Drive Library CA S/N 265000002949, 6 x StorageTek 9840 Tape

Drives & 4 x StorageTek T9940B Full Fabric

Drives

5 Sun Fire V240 S/N TN54340563, 2x1.5GHz CPU, 2GB Memory

6 Sun Fire E4900 S/N 0602MM2000, 4x1.35GHz CPU, 16GB

Memory, 1xCPU/Memory Board, 3xP/S,

3xFans, 2x System Controller, 1xPCI+I/O

Assembly (8 slots each), 2xPCI dual SCSI/dual

Ethernet Adapter, 2xSun Dual GigE+Dual SCSI,

3xDual-channel Differential UltraSCSI HBA,

4x2Gb PCI Dual FC Network Adapter, Sun Fire

Rack with 2 rack fan trays.

7 Sun StoEdge D240 S/N 0548BC1038, with 1 DVD, 3 x 73GB HD,

Connected to E4900

8 Sun StoEdge D240 S/N 0548BC103B, with 1 DVD, 3 x 73GB HD,

Connected to E4900

9 9840 (20GB) Tapes Quantity: 5188 tapes

10 9940 (200GB) Tapes Quantity: 410 tapes + 120 new tapes on order

Software

11 Solaris 9 Running on E4900 and V240.

12 SAM-FS 4.6.49, REV =

5.9.2006.02.23, License for 5000

slots

Running on E4900.

13 ACSLS 7.1.0, License for 5000

slots.

Running on V240.

14 Legato Networker for Solaris

7.3.Build.190

Running on E4900. For detailed listing of server

and client licenses, refer to Legato Networker

Licenses under Table E: Server Infrastructure on

pg. 26-31 of this document (Line 27: iss002).


of 32

Table B: Tape Library Statistics Based On SAM-FS Dump

The Table B below shows the tape library statistics based on SAM-FS Dump.

Note: Above figures may fluctuate on a daily basis.

3.2 SAN Environment

A new central storage system is currently being implemented to replace the StorEdge 9980V.

This new storage system will be hierarchical in design; consisting of two Tier-1 (ST9985V) and

four Tier-2 (ST6140) storage systems.

It is intended that parts of this storage system will be used for the new MSS, either for

permanent storage or temporary (caching) data storage. Four (4) clusters made by eight (8)

Hitachi Data Systems NAS 1300C NFS appliance gateways will replace the NFS clusters as

front-end to client hosts.

The new SAN deployment is still ongoing and is not operational yet. At the time of writing,

the old SE9980V is still in use but will be decommissioned as soon as the new SAN is put into

production (Estimated Q3 or Q4 2009).


Capacity

Capacity Used No. of Tapes

1 Type 9940B online in library 44,9 TB 70,00% 246

2 Type 9840 online in library 49,5 TB 91,00% 2669

3 Type STK9940B offline 28,42 TB 154

4 Type STK9840 offline 43,25TB 2331

5 Capacity in online cache 1,76TB

6 Capacity in disk archive 0,35TB


of 32

BR5100

Server Group A Server Group B Server Group C Server Group D

BR5100 BR4100 BR5100 BR5100 BR5100BR5100 BR4100

Tier 2 StorageTier 1 Storage

48 48

8 8 8 8

88 Serverports

64 Storageports

152 total

88 Serverports

64 Storageports

152 total

Figure 2: Current SAN Design and FC Connections

For a detailed configuration of the SAN Environment see document under page 32 of the

document (Appendix New CTBTO SUN Fiber Layout).

4. CURRENT BACKUP AND ARCHIVING SCHEME

The current backup and archiving processes are performed utilizing SAM-FS hierarchical

storage management software and Legato Networker running on a Sun Fire E4900; and

ACSLS running on the Sun V240. Part of the StorEdge 9980V is used for disk cache. Every

tape in the library is duplicated. One set of tapes is sent to an off-site storage while the other

set stays in the tape library silo. Archived data tapes are stored permanently while, backup

tapes are recycled periodically.

4.1 Archiving

The E4900 exports the SAM-FS file systems via NFS. Data to be archived is written in the

SAM-FS cache file system. SAM-FS maintains in sync written data with the tapes. The cache

file system is cleared according to several SAM-FS directives.

4.2 Backup

Legato Networker which runs on the same E4900 performs backup for all servers. Backups

are written into the file system disk cache of /bdata. SAM-FS is then responsible for the

transfer of backup data from cache file system to tapes.

The following Table C depicts the current sizes of SAM-FS file systems. The first two (2)

comprise the backup data while the rest are archive data.


of 32

Table C: SAM-FS File Systems

No. File System Size

Backup

1 /nsr 28.5GB

2 /bdata 33.8TB

Archive

3 /archive/cdrom 7.4GB

4 /archive/ops 37.9TB

5 /archive/syslog 1.4TB

6 /archive/IMS 4.3TB

7 /archive /Testbed 11.3TB

8 /archive/project/MN 495.5GB

9 /archive/project/SM 687.8GB

10 /archive/ci 389.4GB

11 /archive/gci 100.6GB

Total: 90.36TB

Archiving uses the fast access STK9840 drives; whereas the backup system uses the high

capacity STK9940 drives. The graph below shows the backup and archive growth trend

within the last three (3) years.

Chart 1: SAM-FS Monthly Statistics

The backup and archiving processes as described above has been in place for the last eight

(8) years. It has been proven reliable but needs to be improved in terms of availability and

performance. Also, data security can be further enhanced.


of 32

1) The Sun Fire E4900 is a unique piece of hardware in the Commission’s hardware pool.

As such, it requires non-standard procedures and configuration thereby complicating

system administration and maintenance.

2) There is potential risk that in case of a disaster, the data contained in partially-full

tapes (both copies in library) may be lost.

3) No encryption is currently implemented to protect tapes from unauthorized access in

off-site storage.

4) Access to data stored on tape is slow. Due to increasing amount of data being

handled, response time is no longer adequate.

5. NEW BACKUP AND ARCHIVING CONCEPT

The new MSS should be able to address the deficiencies of the current MSS. A separate

backup and archive processes with their own dedicated resources through “partitioning” for

backup and archiving will be implemented in order to improve system resilience. The new

backup system is to support LAN-less backup and NDMP for NAS clients and other servers

with Fibre Channel connectivity. Legato Networker backup software will be replaced by

Symantec Veritas NetBackup due to the incompatibility with Hitachi NAS appliances.

For utmost availability the servers for archive must be clustered and the tape library system

must be fully redundant in design.

Currently the systems are all in one data centre. For a better recovery point objective (RPO),

a second site for archive data will be implemented.

The new MSS shall have a new backup and archiving (See below Figure 4: Visual depiction of

the new backup concept and Figure 5: Visual depiction of the new archive concept) in

accordance with the following technical design points for the new architecture:

5.1 Archive:

1. High availability of the NFS service

2. For higher performance and faster recovery of the archive, the first copy will

reside on disk. The first copy of data is stored on Tier-2 disk storage (Sun STK6140

presented through Sun ST9985V) in the main site data centre.

3. The second copy of the archive will be stored in the new tape library in the main

site data centre. Tapes will be periodically ejected and vaulted offsite according

to the CTBTO retention policies.

4. For increased recovery point objective (RPO) a third copy of data will be

transferred via LAN to a remote location (through SAM-FS remote) to the second

library system.

5. To support mission-critical operations, the use of a SAM-FS cluster on Sun Solaris

platform is planned. This cluster will be operated in the data centre main site as a

campus cluster.


of 32

5.2 Backup:

1. Backup data will be written into two tapes of the tape library (main site); one

copy will be ejected and stored off-site

2. The backup server does not require the same high availability requirements as

the archive server. However, for performance reasons, the need for a media

server is envisaged.

3. Oracle database systems will be backed up via Symantec Veritas NetBackup.

CTBTO Main-Site

STK

9985VSL 3000 (redundant Robots)

Backup Master +

Media Server

SAM-FS Cluster

Node 1

SAM-FS Cluster

Node 2

CTBTO Remote-Site

SL 3000

SAM-FS

Remote

Backbone Ethernet Switch Ethernet

SAN

1GBit/s Ethernet

SAM-Cache

+ Archive Copy 1

Archive Copy 2

+ Backup Target

Archive Copy 3

9x FC 9x FC

8x FC

8x FC

3x FC

2x FC2x FC2x FC

4x FC 4x FC

2x FC

8x

Ethernet

8x

Ethernet

8x

Ethernet

1x (od. 2x)

Ethernet

2x

Ethernet

Figure 3: New Mass Storage System


of 32

CTBTO Main-Site

STK

9985VSL 3000 (Backup Partition – 5xT10k)

Backup Master & Media

Backbone Ethernet Switch

SAN

Backup Target

9x FC 9x FC

8x FC

8x FC

4x FC 4x FC

8x

Ethernet

2x

Ethernet

52x Sym.

Standard Client

Essential NAS

4x Cluster

8x FC

8x FC

Additional Media Server

Figure 4: Visual depiction of the new backup concept

Figure 5: Visual depiction of the new archive concept


of 32

6. MASS STORAGE SYSTEM REPLACEMENT SERVICES - TECHNICAL REQUIREMENTS

AND CONSIDERATIONS

During the implementation of the new MSS, the Contractor shall provide the goods and

services as set out in this Terms of Reference including, but not limited to, hardware and

software requirements, as described in Section 6.1, environmental considerations as

described in Section 6.2, Service considerations as described in Section 6.3 and equipment

trade-in as described in Section 6.4. The Contractor shall inform the Commission and may

propose alternatives should the specified models, versions and/or releases of hardware and

software change or are superseded.

6.1 HARDWARE AND SOFTWARE REQUIREMENTS

The Contractor shall provide the following hardware and software:

Tape Systems Main Site + Remote Site Configuration Details Mandatory, Preferred,

Optional

Hardware

1.1

Sun STK SL3000 Tape

Library

(Main Site)

Support for the Symantec

Veritas NetBackup

software

M

1.2 Support for all in Table E

listed Hardware-Platforms

and Operating Systems

M

1.3 Support for following drive

types: LTO, T10000

M

1.4 Support for mixing LTO and

T10000 cartridges in all

available slots

M

1.5

Support for hardware

partitioning up to min. 4

partitions

M

1.5 Control via FC and/or

Ethernet

M

1.6 300 slots available

(upgradeable to 1000 slots

minimum per software

key)

M

1.7 7x Sun T10000B drives

(upgradeable to min.20

drives )

M

1.8 Redundant robotics M

1.9 Non disruptive

serviceability incl. CAP

motor, cooling fans, power

supplies, drives

M

1.10 Slot on demand by

software license key

enablement

M

1.11 Operator panel M

1.12 Cartridge Access Port for

min. 20 cartridges

M

1.13 Redundant configuration

and cost per tape drive

KMS 2.0 Encryption System O


of 32


Optional

2.1 Sun STK SL3000 Tape

Library (Remote site)

Support for Symantec

Veritas NetBackup

software

M

2.2 Support for all in Table A



M

2.3 Support for following drive

types: LTO, T10000

M

2.4 Support for mixing LTO and

T10000 cartridges in all

available slots

M

2.5 Control via FC and/or

Ethernet

M

2.6 Operator panel M

2.7 Non-disruptive

serviceability incl. CAP

motor, cooling fans, power

supplies, drives

M

2.8 100x slots available

(upgradeable up to min.

300 slots per software lic.

key)

M

2.9 2x T10000B drives (upgra

to min. 10 drives)

M

2.10 Cartridge access port for

min. 20 cartridges M

3.1 T10000B Drives

/Cartridges

Support for the offered

backup software

M

3.2 Support for all in Table A



M

3.3 Native throughput

(uncompressed) 120 MB/s

or above

M

3.4 Native capacity

(uncompressed) 1 TB

M

3.5 Support for WORM O

3.6 Built in hardware

encryption capabilities

M

3.7 Interface 4 Gb FC M

3.8 Redundant FC ports M

3.9 Error correction capability

of 1x1019

or above

M

3.10 Expected archival life of 20

years or above

M

3.11 Robust cartridge

technology / cartridge

warranty 10 years or above

M


of 32


Optional

Software

4.1 Library Monitoring SNMP based M

4.2 Library Partitioning Min. 4 physical library

partitions

M

Backup Software / Backup & Media Server Configuration Details Mandatory, Preferred,

Optional

Hardware

6.1 Backup server

(Main Site)

1x Sun Fire X4440

or equivalent server type

- CPU: 2x Quadcore Opteron

2.5 GHz (extendable to 4x if

needed)

- RAM: min. 32 GB

(extendable to min. 64 if

needed)

- min. 4x Ethernet ports

10/100/1000

- min. 4x FC ports 8 GbFC

(min. 2 HBAs for redundancy)

- min. 4 internal discs 10k

rpm, min. 146GB, RAID 5 (1

Standby)

- Solaris 10 pre-installed

M

6.2 Media server

(Main Site)

1x Sun Fire X4240


- 2x Quad Core AMD Opteron

Modell 2380, 2.5 GHz

- 32GB RAM

- 2xFC8GB


M

Software

Note: Backup Software support and licensing requirement as per Table E: Server Infrastructure.

7.1

Symantec Veritas

NetBackup

Master Server on Solaris 10 M

7.2 Clients on Solaris 9 and 10 M

7.3 Clients on RHEL 5.2 (+above) M

7.4 Clients on SLES P

7.5 Clients Windows 2000 M

7.6 Clients Windows 2003 M

7.7 Clients Windows 2008 P

7.8 Clients on XEN (RHEL) Guests M

7.9 Clients on XEN (RHEL) Server M

7.10 Vmware ESX 3.x and above P

7.11 Oracle, RMAN, online M

7.12 Open File Support M


of 32

Backup Software / Backup & Media Server Configuration Details Mandatory, Preferred,

Optional

8.1 Required functionality Multistreaming M

8.2 Required functionality Multiplexing M

8.3 Required functionality Monitoring M

8.4 Required functionality Reporting M

8.5 Required functionality Backup to Disk (NFS, or local

Disk)

O

8.6 Required functionality NDMP for HDS Essential NAS

1500c

M


of 32

Archive Server Cluster / Archive remote server Configuration Details Mandatory, Preferred,

Optional

9.1 Two primary Sun SAM-FS

servers (Cluster)

2x Sun Fire X4240


- CPU: 2x Quadcore

Opteron 2.5 GHz

- RAM: min. 32 GB


needed)


10/100/1000


(min. 2 HBAs for

redundancy)



Standby)


M

9.2 Sun SAM-FS server

(remote)

1x Sun Fire X4140


- CPU: 2x Quadcore

Opteron 2.5 GHz

- RAM: min. 32 GB


needed)


10/100/1000


(min. 2 HBAs for

redundancy)



Standby)


M

Software

10.1 SAM-FS Software for Sun

server cluster

Licensed to capacity of

162TB (main site)

M

10.2 SAM-FS Software for SAM

remote server

Licensed to capacity of

80TB

M

10.3 SUN Cluster Software Additional Agent for

failover SAMFS

M

10.4 Disk archive on ZFS ZFS should be used to

hold copy1

P

10.5 SAM-FS remote

configuration

Copy3 is written to a SAM-

remote server

M

6.1.1 Mandatory items:

The Contractor shall provide the following mandatory items for the implementation of the

new MSS:


of 32

1. The primary SAM-FS servers shall be highly available. This may be implemented through

the Sun cluster software. To minimize access time a copy of the data is written to disk

archive. This means that there is no need to access tape for reading data. The preferred file

system type, where archives are written to, is ZFS. The second copy of data is located in the

tape library in the main site. The third copy is written to a remote SAM-FS server connected

via LAN, and is configured as a “SAM remote server” attached to a second tape library.

2. The Contractor shall propose a complete migration plan. This plan shall be subject to the

approval of the Commission’s technical staff prior to implementation. The Commission

reserves the right not to execute this plan or only partially.

3. The backup/archive primary and secondary servers must be installed with the latest

Solaris release for mission-critical operation.

4. The Contractor shall provide an agent for cluster service failover. This agent should

enable failover of SAM-FS from one system to the other. The second cluster node could run

in standby mode.

5. The four (4) NAS clusters shall be backed up via NDMP directly through fibre channel. All

other servers shall be backed up via fibre channel SAN or Ethernet through the Master

Server or another Media Agent. The Contractor shall provide technical recommendations

and alternatives.

6. The Contractor shall provide licensing options for backing up the following clients with

Symantec Veritas NetBackup via LAN-less storage nodes and via backup server/LAN,

including multiplexing and multi-streaming options. (See under Table E: Server

Infrastructure) including:

a. Oracle Backup (RMAN integration, online application agent)

b. Oracle RAC Backup (RMAN integration, online application agent)

c. Backup to disk (NFS share or local Disk) via NDMP and standard Ethernet.

d. XEN (RHEL 5.2 and above, Backup the Image and/or integration in the Guest)

e. For each item, vendors shall provide details of backup/restore procedures as well as

corresponding explanations on advantages and disadvantages.

7. Implementation The implementation of the new MSS must be a turn-key solution and shall cover all

necessary configurations for all systems listed in Table E (Server Infrastructure in Appendix)

as well as all hardware and software listed under section 6.1 above. Planning, project

management, installation, implementation, migration, testing, rollout, training and

documentation shall form an integral part of the Work and each step of the Work shall be

approved by the Commission prior to implementation.

8. Licenses

Table E: Server Infrastructure on pg. 26-31 of this document contains legacy servers that

should be decommissioned in one (1) year, and new Linux servers, where backup could be

avoided. Therefore the Contractor shall provide the required licenses. The Commission

reserves the right to change the number of licenses to be purchased.


of 32

9. SAN design requirement

The current SAN layout needs to be redesigned to incorporate the new backup and archiving

system.

The Contractor shall propose a redesign or upgrade with aim of consolidating the fibre

channel network. Specifically the Contractor shall propose alternative solutions with varying

combinations of equipment. Each one should be described in detail with emphasis on the

benefits and disadvantages of each solution. A possible fibre channel network switch layout

is depicted on figure 6 below.

The following Table D lists the 19 Ethernet ports needed by the MSS equipment.

Table D: CTBTO SAN Configuration

Description SAN Ethernet

SAM-FS Cluster (2 Servers) 8 (4 each Fabric) 16

SAM Remote 4 (direct attached to Library) 2

Backup Master 4 (2 each fabric – better 8

GbFC)

4

Backup Media Agent 4 (2 each fabric) 4

Tape Library (Main) 16 2

Tape Library (Remote) 4 (direct attached to Server) 1

NAS NDMP Ports 16 (2 each node)

The current SAN Layout is a dedicated paired switch configuration with each switch

configured as an independent Fabric. A new design topology will be necessary to allow more

flexible utilization of tape drive resources within a redundant SAN fabric.

The current switch infrastructure is based on fully populated 6x Brocade Model 5100 and 2x

legacy Brocade 4100 switches. The new switch upgrade/redesign shall comply with the

following specifications:

a. Full fabric capable

b. 4 Gb/sec and 8Gb/sec capable

c. No oversubscription (i.e. non-blocking architecture)

d. All all ports populated with vendor recommended/supported Short Wave SFPs

e. Web based administration

f. Zoning (based on: WWNN, WWPN, Port)

g. Support for ISL trunking

h. Support for SNMP based performance and state-of-health monitoring. All

essential environment and performance related parameters must be retrievable

via SNMP. All corresponding MIBS have to be made available to CTBTO with the

system. Proprietary monitoring application may not be proposed.

i. Interoperability with the existing FC-Switch Infrastructure.

j. Hardware must fit in Sun Rack 900 or equivalent rack space.

k. The new switch topology may include (but not limited to) the following hardware

equipment:


of 32

1. 2 x Brocade DCX-4S (maximum 192 ports each)

2. 8 x BRCD DCX G, 48-port blade, R5 (four blades per DCX-4S)

All hardware units, required software, licenses, as well as option boards and other required

parts including services (i.e. migration plan) must be clearly

specified.

Figure 6: SAN Environment with FC Directors

6.2 ENVIRONMENTAL CONSIDERATIONS

The Contractor shall install the new MSS in the current Commission’s computer centre. The

Contractor shall take into consideration the physical specifications of the Commission’s

computer centre, as follows:

1. A maximum enclosure footprint of 4.85 x 1.25 meters (main site) and 1.54 x 1.25

meters (remote site).

2. A maximum height of 2.1 meters (room above for fan exhausting air is excluded).

3. An average floor loading of not more than 500 kg/m2 on a raised floor.

4. The maximum clearance for delivery is 2.20 meters high and 1.14 meters wide.

5. The maximum dimensions for a single part are: depth/width 1.00 meter, height 2.1

meters.


of 32

6.3 SERVICE CONSIDERATIONS

The detailed requirements for the provision of services of the new MSS are grouped into two

(2) categories: mandatory items and preferred items.

6.3.1 Mandatory items:

1. Installation and test plan:

a. The Contractor shall provide a detailed draft project plan encompassing the

delivery, installation, data migration and test of the new MSS. The Contractor

shall outline the execution of these tasks on a daily basis during the Work, and

shall include tentative time frame for performance and commencement of the

tasks. Information with regard to project phases and milestones is also expected.

This draft plan is a non binding document and is for review by the Commission

before the award of the contract to a Contractor.

b. Within four (4) weeks of signing the contract, the Contractor shall provide a more

detailed final project plan encompassing the delivery, installation, data migration

and test plan of the new MSS. The Contractor shall outline the execution of these

tasks on a daily basis during the Work, and shall include tentative time frame for

performance and commencement of the tasks. Information with regard to

milestones, phases, processes and work breakdown structure is also expected.

Essential project information such as project manager, team

members/contributors, project time line, etc. shall be included. The final plan will

be subject to the review and approval by the Commission. The Commission may

request the Contractor to make changes to the final plan before its

implementation.

2. Installation and implementation:

a. The Contractor shall deliver, install and implement the described systems

(hardware and software) according to manufacturer-specified standards as well

as any specific procedures as agreed upon with the Commission (including

hardware and software).

b. The Contractor shall include experienced, trained and certified personnel to

perform installation and implementation tasks.

c. The Contractor shall provide professional services for backup and restore

assessment.

3. Configuration support: The Contractor shall provide support, as and when required,

to the Commission’ specialists to configure the proposed solution.

4. Consulting services: The Contractor shall provide consulting services, as and when

required, for installation, implementation, and troubleshooting support.

5. Testing of the offered storage system (hardware and software): The Contactor shall

provide a test plan, which shall be subject to the Commission’s approval prior to

implementation. Preparation of test-runs and other test scenarios shall be done

together with the Commission’s specialists.

6. Onsite-Training for system operation and maintenance: The Contractor must

provide training for Commission’s personnel such as one (1) hardware engineer and


of 32

at least five (5) system administrators. The training shall be held in two (2) sessions

(separated by a few days) in order to avoid a situation whereby system

administrators and other technical staff are removed from their line duties all at the

same time. The training shall include content that allows system administrators to

operate, configure, monitor the system, and maintain (identify issues, trouble-shoot,

etc.). The content of the training shall be subject to the Commission’s approval prior

to implementation.

7. Documentation: The Contractor shall document the installation, configuration and

testing of hardware and software. This documentation shall be an integral part of the

work performed .

8. Installation of any additional hardware and/or software in existing systems: If

required, the Contractor, upon agreement with the Commission’s specialists, shall

install any additional components, hardware and software in existing servers. These

shall include temporary equipment and software licenses required for data

migrations. Any downtime involved should be arranged with the Commission.

6.3.2 Preferred items:

The Commission may request the Contractor to provide an Optional Recovery

Manual which should include a reference for each server configuration (stand-alone

RHEL server, RHEL clusters, RHEL virtual Machines and hypervisors, Solaris stand-

alone server, Solaris clusters, NAS Clusters).

6.4 EQUIPMENT TRADE-IN

The Contractor shall provide a trade-in for all equipment listed below. The Contractor shall

be responsible for the disassembly and pick up of all equipment indicated below:


Hardware

1 PowderHorn 9310 S/N 4000011845, Library Storage Module

2 Stand Alone LMU S/N 21600003008, Library Management Unit

3 LCU S/N 008000011922, Library Control Unit

4 Drive Library CA S/N 265000002949, 6 x StorageTek 9840 Tape

Drives & 4 x StorageTek T9940B Full Fabric

Drives

5 Sun Fire V240 S/N TN54340563, 2x1.5GHz CPU, 2GB Memory

6 Sun Fire E4900 S/N 0602MM2000, 4x1.35GHz CPU, 16GB

Memory, 1xCPU/Memory Board, 3xP/S,

3xFans, 2x System Controller, 1xPCI+I/O

Assembly (8 slots each), 2xPCI dual SCSI/dual

Ethernet Adapter, 2xSun Dual GigE+Dual SCSI,

3xDual-channel Differential UltraSCSI HBA,

4x2Gb PCI Dual FC Network Adapter, Sun Fire


of 32


Rack with 2 rack fan trays.

7 Sun StoEdge D240 S/N 0548BC1038, with 1 DVD, 3 x 73GB HD,

Connected to E4900

8 Sun StoEdge D240 S/N 0548BC103B, with 1 DVD, 3 x 73GB HD,

Connected to E4900

9 2 x BR4100 To be determined depending on SAN upgrade

and/or redesign.

10 6 x BR5100 To be determined depending on SAN upgrade

and/or redesign.

11 Optional service for the disposal

and destruction of old tapes

Vendors should offer the service as optional

part of their offer.

7. MASS STORAGE SYSTEM MAINTENANCE SERVICES

The MSS shall be offered with both hardware and software maintenance programs, which

shall ensure a continuous 7x24 operation for a period of not less than three (3) years after

its installation. An optional extension of the maintenance program beyond three (3) years

might also be presented. The maintenance program must include a guaranteed response

time for on-site service of not more than four (4) hours.

The Contractor shall provide:

1. Hardware Maintenance for no less than three (3) years.

a. Service coverage: 24 hours, seven (7) days a week including public holidays;

b. Telephone support: transfer to next available engineer;

c. On-site support: response time within four (4) hours;

d. Parts replacement: delivery and installation by technician within four (4)

hours after defective part is identified. Maintenance programs with response

times of 8 to 24 hours must be provided as an option.

2. Software Maintenance for no less than three (3) years.

a. Maximum response time of four (4) hours is required.

b. The Contractor (service provider) shall take responsibility for maintaining the

latest system firmware/software update as they become available.

3. For the Commission there shall be a single point of contact for both hardware and

software maintenance.

4. MTBF and MTTR figures must be presented for the system as whole or each

replaceable component (e.g. tape drive, hard disk, robotic arm, etc.). When possible,

these figures should be presented as “history” or “from calculations.”

5. The Commission reserves the right to not execute or change the quantity of any item

requested in the Terms of Reference.


of 32

6. The Contractor shall describe the content, terms, and conditions of all warranties and

guaranties of the hardware and software to be installed.

7. The Contractor must provide proof of vendor/manufacturer relationship.

8. WORK TASKS OVERVIEW

Due to the relatively long duration of time needed to install, implement, configure, test and

monitor the centralized MSS with minimal downtimes for the mission critical services, an

overview list of work tasks are outlined below for your ease of reference.

Work Tasks Overview

1. The Contractor shall deliver and install all hardware, including testing

hardware functionalities with appropriate diagnostic tools according to the

agreed upon final project plan.

2. The Contractor shall perform training courses for hardware and software after

discussion by the Commission.

3. The Contractor shall perform hardware diagnostics tests in the presence of at

least one (1) of the Commission’s hardware and systems specialists.

4. The contractor shall perform sand report satisfactory hardware functionality.

5. The Contractor shall install and configure all software and shall set up the

required functionalities.

6. The Contractor shall perform any required functional tests with satisfactory

results in the presence of appointed technical staff members from the

Commission.

7. The Contractor shall perform completion of data migration from the old to the

new MSS if such service option is exercised by the Commission.

8. The Contractor shall deliver the required documentation.

9. The Contractor shall provide with both hardware and software maintenance

program.


of 32

APPENDIX AND GLOSSARY

ACSLS Automated Cartridge System Library Software

CTBTO Comprehensive Nuclear Test-Ban Treaty Organisation

DVL Development LAN

FC-AL Fibre Channel Arbitrated Loop

IDC International Data Centre

IMS International Monitoring System

Infra Infrastructure network

MSS Mass Storage System

MTBF Meantime Between Failures

MTTR Meantime To Repair

OPS Operations LAN

RHEL5 RedHat Enterprise Linux 5

SAM-FS Sun StorageTek Storage Archive Manager

TST Testbed LAN


of 32

TABLE E: SERVER INFRASTRUCTURE

Note: This table includes the latest listing of servers at the time of writing and may change or vary in quantity,

type and specifications over time up until the awarding of contract.

No. Host

Name

LAN HW

Platfor

m

CPU/Co

res

CPU

Type

OS Cluster/

RAC

Oracle FC HBA Backup

Full

(GB)

Oracle

(GB)

Development LAN

1 eldey1 DVL Sun

E5500

6 US-II

400MHz

Solaris 9 No No No 4.18

2 flatey1 DVL Sun

E5500

6 US-II

400MHz


3 orac11 DVL Sun

V20Z

1/2core

s

Dual

Core

AMD

250

RH EL 5 No Oracle9

/10

Yes 0.00 132.00

4 dls0012 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5

XEN

Dom0

RH

Cluster

No Yes 5

5 dls0022 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5

XEN

Dom0

RH

Cluster

No Yes 5

6 dls0032 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5

XEN

Dom05

RH

Cluster

No Yes 5

7 dls0042 DVL Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5,

XEN

Dom0

RH

Cluster

No Yes 5

8 dls0052 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5 No No No 13

9 dls0062 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5 No No No 13

10 dls0072 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5 No No No 13

11 dls0082 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5 No No No 13

12 dls0082 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5 No No No 13

13 dls0102 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5 No No No 13

14 dls0112 DVL Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5

XEN

Dom0

RH

Cluster

No Yes 5

15 dls0122 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

2216

RH EL 5 No No No 13


of 32

No. Host

Name

LAN HW

Platfor

m

CPU/Co

res

CPU

Type

OS Cluster/

RAC


Full

(GB)

Oracle

(GB)

16 dls0132 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

2216

RH EL 5 No No No 13

17 dls0142 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

2216

RH EL 5 No No No 13

18 dls0152 DVL Sun

X4100

2/4

cores

Dual

Core

AMD

280

RH EL 5 No Oracle Yes

19 dlv0012 DVL XEN VM 4 cores RH EL 5 Hosted

by

cluster

No 13


by

cluster

No 13


by

cluster

No 13


by

cluster

No 13


by

cluster

No 20


by

cluster

No 13


by

cluster

No 13

Infrastructure LAN

26 iss0013 Infra Sun

V240

2 US-IIIi Solaris 9 No No No 3.03


E4900

4 US-IV

1350

MHz

Solaris 9 No No Yes 131.39

28 aaa Infra Sun

E220R

US-II

450MHz


29 aaa2 Infra Sun

Netra t1

No No No 9.08


V880

4 US-III+ Solaris

10

Sun

Cluster

No Yes 2,148.8

9


V880

4 US-III+ Solaris

10

Sun

Cluster

No Yes 987.27


V880

4 US-III+ Solaris

10

Sun

Cluster

No Yes 919.48


V880

4 US-III+ Solaris

10

Sun

Cluster

No Yes 196.88

34 alw004 Infra Sun

Ultra 40

M2

2/4core

s

Dual-

Core

AMD

2222

RH EL 5 No No No 22.59

35 clw001 Infra HP

Compaq

nc8000

1 Pentium

M

1.70GHz

RH EL 5 No No Yes 5.29

36 ctbtocs1 Infra Sun

E420R

2 US-II

450MHz


37 ctbtocs2 Infra Sun

E420R

2 US-II

450MHz


38 ctbtons11 Infra Sun

Netra

T1

1 US-IIi

440MHz



of 32

No. Host

Name

LAN HW

Platfor

m

CPU/Co

res

CPU

Type

OS Cluster/

RAC


Full

(GB)

Oracle

(GB)

39 ctbtons21 Infra Sun

Netra

T1

1 US-IIi

440MHz


40 ils0022 Infra Sun

X4100

2/4core

s

Dual

Core

AMD

275

CentOS

4.4

No No No 42.1

41 mls0022 Infra Sun

X4100

2/4core

s

Dual

Core

AMD

2216

RH EL 5 No No Yes 0


X4100

2/4core

s

Dual

Core

AMD

2216

Window

s 2003

Server

SE

No No No 15.52

43 jumpstart Infra Sun

T2000

Solaris

10

No No No 53.95


X4600

8/16

cores

Dual

core

AMD

8218

RH EL 5,

XEN

Dom0

RH

Cluster

No Yes 5


X4600

8/16

cores

Dual

core

AMD

8218

RH EL 5,

XEN

Dom0

RH

Cluster

No Yes 5


X4100

2/4

cores

Dual

core

AMD

2216

RH EL 5

XEN

Dom0

RH

Cluster

No Yes 5


X4100

2/4

cores

Dual

core

AMD

2216

RH EL 5

XEN

Dom0

RH

Cluster

No Yes 5

48 plv0032 Infra XEN VM 1core RH EL 5 No Oracle Yes 0.00 15.00

49 plv0042 Infra XEN VM 1core RH EL 5 No Oracle Yes 0.00 12.00

50 clv0012 Infra XEN VM 1core RH EL 5 No No No 5


49 clv0032 Infra XEN VM 1core RH EL 5 No Oracle Yes 0 12












PKI LAN

64 pkilab1 PKI Sun

Ultra 10

WS

1 No No No 3.35

65 pkilab2 PKI Compaq

Deskpro

EN K500

1 No No No 3.96

66 pkilab3 PKI Compaq

Deskpro

EN K500

1 No No No 2.17

Operation LAN

67 cmhost OPS Sun

E420R

2 US-II

450MHz

Solaris 9 No No Yes 95.25

68 bonaire1 OPS Sun 10 US-II Solaris 9 No No No 2.63


of 32

No. Host

Name

LAN HW

Platfor

m

CPU/Co

res

CPU

Type

OS Cluster/

RAC


Full

(GB)

Oracle

(GB)

E5000 248

MHz

69 garciosa1 OPS Sun

Netra

T1

1 US-IIi

440

MHz


70 kuredu1 OPS Sun

E5000

10 US-II

248

MHz


71 maui1 OPS Sun

E5000

10 US-II

248

MHz

Solaris 9 No Oracle Yes 8.47 1,350.0

0

72 moorea1 OPS Sun

E5000

6 US-II

248

MHz


0

73 niue1 OPS Sun

E5500

6 US-II

400MHz


74 pico1 OPS Netra

T1

1 US-IIi

440MHz


75 reunion1 OPS Sun

E5000

10 US-II

248

MHz


76 ols0012 OPS Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

77 ols0022 OPS Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

78 ols0032 OPS Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

79 ols0042 OPS Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

80 ols0052 OPS Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

81 ols0062 OPS Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

82 ols0112 OPS Sun

X4600

16 Dual

core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

83 ols0122 OPS Sun

X4600

16 Dual

core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

84 ols0132 OPS Sun

X4600

16 Dual

core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

85 ols0142 OPS Sun

X4600

16 Dual

core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

86 ols0152 OPS Sun

X4600

16 Dual

core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5


of 32

No. Host

Name

LAN HW

Platfor

m

CPU/Co

res

CPU

Type

OS Cluster/

RAC


Full

(GB)

Oracle

(GB)

87 ols0162 OPS Sun

X4600

16 Dual

core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

88 ols0172 OPS Sun

X4600

16 Dual

core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

Testbed LAN

89 akutan1 TST Sun

E420R

2 US-II

450MHz


90 askja1 TST Sun

Netra

T1

1 US-IIi

440MHz


91 fako1 TST Sun

E420R

2 US-II

450MHz


0

92 fogo1 TST Sun

E420R

2 US-II

450MHz


0

93 galeras1 TST Sun

E420R

2 US-II

450MHz


94 krafla1 TST Sun

Netra

T1

1 US-IIi

440MHz


95 merapi1 TST Sun

E5500

10 US-II

248

MHz


96 ruapehu1 TST Sun

E5500

8 US-II

248

MHz


97 tlw001 TST Sun

Ultra 40

M2

2/4core

s

Dual-

Core

AMD

2218

RH EL 5 No No No 68.51

98 tls0012 TST Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

99 tls0022 TST Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

100 tls0032 TST Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

101 tls0042 TST Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

102 tls0052 TST Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

103 tls0062 TST Sun

X4100

2/4

cores

Dual

core

AMD

275

RH EL 4 No No No 13

104 tls0082 TST Sun

X4100

2/4core

s

Dual

Core

AMD

280

Oracle

Linux,

(RH EL5)

RAC Oracle Yes 0 Will

replace

fako

fogo

105 tls0092 TST Sun

X4100

2/4core

s

Dual

Core

AMD

280

Oracle

Linux,

(RH EL5)

RAC Oracle Yes 0 Will

replace

fako

fogo


of 32

No. Host

Name

LAN HW

Platfor

m

CPU/Co

res

CPU

Type

OS Cluster/

RAC


Full

(GB)

Oracle

(GB)

106 tls0102 TST Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

107 tls0112 TST Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

108 tls0122 TST Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

109 tls0142 TST Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

110 tls0152 TST Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

111 tls0162 TST Sun

X4600

8/16

cores

Dual

Core

AMD

8218

RH EL 5 RH

Cluster

No Yes 5

IMS LAN

112 mss0011 IMS Sun

E420R

2 US-II

450MHz

Solaris 9 No Oracle Yes 14.58

IDC LAN

113 linosa1 IDC Sun

E220R

1 US-II

450MHz

Solaris 9 No Oracle Yes 13.68 10.00

114 lombok1 IDC Sun

E220R

1 US-II

450MHz


115 surtsey1 IDC Sun

E420R

2 US-II

450MHz


116 ctbto61 DMZ Sun

E420R

2 US-II

450MHz


117 ctbto206 DMZ Sun

X4100

2/4core

s

Dual

Core

AMD

280

RH EL 5 No Oracle Yes 0.00

NAS Clusters

118 ES-NAS 1 OPS HDS

Essen-

tial NAS

1300c

N/A Yes Yes/

NDMP

20.00

TB

Max.

119 ES-NAS 2 TST HDS

Essen-

tial NAS

1300c

N/A Yes Yes/

NDMP

20.00

TB

Max.

120 ES-NAS 3 DVL HDS

Essen-

tial NAS

1300c

N/A Yes Yes/

NDMP

20.00

TB

Max.

121 ES-NAS 4 Infra HDS

Essen-

tial NAS

1300c

N/A Yes Yes/

NDMP

20.00

TB

Max.

Table 1 - Detailed description of the server infrastructure. Please refer to notes1,2,3

for further details

1 Legacy Solaris server. To be replaced in one year time

2 Linux Server not currently under backup

3 Server part of the current Mass Storage System that will be replaced by the current proposal


of 32

ctbto mass storage system replacement 2009 and ......12 sam-fs 4.6.49, rev = 5.9.2006.02.23, license...

Documents