Sie sind auf Seite 1von 17

DMX-3 Overview

3/3/06

DMX-3 Agenda
Current DMX-2 Review;
Architecture;
Overview;
Performance;
Teradata Configurations;
Cache Vault;
Space Allocation;
Coexistence;
5400 Design Center;
Contact Information and Additional Information;

Current EMC DMX-2 Teradata Models for 5400

EMC Model

DMX 1000 M2

DMX 2000 M2

Large Clique Config: Two DMX 2000 M2

NCR PID

6291-1002-7300

6291-2000-7300

6291-2000-7300

Disks

73GB 15K RPM

73GB 15K RPM

73GB 15K RPM

MPP: 1 or 2 nodes

MPP: 2, 3, or 4 nodes

MPP: 5,6,7 or 8 nodes

Raid-1 Only

Raid-1 Only

Raid-1 Only

MP-RAS & Windows

MP-RAS & Windows

MP-RAS & Windows

96

192

384

48 / Node

48 / Node

48 / Node

Teradata Use
Raid
Operating Environment
Maximum Teradata disks
Design Center Configuration

EMC DMX -3 Architecture


Disk Cabinet

Up to 120
Disks

Disk Cabinet

Up to 120
Disks

System Cabinet

Host Director
Boards
(i.e. FA)
Up to 8

Disk Cabinet

Disk Cabinet

Up to 120
Disks

Up to 120
Disks

Up to 120
Disks

Up to 120
Disks

Cache Director
Boards Up to 8

DD Pair

DD Pair

Disk Director
Boards Up to 8

DD Pair

Up to 120
Disks

DD Pair

Up to 120
Disks

Configurations are referred to in the following format:


A X B X C where
A = Number of Host Director Boards (FAs)
B = Number of Cache Director Boards
C = Number of Disk Director Boards (DAs)

DMX-3 Product Overview


Second-generation Direct Matrix
Architecture
> 128 GB/stwice the matrix
bandwidth of Symmetrix DMX-2
Eight 1.3 GHz PPC processors per director
> Delivers up to twice the IOPS and
MB/s of the Symmetrix DMX-2
director
Up to 512 GB Global Memory (256 GB
useable)
> Redundant Global Memory and
PowerVault protection
Symmetrix DMX-3 incremental scalability
> Online expansion of capacity and
performance as requirements
increase
Minimum configuration consists of a single
System bay and a single Storage bay
EMC Model

Target GCA
MP-RAS: March 06
Windows: May 06
Linux: April 06 (>4 Node
release)

Storage bay

System bay

Storage bay

System bay

Storage bay

DMX-3

Large Clique Config: DMX-3

Disks

73GB 15K RPM

73GB 15K RPM

Teradata Use

MPP: 1- 4 nodes

MPP: 5 - 8 nodes

Raid-1 Only

Raid-1 Only

Raid
Operating Environment

MP-RAS & Windows WS 2003


& Linux SuSE

MP-RAS & Windows WS 2003


& Linux SuSE

Power Options

Three Phase Delta or WYE

Three Phase Delta or WYE

Maximum disks

240

480

40 Disks / Node
17% reduction from DMX-2

40 Disks / Node
17% reduction from DMX-2

5400 Design Center


Configuration

EMC DMX -3 Architecture

Disk Cabinet

Up to 120
Disks

Disk Cabinet

Up to 120
Disks

System Cabinet

Host Director
Boards
(i.e. FA)
Up to 8

Disk Cabinet

Disk Cabinet

Up to 120
Disks

Up to 120
Disks

Up to 120
Disks

Up to 120
Disks

Cache Director
Boards Up to 8

DD Pair

DD Pair

Disk Director
Boards Up to 8

DD Pair

Up to 120
Disks

DD Pair

Up to 120
Disks

4x8x8

4x8x4

Performance
Data Rate vs. Number of Active RAID-1 Disk Pairs

6.3 MB / sec

ys
ra
Ar

4.7 MB / Sec
5

3
ys
rra
2A

y
ra
Ar

5.3 MB / Sec
5.4 MB / Sec

ys
ra
Ar

DMX-3 4X 8X 8
DMX-3 4X 8X 4

ys
ra
Ar

4.7 MB / Sec
5.4 MB / Sec

y
rra
1A

Active Raid-1 Disk Pairs

2.5 MB / Sec

DMX-3 Teradata Configurations


Confi
guratio
n

# of
Node
s
5400
or
5450

1-2

3-4

5-6

7-8

Choosing
Calculator
Tool
Selections
FAxMemx
DA

FA
Fibre
Channel
Director

Memory
/
Cache
Director

DA
Pair
Disk
Director
(back
end)

Syste
m
Cabin
et/
Bay

Stora
ge
Cabin
et/
Bay

Storage
Cabinet
Drive
Enclosu
re

Syste
m
Cabine
t/
Bay
Power
Modul
e

Pow
er
cabl
e

Three
Phase
Delta
AC
conne
ctor

Fibre
Channel
Cables

Max #
Terad
ata
drive
s

SF
S
dri
ve
s

Sp
are
s
dri
ves

36

116

4x
16GB

4 per
node

F301

F301

F3
02

F3
02

F503

F402

F601

3001
or
3002
*

F101
or
F102
*

F201

F090

F07
1 or
F07
2*

F081

F948

120

236

6x
16GB

4 per
node

F301

F301

F3
02

F3
02

F503

F402

F602

3001
or
3002
*

F101
or
F102
*

F201

F090

F07
1 or
F07
2*

F081

F948

200

354

8x
16GB

4 per
node

F301

F301

F3
02

F3
02

F503

F402

F603

3001
or
3002
*

F101
or
F102
*

F201

F090

F07
1 or
F07
2*

F081

F948

280

474

8x
16GB

4 per
node

F301

F3
02

F3
02

F604

3001
or
3002
*

F101
or
F102
*

F090

F07
1 or
F07
2*

F081

F948

Min #
Data
drive

2x4x2

2x6x4

4x8x6

4x8x8
F301

(front
end)

F503

F402

F201

DMX-3 Teradata Clique Configurations


System Cabinet

Disk Cabinet

2 - Host
Director
Boards

Cache
Director
Boards
4 x 16GB
Disk
Director
1-Pair
DD
Pair

Up to
120
Disks

Disk Cabinet

Up to
120
Disks

Disk Cabinet

Up to
120
Disks

Cache
Director
Boards
8 x 16GB

Up to
120
Disks

Disk
Director
3-Pairs

Up to
120
Disks

Config #4
7-8 Node
Large Clique
Configuration

2 - Host
Director
Boards

Cache
Director
Boards
6 x 16GB

Up to
120
Disks

Disk Cabinet

4 - Host
Director
Boards

DD
Pair
DD
Pair
DD
Pair

Config #3
5-6 Node
Large Clique
Configuration

System Cabinet

Config #2
3-4 Node
Configuration

System Cabinet

Disk
Director
2-Pairs
DD
Pair
DD
Pair

Config #1
1-2 Node
Configuration

Each configuration has been


designated for a specific
number of nodes. Based
on the maximum number
of disks in these
configurations, it is
technically possible to
support more nodes
but not with acceptable
performance. The number
of nodes specified should
not be exceeded.

Up to
120
Disks

System Cabinet
4 - Host
Director
Boards

Disk Cabinet

Up to
120
Disks

Cache
Director
Boards
8 X 16GB

Up to
120
Disks

Disk
Director
4-Pairs
DD
Pair
DD
Pair
DD
Pair
DD
Pair

Disk Cabinet

Up to
120
Disks

Cache Vault
Cache Vault Area on disk utilized by EMC for quickly flushing
its cache in the event of a power failure;
EMC cache sizes have become so big that they no longer have
enough battery power to write out the entire cache contents
block-by-block to their proper location in the event of a power
failure.
The cache vault is an area on disk where EMC can use large
block sequential I/Os to quickly write out the contents of
cache.

> Prior to EMC beginning its cache flush, Teradata is given 3 minutes
to flush its cache;
> 5 GB per disk on the first 32 disks per DA-Pair (per each 120 disk
module) See next slide
> In a Teradata system, 5 GB will effectively be lost on each disk
due to parallelism;

Vault Drives

Up to 120
Disks

5GB from 1st 32


disks used for
cache vault

Up to 120
Disks

Up to 120
Disks

Cache Director
Boards Up to 8

Disk Director
Boards Up to 8

DD Pair

Up to 120
Disks

Host Director
Boards
Up to 8

DD Pair

5GB from 1st 32


disks used for
cache vault

System Cabinet

DD Pair

Disk Cabinet

DD Pair

Disk Cabinet

Disk Cabinet

Disk Cabinet

5GB from 1st 32


disks used for
cache vault

Up to 120
Disks

Up to 120
Disks

5GB from 1st 32


disks used for
cache vault

Up to 120
Disks

Up to 120
Disks

Space Allocation
DMX-2 2000
18 GB
18 GB

DMX-3
5 GB

34 GB

73 GB

18 GB

34 GB

18 GB
36 GB

73 GB

LUN

Mirror

5 GB

5 GB

LUN

Mirror

LUN

Mirror

Mirror

LUN

Mirror

LUN

Mirror

LUN

34 GB

DMX-2
> 73GB disks are divided into four 18GB partitions;
> Each disk has two 18GB LUNs (PDisks);
DMX-3
> 73GB disks are divided into one 5GB vault partition plus two 34GB partitions;
> Each disk has one 34GB LUNs (PDisk);
Why does DMX-3 use larger LUN sizes?
> EMC now supports larger LUN sizes;
> With higher capacity arrays, larger LUNs are required to keep total LUN count below
256 per port (MP-RAS limit);

Impact of Vaulting on Space Allocation


73GB disks are effectively 68GB in the Teradata
environment; (6.8% reduction in usable storage)
Choosing calculator will calculate MaxPerm based on
68GB drive capacity;
Coexistence:
> Balancing capacity between old cliques with DMX-2 and new
Cliques with DMX-3 will take some extra attention (See
following slides for details);

DMX-2 and DMX-3 Coexistence Example


Example:
> Old clique 5400 with DMX-2000
> New clique 5400 with DMX-3
Old Clique
4 x 5400

DMX2000
192 x 73GB disks
(for Teradata)
MaxPerm =
6366 GB
199 GB / AMP

Options with DMX-3


New Clique
4 x 5400

Option #1
Old AMPs capacity
Will be reduced by
12GB (6%)

DMX-3
192 x 73GB disks
(for Teradata)
MaxPerm =
5971 GB
187 GB / AMP

New AMPs capacity


will be reduced by
19GB (8.7%)

New Clique
4 x 5400

Option #2

One extra disk


Per AMP
DMX-3
224 x 73GB disks
(for Teradata)
MaxPerm =
6966 GB
218 GB / AMP

Coexistence Choice
Due to the space requirements for the DMX-3 Vault, balancing the
capacity between old cliques with DMX-2 and new cliques with DMX-3
will not be possible without some amount of unused capacity.
Space / Cost optimization depends on size of the old portion of the
system versus the new;
> Option #1: Configure with equivalent disks between old and new cliques;
Approximately 6% of old system capacity will no longer be available after
the coexistence portion of the system is configured (No existing data will
be lost); Best option when the size of the expansion is larger than the
existing system and data space is not an issue.
> Option #2: Configure with one extra disk per AMP on the new clique.
Approximately 8% of new capacity will be inaccessible; Best option when
the existing system is large and the expansion is small.

Choosing calculator will accurately show capacity in coexistence


environment.

Design Center Recommendations - EMC


5400 w/DMX-2

5400 w/DMX-3

Disk Cabinet

System Cabinet
2 - Host
Director
Boards

5400
Node 4

192 Disks
per array

5400
Node 4
5400
Node 3

5400
Node 3

5400
Node 2

5400
Node 2

5400
Node 1

40 73GB
15K per
node
160 Disks
per Array

Cache
Director
Boards
6 x 16GB

Disk
Director
2-Pairs
DD
Pair
DD
Pair

48 -73GB
15K per
node

5400
Node 1

Per Clique:
MaxPerm:
TPerf:
PerfC:

1592 GB / Node
9.15
.57

Per Clique:
MaxPerm:
TPerf:
PerfC:

1244 GB / Node
10.23
.82

Dramatic PerfC improvement with DMX-3 due to fewer disks per node required (more
bandwidth delivered per disk) and cache vaulting which effectively caps 73GB disks at
68GB.

Contact Information and


Additional Information
Contact Information:
> Ron Yellin
> Patsy Martin

(858) 485-3116
ron.yellin@ncr.com
(858) 485-2618
patsy.martin@ncr.com

Additional Information:
Ordering and Configuration Information
NCR 6293: EMC Disk Array Symmetrix DMX-3
https://www.my.ncr.com/cgi-bin/ncr4me/ncr4me/ep/assetDetail.do?assetID=KM007504

Das könnte Ihnen auch gefallen