3Par Customer Training Inform (T and F Class) GOOD Document

8/13/2019 3Par Customer Training Inform (T and F Class) GOOD Document

1/30

Copyright 2010 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. HP Confidential

October 2010

3PAR INFORM OS


2/30

HP Confidential | October 20102

Course Objectives

At the end of this presentation the student should be able to :

Understand InFormOs Software Architecture

Understand InFormOS RAID concepts

Understand concepts of InServ Chunklets

Understand InFormOS Logical Disks (LDs)

Understand InFormOS Virtual Volumes


3/30


PD (Physical Disk)

Chunklet

Mesh-Active Cluster

Wide Striping

Virtual Volume

Set Size

Step Size

Virtual LUN

CPG (Common Provisioning

Group)

Region

Host

VV Set, Host Set, (AutonomicGroup)

KEY CONCEPTS AND TERMS*

*There will be a quiz.


4/30


Gen3

ASIC

Mixed Workload

Zero Detection

Mesh Active

Fast RAID 5 / 6

InForm

fine-grained

OS

Performance

Instrumentation

Utilization

Manageability

Autonomic

Policy

Management

Self-Healing

Self-Monitoring

Self-Configuring

Self-Optimizing

Utility Storage

Thin

Provisioning

Virtual

Domains

Dynamic

Optimization

System

Reporter

Virtual

Copy

Remote

Copy

Thin

Conversion /

Persistence

Adaptive

Optimization

F-Class T-Class

ARCHITECTURAL DIFFERENTIATION:

PURPOSE BUILT


5/30


SIMPLIFIED STORAGE AND SERVER

PROVISIONING

3PAR Rapid Provisioning Seconds to provision storage with no pre-

planning

Self-configuring and auto load-balanced

storage volumes

Labor-intensive and careful planningeliminated


6/30


PHYSICAL DISKCHUNKLETS (256 MB/1 GB*)

C = 256 MB Data Chunklet

SC = 256 MB Spare Chunklet

C C

C C C C

Physical Disk

SCSCSC

Each InServ Physical

disk is initialized with

data chunklets andspare chunklets


7/30


CHUNKLETS ARE AUTOMATICALLY GROUPED

BY DRIVE ROTATIONAL SPEED

SATA (Nearline) disks are usually

the biggest group(depends on

configuration)

Fibre Channel disk chunklet group

Solid State disk chunklet group is

smaller and reserved for high-value

I/O


8/30


SW ARCHITECTURE: RAPID, TAILORED

PROVISIONING...

Chunklets

Physical drives broken

into fine-grained uniform

256 MB chunklets

Common Provisioning GroupsAutomatically grows by creating Logical

Disks (LDs) as needed (parameters set

by the CPG policies)

Virtual VolumesCreated and exported in twocommands15 seconds with

no pre-planning

Limit

Warning

Limit

Warning

50GB SSD, 300 &

600GB FC, 2TB NL256 MB to 16 TB

Highest performance

High resiliency

Higher cost

Medium performance

Highest resiliency

Lower cost

RAID 0, RAID 10, RAID 50

(1:2-8), RAID 60 (2:6, 2:14)

Autonomic

Group

LDLD

LDLD

LD

LD

Drive

Chassis


9/30


3PAR WIDE STRIPING:

COMPLETELY AND FINELY LOAD BALANCED

8GB LUN spread across 64 disks (RAID 10)8GB LUN spread across 4 disks (RAID 10)

Channel Directors

Cache Boards

Disk Directors

Market LeadingMonolithic Array InServ T400Storage Server


10/30


WHY ARE CHUNKLETS SO IMPORTANT?

Same drive spindle can service many different LUNS, and many

different RAID types at the same time Enables array to be managed by policy, not by administrative

planning

Drives up utilization rate of the disks (no leftover space)

Improved High Availability and Sparing

Enables easy mobility between physical disks, RAID types,

service levels


11/30


HIGH AVAILABILITY + HIGH UTILIZATION RATE

3PAR Availability Level Concepts:

HACage HAMagazine

HAPort

These are policies by which the system lays out RAID sets in order to protect against

hardware failures.

The default configuration will always be the safest but can be overridden by an

administrator.

Default HA level cage unmatched in industry.


12/30


13/30


WHAT IS A REGION AND HOW DOES IT MAP TO A

VIRTUAL VOLUME

Logical Disks (LDs)

Mapped to Volumes via 128MB Regions

Mapped to Drives via Raidlets (sets of

Chunklets with a given RAID and media

type)

A mapped Region can move to another

LD per Adaptive Optimization policy

Host

Virtual Volumes

of any size (256MB to 16TB each)

Physical Disks

broken into Chunklets (256MB each)

Host Servers

See LUNs (exported Virtual Volumes)

Infrequently

accessed portion

of Volume

mapped to a

Region of Tier 2

Logical Disk

Frequently

accessed

portion of

Volume

mapped to aRegion of Tier 0

Logical Disk

Regions mapped

to Raidlets of

the Logical Disk

2 Raidlets

(RAID 1) 4 Raidlets

(RAID 5, 3+1)

SSD SATA


14/30


HOW A VOLUME MAPS FROM VV TO CHUNKLET


15/30


COMMON PROVISIONING GROUPS (CPG)

CPGs are FUNDAMENTAL to administering 3PAR.

CPGs automatically provision Logical Disk capacity on demand CPGs are the combination of a RAID type and a drive type which

equals SERVICE LEVEL and AVAILABILITY LEVEL.

CPGs have many functions:

They are the policies by which free chunklets are assembled into logical disks.

They are a container for existing volumes and used for reporting

They are the basis for service levels and our optimization products.


16/30


17/30


3PAR RAID LEVELS

Inform OS can assemble RAID sets (RAIDLETS) into RAID 00,

RAID 10, RAID 50, RAID 60 Data to Parity Ratios (3PAR Set Size)

Raid 10 mirror or 3-way mirror

Raid 50 from 2+1 to 8+1 (HA-magazine)

Raid 60 at 6+2 or 14+2 (protect against double disk failure with

same capacity tradeoff of RAID 50


18/30


3PAR RAID 10 CONCEPTS

RAID 10 is mirrored data

Data is written as paired chunklets

Each chunklet on the RAID set is on a different physical disk

Setsize = 2

Default size (RAID 1)

Usable space = 256MBC C


19/30


3PAR RAID 5 CONCEPTS (1 OF 2)

RAID 5 uses parity to reconstruct data

RAID 5 uses a setsize equal to number of drive cages (shelves) bydefault to guarantee cage level HA.

Setsize = 4 (3+1)

Default size (RAID 5)

Usablespace = 768 MB(3*256)

C C C p

Setsize = 6 (5+1)

Usable space = 1280MB

(5*256)

C C C c c p

C C p C

Cp CC


20/30


3PAR RAID 5 CONCEPTS (2 OF 2)

C C C c c pCCC

Setsize = 9 (8+1)

What is the usable space for this setsize?

Usable space = 2048 MB (8*256)


21/30


3PAR RAID MULTI PARITY (MP) CONCEPTS

RAID MP uses parity (double paritycan deliver data in a double

disk failure) to reconstruct data and performed in the ASIC XORengine

RAID MP only supports two setsizes ( 8 and 16)

The default set size of 8 has the same data to parity ratio as the

default RAID-5 set size of 4 -- 3:1 in both cases.


22/30


2222

USAGEMEANING OF -HA CAGE FOR RAID MP

The system defines "-ha cage" as "will tolerate the failure of

ONE cage. This means: Up to two chunklets are allowed to share the same cage.

The default R6 -ha cage set size 8 requires 4 cages per node-pair, just like

the default R5 set size 4.

If 8 cages are available, the layout will use one chunklet per cage.

The same rules apply to -ha mag up to two chunklets are allowed per magbut the system will place only one chunklet per mag if possible.


23/30


2323

VIRTUAL VOLUME STEP SIZE

Step Size is The number of contiguous bytes that the

system accesses before moving to the next chunklet. Step size varies based on RAID type.

R10 default is 256K

R50 default is 128K

R60 default varies by Set Size.

Step size is how we avoid hotspots on the back end disks!

NOTE:Administrators can override defaults, but not recommended


24/30


INSERV HA: BUILT FOR THE DEMANDS OF

MULTI-TENANCYTraditional Arrays 3PAR InServ

--- RAID 1 Group ---

--- RAID 1 Group ---

---R1

Raidlet---

---R1

Raidlet---

Shelf-

dependent

RAID

No access

to dataShelf (chassis) Shelf (chassis)

Shelf-

independent

RAID

Data access

preserved

Drive

Shelf

(chassis)

yTraditional Cache

Mirroring

Poor

performance

(write-thru mode)

Persistent

Cache

Mirroring

Consistent

performance

(no write-thru

mode) **

Controller

Node

Disk

Drive

Few-to-one rebuild

Hotspots* & prolonged

rebuild exposure

Many-to-many rebuild

Non-disruptive

rebuilds in the time

spare

drive

spare chunklets

Component


25/30


ADAPTIVE OPTIMIZATION FEATURES, BENEFITS

Optimize

Cost/Performance

Sub-volume, bi-directional

data optimization

Application specific vs.

global thresholds

Support for both Thin and

Fat volumes

Control Timing, QoS

Scheduled movement

Vary usage limits and tier

definitions by application

Minimize Technology Risk

Existing sub-volume data

movement engine

Prevent Data Thrashing

Performance data collected after

cache

Configurable analysis period

No Impacts to UsersReact Swiftly to Changing

Needs

Service Levels at a

Lower Cost

Reduce Cost

Scalable, Granular, Policy-Driven

Autonomic, sub-volume data

movement

Apply Flexibly per-Application

Coexistence of tiered and non-

tiered application volumes

Quality of service prioritization

modes with QoS Gradients

Minimize RiskGain Agility


26/30


27/30


28/30


CLUSTERED ENVIRONMENTS ADD ADDITIONAL

COMPLEXITY TO STORAGE PROVISIONING

VMware clusters create newstorage management challenges

1 cluster of 5 hosts and 10

volumes, requires 50 provisioning

actions on most traditional arrays!

At 10 min/action: More than 1 day!

Error-prone

VMware clusters are

dynamic resources subject to

growth and frequent change


29/30


3PAR AUTONOMIC GROUPS ELIMINATES

REPETITIVE ERROR-PRONE TASKS

3PAR Autonomic Groups Simplifies and automates volume

provisioning in a single command

Exports a group of volumes to a

host or cluster of hosts

Automatically preserve same LUN ID foreach volume across hosts

When a new host is added into the

host group:

All volumes are autonomically exported to

the new host

When a new volume is added into

the volume group:

New volume is autonomically exported to

all hosts in the host group


30/30

Documents

3Par Customer Training Inform (T and F Class) GOOD Document