CML Mod03 StorageCenterAdministration RELEASE v3

7/28/2019 CML Mod03 StorageCenterAdministration RELEASE v3

1/87

Dell CompellentModule 3: Storage Center Administration


2/87

Compellent Storage Center Administration

Objectives After completing the administration section of this module,

you will be able to:

Identify Compellent Core and Application software Install the Storage Center application

Describe a day in the life of a Page

Describe the creation and use of volumes and volume folders

Describe the creation and use of servers and server folders

Perform volume to server mapping

Copy Mirror Migrate Volumes

Confidential2


3/87

Storage CenterSoftware

Confidential3


4/87

Compellent Storage Center Software Overview

Hardware

Licensed

Applications

Core

Software

Confidential4

LicensedApplicationsCoreSoftware


5/87

COMPELLENT STORAGE CENTER

Storage Center Core

Phone Home Virtual Ports (requires alicense)

Space Reclamation(Enterprise Manager)

Variable Page Sizes Copy-Mirror-Migrate Thin Write/Import

Cache Virtualization Boot from SAN

Fluid Data Architecture

Storage Center Applications

Data Progression Fast Track Dynamic Controllers

Data Instant Replay Remote Instant Replay Live Volume

Dynamic Capacity

Confidential5


6/87

Compellent Storage Center - Applications

Confidential6

DynamicCapacity

FastTrack

Tier 3Tier 3

Tier 1Tier 1

Tier 2Tier 2

Data Progression Data InstantReplay

Remote Instant Replay

Enterprise Manager

Original Replay

HQ DR

Dynamic Controllers


7/87

InstallingStorage Center

Confidential7


8/87

Storage Center Startup Wizard Installation Steps to install a Dell Compellent Array

What is an HSN and where do I get one?

Planning the IP network

Initializing via Command Shell

Completing the Storage Center Startup Wizard

Confidential8


9/87

What is an HSN? A hardware serial number assigned by Dell Compellent for

every controller

How does the HSN get assigned to a controller?

In dual controller configurations, how many licenses arerequired?

Peer controller vs Leader controller

Confidential9


10/87

IP Considerations Eth0 is the management IP

Eth0 for every controller

Dual controllers require a third management IP

Eth1 is heartbeat or IPC

Eth1 connects with small blue Ethernet cable

Eth1 IP is by default in range of 11.0.10.x

Ensure Eth1 IP are unique in dual controllers

Each iSCSI port needs an IP

Separate networks for management and iSCSI

Confidential10


11/87

Hardware Initialization Connect via serial port on controller

List of HSNs provided on PO or given by co-pilot

Licenses provided by HSN and distributed via co-pilot

Set HSN in command shell

Use label maker to label each controller on front and back foreasier identification

Confidential11


12/87

Record all IPs Run net show command to see HSN, eth0 and eth1

Record all IPs

Confidential12

Array

Name

Eth0

(management)Mgmt IP

(virtual group)

Eth1

(heartbeat)

Eth1Subnet

Mask iSCSI 1 iSCSI 2

iSCSI Contro l

Port

CML 1 10382/10383 172.20.20.41 192.168.16.41

HSN/SSN 10382 172.20.20.42 11.0.10.14 255.0.0.0 192.168.16.12 192.168.16.42

HSN/SSN 10383 172.20.20.43 255.0.0.0 192.168.16.13 192.168.16.43

CML 2 10376/10377 172.20.20.44 192.168.16.44

HSN/SSN 10376 172.20.20.45 255.0.0.0 192.168.16.15 192.168.16.45

HSN/SSN 10377 172.20.20.46 11.0.10.70 255.0.0.0 192.168.16.16 192.168.16.46

CML 3 10378/10379 172.20.20.47 192.168.16.47

HSN/SSN 10378 172.20.20.48 11.0.10.178 255.0.0.0 192.168.16.18 192.168.16.48

HSN/SSN 10379 172.20.20.49 11.0.10.155 255.0.0.0 192.168.16.19 192.168.16.49

CML 4 10380/10381 172.20.20.50 192.168.16.50

HSN/SSN 10380 172.20.20.51 11.0.10.242 255.0.0.0 192.168.16.21 192.168.16.51

HSN/SSN 10381 172.20.20.52 11.0.10.150 255.0.0.0 192.168.16.22 192.168.16.52


13/87

Step 1 End User License Agreement

Confidential13


14/87

Step 2 - License Key License file in format of snXXXXX where XXXXX is the HSN

number of the leader controller

Browse to license file and click Load License

Confidential14


15/87

Step 3a - Create Disk Folder

Confidential15


16/87

Step 3b Hot Spares


17/87

Step 3c - Disk Folder Attributes


18/87

Step 4a Add Controller


19/87

Step 4b New Controller IP


20/87

Step 5 Time Settings


21/87

Step 6a Management IP


22/87

Step 6b System Setup Cache


23/87

Steps 7, 8, 9 SMTP, Updates, User Setup Configure SMTP mail server

Select the method for Storage Center to handle updates

If no Internet connection, select No Phone Home

Set the User Session Timeout and enter email addresses

Default timeout is 2 hours


24/87

Step 10a - Configure IO Cards

Confidential24


25/87

Step 10b - iSCSI IP

Confidential25


26/87

Step 11a - Configure Ports

Confidential26


27/87

Step 11c iSCSI Control Port

Confidential27


28/87

Step 11d Configure Local Ports

Confidential28


29/87

Step 11e Configure FC Local Ports

Confidential29


30/87

Step 11h FC Fault Domains

Confidential30


31/87

Step 11i FC Fault Domain

Confidential31


32/87

Step 11 iSCSI Fault Domains

Confidential32


33/87

Step 11l Configure SAS Ports

Confidential33


34/87

Step 11m Apply Local Port Changes

Confidential34


35/87

Step 12 Generate SSL Certificate

Confidential35


36/87

Accessing Storage Center

Storage Center is web based GUI

Use IP entered in Step 6 as Management IP

Launch a browser & enter management IP

Default username is Admin

Default password is mmm

Both username and password are case sensitive

Confidential36


37/87

Configuring a Windows Host

Server Host has a NIC dedicated to the Compellent iSCSInetwork

Server Host has a second NIC for management of server Management IP on server should be static if using Enterprise

Manager

Confidential37


38/87

iSCSI and MPIO

Server hosts act as initiator so setup the Dell Compellent arrayas iSCSI target

Windows 2003 requires iSCSI initiator to be downloaded Windows 2008 requires iSCSI to be installed as feature

MPIO (multipath IO) needs to be installed

Confidential38


39/87

MPIO Properties

Confidential39


40/87

Dynamic BlockArchitecture

Confidential40



41/87

Dynamic Block Architecture

Metadata: Block Level Business Metrics

Creation, Access, and Modification time

Relative Frequency of Access

Disk drive type/RAID level

Sophisticated data movement engine

Improves Performance

Unique Patented Design

Benefits: Optimized data placement

All volumes span all drives

Higher performance

Change RAID levels anytime

No performance tuning

Simplified capacity planning

The only storage solution that virtualisesblocks inside the volume

R10

R5R6

SSD FC15K FC 10K SATA/SAS

R10

R5R6

Page pool

Oracle

DB

Exchange

SharePointFile

System

Application Volumes, e.g.



42/87

Conventional Storage System

Disk Virtualization

Compellent Storage Center

Confidential42


43/87

Core: Dynamic Block ArchitectureKey attributesrecorded at write

Data virtualized andmanaged at block level

More efficient management of data at disk level

Metadata

FC10K

RAID10

12:05:09

Confidential43


44/87

RAID Levels

Confidential44


45/87


46/87

RAID 0 Overview

H G F E D C B A

RAID 0 Volume

A B

E F

C D

G H

I J K L

M N O P

Confidential46


47/87

RAID 1 Overview

H G F E D C B A

RAID 1 Volume

A A

B B

C C

D D

=

Confidential47


48/87


49/87

RAID 10 Overview

RAID 10 Volume

H G F E D C B A

A A

C

E E

C

G G

B B

D

F F

D

H H

Mirror Mirror

Stripe Stripe

Confidential49


50/87

Dual Redundancy Additional mirror of data/parity increases availability

Protects against 2 drive failures in the same stripe set

Data Mirror Mirror

Data Mirror Mirror

Data Mirror Mirror

Data Mirror Mirror

DataDataData Data Parity Parity

RAID 6-10

RAID 10 Dual

Mirror

DataDataData Data Parity Parity

RAID 6-6

DataDataData Data

34%

overhead

20%

overhead

66%

overhead


51/87

Dynamic Capacity

Capacity presented to

servers can be

significantly larger

than the physicallyavailable storage

300GB 300GB 300GB

1.5TB Physical Storage

3 TB Dynamic Capacity Presented

300GB 300GB

1TB 1TB 1TB

Confidential51


52/87

Dynamic Capacity Concerns

300GB 300GB 300GB

1.5TB Physical Storage

300GB 300GB

2TB


53/87


Simplify management

Ideal for virtual servers

Independence from

drive type, interfacetype and RAID

No waste when storing data

Buy fewer disk drives

Save on energy and floorspace

Sophisticated datamovement engine

Set policies and let thesystem run

Optimized dataplacement

Block-level intelligence

Manages data inside thevolume

Tracks frequency ofaccess

Enables uniquefeature/benefits

Confidential53


54/87

Core: Fluid Data Architecture

Metadata for each block includes

Creation, Access, and Modification time

Frequency of access

Type and Tier of disk drive

RAID level

Corresponding volume

Confidential54


55/87

Volume

Page pool


Fluid Data Architecture the Page Pool

Collection of allocated and unallocated disk blocks

Maps pages to volumes

Maintains metadata

Default page size is 2MB (4,096 blocks)

Automated, Sophisticated Block Management

Change RAID levels by re-pointing pages

System manages data mapping acrossmultiple RAID levels

Individual files can span multiple drivetypes and RAID levels

Page Pool grows/shrinks as needed

Confidential55


56/87

Tier Level Redundancy

Each tier within the page pool has its own redundancyconfiguration.

The redundancy level of each tier can be modified to reflectthe levels of RAID protection desired for the tier.

Single Redundancy configures the tier for RAID10, RAID 5/5, and RAID5/9.

Dual Redundancy configures the tier for RAID10DM, RAID 6/6, and RAID6/10.

Levels can be modified on the fly.

Confidential56


57/87


Two types of pages, Accessible and Historical (Replay).

Accessible pages are pages that can be read or written by a server atthe current time.

Historical pages are read-only pages (set by Data Instant Replay).

Data Progression uses the accessibility to determine the class ofstorage a page should use.

A B C D E

C1

Confidential57

Fl id D A hi


58/87


Pages are identified into the following categories: Accessible Recently Accessed

These are the active pages the volume is using the most

Accessible Non-recently accessed Read-write pages that have not been recently used

Historical Accessible

Read-only pages the volume is using the most

Think Replays

Historical Non-recently accessed

Read-only pages that have not been recently used

Historical Non-Accessible

Read-only data pages that are not being currently accessible by a volume

That is, they have been aged due to a newer version of the page

System maintains these pages for recovery purposes and are placed on thelowest cost storage possible

Confidential58

C fi M V l D f lt


59/87

Configure My Volume Defaults

Confidential59


60/87

Page Lifecycle

P g Lif l


61/87

Page Lifecycle

How it all works together:

Storage system has two tiers of disk

Volumes are configured to use Recommended Storage Profile

Tier 1 is single redundancy; Tier 3 is dual redundancy

A single Replay occurs once per day and is retained for 3 days

The volume was created today

Volume size is 1TB

B C DAPAGES E

Confidential61

Page Lifecycle


62/87

TIER1

RAID10

TIER3

RAID6

TIER1

RAID5

C2 E1

Page Lifecycle

Expiration complete

A B C1 D E

READ A READ C2

Write C2

DATA

DIR

Changes

READ E1

Write E1

Time 1

Time 2

Confidential62

Page Lifecycle


63/87

C3 E2

Page Lifecycle

Recover a Replay

This becomes a new branch.

The new branch shares read-only blocks.

A B C1 D ETime 1

C2 E1

READ A READ C2

Write C3

DIR

DIR

Changes

READ E1

Write E2

Time 2

Time 3

DATA

DATA Recovery of Volume 1 -> Volume 2

DATA

Volume 1

Confidential63

TIER1

RAID10TIER3

RAID6

TIER1

RAID5

READ B

READ D

Page Lifecycle


64/87

Page Lifecycle

C3 E2

A B C1 D E

Time 1

C2 E1

READ A READ C2

Write C3

DIR

READ E1

Write E2

Time 2

Time 3

DATA

DATA

C4 E3

Volume 1 Volume 2

READ A READ C2

Write C4

READ E1

Write E3

Changes

Recovery View

Confidential64

Volume Configuration Best Practices


65/87

Volume Configuration Best Practices

The Combination of Data Progression, Fast Track, and Data InstantReplay provide a powerful, automated storage system.

Compellent recommends following our best practices to best

advantage these features.

Replay best practice

o All volumes should have at least one replay scheduled per day.

o Exception is log, swap, and pagefile volumes no need to progress this data.

Volume best practices

o Configure all volumes for the Recommended Storage Profile.

o This profile uses T1 R10 for writes and R5 and/or R6 across tiers for Replays.

o Exception is log, swap, and pagefile volumes suggest the High Priority (Tier1)

Profile.

Confidential65


66/87

Disk Folders

Confidential66

Disks and Disk Folders


67/87

Disks and Disk Folders

Disk Folder 1

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk Folder 2

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Disk

Volume

Volume

Volume

Volume

ClassifiedAssigned

Non-ClassifiedTemp

Confidential67


68/87

Volumes andVolume Folders

Confidential68

Volumes and Volume Folders


69/87

Volumes and Volume Folders

Database Volumes

Volume

Volume

Volume

Email Volumes

Volume

Volume

Volume

Volume

ManagerAdmin

Confidential69

Creating Volumes


70/87

Creating Volumes

1

2

Confidential70

Creating a Volume: Confirmation


71/87

Creating a Volume: Confirmation

Confidential71

Servers and


72/87

Servers andServer Folders

Confidential72

Servers and Server Folders


73/87

Windows Server Folder Netware Server Folder

Windows

EmailNetwareDatabase

Confidential73

Mounting an iSCSI Volume to a Server


74/87

g

Confidential74

Creating Server(s)


75/87

g ( )

Confidential75

Mounting a Fibre Channel Volume to a W2008Server


76/87

Right click on

unallocated partition

to get New SimpleVolume Wizard.

Disk Management Windows Server 2008

Confidential76

Mounting a Fibre Channel Volume to a W2003Server


77/87

Disk Management Windows Server 2003

Confidential77

Virtual Servers One to Many


78/87

3

Confidential78

Server Clusters Many to One


79/87

3

1

Confidential79

Lab 3.1:


80/87

CreatingVolumes,Servers, andMappings

Confidential80

Copy


81/87

pyMirrorMigrate

Confidential81

Copy


82/87

Confidential82

Mirror

Migrate

Copy a Volume


83/87

Once the volume copy is complete, the new volume is no longer updated by changes

made to the original volume.

Confidential83

Mirror a Volume


84/87

The destination volume cannot

be mapped to a server.

Confidential84

Migrate a Volume


85/87

Confidential85

Lab 3.2:


86/87

Copy a VolumeMirror a VolumeMigrate a Volume

Confidential86


87/87

Dell Compellent

Thank you

CML Mod03 StorageCenterAdministration RELEASE v3

Documents

Transcript of CML Mod03 StorageCenterAdministration RELEASE v3