EMC VPLEX Overview and General Best Practices: Implementation ...

25
Implementat EMC® Practi Implem Ove VPL Req Sys tion Planning ® VPL ices entation erview LEX Comp quiremen stem Volu Abs This imp com Sep Ver g and Best Pr LEX™ n Planni ponents nts vs. Re umes stract s document i plementation mponents an ptember 2014 sion 02 ractices Tech Overv ng and ecommen is one of a se n and best pra d system vol 4 nical Notes view a Best Pra ndations et of technica actices inform umes are cov and G actices al notes cont mation. A VP vered in this Genera taining curren PLEX overview volume. al Bes nt VPLEX w, explanatio st on of

Transcript of EMC VPLEX Overview and General Best Practices: Implementation ...

Page 1: EMC VPLEX Overview and General Best Practices: Implementation ...

Implementat

EMC®PractiImplem

Ove VPL Req

Sys

 

tion Planning

® VPLices entationerview LEX Compquiremen

stem Volu

Abs

Thisimpcom

Sep

Ver

g and Best Pr

LEX™

n Planni

ponents nts vs. Re

umes

stract

s document iplementationmponents an

ptember 2014

sion 02

ractices Tech

Overv

ng and

ecommen

is one of a sen and best prad system vol

4

nical Notes

view a

Best Pra

ndations

et of technicaactices informumes are cov

and G

actices

al notes contmation. A VPvered in this

Genera

taining currenPLEX overview volume.

al Bes

nt VPLEX w, explanatio

st

on of

Page 2: EMC VPLEX Overview and General Best Practices: Implementation ...

2 EMC VPLEX OImplementat

 

Overview andtion Planning

Cop

Pub

EMCThe

Thereppubfitndes

EMCCorher

For Trad

EMCImp

Part

d General Besg and Best Pr

pyright © 201

blished Sept.

C believes the information

e informationresentations

blication, andess for a par

scribed in thi

C2, EMC, andrporation in tein are the p

the most updemarks on E

C VPLEX Oveplementation

t Number H1

st Practices ractices Tech

14 EMC Corp

. 2014

he informatio is subject to

in this publis or warrantied specificallyticular purpos publication

d the EMC loghe United Stroperty of th

-to-date listin EMC.com.

rview and Gen Planning an

3545

nical Notes

poration. All r

n in this pubo change with

ication is proes of any kindy disclaims imose. Use, copn requires an

go are registeates and otheir respectiv

ng of EMC pr

eneral Best Pnd Best Pract

rights reserve

blication is achout notice.

ovided as is. d with respecmplied warrapying, and disn applicable s

ered trademaher countries.e owners.

roduct names

Practices tices Technic

ed. Published

ccurate as of

EMC Corporact to the info

anties of mercstribution of

software lice

arks or tradem. All other tra

s, see EMC C

cal Notes

d in the USA.

f its publicati

ation makes rmation in thchantability any EMC sofnse.

marks of EMCademarks use

Corporation

.

ion date.

no his or ftware

C ed

Page 3: EMC VPLEX Overview and General Best Practices: Implementation ...

 

ChaAud

Doc

EMC

ChaVPL

Dat

Con

V

S

ChaVPL

Con

G

ChaReq

ChaMet

B

Log

apter 1  Indience ..........

cument Orga

C VPLEX Ove

apter 2  VLEX Platform

ta Mobility ....

ntinuous Ava

Virtualization

Storage/Serv

apter 3  VLEX Engine (V

nnectivity and

General Infor

apter 4  Rquirements v

apter 5  Stadata Volum

Backup Polic

gging Volume

Imp

ntroduction....................

nization .......

rview ...........

VPLEX Overv Availability a

....................

ilability ........

n Architectur

vice Availabil

VPLEX CompVS2) .............

d I/O Paths ..

rmation ........

Requiremens. Recommen

System Volumes ..............

cies and Plan

es .................

EMplementation

n ....................

....................

....................

view and Scaling S

....................

....................

e .................

lity ...............

ponents ....................

....................

....................

ts vs. Recomndations Tab

umes ....................

nning ............

....................

C VPLEX Oven Planning an

....................

....................

....................

Summary .....

....................

....................

....................

....................

....................

....................

....................

mmendationble ...............

....................

....................

....................

erview and Gend Best Pract

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

ns ....................

....................

....................

....................

eneral Best Ptices Technic

Conte

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

....................

Contents

Practices cal Notes

ents

5 ............ 6 

............ 6 

............ 6 

8 ............ 9 

............ 9 

.......... 10 

.......... 10 

.......... 11 

13 .......... 14 

.......... 14 

.......... 15 

18 .......... 19 

22 .......... 23 

.......... 23 

.......... 24 

3

Page 4: EMC VPLEX Overview and General Best Practices: Implementation ...

4

Contents

EMC VPLEX OImplementat

 

Overview andtion Planning

FigFigu

Figu

Figu

Figu

Figu

Figu

d General Besg and Best Pr

ures ure 1 - Acces

ure 2 - Migrat

ure 3 - Contin

ure 4 - Front a

ure 5 - Precon

ure 6 - Contin

st Practices ractices Tech

s anywhere,

tion Compari

nuous Availa

and rear view

nfigured port

nuous availab

nical Notes

protect every

ison .............

bility Archite

w of a VPLEX V

t assignment

bility front-en

ywhere ........

....................

ecture ...........

VS2 engine..

ts - VS2 hard

nd configura

....................

....................

....................

....................

ware ............

tions (dual-e

....................

....................

....................

....................

....................

engine) .........

............ 7 

.......... 10 

.......... 12 

.......... 14 

.......... 14 

.......... 16 

Page 5: EMC VPLEX Overview and General Best Practices: Implementation ...

 

This

Aud

Doc

EMC

s chapter pre

dience .........

cument Orga

C VPLEX Ove

Imp

esents the fo

....................

nization ......

rview ..........

EMplementation

llowing topic

....................

....................

....................

C VPLEX Oven Planning an

Chapte

cs:

...................

...................

...................

C

erview and Gend Best Pract

er 1 In

....................

....................

....................

Chapter 1: Intr

eneral Best Ptices Technic

ntroduc

...................

...................

...................

roduction

Practices cal Notes

ction

........... 6 

........... 6 

........... 6 

5

Page 6: EMC VPLEX Overview and General Best Practices: Implementation ...

6

A

Chapter 1: Int

EMC VPLEX OImplementat

Audience

Documen

EMC VPL

roduction

 

Overview andtion Planning

e

Thewilltech

nt Organ

ThisImpdocper

All d

Themad

LEX Overv

EMCcondesdist

VPL

d General Besg and Best Pr

ese technical be configurihnical notes

SAN techn

Fiber Chan

VPLEX con

ization

s technical nplementationcument that h-topic inform

documents a

e following lisde available:

EMC VPLE

EMC VPLE

EMC VPLE

EMC VPLE

EMC VPLE

EMC VPLE

EMC VPLE

EMC VPLE

EMC VPLE

view

C VPLEX reprntinuous avaisigning; impltributed data

LEX addresse

Data Mobinstallatiogeographi

st Practices ractices Tech

notes are foing, installing requires an u

nology and n

nnel block st

ncepts and c

ote is one ofn Planning an had previousmation that w

are available

st represents:

EX Overview a

EX SAN Conne

EX Host Multi

EX IP Network

EX and Recov

EX Data Mobi

EX REST API

EX Upgrades

EX Virtual Edi

resents the nilability. Thisementing an

a protection s

es two distinc

ility: The abions – within tical region.

nical Notes

r EMC field pg, and suppo understandin

etwork desig

torage conce

omponents

f a set of docnd Best Practsly been avaiill be easier t

on http://su

s the technica

and General

ectivity

pathing

king

verPoint Inter

lity and Migr

tion

ext-generatio architectured perfecting

solutions.

ct use cases:

lity to move a the same dat

personnel anorting VPLEX.ng of the foll

gn

epts

uments that tices for EMClable. It is in

to maintain a

upport.emc.c

al note best p

Best Practice

roperability

rations

on architectue is based on enterprise c

:

application atacenter, acr

d partners an. An understaowing:

supersede t VPLEX Techntended to pr

and keep up-

com.

practice docu

es

ure for data mn EMC’s 20+ylass intellige

and data acroross a campu

nd customeranding of the

he monolithinical Notes rovide more c-to-date.

uments that

mobility and years of expeent cache and

oss different us, or within a

s who ese

ic

concise,

will be

rtise in d

storage a

Page 7: EMC VPLEX Overview and General Best Practices: Implementation ...

 

Fig

Continuouinfrastruct

gure 1 - Acc

Imp

us Availabilitture across t

cess anywher

EMplementation

ty: The abilityhe same vari

re, protect

C VPLEX Oven Planning an

y to create a ied geograph

t everywhere

C

erview and Gend Best Pract

continuouslyhies with unm

e

Chapter 1: Intr

eneral Best Ptices Technic

y available stmatched resi

roduction

Practices cal Notes

torage liency

7

Page 8: EMC VPLEX Overview and General Best Practices: Implementation ...

8

Chapter 2: VP

EMC VPLEX OImplementat

LEX Overview

 

Overview andtion Planning

This

VPL

Dat

Con

d General Besg and Best Pr

s chapter pre

LEX Platform

ta Mobility ...

ntinuous Ava

st Practices ractices Tech

esents the fo

Availability

....................

ailability .......

nical Notes

Cha

llowing topic

and Scaling

....................

....................

apter 2

cs:

Summary ...

...................

...................

VPLE

....................

....................

....................

EX Overv

...................

...................

...................

view

........... 9 

........... 9 

......... 10 

Page 9: EMC VPLEX Overview and General Best Practices: Implementation ...

V

VPLEX Pl

Data Mo

 

latform A

VPLto t

ConVPL

A Vandof F

Eacswieng

Themanalso

VPLclusaccfromdisr

bility

EMCseahetMir

VPLsynandVirtdistinfrMic

The

All Dsolufor

Durwithtargactufor

Availabili

LEX addressehe I/O throug

ntinuous avaLEX Metro, an

PLEX cluster d a managemFibre Channe

ch engine is ptch gets its p

gine or quad-

e managemennagement seo provides th

LEX scales boster as well aomplished n

m a VPLEX Loruptively

C VPLEX enabamless data merogeneous roring are su

LEX Metro or chronous/as

d Distance vMtual Machinetance. This prastructure recrosoft Hyper

e EMC Simple

Directors in aution what is multiple dire

ring a VPLEX hout affectinget devices aual data. A r organization

Imp

ty and Sc

es continuousghput require

ilability and nd VPLEX Geo

consists of oment server. A

l switches fo

protected by power througengine clust

nt server haservices when he point of ac

oth up and ouas from a duanon-disruptivocal to a VPLE

bles the conn mobility and arrays from apported acro

Geo configursynchronousMotion or Mics and their c

provides you esources betwr-V only.

e Support Ma

a VPLEX clusts referred to aector failures

Mobility opeg data integrllowing the uecord of all mal purposes.

EMplementation

caling Su

s availabilityed for the fro

data mobilityo.

one, two, or f A dual-enginr communica

a standby pogh an uninterer, the mana

s a public Eth connected tccess for com

ut. Upgradesal engine to avely. This is rEX Metro or V

nectivity to h the ability to

a single inteross different

rations enab distances. Icrosoft Hyperorrespondin with the abiween data ce

atrix (ESSM) –

ter have acce as an N -1 arc without loss

ration any jority. Data Mo

user to commmobility jobs.

C VPLEX Oven Planning an

ummary

y and data moont-end appli

y features ar

four engines e or quad-enation betwee

ower supply rruptible powagement serv

hernet port, wo the custom

mmunications

s from a singa quad engin referred to asVPLEX Geo ar

heterogeneouo manage storface within a array types a

le migrations In combinatir-V, it allows g applicationlity to reloca

enters. Geo i

– Simplified

ess to all Stochitecture. Ts of access to

obs in progreobility createmit or cancel

are maintain

Chap

erview and Gend Best Pract

obility requirications and

re characteris

(each containgine cluster en directors w

(SPS), and ewer supply (Uver also gets

which providemer network. s with the VP

gle engine to e are fully su

s scale up. Sre also suppo

us storage arorage provisi a data center and vendors.

s between loon with, for e you to transns and data ote, share and

is currently s

version of th

orage VolumeThis type of ao data down

ss can be pas a mirror of

the job withoned until the

pter 2: VPLEX

eneral Best Ptices Technic

rements and back-end sto

stics of VPLEX

ining two dire also contain

within the clu

ach Fibre ChPS). (In a du power from a

es cluster This EthernePLEX Witness

a dual enginupported andScale “out” uorted non-

rrays providinoned from mr. Data Mobi.

cations over example, VMparently relo

over synchrod balance supported wit

he ELab Navig

es making thiarchitecture a to a single d

aused or stop the source aout affecting

e user purges

Overview

Practices cal Notes

scales orage.

X Local,

ectors), ns a pair uster.

annel ual- a UPS.)

et port s.

ne d are pgrades

ng multiple

lity and

r Mware ocate onous

th

gator

is allows irector.

pped and the

s the list

9

Page 10: EMC VPLEX Overview and General Best Practices: Implementation ...

10

VA

Chapter 2: VP

EMC VPLEX OImplementat

Continuo

VirtualizatioArchitecture

LEX Overview

 

Overview andtion Planning

Fig

Onethatmigplanto hhosan o

VPLseaunihosawaonlythat

If thandcominteresy

ous Avail

BuiEMCresiclusacc

Uni

n

d General Besg and Best Pr

gure 2 - Mig

e of the first at it provides

grations off anned outage

have new devst remediatio outage.

LEX eliminateamless and trnterrupted d

st continues tare of the chay to VPLEX ant is handled

he solution ind Replica volumpletely transerruption in tynchronize th

lability

lt on a foundC VPLEX is deides betweenstering architess to shared

que characte

st Practices ractices Tech

gration Comp

and most com a simple trann array are tis with all nec

vices provisioon may be req

es all these pransparent touring the ent

to operate ofange in the bnd there are through VPL

ncorporates Rumes reside sparent to evhe replicatiohe replication

dation of scalesigned to sen the serverstecture that ad block stora

eristics of thi

Scalebig w

nical Notes

parison

mmon use cansparent appme consumicessary apploned and copquired for su

problems ando the serverstire process. ff the Virtual backend array no necessaryEX.

RecoverPoint on VPLEX virven to Recoven so there isn volumes.

lable and coneamlessly sc and heterog

allows serverage devices.

s new archit

e-out clusteriwith predictab

ases for storaproach for arrng due to the

lications thatpied to withopport of the

d makes the a. The applica Host remed Volumes proy. All host ley considerati

t and the Recrtual volumeserPoint. This

s no requirem

ntinuously avale from sma

geneous storrs at multiple

ecture includ

ing hardwareble service le

age virtualizaray replaceme requirement don’t inhereout taking an new array wh

array replaceations contin

diation is not ovisioned froevel support ions for the b

coverPoint Res then array rs solution res

ment to recon

vailable multall to large corage assets, ae data center

de:

e lets you staevels

ation in genement. Standa

nt of coordinently have th

n outage. Addhich may also

ement complnue to operat necessary asm VPLEX and

requirement backend arra

epository, Jo replacement sults in no

nfigure or

ti processor eonfigurations and uses a urs to have rea

art small and

eral is ard ating

he ability ditional o require

letely te s the d is not s apply

ays as

urnal is also

engines, s. VPLEX nique ad/write

grow

Page 11: EMC VPLEX Overview and General Best Practices: Implementation ...

SA

Storage/SerAvailability

 

Witdistbalaacc

EMCacroconarch

EMCto pdistsiteand

Manmusstor

Plea

EacconacroClusactiuse

rvice

h a unique stributed cachancing, and fess with pred

C VPLEX has oss VPLEX Cl

nnectivity. VPhitecture will

C VPLEX usesprovide a VPLtributed/fede

es and a 3 wad the VPLEX W

ny solutions st be accessirage and link

ase refer to t

ch VPLEX sitennected to thoss the sitessters to creatively use the

e the storage

Imp

Advaimproconte

Distrand f

Cons(withenabreloc

cale-up and he coherency failover of stodictable serv

been architeusters. VPLE

PLEX Geo supl enable mor

s a VMware VLEX Witness berated solutiay VPN will beWitness.

require a thiible from thek costs.

he section in

has a local Vat VPLEX Clu to enable fete a distribut storage I/O I/O capabilit

EMplementation

anced data caove performaention

ibuted cache failover of I/O

sistent view ohin a data cenbling new mocation

scale-out arcy provide wororage domai

vice levels.

ected for mulX Metro supp

pports max 5e than two si

Virtual machi between VPLon. This thirde established

rd site, with e solution’s n

n this docum

VPLEX Clustester. The VPLderation. A d

ted RAID 1 vi capability ofty of the stor

C VPLEX Oven Planning an

aching utilizeance and red

e coherence fO across the

of one or mornter or across

odels of conti

chitecture, VPrkload resilieins, and enab

lti-site virtualports max 5m

50ms RTT, anites to be con

ine located wLEX Clusters td site needs d between th

a FC LUN actnode in each

ent on VPLEX

er and physicLEX Clusters

device is takertual volume

f the storage rage in Site B

Chap

erview and Gend Best Pract

es large-scaleduce I/O laten

for automati cluster

re LUNs acros synchronouinuous availa

PLEX advancency, automables both loc

lization enabms RTT, FC ord 10GigE. Thnnected in th

within a sepa that are part only IP connhe VPLEX ma

ting as the qu site resulting

X Witness for

cal storage an themselves en from each

e. Hosts conn in Site A, Ho

B.

pter 2: VPLEX

eneral Best Ptices Technic

e SDRAM cacncy and array

c sharing, ba

ss VPLEX cluus distancesability and w

ced data cachatic sharing, cal and remo

bling federatir 10 GigE he nature of he future.

arate failure d of a ectivity to thnagement se

uorum disk. Tg in addition

r additional d

nd hosts are are interconnh of the VPLEXnected in Sit

osts in Site B

Overview

1 Practices cal Notes

che to y

alancing,

sters ) orkload

hing and

te data

ion

the

domain

e VPLEX ervers

This al

details.

nected X e A actively

11

Page 12: EMC VPLEX Overview and General Best Practices: Implementation ...

12

Chapter 2: VP

EMC VPLEX OImplementat

LEX Overview

 

Overview andtion Planning

Fig

VPLLUNcon

Whonevolumir

d General Besg and Best Pr

gure 3 - Con

LEX distributeN and storagencurrent read

en using a die of the sites ume, with noror leg at the

st Practices ractices Tech

ntinuous Ava

ed volumes ae identifiers w/write acces

istributed vir is lost, all ho

o disruption. e other site.

nical Notes

ailability

are available when exposes across site

rtual volume osts continue VPLEX servic

Architectur

from either Ved from eaches.

across two Ve to have accces all read/

re

VPLEX clusteh cluster, ena

VPLEX Clustecess to the dwrite traffic t

er and have thabling true

rs, if the storistributed virthrough the r

he same

rage in rtual remote

Page 13: EMC VPLEX Overview and General Best Practices: Implementation ...

 

This

VPL

Con

s chapter pre

LEX Engine (V

nnectivity an

Imp

esents the fo

VS2) .............

d I/O Paths .

EMplementation

Chapte

llowing topic

....................

....................

C VPLEX Oven Planning an

er 3 V

cs:

...................

...................

Chapter

erview and Gend Best Pract

VPLEX C

....................

....................

r 3: VPLEX Com

eneral Best Ptices Technic

Compone

...................

...................

mponents

1 Practices cal Notes

ents

......... 14 

......... 14 

13

Page 14: EMC VPLEX Overview and General Best Practices: Implementation ...

14

V

Chapter 3: VP

EMC VPLEX OImplementat

VPLEX En

Connecti

LEX Compone

 

Overview andtion Planning

ngine (VS

VS2is osee

The

Fig

ivity and

ThisSANbesdesTheconnot

Fig

Direconare

nts

d General Besg and Best Pr

S2)

2 refers to theon 2U enginese the append

e following fig

gure 4 - Fro

I/O Path

s section covN. The practist practice. Wsigned with ae VS2 hardwanfigured with offer both so

gure 5 - Pre

ector A and Dnfigured for h configured f

st Practices ractices Tech

e second vers and will beix.

gures show t

ont and rear

hs

vers the hardces mention

We’ll discuss a standard prare must be o FC or 10 Gigolutions in th

econfigured

Director B eacost connecti

for array conn

nical Notes

rsion of hardwe detailed bel

he front and

r view of a

ware conneced below are Host and Arr

reconfigured ordered as a gabit Ethernethe same conf

port assig

ch have four vity and are

nectivity iden

ware for the Vlow. For info

rear views o

a VPLEX VS2

ctivity best pre based on Dray connectiv port arrange Local, Metrot WAN connefiguration.

gnments - VS

I/O modules identified asntified as bac

VPLEX clusteormation on V

f the VPLEX V

engine

ractices for cDual Fabric SAvity. The VPL

ement that is o or Geo. VS2ectivity from t

S2 hardware

s. I/O moduls frontend whckend. The f

er. The VS2 h VS1 hardwar

VS2 Engine.

connecting toAN, which is LEX hardware not reconfig

2 hardware is the factory a

e

les A0 and B0hile the A1 anfrontend port

hardware e please

o the Industry e is gurable. s pre-nd does

0 are nd B1 ts will

Page 15: EMC VPLEX Overview and General Best Practices: Implementation ...

General Information

 

log andthe andcon

Theby aconB2 or Gfor

Thenetwclussitereqthe botfor provcomnetwporpordire

WhconmanHowof fefor

Froninitas t

Do genHBAsec

Offi“miconpurimpdocSolAlso

in to the fabd the backend array targets

d backend ponsideration m

e I/O modules a four port FCnfigurations. and may be aGeo upgrades Local Com an

e FC WAN Comworks that spsters in a Mees. Dual fabruired. The 1 same QoS. h clusters wi

or A2-XG01 avides a redu

mmunicates wwork failure.

rts on one clurt group on thections.

en configurinnfiguration thny instanceswever, there eatures like N connectivity

ntend (FE) poiator ports. B

target ports o

not confuse neral referencA ports on a htions have a

icial documeinimal config

nnectivity. Wrpose of a Proplemented incumentation utions shoulo, this “minim

Imp

rics and presd ports will los. Each direcorts. Array di

must be used

s in A2 and BC module or a VPLEX Local added in thes. The I/O mnd will only u

m ports will bpan the two stro configura

rics that curre0 GigE I/O m

All A2-FC00 aill connect to

and B2-XG01ndant netwo

with all the d For both VP

uster must sehe other clust

ng the VPLEXhat provides t

connectivity are some mi NDU. Variou with a VPLEX

orts provide c Backend (BE)or FA’s.

the usage ofce to a port s host should more specif

nts as may bg” and descri

While this is aoof of Concep a full produc for minimal cd not be intrmal config” d

EMplementation

sent themselog in to the fctor will connrect connect if this option

B2 are for WA a two port 10l configuratio

e field for conodules in slo

use the botto

be connected sites. This aation withoutently span th

modules will b and B2-FC00o one fabric o1 ports will co

rk capabilitydirectors on tPLEX Metro anee all of the dter across tw

X Cluster cabl the best comy can be confnimal require

us requiremenX Cluster.

connectivity t) ports provid

f ports and inhould be a p

use the termic discussion

be found in thbe how to codequate to dpt or use withction environ

config this isoduced into

documentatio

C VPLEX Oven Planning an

lves as target fabrics as initnect to both St is also suppn is required

AN connectiv0 GigE for VPLons will ship nnecting to aots A3 and B3om two ports

d to dual sepllows for datt requiring a

he two sites a be connected0 ports or A2-or network anonnect to they where each he other sitend VPLEX Gedirector’s WA

wo different p

ling and zonimbination of sfigured to varements that nts and reco

to the host ade connectiv

nitiator ports port on a VPL

m “initiator pon of cluster-to

he VPLEX Proonnect it to bdemonstrate hin a Test/Denment. As cls not a “Cont production eon is specific

Chapter

erview and Gend Best Pract

ts for zoningtiators to be

SAN fabrics wported howev.

vity. This slotLEX Metro or with filler blanother net ne3 are popula.

arate backboa flow betwe

merged fabriare also suppd to dual netw-XG00 and B2nd all A2-FC0e other fabric director on o

e even in the o, each direc

AN COM portspipes. This a

ing, the gene simplicity anrying degrees must be adhmmendation

adapters alsovity to storage

within documEX director.

ort.” VPLEX Mo-cluster con

ocedure Genebring up the l the features ev environmeearly stated inuously Ava

environmentsc to host con

r 3: VPLEX Com

eneral Best Ptices Technic

g to the host i used for zonwith both fronver limiting.

t may be pop VPLEX Geo anks in slotsew cluster fo

ated with FC m

one fabrics oeen the two Vic between th

ported but noworks consis2-XG00 ports

01 and B2-FCc or network. one cluster event of a factor’s WAN Cs within the spplies in bot

eral rule is to d redundancs of redunda

hered to for sns are outline

o known as he arrays port

mentation. A All referenceMetro and VPnnectivity.

erator refer to east possible

within VPLEXent it should within the ailable” soluts that are “no

nnectivity. Pl

mponents

1 Practices cal Notes

initiators ning to ntend

Special

pulated

A2 and or Metro modules

or VPLEX he two ot sting of s from 01 ports This

bric or OM

same th

use a cy. In ancy. upport

ed below

ost ts known

Any es to LEX Geo

o a e “host” X for the not be

tion. ot” HA. ease do

15

Page 16: EMC VPLEX Overview and General Best Practices: Implementation ...

16

Chapter 3: VP

EMC VPLEX OImplementat

LEX Compone

 

Overview andtion Planning

not bacbac

The

Fig

nts

d General Besg and Best Pr

try to apply tckend must ackend storage

e following ar

gure 6 - Con

st Practices ractices Tech

this concept allow for conne volumes fro

re recommen

Dual impledata

Eachboth Hostsboth conn

ntinuous ava

BackeachcombchecThis and tdirecboth singl

Fabrisingl

AvoidUse h

nical Notes

to backend nectivity to bom each dire

ded:

fabric designemented to a access even

VPLEX direc host (front-es will connec fabrics and ectivity as re

ailability

k-end connec LUN from ea

bined active k command)

check assure two unique tactor. These b fabrics as we fabric to an

c zoning shoe initiator an

d incorrect FC highest poss

array connecboth fabrics foector.

ns for fabric avoid a singlen in the event

tor will physend) and storct to both an across enginequired with

front-end c

ctivity checksach director. and passive for the LUN

es that there argets in the

backend pathwell. No volum

ny director as

ould consist ond up to 16 ta

C port speed sible bandwid

ctivity. The refor dual path

redundancy e point of fait of a full fab

ically connecrage (back-en A director an

nes for the su the NDU pre

configurati

s verify that t This assures paths (repor is greater tha are at least t set of paths

hs must be come is to be ps this is a sin

of a set of zoargets.

between thedth to match

equirements connectivity

and HA shouilure. This prric outage.

ct to both fabnd) connectind B directorupported HA -checks.

ions (dual-e

here are two s that the numrted by the nan or equal t two unique is to a LUN froonfigured ac

presented ovengle point of

ones, each wi

e fabric and V the VPLEX m

for y to all

uld be rovides

brics for vity.

r from level of

engine)

paths to mber of du pre-

to two. nitiators

m each ross er a failure.

ith a

VPLEX. maximum

Page 17: EMC VPLEX Overview and General Best Practices: Implementation ...

 

Eacanddirecon

ch VPLEX dired storage (baector from bonnectivity as

Imp

port sovers

Eachand Bportsor swloss VPLEgroupminim

ector will phyck-end) conn

oth fabrics an required with

EMplementation

speed and usubscribed p

VPLEX direc BE I/O modus connected twitches so a s of access onEX BE ports wps of devicesmize traffic a

ysically connenectivity. Hond across engh the NDU pr

C VPLEX Oven Planning an

se dedicatedports on SAN

tor has the cules to both fa to on the SAN single blade that fabric o

with Array pors to those VPacross blades

ect to both faosts will conngines for the re-checks.

Chapter

erview and Gend Best Pract

d port speeds switches.

capability of cabrics with mN should be or switch faioverall. A goorts that will bPLEX BE portss.

abrics for botnect to both a supported H

r 3: VPLEX Com

eneral Best Ptices Technic

s i.e. do not u

connecting bmultiple ports on different lure won’t caod design wi

be provisionins in such a w

th host (front an A director HA level of

mponents

1 Practices cal Notes

use

both FE s. The blades ause ill group ng ay as to

t-end) and B

17

Page 18: EMC VPLEX Overview and General Best Practices: Implementation ...

18

Chapter 4: Re

EMC VPLEX OImplementat

quirements vs

 

Overview andtion Planning

C

This

Req

s. Recommend

d General Besg and Best Pr

Chapter

s chapter pre

quirements v

dations

st Practices ractices Tech

4 Req

esents the fo

vs. Recomme

nical Notes

quireme

llowing topic

ndations Tab

ents vs.

cs:

ble ..............

Recomm

....................

mendati

...................

ions

......... 19 

Page 19: EMC VPLEX Overview and General Best Practices: Implementation ...

Requirem

 

ments vs

Theandthe

Du

Du

InicoboDir

FobapeSto

TwbapeSto

. Recomm

e following tad Proof of Con type of envir

ual Fabric

ual HBA

itiator nnected to

oth an A and rector

ur "active" ackend pathser Director peorage Volum

wo "active" ackend pathser Director peorage Volum

Imp

mendatio

able represenncept environronment the

ProductEnvironm

RequireAvailabi

Require

B Require

s er

e

Recommalso It’srequiremhave moactive pdirector volume

s er

e

Require

EMplementation

ons Table

nts recommennments. Be s VPLEX is dep

ion ment

ment for Higility

d

d

mended but a

ment to not ore than 4 aths per

r per storage

d

Chapter 4: R

C VPLEX Oven Planning an

e

ndations and sure to adherployed in.

Test or PConceptEnvironm

h Requiretests invAvailabi

Require

Recomm

Recomm

Require

Requirements

erview and Gend Best Pract

d requiremenre to the requ

Proof of t ment

ment if the volve High ility

d

mended

mended

d

vs. Recomme

eneral Best Ptices Technic

nts for produuirements no

Notes

Dual Fabricsgeneral bes

Single initianot supportdual port HBpoint of fail

For a ProduEnvironmenrequired thaconnectivityinitiator spaa dual or quVPLEX Clust

This is the mnumber of "paths. An active/passarray will hamaximum oand four papreferred paeight in all.

This is a mirequiremenwhich dictatwo VPLEX Dbackend poconnected tports per StVolume. Deworkload, senvironmentype, four "aconfiguratioproven to aperformanctherefore ar

endations

1 Practices cal Notes

ction oted for

s are a st practice.

ator hosts areted and a BA is a singlelure also.

ction nt, it is also at the y for each an engines inuad engine ter.

maximum "active"

sive or ALUA ave a of four active assive or nonaths making

nimum t in NDU

ates that to Director orts will be to two array torage epending on size of nt and array active" path ons have lleviate

ce issues andre

19

e

e

n

-

d

Page 20: EMC VPLEX Overview and General Best Practices: Implementation ...

20

Chapter 4: Re

EMC VPLEX OImplementat

quirements vs

 

Overview andtion Planning

HoCoVP

ArrcoVP

WApo

MeLo

s. Recommend

d General Besg and Best Pr

ost Direct onnected to PLEX Director

rays direct nnected to

PLEX Director

AN COM singort connectivi

etadata and gging Volum

dations

st Practices ractices Tech

rs Not Sup

rs

Not Recbut Sup

gle ity

Not Sup

e

It is requmetadatmetadatare confarrays aif more tis presewere buwith a sand anowere to later timrequiredleg of thvolume backup array.

nical Notes

pported

ommended ported

pported

uired that ta and ta backups figured acrost the local si

than one arrant. If the site

uilt originally ingle array

other array be added at

me then it is d to move onhe metadata and one to the new

Not Sup

Support

Not Sup

ss te ay e

a

e

It is requmetadatmetadatbackupsconfigurarrays asite if mone arrapresentstandarduring aperformIt wouldundesirhave to skip optneeded

pported

ted

pported

uired that ta and ta s are red across

at the local more than ay is . A

rd test a POC is to

an NDU. d be able to use the --tion if not .

recommendminimum opaths per dstorage voluavoid only tconnectivityproduction environmen

Host direct VPLEX Direcsupported.

Array directsupported blimited in scwhy it is notrecommendproduction

Two ports oCOM for eacmust be conit their sepagroups. FibWAN COM (is also suppall four porttheir own po

While it is afor metadatmetadata bconfigured arrays, it is recommendlogging voluarrays as wethe array ththe logging would resuladditional ofull rebuildsarray came

ded over the f two active irector per ume. Try to

two path y in nts.

connect to actor is never

t connect is but extremelycale which ist

ded for a environment

on the WAN ch Director nfigured eacarate port bre Channel (Metro Only) ported with ts each in ort group.

a requirementa and ackups to be

across highly ded to mirror umes across ell. Loss of at contains volumes lt in

overhead of s after the back up.

y s

t.

h

t

e

Page 21: EMC VPLEX Overview and General Best Practices: Implementation ...

 

HoClu

ArrClu

VP

ost Cross-uster Connec

ray Cross-uster Connec

PLEX Witness

Imp

ct SupportWitness

ct

Only supboth sit1ms lateeach othstrictly fpurposeprotectimetadatvolumesVolumesupportto both

RequireAvailabi

EMplementation

ted with VPLEs required

pported if es are withinency from her and

for the e of adding on to ta and loggins. Storage s are not ed connecte

clusters

ment for Higility.

Chapter 4: R

C VPLEX Oven Planning an

EX SupportVPLEX Wrequired

n

ng

d

Only supboth sitwithin 1latency other anfor the padding pto metalogging Storage are not sconnectclusters

h Optionashould mwhat wiproduct

Requirements

erview and Gend Best Pract

ted with Witness d

pported if es are

1ms from each nd strictly purpose of protection data and volumes. Volumes

supported ted to both s

al but mirror ll be in

tion

vs. Recomme

eneral Best Ptices Technic

VPLEX WitnrequiremenCross-Clustregardless oenvironmenresume attrconsistencymust be setadditional r

Connecting both sides oMetro or Gesupported iexceed 1mseach other. extreme cautaken not tosame devicclusters. Alcautious if eperformancinjection tea configurat

VPLEX Witndesigned toVPLEX Metris not implea VPLEX LocWitness hasbe such a venhancemeshould be crequiremenWitness muco-located wthe VPLEX Cit is monito

endations

2 Practices cal Notes

ess is a hardt for Host er Connect

of the type ofnt. The auto ribute on all y groups t to true as an

requirement.

an array to of a VPLEX eo is not if the sites s latency from If done thenution must bo share the es to both lso, be evaluating ce or fault sts with suchtion.

ess is o work with ao or Geo. It

emented withcal. VPLEX s proven to aluable

ent that it considered a t. VPLEX

ust never be with either oClusters that ring.

21

f

n

m n e

h

h

f

Page 22: EMC VPLEX Overview and General Best Practices: Implementation ...

22

Chapter 5: Sys

EMC VPLEX OImplementat

stem Volumes

 

Overview andtion Planning

TheEacits d

This

Met

Log

 

s

d General Besg and Best Pr

ere are two tych VPLEX Met distributed d

s chapter pre

tadata Volum

gging Volume

st Practices ractices Tech

ypes of systemtro or Geo clu

devices.

esents the fo

mes ..............

es ................

nical Notes

Cha

m volumes. uster must al

llowing topic

....................

....................

apter 5

Each clusterso have suff

cs:

...................

...................

Syste

r must have aficient loggin

....................

....................

em Volum

a metadata vg volumes to

...................

...................

mes

volume. o support

......... 23 

......... 24 

Page 23: EMC VPLEX Overview and General Best Practices: Implementation ...

a

Metadat

Backup Policand Planning

 

a Volume

A mto-pcondurfor

Metveri

Not

Metfullyeffe

You

Plan

cies g

es

metadata voluphysical mapnfiguration sering system in example, you

tadata volumefy-on-disk-con

te the followi

Aw

Yo

M

Mwr

TCo

Vt

Ma

Md

M

tadata volumy allocate the

ects to the me

u need to hav

n on the follo

Sa

Imp

ume containspping informaettings, and onstallation. Hu are migrati

es consistencynsistency –sty

ng:

A metadata vwithout claim

You create mor devices

Metadata vounderlying re

Metadata vowhenever morequirement

Two MetadatCluster and mone array is c

Installations VPLEX clustethe second a

Metadata voand read from

Metadata vodevices. It is

Meta volume

mes provisione device so tetadata volu

ve a metadat

owing:

Spare voluma minimum o

EMplementation

s informationation, data a

other system However, young to a new a

y should be peyle short -c <cl

volume is theming it first

metadata volu

lumes shouledundant pro

lumes must ore than one

ta volume ba must be plac configured to

that were iner must movearray once pro

lumes are wrm only during

lumes are sus required for

e names can

ned on Thin dhat over allome should a

a backup you

es for each cof two backu

C VPLEX Oven Planning an

n specific to about the dev informationu may need t

array.

eriodically cheluster>’ comma

e only object

umes directly

d be on storaoperties such

be mirrored array is conf

ackups must ced on differeo a VPLEX Clu

itially confige a Metadata ovisioned

ritten to at thg the boot of

upported on Tr those devic

be a max of

devices havecation of the

additional up

u can recove

cluster to holps per VPLEX

Chap

erview and Gend Best Pract

a VPLEX Clusvices and virt. Metadata v

to create a m

ecked using thand

t you create o

y on storage

age volumesh as RAID 1 o

between difffigured to a V

be configureent arrays whuster – NDU r

ured with a s mirror leg an

he time of a cf each directo

Thin/Virtuallces to be fully

39 character

e the additione thin pool wodates be req

er from.

ld backups —X Cluster

pter 5: System

eneral Best Ptices Technic

ster such as vtual volumesvolumes are c

metadata volu

he ‘meta-volum

on a storage v

volumes, no

that have or RAID 5

ferent storage VPLEX Cluste

ed for every Vhenever more requirement

single array pnd a backup

configurationor

ly Provisioney allocated

rs

nal requiremeon’t have adv

quired.

— You need to

Volumes

2 Practices cal Notes

virtual-, system

created ume if,

me

volume

t extents

e arrays er – NDU

VPLEX e than

per copy to

n change

d

ent to verse

o rotate

23

Page 24: EMC VPLEX Overview and General Best Practices: Implementation ...

24

Chapter 5: Sys

EMC VPLEX OImplementat

Logging

stem Volumes

 

Overview andtion Planning

Ren

MetProcvoluallologg

For on s

Volumes

A phavwritinfoonlysiteandone

If a resybe lcalcnumspaLogloca

TheConrecoandplacthat

s

d General Besg and Best Pr

Ac

Om

aming Metada

tadata volumecedure Generaume backups. cated which is

ging volumes.

additional in support.emc

s

rerequisite tove a logging vtten during aormation in loy changed bl

e. One for wrd one for write log is used

logging voluynchronizatio large enoughculation for dmber of clustace for every gging volumeal mirrors.

e logging volunsequently, itommends thd that you alscing the loggt it is logging

st Practices ractices Tech

A system-widcluster backu

On-demand migrations

ata Backup vo

es are requiredator to zero the Additionally,s necessary fo

nformation, p.com.

o creating a d volume at ea

n inter-clusteogging volumlock regions rites initiatedes succeed l to push data

1. The fon thfor th

2. The 2writelog. remo

me is not creon of every dh to contain odetermining lers] Conseq

160 TB of diss are not use

ume receivest must be abat you stripe

so mirror it, sging volume og against.

nical Notes

de scheduledup for a VPLE

backups bef

olumes is not s

d to be zeroede disks to be u writing zeros

or VPLEX supp

please refer t

distributed dch cluster. Loer link failure

mes to synchr across the lind remotely tha ocally but faa and one is u

first bitmap lohe winning sihe log rebuild

2nd bitmap loes to the loca You then useote cluster.

eated, every distributed de one bit for ev logging volumuently, you nstributed deved for VPLEX

s a large amole to handle it across sevince this is im

on separate p

d backup donEX Metro or V

fore/after ma

supported.

out. Follow t used for the M to thin deviceortability with

to VPLEX with

device, or a reogging volume. After a linkronize the dink. Each DRat fail locallyil remotely.

used to pull d

og is used if te. You will

d

og is used if al leg will fail,e this in a log

inter-cluster evice in the svery page of dme size is: 10

need approxivices in both Local config

ount of I/O du I/O quickly averal disks tomportant dat

physical spin

ne at regular VPLEX Geo is

ajor reconfigu

he procedure Metadata Volues will force thh both Metada

h GeoSynchro

emote devicemes keep track is restored, stributed dev1 requires 2

y (gives array Upon restore data.

the clusters use this log t

your local ar, you mark thg rebuild to ‘

link-failure c system. The distributed s0 GB protectsimately 10 G a VPLEX Meurations and

uring and aft and efficientlo accommodta. EMC alsondles than th

r times — A si not useful

urations and/

outlined in VPmes and Meta

hem to be fullyata volumes an

ony CLI Guid

e, is that you ck of any blo the system uvices by sen bitmap logs

y death protee (of array or

partition, for to ‘send’ the

rray fails. Sinhe 2nd bitmapull’ data fro

could cause a logging volutorage spaces 320TB/N [nB of logging tro and VPLE

d are not used

er link outagly. EMC ate the I/O vo recommen

he storage vo

ingle

/or

PLEX adata y nd

e found

must cks

uses the ding at each ction) link)

r writes blocks

nce ap om the

a full me must

e. The n is the volume EX Geo. d for

ges.

volume, ds

olumes

Page 25: EMC VPLEX Overview and General Best Practices: Implementation ...

 

Becpraposon tpertheynor

If onusereq

Youuse

Logthinreqhigh

cause loggingctice is to mi

ssibility of da the back-endformance. Wy will experiemal healthy

ne array's daed to mirror thuired to migr

u can have med for which d

gging volumen device be fuuirement, loghest level of

Imp

g volumes arirror them acata loss on thd arrays. TheWhen a failureence very hig system activ

ata may, in thhe logging vorate at the sa

ore than one distributed d

s are supporully allocatedgging volume availability d

EMplementation

re critical to tross two or m

hese volumese RAID level we happens th

gh read/writevity, logging v

he future, be olumes shouame time.

e logging voluevice.

rted on thin dd. For similaes are active

during that ti

C VPLEX Oven Planning an

the functioninmore back-ens. In additionwithin the arrhat invoke the I/O activity volumes are

migrated to uld be chosen

ume, and can

devices hower reasons as during criticme.

Chap

erview and Gend Best Pract

ng of the sysnd arrays to en, they can beray should bee use of the

during the o not used.

another arrayn such that th

n select whic

ever it is a re the metadatal times and

pter 5: System

eneral Best Ptices Technic

stem, the bes eliminate thee striped intee considered logging voluutage. Durin

y, then the ahey will not b

ch logging vo

quirement thta volume must have t

Volumes

2 Practices cal Notes

st e ernally

d for high me then

ng

rrays be

olume is

hat the

the

25