3par customer training

Serving Information®. Simply.

Serving Information™. Simply.

3PAR Company Confidential

3PAR Customer Training:

Software/Hardware Overview

2

F200 F400 T400 T800Controller Nodes 2 2 – 4 2 – 4 2 – 8

Fibre Channel Host Ports Optional iSCSI Host PortsBuilt-in Remote Copy Ports

0 – 12 0 – 8

2

0 – 24 0 – 16

2

0 – 64 0 – 16

2

0 – 128 0 – 32

2

GBs Control CacheGBs Data Cache

8 12

8-16 12-24

8-1624-48

8-3224-96

Disk Drives 16 - 192 16 - 384 16 – 640 16 – 1,280

Drive Types 50GB SSD, 146/300/600GB FC and/or 1TB/2TB NL

50GB SSD, 146/300/600GB FCand/or 1TB/2TB NL



Max Capacity 128TB 384TB 400TB 800TB

Throughput/IOPS (from disk)

1,300 (MB/s) / 46,800

2,600 (MB/s) / 93,600

3,200 (MB/s) / 156,000

6,400 (MB/s) / 312,000

SPC-1 BenchmarkResults

93,050SPC-1 IOPS

224,990SPC-1 IOPS

3PAR InServ Storage Servers

Ready

2

Serving Information3

3PAR F-Class Architecture Basics

• Same underlined architecture as the T-Class – tailored for the midrange– Cache coherent & massively load

balanced– Mixed workload & Fast RAID– Thin Built In

• Same advanced 3PAR software as in the T-Class– InForm OS – Thin Provisioning & Virtual Copy– Dynamic Optimization– Virtual Domains– Remote Copy (connect to other InServ

models)

Serving Information3PAR Company Confidential

3PAR InServ F-Class Storage Server Specifications

F-Class Drive Chassis (frontview)

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD

3U

F-Class Controllers (Rearview)

Integrated Power

Supply & Battery

Integrated Power

Supply & Battery

Optional Adapter Slots Built-in Fibre Channel

(4Gb/s) ports

Built-in GigE port for Remote Copy

4U


3PAR InServ F-Class Storage Server Specifications

F-Class Controllers (Rearview)

F-Class Drive Chassis (frontview)

Integrated Power

Supply & Battery

Integrated Power

Supply & Battery

• One Xeon Quad-Core 2.33GHz CPU per node• One 3PAR Gen3 ASIC per node• 4GB Control & 6GB Data Cache per node• Built-in I/O ports per node

– 4 FC (4Gb/s) ports (host or backend connectivity)

– Gigabit Ethernet port for Remote Copy• Optional I/O adapter slots per node

– Up to 2 slots per node (or up to 4 more FC and/or iSCSI ports per node

• 4U Form Factor• Cabinet Options: 2M Cabinet or 3rd party rack

mountable

• 4Gb/sec internally switched FC Drive Chassis• 16 drives in 3U• Up to 384 drives across 24 Drive Chassis• Mixable FC and Nearline drives• Cabinet Options: 2M Cabinet or 3rd party rack

mountable

Optional Adapter Slots Built-in Fibre Channel

(4Gb/s) ports

Built-in GigE port for Remote Copy

4U

3U

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD

HDD HDD HDD HDD


3PAR InServ F-Class Port Configuration Recommendations

Configured for Greater Host Connectivity

Slot 1

Slot 2

Port 4

Port 3

Port 2

Port 1

Disk Host Host Disk

Configured for Greater Disk Connectivity

Slot 1

Slot 2

Port 4

Port 3

Port 2

Port 1

Disk Host Disk Disk

Slot 0

Slot 0





Virtual Volume (VV) Concepts


InServ Concepts for Volume Management

Section Content covers:

– InServ Chunklet/Physical disk– InServ RAID 1 – InServ RAID 5 – InServ RAID MP (RAID 6)– Virtual Volumes, VLUNS (LUNS)– Logical disks (LDs)


Disks are broken up into 256 MB fine grained Chunklets

“Chunklets”… 256MB make 3Par Virtualized Storage Arrays and Fast

Increase performance over traditional methods like Hyper / Meta’s by using uniformed fine grain 256 MB data “Chunklets”

No wasted space

Enables Hosts to have faster access to data across drives

Allows for performance optimized and easier Array management

Maximizes Throughput in MB’s and IOP’s


Physical Disk – Chunklets (256 MB)

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 and spare chunklets.


3PAR RAID 1 Concepts

• RAID 1 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

C C


3PAR RAID 5 Concepts

• RAID 5 uses parity to reconstruct data• RAID 5 uses a setsize of 4 by default

Setsize = 4 (3+1)

Default size (RAID 5)

Usable space = 768 MB (3*256)

C C C p

Setsize = 6 (5+1)


C C C c c p

C C p C

Cp CC


3PAR RAID 5 Concepts Cont’d

C C C c c pCCC

Setsize = 9 (8+1)

What is the usable space for this setsize?



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.


3PAR Volume Management View

Logical disksPhysical Disks Chunklets

• The 3PAR InForm OS manages the above

automatically

3PAR VM manages and presents volumes to server farms

Virtual Volumes

OLTP

D.W.


3PAR InServ Virtual Volume

The only storage component visible to Hosts

Virtual Volume

Host Sees Virtual Volume

as a LUN


Logical Disk

• A collection of physical disk chunklets (256 MB)

• Arranged as rows of RAID sets

• Each RAID set is made up of chunklets from different physical disks

• A chunklet can only be assigned to one logical disk


InServ Virtual Volume For RAID 5

Virtual Volume

Node Node

Logical Disk

Logical Disk

6 GB VV

3072 MB per Node/LD

C = 256 MB Chunklet

C

C

C

P

C

C

P

C

C

P

C

C

P

C

C

C

4 RAID Sets * 768 MB usable data = 3072 MB

3072 MB per Node/LD

C

C

P

P

C

C

C C

C

P

P

C

C

CC

C

RAID Set RAID Set

1

3

2

4

1

3

2

4



3PAR Virtualization: Load balanced across 3 Tiers

Node 0master

Node 1backup

......

......

......

......

Node 1master

Node 0backup

......

......

......

......

Node 2master

Node 3backup

......

......

......

......

Node 3master

Node 2backup

......

......

......

......

VirtualVolume

Logical Disk

Physical Disk(Chunklets)

Balance Load Across Nodes

Balance Load Across Disks

Hosts see a “LUN”

3PAR InForm™ OS uses chunklets like

legacy systems use physical disks

RaidSet Raid

Set

RaidSet

RaidSet

RaidSet

RaidSet

RaidSet

RaidSet


Default InServ Layout of 2 Node 6 GB Logical Disk

• InServ will place “chunklets” on separate physical disks

• InServ will insure physical disks are on separate drive magazines

• InServ will try to have each drive magazine on a separate drive chassis

• InServ will try to make each Logical Disk owned by each node the same size




Software


Scalable, autonomic administration

• Scalable GUI– Java-based– Spans multiple 3PAR systems

• Autonomic Administration– Knowledge of the underlying

logical and physical devices is not required for administration

– Availability and performance rules are implemented intelligently by the system based on available resources

3PAR InForm OS

• Comprehensive CLI– Platform independent– Multiple levels of administration

• SMI-S Support


3PAR Full Copy : flexible point-in-time copies

• Share data quickly and easily

• Full physical point-in-time copy of base volume

• Independent of base volume’s RAID and physical layout properties for maximum flexibility

• Fast resynchronization capability

• Thin Provisioning-aware• Full copies can consume same physical

capacity as Thin Provisioned base volume

3PAR Full CopyBase Volume

Full Copy


3PAR System Reporter: Historical Reporting

3PAR System Reporter

• Historical system data covering performance trends and capacity utilization

• Metering of all physical and logical objects, including Virtual Domains

• Useful for troubleshooting, planning, charge-back, SLA management

• Custom thresholds and e-mail notifications

• DB Choices: SQLite, MySQL, Oracle

• DB Access:

• Clients: Windows IE, Mozilla, Excel

• Directly via published DB schema




Thin Provisioning


Objectives

• At the end of this presentation the user should be able to :

– Explain the benefits of Thin Provisioning– Understand the concepts of Thin Provisioning– Set-up a Common Provisioning Group (CPG)– Create a Thin Provisioned Virtual Volume (TPVV)– Manage Alerts for CPG– Understand Best Practices of CPG


Thin Technologies

• Thin Conversion - Rapid migration from Fat to Thin allows for easy conversion from

legacy storage environments at line speeds Preserve service levels or performance impact during

Migrations• Thin Persistence - Reduce storage capacity costs by

allowing “thin” volumes to stay “thin”

• Thin Copy

Reclamation - Reduce storage capacity costs by reclaiming storage capacity

that is deleted but still “locked” in allocated space


Thin Conversion

• Thin your online SAN storageup to 75%

• A practical and effective solution to eliminate costs associated with:• Storage arrays and capacity• Software licensing and support• Power, cooling, and floor space

• Unique 3PAR Gen3 ASIC with built-in zero detection delivers:• Simplicity and speed – eliminate the time & complexity of getting

thin• Choice - open and heterogeneous migrations for any-to-3PAR

migrations• Preserved service levels – high performance during migrations


Thin Persistence

• Non-disruptive and application-transparent “re-thinning” of thinprovisioned volumes

• Thin “insurance” against unexpected or thin-hostile application behavior

• Returns space to thin provisioned volumes and to free pool for reuse

• Unique 3PAR Gen3 ASIC with built-in zero detection delivers:• Simplicity – No special host software required. Leverage standard

file system tools/scripts to write zero blocks.• Preserved service levels – zeroes detected and unmapped at line

speeds


Thin Copy Reclamation

• Online thin copy “re-thinning”

• Capacity can be freed from Thin Copies as they age and are deleted • Full/Virtual/Remote Copies

• Minimal performance overhead

• Supported on all InServs • T, S, F and E-class • Available for all supported hosts• No special host software required


Thin-Reclaim Reclaim

• How previously thin-provisioned SD/SD2 space becomes unused?

– Remove snapshot, and thus copy space is less utilized

– Zero detection (thin built-in), zero cmp filled


3PAR Thin Provisioning

• Offers a simple solution to the problem of unused allocated capacity

• Allows IT departments to safely allocate to an application as much “virtual” logical capacity as conceivably needed

• Actual “physical” capacity is drawn from a common pool called a Common Provisioning Group (CPG)

• The physical capacity drawn from the CPG relates directly to Application writes (dedicate on write)


Traditional (Fat) Provisioning

- Dedicate on Allocation -

3PAR Thin Provisioning

- Dedicate on Write -

Traditional versus Thin Provisioning

Volume

Volume

Volume

Written Data Written

Data

Written Data

Common Buffer Pool

Purchased Physical Capacity Purchased Physical Capacity

Volume

Volume

Volume

Written Data Written

Data

Written Data


Logical Disksintelligent combinations of chunklets for tailored cost, performance, availability

D WOLTP

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

Physical Disksbroken into Chunklets (256MB each)

Host ServersSee LUNs with tailored cost,

performance, availability, and capacityTraditional Virtual

Volume

Management

Logical Disks are pre-dedicated to support the entire logical capacity of

Virtual Volumes

Typical 3PAR Virtual Volume Management


Logical Disksintelligent combinations of chunklets for tailored cost, performance, availability

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

Physical Disksbroken into Chunklets (256MB each)

Host ServersSee LUNs with tailored cost,

performance, availability, and capacity

Common Provisioning Groups manage the creation and dedication of

Logical Disks

Thin Provisioned

Virtual Volume

Management

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

D WOLTP

3PAR Thin Provisioned Volume Management


Common Provisioning Group (CPG)

• A virtual pool of logical disks

• Automatically provisions logical capacity to Snapshot Administration (SA) and Snapshot Data (SD)

• Snapshot Data is the Virtual Volumes User Space

• Careful planning and monitoring is essential to manage space

• 3PAR provides many “Safety” mechanisms to help manage CPGs


Thin Provisioned Virtual Volumes (TPVVs)

• TPVVs behave like traditional VVs – the differences are transparent to the host

• Virtual capacity is represented to host servers and applications as a Virtual Volume

• A TPVV has no user space

• A base TPVV users space is mapped “on demand” to a Snapshot Data (SD) on a copy-on-write basis

• The Snapshot Administration (SA) and SD spaces of a TPVV are always associated with a CPG

• The same ease-of-use for VVs exist with TPVVs


Administering CPGs and TPVVs

• Gui

• CLI– createcpg– createtpvv


Where to Find Help on CPGs and TPVVs

• 3PAR InForm OS Command Line Interface Reference

• createtpvv• createcpg

• 3PAR OS InForm Administrator’s Guide

• Using Common Provisioning Groups• Consult HP 3PAR SE for Technical Assistance

• White Paper – 3PAR Thin Provisioning “Architecture Overview and Best Practices”


Creating a Common Provisioning Group (CPG) - CLI

<createcpg> command

Task: Create a CPG where the “set auto grow” is 16GB with a “Growth limit” of 32 GB and has a “Growth warning” at 24 GB.

CLI% createcpg –sdgs 16g –sdgl 32g –sdgw 24g cpgretail

Note: For a Full listing of <createcpg> command options refer to the “OS CLI Reference”


Growth Increment Considerations

• Should not exceed available space on your system

• The nature of the data running on the system

• The number of CPGs in the system

• The number of volumes associated with those CPGs

• Anticipated growth rate of the volumes associated with the CPG


Growth Increment Defaults and Minimums

Note: A smaller growth increment carries less risk in that it can prevent the CPG from automatically allocating a large amount of space at an inopportune time.

* If not sure – discuss with your SE.


Determining Space Usage

• Showcpg -rAt Creation

After TPVV Creation


CPG Growth Warning

• When a CPG approaches its “growth” warning an “alert” is generated

• The Administrator should check and determine if any action is required upon receiving a “growth” warning

• The InServ will suspend writes when a CPG is out of space

• An Administrator can add physical disk space or limit the future growth of volumes that draw from the CPG


CPG Growth Limit

• The InServ Administrator must be very careful when setting “Growth Limits”

• The Administrator can set a Growth limit greater than the systems physical disk space

• Recommendation: Do not allow a volume that draws form a CPG to exceed its growth limit

System Alert: If a volume that draws from the CPG reaches the CPG’s growth limit, an “alert” is generated notifying you that all logical capacity for the CPG has been consumed


Viewing Alerts Using InForm GUI

• Alerts can be seen by viewing the “Alert Pane” or selecting “Events” from InForm GUI


Thinly Provisioned Virtual Volumes

• A base volume capable of responding to host write requests by allocating space on demand in small increments

• Structured so that each volumes virtual size (the size that the volume presents to the host) always remains the same

• The storage behind the volume is allocated on demand


TPVV Components

• Snapshot Data Space

– Known as copy space– Contains the volumes user data and snapshot copy

data– A TPVV can have its user data or VC data in separate

CPGs (different QOS)

• Snapshot Administration

– Known as admin space– A Pointer file that “points” to VC or TPVVs


Creating a TPVV

• Creating a TPVV where the VC space and the user space are in the same CPG

createvv –tpvv –snp_cpg Raid1FC Raid1FC TPVV_oracle_log 50G

• Creating a TPVV where the VC space is in a different CPG than the user space

createvv –tpvv –snp_cpg Raid5NL Raid1FC TPVV_Oracle 50G


Editing CPG Parameters

• The following CPG parameters can be edited:

– Growth increment – Growth warning– Growth limit

• The following Logical disk parameters for CPG can be edited:

– RAID Type– Availability– Stepsize– Rowsize– Disk Filter

You can use “CLI” or “GUI” to make the changes. <setcpg> command is used to edit CPG parameters


Removing a CPG

• A CPG can be removed if no volumes are drawing Logical Disks from it

• To remove CPG using GUI (right click):

• To remove using CLI– <removecpg> command




Remote Copy

Serving Information

Converter/ Extender

Converter/ Extender

Primary Secondary

Primary Secondary

Other Common Approach

vs.

3PAR Remote Copy

Actual Used Capacity

Unused Purchased Capacity

Base Volume

BCV

Remote Copy

Thin Provisioned Base Volume

3PAR Remote Copy

ThinRemote Copy: Protect and share data affordably

• Smart– Initial setup in minutes– Simple, intuitive commands– No consulting services– VMware SRM integration

• Thin– Native IP-based, or FC– Thin provisioning aware– No extra copies or

infrastructure needed

• Ready– Mirror between any InServ

size or model– Many to one, one to many– Asynchronous Periodic,

Synchronous, or Synchronous Long Distance



How Asynchronous Periodic Mode Works

BaseVolume

Snap-shot

BaseVolume

Snap-shotTime

Primary Site Secondary Site

A AR1 Initial Copy

BRB-Adelta

Resynchronization. Delta Copy

B AR

Resynchronization.Starts withsnapshots

2

Ready for nextresynchronization

A AR

B BR

Upon Completion. Delete old snapshot

3



B ARResynchronizationStarts withsnapshots2

Asynchronous Periodic and Test/Dev SnapShots

BaseVolume

Snapshot BaseVolume

Snapshot

Primary Site Secondary Site

A AR

1 Initial Copy

BR

B-Adelta

ResynchronizationDelta Copy

Ready for nextresynchronization

A AR

B BR

Upon Completion. Delete old snapshot

3

Test / DevROSnapshot

RWSnapshots

E

Snapshot Copy (Read only) C

Snapshot Copies(Read/Write Copy) D

4

5




Other Software

65

Virtual Machines for Shared Systems

3PAR Virtual Domains: Ready for consolidation

VirtualDomain B

VirtualDomain A

Hosts

Access

CPGParameters

Volumes

Hosts

Access Volumes

CPGParameters

• Simple and Secure• Master administrator creates/assigns users, logical

elements, and domains• Users authorized to manage elements in their

Domain(s) only with Domain-specific statistics• Integrated with System Reporter, LDAP, & Remote

Copy

• Improved QoS• Completely virtual implementation preserves

massively parallel InServ load balancing• Higher performance and availability levels than pre-

consolidation levels • Virtual Domains Ideal for:

• “Self-service” storage• Disparate applications and user groups• Test & Dev. + Production• Error prevention• Compliance

Up to 1,024 Virtual Domains / InServ

Ready

Virtual Copy: Protect, retain & share data affordably

Integration withOracle, SQL,

Exchange, VMware VDI

3PAR Virtual CopyBase Volume 100s of Snaps…

Thin

• Smart– Safely promoteable snapshots– Safely deleteable snapshots– Scheduled creation/deletion– Consistency groups

• Thin– Reservationless snapshots– Non-duplicative snapshots– Thin Provisioning aware– Automatic space reclamation of deleted snaps

• Ready– Instant readable or writeable snapshots– Snapshots of snapshots– "mySnapshot“ utility– Virtual Lock for retention of read-only snaps

…but justone CoW

Dynamic Optimization: No complexity or disruption

Performance

Cost per Useable TB

Fibre Channel Drives

Nearline Drives

Optimize performance, efficiency and resiliency…

non-disruptively in a single command

RAID 1RAID 5 (2+1)RAID 5

(3+1)RAID 5 (7+1)

RAID 1RAID 5 (2+1)RAID 5

(3+1)

RAID 5 (7+1)

No migrations !

Smart

RAID MP (6+2)

RAID MP (14+2)

RAID MP (6+2)

RAID MP (14+2)

• An Adaptive Optimization (AO) configuration provides application specific profile– Up to 3 configurable tiers per AO profile– Vary storage type, RAID type, availability settings,

stripe characteristics, data placement on platter

• Multiple AO profiles per system – Each supports one or more volumes / applications– Sub-disk technology: Different profiles can

share physical disks

• Autonomic policy execution with manual overrides:– Execution schedule, sample interval– Maximum capacity to move – Maximum period for data movement

• Application performance prioritization – Selectively allocate valuable resources (e.g. SSD)– Intelligently optimize data movement with QoS Gradients: performance, balanced, cost

Adaptive Optimization Overview

72

Tier 1SSD

R5 (3+1)

Application

Profile A

Tier 2FC 15KR5 (3+1)

Tier 3SATA

R5 (7+1)

Application

Profile BV

olume 1

Volum

e 2

Tier 3SATA

R5 (3+1)

Tier 1SSD

R5 (3+1)

Volum

e 3

Volum

e 4





Provisioning and Management Concepts & Information

Serving Information

• Users• Ports• Hosts• Common Provisioning Group (CPG)• Virtual Volumes (VV)

– Fat volumes– Thin volumes– VLUNs

• Host Sets• VV Sets

Provisioning and Management

74


Why Host Personas

• Different operating systems require slightly different behaviors both from the port level and the SCSI layer

• Host persona splits this into SCSI layer behaviors (host persona capabilities) and port behavior settings (via “controlport config”)

• Multiple host types can share a single InServ Storage

Server port.

• Each host initiator gets its unique FC/SCSI level behavior.


Available Host Personas

For HPUX, AIX, and ONTAP all Host Personas are “Legacy Personas” since each OS was not going to take advantage of the new “Capabilities” of UARelLun, SesLun, and RTPG.

Serving Information3PAR Company Confidential 77

Host Personas – Some Details

• Host personas are tied to the host name and identified by the host persona number

• The host persona number can be set when the host is created or can be modified later

• The host personas can be created, modified, removed or displayed using the IMC or CLI commands

Serving Information3PAR Company Confidential 78

How Does It Work

• Controlport config sets existing and new loop attributes

– disk--initiator ports

– host--target ports

– rcfc--remote copy

– loop/point--connection topology

– unique_nwwn--ontap ports

Follow Implementation Guides (IGs) exactly when configuring hosts


Host Persona Capabilities

• UARepLun --Issue CC/UA report luns changed on vlun exports (new)

• SESLun --Make lun 254 available for host agent (new)

• RTPG --Report Target Port Group support for ALUA (new)

• NACA --Normal Auto Contingent Allegiance (AIX)

• VolSetAdd --Volume Set Addressing (HPUX)

• SoftInq --"Soft Inquiry" for EGENERA/ONTAP




3PAR Customer Training: Support

Serving Information

• For any issue with your InServ, call:– 1-888-372-7226– 24 x 7

• Create an iSupport account– Go to the 3PAR website

• Services, then “log in to 3PAR Central”

– Can download manuals, open service ticket

SUPPORT

81

3par customer training

Documents

tclass servers

par utility storage

gb fcandor 1tb2tb nl50gb

par software

t800 storage servers

gb fc andor 1tb2tb nl50gb

inserv models

drive types50gb ssd