8/31/2016

POOL|DavidRing

DavidRing
Virtualization&Storage

POOL

EMCVMAXDiskGroup&
PoolExpansion
(https://davidring.ie/2014/09/17/emc
vmaxdiskgrouppoolexpansion/)
September17,2014September24,2014
DavidRing VMAX
DiskGroup,EMC,
Expansion,HYPER,POOL,TDAT,VMAX
InordertoexpandaVMAXThinPoolwemustrstcreatetheadditionalDataDevices(TDATs)onthe
underlyingphysicalDiskGroup.ThisexampleoutlineshowtocalculateandcreatethoseTDATdevices
andthenexpandtheThinPoolwiththenewlycreatedTDATs.
Scenario:
ADiskGroupthatconsistedof64X600GBdiskdriveshasbeenincreasedto128X600GBDrives.EMC
willberequiredtocreateandapplyanupgradeBINinordertoexpandtheexistingDGto128Disks,
oncethishasbeencompletedwecanthenproceedwiththeTDATconguration.
AftergatheringthedetailswithrespecttotheexistingHyperandTDATsizes,thenwecandoaquick
calculationinordertodeterminethecountandsizeoftheTDATsrequired(Inthiscasetheconguration
isasimplereplicaoftheexistingconguration).
CalculatingtheHyperSize
Ifwetakethescenarioabovewherea64DriveDGhasbeendoubledto128Drives,witheachoftherst
64drivesintheDGhaving8HypersperdiskinaRAID5(3+1)conguration.

https://davidring.ie/tag/pool/
ListingtheexistingTDATswithinDiskGroup1:

1/17

8/31/2016

POOL|DavidRing

ListingtheexistingTDATswithinDiskGroup1:
symdevlistdisk_group1datadev
FromtheoutputofthiscommandwecanseethattheTDATsizeis206130MB,fromthiswecancalculate
theHypersizeused:
206130/3
=68710MBHyperSize

(hps://davering.les.wordpress.com/2014/09/hypers.jpg)
CalculatingthenumberofTDATsRequired

https://davidring.ie/tag/pool/

2/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2014/09/tdat.jpg)
Fromtheimageaboveyoucangatherthatforeachsetof4Drives(Raid53+1)werequireatotalof8x
TDATs.
8Hypers*64Disks
=512Hypers
=512/4(R53+1)
=128TDATs
CreatingtheNewTDATs
Creatingthenew128xTDATsrequiredonthenewlyadded64Disks:
symconguresidxxxcmdcreatedevcount=128,cong=Raid5,data_member_count=3,aribute=datadev,
emulation=FBA,size=206130mb,disk_group=1;Previewnop
symconguresidxxxcmdcreatedevcount=128,cong=Raid5,data_member_count=3,aribute=datadev,
emulation=FBA,size=206130mb,disk_group=1;Commitnop
NewTDATRangeReturned=1177:11F6
ListthenewTDATrangecreated:
symdevlistdatadevdisk_group1nonpooled
AddingthenewTDATstotheThinPool
AddingandenablingthenewTDATstotheexistingpoolandthusessentiallydoublingthecapacityof
thePool:
symconguresidxxxcmdadddev1177:11F6topoolPoolNametype=thin,member_state=enable;Preview
nop
symconguresidxxxcmdadddev1177:11F6topoolPoolNametype=thin,member_state=enable;Commit
nop

https://davidring.ie/tag/pool/
RebalancethePool

3/17

8/31/2016

POOL|DavidRing

RebalancethePool
ThiscommandwillrebalancetheallocatedextentsintheThinPoolnondisruptivelyacrossallofthe
enableddatadevicesinthepool.Automatedpoolrebalancingshouldberunwhenevernewdatadevices
areaddedtoapool.
symconguresidxxxcmdstartbalancingonpoolPoolNametype=thin;commitnop
Checkontherebalancingprogress:
symcfgsidxxxpoolPoolNameverifypoolStatebalancing
DisplayadetailedreportoftheexpandedPool
symcfgshowpoolPoolNamethindetailallmb|more
Thepoolnowconsistsof256TDATs(or1024Hypers!)
12Comments

EMCVMAXProvisioningMetaVolumes
andBindingtoaVirtualPoolvia
Unisphere&SYMCLI
(https://davidring.ie/2014/01/10/emc
vmaxprovisioningmetavolumesand
bindingtoavirtualpoolviaunisphere/)
January10,2014May16,2014
DavidRing VMAX
AUTOMETA,BIND,EMC
VMAX,META,METAVOLUME,POOL,TDEV
WhileIhavecoveredAutoMetahere(hps://davering.wordpress.com/2013/11/04/emcvmaxseing
autometaaributes/)therearetimeswhenamoregranularapproachisneeded.Thismayinvolve
creatingMetaMemberswithadierentsizethanwhatisconguredthroughAutoMetacreation.For
thisexamplewewillcreate64x480GigMetavolumeswitheachvolumeconsistingof16x30GigMeta
members.WewillthenBindthesevitualvolumes(TDEVs)toaPool.Thisexamplewillshowcasehow
simplethisisbyusingtheUnisphereconsole.
WhileIhavealsoaddedaSYMCLIexamplebelow,thishasalreadybeencoveredinagreatposthere
(hp://codyhosterman.com/2013/06/11/rstpostandaquicksymclishortcut/)byCody.
Note:ThemaximumMetaVolumethatcanbecreatedis60TBWhichconsistsof255X240GigMeta
Members.
ProvisioningMetaVolumesandBindingtoaVirtualPoolviaUnisphere:
https://davidring.ie/tag/pool/
1.ChooseCreateametavolumefromcommontasks:

4/17

8/31/2016

POOL|DavidRing

1.ChooseCreateametavolumefromcommontasks:

(hps://davering.les.wordpress.com/2014/01/12.jpg)
2.Emulation=FBA,stripedmetavolumesandVitualVolumesasweareusingVPandbindingtoathin
pool:

(hps://davering.les.wordpress.com/2014/01/2.jpg)
3.Thenumberofmetavolswewanttocreateis64witheachmetaconsistingof16members.Each
memberis30GiginsizetogiveatotalVolumesizeof480Gig:

https://davidring.ie/tag/pool/

5/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2014/01/3.jpg)

(hps://davering.les.wordpress.com/2014/01/4.jpg)

https://davidring.ie/tag/pool/

6/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2014/01/5.jpg)
Letstakealookatoneofthe64Metasthatwerecreated,meta2629:

https://davidring.ie/tag/pool/

7/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2014/01/5b1.jpg)
4.NavigatetotheThinPool(FC_VP)andthenchoosetheoptiontoBindthenewlyformedTDEVs:

https://davidring.ie/tag/pool/

8/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2014/01/6.jpg)
5.Selectthe64volumesandinthisexamplewechosetoPreallocatethefullcapacity:

https://davidring.ie/tag/pool/

9/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2014/01/7.jpg)
NowifwetakealookattheboundvolumesfortheFC_VPpoolwecanseeour64fullypreallocated
TDEVs:

https://davidring.ie/tag/pool/

10/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2014/01/8.jpg)
ProvisioningMetaVolumesandBindingtoaVirtualPoolviaSYMCLI:
#########################################
########No.OfThinDevices:64########
########SizeOfThinDevice480GB########
########No.MetaMemsPerTDEV16########
########MetaMembersize30GB########
########DrivePool:FC_VP########
#########################################
480/16=30GIGMetaMemberSize
64X16=1024Metamembers(1024IsCalulatedbyscriptbelow;justshowinghereforreference)
symconguresidxxxcmdcreatedevcount=64,size=480GB,emulation=a,cong=tdev,
meta_member_size=30GB,meta_cong=striped,preallocatesize=ALL,allocate_type=persistent,bindingto
Pool=FC_VP;vpreviewnop
symconguresidxxxcmdcreatedevcount=64,size=480GB,emulation=a,cong=tdev,
meta_member_size=30GB,meta_cong=striped,preallocatesize=ALL,allocate_type=persistent,bindingto
Pool=FC_VP;vcommitnop
##########ListPoolDetails##########
symcfgshowpoolFC_VPthindetailgb|more
symcfglisttdevpoolFC_VPgb|more
1Comment

https://davidring.ie/tag/pool/

11/17

8/31/2016

POOL|DavidRing

EMCVMAXRemovalOfATDEV
(https://davidring.ie/2013/12/31/emc
vmaxremovableofatdev/)
December31,2013June15,2015
DavidRing VMAX,VMware
DELETE,Dissolve
meta,EMCVMAX,maskingview,POOL,RECLAIM,Symmetrix,TDEV
YoumaynolongerhaveuseforaspecicTDEVvolumeinaStoragePoolandwanttofreethisspaceto
createanewvolumeorexpandanexistingvolume.ThesearethestepsinvolvedtodeletetheTDEVand
reclaimthisspaceinthePool.
ThisexampledetailshowtodeleteasingleTDEVvolumeinaStorageGroup.Anexampleofsucha
congurationisinthecasewhereasingleTDEVwasmappedandusedasadedicatedVMwareESX
bootvolumewithnoothervolumesbeingpresentintheStorageGroup.Scenario:Itmaybeacasewhere
anESXHostisbeingdecommissionedandwearereclaimingthespaceusedintheStoragePool.
Thestepsinvolvedare:
1.DeletetheESXHostMaskingView
2.RemoveESXBootvolume(TDEV)fromStoragegroup
3.DeletetheESXHostStorageGroup
4.MarktheTDEVasnot_ready
5.UnmaptheTDEVfromtheFAports
6.UnbindTDEVfromPool
7.(If)METAVolumeDissolve
8.DeletetheDevice
InordertoviewthelistofallTDEVscreatedinthePool(ESXBOOTpool):
symcfgsidxxxlisttdevgbthinpoolESXBOOT
ListallTDEVsinthesystem:
symcfgsidxxxlisttdev
1.DeletetheESXHostMaskingView
Listthealltheviews:
symaccesssidxxxlistview
RemovetheESX01_BOOT_MVMaskingView:
symaccesssidxxxdeleteviewnameESX01_BOOT_MV
2.RemoveESXBootvolume(TDEV)fromStoragegroup
ViewthedetailsofthestoragegroupESX01_BOOT_SGinordertogatherthecorrectdevID(for
example0234):
symaccesssidxxxlisttypeSTORAGE
https://davidring.ie/tag/pool/
symaccesssidxxxshowESX01_BOOT_SGtypestorage

12/17

8/31/2016

POOL|DavidRing

symaccesssidxxxshowESX01_BOOT_SGtypestorage
Removethedev0234fromtheStorageGroup:
symaccesssidxxxnameESX01_BOOT_SGtypestorageremovedevs0234
3.DeletetheESXHostStorageGroup
symaccesssidxxxnameESX01_BOOT_SGtypestoragedelete
4.MarktheTDEVasnot_ready
symdevsidxxxnot_ready0234
IfyourequiretochangethestatusofallthedevicesinaSG:
symsgsidxxxsgSGNamenot_ready
5.UnmaptheTDEVfromFAports
symconguresidxxxcmdunmapdev0234;PREVIEW
symconguresidxxxcmdunmapdev0234;COMMIT
IfyourequiretoUnmaparangeofdevs:
symconguresidxxxcmdunmapdev0234:0236;COMMIT
6.UnbindTDEVfromPool
symconguresidxxxcmdunbindtdev0234frompoolESXBOOT;PREVIEW
symconguresidxxxcmdunbindtdev0234frompoolESXBOOT;COMMIT
CheckiftheUnbindwassuccessful:
symcfgsidxxxlisttdevgbthinpoolESXBOOT
OncetheTDEVisunboundallpointerstothedatapoolareremovedandthosetracksthatwere
consumedbytheTDEVaremarkedasavailablespaceintheESXBOOTPool.
IfyourequiretoUnbindarangeofdevs:
symconguresidxxxcmdunbindtdev0234:0235frompoolESXBOOT;
7.Dissolve(IF)MetaVolume
symconguresidxxxcmddissolvemetadev0234;PREVIEW
symconguresidxxxcmddissolvemetadev0234;COMMIT
8.DeletetheDevice
symconguresidxxxcmddeletedev0234;PREVIEW
symconguresidxxxcmddeletedev0234;COMMIT
IfyourequiretoDeletearangeofdevs:
symconguresidxxxcmddeletedev0234:0235;COMMIT
ComrmDeletewassuccessful:
symcfgsidxxxlisttdev
##################################################################
FollowingonfromBurhanscommentbelow
BurhanHalilov(@7400N)(hps://twier.com/7400N)says:
Ifyouuseunmaptosymaccessdeleteviewin1.youcanskipsteps4and5
AlsoyoucanrunsymsgsidxxxsgyyyunbindbeforeyoudeletetheSGin3.andsavestep6.
Thesymcongurebind/unbindarebeingdepreciatedafterse7.6andreplacedwith
symdev/symsg/symdgbind/unbind
HereisanotherwayofachievingtheremovalaTDEVinaquickerfashionasperabove,butalso
includingthescenariowheretheSGisassociatedwithaFASTPolicy:
https://davidring.ie/tag/pool/
1.DeletetheESXHostMaskingView&UnmaptheTDEVfromFAports

13/17

8/31/2016

POOL|DavidRing

1.DeletetheESXHostMaskingView&UnmaptheTDEVfromFAports
symaccesssidxxxdeleteviewnameMVNAMEunmapNOP
2.IftheSGisassociatedwithaFastPolicythenitwillneedtobedisassociated
symfastsidxxxdisassociatesgSGNAMEfp_nameFPNAME
3.UnbindtheSGTDEV(s)fromPool
symsgsidxxxsgSGNAMEunbindNOP
4.RemovetheTDEVsfromthestoragegroup
symaccesssidxxxnameSGNAMEtypestorageremovedevsXXXX:XXXX
5.DeletetheStorageGroup
symaccesssidxxxnameSGNAMEtypestoragedeleteNOP
7.Dissolve(IF)MetaVolume
symconguresidxxxcmddissolvemetadevXXXX:XXXX;PREVIEWNOP
symconguresidxxxcmddissolvemetadevXXXX:XXXX;COMMITNOP
symcfglisttdev
8.DeletetheDevice(s)
symconguresidxxxcmddeletedevXXXX:XXXX;PREVIEWNOP
symconguresidxxxcmddeletedevXXXX:XXXX;COMMITNOP
symcfglisttdev
VMAX3TDEVDeletionProcess:
ExampleTDEV'0234'
1.DeletetheESXHostMaskingView&UnmaptheTDEVfromFAports:
symaccesssidxxxdeleteviewnameMVNAMEunmapNOP
2.RemovetheTDEVsfromthestoragegroup:
symaccesssidxxxnameSGNAMEtypestorageremovedevs0234
3.DeletetheStorageGroup:
symaccesssidxxxnameSGNAMEtypestoragedeleteNOP
4.FreeallAllocationsassociatedwiththedevice:
symconguresidxxxFREEALL0234NOP
IfyouneedtoFREEALLforarangeofdevs:
symdevsid289FREEALLDEVS0234:0236NOP
5.DeletetheDevice(s)
symconguresidxxxcmddeletedev0234;PREVIEWNOP
symconguresidxxxcmddeletedev0234;COMMITNOP
symcfglisttdev
IfyouneedtodeletearangeofTDEVsonVMAX3:
Gatherdetails:
symaccesssidXXXlistviewnameMVNAMEdetail
https://davidring.ie/tag/pool/
symaccesssidXXXlisttypestoragenameSGNAME

14/17

8/31/2016

POOL|DavidRing

symaccesssidXXXlisttypestoragenameSGNAME
symaccesssidXXXtypestorageshowSGNAME
Delete:
symaccesssidXXXnameSGNAMEtypestorageremovedevs00CE:00D0
symdevsidXXXFREEALLDEVS00CE:00D0NOP
symconguresidXXXcmddeletedev00CE:00D0;COMMITNOP
8Comments

EMCVNXPOOL
PERFORMANCEPLANNING
(https://davidring.ie/2013/07/20/emcvnx
poolperformanceplanning/)
July20,2013July21,2013
DavidRing VNX
EMC,FASTVP,IOPS,
PERFORMANCE,POOL,VNX
InthispostIwillgiveaguidelineonhowtocalculatetherequireddrivecountforaVNXPoolbasedon
Throughputperformance(IOPS).ThisisonlyaRoughOrderofMagnitude(ROM)whichwillgivean
approximationtotherequireddrivecount.PleaseconsultEMC/VCE/PartnerTechnicalsalesastheywill
haveaccesstothelatestsizingtoolsinordertocalculatetheexactdrivecountforyourworload.
FirstlyweneedtoconsidertheimpactthedierentRAIDtypeswillhaveonthedrivecalculation
(ChoosingyourRAIDtypeisforanotherdiscussion).ThemaindierencebetweentheRAIDtypesisthe
randomwriteperformance.TheperformanceofReadIOPSismuchthesameacrossalltheseRAID
types.RAID1/0requirestwodiskoperationsforeachhostwrite,RAID5requiresfouroperationsper
hostwriteandRAID6requiressixoperationsperhostwrite.Tosummarisehereishowthebackend
RAIDpenaltiesdier:
MirroredRAID1/0:1HostWrite=2Writes
ParityRAID5:1HostWrite=2Reads+2Writes
ParityRAID6:1HostWrite=3Reads+3Writes
SotakingtheaboveimplicationsthatHostwriteshaveonthebackendRAIDtypesherearethe
calculationsthatcanbeusedtodeterminetherequiredDriveIOPS(Backend):
ParityRAID5:DriveIOPS=ReadIOPS+4*WriteIOPS
ParityRAID6:DriveIOPS=ReadIOPS+6*WriteIOPS
MirroredRAID1/0:DriveIOPS=ReadIOPS+2*WriteIOPS
ExampleRAID_5IOPSCalculation
HOSTWORKLOAD:20,000RandomIOPS,80%Reads,20%Writes
UsingRAID_5asanexamplewithanI/Oratioof80/20withatotalHostIOPSrequirementof20,000we
https://davidring.ie/tag/pool/
cancalculatetheDriveIOPS:

15/17

8/31/2016

POOL|DavidRing

cancalculatetheDriveIOPS:
DriveIOPS=(0.8*20,000+4*(0.2*20,000))
DriveIOPS=32,000
DetermineyourdiskcountBasedonIOPS:
UsingtheprovidedtablewecandoaquickcalculationtoestimatetherequireddrivecountforthePool.
TheseexamplesandtheestimatedIOPScountisbasedonSmallblockrandomI/OsimilartotheI/Osof
databasesystems(16KBorLess).ThedriveIOPSgureslistedhereareusedasastartingpointfor16KB
orlessforanyI/0largerthan16KBtherewillbeareductionintheIOPgureslistedbelow.

(hps://davering.les.wordpress.com/2013/07/iops_disk1.jpg)
TakeitthatwewanttouseallSAS15Kdrivesinaheterogeneouspoolasarstexample:
Giventherequirementfor32,000IOPSwecandoaquickcalculationtogettherequireddrivecountto
servicethisworkload:
32,000IOPS/180IOPSPERDISK=177.8Disks
AsthisisaRAID_5basedpooltheprivateRaidgroupswillbeusing4+1thusroundingthedrivecount
to180willgiveus36xRAID_54+1privateraidgroups.
NowasasecondexampleassumethatatwotieredFASTVPHomogenousPoolisthepreferredoption
usingFlashandSASdrivesinatwotieredapproach.Using5FlashDrivesinaFASTVPPool
congurationthenwewouldvastlyreducethecountofSASdrivesasfollows:
5X3500IOPS(FlashDrives)=17,500IOPSservicedbythe5FlashDrives
Thisleavesuswith18,500IOPSthatwillneedtobeservicedbySAS15Kdriveswhichwouldhavea
totaldrivecountrequirementof:
18,500/180=102.7
AgainusingaRAID_54+1congurationwewouldhaveatotaldrivecountof105forSAS.
Thusgivingareductionof70(180110)drivescomparedtothepreviousexampleofusinga
HeterogeneousVPPoolofallSAS15Kdrives.ThepowerofFLASH!

https://davidring.ie/tag/pool/
(hps://davering.les.wordpress.com/2013/07/blog_iops1.jpg)

16/17

8/31/2016

POOL|DavidRing

(hps://davering.les.wordpress.com/2013/07/blog_iops1.jpg)
NOTE:TherstfourdrivesinaVNXarethesystem(Vault)drivesandcannotbeusedinapool.
10Comments
DavidRing(hps://davidring.ie/)
BlogatWordPress.com.(hps://hps://wordpress.com//?ref=footer_blog)

https://davidring.ie/tag/pool/

17/17