Professional Documents
Culture Documents
Administration Guide
Release 11.0
MK-92HNAS012-00
20112012Hitachi,Ltd.Allrightsreserved.
Nopartofthispublicationmaybereproducedortransmittedinanyformorbyany
means,electronicormechanical,includingphotocopyingandrecording,orstoredin
adatabaseorretrievalsystemforanypurposewithouttheexpresswrittenpermission
ofHitachi,Ltd.
Hitachi,Ltd.,reservestherighttomakechangestothisdocumentatanytimewithout
noticeandassumesnoresponsibilityforitsuse.Thisdocumentcontainsthemost
currentinformationavailableatthetimeofpublication.Whenneworrevised
informationbecomesavailable,thisentiredocumentwillbeupdatedanddistributed
toallregisteredusers.
Someofthefeaturesdescribedinthisdocumentmightnotbecurrentlyavailable.
Refertothemostrecentproductannouncementforinformationaboutfeatureand
productavailability,orcontactHitachiDataSystemsCorporationathttps://
portal.hds.com.
Notice:Hitachi,Ltd.,productsandservicescanbeorderedonlyunderthetermsand
conditionsoftheapplicableHitachiDataSystemsCorporationagreements.Theuseof
Hitachi,Ltd.,productsisgovernedbythetermsofyouragreementswithHitachi
DataSystemsCorporation.
HitachiisaregisteredtrademarkofHitachi,Ltd.,intheUnitedStatesandother
countries.HitachiDataSystemsisaregisteredtrademarkandservicemarkof
Hitachi,Ltd.,intheUnitedStatesandothercountries.
Archivas,BlueArc,DynamicProvisioning,EssentialNASPlatform,HiCommand,Hi
Track,ShadowImage,Tagmaserve,Tagmasoft,Tagmasolve,Tagmastore,TrueCopy,
UniversalStarNetwork,andUniversalStoragePlatformareregisteredtrademarksof
HitachiDataSystemsCorporation.
AIX,AS/400,DB2,Domino,DS8000,EnterpriseStorageServer,ESCON,FICON,
FlashCopy,IBM,Lotus,OS/390,RS6000,S/390,Systemz9,Systemz10,Tivoli,VM/
ESA,z/OS,z9,zSeries,z/VM,z/VSEareregisteredtrademarksandDS6000,MVS,and
z10aretrademarksofInternationalBusinessMachinesCorporation.
Allothertrademarks,servicemarks,andcompanynamesinthisdocumentorwebsite
arepropertiesoftheirrespectiveowners.
MicrosoftproductscreenshotsarereprintedwithpermissionfromMicrosoft
Corporation.
ii
Notice
HitachiDataSystemsproductsandservicescanbeorderedonlyunderthetermsandconditionsof
HitachiDataSystemsapplicableagreements.TheuseofHitachiDataSystemsproductsisgoverned
bythetermsofyouragreementswithHitachiDataSystems.
ThisproductincludessoftwaredevelopedbytheOpenSSLProjectforuseintheOpenSSLToolkit
(http://www.openssl.org/).SomepartsofADCuseopensourcecodefromNetworkAppliance,Inc.
andTraakan,Inc.
PartofthesoftwareembeddedinthisproductisgSOAPsoftware.PortionscreatedbygSOAPare
copyright20012009RobertA.VanEngelen,GeniviaInc.Allrightsreserved.Thesoftwareinthis
productwasinpartprovidedbyGeniviaInc.andanyexpressorimpliedwarranties,including,but
notlimitedto,theimpliedwarrantiesofmerchantabilityandfitnessforaparticularpurposeare
disclaimed.Innoeventshalltheauthorbeliableforanydirect,indirect,incidental,special,
exemplary,orconsequentialdamages(including,butnotlimitedto,procurementofsubstitute
goodsorservices;lossofuse,data,orprofits;orbusinessinterruption)howevercausedandonany
theoryofliability,whetherincontract,strictliability,ortort(includingnegligenceorotherwise)
arisinginanywayoutoftheuseofthissoftware,evenifadvisedofthepossibilityofsuchdamage.
TheproductdescribedinthisguidemaybeprotectedbyoneormoreU.S.patents,foreignpatents,
orpendingapplications.
iii
Date
Description
MK92HNAS01200
August2012
Firstpublication
Contact
HitachiDataSystems
750CentralExpressway
SantaClara,California950502627
https://portal.hds.com
NorthAmerica:18004460744
iv
Hitachi branded
BlueArc branded
NASPlatform3080G2
Mercury50server
NASPlatform3080G2
Mercury55server
NASPlatform3090G1
Mercury100server
NASPlatform3090G2
Mercury110server
NASOS
BlueArcOS(BOS)
Related Documents
Other publications available on the System Management Unit (SMU) are:
YL
Release Notes: Gives late-breaking news about the system software, and provides
any corrections or additions to the included documentation.
Table of Contents
1 Storage Management
Storage Management Components . . . . . . . . . . . . . . . . . . . . . . . . 1
System Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
System Drive Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Tiered Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
. . . . . . . . . . . . . . . . . . . . . . . . . . 27
vii
Table of Contents
viii
Table of Contents
ix
Table of Contents
Storage Management
System Drives
Systemdrives(SDs)arethebasic(logical)storageelementusedbytheserver.
StoragesubsystemsuseRAIDcontrollerstoaggregatemultiplephysicaldisks
intoSDs.FormoreinformationaboutconfiguringandusingSDs,seeSystem
DrivesandSystemDriveGroups.
System Drive
Groups
Withmanystoragesubsystems,systemdrives(SDs)arelimitedto2TB
each.However,withtodayslargephysicaldisks,RAIDarraysmustbe
considerablylargerthan2TBinordertomakeefficientuseofspace.System
administratorsoftenbuildlargeRAIDarrays(oftencalledRAIDgroupsor
volumegroups)andthendividethemintosystemdrives(SDs)of2TBor
less.NotethateachSDinaRAIDgrouptypicallyusessomespaceoneach
diskintheRAIDgroup.SDsaretheunitsofstoragethattheserverseesand
manages(theserverorganizesSDsintostoragepools,whichthencontainthe
filesystems).
Whenperformingwriteoperations,iftheserverweretowritesimultaneously
tomultipleSDsinthesameRAIDgroup,itwouldincreaseheadmovement,
reducingbothperformanceandtheexpectedlifeofthedisks.TheNASserver
hasamechanismtoallowittowritetoonlyoneSDinaRAIDgroupatany
onetime.BydefiningSDgroups,youtelltheserverwhichSDsareineach
Storage Management
RAIDgroupandgiveittheinformationitneedstooptimizewrite
performance.
ForHighperformanceNASPlatform/clusters,systemdrivegroupsare
supportedonSeries2000andSeries3000storageservers,butonlySeries3000
HighperformanceNASPlatforms/clusterstakeadvantageofthis
functionality.AllHitachiNASPlatforms/clusterstakeadvantageofsystem
drivegroups.
Asystemdrivethatisnotinanygroupistreatedasifitwereinagroupofits
own.
FormoreinformationaboutSDgroups,seeSystemDrivesandSystemDrive
Groups.
Storage Pools
Astoragepool(knownasaspaninthecommandlineinterface)isthelogical
containerforacollectionofoneormoresystemdrives(SDs).Therearetwo
typesofstoragepools:
Anuntieredstoragepool:Anuntieredstoragepoolismadeupsystem
drives(SDs)createdononeormorestoragesubsystemswithinthesame
tierofstorage(storagesubsystemswithinthesametierofstorage(storage
subsystemswithcomparableperformancecharacteristics).Tocreatean
untieredstoragepool,theremustbeatleastoneavailableandunused
systemdriveonthestoragesubsystemfromwhichtheSDsinthestorage
poolwillbetaken.
Atieredstoragepool:Atieredstoragepoolismadeupsystemdrives
(SDs)createdonstoragesubsystems(RAIDarrays)withdifferent
performancecharacteristics.Typically,atieredstoragepoolismadeupof
SDsfromhighperformancestoragesuchasflashmemory,andSDsfrom
lowerperformancestoragesuchasFibreChannelorSATA.Youcan,
however,createatieredstoragepoolfromSDsonstoragesubsystems
usinganystoragetechnology.Formoreinformationabouttieredstorage
pools,seeTieredStoragePools,onpage3.
TieredstoragepoolsaresupportedonlyonHitachiNASPlatforms/Clusters.
Formoreinformationaboutstoragetiers,andthetechnologiesthatmakeup
eachtier,seeUnderstandingTieredStorage.
Storagepools:
CanbeexpandedasadditionalSDsarecreatedinthestoragesubsystem,
andanSDcangrowtoamaximumof1PBor256SDs.
Expandingastoragepooldoesnotinterruptnetworkclientaccessto
storageresources.Byallocatingasharedpoolofstorageformultipleusers
andallocatingspacedynamically(thinprovisioning),aserver/cluster
supportsoversubscription,sharingspacethataccommodatesthepeak
requirementsofindividualclientswhilesavingtheoverheadassociated
Storage Pools
withsustainingunnecessarystorage.RefertotheFileServices
AdministrationGuideformoreinformationonthinprovisioning.
Containasinglestripesetwhencreated.Eachtimethestoragepoolis
expandedanotherstripesetisadded,uptoamaximumof64stripesets
(meaningthat,aftercreation,astoragepoolcanbeexpandedamaximum
of63times).
Canholdupto128filesystems,centralizingandsimplifyingmanagement
ofitscomponentfilesystems.Forexample,thesettingsappliedtoa
storagepoolcaneitheralloworconstraintheexpansionofallfilesystems
inthestoragepool.
Storagepoolsaremadeupofmultiplesmallallocationsofstoragecalled
chunks.Thesizeofthechunksinastoragepoolisdefinedwhenthestorage
pooliscreated.Astoragepoolcancontainuptoamaximumof16,384chunks.
Inturn,anindividualfilesystemcancontainuptoamaximumof1023
chunks.Planningthechunksizeisanimportantconsiderationwhencreating
storagepools,fortworeasons:
Tiered Storage
Pools
Chunksdefinetheincrementbywhichfilesystemswillgrowwhenthey
expand.
Asafilesystemcontainsafinitenumberofchunks,thechunksizeplacesa
limitonthefuturegrowthoffilesystemsinastoragepool.
Currently,atieredstoragepoolmusthavetwotiers:
Tier0isusedformetadata,andthebestperformingstorageshouldbe
designatedasTier0.
Tier1isusedforuserdata.
Formoreinformationaboutstoragetiers,andthetechnologiesthatmakeup
eachtier,seeUnderstandingTieredStorage.
TieredstoragepoolsaresupportedonlyonHitachiNASPlatforms/Clusters.
Tocreateatieredstoragepool,theremustbeatleastoneavailableandunused
SDoneachofthestoragesubsystemsfromwhichthestoragepooltierswillbe
made.Whencreatingatieredstoragepool:
UsingWebManager,thefirsttiercreatedisthemetadatatier(Tier0).The
userdatatier(Tier1)canbecreatedlater,butcannotbecreatedbeforethe
metadatatier.
UsingtheCLI(CommandLineInterface),however,tierscanbecreatedin
anyorder.
Duringnormaloperation,onetierofatieredstoragepoolmaybecomefilled
beforetheothertier.Insuchacase,onetierofthestoragepoolcanbe
expanded(byaddingatleastoneSD)withoutexpandingtheothertier.Note
that,whenexpandingatier,youmustmakecertainthattheSDbeingadded
tothetierhasthesameperformancecharacteristicsastheSDsalreadyinthe
tier.
Storage Management
Creating a
Storage Pool
GivenavailabilityofSDs,administratorscancreateastoragepoolatanytime.
Atthetimeofcreation,astoragepoolcancontainupto32SDs;later,storage
poolscanexpandbyaddingmoreSDsuntilthetotalsizeofthepoolhas
reachedupto1PB.Forinstructions,seeExpandingaStoragePooloraTier,
onpage16.
Whencreatingatieredstoragepool,toattainoptimalperformance,makesure
thattheSDsofthemetadatatier(Tier0)areonthehighestperformance
storage.
Note:IfDynamicWriteBalancingisnotenabled,orifyoursystemdoesnot
supportDynamicWriteBalancing,aftercreatinganewstoragepool,useas
manydiskdrivesaspossibleandkeepSDsaslargeaspossibletoattainoptimal
performance.Afterthestoragepoolhasbeencreated,smallerfilesystemscan
becreatedinthepoolformoregranularstorageprovisioning.Formore
informationonDynamicWriteBalancing,seeSystemDriveGroupsand
DynamicWriteBalancing.
Tocreateastoragepool:
1. NavigatetotheStoragePoolspage.
FromtheStorageManagementheading,clickStoragePoolstodisplay
theStoragePoolspage:
ClickcreatetostarttheStoragePoolWizard.
2. Selectthetypeofstoragepooltocreate:
Selectwhichtypeofstoragepoolyouwanttocreate.
Tocreate:
Anuntieredstoragepool,clickAnUntieredStoragePool.
Atieredstoragepool,clickATieredStoragePool.
TheStoragePoolWizardpageopens,andyoucanselecttheSDsforeither
thestoragepool(foranuntieredstoragepool)orthemetadatatier(Tier0)
ofatieredstoragepool.
3. SelecttheSDsforthestoragepool/tier.
UsingtheStoragePoolWizardpage,fromthelistofavailableSDsonthe
page,selecttheSDsforthestoragepool/tier,andspecifyboththestorage
poollabelandtheguidelinechunksize.
Storage Management
Thefollowingtabledescribesthefieldsinthispage:
Item/Field
Description
ID(Label)
SDnumberassignedbytheserverandtheSDlabel.Appearsinthe
eventlog.
FirstSDinSD
Group
ListstheSDlabelofthefirstSDoftheSDGroup.
Capacity
SDssize.
Manufacturer
ManufactureroftheRAIDarraycontainingthedisksonwhichtheSD
wascreated.ForinformationaboutthesupportedRAIDArrays,refer
totheSupportedStorageSubsystems.
Comment/
RackName
Racknameandanyadditionalinformation.
DiskType
TypeofSD;forexample,Fibre,SATA,orSAS.
DiskSize
Size(usable)ofthedisksmakinguptheSD.
Item/Field
Description
Superflush
Settings
Thesesettingscontrolthesuperflushsettingsusedforthestorage
pool.Superflushisatechniquethattheserverusestooptimizewriting
toRAID5systemdrives(SDs).Bywritingawholestripelineatatime,
theserverallowstheRAIDcontrollertogenerateparitymore
efficiently.
Width:NumberofphysicaldisksintheSD.Tellstheserverhow
manydata(nonparity)diskstheSDhas.IftheSDusesmultiple
stripesets,indicatesthenumberofdatadisksinasinglestripeset.
StripeSize:DataformatsizeusedforwritingtoaSD.Tellsthe
servertheSDsstripesize,inkilobytes.Thestripesizeisthe
amountofdatathattheRAIDcontrollerwritestoasingledisk
beforemovingontothenextdisk.
ForBlueArcstoragearrays,StripeSize*Widthmustbelessthanor
equalto4064KB.
StoragePool
Label
Thenameofthenewstoragepool.Storagepoollabelsarenotcase
sensitive,buttheydopreservecase(labelswillbekeptasentered,in
anycombinationofupperandlowercasecharacters).Also,storage
poollabelsmaynotcontainspacesoranyofthefollowingspecial
characters:"&*/;:<>?\|.
Note:Storagepoollabelsmustbeuniquewithinaserverorcluster.
Also,astoragepoolcannothavethesamelabelasafilesystem.
Youshouldlabelstoragepoolsforthedatatheywillcontain.Also,
makesureyourstoragepoollabelsareuniqueacrossyourentiresite,
incaseyouneedtomovethestoragepool.
Guideline
ChunkSize
Thechunksizethatwillbeusedforstoragepoolexpansion.Youcan
usethedefaultchunksizesuggestedbythesystem,oryoucanchoose
acustomchunksize.
Toselectthedefaultchunksize,clickDefault.Thedefaultchunksize
willbeshownintheadjacenttextbox,andisautomaticallybe
calculatedtoequal[storagepoolsize]/256.
Tosetacustomchunksize,clickCustomandenterasizebetween
512MBand1TB.HitachiDataSystemsSupportCenterdoesnot
recommendchunksizeslessthan5GB.
SelectoneormoreSDsforuseinbuildingthenewstoragepool/tier.To
selectanSD,fillthecheckboxnexttotheID(Label).
AnuntieredstoragepoolcannotcontainSDsonRAIDarrayswith
differentmanufacturers,disktypes,orRAIDlevels.Anyattempttocreate
astoragepoolfromsuchdissimilarSDswillberefused.
AtieredstoragepoolcancontainSDsonRAIDarrayswithdifferent
manufacturers,ordisktypes,aslongastheyareindifferenttiers.Atiered
storagepoolcannot,however,containSDswithdifferentRAIDlevels.
AnyattempttocreateastoragepoolwithSDsthathavedifferentRAID
levelswillberefused.
Forthehighestlevelofperformanceandresiliencyinanuntieredstorage
poolorinatierofatieredstoragepool,HitachiDataSystemsSupport
Storage Management
CenterstronglyrecommendsthatallSDsbeofthesamecapacity,width,
andstripesize,anddiskssize;however,afterfirstacknowledginga
warningprompt,youcancreateastoragepoolwithSDsthatarenot
identicallyconfigured.
4. Applysettings.
Verifyyoursettings,thenclicknexttodisplayasummarypage.The
summarypagedisplaysthesettingsthatwillbeusedtocreatethestorage
pool/tier.
IfyouhavemirroredSDs,fordisasterpreparednessorreplication
purposes,andyouwanttheservertotrytoreestablishthemirror
relationship,filltheLookForMirroredSystemDrivescheckbox.
Onceyouhavereviewedtheinformation,clickcreatetocreatethestorage
pool/tier.
Note:Afterthestoragepoolhasbeencreated,itcanbefilledwithfile
systems.Formoreinformation,refertotheFileServicesAdministration
Guide.
5. Completethecreationofthestoragepoolortier.
Afterclickingcreateinthelaststep,youwillseeoneofthedialogsshown
below.Ifyouarecreating:
Anuntieredfilesystem,thefollowingdialogwillappear:
Youcannowclickyestocreatefilesystems,orclicknoreturntothe
StoragePoolspage.
Thefirsttierofatieredfilesystem,thefollowingdialogwillappear:
Youcannowclickyestocreatethesecondtierfilesystems,orclickno
returntotheStoragePoolspage.
Ifyouchoosenottocreatethesecondtiernow,youcanadditatalater
time,butyoucannotcreatefilesystemsinthisstoragepooluntilthe
secondtierhasbeenadded.Forinformationonaddingthesecondtier,
seeAddingtheUserDataTier,onpage11.
Ifyouchoosetocreatethesecondtierofatieredstoragepool,seethe
step
SelecttheSDsforthesecondtierofastoragepool.
Thesecondtierofatieredfilesystem,thefollowingdialogwill
appear:
Youcannowclickyestocreatefilesystems,orclicknoreturntothe
StoragePoolspage.
6. SelecttheSDsforthesecondtierofastoragepool.
Storage Management
UsingtheStoragePoolWizardpage,fromthelistofavailableSDsonthe
page,selecttheSDsforthesecond(userdata)tier.ToselectanSDforthe
tier,fillthecheckboxnexttotheSDlabel.
Foradescriptionofthefieldsinthispage,see
,onpage5.
SelecttheSDsforthestoragepool/tier.
Verifyyoursettings,thenclicknexttodisplayasummarypage.
7. Reviewandapplysettings.
Thesummarypagedisplaysthesettingsthatwillbeusedtocreatethe
storagepool/tier.
IfyouhavemirroredSDs,fordisasterpreparednessorreplication
purposes,andyouwanttheservertotrytoreestablishthemirror
relationship,filltheLookForMirroredSystemDrivescheckbox.
10
Onceyouhavereviewedtheinformation,clickaddtocreatethesecond
tierofthestoragepool.
Note:Afterthestoragepoolhasbeencreated,itcanbefilledwithfile
systems.Formoreinformation,refertotheFileServicesAdministration
Guide.
8. Completethecreationofthestoragepoolortier.
Afterclickingaddinthelaststep,youwillseethefollowingdialog:
Youcannowclickyestocreatefilesystems,orclicknoreturntothe
StoragePoolspage.
Ifyoucreatedatieredstoragepool,butonlydefinedtheSDsforonetier,you
havedefinedthemetadatatier(Tier0),butnottheuserdatatier(Tier1).Until
theuserdatatierhasbeencreated,youcannotcreatefilesystemsinthis
storagepool.
Note:Youcannotaddatiertoastoragepoolthatwascreatedasanuntiered
storagepool.
Toaddatiertoastoragepool:
1. NavigatetotheStoragePoolspage.
11
Storage Management
FromtheStorageManagementheading,clickStoragePoolstodisplay
theStoragePoolspage:
2. Selectthestoragepooltowhichyouwanttoaddthetier.
ClickdetailstodisplaytheStoragePoolDetailspageforthestoragepool
towhichyouwantaddtheuserdatatier.
3. Selectthestoragepooltowhichyouwanttoaddthetier.
12
Clickdetailstodisplaythedetailsofthestoragepooltowhichyouwant
addtheuserdatatier.
4. DisplaytheStoragePoolWizard.
TodisplaytheStoragePoolWizardpage,sothatyoucancreatetheuser
datatier,clicktheAddaTierlink.
13
Storage Management
Foradescriptionofthefieldsonthispage,see
SelecttheSDsforthestoragepool/tier.
,onpage5.
5. SelecttheSDstomakeuptheuserdatatier.
UsingtheStoragePoolWizardpage,fromthelistofavailableSDsonthe
page,selecttheSDsforthesecond(userdata)tier.ToselectanSDforthe
tier,fillthecheckboxnexttotheSDlabel.
Foradescriptionofthefieldsinthispage,see
,onpage5.
SelecttheSDsforthestoragepool/tier.
Verifyyoursettings,thenclicknexttodisplayasummarypage.
6. Reviewandapplysettings.
Thesummarypagedisplaysthesettingsthatwillbeusedtocreatethe
storagepool/tier.
14
IfyouhavemirroredSDs,fordisasterpreparednessorreplication
purposes,andyouwanttheservertotrytoreestablishthemirror
relationship,filltheLookForMirroredSystemDrivescheckbox.
Onceyouhavereviewedtheinformation,clickaddtocreatethesecond
tierofthestoragepool.
Note:Afterthestoragepoolhasbeencreated,itcanbefilledwithfile
systems.Formoreinformation,refertotheFileServicesAdministration
Guide.
7. Completethecreationofthestoragepoolortier.
Afterclickingaddinthelaststep,youwillseethefollowingdialog:
Youcannowclickyestocreateafilesystem,orclicknoreturntothe
StoragePoolspage.Ifyouchoosetocreateafilesystem,theCreateFile
Systempagewillappear.
Deleting Storage
Pools
Astoragepoolthatdoesnotcontainfilesystemscanbedeletedatanytime;
otherwise,deletethefilesystemsfirst.Afterthepoolhasbeendeleted,itsSDs
becomefreeandavailableforusebyneworexistingstoragepools.
Todeleteastoragepool:
1. NavigatetotheStoragePoolspage.
15
Storage Management
FromtheStorageManagementpage,clickStoragePoolstodisplaythe
StoragePoolspage.
2. Selectastoragepool.
Fortheselectedstoragepoolclickdetails.
3. Deletethestoragepool.
Clickdelete,thenOKtoconfirm.
Expanding a
Storage Pool or a
Tier
ExpandastoragepooloratierofatieredstoragepoolbyaddingmoreSDsto
thepool/tier.Anuntieredstoragepoolcanbeexpandedtoprovidemore
usablestorageforfilesystems.Eithertierofatieredstoragepoolcanbe
expandedtoprovidemoreusablestorage;expandTier0toprovidemore
spaceformetadataorexpandTier1toprovidemorespaceforuserdata.A
storagepooloratiercanbeexpandedatanytimeandwithoutinterrupting
servicetoclients.Astoragepoolcanbeexpandeduntilitreachesanyofthe
followinglimits:
Atotalsizeof1PB.
Amaximumof16,384chunks.
Amaximumof256SDs.
Amaximumof64stripesets.Anewlycreatedstoragepoolcontainsone
stripeset,andonestripesetisaddedeverytimethestoragepoolis
expanded(meaningthatastoragepoolcanbeexpandedupto63times).
Note:IfDynamicWriteBalancingisnotenabled,orifyoursystemdoesnot
supportDynamicWriteBalancing,whenexpandingthestoragepool,useas
manydiskdrivesaspossibleandkeepSDsaslargeaspossibletoattainoptimal
performance.Afterthestoragepoolhasbeencreated,smallerfilesystemscan
becreatedinthepoolformoregranularstorageprovisioning.Formore
informationonDynamicWriteBalancing,refertotheSystemDriveGroups
16
andDynamicWriteBalancing.
Toexpandastoragepool/tier:
1. NavigatetotheStoragePoolspage.
FromtheStorageManagementpage,clickStoragePoolstodisplaythe
StoragePoolspage:
2. Selectthestoragepoolorthestoragepoolthathasthetieryouwantto
expand.
Fillthecheckboxnexttothelabelofthestoragepoolyouwanttoexpand,
andclickdetailstodisplaytheStoragePoolDetailspage.
17
Storage Management
Ifthestoragepoolisanuntieredstoragepool,theStoragePool
Detailspagelookslikethefollowing:
Todisplaytheavailablesystemdrivestoaddtothestoragepool,click
expand.TheStoragePoolWizardpageisdisplayed.SeeDisplaythe
availablesystemdrive(s)toaddtothestoragepool.,onpage19for
moreinformation.
18
Ifthestoragepoolisatieredstoragepool,theStoragePoolDetails
pagelookslikethefollowing:
Todisplaytheavailablesystemdrivestoaddtoatier,selectthetier
youwanttoexpand,andclickexpand.TheStoragePoolWizardpage
isdisplayed.
3. Displaytheavailablesystemdrive(s)toaddtothestoragepool.
Todisplaytheavailablesystemdrivestoaddtothestoragepool,click
expand.TheStoragePoolWizardpageisdisplayed.
Ifyouareexpandinganuntieredstoragepool,theStoragePool
Wizardpagelookslikethefollowing:
19
Storage Management
Ifyouareexpandingatieredstoragepool,theStoragePoolWizard
pagelookslikethefollowing:
4. Selectthesystemdrive(s)toaddtothestoragepool.
20
Fillthecheckboxnexttothelabelofthesystemdriveyouwanttoadd,
thenclicknexttodisplaythenextStoragePoolWizardpage.
5. AddtheSDstothestoragepool/tier.
Clickexpand.
Reducing the
Size of a Storage
Pool
Denying Access
to a Storage Pool
Thesizeofastoragepoolcannotbereduced.
Denyingaccesstoastoragepool:
Removestheassociationbetweenthefilesystemshostedbythepooland
theirVirtualServer(EVS).Onceaccesstothepoolisallowed,filesystems
mustbereassociatedwithanEVS.Accesstoastoragepoolshouldonlybe
deniedduringaplannedmaintenancewindowandonlyatthedirection
ofHitachiDataSystemsSupportCenter.
Removesthestoragepoolanditsfilesystemsfrommemory,meaningthat
thosefilesystemsarenolongervisibleusingWebManager.
DeniesaccesstotheSDsthathostthestoragepool,withtheeffectthatthe
poolisnotreloadedthenexttimetheclusternode/serverboots.
IrrevocablydeletesalldataassociatedwithfilesystemsintheNVRAM
buffer,withtheeffectofdestroyingdataunlessallfilesystemshostedby
thestoragepoolwereunmountedsuccessfullybeforeaccesstothestorage
poolwasdenied.
Note:Thetechniqueofdenyingaccesstoastoragepoolcanbeusedtoprepare
astoragearrayforphysicalrelocation.Thestoragepoolanditscontentsarenot
Storage Subsystem Administration Guide
21
Storage Management
lostordeleted,andaccesscanbereturnedwhenneeded.
Theprocedurefordenyingaccesstoastoragepoolinvolvesunmountingeach
filesysteminthepool,thenchangingthepoolsaccessmode.Forinstructions
onunmountingfilesystems,refertotheFileServicesAdministrationGuide.
Todenyaccesstoastoragepool:
1. NavigatetotheFileSystemspage.
FromtheStorageManagementpage,clickFileSystemstodisplaythe
FileSystemspage:
2. Unmounteveryfilesysteminthestoragepool.
Selectallthefilesystemsinthestoragepooltowhichyouwanttodeny
access,thenclickunmount;intheconfirmationdialog,clickOK.
3. Selectastoragepoolanddenyaccess.
ClicktheStoragePoolsshortcuttodisplayalistofallpools,thenselecta
particularstoragepoolandclickDenyAccess;intheconfirmationdialog,
clickOK.
Thiswillalsoremovethepoolfromthestoragepoolslist,butitwillnotbe
deleted.
Allowing Access
to a Storage Pool
Thisprocedurerestoresaccesstoastoragepool,butcanalsobeusedwhena
storagearraypreviouslyownedbyanotherserverhasbeenphysically
relocatedtobeservedbyanotherserver.Theprocessrestoresaccesstothe
SDsthatbelongtothestoragepool,thenrestoresaccesstothepoolitself.
Toallowaccesstoastoragepool:
1. NavigatetotheSystemDrivespage.
22
FromtheStorageManagementpage,clickSystemDrivestodisplaythe
SystemDrivespage:
2. ModifySDaccess.
SelectoneoftheSDsbelongingtothestoragepool,thenclickAllow
Access.
3. Modifystoragepoolaccess.
Selectapoolandclickdetails.IntheDetailspageforthatstoragepool,
clickAllowAccess;then,intheconfirmationpage,clickOK.
Note:Tobecomeaccessible,eachfilesysteminthestoragepoolmustbe
associatedwithanEVS.Todothis,navigatetotheDetailspageforeachfile
systeminthestoragepoolandassignittoanEVS.
Renaming a
Storage Pool
Thenameforastoragepoolcanbechangedatanytime,andwithoutaffecting
anyclients.
Torenameastoragepool:
1. NavigatetotheStoragePoolspage.
FromtheStorageManagementpage,clickStoragePoolstodisplaythe
StoragePoolspage:
2. Renamethestoragepool.
Selectastoragepoolandclickdetails.IntheDetailspage,enteranew
nameintheLabeltextbox,thenclickrename.
Storagepoollabelsarenotcasesensitive,buttheydopreservecase(labels
willbekeptasentered,inanycombinationofupperandlowercase
characters).Also,storagepoollabelsmaynotcontainspacesoranyofthe
followingspecialcharacters:"&*/;:<>?\|.
Note:Storagepoollabelsmustbeuniquewithinaserverorcluster.Also,a
23
Storage Management
storagepoolcannothavethesamelabelasafilesystem.
Configuring
Automatic File
System
Expansion for an
Entire Storage
Pool
Usethisproceduretoalloworprohibitautomaticexpansionofallfilesystems
inthespecifiedstoragepool.Thissettingonlyaffectsautoexpansion;manual
expansionoffilesystemsinthestoragepoolisnotaffectedbythissetting.
Toconfigureautomaticfilesystemexpansionforallfilesystemsinanentire
storagepool:
1. NavigatetotheStoragePoolspage.
FromtheStorageManagementpage,clickStoragePoolstodisplaythe
StoragePoolspage:
2. NavigatetotheStoragePoolDetailspage.
SelectastoragepoolandclickdetailstodisplaytheStoragePoolsDetails
page.
24
3. Configureautoexpansion.
Youcanconfigurefilesystemautoexpansionatthestoragepoollevelin
oneoftwoways:
Enableautoexpansion
Evenifthestoragepoolisconfiguredtoallowitsfilesystemsto
automaticallyexpand,thefilesystemsmustalsobeconfiguredto
supportautomaticexpansion.Formoreinformation,refertotheFile
ServicesAdministrationGuide.
Note:Afterafilesystemhasexpanded,itssizecannotbereduced.
Iffilesystemautoexpansioniscurrentlydisabled,youcanenableit
byclickingenableautoexpansionintheFSAutoExpansionoption
box.
25
Storage Management
Disableautoexpansion
Whenautomaticexpansionofafilesystemisdisabled,manual
expansionoffilesystemsinthestoragepoolisstillpossible.Formore
informationaboutmanualexpansionoffilesystems,refertotheFile
ServicesAdministrationGuide.
Iffilesystemautoexpansioniscurrentlyenabled,youcandisableit
byclickingdisableautoexpansionintheFSAutoExpansionoption
box.
26
Basedonastoragesubsystemsperformancecharacteristics,itisclassifiedas
belongingtoacertaintier,andeachtierisuseddifferentlyintheenterprise
storagearchitecture.Thecurrentlysupportedstoragesubsystemsarefitinto
thetieredstoragemodelasfollows:
Tier
Performance
DiskType
DiskRPM
Veryhigh
DualportedFC
15,000
SAS
15,000
27
Performance
DiskType
DiskRPM
High
DualportedFC
10,000
Nearline
SATAorNLSAS
7,200
Archival
SATAorNLSAS
7,200
Longtermstorage
N/A(Tape)
NA
Thestorageserversupportstiersofstorage,whereeachtierismadeupof
deviceswithdifferentperformancecharacteristicsortechnologies.Whenused
withHitachiDataSystemsstoragesubsystems,thestorageserveralso
supportsstoragevirtualizationthroughHitachiUniversalStoragePlatform
VSP,USPV,andUSPVMtechnology.
TiersofstorageandstoragevirtualizationarefullysupportedbyData
Migrator,anoptionalfeaturewhichallowsyoutooptimizetheusageoftiered
storageandremoteNFSv3servers(note,howeverthatDataMigratordoesnot
supportmigrationtoorfromtapestoragedevicesortapelibrarysystems).
DataMigratorautomaticallymigratesdataamongstoragesubsystemsof
primaryandsecondarystoragebasedonuserdefinedpolicies.DataMigrator
monitorsfilemetadatasuchassize,type,durationofinactivity,accesshistory,
andsoon.Whenthecriteriaofapolicyaremet,DataMigratormigratesfiles
accordingtorulesspecifiedinthepolicyasbackgroundtaskswithminimal
impactonserverperformance.Fromtheperspectiveoftheclientworkstation,
primaryversussecondaryfilelocationistransparent.Fordetailed
informationaboutDataMigrator,refertotheDataMigratorAdministration
Guide.
Tiered and
Untiered Storage
Pools
28
Astoragepool(knownasaspaninthecommandlineinterface)isthelogical
containerforacollectionofoneormoresystemdrives(SDs).
Therearetwotypesofstoragepools:
Anuntieredstoragepool:Anuntieredstoragepoolismadeupsystem
drives(SDs)createdononeormorestoragesubsystemswithinthesame
tierofstorage(storagesubsystemswithcomparablyperformance
characteristics).Tocreateanuntieredstoragepool,theremustbeatleast
oneavailableandunusedsystemdriveonthestoragesubsystemfrom
whichtheSDsinthestoragepoolwillbetaken.
Atieredstoragepool:Atieredstoragepoolismadeupsystemdrives
(SDs)createdonstoragesubsystems(RAIDarrays)withdifferent
performancecharacteristics.Typically,atieredstoragegroupismadeup
ofSDsfromhighperformancestoragesuchasflashmemory,andSDs
fromlowerperformancestoragesuchasfibrechannelorSATA.Youcan,
however,createatieredstoragegroupfromSDsfromstoragesubsystems
usinganystoragetechnology.
Note:TieredstoragepoolsaresupportedonlytheHitachiNASPlatformserv
ers/clusters.
Tiered and
Untiered File
Systems
Afilesystemtypicallyconsistsoffilesanddirectories.Dataaboutthefilesand
directories(aswellasmanyotherattributes)iskept;thisinformationisthe
metadata.Thedatawithinthefilesystem(bothuserdataandmetadata)is
storedinastoragepool.
Storagepoolscanbecreatedusingstoragefromdifferenttiers(uptotwotiers
arecurrentlysupported).Thesestoragepoolsarecalledtieredstoragepools.
Forinformationabouttieredstoragepools,seeTieredandUntieredStorage
Pools,onpage28.
Likestoragepools,filesystemdata(metadataanduserdata)maybestoredin
asingletier,orinmultipletiers.
Whenfilesystemdataisstoredonstoragesubsystemsonmultipletiers,
thefilesystemiscalledatieredfilesystem.
Inatieredfilesystem,metadataisstoredonthehighestperformancetier
ofstorage,anduserdataisstoredonalowerperformancetier.Storing
metadataonthehigherperformancetierprovidessystemperformance
benefitsoverstoringboththemetadataanduserdataonthesametierof
storage.
Whenfilesystemdataisstoredonstoragesubsystemsonasingletier,the
filesystemiscalledanuntieredfilesystem.
fc-linktoenable/disabletheFClink.
fc-link-typetochangetheFClinktype.
fc-link-speedtochangetheFCinterfacespeed.
Formoreinformationaboutthesecommands,refertotheCommandLine
Reference.
About FC Paths
TheNASserveraccessesthestoragesubsystemthroughaminimumoftwo
FCpaths(atleastonefromeachoftheFibreChannelswitches).AnFCpathis
29
madeupoftheservershostportID,thestoragesubsystemportWWN
(worldwidename),andtheSDidentifier(ID).Thefollowingillustration
showsacompletepathfromtheservertoeachoftheSDsonthestorage
subsystem:
YoucanviewinformationabouttheFCpathsontheserver/clusterthrough
thecommandlineinterface(CLI),usingthefc-host-port-load,fctarget-port-load,andthesdpathcommands.
Load Balancing
and Failure
Recovery
Loadbalancingonastorageserverisamatterofbalancingtheloadstothe
systemdrives(SDs)onthestoragesubsystems(RAIDarrays)towhichthe
storageserverisconnected.LUNsarealogicaldivisionofagroupofthe
physicaldisksofthestoragesubsystem,andLUNsthatarevisibletothe
storageserverareknownasSDs,whicharethebasicstorageunitofthe
storagesubsystem.
TheserverroutesFCtraffictoindividualSDsoverasingleFCpath,
distributingtheloadacrosstwoFCswitchesand,whenpossible,acrossdual
active/activeormultiportRAIDcontrollers.
Followingthefailureofapreferredpath,diskI/Oisredistributedamong
other(nonpreferred)paths.Whentheserverdetectsreactivationofthe
preferredFCpath,itonceagainredistributesdiskI/OtousethepreferredFC
path.
Defaultloadbalancing(loadbalancingautomaticallyperformedbythe
storageserver)isperformedbasedonthefollowingcriteria:
30
LoadisdefinedasthenumberofopenSDs,regardlessofthelevelofI/O
oneachSD.SDscounttowardsloadatthetargetiftheyareopentoatleast
Hitachi NAS Platform
oneclusternode;thenumberofnodes(normallyallnodesinacluster,
afterboot)isnotconsidered.
BalancingloadonRAIDcontrollertargetportstakesprecedenceover
balancingloadonserverFChostports.
BalancingloadamongasubsystemsRAIDcontrollerstakesprecedence
overbalancingamongportsonthosecontrollers.
Inacluster,choiceofRAIDcontrollertargetportiscoordinatedbetween
clusternodes,sothatI/OrequestsforagivenSDdonotsimultaneouslygo
tomultipletargetportsonthesameRAIDcontroller.
YoucanmanuallyconfigureloaddistributionfromtheCLI(overridingthe
defaultloadbalancingperformedbytheserver),usingthesdpathcommand.
Whenmanuallyconfiguringloadbalancingusingtheusingthesdpath
command:
Youcanconfigureapreferredserverhostportand/oraRAIDcontroller
targetportforanSD.Ifbothareset,theRAIDcontrollertargetport
preferencetakesprecedenceovertheserverhostportpreference.Whena
specifiedportpreferencecannotbesatisfied,portselectionfallsbackto
automaticselection.
FortheSDsvisibleonthesametargetportofaRAIDcontroller,you
shouldeithersetapreferredRAIDcontrollertargetportforall SDsorfor
none of the SDs.SettingthepreferredRAIDcontrollertargetportforonly
someoftheSDsvisibleonanygivenRAIDcontrollertargetportmay
createasituationwhereloaddistributionissuboptimal.
ThesdpathcommandcanalsobeusedtoquerythecurrentFCpathbeing
usedtocommunicatewitheachSD.Formoreinformationonthesdpath
command,runtheman sdpathcommand.
Fibre Channel
Statistics
Theserverprovidesperportandoverallstatistics,inrealtime,at10second
intervals.Historicalstatisticscovertheperiodsincepreviousserverstartor
statisticsreset.TheFibreChannelStatisticspageoftheWebManager
displaysahistogramshowingthenumberofbytes/secondreceivedand
transmittedduringthepastfewminutes.
Currentofferings:AMS2100,AMS2300,AMS2500,DF850,VSP,USPV,
andUSPVM
Discontinued,butstillsupported:WMS100,AMS200,AMS500,AMS
1000,AMS2000family,USP100,USP600,andUSP1100
Manyarrayshaveseveralconfigurations,andmaybesuitableforusein
severaltiersinthetieredstoragemodel,basedonconfigurationofthe
individualstoragearray.Duetothespecificcapacityandperformance
31
characteristicsofeachstoragesubsystem,arrayswilltypicallybeusedinthe
storagemodeltiersasfollows:
Manufacturer
Array
TypicallyusedinTier(s)
HDS
AMS500,AMS1000,and
AMS2000family
Tier1,Tier2,andTier3
AMS200
Tier2andTier3
DF850
Tier1,Tier2,andTier3
USP100,USP600,and
USP1100
Tier1andTier2
USPV
Tier1,Tier2,andTier3
USPVM
Tier1andTier3
VSP
Tier1
WMS100
Tier3
ThefollowingtabledescribestheRAIDlevelssupportedbyeachofthe
currentlysupportedstoragesubsystems:
32
Manufacturer
Array
RAIDLevel(s)Supported
HDS
USP100,USP600,USP1100,USPV,
USPVM,andVSP
1/5/6
AMS2000,AMS1000,AMS500,
AMS200,DF850,andWMS100
1/5/6/10
Storage Characteristics
BlueArcstoragearraycontrollerenclosuresusehardwareRAIDcontrollers,
whichprovidecompleteRAIDfunctionalityandenhanceddiskfailure
management.
TheRC12EandtheRC16EXParedriveshelfexpansionenclosuresthatattach
totheRAIDcontrollersinordertoexpandtheamountofstorageavailable.
RAID Controllers
TheRAIDcontrollersoperateasanActive/Active(A/A)pairwithinthesame
rack.BothRAIDcontrollerscanactivelyprocessdiskI/Orequests.Shouldone
ofthetwoRAIDcontrollersfail,thestorageserverreroutestheI/O
transparentlytotheothercontroller,whichstartsprocessingdiskI/Orequests
forbothcontrollers.
Changingtherackname,password,ormediascanperiod.
Checkingthestatusofmediascanandotheroperations.
ReviewingeventsloggedbytheRAIDrack.
Determiningthestatusofphysicaldisks.
33
Discovering and
Adding Racks
Beforecreatingsystemdrives,RAIDracksmustbediscoveredandaddedto
thelistofRAIDracksforthecurrentlyselectedmanagedserver.
ToAddaRAIDrack:
1. NavigatetotheStorageManagementpage(Home>Storage
Management>RAIDRacks).
2. IntheRAIDRackspage,clickDiscoverRacks.
3. Selectarack.
IntheChooseRackstoMonitorarea,checkthecheckboxesintheRack
Namecolumntobeaddedtothecurrentlymanagedserver.UsetheRack
Passwordfieldforrackswithconfiguredpasswords.Then,clickOK.
Ifnoracksappear,theSMUwasunabletofindanysupportedracksonits
network.Inthiscase,verifythattheRAIDrackshavetheirnetwork
settingsproperlyconfigured.
Note:RAIDracksthathavealreadybeenaddedtothecurrentlymanaged
serverwillnotbepresentinthelistofdiscoveredRAIDracks.
Oncearackisadded,thefollowingeventsoccur:
34
TheselectedRAIDracksappearontheRAIDRackslistpageandon
theSystemMonitor(forthecurrentlyselectedmanagedserver).
TheSMUbeginsloggingrackevents,whichcanbeviewedthrough
theEventLoglinkontheRAIDRackDetailspage.
RAIDracksevereeventswillbeforwardedtoeachmanagedserver
thathasdiscoveredtherackandincludedinitseventlog.Thistriggers
Hitachi NAS Platform
theserversalertmechanism,possiblyresultinginalertemailsand
SNMPtraps.
RAIDracktimeissynchronizeddailywithSMUtime.
IfsystemdrivesarepresentontheRAIDrack,therackcacheblock
sizewillbesetto16KB.
Listing Installed
RAID Racks
TolistinstalledRAIDracks:
1. NavigatetotheRAIDRackspage(StorageManagement>RAIDRacks).
Thefollowingactionsareavailableandapplytoracksselectedbyfilling
thecheckboxfortheRAIDrack:
DeleteremovestheRAIDrackfromthelist.Deletingtherackjust
removestherackasamanagedrack,itdoesnotaffectthesystem
drivesconfiguredonthestorageenclosuresintherack.
DiscoverRacksallowstheservertocheckforadditionalRAIDracks.
Itsearchesforsupportedstoragedevicesconnectedtoboththepublic
andprivatemanagementnetworks.OnceaRAIDrackhasbeenfound,
thenitcanbemanaged.
35
ViewPhysicalDisksshowsthestatusofthephysicaldisksassociated
withaRAIDrack.
ViewActiveTasksshowsthestatusofoperations,suchasmedia
scans,whichareinprogressforaRAIDrack.
TheshortcutforSystemDrivesbringsuptheSystemDrivespagein
whichasystemdrivecanbemanaged.
Inanyindividualrow,clickingthedetailsbuttonbringsupaRAIDRack
Detailspage.ThispageprovidesinformationontheRAIDrack.
36
Thefollowingtabledescribesfieldsandcolumnsinthispage:
Area
Field
Identification
Description
Thisareadisplaysidentificationinformation,
including:
RackStatus
Summary
Name.ThenameoftheRAIDrack.Youcan
changethisnametomakeiteasiertoidentify
theRAIDrack.
RackWWN.WorldwidenamefortheRAID
rack,setbythemanufacturer.
Theindicatorlightprovidesstatusinformation
abouttheRAIDrack:
GreenOK
AmberWarning
RedSevere
WhenyouclicktheViewIssueslink,theRack
Issuespageisdisplayed.
Configuration
MediaScan
Period
Controllers
Physical
Disks
Thenumberofdaysoverwhichacompletescanof
thesystemdriveswilloccur.
Thename,IPaddress(ifavailable),andstatus
informationforeachRAIDcontroller:
Status.ThestatusoftheRAIDcontroller.
Mode.ThemodereportstheRAIDcontrolleras
runningineitheractiveorpassivemode.By
default,bothcontrollersareactive.
Firmware.Thefirmwareversioninstalledon
theRAIDcontroller.
Thesummaryoftheoverallstatusofthephysical
diskswithintheRAIDrack:
GreenOK
AmberWarning
RedSevere
Clicktheindicatorlightorthestatustodisplaythe
physicaldisksontheRAIDRackpage.
37
Field
Batteries
Description
BatteriesmaintaindataheldintheRAIDcontrollers
cache,preservingdataintheeventofapower
failure.
TheinformationforeachbatterywithintheRAID
rack:
Status.Thestatusofthebatteries:
Power
Supplies
AmberWarning
RedSevere
Location.Thelocationofthebatterieswithin
theRAIDrack.
Age.Thenumberofdaysthatthebatterieshave
beenintheRAIDrack.
LifeRemaining.Thenumberofdaysuntilthe
batteriesshouldbereplaced.
Thestatusofeachpowersupplyunit(PSU)inthe
RAIDrack.
Status.ThestatusofthePSU:
GreenOK
AmberWarning
RedSevere
Location.ThelocationofthePSUintheRAID
rack.
Thestatusandlocationoftheenvironmental
servicesmodule(ESM)temperaturesensorinthe
RAIDrack.
Fans
ESM
Temperature
Sensors
GreenOK
Status.Thestatusofthesensor:
GreenOK
AmberWarning
RedSevere
Location.ThelocationofthesensorintheRAID
rack.
ThestatusofthefanswithintheRAIDrack.
Status.Thestatusofthefan:
GreenOK
AmberWarning
RedSevere
Location.ThelocationofthefanintheRAID
rack.
Thefollowingactionsareavailable:
38
ClickApplytosaveanychangestotheRAIDrackidentificationor
configuration.
ClickChangePasswordtodisplaytheRAIDRackPasswordpage.
Thefollowingshortcutsareavailable:
Performing a
Media Scan on a
System Drive
PhysicalDiskStatus.ClickthePhysicalDiskStatuslinktodisplay
thePhysicalDisksonRAIDRackpagefortheRAIDrack.
ActiveTasks.ClicktheActiveTaskslinktodisplaytheActiveTasks
pagefortheRAIDrack.
EventLog.ClicktheEventLoglinktodisplaytheRackEventLog
page.
SystemDrives.ClicktheSystemDriveslinktodisplaytheSystem
Drivespage.
MediaScanprovidesearlywarningofsystemdrivefailureandreducesthe
possibilityofencounteringamediaerrorduringhostoperations.Atypicalfile
systemcomprisesfrequentlyusedfiles,rarelyusedfiles,andfreespace.When
adiskdevelopsbadspotsinseldomaccessedsectors,failuresinthose
locationscanremainundetected.MediaScancandetectsuchdrivemedia
errorsbeforetheyarefoundduringanormalreadorwritetothesystem
drive.
MediaScanisperformedasabackgroundtask,scanningandcomparingall
dataandparityinformationontheconfiguredsystemdrives.MediaScanruns
onallsystemdrivesthatareoptimal(thatis,operatingwithoutknown
failures)andhavenomodificationoperationsinprogress.Errorsdetected
duringascanarereportedintheeventlog.
Monitoring Active
Tasks
Youcanviewthestatusofongoingactivity(MediaScan,CopyBack,
initializing,andsoon)withintheRAIDrackontheActiveTaskspage.
1. NavigatetotheRAIDRackspage(Home>StorageManagement>
RAIDRacks).
2. SelectaRAIDrack.
IntheRAIDRackspage,checkthecheckboxnexttotheRAIDrackon
whichtoviewtheActiveTasks,thenclickViewActiveTasks.
AllongoingactivityontheRAIDrackaredisplayedonthispage.This
pagewillautomaticallyrefreshevery60seconds.
Thefollowingchoicesareavailable:
RefreshupdatesthestatusofActiveTasks.
Storage Subsystem Administration Guide
39
BackbringsuptheRAIDRackslistpage.
Note:SometaskswillreportaPercentageCompletebutnotaTimeRe
maining.Inthiscase,TimeRemainingwillbeshownasNotKnown.
Reviewing Events
Logged
TheSMUmonitorsevents,suchasfailureconditions,loggedbytheRAID
rack.TheSMUisconnectedtothestoragesubsystemthroughanoutof
bandEthernetlink(theprivatemanagementnetworkistypicallyusedfor
thispurpose).Severeeventsareimmediatelyforwardedtotheserversevent
log.Thiswilltriggeralertnotifications(forexample,emailorSNMPtraps)if
theserverisconfiguredtodoso.Inaddition,iftheSMUisunabletoconnect
totheRAIDracks,aseverealertwillbetriggeredontheserver.
TorevieweventsloggedbytheRAIDrack:
1. NavigatetotheRAIDRackDetailspage(Home>StorageManagement
>RAIDRacks).
ClickthedetailsbuttoncorrespondingtotheRAIDrackonwhichtoview
theRAIDRackDetailspage.
2. Displaytheeventlog.
FromtheRAIDRackDetailspage,clickEventLog.
Theeventlogisupdatedeverythreeminutesorwhenasevereevent
occursontheRAIDrack.Itdisplaysamaximumof1,000events(infoor
40
severe).Upto3,000eventsarearchivedontheSMUandareavailablefor
downloadusingthedownloadbutton.
Thistablecanalsobefilteredtoviewtheeventlogbasedonseveritylevel:
All,Info,orSevere.
Item/Field
Description
Severity
Thelevelofseverityisdisplayedforeachevent.Severitymightbeeither
Info(informational),orsevere(error).
Date/Time
Thedateandtimeatwhichtheeventwaslogged.
Component
Location
Thecomponent(controller,battery,volume,channel,andsoforth)and
locationoftheevent,ifknown.
ID/Message
TheeventIDandthedetailsabouttheevent.
TheDetailssectionprovidestheracknameandthecurrent(RAID)
controllersdateandtime.
Thefollowingactionsareavailable:
RefreshupdatestheEventLogpage.TheEventLogpage
automaticallyrefreshesevery60seconds.
Downloadallowsthearchivedeventstobedownloadedinacomma
separatedvalues(.csv)providedinaZIPfile.EventhoughtheSMU
displaysonlythemostrecent1,000events,manymorearearchivedon
theSMUharddrive.Approximately2MB(about4,000)ofthemost
recenteventsarearchived.
ClearAllpermanentlydeletesalltheeventsintheSMUeventlogand
theRAIDracklog.
41
CheckthecheckboxfortheRAIDrackwithphysicaldisksofinterestand
clickViewPhysicalDisks.
Thefollowingtabledescribesthecolumnsinthispage:
42
Item/Field
Description
Enclosure
TheIDoftheenclosurehousingthedisk.
Slot
Theslotnumberinthestorageenclosureinwhichthephysicaldisk
resides.
Capacity
Thestoragecapacityofthedisk.
Type
Thetypeofphysicaldiskintheenclosure,typicallyeitherFibre
ChannelorSATA.
StoragePool
ThelabeloftheStoragePool,ifthephysicaldiskisinusewithina
StoragePool.
Status
ThecurrentstatusofthephysicaldiskswithintheRAIDrack.
HotSpare
Theboxischeckedifitisassignedasahotspare.
Available
Theboxischeckedifthephysicaldiskisavailable.
Offline
Theboxischeckedifthephysicaldiskisoffline.
Manufacturer
Thenameofthediskmanufacturer.
Firmware
Thefirmwareversiononthephysicaldisk.
WithinthePhysicalDiskpage,physicaldiskswhichareshownas
availablecanbeassignedorunassignedashotspares.
Note:HitachiDataSystemsrequiresthatatleastonediskbemarkedasa
hotsparebythetimethefirstsystemdriveiscreated.
43
44
SA48 Specifications
TheSA48CstoragesubsystemsprovidehighdensityTier3(nearline)storage
usingSATAdisks.
TheSA48Cstoragesubsystemsincludethefollowingelements:
Storagecontrollerenclosure,whichconsistsofthe4USA48Cstorage
controllerenclosure,housing48SATAdisks(SASdisksarenotsupported)
anddualRAIDHA(HighAvailability)controllers.EachRAIDcontroller
hasdualRAIDhostports,andconnectstoasingleexpansionunitthrough
acable.TheRAIDcontrollersinanSA48Cstorageenclosuresupporta
maximumofoneexpansionenclosure.
Optionally,oneSA48expansionenclosurecanbeconnectedtoanSA48C
storagecontrollerenclosure.
RAID Controllers
TheRAIDcontrollersoperateasanActive/Active(A/A)pairwithinthesame
rack.BothRAIDcontrollerscanactivelyprocessdiskI/Orequests.Shouldone
ofthetwoRAIDcontrollersfail,thestorageserverreroutestheI/O
transparentlytotheothercontroller,whichstartsprocessingdiskI/Orequests
forbothcontrollers.
Whenadiskfails,theRAIDcontrollerautomaticallyreconstructsdatafrom
thefaileddiskonahotspareandbeginsusingthediskinnormaloperations.
Thefaileddiskcanthenbereplacedanddesignatedasahotspare,whichwill
thenbeavailableforfutureuse.
Ifitisnecessarytoremoveandreplacefaileddisks,itispossibletoperform
hotswapoperations.Inahotswap,anofflineorfaileddiskisremovedand
areplacementdiskisinsertedwhilethepowerisonandthesystemis
operating.
Note:Whenreplacingdiskdrives,allowatleastaoneminuteintervalbetween
diskremovalanddiskreplacement.ThisintervalallowstheRAIDcontrollerto
recognizethechangeintheRAIDracksconfiguration.
45
Changingtherackname.
Checkingthehardwarestatus(controllers,disks,batteries,PSUs,and
fans)andtemperaturesensorreadings.
Reviewingactivetasksandrackevents.
Additionally,youcanlaunchtheintegratedStorViewmanagement
application.ThisapplicationisusedtocreateLUs,Arrays,andmanagehot
spares.
Discovering and
Adding Racks
Beforecreatingsystemdrives,RAIDracksmustbediscoveredandaddedto
thelistofRAIDracksforthecurrentlyselectedmanagedserver.Forthe
SA48C,thisdiscoveryoccursautomatically.Oncethediscoveryprocessis
completetheRAIDrackwillappearintheSystemMonitorwithitsdefault
name,youcanthengototheSystemMonitorandrenametheRAIDrack.
Listing Installed
RAID Racks
46
TolistinstalledRAIDracks:
1. NavigatetotheRAIDRackspage(StorageManagement>RAIDRacks).
Thefollowingactionsareavailableandapplytoracksselectedbyfilling
thecheckboxfortheRAIDrack:
DeleteremovestheRAIDrackfromthelist.Deletingtherackjust
removestherackasamanagedrack,itdoesnotaffectthesystem
drivesconfiguredonthestorageenclosuresintherack.
DiscoverRacksallowstheservertocheckforadditionalRAIDracks.
Itsearchesforsupportedstoragedevicesconnectedtoboththepublic
andprivatemanagementnetworks.OnceaRAIDrackhasbeenfound,
thenitcanbemanaged.
ViewPhysicalDisksshowsthestatusofthephysicaldisksassociated
withaRAIDrack.
ViewActiveTasksshowsthestatusofoperations,suchasmedia
scans,whichareinprogressforaRAIDrack.
TheshortcutforSystemDrivesbringsuptheSystemDrivespagein
whichasystemdrivecanbemanaged.
47
Inanyindividualrow,clickingthedetailsbuttonbringsupaRAIDRack
Detailspage.ThispageprovidesinformationontheRAIDrack.
48
Thefollowingtabledescribesfieldsandcolumnsinthispage:
Area
Description
Identification
Thisareadisplaysidentificationinformation,including:
Name.ThenameoftheRAIDrack.Youcanchangethisnameto
makeiteasiertoidentifytheRAIDrack.
RackWWN.WorldwidenamefortheRAIDrack,setbythe
manufacturer.
Ifyouhavechangedtherackname,clickapplytosavethechange.
RackStatus
Summary
Controllers
TheindicatorlightprovidesstatusinformationabouttheRAIDrack:
GreenOK
AmberWarning
RedSevere
Thename,IPaddress(ifavailable),andstatusinformationforeach
RAIDcontroller:
TolaunchtheintegratedStorViewapplication,clickLaunch
GUI.
IPAddress.ThisfieldisusedtosendtheIPAddressofaRAID
controller(orbothRAIDcontrollers)tothemanagedserver/
clusterandtheSMU.Becausetheserver/clusterandtheSMU
cannotdeterminecontrollerIPaddressvaluesforthemselves,
entertheIPaddressforoneRAIDcontroller(orbothRAID
controllers),andclickapply.
Note:EnteringRAIDcontrollerIPaddressvaluesdoesnotaffect
thenetworksettingsofthecontrollers;itmerelyprovidesthis
informationtothemanagedserverandtheSMU.
Physical
Disks
Status.ThestatusoftheRAIDcontroller.
Mode.ThemodereportstheRAIDcontrollerasrunningin
eitheractiveorpassivemode.Bydefault,bothcontrollersare
active.
Firmware.ThefirmwareversioninstalledontheRAID
controller.
Thesummaryoftheoverallstatusofthephysicaldiskswithinthe
RAIDrack:
GreenOK
AmberWarning
RedSevere
Clicktheindicatorlightorthestatustodisplaythephysicaldiskson
theRAIDRackpage.
49
Description
Batteries
BatteriesmaintaindataheldintheRAIDcontrollerscache,
preservingdataintheeventofapowerfailure.
TheinformationforeachbatterywithintheRAIDrack:
Power
Supplies
GreenOK
AmberWarning
RedSevere
Charged.Thepercentageofchargeremaininginthebattery.
StandbyTime.Anestimateoftheamountoftimethatthe
batterycanmaintaindataintheRAIDcontrollerintheeventofa
powerloss.
Thestatusofeachpowersupplyunit(PSU)intheRAIDrack.
Status.ThestatusofthePSU:
GreenOK
AmberWarning
RedSevere
Location.ThelocationofthePSUintheRAIDrack.
ThestatusandlocationofthetemperaturesensorsintheRAIDrack.
Fans
Temperature
Sensors
Status.Thestatusofthebatteries:
Status.Thestatusofthesensor:
GreenOK
AmberWarning
RedSevere
Location.ThelocationofthesensorintheRAIDrack.
ThestatusofthefanswithintheRAIDrack.
Status.Thestatusofthefan:
GreenOK
AmberWarning
RedSevere
Location.ThelocationofthefanintheRAIDrack.
Thefollowingshortcutsareavailable:
Creating RAID
Arrays and LUs
50
PhysicalDisks.ClickthePhysicalDiskslinktodisplaythePhysical
DisksonRAIDRackpagefortheRAIDrack.
ActiveTasks.ClicktheActiveTaskslinktodisplaytheActiveTasks
pagefortheRAIDrack.
SystemDrives.ClicktheSystemDriveslinktodisplaytheSystem
Drivespage.
RAIDArrays(oftencalledRAIDgroupsorvolumegroups)arecreatedon
theSA48C,andarethendividedintosystemdrives(SDs).RAIDArraysare
groupsofdisksthatareorganizedintoasinglelogicalunit,whichcontains
Hitachi NAS Platform
datadisksandhotsparedisks,whichreplacedisksthatfailduring
operation.Whenadatadiskfails,ahotsparediskisrebuilt(loaded)with
thedatafromthefaileddatadisk.DependingonthesizeoftheRAIDlevel
ofthearraybeingcreated,andthesizeoftheLUstobecreatedonthearray,
youmayhavetouseadifferentnumberofdataandhotsparedisksinyour
arrayconfiguration.
1. NavigatetotheRAIDRackspage(Home>StorageManagement>
RAIDRacks).
2. LaunchtheStorViewapplication.
OntheRAIDRackspage,selectoneofthecontrollersintheRAIDRack
thathastheeventsyouwanttosee,andclickLaunchGUItostartthe
StorViewapplication.
3. GototheCreateArraypage.
TodisplaytheCreateArraypage,clickontheCreateArrayiconunderthe
Configurationheading.
4. Selectavailabledrivesforthearray.
DrivesthatareonlineandreadyforselectionaremarkedasAvailable.
Toselectthedrive,simplyclickonit.Whenselected,thedrivescolorwill
change,andifislabelledselected.
Ifpossible,selectthedrivesforthearrayinahorizontalpatternacrossthe
enclosure.
Onceyouhaveselectedallthedrivesforthearray,proceedtothenext
step.
5. Specifythearrayconfigurationsettings.
UndertheNewArraySettingsheading,chooseappropriatesettingsfor
theRAIDlevelyouwantthearraytouse.Supportedconfigurations
include:
RAIDLevel
SupportedConfigurations
(DataDisks+HotSpares)
2+1
Note:4+2(forhigherperformance),7+2,9+2,or13+2(largest
LUs)
Note:RAID6ismandatoryforLUsgreaterthan2TB.
Thefollowingarrayconfigurationsettingsarerecommended:
SettingName
Value
RAIDLevel
5or6
ChunkSize
32KB
Initialize/Trust
Initialize
51
Value
Backoffpercent
1%
Readaheadcache
Automatic
Writebackcache
MaxMB
Mirrorcache(disablewhenpartnercontrollermissingoroffline)
Checkboxfilled
DisableWBcacheifcontrollerbatteryislow,missingorfailed
Checkboxfilled
DisableWBcacheifarraybecomescritical
Checkboxempty
BlockSize
512bytes
Disablewritecache
Checkboxfilled
NotethattheName(item3)isauserfriendlyname,suchasArrayx,
thatwillbeassignedtothearray.
6. Createthearray.
ClickCREATEtocreateandinitializethearray.
7. ClosetheCreateArraypage.
ClickCLOSEtoclosetheCreateArraypageandreturntothemainpage
oftheStorViewapplication.
8. Createadditionalarraysifnecessary.
Tocreateadditionalarrays,repeatsteps3through7foreachadditional
array.
9. GototheAdvancedSettingspage.
TodisplaytheAdvancedSettingspage,clickontheAdvancedSettings
iconundertheConfigurationheading.
10. Whenthearrayisinitialized,createLUs.
TocreateLUs(logicalunits):
a. GototheCreateLogicalDrivepageofStorView.
TodisplaytheCreateLogicalDrivepage,clickontheCreateLogical
DriveiconundertheConfigurationheading.
b. SelectthearraystobeusedfortheLU.
SelectthearraystousefortheLU,startingwitharray0.Thetotal
capacityoftheLUisdisplayedintheSizefield.
Note:TheentirecapacityofaRAIDarrayshouldbeconfiguredasasingle
LU.
52
c. SpecifytheLUconfigurationsettings.
ThefollowingadvancedLUconfigurationsettingsarerecommended:
SettingName
Value
Name
Userset
Mappedto
(Acceptthedefault)
Availability
(Acceptthedefault)
d. CreatetheLU.
ClickCREATEtoacceptallthedefaultsettingsandcreatetheLU.
11. SpecifytheLUconfigurationsettings.
ThefollowingadvancedLUconfigurationsettingsarerecommended:
SettingName
Value
DifferentNodeNames
Checkboxfilled
ControllerLUN
Disabled
AutoSpare
Checkboxfilled
AutoRebuild
Checkboxfilled
SingleControllerMode
Notsupported(shouldbegrayedoutand
notavailable)
BackgroundDriveVerify
Checkboxempty
InitializationPriority
50%
RebuildPriority
50%
12. ReturntoWebManager.
ReturntoWebManagerbyclickingthebackbuttononyourbrowser
twice.
Monitoring Active
Tasks
Youcanviewthestatusofongoingactivity(initializing,rebuilding,parity
checking,andsoon)withintheRAIDrackontheActiveTaskspage.
1. NavigatetotheRAIDRackspage(Home>StorageManagement>
RAIDRacks).
2. SelectaRAIDrack.
53
IntheRAIDRackspage,checkthecheckboxnexttotheRAIDrackon
whichtoviewtheActiveTasks,thenclickViewActiveTasks.
AllongoingactivityontheRAIDrackaredisplayedonthispage.This
pagewillautomaticallyrefreshevery60seconds.
Thefollowingchoicesareavailable:
RefreshupdatesthestatusofActiveTasks.
BackbringsuptheRAIDRackslistpage.
Note:SometaskswillreportaPercentageCompletebutnotaTimeRe
maining.Inthiscase,TimeRemainingwillbeshownasNotKnown.
Reviewing Events
Logged
Boththeserver/clusterEventLogontheSMU(availablethroughWeb
Manager)andtheembeddeduserinterface(StorView)monitorevents,such
asfailureconditions,loggedbytheRAIDrack.
TheSMUisconnectedtothestoragesubsystemthroughanEthernetlink
(theprivatemanagementnetworkistypicallyusedforthispurpose).
Severeeventsareimmediatelyforwardedtotheserverseventlog.This
willtriggeralertnotifications(forexample,emailorSNMPtraps)ifthe
serverisconfiguredtodoso.Inaddition,iftheSMUisunabletoconnect
totheRAIDracks,aseverealertwillbetriggeredontheserver.
ThelogintheStorViewmanagementinterfacelistsmanyeventsthatare
notrecordedintheserver/clusterEventLog.
Note:IftheRAIDrackandtheserver/clusterhavebeenconfiguredtouse
SNMP,alleventsintheStorViewmanagementinterfacelogwillalsoap
pearintheserver/clustereventlog.
Dependingonthetypeofeventyouwanttosee,youmayuseeitherthe
server/clusterEventLog,ortheStorViewlog.
54
FromtheHomepage,selectStatus&Monitoring,thenclickEventLogto
displaytheEventLogpage.
55
OnthefirstpageofStorView,clickLOGS.Anewwindowwillappear,
displayingtheStorViewLog.
Note:IftheRAIDrackandtheserver/clusterhavebeenconfiguredtouse
SNMP,alleventsintheStorViewmanagementinterfacelogwillalsoap
pearintheserver/clustereventlog.
4. ReturntoWebManager.
Onceyouhavereviewedthelog,closethewindowandreturntoWeb
Managerbyclickingthebackbuttononyourbrowsertwice.
56
CheckthecheckboxfortheRAIDrackwithphysicaldisksofinterestand
clickViewPhysicalDisks.
Thefollowingtabledescribesthecolumnsinthispage:
Item/Field
Description
Enclosure
TheIDoftheenclosurehousingthedisk.
Slot
Theslotnumberinthestorageenclosureinwhichthephysicaldisk
resides.
Capacity
Thestoragecapacityofthedisk.
Type
Thetypeofphysicaldiskintheenclosure,typicallyeitherFibre
ChannelorSATA.
StoragePool
ThelabeloftheStoragePool,ifthephysicaldiskisinusewithina
StoragePool.
Status
ThecurrentstatusofthephysicaldiskswithintheRAIDrack.
HotSpare
Theboxischeckedifitisassignedasahotspare.
Available
Theboxischeckedifthephysicaldiskisavailable.
Offline
Theboxischeckedifthephysicaldiskisoffline.
Manufacturer
Thenameofthediskmanufacturer.
Firmware
Thefirmwareversiononthephysicaldisk.
57
WithinthePhysicalDiskpage,physicaldiskswhichareshownas
availablecanbeassignedorunassignedashotspares.
Note:HitachiDataSystemsrequiresthatatleastonediskbemarkedasahot
sparebythetimethefirstsystemdriveiscreated.
TostopI/OontheSA48CRAIDsystemthatisbeingexpanded.
TwoSAScables(bothendsofeachcablemustbeoftheSFF8470format).
TheStorViewusernameandpasswordfortheSA48expansionenclosure
beingadded.
TomakesurethattheSA48CRAIDsystemthatisbeingexpandedmustbe
runningfirmwareversionv2.5orlater.ContacttheHitachiDataSystems
SupportCenterifitisnecessarytoupgradethefirmwarepriortoadding
anexpansion.
Tomakesurethatthereisnoarrayconfigurationpresentonanyofthe
diskdrivesintheexpansionenclosuretobeattachedtoanalready
configuredSA48CRAIDsystem.Thismeansthatyoumustconfigurethe
arraysontheexpansionenclosureafteraddingit;configuringan
expansionbeforeaddingittotheexistingSA48Csystemisnotsupported.
Forinformationoncreatingthearrays,seeCreatingRAIDArraysand
LUs,onpage50.
Tohavetheexpansionphysicallyplacedinthelocationwhereitisdesired
(forexample,mountedinarack),andthattheexpansionenclosureis
populatedwiththedesireddiskdrives.
Note:AfullypopulatedSA48enclosureisheavy!Youshouldinstallthe
rackstabilizerplatebeforemountingtheSA48enclosureinarack.
ToaddanexpansionenclosuretoanexistingSA48Cstoragesubsystem,use
thefollowingprocedure:
1. UnpackandmounttheSA48Crackstabilizationplate.
BeforemountingtheSA48enclosureinarack,installtherackstabilizer
plate.MounttheSA48enclosureusingonlytheincludedmountingrails.
Also,asaprecautionagainsttippingtherack,theSA48enclosureshould
bemountedaslowaspossibleintherack.
2. UnpackandmounttheSA48Cexpansionenclosure.
TheexpansionenclosuremustbemountedneartheSA48Cbeing
expanded,sothattheSAScablescanbeattachedwithoutstrain.
3. ConnecttheSA48expansionenclosuretotheSA48CRAIDcontroller
enclosure.
58
UsingtheSAScables,connecttheSA48expansionenclosuretotheSA48C
RAIDcontrollerenclosureasshownbelow.
Note:IntheeventofaRAIDcontrollerfailure,ifbothRAIDcontrollersare
notconnectedtotheexpansionenclosureasillustratedabove,alossof
accesstothedrivesintheexpansionenclosurewilloccur.
4. ConnectthepowercablestotheSA48expansionenclosure.
5. StopI/OontheSA48CRAIDcontrollerenclosurebeingexpanded.
ThesafestwaytostopI/Oistounmountallthefilesystemsusingthe
SA48C.
6. Poweruptheexpansionenclosure.
NowthattheRAIDchassishasbeenconnectedtotheexpansionenclosure
withSAScables,andthepowercablesareconnected,turnthepoweronto
theexpansionenclosure.
7. Waitfortheexpansionenclosuretobootandfordrivestospinup.
Itshouldtakeapproximatelyoneminutefortheexpansionenclosureto
bootup,andforalldrivestofullyspinup.
8. Verifythattheexpansionenclosurehasbeenrecognized.
OpenuptheStorViewGUIandmonitorthemainpage(thisiswhereall
theenclosures/diskdrivescanbeviewedononescreen).
Withinaboutaminute,asecondenclosureshouldappearunderneaththe
mainRAIDchassis.Ifasecondenclosuredoesnotappear,waitanother
59
minuteorsotogivetheRAIDcontrollerachancetodiscoverthe
expansionenclosure.
Ifthreeminuteshavepassed,andtheexpansionenclosureisnotdisplayed
onthemainpageofStorView,doublechecktheSAScablesthatwere
connectedinstep3.
Whentheexpansionenclosureappears,noticethatallthedrivesareofthe
Availablestatus(greenbackgroundwithscrollingtext).
TheexpansionenclosureisnowreadytoaddnewarraysandLUNstothe
existingconfiguration.
9. AddarraysandLUstotheexpansionenclosure.
ThestepstoaddarraysandLUNswouldbeidenticaltohowtheSA48C
RAIDcontrollerenclosurewasconfigured.SeeCreatingRAIDArraysand
LUs,onpage50formoreinformationoncreatingarraysandLUs.
10. ResumeI/OontheSA48CRAIDcontrollerenclosure.
Afterconfiguringtheexpansionenclosure,normalI/Oloadmaybe
resumed.
ToresumeI/O,mountthefilesystemsusingtheSA48systemandrestart
anyapplicationsthatreadfromorwritetothosefilesystems.
Powering the
SA48C and
Expansion
Enclosures
WhenshuttingdownorstartingSA48RAIDcontrollerandexpansion
enclosures,thefollowingconsiderationsapply:
WhenpoweringoffSA48RAIDcontrollerandexpansionenclosure,
powerofftheRAIDcontrollerenclosurefirst.
ThisensuresthattheRAIDsystemdoesnotseeanyofthedrivesinthe
expansionenclosuredisappear.Failuretodothismayresultinthe
RAIDcontrollerfailingthearraysandLUNsthathaddrivesinthe
expansionenclosure.
WhenpoweringonSA48RAIDcontrollerenclosureandexpansion
enclosure,poweruptheexpansionenclosurebeforepoweringonthe
RAIDcontrollerenclosure.
Afterpoweringuptheexpansionenclosure,youshouldwaitoneminute
beforestartingtheSA48CRAIDcontrollerenclosure.Thisensuresthatthe
drivesintheexpansionenclosureareavailablewhentheSA48CRAID
controllerloadstheconfiguration.Failuretostarttheexpansionenclosure
beforetheRAIDcontrollerenclosuremayresultintheRAIDcontroller
failingthearraysandLUsthathavedrivesintheexpansionenclosure.
60
System Drives
Logically,systemdrives(SDs)arethebasicstorageelementusedbythe
storageserver.Theserverassignseachsystemdriveauniqueidentifying
number(ID)and,onceassigned,theSDisreferencedbythatIDnumber,and
theIDnumbermaynotbechanged.
Physically,eachSDismadeupofaLUNinaRAIDgroup.Thesizeofthe
systemdrivedependsonfactorssuchastheRAIDlevel,thenumberofdisks,
andtheircapacity.SeeSupportedStorageSubsystems,onpage31for
informationontheRAIDlevel(s)supportedbyyourstoragesubsystem(s).
OnallHitachiNASPlatform/clusters,andallSeries3000Highperformance
NASPlatforms/clusters,systemdrivescanbeorganizedintosystemdrive
groups,whichcanimprovetheperformanceofastorageserverorclusterby
optimizingreadsandwrites.
System Drive
Groups
Withmoststoragesubsystems,systemdrives(SDs)arelimitedto2TB
each.However,withtodayslargephysicaldisks,RAIDarraysmustbe
considerablylargerthan2TBinordertomakeefficientuseofspace.Soitis
commonforsystemadministratorstobuildlargeRAIDarrays(oftencalled
RAIDgroupsorvolumegroups)andthendividethemintoLUNsof2TB
orless.NotethateachLUNinaRAIDgrouptypicallyusessomespaceon
eachdiskintheRAIDgroup.LUNsthatarevisibletotheserver/clusterare
knownasSDs,whicharetheunitsofstoragethattheserverseesandmanages
(theserverorganizesSDsintostoragepools,whichthencontainthefile
systems).
Whenperformingwriteoperations,iftheserverweretowritesimultaneously
tomultipleSDsinthesameRAIDgroup,itwouldincreaseheadmovement,
reducingbothperformanceandtheexpectedlifeofthedisks.Sotheserver
hasamechanismtoallowittowritetoonlyoneSDinaRAIDgroupatany
onetime.BydefiningSDgroups,youtelltheserverwhichSDsareineach
RAIDgroupandgiveittheinformationitneedstooptimizewrite
performance.
Note:ForHighperformanceNASPlatform/clusters,systemdrivegroupsare
supportedonSeries2000andSeries3000storageservers,butonlySeries3000
HighperformanceNASPlatforms/clusterstakeadvantageofthis
functionality.AllHitachiNASPlatforms/clusterstakeadvantageofsystem
drivegroups.
61
Asystemdrivethatisnotinanygroupistreatedasifitwereinagroupofits
own.
Systemdrivesthatareusedinopenstoragepoolscannotbegroupedor
ungrouped.Astoragepoolisopenifithasanyfilesystemthatismountedor
isbeingcheckedorfixedanywhereonthecluster.
DuringEVSmigration,theSMUautomaticallycopiesthegroupsfromthe
sourcestorageserverorclusterandaddsthemtothetargetstorageserveror
cluster.
SeeManagingSystemDriveGroups,onpage65forinformationoncreating
andmodifyingsystemdrivegroups.
System Drives
ofdataintotherecentlyaddedstorage,theutilitywilleitherrefusetorunor
produceunpredictableresults.
Thefilesystemdataredistributionutilityisdesignedtooperatewhenafile
systemisexpandedintonewstorageafterSDshavebeenaddedtoastorage
poolwhenthefilesystemisnearlyfull.However,storagemayalsobeadded
toastoragepoolforotherreasons:
Toincreaseperformance.
Topreventthefilesystemfrombecoming100%full.
Toachievethedesiredresultsineitherofthesesituations,youcanusethe
followingprocessafteraddingthestorage(afteraddingtheSDstothestorage
pool):
1. Createadummyfilesystem,usingallavailablespace.
2. ExpandthestoragepoolintothenewSDs.
3. Expandthealmostfulltargetfilesystemtousesome(orall)ofthespace
addedtothestoragepool.Notethattheexpansionshouldbeatleast50%
oftheaddedstoragecapacity.
4. Runthefilesystemdataredistributionutility.
5. Deletethedummyfilesystem.
SnapshotsandtheFileSystemDataRedistributionUtility
Whenthefilesystemdataredistributionutilityisrunandsnapshotsare
enabled,theolddataispreserved.Asaresult,snapshotswillgrow,
consumingalotofdiskspace.Thespaceusedbythesesnapshotsisnotfreed
untilallsnapshotspresentwhenthefilesystemdataredistributionutilitywas
startedhavebeendeleted.
Therearefouroptionsavailabletorecoverthespaceusedbysnapshots:
1. Allowthesnapshotstobedeletedaccordingtothesnapshot
configuration.
Thisistheslowestoptionforrecoveringspace,butitcanbeusedin
scenarioswherethespacewontberequiredimmediatelyafterthefile
systemdataredistributionutilitycompletes.
2. Manuallydeletesnapshotsafterrunningthefilesystemdata
redistributionutility.
Thisoptionrecoversspacemorequicklythanoption1.
3. Manuallykillsnapshotsafterrunningthefilesystemdataredistribution
utility.
Thisoptionalsorecoversspacemorequicklythanoptions1or2,butit
requiresthatthefilesystemistakenoffline.
4. Disablesnapshots(andthereforebackups)andkill/deleteexistent
snapshotsbeforerunningthefilesystemdataredistributionutility.
Thisoptionavoidsthesnapshotspaceusageproblemaltogether.
Storage Subsystem Administration Guide
63
Astoragebottleneckiscreatedbecauseallwritesaregoingtoasingle
stripeset,regardlessofthenumberofSDsinthestoragepool.
Ifthestripesetsvaryinperformance(forexample,someSDsmaybeon
higherperformancestorageormaycontainmoreSDs),thewrite
performanceofthefilesystemwillvaryovertime,dependingonthe
stripesetcharacteristics.
Ifmorestorageisaddedtothestoragepool,thefilesystemswrite
performancedoesnotimmediatelyimprove;itwillimproveonlyafter
newchunkshavebeenaddedtothefilesystem.However,write
performancewillfallagainwhenwritingtoolderchunks.
DynamicWriteBalancing(DWB)solvestheseproblemsbywritingtoallSDs
inparallel.
ToimplementDynamicWriteBalancing,theNASserverrequiressome
knowledgeofthephysicalconfigurationofthestorage.SDsmustbeassigned
toSDgroups,witheachSDgrouptypicallycorrespondingtooneRAID
group.OnceSDgroupshavebeenconfigured,writeoperationsareassociated
withSDgroupsratherthanwithSDs;withineachSDgroup,theNASserver
willscanthewholeofoneSDforfreespacebeforemovingontothenextSD.
Forsomestoragesubsystems,SDgroupsmustbemanuallyconfiguredbyan
administrator.Forotherstoragesubsystems,theSMUwillautomatically
configureSDgroups,andtheseSDgroupswillbeperiodicallychecked.See
SystemDriveGroups,onpage61formoreinformationonSDgroups.
OptimizingDynamicWriteBalancingPerformance
Althoughdynamicwritebalancingremovesmanyoftherestrictionsof
previousallocationschemes,afewimportantguidelinesstillapply:
1. MakeSDsaslargeaspossible,anduseasfewSDsaspossible.
NeverdividestorageintodozensoftinySDs,andthencreateastorage
poolfromthemanysmallSDs.
All the SDs in a RAID group should be used in the same storage pool.
64
IfmultipleSDsinanSDgrouparesharedbetweenstoragepools,theSD
groupmechanismwillnotpreventtheserverfromwritingtoseveralof
thesharedSDsatonce.
Creating SD
Groups
Automatically
Thefollowingstepsdescribehowtocreatesystemdrivegroupsautomatically.
1. NavigatetotheSystemDrivesGrouppage(Home>Storage
Management>SystemDriveGroups).
TheSystemDriveGroupspageindicatesthenumberofSDsnotin
groupsandliststheSDgroupsthathavealreadybeencreated.
65
2. Startautogroupingthesystemdrives.
IntheSystemDrivesGrouppage,clicktheauto_grouplink(ifthe
NumberofSystemDrivesNotInGroupsiszero,theauto_grouplinkis
unavailablebecausenogroupscanbecreated).
TheAutoGroupSystemDrivespageopens,allowingyouto
automaticallygroupsystemdrives.
GroupingsystemdrivesautomaticallycanbeperformedonlywhentheSMU
candeterminethephysicallocationofthesystemdrivesalongwiththeRAID
configuration.Currently,theSMUcandeterminethephysicallocationofthe
systemdrivesonlyforsomestoragesubsystems.Withoutsuchinformation,
youwillneedtogroupsystemdrivesmanually(seeCreatingSDGroups
Manually,onpage67).ThestorageservercannotautomaticallygroupSDson
HDScertainstoragesubsystems,becausethoseSDsarenotdirectlymanaged
bythestorageserver.Becauseofthis,whenyouusetheautogroupfeatureof
thestorageserver,eachSDonthesestoragesubsystemswillbeplacedintoa
separategroup.
66
1. ClickOKtoautomaticallycreatetheSDgroups.
Creating SD
Groups Manually
BeforecreatingSDgroupsmanually,youmustfirstdeterminethephysical
locationofthesystemdrivesalongwiththeRAIDconfiguration.This
informationcanbeobtainedusingvariousthirdpartyapplications.Withthis
information,youcandeterminetheSDsthatareinthesameRAIDgroup,and
groupthemtogether.
Thefollowingstepsdescribehowtocreatesystemdrivegroupsmanually.
1. NavigatetotheSystemDriveGrouppage(Home>Storage
Management>SystemDriveGroups).
TheSystemDriveGroupspageindicatesthenumberofSDsnotin
groupsandliststheSDgroupsthathavealreadybeencreated.
2. CreatetheSystemDriveGroup.
IntheSystemDriveGrouppage,clickcreate(iftheNumberofSystem
DrivesNotInGroupsiszero,thecreatebuttonisunavailablebecauseno
groupscanbecreated).TheCreateSystemDriveGrouppageopens,
allowingyoutomanuallygroupsystemdrives.
TheAvailableSystemDriveslistshowsallsystemdrivesinthestorage
serverorclusterthatarenotalreadyinagroup.
Storage Subsystem Administration Guide
67
SelecttheSDsyouwanttogrouptogetherfromtheAvailableSystem
DriveslistandclicktherightarrowtomovethemtotheSelectedSystem
Driveslist.
3. CreatethenewSystemDriveGroup.
IntheCreate System Drives Grouppage,clickOKtocreateanewgroup
containingtheSDsintheselectedlist.Repeatthesestepsasneededto
createthedesiredSDgroups.
Backing up or
Restoring SD
Groups
BackingupandrestoringSDgroupsisasimple,quick,anderrorfreemethod
oftransferringSDgroupdefinitionsamongclustersorserversthatshare
storageorwhenmovingstoragebetweenservers/clusters.SDgroupsare
backedupasapartofthenormalserver/clusterconfigurationbackupprocess,
sobackingupSDgroupsisnotnecessaryforfailurerecovery.
BackingupSDgroupsimposesaveryslightmanagementoverhead,andmay
causeothermanagementfunctionstoslowdownslightlyduringtheshort
timethebackupisbeingmade.Thereshouldbenonoticeableeffectonfile
servingthroughput.
AswithbackingupSDgroups,restoringsavedSDgroupswillnotcausea
significantoverhead,buttherearerulesaboutwhenyoucanandcannot
importgroups.Forexample,youcannotimportagroupthatincludesSDs
thatareusedinastoragepoolthathascurrentlymountedfilesystems.For
moreinformationontheserestrictions,seethesd-groupcommandinthe
CommandLineReference.
Note:Whenmovingstoragebetweenstandaloneserversorclusters,beaware
thatSDdeviceIDsusuallychange,whichmaymakeitseemasifgroupshave
beenimportedincorrectly.
TobackuporrestoreSDGroups:
1. NavigatetotheSystemDriveGroupsBackup&Restorepage.
FromtheStorageManagementpage,selectSystemDriveGroups,then
clickBackup&RestoretodisplaytheSystemDriveGroupsBackup&
Restorepage.
2. Backuporrestore:
68
Tobackup:Clickbackup.Inthebrowser,specifythenameand
locationofthebackupfile,thenclickOK/Save(thebuttonsdisplayed
andthemethodyouusetosavethebackupfiledependonthebrowser
youuse).
Abackupfilenameissuggested,butyoucancustomizeit.The
suggestedfilenameusesthesyntax:
SD_GROUPSyyyy-mm-dd_time-UTC-offset.txt,wherethefollowing
exampleillustratestheappropriatesyntax:SD_GROUPS2008-0430_1729-0700.txt
Torestore:ClickBrowsetodisplayadialogyoucanusetochoosethe
backupfile,navigatetothedirectorywherethebackupfileisstored,
selectthebackuptextfile(SD_GROUPS2008-04-30_1729-0700.txt)
forthespecificexport(s)youwanttorestore,thenclickOpen.
WhentheSystemDriveGroupsBackup&Restorepagedisplaysthe
nameandlocationoftheselectedfile,clickrestore.
Modifying System
Drive Groups
Aftersystemdrivegroupsarecreated,youcanmodifyagroupbyaddingor
removingsystemdrives.BeforemodifyingSDgroups,youmustfirst
determinethephysicallocationofthesystemdrivesalongwiththeRAID
configuration.Thisinformationcanbeobtainedusingvariousthirdparty
applications,suchasStorageNavigator.ContactyourHitachiDataSystems
representativeforinformationaboutwhichthirdpartyapplicationsare
supported.
Caution:Whenmodifyingasystemdrivegroup,youmustensurethatthesys
temdrivesbeingaddedtoagrouparelocatedonthesamephysicaldevices(or
RAIDgroup)asthesystemdrivesalreadyinthegroup.Otherwisesystemper
formancecanbeadverselyaffected.
Thefollowingstepsdescribehowtomodifysystemdrivegroupsmanually.
1. NavigatetotheSystemDrivesGrouppage(Home>Storage
Management>SystemDriveGroups).
69
TheSystemDriveGroupspageindicatesthenumberofSDsnotin
groupsandliststheSDgroupsthathavealreadybeencreated.
2. Selectthesystemdrivegroupyouwanttomodify.
IntheSystemDrivesGrouppage,clickdetailsforthesystemdrivegroup
youwanttomodify.TheModifySystemDriveGrouppageopens,
displayingthesystemdrivesthatareavailabletobegroupedandtheSDs
intheselectedgroup.
TheAvailableSystemDriveslistshowsallSDsinthestorageserveror
clusterthatarenotalreadyinagroup.TheSelectedSystemDriveslist
showstheSDsthatarealreadyincludedintheselectedgroup.
3. ModifytheSDgroup.
YoucanaddSDstotheSDgroupbyselectingthemintheAvailable
SystemDriveslistandclickingtherightarrowtomovetheSDstothe
SelectedSystemDriveslist.
YoucanremoveSDsfromtheSDgroupbyselectingthemintheSelected
SystemDriveslistandclickingtheleftarrowtomovetheSDstothe
AvailableSystemDriveslist.
4. Reviewandsaveyourchanges.
70
71
72
MK-92HNAS012-00