Академический Документы
Профессиональный Документы
Культура Документы
Introduction Written by: John Merryman GlassHouse Technologies, Inc. TivoliStorageManager(TSM)customersrarelymanageenvironmentswithfixedor shrinkingstoragepools.IfyouasaTSMadministratordofallintothisrarecategoryyou neednotreadfurtherasthispaperwillnotlikelybeofinteresttoyou.Ifyouarebeing askedtomanagemoredataandstorage,readon. DataDomainprovidesanalternativestoragesolutionforTSMcustomerswhoarefaced withneverendingdatagrowthandunabatedstorageexpansionassociatedwith ballooningbackupandarchivedata.WhileTSMisoneofthemostscalabledata protectionsolutionsavailabletothemarket,datagrowthanddataretention requirementsdrivenearcontinualexpansiontoTSMstoragepools. ThescopeofthiswhitepaperfocusesonhowtheDataDomainstoragesolution integrateswithstandardTSMarchitecturalandoperationalenvironments. TSMArchitectureandTerminology TivoliStorageManager(TSM)isaclientserversoftwaresolutiondesignedfor enterprisecustomers.Thecoreproductfunctionalityincludesbackup/recovery, archive/retrieval,HSM,anddisasterrecovery.Thefollowingfigureillustratesthe classicTSMarchitecturedesign.
GlassHouse Whitepaper
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
Figure1:ClassicTSMArchitectureDesign
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
EachTSMserverinstanceissupportedbyaselfmanagedrelationaldatabaseand recoverylog.Aprimarydiskstoragepooloftenservesasaninitiallandinglocationfor nightlybackups.ThisdataismigrateddailytothePrimaryStoragePoolandareplicaof thisdataismaintainedinaCopyStoragePool,typicallyforpurposesofdisaster recoveryandmediarecovery.Commonterminologyusedinthiswhitepaperis providedinthefollowingtable. Term SelectiveBackup Definition Selectivebackupsallowyoutomanuallyselectaset offilestobackupregardlessofwhethertheyhave changedsinceyourlastincrementalbackup. Incrementalbackupsonlybackupfilesthathave changedsincethelastincrementalbackup. Aprimarydiskpoolisastoragepoolconsistingof diskstoragevolumes.Diskpoolsaretraditionally usedfordailyincrementalbackupstaging,upon whichdataismigrateddailytoaprimarystorage pool. Anamedsetofvolumesthattheserverusestostore backupversionsoffiles,archivecopiesoffiles,and filesmigratedfromHSMclientnodes.Youcanback upaprimarystoragepooltoacopystoragepool. Primarystoragepoolscanbecomprisedoftapeor diskvolumes.Multiplestoragepoolscanbecreated, eachusingaspecificdevicetype. CopyStoragePool Anamedsetofvolumesthatcontainscopiesoffiles thatresideinprimarystoragepools.Copystorage poolsareusedonlytobackupthedatastoredin primarystoragepools. Copystoragepoolscanbecomprisedoftapeordisk volumes.Multiplestoragepoolscanbecreated,each usingaspecificdevicetype. LANFreeBackup Thedirectmovementofclientdatabetweenaclient machineandastoragedeviceonaSAN,ratherthan ontheLAN.LANFreebackupscanonlybe configuredtowritetoTSMtapeorvirtualtape devices. Anindustrystandardprotocolthatallowsanetwork storagemanagementapplicationtocontrolthe backupandrecoveryofanNDMPcompliantfile server,withoutinstallingthirdpartysoftwareon
IncrementalBackup PrimaryDiskPool
PrimaryStoragePool
NDMPBackup
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
Term Definition thatfileserver. Expiration Expirationisadailyadministrativeprocess,which deletesrecordsforTSMobjectswhichareexpired fromtheTSMdatabase. Reclamationisadailyadministrativeprocess,which reclaimsunusedspaceinsequentialstoragepoolsby mountingpartiallyfilledvolumesandmigrating datatoreturnthesevolumestoascratchstatus. Migrationisadailyadministrativeprocess,which migratesnewincrementalbackupdatafroma PrimaryDiskPooltoaPrimaryStoragePool. Migrationistypicallyscheduledasthelast administrativebatchprocess,priortotheproduction backupwindow. AnactiveTSMfilerepresentsthemostrecentactive versionofafileonthebackupclientmachine.An ActiveDatastoragepoolcontainsonlyactivefiles. TSMbatchprocessesincludenonbackupand restorerelatedprocesseswhichareessentialforTSM dailyoperations.Batchprocessesaretypically scheduledaftertheproductionbackupwindow,and includeadministrativeandstoragemanagement functionssuchasstoragepoolbackups,expiration, TSMdatabasebackups,andmigration.
Table1:TSMTerminology
Reclamation
Migration
ActiveDataPool
BatchProcess
TypicalTSMChallenges ThetypicalTSMenvironmentsupportshundredstothousandsofclients.TSMscalesby addingadditionalTSMserverinstances,andassociateddiskandtapestorageresources. ThemostcommonchallengesinTSMenvironmentsinclude: CompletingbatchTSMworkloads(storagepoolbackups,offsitetapevaulting, andreclamation)withlimitedtimeandphysicalresources Contendingwithextremelylargeclientbackups(>2TBincrementalchangeper client,orseveralmillionfileschangingperday) ScalingTSMinstances,databases,logs,storagepoolstokeepupwithsheer demand Eliminatingredundantdatabackups(copiesofdatabases,aggressivebackup retentionpolicies,etc.)
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
TechnologyOverview DataDomaineliminatesunnecessaryTSMdatastorageviadatadeduplicationand traditionalcompression.Datadeduplicationisperformedonincomingdatastreamsand allowsredundantsegmentsofdatatobeidentifiedandstoredasuniqueinstances withintheDataDomainRestorerfilesystem.Thefollowingtablelistskeyterminology forDataDomain. Term DataDomainRestorer(DDR) ProtectedDataSize Definition AstandaloneDataDomainstorageappliance, gateway,orasinglecontrollerinaDDXarray. Thesumtotalofallfilesizesintheactivesetof primarydatabeingbackedup(equivalenttothe TSM5.4conceptofActiveStoragePool). Thetotalsizeofallbackupimagesinallstorage poolsonaDataDomainRestorer.Thistotalsize includesallstoragepoolsinTSMmappedtoaData DomainRestorerinstance,whichcaninclude primarydiskpools,primarystoragepools,andcopy storagepools. Thesizeofanindividualbackupimagewrittentoa storagepool(forexample,onenightsworthof backupdata). TheamountofphysicalspaceavailableonaData DomainRestorertostorededuplicatedand compressedbackupimages. TheamountofaddressablecapacityonaData DomainRestorercurrentlystoringbackupdataand associatedmetadata. Theratioofthelogicalstoragesizetothephysically storedspace. Theratioofoneormorediskpooldumpstothe physicallyconsumedstorageforthosedumps.Note thattheperiodiccompressionfactoroverany intervalbeyondthefirstfewdayswilltypically exceedthecumulativecompressionfactorbyalarge marginbecausethefirstversionofafilewrittentoa Eliminatingperformancebottlenecks(TSMserverordatabase,networking, client,etc.) Lackofcapacityplanningandreportingdisciplines
LogicalStorageSize
DiskPoolDumpSize
AddressableCapacity
PhysicallyConsumedStorage
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
Term Definition DataDomainRestorerwillcompresslessthan subsequentversions.Considerforexampletwo selectivebackupsof100GBofprotecteddataover twonights:typicalperiodiccompressionfactors mightbe2:1thefirstnightand50:1thesecondnight, butthecumulativecompressionfactorwouldonly be~4:1(200GB/50+2GB)ratherthanthe25:1orso onemightexpect.Notefurtherthatwhilethe cumulativecompressionfactoriswhatdetermines costperGB,itistheperiodiccompressionfactorthat mostaffectsreplicationbandwidthrequirements. Deduplication LocalCompression Replacing4KBto16KBsegmentsinincomingdata streamswithverysmallreferencestoidentical segmentsalreadystoredondisk.Alsoknownas globalcompression.Segmentsizeisexpressedin binaryvalues. Standardlosslesscompressionalgorithms.The availableLocalCompressionalgorithmsavailableon aDataDomainRestorerincludeLZ(LempelZiv),gz andgzfast. Aperiodicprocesstofindanyunreferenced segmentsonaDataDomainRestorerandmakethat spaceavailableforsubsequentbackups.Because DataDomainRestorersneveroverwritedata,file deletesbyaTSMserverdonotimmediatelymake spaceavailableforsubsequentbackupscleaning mustrunfirst.Cleaningmaybeperformedona DataDomainRestoreratthesametimeas backup/restoreI/O,butbecausecleaningisafairly resourceintensiveprocessitisbesttoscheduleitfor nonpeakhours.Thedefaultscheduleforcleaningis Tuesdaymorningat6:00a.m.butmaybe rescheduledforanyconvenienttimesduringthe week.
Table2:DataDomainTerminology
Cleaning
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
whichperformdeduplicationatthefileleveloratablocklevel,resultinginmore efficientdeduplicationcapabilities. Sinceatmostsitestherateofprimarydatachange(newlyintroducedunique4Kto16K segments)staysaboutthesamefromnighttonight,theamountofphysicallyconsumed storageforaselectiveTSMbackupisroughlythesameasthephysicallyconsumed storageforanincrementalTSMbackup.Theratioofprotectedstoragesizeto incrementallyconsumedphysicalstorageeachnightstaysaboutthesame,butthe periodiccompressionfactorofanincrementalbackupismuchlowerthantheperiodic compressionfactorofaselectivebackup(becausetheformerismuchsmallerinsize). Asaresult,itisextremelyinexpensivetoincludemanyversionsoffilesinastoragepool onaDataDomainRestorer.Therelativesizeofprotecteddataandincrementalbackup data,beforeandafterdeduplicationandcompressionisillustratedinthefollowing figure.
Figure2:BackupDataDeduplicationandCompression
Bothdeduplicationandstandarddatacompression(alsoreferredasLocal Compressioninproductliterature)areexecutedvialosslesscompressionmethods(ie. nodataintegrityimpact).LempelZiv(LZ)compressionisstandard,howeverGZFastor GZarealternativesavailabletoeachDataDomainRestorerinstanceforstandarddata compression.Asarule,backupdatashouldnotbecompressedpriortoattempting additionalcompressionatthedevicelevel. DataDomainArchitectureandModels ThebaseDataDomainRestorermodelsupportsupto16TBofaddressablestorage, whichmeansthatdependingondatadeduplicationandcompressionrates,80241TBof logicalstorageisavailabletoeachinstanceofaDataDomainRestorer.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
EachDataDomainRestorerinstancesupports100MB/secaveragethroughput.Thisbase metricappliesbothtoreadandwriteoperations,asthearchitectureisoptimizedfor sequentialI/O. ModelName Addressable Capacity LogicalDataStorage (TB)* MaximumI/O Performance (GB/Hour)
DDX/16Fully Expanded usingDD560 DDX/16 DD560Fully Expanded DD560 DD460 DD430 DD410
1,2843,852 4131,239 80241 2679 2265 1132 412 410 297 225 164 6,554
Table3:DataDomainModels,AddressableandLogicalCapacity
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
Figure3:DataDomainRestorerArchitectureScalability
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
Figure4:TSMDataDomainRestorerIntegration
Fornetworkfilesystemaccess,TSMaddressestheDataDomainRestorerdeviceviaa nativeNFS/CIFSmount.TSMaddressestheusablespaceexactlyasitwouldastandard filesystemmountpoint(NTFS,JFS,UFS,etc.). TheVTLinterfaceemulatesaSTKL180tapelibrarymanager,andrequiresafiber channelconnectionalongwiththeappropriateTSMdevicedriver.NDMPbackupsare alsosupportedviatheDataDomainVTLinterface.MultipleinstancesofVTLcanbe createdperDataDomainRestorerinstance.Upto47LTOtapedrives,10000slots,and 100,000virtualcartridgescanbecreatedperDataDomainRestorerinstance.Asa standaloneVTL,existingphysicaltaperesourcescanbeleveragedbynativeTSM capabilities. Replication AsynchronousdatareplicationissupportedbetweenDataDomainRestorerinstances. Oncetheinitialmirrorreplicaisestablished,onlychangestoindex/metadataandnew datasegmentsarereplicatedtothetargetsite.Asaresult,WANbandwidth requirementsaresignificantlyreducedbyupto99%andtheamountoftimetoreplicate datatoanoffsitelocationissignificantlyreduced. ReplicationisconfiguredinCollectionorDirectorymode.Collectionmodeallowssingle DataDomainRestorerinstancestobeconfiguredinasourcetargetrelationship,with
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
10
Figure5:CollectionandDirectoryReplicationModes
HowDataDomainBestFitswithTSM ADataDomainRestorerprovidesanalternativefordiskandtapestoragepoolsinTSM. TheDataDomainfilesystemisoptimizedforsequentialreadandwriteoperations, whichmakeforagreatfitwithTSMproductionbackupandbatchworkloads.AData DomainRestorercanbeconfiguredasaprimaryorcopystoragepoolinTSM. Note:TSMwasdesignedforadeploymentmodelwherebackupdataiswritten firsttoaTSMprimarydiskpool(aDISKTYPEpoolontraditionaldiskmedia) andthensubsequentlycopiedtootherdiskortapestoragepoolsforlonger retention.TheDataDomainRestorerprovidesanoutstandingtargetforthese lattercopies,andinsmallerenvironmentsitisoftenpossibletoeliminatetheTSM primarydiskpoolaltogetherandtargetbackupsdirectlytoa(FILETYPE) storagepoolonaDataDomainRestorer.ForlargerTSMenvironmentswhere morethan20concurrentbackupsessionswouldberequiredperDataDomain
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
11
Restorerinstance,werecommendcontinueduseofaTSMprimarydiskpoolfor incomingbackupclienttrafficthatissubsequentlycopiedtoa(FILETYPE) storagepoolonaDataDomainRestorer. TSMdatabasesshouldcontinuetobeprovisionedontraditionaldiskdevices.AData DomainRestorershouldnotbeusedforstoringactiveTSMdatabases,logs,and configurationfiles.Instead,theseTSMelementscanbebackeduptoaDataDomain Restorerforoperationalrecoveryandreplicatedtoaremotesitefordisasterrecovery. Note:SomeTSMenvironmentssupportextremelyhighperformancebackupsfor highvolumeclients.Typically,specializeddesignsareimplementedtosupport backupsof14TB/hour.TheDataDomainRestorerarchitecturecanbeconfigured tosupporthighperformanceworkloads(viamultipleparallelinstanceswitheach DataDomainRestorerinstancesupporting100MB/secworkloadsoncurrently shippingDataDomainRestorers.
Planning/SizingConsiderations
BackupPoliciesandDataVolatility TSMpoliciesareuniquetoeachcustomerenvironment,buttypicallyrangefrom7to60 effectiveversionsforactivefiles.Mostsitesuseincrementalbackupsandrarelyrun selective(full)TSMbackups.Backuppoliciesandassociatedclientdatachangerates spellthefateofstoragepoolsizesinTSM.WhileTSMbenefitsfromanincremental foreverbackupmethodology,datavolatilityisthefinalarbiterfortheamountof backupdatastoredbyTSM. TheimpactofbackuppoliciesonDataDomainRestorersizingislesssignificantthanthe datavolatilityandactualdatachangerate.FromaTSMperspective,adatabasebackup mayappearnetneweachtimeitisbackedup,butfromaDataDomainRestorer perspective,theactualdatachangesmayresultinminimalnewphysicalstorage consumption.Databases,email,andunstructureddata(fileserverdata)willbenefitthe mostfromdatadeduplicationinmostproductionenvironments.Datagrowthissuesare alsocompoundedbyreportingcopiesofproductionandthehighvolumesof applicationtestdata,allofwhicharetypicallybackedupdailytoTSM.Thenetresultis aneverendingdemandforTSMphysicalstorageresources.DataDomaincountersthe effectsofuncontrolleddatagrowthonTSMstorage. Deduplicationbenefitsarerealizedovertimeandeventuallyplateauoncethebackup versioningpolicyandtheincrementalbackuptrafficisfullyrealized.Sincedatachange ratesvarybydatatypeandproductionenvironment,acombinationofbackuppolicies, datavolatility,anddatastructureimpactsDataDomainRestorersizingestimates. Sizing Sizingstoragecapacitiesforadatadeduplicationsolutiontakesintoconsiderationactual datachangerates,whicharenotvisiblefromaTSMperspectivesinceTSMviewsdata changeatthefile/objectlevel.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
12
TheratioofcurrentbackupdatatoDataDomainRestorerdatastorage(afterdata deduplication+compression)varies,butonaverageTSMcustomerscanexpectupto 15:1backupdatareduction.Thisratioiswhollydependentonthedatavolatility, backupmethodsbeingused,andthebackuppolicy. Note:ForcustomersusingVTLmode,DataDomainRestorerdoesnotrequirespace preallocationforvirtualtapevolumes.Asvirtualtapevolumesaremountedand filledintheDataDomainRestorer,physicalspaceisnothedgedforscratchvirtual tapevolumes.OtherVTLtechnologiespreallocatephysicaltapevolumes, regardlessofwhetherornottheyareempty,full,orfilling. AninitialsizingmetricfortheDataDomainRestoreristoestimatehalfoftheprimary volumeofdataonallbackupclients,ora2:1ratioofprimarydata(nottobeconfused withbackupdata)totheDataDomainRestoreraddressablecapacity.Anotherapproach istototaltheoccupancyofTSMstoragepoolsandestimateusableDataDomain Restorerstorageusingafactorof15:1(TSMStoragePoolOccupancytoDataDomain RestorerAddressableCapacity)andthenbufferwithcapacityoverhead,asoutlinedin thefollowingtable. Storage Pool Occupancy (TB) Data Domain Restorer Sizing Metric 15:1 15:1 15:1 CapacityOverhead DataDomain Restorer Addressable CapacityRequired (TB)Note1
40 30 50
Note1:ForPoolA:3.3TB=1.25*(40/15)
Table4:DataDomainRestorerSizingExample
FornewDataDomainRestorercustomers,DataDomainrecommendsongoingcapacity planning,throughadisciplineofsizing,provisioning,utilization,andongoing measurement.Thisidealcapacityplanningmethodincludesongoingmeasurement,and demandforecastingonceasubsetofproductionbackupdataissenttoaTSMserver usingDataDomainRestorerandpoliciesarefullyrealized.Generally,thebenefitsof datadeduplicationarerealizedovertimeasbackuppoliciesarefullyrealized.Only then,dodatavolumesplateauwithinDataDomainRestorerinstances. Note:AlthoughmostTSMenvironmentslimittheeffectivenumberofbackup versionsduetophysicalspacelimitations,theimpactofadditionalbackupversions toDataDomainRestorerisoftennegligible.Whilethisbenefitallowsmoreflexibility
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
13
foraggressivebackuppolicies,TSMdatabasesizeshouldremainakeyconsideration inTSMpolicyplanning.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
14
Figure6:TSMSiteIntegration
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
15
OneormoredirectoriescanbespecifiedasthelocationoffilesforaFILEdeviceclass. Asaresult,multipleDataDomainRestorerinstancescanbededicatedtoasingleTSM instance;howeverthebenefitsofdatadeduplicationdonotspanmultipleDataDomain Restorerinstancesatthistime.Storagepoolscontaininglikedatacanbemappedto individualDataDomainRestorerinstances,ortoindividualmountpointswithinaData DomainRestorer.Forexample,someTSMadministratorscreatepolicydomainsforall fileservers,whereasignificantvolumeofprimaryunstructureddataisredundant. Mappingthispolicydomainandassociatedstoragepool(s)toaDataDomainRestorer expandsthebenefitsofdatadeduplicationaboveandbeyondredundantbackupcopies. Thefollowingfigureillustratesthisconcept.
Figure7:MappingDataTypestoStoragePoolsandDataDomainRestorerInstances
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
16
IfaDataDomainRestorerinstancereachescapacity,individualdirectoriescanbe migratedtoanewDataDomainRestorerinstanceusingreplication,withminimal reconfigurationanddowntimerequirements.Forexample,ifallOracle,Exchange,and fileserverbackupsaremappedtoindividualDataDomainRestorerdirectories,a specificbackupdatatypecanbemigratedtoanewDataDomainRestorertoreduce capacityintheoriginalDataDomainRestorerinstance,allowingforadditionalcapacity andgrowth. LargeTSMenvironmentscontendwithaneverendingchallengeofperformance optimizationforsystemresources.Toavoidperformancebottleneckingandtoobtain optimalDataDomainRestorerperformance,multipleDataDomainRestorerscanbe deployedtosupportparallelworkload/performancedemands.Thesamearchitectural conceptappliestotraditionalfilesystemandphysicaldisklayoutplanningfor performanceworkloads.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
17
Figure8:LargeSiteTSMIntegration
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
18
Figure9:TSMDailyOperations
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
19
Figure10:TSMDailyOperationswithDataDomain
Capacityplanningandspacemanagementisanewoperationalrequirementwhenusing aDataDomainRestorerwithTSM.Justlikephysicaldiskandtaperesource managementinTSM,DataDomainRestorerinstancesmustbemanagedtoensure efficientutilizationandsufficientavailablespace.Asillustratedinthefollowingfigure, theTSMadministratorshouldmonitoravailableDataDomainRestorerspaceasa routineoperationaltask. Resource /ddvar Precompression DataIf100%cleaned* Metadata Index SizeGB 78.7 14949.7 19.4 17.2 UsedGB 17.7 6296.1 373.1 0.2 4.8 AvailGB 57.1 14576.6 18.2 12.3 Use% 24% 2% 1% 28%
Estimatedcompressionfactor*:16.6x=6296.1/(373.1+0.2+4.8)
Figure11:ExampleDataDomainRestorerStorageUtilization
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
20
TheDataDomainRestorerrequiresanadditionaloperationalprocesstoperform cleaningoftheDataDomainRestorerfilesystem,whicheffectivelyreclaimsspaceand optimizestheDataDomainRestorerfilesystemforperformance.Thedefaultschedule forcleaningistorunweekly,howeverdependingondatavolatilityandavailableData DomainRestorerspacethisprocesscanbescheduledmorefrequently(23timesper week). Note:TheDataDomainRestorercleaningprocessisresourceintensive.Athrottle commandisavailabletoassigntherelativeprioritytocleaningprocessestonormal backupandrestoreI/O.WerecommendtheDataDomainRestorercleaning processesrunperiodicallyaspartofstandardTSMoperations,scheduledwhen backup/restoreactivityisatminimumlevels. WhileexpirationprocessinginTSMimmediatelydeletesdatafromfiletypedevice classstoragepools,thedataisnotimmediatelydeletedfromvirtualtapevolumeswhen usingaDataDomainRestorerinVTLmode(exactlyasistruewithphysicaltape volumes).Consequently,TSMreclamationprocessingshouldstillberunonVTLstorage poolstoeffectivelyreclaimunusedspaceonvirtualvolumesandreturnthesevolumes toscratchstatuswithinTSM. RecoveryConsiderations ThemajorityofTSMsitesleveragetheincrementalforeverapproachforproduction backups.Whilethisminimizesbackupstorageresourcerequirements,incremental changesareoftenspreadacrossmultiplephysicaltapevolumes,andconsequentlylarge restoreoperationsrequiremultiplemountsandinsomecasessignificantamountsof timetoperformrestoreoperations. TSMadministratorscontendwiththischallengebyleveragingstoragepoolcollocation, runningperiodicselectivebackups,orperformingmovenodedataoperationsto consolidateclientdataontofewerphysicalvolumes.Eachoftheseoptionsdemandtape processingresources,oftenwhichareinhighdemandinabusyTSMenvironment. ADataDomainRestorerstoragepool(andmovingfromtapeingeneral),eliminatesthe sequentialaccesslimitationsofphysicaltape,andprovidesimmediateaccesstoall incrementalbackupobjectsrequiredforarestoreoperation.Thiscapabilitycan significantlyimproverestoreperformanceforTSM. Note:AswithanyTSMstoragedevice,therestoreperformanceofeachData DomainRestorerinstance(100MB/sec)mustbetakenintoconsiderationwhen planningforlargeclientorlargescale(disasterrecovery)restoreoperations.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
21
IntegrationBasics
TSMServerTuning TSMServertuningisrecommendedfornewDataDomainRestorerimplementations usingNFS/CIFSandIPprotocol.TheTSMoptionscanbesetbymodifyingthe DSM.OPTserverconfigurationfileorbyexecutingtheassociatedSETcommands. Note:SomeTSMServerconfigurationchangesrequireaTSMserverrefreshtotake effect. ThefollowingtableoutlinesstandardTSMservertuningparametersforoptimalData DomainRestorerperformancewithTSM,usingNFS/CIFSandIPprotocol. ConfigurationType Comments
AIXNetwork Configuration
HPUXNetwork Configuration
SOLARISNetwork Configuration
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
22
ConfigurationType Comments
echo3276826214416777216> /proc/sys/net/ipv4/tcp_wmem echo262144>/proc/sys/net/core/rmem_max echo262144>/proc/sys/net/core/wmem_max echo262144>/proc/sys/net/core/rmem_default echo262144>/proc/sys/net/core/wmem_default echo536870912>/proc/sys/kernel/shmmax echo536870912>/proc/sys/kernel/shmall WINDOWSNetwork Note: DonotmodifytheWindowsregistryparameter Configuration AFDiftheTSMserveroranyassociatedTSMclientsare supportedbyWindowsNT4.0 1.OpenREGEDT32andnavigateto: HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCON TROLSET\SERVICES\AFD\PARAMETERS 2.AddanewDWORDvaluetotheDefaultSendWindow keyandsetthevalueto65536(decimal). 3.AddanewDWORDvaluetothe DefaultReceiveWindowkeyandsetthevalueto65536 (decimal). 4.WithinREGEDT32,navigatetothefollowinglocation: HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCON TROLSET\SERVICES\TCPIP\PARAMETERS 5.AddanewDWORDvaluetothe GlobalMaxTcpWindowSizekeyandsetthevalueto 65536(decimal). 6.AddanewDWORDvaluetotheTcpWindowSizekey
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
23
ConfigurationType Comments
Note:TSMbufferpoolspacepreallocatesphysicalmemoryasamemorycache forTSMdatabasetransactions,andprovidesdatabaseperformance improvements.TSMbufferpoolsizingmustbecustomizedbyadjustingthe bufferpoolsizetotheamountofphysicalmemoryavailabletotheTSMserver. NetworkFileSystemIntegration NFSisthemostcommonlyusedTSMimplementationmethodforaDataDomain Restorer.NFSmountsrequireIPprotocolandadedicatedGigabitVLANordirect GigabitconnectionisrecommendedforTSMserverintegration.Jumboframesmaybe usedtomaximizeTCP/IPprotocolefficiencyandprocessoroverheadontheTSMserver. NetworkconnectiontrunkingisnotcurrentlysupportedbytheDataDomainRestorer. DataDomainrecommendsthefollowinggeneralNFSconfigurationsettingsfor mountingaDataDomainRestorertoaTSMserver. TSMServer Platform AIX NFSConfiguration mountvnfso proto=tcp,vers=3,intr,hard,combehind,rsize=32768,wsize=32768,llock ndd200restorername:/backup/mountpoint mountFnfsohard,intr,vers=3,proto=tcp,rsize=32768,wsize=32768 restorername:/backup/mountpoint mountFnfsorsize=32768,wsize=32768,hardrestorername:/backup /mountpoint mounttnfsointr,hard,rsize=32768,wsize=32768,proto=tcp,vers=3 ddr:/backup/dd/<mountpoint> CIFSaccesstoDataDomainRestorerisrecommendedforWindows TSMServers
Table6:NFSMountConfigurationGuidelines
Note:DataDomainonlysupportsTCPprotocolwithNFS,andrecommends hardmountstoensureavailabilityafterTSMserveroutages.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
24
StoragePoolandDeviceClassDesignConsiderations TSMallowsdisktypedeviceclassestobedefinedaseitherFILEorDISKtype.FILE deviceclassesarecommonlyusedinTSMforvirtualvolumemanagement,however, mostTSMadministratorsdefinediskstoragepoolsusingDISKdeviceclassdefinitions andassociateformatted*.dsmfilesasstoragepoolvolumes. Note:TheTSM5.3and5.4AdministratorsGuidestatesTivoliStorageManager supportstheuseofremotefilesystemsordrivesforreadingandwritingstorage pooldata,databasebackups,andotherdataoperations. FILEtypedeviceclassesarerecommendedforusewithaDataDomainRestorer.FILE deviceclassesallowTSMtoperformsequentialread/writeactivitytofileswithinafile system.Incomingbackupdataiswrittentoafile,andonceafileisfilled,anewscratch fileisautomaticallycreatedbyTSMandisfilledwithadditionalincomingbackupdata. Note:Random/DiskdeviceclassesarenotsupportedwiththeDataDomain Restorerasastoragepooldevice. SeveraloptionsexistfordeviceclassandstoragepoolconfigurationsinTSM.TheFILE deviceclassforsequentialmediaallowsafilesystemmountpointtobedefinedfora primaryorcopystoragepool. OneormoremountpointscanbespecifiedasthelocationoffilesforaFILEdeviceclass; howeverthereisnobenefittocreatingmultipledirectories/mountpointswithinasingle DataDomainRestorerinstancefromaperformanceperspective,howeverkey advantagesareexploredaboveintheIntegrationPlanningsection. DeviceClassConfiguration Detail Directory CreateaseparatefolderforeachTSMdeviceclass (FILETYPE) Performcapacityplanningandmeasurementto ensuretheDataDomainRestorercapacityis adequateforeachfolder Ifsubdirectoriesarecreated,exportthe subdirectoriesviaNFStoensureTSMcalculates accuratespaceforvolumes. FormultipleTSMserversusingasingleData DomainRestorerinstance,createaseparatefile systemmountpointorfolderforeachTSMinstance MaximumCapacity ThedefaultTSMMaxCapacityvalueforaFILE deviceclassis2GB.Dependingontheoperating systemoftheTSMserver,maximumcapacity parametersvary.Thisparameterissizedbetween 200and400GBforDataDomainRestorer
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
25
DeviceClassConfiguration Detail implementations. MountLimit ThedefaultMountLimitvalueis20andthe maximumvalueforthisparameteris4096.This meansthatupto4096individualfilescanbeopened atasingletime.EachDataDomainRestorer instancesupportsupto20concurrentI/Othreads, sothedefaultMountLimitvalueisrecommended.
Table7:TSMFileDeviceClassConfigurationStandards
Figure12:NDMPIntegrationwithTSMandDataDomainRestorer
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
26
LANFreeBackupIntegration TSMsitesleverageLANFreebackupsforlargedatabasebackups(usuallydatamarts andwarehouses)directtotape.LANFreebackupsaretypicallyconfiguredwith212 tapemounts(dependingonthedrivetechnology)perbackupclient,toaccommodate extremelyhighperformancebackups.ThebackupdatamovesacrossFiberChannel directlyfromtheTSMclientmachinetothemountedtapedevices,whilebackup metadataisbrokeredtotheTSMserveroverIP.FiberChanneloffersthebenefitofdirect channelconnectivityandareductioninserverCPUresourceconsumptionduringthe backupwindow. LargeTSMLANFreeimplementations(withdozenstohundredsofmountpoints)must accomplishaperfectbalancingactoftapedriveavailability,availablemountpoints, andappropriatebackupschedulingtoavoidcontentionformountpoints.Whenthe balancingactfails,sodomanyLANFreebackupjobsthatusuallyhavealimited windowavailableforproductionbackup.WhenLANFreebackupsoverlapwiththe batchTSMwindow,resourcecontentionissuestypicallycascadeandTSM administratorsendupsacrificingeithermissed/failedLANFreebackupsordailybatch processes.WeincreasinglyseededicatedIPbasedalternativesreplacinglegacyLAN Freeconfigurations,duetoloweradministrativeoverheadandmanagementcomplexity. ForTSMsitesthatneedtoretainLANFreechannelconfigurationsfornetwork performancereasons,aDataDomainRestorerrunninginVTLmodeoffersan alternativesolution.VTLoffersahighnumberofavailablemountpointsandhigher availabilityofvirtualtapedrivescomparedtophysicalcounterparts.SeveralData DomainRestorerinstanceswouldneedtobedeployedtoprovidethesamebackup performanceinaLANFreeconfigurationusingseveralhighperformancetapedrives. ThefollowingdiagramillustratesTSMLANFreeintegrationwiththeDataDomain Restorer.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
27
Figure13:TSMLANFreeClientIntegrationwithDataDomainRestorer
ActiveDataPools ActiveDatapoolsareanewTSMfeatureaddedinTSM5.4.Thisfeaturegroupsactive TSMfilestogether,whichcangreatlyincreasethespeedofTSMrestores.TheData DomainRestorerprovidesanoptimallocationforActiveDatapools.ByplacingActive DatapoolsonthesameDataDomainRestorerastheprimarystoragepools,therewill bealmostnoimpactonthespacerequiredtostoretheActiveDatapools.SincetheData DomainRestorerisalreadystoringtheprimarypoolwithalltheactiveandinactive copies,theActiveDatapoolswillcontain100%duplicatedata. Note:ActiveDataPoolssignificantlyreducerestoretimesfromphysicaltape storagepoolsonly.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
28
Figure14:UsingActiveDatapoolswithDataDomainRestorers
ArchivingIntegration LongtermdataretentioninTSMisaccomplishedeitherviatraditionalbackupor archivefunctionality.TSMarchivefunctionsasaselective,nonincrementalcopyofdata forlongtermretention.Byextendingbackupmanagementclassretentionsettings, traditionalbackupscanbescheduledonaninfrequentbasis(monthly,quarterly,etc.) usinganalternateTSMnode(BackupClient01_Arc).ThisalternateapproachallowsTSM toaccomplishlongtermretentionwiththebenefitsofincrementalbackupcopies. ForTSMsitesdesiringlongtermretention,aDataDomainRestorercanbeleveragedas aprimaryorcopystoragepoolforarchivedata,orasastagingareaforincoming archivedata.ThefollowingdiagramillustratesTSMarchivedatamovementtoaData DomainRestorerarchivestoragepool,whichisconfiguredtomigratedataperiodically toanarchivetapepoolforlongtermretention.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
29
Figure15:TSMArchivingtoTapewithaDataDomainRestorerforArchiveStaging
TSMarchivedatacanalsobearchiveddirecttotape,whichworkswellforlargeobject archives(largefiles,databases,etc.). TSMDatabaseBackups TSMdatabasebackupsarecriticaltotherecoveryofaTSMserver.ATSMdatabase backupcanbefullorincremental,andcapturesalltransactionscurrentlycommittedto thedatabase.Databasebackupsareusuallywrittentotapeanditistypicalfortwofull TSMdatabasebackupstobedoneeachday.Onebackupissentoffsitefordisaster recoverypurposesandtheotheriskeptonsiteforoperationalrecovery. AdrawbackofTSMbackuptotapeisthateachbackupmustbeonitsowntape.This leadstoinefficientuseoftapecapacityespeciallywithtodayslargertapecapacities. WithatypicalLTO3cartridgeholding1TB,a100GBTSMdatabasewillleave90%of thetapeunutilized.Witha5daydatabaseretentionandtwobackupsaday,each instanceofTSMwillhave10tapesthataresignificantlyunderutilizedforDBbackups. WiththeintroductionofaDataDomainRestorertotheTSMenvironment,TSMDB backupscanbewrittendirectlytotheDataDomainRestorer.WhenTSMdatabase backupsaresenttotheDataDomainRestorer,storagespaceisnotwasted;thisistrue whethertheDataDomainRestorerisusedinVTLmodeorsequentialaccessfilemode. ADataDomainRestorerattheprimarysitecancutthenumberoftapesusedforTSM databasebackupsinhalf.IfasecondDataDomainRestorerisintroducedatanalternate
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
30
Figure16:TSMDatabaseBackupusingDataDomainRestorers
TSMDisasterRecovery SeveralarchitecturalscenariosexploretheuseofaDataDomainRestorerasacentral mechanismforvaultingTSMdatatoanalternatesiteforpurposesofdisasterrecovery. AswithanyothermethodofperformingTSMdisasterrecoveryoperations,theTSM database,configurationfiles,andstoragepoolsmustbeavailableforrecovery operations. Note:ATSMdatabaseinstancecanonlyrecoverdatafromdirectlyassociated storagepools.StoragepoolsallocatedtootherTSMinstancescannotberecoveredto asingleTSMserver. WerecommendtheuseofTivoliDisasterRecoveryManager(DRM)toautomate TSMdisasterrecoveryoperations.Thegeneralsequenceofeventstorecovera TSMserverinstanceincludesthefollowingsteps.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
31
Note:TostarttherecoverprocessyouwillneedanewserverrunningthesameOS andpatchlevelastheproductionTSMserveranditwillneedtobeconnectedtothe DataDomainRestorerattheDRsite. 1.InstalltheTSMserverCode 2.ConfiguretheTSMservertoseetheDataDomainRestorerfilesystems,they mustbeconfiguredidenticaltothewaytheywereinproduction. 3.DefinetheTSMdatabaseandlogfilesystemstomatchwhatwasconfiguredin production 4.Formatthedatabaseandlogvolumes 5.Usedsmservrestoredbtorestorethedatabase 6.RegisterTSMserverlicensing 7.Inventoryrequiredmediaforstoragepools(onlyifphysicaltapeis managedbyTSM) 8.Resumebackupandrestoreoperationsinalternatebackupenvironment
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
32
ArchitecturalScenarios
LocalDataDomainPrimaryStoragewithManualTapeVaulting Inthescenarioillustratedinthefollowingfigure,aDataDomainRestorerinstanceis usedtoreplacetraditionalTSMdiskandtapeprimarystoragepools.
Figure16:LocalDataDomainRestorerPrimaryStoragewithManualTapeVaulting
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
33
Figure17:LocalDataDomainRestorerPrimaryStoragewithElectronicTapeVaulting
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
34
Figure18:LocalDataDomainRestorerPrimaryStoragewithReplicationtoOffsiteDataDomainRestorer
ByutilizingtheDataDomainRestorerdevicesatboththeprimaryandalternatedata center,thedailyoperationaltasksforbackupstoragepoolsarereduced.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
35
Figure19:MixedTSMProduction/DRwiththeDataDomainRestorerReplication
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
36
Figure20:CentralDisasterRecoveryDataCenterConfiguration
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
37
Figure21:RemoteOfficeLocalandDisasterRecoveryConfiguration
Conclusion DataDomainarchitectureoffersavarietyofnewstoragearchitecturestrategiesforTSM customers.TheTSMapplicationfunctionsasiswiththeDataDomainRestorer interfacemethods,minusthecomplexitiesandmanagementoverheadassociatedwith physicaltapemedia.Fortheenterprise,disasterrecoveryreplicationofTSMdatahas traditionallyrequiredsignificantarchitecturalmeasuresandmanagementoverhead. DataDomainarchitectureprovidesaviableoffsitereplicationalternative,whichis coupledwithareductionindailyTSMbatchoperationalprocesses. WeseeaparticularlycompellingcasefortheDataDomainRestorertorevolutionizethe waysmallandremoteTSMsitesmanagephysicalstorageresourcesandreplicationfor disasterrecovery.ForextremelylargeTSMinstances,appropriateplanning,sizing,and integrationstrategiesmaketheDataDomainRestoreraviablesolutionforthe enterprise.
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
38
Copyright2007GlassHouseTechnologies,Inc.Allrightsreserved.
39
40