Net 装机维护 ClusteredDataONTAP82SANAdministrationGuide.docx

1、NetAppxClusteredDataONTAP8.2SANAdministrationGuideNetApp, Inc.495 East Java Drive Sunnyvale, CA 94089 U.S.Part number: 215-07953_A0May 2013Telephone:+1(408)822-60Fax:+1(408)822-4501Supporttelephone:+1(888)463-8277Web:Feedback:doccommentsContentsPreparingforLUNsetupLUNsetupworkflow9DecidingwhichLUNty

2、petouseinSANenvironments10HowtherateofchangeinyourdatadeterminesLUNtypeIOCalculatingRateofChange11HowmuchroomdoyouneedforSnapshotcopies12HowLUNsconsumespaceonavolume13AdditionalconsiderationsforthinlyprovisionedLUNs13WhatLUNthinprovisioningis13WhentousethinlyprovisionedLUNs15WhythinlyprovisionedLUNs

3、gooffline15HowtokeepyourthinlyprovisionedLUNsonline16WhattodoifyourLUNsgooffline24Additionalconsiderationsforspace-reservedLUNs25Whatspace-reservedLUNsare25Whentousespace-reservedLUNswithoutSnapshotreserve26Whentousespace-reservedLUNswithSnapshotreserve26SPaCe-reservedLUNsinathinlyprovisionedvolume2

4、7UnderstandingspaceusageofLUNsandSnapshotcopies28ShowingdiskspaceusageforLUNswithoutSnapshotcopies28ShowingdiskspaceusageforLUNswithSnapshotcopies31SANconfigurationsalwaysuseFIexVoIvolumes36Volumeconfigurationoptions37ConsiderationsforsettingfractionalreserveforFlexVolvolumes37WhatSnapshotautodelete

5、is38Whentousetheautodelcteconfiguration39Whatsnapreserveis39HowDataONTAPcanautomaticallyprovidemorespaceforfullFIexVolvolumes39ConfiguringvolumesinaSANenvironment41ConfiguringvolumesforthinlyprovisionedLUNs4lConfiguringvolumesforspace-reservedLUNswithoutSnapshotreserve45Configuringvolumesforspace-re

6、servedLUNswithSnapshotreserve481.UNsetup52LUNguidelinesforSANenvironments52RecommendedandsupportedSANconfigurations53ConsiderationswhencreatingaLUNfromanexistingfile53ConsiderationsaboutLUNidentificationnumbers53GuidelinesforprovisioningstorageinaSANenvironment54GuidelinesformappingLUNstoigroups54Gu

7、idelinesforLUNlayoutandspaceallocation55UnderstandingLUNfunctions55HowfileandLUNreservationsworkforFlexVolvolumes56HowthehostoperatingsystemaffectsusablespaceforaLUN56LUNavailabilityonspecifictargetLIFs56HowDataONTAPavoidsigroupmappingconflicts57SnapMirrordestinationsandread-onlyLUNs57Introductionto

8、LUNsinavirtualizedSANenvironment58HowLUNaccessworksinavirtualizedenvironment58HowtolimitLUNaccessinavirtualizedenvironment61ConsiderationsforLIFsinclusterSANenvironments61SettingupLUNs61SettingupLUNsmanuallywithiSCSIblockaccess62SettingupLUNsmanuallywithFCblockaccess69SettingupLUNsusingtheVserverset

9、upwizard77ManagingdataprotectioninyourSANenvironment79Dataprotectionmethods79CopyingallLUNsonavolumewiththevolumecopycommand81UsingSnapshotcopiestoprotectyourdata83RequiredchangestoSnapshotcopydefaultsettings83RestoringasingleLUNfromaSnapshotcopy83RestoringalltheLUNsinavolumefromaSnapshotcopy85Delet

10、ingoneormoreexistingSnapshotcopiesinavolume87UsingFlexCloneLUNstoprotectyourdata88ReasonsforusingFlexCloneLUNs88WhatFlexCloneLUNautodeleteis89HowaFlexVolvolumecanreclaimfreespacefromFlexCloneLUNs89ConfiguringaFlexVolvolumetoautomaticallydeleteFlexCloncLUNs.90CloningLUNsfromanactivevolume92CloningLUN

11、sfromaSnapshotcopyinavolume93PreventingaspecificFlexCloneLUNfrombeingautodeleted94ConfiguringandusingbackupvaultsinaSANenvironment96Accessingaread-onlyLUNcopyfromabackupvault97RestoringasingleLUNfromabackupvault98RestoringallLUNsinavolumefromabackupvault100Howyoucanconnectahostbackupsystemtotheprima

12、rystoragesystem103BackingupaLUNthroughahostbackupsystem104ManagingLUNs106MisalignedI/OcanoccuronproperlyalignedLUNs106ControllingandmonitoringI/OperformancetoLUNSbyusingStorageQoS107IncreasingthesizeofaLUN108DecreasingthesizeofaLUN109DeletingLUNs109ExaminingconfiguredandusedspaceofaLUN110Commandsfor

13、managingLUNs111Commandsformanagingportsets112ManagingLIFs113LIFmigrationinaSANenvironment113RemovingaSANLIFfromaportset114MovingSANLIFs114DeletingaLIFinaSANenvironment116FCandFCoELIFsonthesameportneedtobeinseparatezones117Understandingigroupfunctions118Whatigroupsare118igroupexample119AboutiSCSIinit

14、iatornodenames120FCprotocolinitiatorWWPN120WhatALUAis120MPIOandALUA121Managingigroups122Commandsformanagingigroups122iSCSIservicemanagement123HowiSCSIisimplementedonthehost123HowiSCSIauthenticationworks123iSCSIinitiatorsecuritymanagement124WhatCHAPauthenticationis124GuidelinesforusingCHAPauthenticat

15、ion124iSCSIinterfaceaccessmanagement125ManagingyouriSCSIservice126Definingasecuritypolicymethodforaninitiator126EnablingiSCSIsessionerrorrecoverylevels1and2127DeletinganiSCSIserviceforaVserver128CommandsformanagingiSCSIservices128iSNSserverregistration132WhatiSNSis132WhataniSNSserverdoes132HowVserve

16、rsinteractwithaniSNSserver132AboutiSNSserviceversionincompatibility135RegisteringaVserverwithaniSNSse,er135CommandsformanagingiSNS137iSCSItroubleshootingtips138LUNsnotvisibleonthehost138ResolvingiSCSIerrormessagesonthestoragesystem139UnderstandingFCandFCoESANfunctions141HowFCswitchesareidentified141

17、Howworldwidenameassignmentswork142UnifiedEthernetnetworkmanagement142FibreChanneloverEthernetoverview143Whatdatacenterbridgingis143ManagingsystemswithFibreChanneladapters145ConfiguringFCadaptersforinitiatormode145ConfiguringFCadaptersfortargetmode147DisplayingthestatusofonboardFCadapter148Displaying

18、informationaboutanFCtargetadapter149ChangingtheFCadapterspeed150CommandsformanagingFCadapters151ManagingyourFCservice153ChangingtheWWPNforanFClogicalinterface153DeletinganFCserviceforaVserver154VerifyingthatDCBisconfiguredcorrectly154CommandsformanagingFCprotocols155Volumemanagement158Virtualization

19、ofstorage159LUNalignmentinvirtualenvironments159ImprovingVMwareVAAIperformanceforESXhosts160RequirementsforusingtheVAAIenvironment160HowtodetermineifVAAIfeaturesaresupportedbyESX161ImprovingMicrosoftremotecopyperformance161RequirementsforusingODX162Specialsystemfilerequirements162Considerationsforus

20、ingODX163UsecasesforODX164BasiciSCSIandFCconcepts166Howhostsconnecttostoragesystems166WhatHostUtilitiesare166AboutSnapDriveforWindowsandUNIX167HowDataONTAPimplementsaniSCSInetwork167WhatiSCSIis167WhatiSCSInodesare168HowiSCSItargetnodesconnecttothenetwork168HowiSCSInodesareidentified168Storagesystemn

21、odename169Howthestoragesystemchecksinitiatornodenames169DefaultportforiSCSI169HowiSCSIcommunicationsessionswork170HowiSCSIworksinaVserver170HowDataONTAPimplementsanFCSAN170WhatFCis170WhatFCnodesare170HowFCtargetnodesconnecttothenetwork171HowFCnodesareidentified171HowWWPNsareused171Copyrightinformati

22、on172Trademarkinformation173Howtosendyourcomments174Index175PreParingforLUNSetUPWOrkfIOWAprerequisiteforcreatingLUNsisthatyouhaveanaggregate,aVserver,andavolume.AlsobeforeyoucanbeginLUNsetup,youmustdecidewhattypeofLUNthatyouneedforyourSANenvironmentandconfigureyourvolumeforthatLUNtype.Relatedconcept

23、sDecidingwhichLUNtypetouseinSANenvironmentsonpage10LUNsetupworkflowAfteryouhaveconfiguredyourvolumeforaspecificLUNtype,youcanbeginconfiguring(settingup)yourLUNs.Configurationinvolvesseveralsteps.1.UNsetupVerifyingthelicenseforFCoriSCSIEnablingblockaccessforaVserverwithiSCSI,FC,orFCoECreatingLUNsandm

24、appingigroupsCreatingportsetsandbindingigroupstoportsetsEnablingblockaccessforaspecifichostRelatedconcepts1.UNsetuponpage52DecidingwhichLUNtypetouseinSANenvironmentsYoushoulddecidehowyouwanttoallocatespaceforLLTNsandSnapshotcopiesbeforeyouconfigureyourvolumeorsetupyourLUNs.Doyouwanttoreservespaceahe

25、adoftime(space-reservedLUNs),ordoyouwanttoallocatespaceasneeded(thinlyprovisionedLUNs)?YoucanreservespaceupfrontoraddspaceasneededforLUNsandSnapshotcopiesinyourvolume.YoushouldanswerthefollowingquestionstodeterminethetypesofLUNsandSnapshotcopiesthatworkbestinyourenvironment:Doyouwanttoallocatespaceo

26、nyourvolumeasneededforyourLUNsandSnapshotcopies?DoyouwanttoreservespaceonyourvolumeforyourLUNsandSnapshotcopies?DoyouwanttoreservespaceonyourvolumeforyourLUNsbutallocatespaceasneededforyourSnapshotcopies?Howcloselydoyouneedtomonitoryourenvironment?WilltheamountofdatainyourLUNsgrowquickly?Howyouanswe

27、rthesequestionsdetermineswhichofthethreecommonusagescenariosforallocatingspaceinyourvolumeforyourLUNsandSnapshotcopiesworksbestforyourenvironment.Thethreecommonusagescenariosareasfollows:ThinlyprovisionedLUNsSpace-reservedLUNSwithoutSnapshotrese,eSpace-reservedLUNswithSnapshotreserveRelatedconceptsA

28、dditionalconsiderationsforthinlyprovisionedLUNsonpage13Additionalconsiderationsforspace-reservedLUNsonpage25HowtherateofchangeinyourdatadeterminesLUNtypeTherateofchangeinyourdatahelpsyoudeterminewhattypeofLUNbestsuitsyourenvironment,space-reservedLUNorthinlyprovisionedLUN.IRateofdeletionorchangeofda

29、taINotesLotsofdeletes(highrateofchange)Usespace-reservedLUNsNeedextraroomforSnapshotcopiesSetfractionalreserveto100%RateofdeletionorchangeofdataVerylowrateofchange(lowrateofchange)Steadygrowth(lowrateofchange)Notes UsethinlyprovisionedLUNsUsethinlyprovisionedLUNs UsevolumeautogrowInconsistentgrowthU

30、sethinlyprovisionedLUNsUsevolumeautogrowtoensureroomforLUNsUseSnapshotautodeleteUsespacereclamationifpossibleCalculatingRateofChangeYouwillneedtoknowtherateatwhichyourdataischangingovertimetodeterminewhetheryoushouldusespace-reservedLUNsorthinlyprovisionedLUNs.AboutthistaskIfyouhaveaconsistentlyhigh

31、rateofdatachange,thenspace-reservedLUNsmightbeabetteroptionforyou.Ifyouhavealowrateofdatachange,thenyoushouldconsiderleveragingtheadvantagesofthinprovisioning.Youwillneedtoobserveyourdataoverasetperiodoftimetodetermineyourrateofchangeasaccuratelyaspossible.Steps1. Setupaspace-reservedLUN.2. Monitort

32、hedataontheLUNforasetperiodoftime,suchasoneweek.3. Eachday,recordinGBhowmuchyourdatachanges.4. Attheendofyourmonitoringperiod,addthetotalsforeachdaytogetherandthendividebythenumberofdaysinyourmonitoringperiod.Thiscalculationyieldsyouraveragerateofchange.Youneeda200GBLUNandaretryingtodetermineifitsho

33、uldbeaspace-reservedLUNorathinlyprovisionedLUN.YoudecidetomonitortheLUNforaweekandrecordthefollowingdailydatachanges: Sunday-20GBMonday-18GBTuesday-17GBWednesday-20GBThursday-20GB Friday-23GBSaturday-22GBInthisexample,yourrateofchangeis(20+18+17+20+20+23+22)/7=20GBperday.HowmuchroomdoyouneedforSnaps

34、hotcopiesThelongeryouneedtokeepSnapshotcopies,themorespaceyouneedtosetasideforyourSnapshotcopies.YoucanusevolumeautosizetoautomaticallygrowyourvolumetoensureyouhaveenoughspaceforyourLUNandSnapshotcopies.YoucanalsouseSnapshotautodeletetoremoveSnapshotcopies.Some Snapshot copies for a long durationFor

35、moreinformationaboutSnapshotautodelete,seetheClusteredDataONTAPDataProtectionGuide.Formoreinformationaboutvolumeautosize,seetheClusteredDataONTPLogicalStorageManagementGuide.HowlongdoyouneedaSnapshotcopyfor?NotesLotsOfSnaPShotcopiesforalongduration.LeaVealargepercentageofroomforSnapshotcopiesUseSnap

36、shotautodeleteaggressivelyHighertherateofchangethemoreroomyouneedUseSnapshotreserveUsevolumeautogrowbeforesnapshotautodeleteSomeSnapshotcopiesforashortdurationUseSnapshotwithoutreserveLeaveasmallpercentageofroomforSnapshotcopies.EnsuresnapshotautodcletedocsnotdeletetheSnapMirrorcopies.Usevolumeautog

37、rowbeforesnapshotautodeleteHowLUNsconsumespaceonavolumeThinlyprovisionedandspace-reservedLUNsconsumespaceonavolumedifferently.WhenyoucreateathinlyprovisionedLUN,thisLUNconsumesalmostnospaceinitscontainingvolume.DatawrittentothethinlyprovisionedLUNisallocatedfromthevolumesfreespace,andanequalamountof

38、spaceisaddedtotheLUNsusedsize.Incontrastwhenyoucreateaspace-reservedLUN,theamountofspaceequaltotheLUN,sconfiguredsizeisremovedfromthefreespaceofthevolumeimmediatelyuponcreation.TheusedsizeofaLUNcannotbelargerthantheconfiguredsize.RelatedtasksEnablingspaceallocationforthinlyprovisionedLUNsonpage22Add

39、itionalconsiderationsforthinlyprovisionedLUNsWhenyouusethinlyprovisionedLUNs,DataONTAPhasseveralstrategiesthatcanhelpkeepyourLUNsonline,suchaseffectivemonitoring,spacereclamation,andappropriatevolumesizing.Additionally,DataONTAPhasseveralstrategiesformakingmorespaceavailableonyourvolumes:volumeautog

40、rowSnapshotautodelete,FlexCloneLUNautodeleteAutomaticspacereclamationFormoreinformationaboutthesestrategies,seetheClusteredDataONTAPLogicalStorageManagementGuide.RelatedconceptsHowDataONTAPcanautomaticallyprovidemorespaceforfullFlexVolvolumesonpage39WhatSnapshotautodclcteisonpage38WhatFlexCloneLUNau

41、todeleteisonpage89WhatLUNthinprovisioningisThinprovisioningenablesstorageadministratorstoprovisionmorestorageonaLUNthaniscurrentlyavailableonthevolume.Usersoftendonotconsumeallthespacetheyrequest,whichreducesstorageefficiencyifspace-reservedLUNsareused.Byover-provisioningthevolume,storageadministrat

42、orscanincreasethecapacityutilizationofthatvolume.WhenanewthinlyprovisionedLUNiscreated,itconsumesalmostnospacefromthecontainingvolume.AsblocksarewrittentotheLUNandspacewithintheLUNisconsumed,anequalamountofspacewithinthecontainingvolumeisconsumed.Withthinprovisioning,youcanpresentmorestoragespacetot

43、hehostsconnectingtotheVserverthanisactuallyavailableontheVserver.StorageprovisioningwiththinlyprovisionedLUNsenablesstorageadministratorstoprovideuserswiththestoragetheyneedatanygiventime.Theadvantagesofthinprovisioningareasfollows:Providesbetterstorageefficiency. AllowsfreespacetobesharedbetweenLUN

44、s. EnablesLUNstoconsumeonlythespacetheyactuallyuse.ExampleofavolumewiththinlyprovisionedLUNsAnadministratorcanprovisiona4,000-GBvolumewithfivethinlyprovisionedLUNswith1,000GBofspaceforeachLUNasshowninthefollowingtable.Table1:ThinlyprovisionedLUNsona4,000-GBvolumeLUNnameSpaceactuallyusedbytheLUNConfi

45、guredspaceavailabletoLUNIunl100GB1,000GBlun2100GB1,000GBlun3100GB1,000GBlun4100GB1,000GBlun5100GB1,000GBTotals500GB5f000GBAll5LUNsuse100GBofstorage,buteachLUNhasthepossibilityofusing1,000GBofstorage.Inthisconfiguration,thevolumeisovercommittcdby1,000GB,butbecausetheactualspaceusedbytheLUNsis500GB,th

46、evolumestillhas3,500GBavailablespace.ThinprovisioningallowsLUNstogrowatdifferentrates.Fromthepoolofavailablespace,aLlTNcangrowasblocksofdataarewrittentothatLUN.IfalltheLUNsusedalltheirconfiguredspace,thenthevolumewouldrunoutoffreespace.ThestorageadministratorneedstomonitortheVserverandincreasethesizeofthevolumeasneeded.YoucanhavethinlyprovisionedandSPaCe-reservedLUNsonthesamevolumeandthesameaggregate.Forexample,youcanusespace-reservedLUNsforcriticalproductionapplications,andthinprovisionedLUNsforothertypesofapplicati