ETERNUS DX80 S2, DX90 S2, DX410 S2, DX440 S2 and DX8700 S2 › media › files › ... · Data Protection by Data Block Guard 8-byte check code is added to every 512-byte data to

ETERNUS DX80 S2, DX90 S2, DX410 S2, DX440 S2 and DX8700 S2

Common Features

Common Features ETERNUS DX S2 0 Copyright Fujitsu, Release May 2012

Contents (1)

Reliability RAID Functionality RAID and HDD Features Dynamic LUN Configuration Hard Disk Drives

Common Features ETERNUS DX S2 Copyright Fujitsu, Release May 2012 1

Contents (2)

Environmental Effort and Green Thin Provisioning Operability Miscellaneous


Reliability

Redundancy of DE Access Path Data Protection by Data Block Guard


Redundancy of DE Access Path Backend CM operation secures redundancy of DE access path In normal operation each CM

have a CM Expander that controls the disks in the DEs that are assigned to it CM Expander is a CM internal

component controlling the DE access

If one CM fails but the CM Expander is still functional, the surviving CM continues using the CM Expander of the failed CM to manage all disks

Copyright Fujitsu, Release May 2012 Common Features ETERNUS DX S2

℃

・・・・・・

DE

MP

EXP ℃

℃ ・・・・・・

DE

MP

CM#0

CE

CM#1 IA

Fault CM Expander continues to

be used (= Backend CM

is running)

EXP

IOM6 IOM6 IOM6 IOM6 EXP EXP EXP EXP

EXP EXP

IA panel

Controls DE access

Controls the other DE access

4

Copyright Fujitsu, Release May 2012

Data Protection by Data Block Guard 8-byte check code is added to every 512-byte data to

control data integrity on the disk and in the cache Guarantees consistency of all stored data

Common Features ETERNUS DX S2

WRITE READ

Apply Check Code

User Data

CC: Check Code

A0 A1 A2

A0 A1 A2 CC CC CC

（2）（3）

（3）

User Data

DISK

A0 A1 A2

A0 A1 A2 CC CC CC

A0 A1 A2 CC CC CC

Controller Module

Written Data

ETERNUS DX

Write Check Code

Verify Check Code

（1）

Cache ECC Protected

Verify & delete Check Code （4）

（2）

（1）

（3）

5

RAID Functionality

Supported RAID Levels Comparison RAID 5+0 and RAID 5 Improved Reliability and Performance with RAID 5+0 Further Improved Reliability with RAID 5+0 Comparison Between RAID 5, 5+0 and 6 Stripe Depth



Supported RAID Levels


RA

ID 5

[4+1

] R

AID

5+0

2x[

2+1]

R

AID

6 [4

+2]

7


Comparison RAID 5+0 and RAID 5 RAID 5+0 provides high performance and large capacity by

striping the data and parity blocks over two RAID 5 configurations This increases the data transfer rate in comparison to a standard RAID 5

configuration

RAID 5 RAID 5+0

Because RAID 5+0 consist in practice of two RAID 5 sets it

enables a RAID Group with double the capacity of RAID 5 RAID 5 can be set up from 2+1 up to maximum 15+1 disk configuration RAID 5+0 can be set up from 2 x (2+1 up to maximum 15+1)


RAID 5+0 (3D+1P) x 2

D3-1

D2-1

D1-1

P3

D2-2

D1-2

D3-2

P2

D1-3

D3-3

D2-3

P1

D3-4

D2-4

D1-4

P3”

D2-5

D1-5

D3-5

P2”

D1-6

D3-6

D2-6

P1”

Equivalent to RAID 5 (3D+1P) Equivalent to RAID 5 (3D+1P) 8 drives

Striping

P3 D3-1

D2-1

D1-1

D2-2

D1-2

D3-2

RAID 5 (3D+1P)

D3-3

D2-3

P1

P2

D1-3 4 drives

"D" = data area "P" = parity area

8


Improved Reliability with RAID 5+0 RAID 5+0 One drive from each of the RAID 5 sets could fail without loss of data After a single disk failure, RAID 5+0 has a shorter rebuild time than

RAID 5 with the same number of data disks • RAID 5+0 has less disks per RAID 5 set and therefore less data disks to use for

the re-calculation


D3-1

D2-1

D1-1

D3-2

D2-2

D1-2

D3-3

D2-3

D1-3

RAID 5 (6D+1P)

D3-4

D2-4

D1-4

P3

D2-5

D1-5

D3-5

P2

D1-6

D3-6

D2-6

P1 7 drives

Rebuild time will be long due to increase in number of drives


Shorter rebuild time than 6D+1P

D3-1

D2-1

D1-1

P3

D2-2

D1-2

D3-2

P2

D1-3

D3-3

D2-3

P1

D3-4

D2-4

D1-4

P3”

D2-5

D1-5

D3-5

P2”

D1-6

D3-6

D2-6

P1”

4+4 drives Equivalent to RAID 5 (3D+1P) Equivalent to RAID 5 (3D+1P)

Small number of drives RAID 5+0 (3D+1P) x 2

9


Improved Performance with RAID 5+0 RAID 5+0 writes faster than RAID 6 due to lower load in writing RAID 6 needs more calculation time during write for double parities RAID 5+0 can recover from double disk failure providing the disks fail

from different RAID 5 sets


RAID 6 (6D+2P)

D3-1

D2-1

D1-1

D3-5

D2-5

P1

D3-2

D2-2

D1-2

P3

D2-3

D1-3

Q3

D2-4

D1-4

D3-3

P2

D1-5

D3-4

Q2

D1-6

D3-6

D2-6

Q1 8 drives

Striping

RAID 5+0 (3D+1P) x 2

D3-1

D2-1

D1-1

P3

D2-2

D1-2

D3-2

P2

D1-3

D3-3

D2-3

P1

D3-4

D2-4

D1-4

P3”

D2-5

D1-5

D3-5

P2”

D1-6

D3-6

D2-6

P1”

8 drives

Faster data transfer with RAID5 (3D+1P) by striping

Equivalent to RAID 5 (3D+1P) Equivalent to RAID 5 (3D+1P)

- Two parity drives are created - High loads when writing data

Able to recover from two concurrent drive failures

Recover from single drive failure in each RAID 5 (3D+1P)


10


Further Improved Reliability with RAID 6 Tolerates two simultaneous hard disk failures in the same

RAID Group independent of the disk position RAID 5+0 can recover from double disk failure only providing the disks

do not fail in the same RAID 5 set This is advantageous when using large capacity hard disks that need a

long time for rebuild • For example Nearline SAS disks


RAID 6 (6D+2P)

D3-1

D2-1

D1-1

D3-5

D2-5

P1

D3-2

D2-2

D1-2

P3

D2-3

D1-3

Q3

D2-4

D1-4

D3-3

P2

D1-5

D3-4

Q2

D1-6

D3-6

D2-6

Q1

Uses two different parity blocks for the recalculation of missing data

8 drives

Able to recover from two concurrent drive failures

Striping

"D" = data area "P", "Q" = parity area

11

Comparison Between RAID 5, 5+0 and 6 (1) RAID 6 has advantages in reliability RAID 5 has advantages in data efficiency RAID 5+0 has advantages in write performance


Data efficiency

Write performance

RAID 5 RAID 6

Reliability

Write performance

RAID 5+0

RAID 5 RAID 6

RAID 5+0

*1; *2; *3 see next page

Reliability 1) Data efficiency 2) Write performance 3)

RAID 5 OK Very good Good RAID 5+0 Good Good Very good RAID 6 Very good Good OK

12

Comparison Between RAID 5, 5+0 and 6 (1) 1) Data Reliability

RAID 5: Is able to recover from single drive failure RAID 5+0: Is able to recover from double drive failure on the same RAID

set • One drive in each RAID array can fail

RAID 6: Is able to recover from double drive failure on the same RAID set

2) Data efficiency

When comparing equal sized data capacities

• RAID 5 (6+1) compared to RAID 5+0 (3+1) compared to RAID 6 (6+2)

3) Write performance

RAID 5+0 writes the two RAID 5 sets in parallel • RAID 5 (6+1) compared to RAID 5+0 (3+1)

Copyright Fujitsu, Release May 2012 Common Features ETERNUS DX S2 13

Stripe Depth Stripe depth can be set for RAID Group types 0, 1+0 and 5 Bigger stripe size improve random I/O performance by placing data

stripes more often within a single drive instead of across drives

14 Copyright Fujitsu, Release May 2012 Common Features ETERNUS DX S2

RAID5 (with default Stripe Depth) RAID5 (with expanded Stripe Depth)

Stripe size I/O request

RAID and HDD Features

Control of a Failed Disk Global and Dedicated Hot Spare Automatic Hot Spare Assignment S.M.A.R.T. Redundant Copy Triggered by S.M.A.R.T. Rebuild Priority Setting Quick Format Drive Patrol


Control of a Failed Disk Two different modes are supported Rebuild

• ETERNUS DX rebuilds the data of a failed drive from the remaining drives and writes it to a Hot Spare • When no Hot Spare is available

ETERNUS DX rebuilds the data after the defective drive is replaced

• Redundancy of the RAID Group is recovered after rebuild is completed

Copy Back • After redundancy of the RAID

Group is re-established, data is copied back from the Hot Spare to the replaced drive


HS

Disk replacement

Failed

Failed

Without redundancy

Recover redundancy

New

Without redundancy

Recover redundancy

Failed Disk replacement

New

Rebuild

Copy Back

Rebuild Failed

HS

16

Global and Dedicated Hot Spare Dedicated Hot Spare (DHS) disk Has to be assigned to a specific

RAID Group When a disk of a RAID Group with

a Dedicated HS fails, then this Dedicated HS is selected and used to rebuild the RAID Group

Global HS (GHS) Used by all RAID Groups When a disk in any RAID Group fails

and there is no Dedicated HS available, a Global HS is used to rebuild the RAID Group


GHS

DHS

DHS

: Global Hot Spare

: Dedicated Hot Spare for RAID Group D

: Dedicated Hot Spare for RAID Group E

ETERNUS DX S2

RAID Group D

RAID Group E DHS

DHS

Failed

RAID Group C

RAID Group B

RAID Group A GHS

17

Automatic Hot Spare Assignment (1) ETERNUS DX systems search for an appropriate HS disk and

assign it to each RAID Group Three search algorithms are used Search 1

• Take a Hot Spare disk with the same capacity and matching rotation speed as the failed drive

• Search through drive numbers in ascending order Search 2

• Take a Hot Spare disk with matching rotation speed and larger capacity • Priority is given to HS disks with similar capacity as the failed drive

Search 3 • Take a Hot Spare disk with matching rotation speed • Faster rotating drives have a preference


Automatic Hot Spare Assignment (2) This example shows the search algorithm for an automatic Hot

Spare disk assignment


Priority Assignment

Hot Spare Search criteria

2.5" 300 GB 10k rpm

2.5" 450 GB 10k rpm

2.5" 600 GB 10k rpm

3.5" 450 GB 15k rpm

3.5" 2 TB

7.2k rpm

Disk#008 (HS)

Disk#007 (HS)

Disk#005 (HS)

Disk#004 (HS)

Disk#006 (HS)

1 2 3 4 5

Same number of rotations

Same capacity


Similar capacity


Larger capacity

Different number of rotations

Faster

Different number of rotations

Slower

Search 1 Search 2 Search 3

Disk#000 Disk#001 Disk#002 Disk#003

RAID Group

2.5" 300 GB 10k rpm

2.5" 300 GB 10k rpm

2.5" 300 GB 10k rpm

2.5" 300 GB 10k rpm

Failure

19

S.M.A.R.T. Self-Monitoring Analysis and Reporting Technology Built-in mechanism of the disk drive collecting various information

• ETERNUS DX monitors the SMART data to recognize early signs of disk failure Makes it possible to identify failing disk drives before data redundancy in

the RAID Group is lost • Redundant Copy is triggered when certain SMART alerts occur or thresholds

are exceeded Disk drives are not detached immediately when a threshold is exceeded

• First the data of this flagged disk is rebuilt to a HS disk • The flagged disk is still member of the RAID set • Only after the data rebuild has completed the flagged disk will be detached • After disk replacement the data from the Hot Spare disk will be restored with

the Redundant Copy function


Redundant Copy Triggered by S.M.A.R.T. After a S.M.A.R.T error threshold is

reached, the disk is flagged and the Redundant Copy process starts A rebuild to a Hot Spare drive is

started automatically while redundancy is maintained

Flagged disk still a member of the RAID Group

The flagged drive is removed from the RAID Group and set faulty after the rebuild is completed

Redundant Copy started by S.M.A.R.T is interrupted immediately if another complete disk failure occurs and there are no further HS disks available


Remove the failed drive

Hot Spare drive RAID 5 (4+1)

Kee

p re

dund

ancy

Incorporate the HS drive to RAID and remove the drive

showing signs of failure

HS

RAID 5 (4+1)

Restore data from a failed drive and write it to HS

HS

RAID 5 (4+1)

21

Rebuild Priority Setting Rebuilding priority can be set per RAID Group Priority setting determines the I/O precedence between host I/O and

Copyback / Redundant Copy function


Rebuild priority setting I/O precedence Remarks

Low (default) Host I/O is prioritized If there is no host I/O then the setting has no effect. Settings Middle and High degrade host I/O performance while achieving faster full redundancy of the RAID Group.

Middle Rebuild is prioritized over host I/O

High Rebuild is 2 - 3.5 times faster than with setting Low

Quick Format Host can access Volumes of a RAID Group while formatting of

a Volume is in progress (1) ETERNUS DX first creates a format control table

• To manage formatted and unformatted blocks (2) After the format control table is created

• The LUNs become accessible from hosts • ETERNUS DX starts the physical format for the Volumes from the first block

and process all blocks sequentially (3) If ETERNUS DX receives "Read/Write I/O" to any unformatted block,

the block is first formatted and then access is allowed NOTE: ETERNUS will continue Quick Format after a power cycle


Offline Online E Read/Write Host view

Behavior of ETERNUS DX

Creation of format control table

Format Start Format Completed Read/Write Request One Point Format

Physical Format (Sequential)

Read/Write Completed

S

(1) (2)

(3)

23

Drive Patrol Drive Patrol improves hard disk reliability A background process reads

the data on drives If an error is detected, the faulty

data is recreated The recreated data is written to

another block on the same disk drive

Disks can be selected for Drive Patrol in ETERNUS Manager GUI by different categories, for example HS disks New installed disks Unused disks


Parity

RAID Group

Error detection

Check of drive media

Read out

RAID Group

D 1 D 2 P D 3 D 1

Write back

D 1

24

Dynamic LUN Configuration

Dynamic LUN Expansion Logical Device Expansion LUN Concatenation RAID Migration Dynamic LUN Mirroring Automated Storage Tiering (AST)


Dynamic LUN Expansion The ETERNUS DX Series is able to expand the capacity of

LUN (Logical Unit Number) without stopping the operation


Expand Logical device expansion

LUN Concatenation

LUN0 New

added drive Current

RAID Group RAID 5 (4+1)

LUN0 Unused area

Expand RAID Group by "Logical Device Expansion"

RAID Group now RAID 5 (5+1)

LUN0

Expand LUN0 capacity by "LUN concatenation"

RAID Group RAID 5 (5+1)

26

Logical Device Expansion Expand capacity (free space) of a RAID Group by adding

unused disk drives RAID level can be changed


Expands

Existing RAID Group RAID 5 (3+1)

Unused disks not assigned to any RAID Group

Same RAID Group RAID 5 (5+1)

27

LUN Concatenation LUN capacity can be expanded by using LUN concatenation Consolidates unused areas in the same or across multiple

RAID Groups for efficient use of drives NOTE: After LUN Concatenation it may be necessary to adapt

the Operating System and/or application to recognize the increased LUN size Maximum LUN capacity is 128 TB Minimum LUN capacity is 1 GB Maximum number of LUNs that can be concatenated is 16 Able to mix different RAID levels


RAID 5 450 GB x4

LUN1 600 GB

RAID 5 450 GB x4

Unused area 1.2 TB

RAID 5 450 GB x4

LUN1 600 GB

RAID 5 450 GB x4

LUN0 1.2 TB concatenate LUN2 600 GB

RAID Group 1 RAID Group 2

RAID-Grp1

RAID Group 2

LUN0 1.2 TB LUN2 with 1.8 TB

RAID Group 1

28

RAID Migration Enables data to be moved between different RAID Groups

without interrupting operation Migrate existing LUNs from a RAID Group to a different one Migration between different RAID levels RAID migration to expand LUN capacity Migration is transparent from server point of view DX80 S2, DX90 S2, DX410 S2 and DX440 S2 systems allow to migrate

concatenated LUNs


Migrate data to large capacity drives

Migrate data to a high reliable RAID level

LUN 0

RAID 5 300 GB

Unused 600 GB

RAID Group 1

RAID Group 2

Unused 300 GB

LUN 0 RAID 5 600 GB

RAID Group 1

RAID Group 2

RAID 5 600 GB

Unused 600 GB

LUN 0

RAID Group 1

RAID Group 2

Unused 600 GB

RAID 1+0 600 GB

LUN 0 Mirroring

LUN 0

RAID Group 1

RAID Group 2

29

Automated Storage Tiering (AST) Optimizes storage resources by moving data to the most

appropriate disk drives and thus reduces overall storage and management costs Optimal drive selection brings better performance and storage cost

reduction Automatic data relocation during operation enables management cost

reduction Data in a Volume is allocated in units of sub-LUN Requires

ETERNUS SF Storage Cruiser Optimization license


Automatic data relocation

Access frequency

High

Low

SSD Fastest

Online drives Fast

Nearline drives Large capacity & inexpensive

A

C

B

LUN

A: Usage (IOPS) has increased B and C: Usage has decreased

Minimizes response time

Reduces storage cost

Hard Disk Drives

Support for Wide Range of HDDs Hard Disk Drive Overview Discontinued and New HDDs Two Types of Data Encryption Self Encrypting Drives (SED) Data Encryption Using Firmware


Support for Wide Range of HDDs Eight drives must be installed in the ETERNUS DX8700 S2

when using the smallest configuration (4 DEs) Additionally one Hot Spare per Drive Enclosure

Enclosure backend connection is a SAS 2.0 interface with a speed of 6 Gbit/s Each hard disk drive has an embedded dual ported SAS 2.0 interface The different types of drives can be intermixed within the same enclosure


SSD SAS Nearline SAS

Hard Disk Drive Overview SAS disk drives for mission critical data Enterprise performance and reliability

• 15k rpm 3.5"; 300 GB, 450 GB, 600 GB • 10k rpm 2.5", self encrypting (SED) and

non-encrypting; 300 GB, 450 GB, 600 GB, 900 GB

Reliable Nearline SAS disk drives: cost-efficient capacity More reliability with Nearline SAS compared with SATA II

• 24-hours/days vs. 8-hours/day • 5 years warranty vs. 2-3 years

High capacity, low cost, suits backup and archiving 7.2 krpm 3.5"; 1 TB, 2 TB, 3 TB 7.2 krpm 2.5"; 1 TB Enterprise SSDs provide best I/O per cost ratio Excellent random read and writes, lowest latency Good for highest IOPS demands 2.5" and 3.5"; 100 GB, 200 GB, 400 GB


Discontinued and New HDDs


DX80S2 DX90 S2

DX80 DX90

DX410 S2 DX440 S2

DX410 DX440 DX8700 S2 DX8700

DX8400 SAS 15k rpm (3.5") 600 GB x x x - x -

450 GB x x x - x - 300 GB x x x - x -

FC 15k rpm (3.5") 600, 450, 300 GB - - - x - x SAS 10k rpm (2.5") - Without encryption

900 GB x - x - x - 600 GB x x x - x - 450 GB x x x - x - 300 GB x x x - x -

SED SAS 10k rpm (2.5") - With encryption

900 GB x - x - x - 600 GB x - x - x - 450 GB x - x - x - 300 GB x - x - x -

Nearline SAS 7.2k rpm (3.5") 3.0 TB x - x - x - 2.0 TB x x x - x - 1.0 TB x x x - x -

Nearline SAS 7.2k rpm (2.5") 1.0 TB x - x - x - Nearline SATA 7.2k rpm (3.5") 2.0, 1.0, 500 GB - - - x - x SSD (2.5" / 3.5") 400 GB x - x x x x

200 GB x x x x x x 146 GB - - - x - x 100 GB x x x - x - 73 GB - - - x - x

NOTE: Hard disks between generations are not compatible with each other. Hard disks for S2 models are compatible with each other.

Two Types of Data Encryption Disk encryption with SED (Self Encrypting Drive) No performance degrade compared to non-encrypting drives

Disk encryption by ETERNUS firmware Can be activated on a LUN basis Encryption algorithm can be chosen between Fujitsu's proprietary and

128-bit AES


Encrypt. Encryption

Plain data

Encryption

Encryption

Encryption

Encryption

Encryption

Encryption

Encryption

Encryption

Encryption

Encryption

Encryption

Encryption

Data removal protection

Encryption setting and management

Server A Server B Server C

35

Self Encrypting Drives (SED) Authentication key for SED encryption set up with ETERNUS

Web GUI Encryption method is 256-bit

AES (Advanced Encryption Standard) Data is fully encrypted in the

drives The encryption engine guarantees

full disk interface bandwidth without affecting the performance

Transparent for the end user and the ETERNUS DX system

Data is encrypted in units of RAID Groups


CM

Cache

SED

Authentication key

(hash value) Encryption key

(Encrypted data)

Authentication key

(plain data)

Data (Encrypted)

1. Authentication

Authentication key

Data (Plain data)

2. decryption

3. Encrypts/ Decrypts data

36

Data Encryption Using Firmware Selectable via ETERNUS Web GUI Fujitsu's unique encryption algorithm 128-bit AES encryption

Encrypts user data in units of LUN Both encrypted and unencrypted

data can exist in the same RAID Group

Possible to encrypt an existing unencrypted Volume All disk types can be encrypted


CM

Disk

Encryption key (Encrypted)

Encryption key

(plain data)

Master key

Data (Plain data)

1. Decrypts key

Data (Encrypted)

Encryption buffer

CACHE

Data (Encrypted)

2. Encrypts/ decrypts

data

37

Environmental Effort and Green

Power Saving Eco-mode Saving Power and Space with Latest Drives Visualization of Power Consumption and Temperature


Power Saving Eco-mode (1) Reduces power consumption When drives (RAID Groups) are used only a few hours per day

(for example for backup), Eco-mode is an effective way of saving power Drive spin down can be scheduled

• Drives are spun down if idle during the schedule time Drives are spun up automatically when accessed Can be managed with GUI or CLI of ETERNUS DX series


AM

12 on

off PM off

12 ・・・

・・・ ETERNUS DX

Data volume 600 GB SAS x 36

RAID 5 (5D+1P), 3 TB

All backup Volume drives are "ON" only for five hours a day Up to 15% power consumption reduction!!

Backup volume 1 TB Nearline SAS x 36

RAID 5 (6D+1P), 6 TB

5

39

Power Saving Eco-mode (2) Eco-mode allows the disks to be spun down for specified

periods and thus reduce the overall power consumption A schedule to spin up and spin down the disks can be set per RAID

Group


Power Saving Eco-mode (3) Eco-mode and MTBF Eco-mode has a very small impact on the MTBF value

• For example, Eco-mode setting for spinning up and down is 3 times per day on each disk • In 5 years Eco-mode makes the disk to spin up and down a total of 5475 times which is

far less than the given MTBF • The disk manufacturer gives an MTBF of 50.000 spin up/down cycles

How long does it take to spin up the disks? Typical spin up time is

• SAS disk => 15 sec • Nearline SAS => 20 sec


Saving Power & Space with Latest Drives ETERNUS DX systems use latest disk drive technology to

save power 2.5" disks have by nature lower power consumption, SSD disks very low Reduced physical size reduces system footprint and consequently data

center cooling costs


Pow

er c

onsu

mpt

ion

per d

rive

capa

city

Driv

e ge

nera

tion

About 50 % reduction in two years

Pow

er c

onsu

mpt

ion SAS

Nearline SAS

(year)

450 GB

1 TB

600 GB

2 TB

200 GB SSD

2009 2010

3 TB

400 GB

900 GB

100 GB

42

2011

Visualization of Power and Temperature ETERNUS SF Storage Cruiser (optional software) Enables administration users to monitor power consumption and ambient

temperature data and visualize statistic information of each operation • Real time monitoring • History log is available by day, week or year • One or a group of ETERNUS DX systems can be monitored


Storage management software ETERNUS SF

Storage Cruiser

Obtain power consumption and temperature of each

registered ETERNUS System

ETERNUS DX

43

Thin Provisioning

Introduction to Thin Provisioning Thin Provisioning Function Balancing Thin Provisioning Volume


Introduction to Thin Provisioning Simplifies the creation and allocation of storage capacity System can be configured future proof instead of being bound to

currently available physical storage Application can use capacity-on-demand from a shared storage pool Administrator can monitor and replenish each Pool, not each Volume

Storage perceived by the application is larger than the physically available storage Thin Provisioning (TP) Pool utilizes TP Volumes Several TP Pools can be created and used in parallel

TP requires a license key


Application 1

Application 2

Application 3 Allocated Allocated Allocated

Common TP

Storage Pool

Host Reported Capacity

Actual used

Capacity by Application

45

Thin Provisioning allocates volume capacity via virtual volumes Effective use of storage capacity reduces initial investment (start small) Possible to increase available storage capacity to suite changing

business needs • There is no need to add storage capacity per volume or application utilization

Thin Provisioning Function


2 TB is enough for the year ahead, but we will need 10 TB five years from now.

Server

Logical capacity matches future requirement

Virtual volumes (10 TB logical volume)

Write

Write

ETERNUS DX Physical capacity only matches current requirements

Physical drive (2 TB drive pool)

ETERNUS SF Storage Cruiser

Write data

New Threshold

No need to add/change systems even if physical

drives are added

After adding physical drives to the TP Pool

New added capacity

Add drives

Threshold alert

Threshold warning

46

Balancing Thin Provisioning Volume Assigns Thin Provisioning Volumes evenly across the RAID

Groups to remove hot spots by distributing the I/O access Done automatically without affecting normal operations


RAID Group #0 RAID Group #1 RAID Group #2

Volume #1 Volume #2 Volume #0 Volume #0 Volume #0

Volume #0

Thin Provisioning Pool - Without balancing

RAID Group #0 RAID Group #1 RAID Group #2

Volume #1 Volume #0

Volume #2 Volume #0 Volume #0

Volume #0

Thin Provisioning Pool - With balancing

Operability

ETERNUS Web GUI Similar ETERNUS GUI CLI Support

Common Features ETERNUS DX S2 48 Copyright Fujitsu, Release May 2012

ETERNUS Web GUI (1) Same look-and-feel for all ETERNUS DX S2 systems Intuitive operability Easy operation by just selecting an item and operation

• An example: Create a Volume • Menu (Volume) => Select category (Volume list is displayed) => Select "Create"


Select an item to be operated

Select category Status can be confirmed (select the item to be operated)

Main display

Only the items that can be operated are

displayed

Select action

Select from the menu

Please note the screenshot may look different depending on the firmware version.

ETERNUS Web GUI (2) Continued from previous page


Enter parameters

Click the "Create" button

Easy operation by

following information

Dedicated screen for operation is displayed

Operation is completed

Please note the screenshots may look different depending on the firmware version.

Similar ETERNUS GUI Similar GUI look-and-feel for each ETERNUS DX S2 system

and ETERNUS SF v15 onwards Simple consolidated management with integrated management software


ETERNUS SF Manager display ETERNUS DX Web GUI display

Status display Select an action Select an item Status

display Select an action Select an item

Please note the screenshots may look different depending on the firmware version.

CLI Support All DX S2 systems are able to use the same script with Entry

and Midrange models Use of scripting enables automated routine operations

• Provides ability to automate operational and setup routines Extensive command set provides similar functions as GUI Same commands for DX Entry, Midrange and Enterprise S2 models


GUI

CLI

＞xxxxxxx

CLI: Command Line Interface GUI: Graphical User Interface

ETERNUS DX

Operation terminal

Miscellaneous Email Notification Supporting SNMP, SMI-S, Syslog Access Authority Setting for Users Wake-on-LAN (WOL) Quality of Service (QoS) Redundant IP Host Affinity ETERNUS DX Advanced Copy Functions Improved Remote Copy Function


Email Notification When an event occurs, email can be sent by ETERNUS DX Without additional management software


Email

Without built-in Email functionality

ETERNUS DX S2

Event

Error

Error

ETERNUS DX

Mail server Management software

SNMP Trap or polling

of device status

Creating E-mail after analyzing

information from device

Email created by device Mail server

Operation other than Alarm can be triggered, for example Information, Warning, Error, Enhanced log contents for example Parts type, Installation positioning information

Administrator / Engineer

Administrator / Engineer

Note: The conventional technology can also be used

Email

54

Supporting SNMP, SMI-S, Syslog ETERNUS DX supports SNMP v1, v2c and v3

• Can be used to receive traps for ETERNUS information and notifications SMI-S Version 1.4

• Possible to manage ETERNUS DX by using storage management software complying with SMI-S

Syslog daemon complying with RFC3164, RFC5424 • Event logs can be sent to an external server • Any server that can receive messages that conform to RFC 3164 (the BSD

Syslog Protocol) can be used as the Syslog server, for example • Syslog daemon in standard Unix or Linux • Microsoft Operations Manager (MOM)


Access Authority Setting for Users Two default user accounts are available "root" with default password "root" "f.ce" with default password "<check code><serial-no. of DX>"

ETERNUS DX restricts the available administration functions per user account role to balance between what the particular user roles needs to do and is allowed to do RBAC (Role Based Access Control) Assigns roles and access authorities when creating an ETERNUS DX

user account


Role Available functional range Monitor Status display

Administrator All settings excluding maintenance work

Storage Admin Status display, RAID group settings, Volume settings, Host connection settings, etc.

Account Admin Status display, User account settings, Authentication settings, Role settings

Security Admin Status display, Security settings, Maintenance information

Maintainer All settings including maintenance work

56

Wake-on-LAN (WOL) WOL can be enabled for each LAN port of the ETERNUS DX

S2 systems with ETERNUS Web GUI or CLI A Magic Packet sent to DX LAN MAC address can be used to remotely

power on the ETERNUS DX system


Sends a Magic Packet ( XX-YY-ZZ-AA-BB-CC)

with WoL utility tool

XX-YY-ZZ-AA-BB-CC

Activate system remotely

57

Quality of Service (QoS) Host I/O performance of priority business

applications can be guaranteed by setting workload limits Allowed maximal I/O performance of lower

priority applications can be limited Can be set per Host and per Port


Server A Low priority

Server B High priority

ETERNUS DX

Without QoS

I/O performance

Server A

Server B Required performance

Required performance

Temporarily increased I/O requests

Not enough bandwidth available

With QoS

I/O performance

Server A

Server B Required performance

Required performance

I/O requests are limited

Bandwidth is secured

Redundant IP (1) Possible to set different IP addresses within the same subnet

to each CM When the role is changed between the CMs, the Master and Slave keep

their IP addresses (see next slide) Maximum of two IP addresses in two subnets can be set per CM


CM0 2)

MN

T

RM

T

FST CM1 2)

MN

T

RM

T

FST

Switch Switch

IP x.x.x.a IP x.x.x.b IP y.y.y.c IP y.y.y.d

59

1) The ETERNUS DX Entry models do not have an FST port. 2) On DX8700 S2 these ports reside in SVC0 and SVC1.

1)

1)

Redundant IP (2) When Master CM is changed IP Address of previous Master CM is taken over by new Master CM IP address of previous Slave CM is taken over by new Slave CM


FST

Master Slave ETERNUS DX

CM#0

Switch

CM#1

172.168.30.10 172.168.30.20

FST


CM#0

Switch

CM#1

Link Down 172.168.30.10

CM#1

FST


CM#0

172.168.30.10

Direct Connection

Connection using switch / hub

LAN Link Down

FST


CM#0

Switch

CM#1

172.168.30.10 172.168.30.20

60

NOTE: On DX8700 S2 the FST, RMT and MNT ports reside in SVC#0 and SVC#1.

Host Affinity Two different mapping procedures are configurable LUN Mapping = LUN is mapped per ETERNUS DX CA port

• Volumes that are mapped directly to a CA port or CA ports • Are accessible from each host that has physical access to that or those CA port(s) • A particular host cannot be prevented from access

HBA Mapping = LUN is mapped per HBA hardware address (WWPN / iqn / SASPN) • Volumes have to be grouped in the ETERNUS DX system

• Volumes are mapped to LUNs • These Volume groups are assigned to HBAs of one host or HBAs of different hosts via

CA ports • New Volumes can be added to an existing Volume Group

NOTE: One CA port can only support either LUN mapping or HBA mapping


Improved Remote Copy Function The ETERNUS DX90 S2, DX400 S2 and DX8700 S2 models

are able to use REC between different ETERNUS DX generations


Local site

ETERNUS DX90 S2

Backup site ETERNUS DX400 S2 ETERNUS DX8700 S2

ETERNUS DX8700 S2

DR site REC connections DX8700 S2

ETERNUS DX8700 S2 ETERNUS DX400 S2 series ETERNUS DX90 S2

FC, iSCSI

ETERNUS DX400/DX8000 ETERNUS 4000/8000

FC, iSCSI 1)

ETERNUS DX90 FC

ETERNUS6000 N/A

ETERNUS3000 FC 2)

1) S2 models require an iSCSI Remote Adapter (RA) to connect with the iSCSI RA of the earlier models.

2) Remote connection is available only for data migration. Both Stack mode and Through mode can be used as a transfer mode.

The connection matrix is applicable to both local site and backup / DR site.

Documents

ETERNUS DX80 S2, DX90 S2, DX410 S2, DX440 S2 and DX8700 S2 › media › files › ... · Data Protection by Data Block Guard 8-byte check code is added to every 512-byte data to