You are on page 1of 30

3PAR INFORM OS

October 2010

Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Confidential

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

HP Confidential | October 2010

KEY CONCEPTS AND TERMS*


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, (Autonomic Group)

*There will be a quiz.


3 HP Confidential | October 2010

ARCHITECTURAL DIFFERENTIATION: PURPOSE BUILT


Utility Storage
Thin Conversion / Persistence Thin Provisioning Virtual Domains Dynamic Optimization Adaptive Optimization System Reporter Virtual Copy Remote Copy

F-Class

T-Class

Self-Configuring

Self-Healing
Autonomic Policy Management

Self-Optimizing
Utilization Manageability Mesh Active Fast RAID 5 / 6
4 HP Confidential | October 2010

Self-Monitoring
Performance

InForm fine-grained OS

Instrumentation Mixed Workload

Gen3 ASIC

Zero Detection

SIMPLIFIED STORAGE AND SERVER PROVISIONING


3PAR Rapid Provisioning
Seconds

to provision storage with no pre-

planning
Self-configuring Labor-intensive

and auto load-balanced storage volumes and careful planning eliminated

HP Confidential | October 2010

PHYSICAL DISK CHUNKLETS (256 MB/1 GB*)


C
= 256 MB Data Chunklet = 256 MB Spare Chunklet

SC

C C

C C

Each InServ Physical disk is initialized with data chunklets and spare chunklets

Physical Disk
SC SC SC

HP Confidential | October 2010

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
7 HP Confidential | October 2010

SW ARCHITECTURE: RAPID, TAILORED PROVISIONING...


Chunklets
Physical drives broken into fine-grained uniform 256 MB chunklets

Common Provisioning Groups


Automatically grows by creating Logical Disks (LDs) as needed (parameters set by the CPG policies)
Highest performance High resiliency Higher cost
Limit Warning

Virtual Volumes
Created and exported in two commands 15 seconds with no pre-planning

Drive Chassis

LD LD LD LD
Medium performance Highest resiliency Lower cost Autonomic

Limit Warning

LD LD
256 MB to 16 TB RAID 0, RAID 10, RAID 50 (1:2-8), RAID 60 (2:6, 2:14) Group

50GB SSD, 300 & 600GB FC, 2TB NL


8 HP Confidential | October 2010

3PAR WIDE STRIPING: COMPLETELY AND FINELY LOAD BALANCED


Market Leading Monolithic Array InServ T400 Storage Server

Channel Directors

Cache Boards

Disk Directors

8GB LUN spread across 4 disks (RAID 10)


9 HP Confidential | October 2010

8GB LUN spread across 64 disks (RAID 10)

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

10

HP Confidential | October 2010

HIGH AVAILABILITY + HIGH UTILIZATION RATE


3PAR Availability Level Concepts:
HA

Cage HA Magazine HA Port


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.

11

HP Confidential | October 2010

3PAR INSERV DATA LAYOUT

Logical Disks are bound to, serviced by All LDs are bound and load balanced together transparently Each Physical Drive across allpairs Nodes Drive Magazines have Drive Chassis are Nodes are added in RAID Sets are to form a single is divided into Chunklets 4 of the same drives point-to-point connected for cache redundancy. bound together to for RAID sets ( 3+1 R5 volume. And presented each 256 MB in size. FC 15, SATA, SSD etc. to controllers nodes in An InServ with 4 or more form logical disks example will stripe the L to the host across all D Drive magazines can the T Series InServs to nodes alsoall supports 4 members of the ports and nodes. Each VVcage is automatically be mixed inside the provide level Cache Persistence RAID set into separate Enabling a TRUE widely striped across same drive chassis. availability. Which enables chassis. Massively active/active chunklets on all disk spindles The ability to withstand maintenance windows striping data and configuration on a PER of the same type (Fiber the loss ofchassis an Entire and upgrades without enabling level LUN basis. Not channel, SATA, by default etc. drive enclosure without performance penalties. availability. (default) Active/passive on aparallel per Creating a massively losing access to your LUN basis as other system data. architectures.

OK OK / !

0 3

1 4

2 5

<. E > 0

<. E > 1

|O| | O

C 0

OK OK / !

0 3

1 4

2 5

<. E > 0

<. E > 1

|O| | O

C 0

L D

OK OK / !

0 3

1 4

2 5

<. E > 0

<. E > 1

|O| | O

C 0

OK OK / !

0 3

1 4

2 5

<. E > 0

<. E > 1

|O| | O

C 0

L D

L D

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

256 256 256 256

12

HP Confidential | October 2010

WHAT IS A REGION AND HOW DOES IT MAP TO A VIRTUAL VOLUME


Host Servers See LUNs (exported Virtual Volumes) Host Infrequently accessed portion of Volume mapped to a Region of Tier 2 Logical Disk

Virtual Volumes of any size (256MB to 16TB each)

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

Frequently accessed portion of Volume mapped to a Region of Tier 0 Logical Disk

Regions mapped to Raidlets of the Logical Disk 2 Raidlets (RAID 1) 4 Raidlets (RAID 5, 3+1)

Physical Disks broken into Chunklets (256MB each) SSD


13 HP Confidential | October 2010

SATA

HOW A VOLUME MAPS FROM VV TO CHUNKLET

14

HP Confidential | October 2010

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.

15

HP Confidential | October 2010

COMMON PROVISIONING GROUPS (CPG)


Host Servers
See LUNs with tailored cost, performance, availability, and capacity

OLTP Virtual Volumes


of any size (256MB to 2TB each)

3PAR Virtual Volume Management


Logical Disks are created and dedicated as needed to support the written to portion of Virtual Volumes

DW

Common Provisioning Groups


manage the creation and dedication of Logical Disks

Logical Disks
intelligent combinations of chunklets for tailored cost, performance, availability

Physical Disks
broken into Chunklets (256MB each)

16

HP Confidential | October 2010

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

17

HP Confidential | October 2010

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 = 256 MB

18

HP Confidential | October 2010

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) by default to guarantee cage level HA.
Setsize = 4 (3+1)
C C C p

C
C

C
p

p
C

C
C

Default size (RAID 5) Usable space = 768 MB (3*256)

Setsize = 6 (5+1)
Usable space = 1280 MB

(5*256)

19

HP Confidential | October 2010

3PAR RAID 5 CONCEPTS (2 OF 2)

Setsize = 9 (8+1) What is the usable space for this setsize?

Usable space = 2048 MB (8*256)

20

HP Confidential | October 2010

3PAR RAID MULTI PARITY (MP) CONCEPTS


RAID MP uses parity (double parity can deliver data in a double disk failure) to reconstruct data and performed in the ASIC XOR engine 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.

21

HP Confidential | October 2010

USAGE MEANING 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 If

default R6 -ha cage set size 8 requires 4 cages per node-pair, just like the default R5 set size 4. 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 mag but the system will place only one chunklet per mag if possible.

22

HP Confidential | October 2010

22

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

23

HP Confidential | October 2010

23

INSERV HA: BUILT FOR THE DEMANDS OF MULTI-TENANCY


Component
Traditional Arrays 3PAR InServ

Disk Drive
spare drive

Few-to-one rebuild Hotspots* & prolonged rebuild exposure

spare chunklets

Many-to-many rebuild Non-disruptive rebuilds in the time

--- R1 Raidlet ---

Drive Shelf (chassis)

--- RAID 1 Group ---

--- RAID 1 Group --Shelf (chassis)

Shelfdependent RAID No access to data

--- R1 Raidlet ---

Shelfindependent RAID Data access preserved


Shelf (chassis)

Controller Node

Traditional Cache Mirroring Poor performance (write-thru mode)

Persistent Cache Mirroring Consistent performance (no write-thru mode) **

24

HP Confidential | October 2010

ADAPTIVE OPTIMIZATION FEATURES, BENEFITS


Reduce Cost Gain Agility Minimize Risk

Optimize Cost/Performance Sub-volume, bi-directional data optimization Application specific vs. global thresholds Support for both Thin and Fat volumes

Scalable, Granular, Policy-Driven Autonomic, sub-volume data movement

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

Apply Flexibly per-Application


Coexistence of tiered and nontiered application volumes Quality of service prioritization modes with QoS Gradients

Service Levels at a Lower Cost


25 HP Confidential | October 2010

React Swiftly to Changing Needs

No Impacts to Users

3PAR INSERV VIRTUAL VOLUME


A virtual disk. Assembled by policy. Backed by every physical disk of the specified service level.

Virtual Volume

Host Sees Virtual Volume as a LUN

The only storage component visible to Hosts

26

HP Confidential | October 2010

3PAR HOST DEFINITION


Host Definition (Stand alone or into Host Set) Host Persona - Different operating systems require slightly different behaviors both from the port level and the SCSI layer Follow Implementation Guides Per Host OS VLUNS are what you get when you match a Virtual Volume (VV) to a host definition (or host set)

27

HP Confidential | October 2010

CLUSTERED ENVIRONMENTS ADD ADDITIONAL COMPLEXITY TO STORAGE PROVISIONING


VMware clusters create new storage 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

28

HP Confidential | October 2010

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 for each 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

29

HP Confidential | October 2010