2.3 Product Manual Models: 400, 500, 500 R, and 1000

Transcription

1 MiraLinkCorporation 2.3ProductManual Models:400,500,500 R,and MiraLinkCorporation AllRightsReserved. MiraLink andintellibuffer aretrademarksofthemiralinkcorporation. DocumentID:2.0.7

2 LicenseAgreement IMPORTANT:PLEASEREADTHESETERMSANDCONDITIONSCAREFULLYBEFORE USINGTHEHARDWARE.BYINSTALLINGTHEUNITS,LOGGINGINTOTHEUNIT,OR OTHERWISE USING THE PRODUCT OF MIRALINK CORPORATION AND ITS SUPPLIERS,YOUAGREETOBEBOUNDBYTHETERMSANDCONDITIONSOFTHIS LICENSE.IFYOUDONOTAGREEWITHTHETERMSOFTHISLICENSE,PROMPTLY RETURN THE UNUSED EQUIPMENT, SOFTWARE, AND ACCOMPANYING MANUAL, (WITHPROOFOFPAYMENT)TOEITHERTHESERVICEPROVIDERORRESELLEROF THEPRODUCTORMIRALINKFORAFULLREFUND.IFYOUHAVEORDEREDTHIS SOFTWAREOREQUIPMENTINWHICHTHISSOFTWAREISEMBEDDED,MIRALINK S ACCEPTANCEISEXPRESSLYCONDITIONALONYOURASSENTTOTHESETERMSTO THEEXCLUSIONOFALLOTHERTERMS;IFTHESETERMSARECONSIDERED AN OFFERBYMIRALINK,ACCEPTANCEISEXPRESSLYLIMITEDTOTHESETERMS. Thisisanagreement( Agreement )betweencustomerandmiralinkcorporation. 1.LICENSEGRANT.MiraLinkCorporation( MiraLink ),grantstocustomer( Customer )a nonexclusiveandnon transferablelicense( License )touseonecopyofthesoftwarerelease ( Software ),inobjectcodeform,solelyinconjunctionwithamiralinksystemownedorleased bycustomer.asusedhere, Product referstothesoftware,ortothesoftwareandhardware, whichisprovidedtothecustomerbymiralink,includingthecorrespondingusermanualsand otherdocumentationprovidedbymiralink. EXCEPT AS EXPRESSLY AUTHORIZED ABOVE, CUSTOMER SHALL NOT: COPY, IN WHOLE ORINPART,SOFTWAREORDOCUMENTATION;TRANSLATE,MODIFY, OR CREATEDERIVATIVEWORKSOFTHESOFTWARE;REVERSEENGINEER,DECOMPILE, OR REVERSE ASSEMBLE ALL OR ANY PORTION OF THE SOFTWARE; OR SUBLICENSE, RENT, LEASE, DISTRIBUTE, OR SELL THE SOFTWARE. Any attempted transferorassignmentofrightsunderthisagreementwithoutpriorwrittenconsentfrommiralink isvoid. 2.OWNERSHIP.TheenclosedSoftwareanddocumentationandallcopiesthereofareownedby MiraLinkand/orothersfromwhomMiraLinkhasobtainedarespectivelicensingright,andare protectedatleastbycopyright,trademarkandtradesecretlawsandinternationaltreatyprovisions. THISSOFTWAREISLICENSEDANDNOTSOLD. 3. PROPRIETARY INFORMATION. Customer agrees that aspects of the licensed materials, including the specific design and structure of individual programs, constitute trade secrets, proprietaryinformation,and/orcopyrightedmaterialofmiralink.customeragreesnottodisclose, provide,orotherwisemakeavailablesuchtradesecrets,proprietaryinformation,orcopyrighted materialinanyformtoanythirdpartywithoutthepriorwrittenconsentofmiralink.customer

3 agrees to implement reasonable security measures to protect such trade secrets, proprietary information,andcopyrightedmaterial. 4. UPGRADES.From timetotime MiraLinkmay releasenewversions ofthe Software that containimprovements.ifyoupurchase,receive,ordownloadanupgrade,thisagreementwillbe extendedtoincludeboththeoriginalversionofthesoftwareandthenewversion. 5.TERM.ThisSoftwareLicenseAgreementiseffectiveuntilterminated.Customermayterminate this AgreementatanytimebynotifyingMiraLink.MiraLink,oranythirdpartyfromwhom MiraLink may have obtained a respective licensing right, may immediately terminate this AgreementifCustomerfailstocomplywithanytermorcondition.Uponanyterminationofthis Agreement,CustomershallimmediatelydiscontinuealluseoftheProductandreturntoMiraLink allofthesoftware,printedmaterials,andrelatedequipment. 6.LIMITEDWARRANTY.MiraLinkwarrantsthatSoftwarewillsubstantiallyconformtothe publishedspecificationsforsuchproductifusedinaccordancewithproducts documentationas outlined below. MiraLink warrants that parts will be under warranty for one (1) year, with installationlaborunderwarrantyforninety(90)daysfromthedateofinstallationordateofinitial useofproductbycustomer,whicheverislater.thiswarrantyalsocoversanyandallsoftware componentsembeddedwithinthehardwareofproductsproducedbymiralinkcorporation.the Softwareiscoveredforaperiodofninety(90)daysfromthedateofpurchaseafterthewarrantyis activated. Tobeeligibleforaremedy,Customermustreportallproblemswithinthewarrantyperiodto MiraLink,andmakesuitablearrangementsforsuchserviceinaccordancewithanyinstructions received from MiraLink. MiraLink s sole and exclusive obligation and Customer s sole and exclusiveremedywithrespecttononconformingsoftwarereportedduringthewarrantyperiod willbeeitherto(i)provideacorrectionoraworkaroundforanyreproducibleerrorscausedbythe Software,or(ii)refundtoCustomertheportionofthelicensefeeorpurchasepriceapplicableto theproductiftheremedyin(i)aboveisnotreasonablyavailable.anerrorcausedbycustomer s otherhardwareorsoftwarewillnotbeeligibleforaremedy.customeragreestocooperatewith MiraLinkinrecreatingtheenvironmentinwhichtheerroroccurred.Further,Customeragreesto supply any necessary equipment for such tests. If there is a MiraLink Corporation s Product WarrantyStatementincludedwithunits,itisincorporatedhereinbythisreference.Pleasereview themiralinkcorporationproductwarrantystatementforfurtherwarrantydetails. ThisLimitedWarrantydoesnotapplytoSoftwarewhich(i)hasbeenaltered,exceptasauthorized bymiralink,(ii)hasnotbeeninstalled,operated,repaired,ormaintainedinaccordancewithany installation,handling,maintenance,oroperatinginstructionssuppliedbymiralink,(iii)hasbeen subjectedtounusualphysicalorelectricalstress,misuse,negligence,oraccident,(iv)hasbeen usedinsuchawaythatmiralinkcannotreasonablyreproducethesoftwareerror,(v)hasbeen exportedfromtheoriginalcountryofdestinationwithoutwrittenconsentofmiralinkor(vi)has beenmisapplied.innoeventdoesmiralinkwarrantthattheproductiserrorfreeorthatcustomer willbeabletooperatetheproductwithoutproblemsorinterruptions.

4 THIS WARRANTY IS IN LIEU OF AND MIRALINK DISCLAIMS ALL OTHER WARRANTIESANDCONDITIONSNOTREFERENCEDHEREIN,WHETHERSTATUTORY, EXPRESS OR IMPLIED, INCLUDING THOSE OF MERCHANTABILITY, NONINFRINGEMENT,ANDFITNESSFORAPARTICULARPURPOSEWITHRESPECTTO THEPRODUCTANDANYACCOMPANYINGPRINTEDMATERIALS.EXCEPTFORTHE FOREGOING,THEPRODUCTISPROVIDED ASIS. 7.LIMITATIONOFLIABILITY.INNOEVENTSHALLMIRALINK,OTHERSFROMWHOM MIRALINK HAS OBTAINED LICENSING RIGHTS, OR MIRALINK S SUPPLIERS, BE LIABLE WITH RESPECT TO THE SOFTWARE, ANY SUBJECT MATTER OF THIS SOFTWARELICENSEAGREEMENT,ORANYRELATEDPRODUCTORDERUNDERANY CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHER THEORY (A) FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES INCLUDING, WITHOUTLIMITATION,LOSTPROFITSORLOSSORDAMAGETODATA,(B)FORCOST OFPROCUREMENTOFSUBSTITUTEGOODS,SERVICESORTECHNOLOGY,OR(C)FOR ANYMATTERBEYONDITSREASONABLECONTROL,EVENIFMIRALINKHASBEEN ADVISEDOFTHEPOSSIBILITYOFANYOFTHEFOREGOINGDAMAGES.INNOEVENT WILLMIRALINK SLIABILITYEXCEEDTHEAMOUNTPAIDBYCUSTOMERFORTHE PRODUCT. Some states donot allowlimitationor exclusionof liability forconsequential or incidentaldamages. 8.THIRD PARTYDISCLAIMER.Exceptasexpresslyagreedotherwise,thirdpartiesfromwhom MiraLinkmayhaveobtainedalicensingrightdonotwarranttheSoftware,donotassumeany liabilitywithrespecttoitsuse,anddonotundertaketofurnishanysupportorinformationrelating thereto. 9.EXPORT.Customerwillcomplywithallapplicableexportlawsandregulationsifitexportsany of MiraLink s products or documentation. This restriction and all provisions on ownership, confidentiality, warranty disclaimer, and limited remedies shall survive termination of this Agreement. 10. GOVERNMENT ACQUISITION. If Customer is a unit or agency of the government, or acquiring the Softwarewithgovernment funds, thesoftwareanddocumentationareprovided subjecttomiralink sstandardcommerciallicense;provided,however,thatanycontractswithnon defense agencies subject to the FAR, the Government shall have the rights set forth in subparagraph (c) of FAR , Commercial Computer Software Restricted Rights, as applicable. 11.GENERAL.ThisSoftwareLicenseAgreementisthecompleteandexclusivestatementofthe mutualunderstandingofthepartiesandsupersedesanyotheragreementrelatingtothesoftware. ThisAgreementmaynotbemodified,amendedorinanywayalteredexceptbyawrittenstatement signedbybothmiralinkandcustomer.thisagreementshallbeconstruedpursuanttothelawsof thestateoforegonandtheunitedstateswithoutregardtotheconflictoflawsorprovisions

5 thereofandwithoutregardtotheunitednationsconventiononcontractsfortheinternational SaleofGoods,andalldisputesarisinghereundershallbeheardinOregon.TotheextentthatEC lawisapplicable,therestrictiononreverseengineeringislimitedtoprohibitsuchactivitytothe maximumextentwithoutviolatingtheecdirectiveonthelegalprotectionofcomputerprograms. NowaiverofanybreachofanyprovisionofthisAgreementshallconstituteawaiverofanyprior, concurrentorsubsequentbreachofthesameoranyotherprovisionshereof,andnowaivershallbe effectiveunlessmadeinwritingandsignedbyanauthorizedrepresentativeofmiralink.ifany portionhereofisfoundtobevoidorunenforceable,theremainingprovisionsofthisagreement shallremaininfullforceandeffect.

6 TableofContents GettingStarted HardwareModels It sjustaharddrive CommonConfigurationTypes PreparingToInstall OverviewofOperations PoweringSystemsOn/Off Chapter2:Installation Overview PhysicalConnections PoweronSystems InitialSynchronization ConnectingtotheMiraLinkUserInterface ConfigureUnitsforDeployment AdditionalRecommendations Chapter3:MiraLinkUserInterfaceandConfiguration Login Status Settings Network SNMP Role Intellibuffer Resync ChangeAdministratorPassword Shutdown/Reboot Logout Chapter4:Monitoring WhattoLookFor MonitoringthroughtheUserInterface MonitoringwithSNMP Chapter5:DisasterRecovery ConceptualOverview DisasterRecoverySequenceofEvents TypesofDisasters Chapter6:DisasterRecovery DataRecovery SystemMirror DataMirror PrimaryStorage Chapter7:DisasterRecovery RestoringLocalOperations DriveFailureDetectionandProcedures Chapter8:GettingHelp Appendixes

7 GettingStarted WelcometoMiraLinkCorporation sproductmanualformodels400,500,and1000.thisguide willhelpyouinstall,configureandproperlymonitoryournewlypurchasedmiralinksolution. MiraLink is the leader in remote disk mirroring over IP networks. Our products deliver an unprecedentedlevelofinformationsafety,simplicity,andlowcostofownership.byutilizingyour existingipnetwork,miralinkunitsprovideacompleteandreal timecopyofcriticaldatatobe maintainedoff siteatafractionofthecostofcompetingtechnologies. 1.1.HardwareModels TheMiraLinkfamilyofproductsincludes5models.Allmodelssharethesamearchitecture,with thehigherendmodelsusingscalableraidstoragearrays. Desktop(MiraLink400) Height:6½ Depth:17 Width:17 Weight:29lbs Rackmount(MiraLink Series) Height:4U 7 Depth:28 Width:17 fitsinto19 rack Weight:55lbs FibreChannelandiSCSI : MiraLinkunitscanalsotakeadvantageofFibreChanneloriSCSItechnologieswiththeuseofa bridgingdevice.pleasecontactmiralinksalesorsupportformoreinformation. 1.2.It sjustaharddrive ThisisaphrasethatisfrequentlyheardinthehallwaysatMiraLinkCorporation. Sure,we re proud of the complex technology we ve produced to combine synchronous and asynchronous mirroringoveralow bandwidthconnection,carefullypreservingthewriteorderandeverytinybit ofyourdatainordertoprovideyouwithaperfectmirrorofyourdataataremotesite. Despite its complexity, though, one of the best things about our product is that, from the perspectiveofyourserver,it sjustaharddrive.youdon thavetoinstallspecialsoftwareonyour servertousethemiralinkunits.theserverisnotawarethatthedevicethatisscsi attachedtoit isanythingotherthanasimpleharddrive. 1

8 Becauseyoucanuseitasyouwouldanyexternalharddrive,themethodsforemployingitin operationaluseandindisasterrecoveryareendless.intheconfigurationdiscussions,wefocuson themostcommonconfigurationtypes.inthedisasterrecoverysections,weconcentrateonthe mostdevastatingscenarios. Everynetworkisdifferent.Notwoimplementationswillbethesame.Wetrytocoverthecases thatwillbeusefultothemostcustomers.ifyoudon tfindtheproceduresforyourexactsituation, sometimesithelpstostepbackandrememberthat it sjustaharddrive. Ifthatdoesn thelp,flip totheendofthismanualforourcontactinformation! OperatingSystemSupport TheMiraLinkunitssupporttheSCSIprotocol,andshouldworkwithanyoperatingsystem thatsupportsscsidisks.pleasecontactsalesorsupportforalistoftestedandcertified SCSIadaptersforuseinyourserver. Wetestwiththelatestsupportedversionsofoperatingsystems.Itisyourresponsibilityto ensurethatyourserverisup to datewiththelatestpatchesanddriversavailablefromthe vendor. 1.3.CommonConfigurationTypes TherearethreeprimarywaystoconfigureanduseyourMiraLinkdevices.Yourconfigurationwill dependontheneedsofyourinfrastructureandyourdisasterrecoverystrategy.pleaseconsultthe followingdescriptionstodeterminewhichtypeofconfigurationyouwillbeusing.wewilluse thesetermstodistinguishbetweenthethreestandardconfigurationsthroughoutthisguide. SystemMirror Thisconfigurationtypeisusedtomakeanexactcopyoftheserver soperatingsystem drive in case of a hardwarefailure or disaster situation. The primary benefit of this configurationmethodisthatitresultsinabootableimageonthemiralinkunitatthe remotesite.thedrawbackisthatittypicallyinvolvesmirroringmuchmoredatathanis necessary.inordertobootanewserverusingtheremotemirror,youwillneedtohavean identicalstandbyserveravailableattheremotesite. DataMirror Ifyouwanttomakeanexactcopyofoneormoreofyourdatadrives,youwouldconfigure youroperatingsystemtomirrorthedrive(s)toyourmiralinkunits.inthisconfiguration, youwillbemirroringonlythedatathatyouneed,andthestandbyserverattheremotesite neednothaveidenticalhardware. However,thestandbyservermusthavetheoperating systeminstalled,astheremotemirrorwillnotbeabootableimage. 2

9 PrimaryStorage Onceeverythingisproperlyconnected,yourOperatingSystemwillseetheMiraLinkunit asanotherharddrive.tousethemiralinkunitasprimarystorage,partitionandformatit usingthesameproceduresusedtoconfigureotherharddrivesonyoursystem,andthenuse itforstoringdata.thisscenarioremovestheoperatingsystem smirroringfunctionality, whichmayreducethecomplexityoftheconfigurationandimproveperformance. The drawbackisthatyouhaveonlyasinglecopyofthedataattheprimarysite;usingamirror resultsintwocopiesofthedataattheprimarysite,whichcanbeusedintheeventofa serverhardwarefailure. NOTE:Throughoutthisdocument,werefertothelocationoftheproductionserver(s)as theprimarysite,andthesecondarylocationas theremotesite.themiralinkunitsare referredtoasthesourceunit(attheprimarysite)andthedestinationunit(attheremote site). Peerunit referstothemiralinkunitpairedwitheitherthesourceordestination unit. Figure1.1 demonstratesthebasicfunctionalityofyourmiralinkunits.onceyouconfigurea systemmirror,adatamirror,orprimarystorage,thedatawillbecopiedfromthesourcemiralink unitresidingattheprimarysitetothedestinationmiralinkunitattheremotesite. Figure PreparingToInstall AswithallInformationTechnology(IT)endeavors,goodpreparationwillfacilitateasmoothand successfulinstallation.beforeyoubegin,takethetimetoreadthroughthismanualandplanhow youwillusethemiralinkunits. PlanYourDisasterRecoveryStrategy BeforeyouinstallyournewMiraLinkdevices,itishighlyrecommendedthatyouhavea businesscontinuity(a.k.a.disasterrecovery)planinplace.thisdocumentshouldnotbe 3

10 consideredabusinesscontinuityplan;itcontainsonlyinstructionsfortheoperationofyour MiraLinkunits.YourITplanandproceduresforresumingthecriticalfunctionsofyour network after a disaster will be specific to your business needs and infrastructure. Proceduresformaintainingthedisasterrecoverysolutionandrecoveringafteradisaster shouldbeclearlydocumentedbeforedisasterstrikes! PrepareYourNetwork TheMiraLinksourceunitwillneedanIPaddressonthenetworkattheprimarysite,and thedestinationunitwillneedanipaddressonthenetworkattheremotesite(thefactory defaultipaddresses, and ,canbeusedfortheinitialsynchronization andconfiguration).ifyouhaveafirewallorotherport filteringdeviceinplacebetween yourprimaryandremotesites,youwillneedtoconfigurethemtoallowsometraffic throughinorderforthemiralinkunitstofunctionproperly. ToaccesstheMiraLinkUserInterface,whichisusedforconfiguringtheMiraLinkunits, youwillneedtoallowconnectionsfromyourworkstationtoport80(http),andoptionally 443(https),onboththesourceanddestinationunit. In order to mirror data between your MiraLink units, the units must be able to communicatewitheachotheronport248inbothdirections(seefigure1.2).forsecurity reasons,youshouldrestrictport248sothatonlythemiralinkunitscanconnecttoeach other. ItisstronglyrecommendedthatyousetupaVirtualPrivateNetwork(VPN)betweenthe primaryandremotesitesinordertoprotecttheconfidentialityofyourdata. Figure1.2 WARNING! Ifport248isblockedineitherdirection,youwillbeunableto mirrordata. PrepareYourSpace DependingonwhichMiraLinkmodelyoupurchased,youwillneedtopreparetheproper amountofspaceforplacementofthemiralinkdevices.allmiralinkmodelsare4urack mountable,withtheexceptionofthemiralinkmodel400,whichisdesignedtobeplaced onorbelowadesk. 4

11 PrepareYourDisasterRecoveryServer Afteradisaster,inordertoaccessyourdataimmediatelyattheremotesite,youwillneed tohaveaspareserveravailableattheremotesite.ifyouaremirroringyoursystemdriveto themiralinkunits,itisimperativethattheserverhardwarebeidenticaltothehardwarein theserveratthelocalsite,becausethesystemstoreshardwareconfigurationinformation onthedrive. ITMaintenanceWindow AswithallSCSIdevices,youmustpoweroffyourserverbeforeconnectingtheMiraLink source unit to the server. Depending on your Information Technology processes and procedures,youmayneedtoscheduleamaintenancewindowfortheinstallationofyour MiraLinkunits.InstallationofaModel400,500,or1000typicallyrequires30minutesto 2hours. Notethatthesetimeestimatesrefertoactualserverdowntime. Theydonottakeinto accounttimerequiredforbuildingalocalmirrororcopyingdatatothesourceunit,or transferringthedatatothedestinationduringtheinitialsynchronization.yourservercan beupandoperationalduringthattime,althoughperformancemaybereducedduetohigh diskactivity.timerequiredtocompletetheinitialsynchronizationwillvarydependingon yourconfigurationtype,theamountofdata,andyournetworkspeed. 1.5.OverviewofOperations Now that you have your new MiraLink units, you will want to install them, customize the configurationtoyourparticularneeds,andthenmonitortheunitstomakesurethateverythingis workingaccordingly. Installation Installation involves configuring and synchronizing both systems at the primary site. Chapter 2 walks you through everything from connecting the cables to preparing the destinationunitforitsjourneytotheremotesite.chapter3containsdetailsonusingthe MiraLinkUserInterfacetoconfigureyourMiraLinkunits. Deployment Afteryouhavefinishedtheinitialconfigurationandsynchronization,youwillrelocatethe destinationunittotheremotesiteandbeginreal timemirroringbetweenyourprimaryand remotesites. Monitoring Onceeverythingisphysicallyinplaceandconfiguredthewayyouwantit,youwillbeable tomonitoryourmiralinkdevices.thesimplestwaytomonitoryourmiralinkdevicesis throughtheuserinterfaceforeachdevice.miralinkalsoprovidesacustomizedmibfor usewithsnmpmonitoringsolutions.chapter4providesdetailedinformationonhowto monitoryourunitsandwhattolookfor. 5

12 1.6.PoweringSystemsOn/Off InordertopreventlossofdataandensureproperfunctioningofyourMiraLinkunitsandserver, alwaysfollowtheseprocedureswhenpoweringsystemsonoroff. ShuttingSystemsDown AlwaysusetheMiraLinkuserinterfacetoshutdownorreboottheMiraLinkunits.Cutting thepowertotheunitabruptlycancausedataloss. WARNING!Alwaysshutdowntheserverbeforeshuttingdownorrebootingthe MiraLinksourceunit. Ifthesourceunitisshutdownbeforetheserver,itappearstotheserverasthoughoneofits hard drives has disappeared. Depending on the timing of the event, this can cause operatingsystemorapplicationproblems. Additionally,ifthereisinformationintheserver swritecachethathasnotbeenwrittento themiralinkdrive,thatdatacouldbelost. TurningSystemsOn YourserverinteractswiththeMiraLinksourceunitasitwouldwithanySCSIharddrive. InorderfortheMiraLinkunittoberecognizedasaSCSIdevice,itmustbepoweredon beforetheserver,sothattheoperatingsystemcanidentifythemiralinkunitasitboots. Allow90secondsafterpoweringontheMiraLinkunit,beforepoweringontheserver. UseaUniversalPowerSupply(UPS) BothMiraLinkunitsshouldbepluggedintoaUPSwithsufficientbatterpowertokeepthe unitrunningintheeventofapoweroutageuntilitcanbeshutdowngracefully.abrupt lossesofpowertothemiralinkunitscanresultindataloss. ANoteAboutWriteCaching Mostoperatingsystemscacheinformationinmemorybeforewritingittodisk. Thisis donetoimproveperformance,asthedatacanbewrittenlater,whenthesystemisless active. Intheeventofasuddenlossofpowerordisconnectbetweentheserverandthe sourceunit,datathatisintheserver swritecachemaynothavebeenwrittentodisk.this canresultindatacorruptiononboththesourceanddestinationunits,similartothedata corruptionthatcanoccuronaninternalharddrivewhensystemsareturnedoffsuddenly insteadofshutdowngracefully. 6

13 Chapter2:Installation ThischapterdescribesthestepsforinstallingandconfiguringyourMiraLinkunits. 2.1.Overview Afterunpackingtheequipmentandconnectingcablesasnecessary,youwillattachtheMiraLink sourceunittoyourserverandbeginwritingdatatoit.yourserverwillinteractwiththemiralink unitsinthesamewayitwouldwithanyotherexternallyattachedharddrive.thereisnomiralink softwaretoinstallonyourserver. Youmayfindithelpfultohavethedocumentationforyour operatingsystemonhandforspecificinformationonhowtoview,format,andwritetoexternal SCSIdevices. YouwillusetheMiraLinkUserInterfaceonboththesourceanddestinationunitstoconfigurethe MiraLinkunits.TheinterfacecanbeaccessedusinganyInternetbrowser.Mostcustomersprefer to use a laptoporworkstation as theconfigurationclient ratherthantheirproductionserver. Havingaseparatesystemreducesdowntime,becauseyoudonothavetochangetheIPaddresson yourproductionserver,anditisalsomoreconvenient,becauseyoumayneedtoaccesstheuser interfaceatatimewhentheserveristurnedoff. Duringtheinitialinstallation,werecommendthatcustomerssetupbothMiraLinkunitsatthe primarysite,andthenshipthedestinationunittotheremotesiteaftertheinitialsynchronization. The following steps describe how to install and configure everything before shipping the destinationunittotheremotesite.ifyouhavealreadyshippedthedestinationunitdirectlytothe remote site, you can still follow these instructions, but be aware that the time required for synchronizationmaybemuchlongeriftheunitsarenotatthesamelocation. If you are reading this, you have probably already unpacked the MiraLink units and the accompanyingcablesanddocumentation.thenextsectionexplainshowtoconnectthemiralink unitsinpreparationfortheinitialconfiguration. Remembertokeepthepackingmaterialsforthedestinationunit, sothatyoucanprotectitintransittotheremotesite. 2.2.PhysicalConnections AfteryouhaveunpackedtheMiraLinkunitsandpreparedyourspace,makesurethatallsystems arepoweredoffandperformthefollowingsteps: 7

14 1. RefertothelabelsoneachyourMiraLinkunitstodeterminetheunit sfactorysetrole (sourceordestination).yourserverwillbeconnectedtothesourceunit,anddatawrittento thesourceunitwillbeautomaticallymirroredtothedestinationunit. 2. AttachoneendoftheprovidedSCSIcabletotheportlabeled HostSCSIBus ontheback ofthesourceunitandtheotherendtothescsiportontheserver.(ifyoupurchaseda FibreChanneloriSCSIbridge,attachthesourceunittothebridgeinsteadoftotheserver. Refer to the bridge s documentation for proper configuration of the bridge.) Pleasechecktheappendixorcontactyoursalesorsupport representativeforacompletelistofsupportedscsicards foruseintheserver. 3. Connectthesourceunit,destinationunit,andthecomputeryouwillusetoaccessthe MiraLink User Interface (any computer with an Internet browser will suffice) to an EthernethuborswitchusingstandardRJ 45cables.Usinganisolatednetwork(separate VLAN or switch) during installation will reduce the time required for the initial synchronization. WARNING WhenusingSCSIdevices,youmustpoweroffallconnecteddevicesbefore disconnectingorconnectingscsicables.failuretodosocanresultintemporarysoftware malfunctionorpermanentdamagetosystemhardware. Figure2.1illustratesthephysicalconfigurationdescribedabove. Figure PoweronSystems Whenpoweringonyoursystems,itisimportanttopowerthemupinthecorrectordersothatall componentsareproperlyrecognized.whenpoweringonthemiralinkunits,allowatleast90 secondsfortheunittofullybootupbeforepoweringonthenextdevice. 8

15 NOTE: In order to prevent data loss in the event of a power failure, it is strongly recommendedthatyouconnectyourmiralinkunitstoabackuppowersource(ups). Pleasemakesureyoupoweroneverythinginthefollowingorder: Ethernethub/switch MiraLinkdestinationunit MiraLinksourceunit Server(attachedtothesourceunitviaSCSIcable) Wheneverythingispoweredonproperly,theserverwillseetheMiraLinksourceunitasahard disk device attached to the SCSI controller. Please refer to server s operating system documentationforinstructionsonpartitioningandformattinganewharddisk. WARNING! If the components are powered up in the wrong order, or if you power everythingonatthesametime,someofthedeviceswillnotproperlyrecognizeeachother. 2.4.InitialSynchronization AssoonasyouconfigureyourservertousetheMiraLinksourceunitasaharddrive,theMiraLink sourceunitbeginsmirroringthedatatothedestinationunit. Ifthenetworkisnotconfigured properly,orifthedatachangerateoverthelocalscsibusisfasterthanthebandwidthonyour network,dataisqueuedinthesourceunit sintellibuffer untilitcanbesenttothedestination unit. WhenyouformattheMiraLinkunitorsetitupasamirror,thereistypicallyalotofdatawrittenat once.thisistheprimaryreasonforhavingthesourceanddestinationunitsinthesamelocationfor the initial configuration. Data travels much more quickly over a local network than over the Internet. NOTE:IfyouwishtohavemultiplepartitionsormirrorsontheMiraLinkdrive,itismuch faster to build one partition or mirror at a time than to build multiple partitions concurrently. BeforeyoureconfigureyourMiraLinkdevicesforproductiondeployment,youshouldcomplete theinitialformattinganddatatransfertothemiralinksourceunitandlettheintellibufferdrain completely. You can use the MiraLink user interface to monitor the progress of the synchronization. 9

16 2.5.ConnectingtotheMiraLinkUserInterface MiraLinkunitsshipwithdefaultnetworksettingsthatyouwillusefortheinitialconfiguration. Thefollowingisalistofthedefaultandrecommendednetworksettingsforinitialconfiguration: Table1 1 MiraLinkSource MiraLinkDestination ServerorLaptop IPAddress Netmask TheuserinterfaceiscoveredindetailinChapter3.Thischapterdescribesonlythestepsyouwill useduringinstallationanddeployment. ConnecttotheMiraLinksourceunitbytypingthefollowingURLintotheInternetbrowserofa computerthatisonthesamenetworkasthemiralinkunits: Loginasuseradminwiththedefaultpasswordmiralink. WaituntiltheserverisdonewritingtotheMiraLinksourceunitandtheIntellibuffer isempty(0 MB)beforeproceeding.Becausemostoperatingsystemscachedatapriortowritingittodisk,itis a good idea to reboot your server after the initial synchronization and prior to shipping the destinationunit,toensurethattheserverhaswrittenallpartitioninformationtothedisk. NOTE Intheuserinterface Status tab,youcanseehowmuchdataisinthe Intellibuffer andthetransferratebetweenthesourceanddestination.usethe Refreshbuttononyourbrowsertoupdatethestatistics. 2.6.ConfigureUnitsforDeployment Oncetheinitialsynchronizationhasbeencompleted,youwillneedtoconfiguretheIPsettingsof thesourceanddestinationunitbeforeyoutransportthedestinationunittotheremotesite. Notethatinmostenvironments,youwillneedtobeawareoftwoIPaddressesforeachMiraLink unit. EachunitwillhaveanIPaddressontheprivatenetwork. Eachunitwillalsohavean externallyvisibleipaddress,whichistypicallyanaddressonthefirewallorothernatdevice. WhenconfiguringtheaddressthataMiraLinkunitusestoconnecttoitspeer,remembertousethe IPaddressthattheunitsees,whichisnotnecessarilytheprivateIPaddressofthepeer. 10

17 ConfiguretheSourceUnit snetworksettings 1. Logintotheuserinterfaceforthesourceunit(defaultIPaddressis ). 2. ChangethePeerIPAddressintheSettingstabtotheIPaddressthatthesourceunitwill usetoconnecttothedestinationunitonceitisattheremotesite.notethatafteryou make this change, the source unit will no longer be able to transfer data to the destinationunit,anditwillbeginstoringdataintheintellibuffer. 3. ChangetheIPAddressintheNetworktabtotheIPaddressthatyouhaveassignedto thesourceunitonyourproductionnetworkattheprimarysite.notethatafteryousave thissetting,youwillnotbeabletoaccesstheuserinterfaceagainuntilyou have connectedthesourceunittoyourproductionnetwork. 4. Connectthesourceunit snetworkinterfacetoyourproductionnetwork. ConfiguretheDestinationUnit sipsettings 1. Logintotheuserinterfaceforthedestinationunit(defaultIPaddressis ). 2. ChangethePeerIPAddressintheSettingstabtotheIPaddressthatthedestinationunit willusetoconnecttothesourceunitfromtheremotesite. 3. ChangetheIPAddressofthedestinationunitintheNetworktabtotheIPaddressthat youhaveassignedtoyourdestinationunitattheremotesite. 4. ChangetheIPaddressofthesystemthatyouareusingtoconnecttotheuserinterface sothatitisonthesamenetworkasthedestinationunit.youmustdothisinorderto connecttotheuserinterface. 5. PoweroffyourdestinationunitusingtheShutdownlinkintheAdministrationtab. PleaseseeChapter3fordetailedinstructionontheuserinterface DeploytoRemoteSite Youarenowreadytotransportthedestinationunittotheremotesite. Usetheoriginal packagingmaterialstoprotectthedestinationunitintransit. Whilethedestinationunitistraveling,datathatiswrittentothesourceunitbytheserver willbestoredinthesourceunit sintellibuffer.whenthedestinationunitcomesonline, thesourceunitwillsendthedata.(werefertothisasdrainingtheintellibuffer.) Whenthedestinationunitarrivesattheremotesite,removeitfromthepackaging,installit inaserverrackifappropriate,connectittothenetwork,poweriton,anditwillbegin receivingdatafromthesourceunit. Thedestinationunitisaread onlysysteminordertoensurethatthedataonthedestination isidenticaltothedataonthesourceunit.forthisreason,youshouldnotconnectaserver tothedestinationunitatthistime.refertothedisasterrecoveryprocedureslaterinthis documentforinformationonconvertingthedestinationunittoasourceunitandattaching theserver. 11

18 2.7.AdditionalRecommendations Werecommendtakingthefollowingstepsinadditiontothosedescribedabove. ChangetheAdministrativePassword Passwordcontrolshouldalreadybepartofyoursecurityplan.Werecommendthatoneof thefirstthingsyoudoischangethedefaultpasswordonyourmiralinkunits.youshould changethepasswordonbothunits.youmayuseadifferentpasswordforthesourceand destination. Encryption InformationtransmittedbetweenMiraLinkunitsisnotencrypted.Itisrecommendedthat the MiraLink units communicate over a secure, private network segment or a Virtual PrivateNetwork(VPN). Firewall Afirewallorport filteringrouterplacedinfrontofthemiralinkunitsatbothsitescan restricttraffictoonlythoseportsneededbythemiralinkunits(port80,443,and248by default),andcanpreventunauthorizedsystemsfromconnectingtothemiralinkunits. PageFile/SystemSwap WhentheMiraLinkunitsareusedaspartofasystemmirror,itisstronglyadvisedthatcare istakenintheselectionofwhatisincluded.ifthepagefile/systemswaparepartofthe mirror,significantnetworktrafficwillbegenerated.forbestperformance,thepagingfile shouldbeplacedonadifferentphysicalharddiskdrive. 12

19 Chapter3:MiraLinkUserInterfaceandConfiguration Figure3 AllMiraLinkconfigurationchangesaredonethroughthegraphicaluserinterfaceoneachunit. YouwillneedtobeabletoaccesstheuserinterfaceonbothMiraLinkunitsinordertoconfigure themforyourspecificneeds. Theuserinterfaceisorganizedintotenfunctionalareas,denotedbythetabsattheleftoftheuser interface(seefigure3).eachofthetabswillbecoveredindetailinthefollowingsections. 13

20 3.1.Login TologintotheMiraLinkuserinterface,entertheIPAddressoftheunityouwishtoconfigure (e.g )inyourbrowser,andyouaregreetedwiththeloginpage(seefigure3.1).thisis whereyouentertheusername(default:admin)andpassword(default:miralink)andclickonthe Loginbutton. Figure3.1 SecureLogin TologintoyourMiraLinkunitsusingSSLencryption,youcanclickonthe SecureLogin tab.youmayseeawarninginregardstothesslcertificate.thisisexpected,becausethe certificatewasself generatedandself signedonthemiralinkunit,andisnotsignedbya recognizedcertificateauthority. Goaheadandclick OK inresponsetoanycertificate relatedwarnings. 14

21 3.2.Status TheStatustabprovidesusefulinformationformonitoringyourMiraLinkunits(seefigure3.2). Figure3.2 Intellibuffer TheIntellibufferisdesignedtoallownetworkfaulttolerance.Dataisqueuedinthesource unit sintellibufferuntilitcanbesenttothedestinationunit.becauseofthis,nodataislost duringanetworkoutagebetweenthesourceanddestinationunits.whentheintellibufferis empty, the mirror between the source and destination is perfect. Intellibuffer status informationisdisplayedonthesourceunitonly. ThePercentFullandUsedstatisticsshowtheamountofdatacurrentlyintheIntellibuffer. TheStatuswillindicateoneofthefollowingthreestates: OK Intellibufferisinnormalmode RESYNC Thesourceanddestinationunitsarecurrentlyresynchronizing. 15

22 COMPACT WhentheIntellibufferexceeds80%capacity,itwillgointoCompact Mode.Seechapter4Monitoring,forinformationoncompactmode. TransferRate TheCurrenttransferrateprovidesasnapshotofthenumberofKilobytespersecondbeing sent to the destination, while the Average transfer rate provides an average since the beginningofthecurrentdatatransfer.whenthe Current transferratedropstozero,the Averagetransferrateisreset.YoumayalsoseeatransferrateofzerowhentheIntellibuffer isdrainingtothedestinationfasterthantheserveriswritingtodisk. Resync When a resynchronization has been requested by the administrator, the progress is displayedaspercentcomplete. PeerStatus The Peer Status reflects the current state of the connection between the source and destinationunits.thestatusismeaningfulonlywhenthereisdataintheintellibuffer the unitsdonotmaintainanetworkconnectionwhenthereisnodatatosend. DiskStatus TheDiskStatusreportsthehealthoftheunitsdiskdrives.Ifadiskappearstobefailingor hasfailedthestatuswillchangeto NotOK. 16

23 3.3.Settings The Settings tabisusedtochangeconfigurationsettingsonthemiralinkunittowhichyour browserisconnected(seefigure3 3).Thesesettingsdonotmodifytheconfigurationofthepeer MiraLinkunit. Figure3.3 Device ThesearethesettingsfortheMiraLinkunitthatyouarecurrentlyloggedinto. Serial:Serialnumberassetatthefactory. Hostname: The hostname field allows you to label the unit in a way that is meaningfultoyou.itisnotusedforanyotherfunction. MaxTransferRate:Configurethemaximumtransferrateinkbits/second.The defaultsettingof 0 allowsthemiralinkunitstouseallthebandwidththeyneed. Ifyousetittoapositiveinteger(e.g.1500for1.5Mbits/second),itwilllimitthe bandwidthusedtotransferdatabetweenthesourceanddestinationtothatlevel. Thisisfrequentlyreferredtoasbandwidththrottling. SCSIID:ConfigurestheidnumberthattheMiraLinkunitpresentstoyourserver's scsidevice. 17

24 3.4.Network The Network tabisusedtoconfigurethenetworksettingsofthemiralinkunit thatyou are currentlyloggedinto(seefigure3.4). Figure3.4 WARNING Be very careful when changing network related settings. Changing them incorrectlycouldcauseyoutoloseaccesstothedevice.itisalsoagoodideatodocument thenewnetworksettings. Interface1 ThissectioniswhereyouconfiguretheIPaddressandnetmaskthatyouhaveassignedto yourmiralinkunit. NOTE IfyouchangetheIPAddress,youmayhavetochangetheIP Addressonyourserverorlaptopbeforeyoucanreconnecttotheuser interfaceatthenewlyconfiguredaddress. Routing ContainsthedefaultgatewayfortheMiraLinkdevice. Peer ThisiswhereyouchangetheIPaddressthatthecurrentunitusestoconnecttoitspeer. 18

25 Forexample,ifyouareloggedintothesourceunit,thisfieldshouldcontaintheIPaddress ofthedestinationunit.changingthisfieldtellsthemiralinkdevicethatyouarecurrently loggedintowheretofinditspeer;itdoesnotchangetheconfigurationonthepeerunit. Note that this should be the externally visible IP address of the peer, which is not necessarilytheipaddressconfiguredonthepeerunit.forexample,ifyouhaveafirewall performingaddresstranslation,thepeeraddresswillbetheipaddressthatyousetupon thefirewalltoforwardport248traffictothepeerunit. 3.5.SNMP TheSNMPtabisusedtoconfiguretheSNMPsettingsoftheMiraLinkunitthatyouarecurrently loggedinto(seefigure3.5). Thefollowingvaluescanbechangedfromthedefaults: SystemName SystemLocation SystemContact CommunityString Onceyouhaveenteredyourcustomconfigurationvalues,clickonthe Save buttontosavethe changes.thesechangeswilltakeaffectimmediately. Figure3.5 19

26 3.6.Role TheRoletaballowstheMiraLinkunit sroletobechangedfromsourcetodestinationorviceversa (seefigure3.6).thisisusuallydoneduringdisasterrecoverysituationsandiscoveredinmore detailinchapter5:disasterrecovery. Role ChangingroleswilldiscardalldatacurrentlyintheIntellibuffer.Acompleteremirroris requiredafterdiscardingtheintellibufferinordertoensuredataconsistency.duringa resynchronization,youarenotabletochangeroles.tochangeroles,clickoneitherthe sourceordestinationradiobutton,checktheconfirmationbox,andthenclickonthesave buttontosaveyourchanges. Figure3.6 WARNINGChangingrolescompletelychangesthebehavioroftheMiraLinkdevice.For example,ifyouchangeaunitfromsourcetodestination,youwillnolongerbeabletowrite datatothemiralinkunitfromyourserver. 20

27 3.7.Intellibuffer TheIntellibuffer isthepatentedtechnologythatallowsthemiralinksolutiontoworkoverlow bandwidthnetworks.whenthedatachangerate(thespeedatwhichdataiswrittentothesource unit by the server) exceeds the available bandwidth, data is buffered, or stored, in the Intellibufferbeforebeingsenttothedestination(seefigure3.7). DataTransfer ThissettingenablesordisablestransferofdatatothedestinationMiralinkunit.Ifyou disabledatatransfer,datawillcontinuetoqueueintheintellibuffer,butitwillnotbesent tothedestinationuntilyoure enabledatatransfer. Figure3.7 Discard ThissettingallowsyoutodiscardanydatathathasbeenqueuedupintheIntellibuffer.In ordertodiscardthedataintheintellibuffer,clickintheconfirmationboxnexttodiscard IntellibufferandthenclickontheDiscardIntellibufferbutton. ThedatathatwasqueuedintheIntellibufferwillnotbesenttothedestination.Thismeans thatthedestinationandthesourcewillnolongerbesynchronized. Afterdiscardingthe Intellibuffer,acompleteresynchronizationwiththedestinationunitwillberequiredin ordertoachievedataconsistency. 21

28 3.8.Resync Resynchronizationisaprocessbywhichallofthedatastoredonthesourceunitiscopiedtothe destination.thisactionshouldbeperformedonlywhenyoususpectadiscrepancybetweenthe sourceanddestination,suchasafterdiscardingtheintellibufferorafterarolechange. Toinitiatearesynchronization,choose StartResync andconfirmbyclickingthe StartResync button(seefigure3.8).oncearesynchasbeenstarted,youcanusethisformtocanceltheresync. Statusinformationspecifictotheresyncphase(suchaspercentcomplete)canbeviewedunderthe Statustab. ATTENTION!Theamountoftimethatittakesfortheresynctocompletedependsonthe sizeofyourmiralinkdatadriveandthespeedofyournetwork. Keepinmindthata resynccopiestheentiredisk,notjustthepartofthediskyouareusing.so,ifyouhavea 300GBdatadriveandyouareusingonlya2GBpartitiononthatdrive,itwillstillcopyall 300GBofdataduringaresyncoperation. Figure3.8 Todeterminetheamountoftimerequiredforaresynchronization,convertthesizeoftheMiraLink datadrivetokilobytes(thereare8bitsinabyte,and1024kilobitsinamegabit)anddivideitby theaveragetransferrateduringadatatransfer.thiswillgiveyouthenumberofsecondsrequired (thereare3,600secondsinanhour,and86,400secondsinaday). Duringtheresynchronization,youmayusetheservertowritetotheMiraLinksourceunitasyou normallywould. DatawillbequeuedintheIntellibufferandsenttothedestinationafterthe 22

29 resynccompletes. Beawarethatyoursourceanddestinationwillnotbeperfectlysynchronized untiltheresynchascompletedandtheintellibufferhascompletelydrained. WARNING!CancelingaresyncwillcauseyourMiraLinkunitstobeoutofsyncandyour remotediskmaynotbeusableuntilyoucompleteanotherresync. 3.9.ChangeAdministratorPassword Here,youcanchangethepasswordfortheuserinterfaceorremotelyshutdownorrebootyour MiraLinkunits. Figure3.9 ChangePassword Thereisonlyoneuser(admin)definedfortheWebinterface.Thisusernameprovidesfull authorizationtomakechangestothesystemsconfiguration.thedefaultpasswordforthis usernameis miralink.forsecurityreasons,itisimportantthatthedefaultpasswordbe changedonbothunitsassoonaspossible. Inordertochangethepassword,clickonthe ChangePassword linkatthetopofthe administrationpage.youwillneedtoenterthecurrentpasswordandthentypeyournew passwordinthetwoboxesbelow.tosubmitthenewpassword,clickonthesavebutton. (seefigure3.9) 23

30 NOTE Thechangepassworddialogchangesthepasswordonlyonthe MiraLinkunitthatyouarecurrentlyconnectedto Shutdown/Reboot Shutdown/Reboot Inordertoavoiddatacorruption,alwaysusetheMiraLinkuserinterfaceforshuttingdown orrebootingyourmiralinkunits.ifyouneedtoshutdownorrebootyourmiralinkunits, clickontheshutdown/rebootlinkatthetopoftheadministrationtab.onceyouenterthe Shutdown/Rebootscreen,clickoneitherbuttontorebootorshutdownyourMiraLinkunit (seefigure3.10). Donotclickthe Refresh buttoninyourbrowserafteryouinitiateashutdownorreboot. Thiswillre submityourrequestandre issuetheshutdownorrebootcommand.instead, clickononeofthetabsintheuserinterfacetoloadtheappropriatepage. ATTENTION!UsersoftheMiraLink400canhitthepowerbuttononthefrontoftheunit andagracefulsoftwareshutdownwillbeinitiated.ifthepowerbuttonishelddownfor more than 6 seconds the unit will shutdown immediately. However, this will cause corruptionofuserdata. Figure Logout Thistabisusedtologoutoftheuserinterface.OnceyouclickontheLogoutlink,youwillbe returnedtotheloginpage,andpromptedforausernameandpassword. 24

31 Chapter4:Monitoring AfteryouhaveinstalledandconfiguredyourMiraLinkunits,youwillwanttomonitorthemto makesurethateverythingisworkingproperly. 4.1.WhattoLookFor Inordertoensurethatyourdataisavailableintheeventofadisaster,youshouldmonitoryour MiraLinksourceunittoverifythatyourbandwidthissufficienttohandleyourdatachangerate. ThedatachangerateistherateatwhichtheserveriswritingdatatotheMiraLinksourceunit. Thedatatransferrateistherateatwhichthesourceunitistransferringdatatothedestinationunit. Whenthedatachangerateexceedsthedatatransferrate,dataisqueuedintheIntellibufferand thensenttothedestinationunit. Inatypicalenvironment,theIntellibufferwillgrowduringpeakusage,andthendraintoempty during periods of inactivity. The situation you want to watch out for is one in which the Intellibufferisconstantlygrowing,oroneinwhichthetimeittakestheIntellibufferto catchup afterabusyworkdayexceedsyourorganization stolerancelevels. IfyoumonitortheIntellibufferandnoticethatitisgrowingovertimeandfailingtoemptyduring periodsofinactivity,itislikelythatyoudonothaveenoughnetworkbandwidthtosupportthe levelofdiskactivity.increasingtheamountofbandwidthavailabletothemiralinkdevicesmay enabletheintellibuffertodrain. IfyourIntellibuffergrowstomorethan80%full,theIntellibuffergoesintoCompactMode.This isreflectedintheintellibuffer sectionofthestatus pageintheuserinterface.inthismode,the dataisstoredinamorecompactformthanduringnormaloperation,sothatmoredatacanbeheld inasmallerspaceintheintellibuffer.becauseofthecompromisesrequiredforstoringthedata usinglessdiskspace,theoriginalwriteorderofthedatamaynotbepreserved,whichmeansthat thesourceanddestinationunitwillnotbeperfectlysynchronizeduntiltheintellibufferhasfully drained.ifyouhaveabandwidthavailabilityissue,youshouldcatchitwellbeforetheintellibuffer reaches80%full!theintellibufferwillstayincompactmodeuntilitdropsto74%. IftheIntellibufferreaches100%full,itcannotstoreanymoredata,andthedataonthesourceand destinationwillbeoutofsync.acompleteresynchronizationwiththedestinationunitisrequired inordertoachievedataconsistency.thisisstartedautomaticallybytheunitonceitreaches100%. 25

32 4.2.MonitoringthroughtheUserInterface UsetheMiraLinkuserinterface sstatustabtoviewinformationabouttheintellibufferandcurrent bandwidthusage.thestatustabisdiscussedindetailinchapter MonitoringwithSNMP The Simple Network Management Protocol (SNMP) is an Internet standard for monitoring network attached devices. There are many different software SNMP agents available. This documentwillexplainwhatthemiralinkmibiscapableof,withoutdelvingtoofarintothe technicaldetailsofsnmporsnmpsoftware.refertothedocumentationprovidedwithyour SNMPsoftwareforspecificproceduralinformationonitsuse.Seesection3.5forinformationon configuringsomebasicsnmpvaluesonyourmiralinkunits. MiraLinkMIBContents TheMiraLinkMIBisusedtogetinformationregardingtheconfigurationandcurrent statusofyourmiralinkunits.themiralinkmibisread onlyanddoesnotallowyouto makeconfigurationchangesviasnmp. Thefollowingtableliststhedefinedobjects,theOID s,thereturnvalue,andadescription ofeach. ObjectName OID ReturnValue Local (1) Remote(2) BufferStatus Normal (1) Compact (2) Resync(3) EnqEnabled Off On(2) (1) DeqEnabled Off On(2) (1) Read/Write Status Readonly (1) Readwrite(2) Role SerialNumber PeerIPAddress SCSIID 26 Description The identification of this platform as either a localorremotedevice.thisisalsothesameas SourceandDestination. TheMiraLinkserialnumber Thepeer'sIPAddress Thisvalueisequaltotheunit'sSCSIID Thisobjectcontainsthestatusofthebuffer.If the buffer is less than 80% full, then the unit operatesinnormalmode.ifthebufferismore than80%full,thentheunitoperatesincompact mode.inthismodethelbn ofeachblockis storedinthebuffer This object shows whether it is configured to duplicatediskwritestothebufferinpreparation totransferittothedestinationunit.thisvalue should be on for a source unit, and off for a destinationunit. This object shows whether it is configured to transmit buffered data to the destination unit. Thisvalueshouldbeonforasourceunitandoff foradestinationunit. Thisobjectshowsthecurrentdatadiskaccess fortheclientserverattachedtothemiralinkunit. Thisvalueshouldbereadwriteforthesource, andread onlyforthedestinationunit.

33 BlockSize MaxCQBBlocks Current Blocks Current CQB BlocksPercent Instantaneous Throughput Remaining Disk Blks MaxDiskBlk PercentResync Thisobjecthasthenumberofbytesthatarein eachblockinthemainmemorycache. Theobjecthasthesizeofthebuffer(inblocks) asit'svalue Thisobjecthasthenumberofblocksthatare currentlyinthecircularbuffer.ifthereisdatato betransmittedtothedestination,it'svaluewill begreaterthanzero.thisvalueisonlyvalidon thesourceunit. Thisobjectcontainsthepercentagefullofthe bufferonthesourceunit.thisvalueisonlyvalid onthesourceunit. This object contains network throughput information for the Miralink unit. The value is Bytespersecond.Thisvalueisonlyvalidonthe sourcemachine. This object will be non zero if a resync is occurring.it'svalueindicatesthenumberofdisk blocks yet to be sent. When it reaches MaxDiskBlk,theresynchronizationisdone.This valueisonlyvalidonthesourcemachine. Thisobject'svalueisthenumberofdiskblocks inthemirrorvolume. This object will be non zero if a resync is occurring.itsvalueisthepercentcomplete.this valueisonlyvalidonthesourceunit CQB UsingtheMiraLinkMIB TheMiraLinkMIBisavailableintheSNMPdirectoryofthedocumentationCDprovided withyourmiralinkunits(thesamecdthatcontainsthismanual).youwillneedtocopy the file MIRALINK MIB.txt to the proper location on the system you use for SNMP monitoring.refertoyoursnmpsoftware sdocumentationfordetailsonhowtoinstallthe MIBandhowtoaccessitsvaluesonceyouhaveinstalledit. 27

34 Chapter5:DisasterRecovery ConceptualOverview DisasterRecovery(DR)ininformationtechnologyreferstothestepstakentorestoreoperations afteradisaster,suchasafire,flood,orhardwarefailure.companieswithoutadisasterrecovery planinplacerarelysurviveaftercriticaldataislostduetoadisaster.inorderforyourorganization toeffectivelyprotectitsresourcesfrompotentialdisaster,itisstronglyrecommendedthatyouhave a business continuity plan with detailed disaster recovery procedures in place before disaster strikes. This manual should not be considered a disaster recovery plan; it contains only instructionsfortheoperationofyourmiralinkunits. ThischapterdiscussestheconceptualinformationyouneedtouseyourMiraLinkunitsaspartof yourdisasterrecoverysolution.thesubsequentchaptersprovideproceduralinformationrelatedto disasterrecoveryusingmiralinkunits.itisrecommendedthatyoureadthroughthenextfew chapterswellinadvanceofanactualdisasterandincorporatethemintoyourdisasterrecovery plan. 5.1.DisasterRecoverySequenceofEvents Atthemomentthatyourlocalsitebecomesunavailable,thedatastopstransferringtotheremote site.anydatathatisintheintellibufferwillnotbesenttothedestination.theremayalsobedata thatwascachedontheserverthatdidnotgetwrittentotheharddrive(s).thisisanunavoidable consequenceofasuddenlossofpowertotheserverormiralinksourceunit. Wedividedisasterrecoveryintotwophases:DataRecoveryandRestoringLocalOperations. DataRecovery Immediatelyfollowingthedisaster,thefirststeptowardrestoringoperationsistogain accesstothemirroreddataatyourremotesite.inthisphase,youwillusethedataonthe MiraLinkdestinationunittogetyourservicesupandrunning. RestoringLocalOperations Restoring local operations refers to bringing operations back to the primary site, as opposedtorunningoffofthedataatyourremotesite. Whenyouarereadytorestore operationsattheprimarysite,youwillmirrorthedatafromtheunitattheremotesiteback totheprimaryunit(orareplacement),sothatyoucanresumeoperationslocally. 28

35 5.2.TypesofDisasters YouprobablypurchasedtheMiraLinkunitstoprotectyourdataintheeventofamajor disasterthatdestroysyourdatacenterandalloftheequipmenttherein.perhapsyouneeded the MiraLink solution to bring you into compliance with your industry s regulations. Fortunately,theprimaryfunctionoftheMiraLinkunitsistoprovideaperfectremote mirrortomeetyourdisasterrecoveryneeds. Thischapterandthenextdescribetheproceduresforconnectingaservertothedestination unitandresumingoperationsusingthemirroreddata. Thisisappropriateinascenario where,forexample,yourprimarysiteandalloftheequipmenthasbeendamagedbya floodorfire. Remember,though,thattherearemanysituationsthatarenotmajordisastersinwhichyou mayfindthemirroreddataonthemiralinkunitsuseful.forexample,ifyouaremirroring thesystempartitionfromyourserverontothemiralinksourceunit,andyourserver s internalharddrivegoesbad,youcanbootoffofthemiralinksourceunitandresume operationsimmediately. Ifyouareusingitastheprimarydatadriveforaproductionapplication,andtheserver crashes,youcanconnectthesourcemiralinkunittoaspareserverandresumeoperations. Readthroughthischapterandthenext,andunderstandtheconceptsandproceduressothat you can incorporate the MiraLink solution into your organization s disaster recovery procedures,takingintoaccountthatnotalldisastersaremajor. 29

36 Chapter6:DisasterRecovery DataRecovery ThischapterfocusesonhowtorecoverifyourprimaryserverandsourceMiraLinkunitbecome inaccessibleduetoadisastersituation.wewillbegoingintodetailsonhowtorecoverwhenusing yourmiralinkasasystemmirror,datamirror,oraprimarystorage.theseconfigurationtypesare describedinmoredetailinchapter1. Yourdestinationunitattheremotesiteisoperatinginread only,ordestination,mode.inorderfor therecoveryservertouseitasaharddrive,youmustconvertittoasourceunitandattachitvia SCSIcabletotheserver. When you change the role of the MiraLink unit, it will begin behaving as a source unit immediately.itwillaccumulatedataintheintellibufferandattempttosendthedatatoitspeer.it willnolongeracceptchangesfromtheoriginalsourceunit. Inordertoavoidconfusionwiththeoriginalsourceunit,wewillrefertothedestinationunitthat hasbeenchangedtoasourceastherecoveryunit,becauseitislocatedatyourdisasterrecovery (remote)site. 6.1.SystemMirror IfyouhaveconfiguredtheMiraLinkunittomirrorthesystemdiskofyourserverandtheprimary sitebecomesunavailable,youshouldtransitionoperationstotheremotesiteandusethesecondary serverastheprimaryserver. NOTEKeepinmindthattheMiraLinkunitisastoragedeviceandcannotbeusedasa server.forrapidrecoveryintheeventofadisaster,itisrecommendedthatidentical hardwarebeusedforboththeprimaryandsecondaryservers. ThissectionwalksyouthroughtheprocessofattachingyourMiraLinkdestinationunittothe recoveryserverandbootingtheserverusingthemiralinkunitasthebootdrive.theprocessfor bootingfromanexternaldrivewillvarygreatlydependingonyouroperatingsystem. Insome cases,youmayneedtouseabootfloppyorrecoverycdintheserver. Refertothetechnical documentationprovidedwithyouroperatingsystemforproceduraldetails. TransferOperationstotheRemoteSite 1. NetworkSettings.Dependingontheconfigurationofyournetwork,youmayneedto makemanualchangestoyoursite sdnsorothernetworksettingsinordertobegin usingtheremoteserverasyourprimaryserver. 30

37 2. ChangeRole.Connecttotheuserinterfaceonthedestinationunit(hereafterreferred toasrecoveryunit),clickontheroletab,andchangetheroletosource. 3. Shutdown.Intheuserinterface,clickontheAdministrationtabandshutdownthe recoveryunit. 4. PhysicalConnection.Ifyourserveriscurrentlypoweredon,youmustshutitdown beforeproceeding.attachoneendoftheprovidedscsicabletotheportlabeledhost SCSIBusonthebackoftherecoveryunit,andtheotherendtotheSCSIportonthe server.(ifyoupurchasedafibrechanneloriscsibridge,attachtherecoveryunitto thebridgeinsteadoftotheserver.) 5. Power On. Power on the recovery unit, and allow 90 seconds for it to boot up completely.powerontherecoveryserver.ifrequiredbyyouroperatingsystem,enter the BIOS management menu for the server s motherboard and/or SCSI card and configureittousethemiralinkunitasitsprimarybootdevice. 6. RebuildMirror.Ifappropriate,useyouroperatingsystem sdiskmanagementtoolsto mirrorthedatafromtherecoveryunitbacktotheserver sharddrive. 7. Reboot. After the mirror has been rebuilt, you should power down your server, reconfigurethemotherboardorscsibiosifnecessary,andbootoffoftheserver s internaldrive. OncetheserverhasbootedusingtheMiraLinkrecoveryunit,itisreadytobeusedasyour primaryserver.themiralinkwillnowactasasourceunit,storingdataintheintellibuffer untilitcanbesenttoadestinationunit. Duringthetimethatyouareoperatingattheremotesite,dataisbeingchangedonthe recoveryunit.whenyouarereadytorestoreoperationsatthelocalsite,youwillneedto synchronizethedatafromtherecoveryunittothelocalunitorreplacementunit. See Chapter7forproceduraldetails. 6.2.DataMirror IfyouhaveconfiguredtheMiraLinkunitasamirrorofadatapartitionorpartitionsofyourserver andtheprimarysitebecomesunavailable,youcantransitionoperationstotheremotesiteanduse thesecondaryserverastheprimaryserver. TransferOperationstotheRemoteSite 1. NetworkSettings.Dependingontheconfigurationofyournetwork,youmayneedto makemanualchangestoyoursite sdnsorothernetworksettingsinordertobegin usingtheremoteserverasyourprimaryserver. 2. ChangeRole.Connecttotheuserinterfaceonthedestinationunit(hereafterreferred toasrecoveryunit),clickontheroletab,andchangetheroletosource. 31

38 3. Shutdown.Intheuserinterface,clickontheAdministrationtabandshutdownthe recoveryunit. 4. PhysicalConnection.Ifyourserveriscurrentlypoweredon,youmustshutitdown beforeproceeding.attachoneendoftheprovidedscsicabletotheportlabeledhost SCSIBusonthebackoftherecoveryunit,andtheotherendtotheSCSIportonthe server.(ifyoupurchasedafibrechanneloriscsibridge,attachtherecoveryunitto thebridgeinsteadoftotheserver.) 5. Power On. Power on the recovery unit, and allow 90 seconds for it to boot up completely.powerontherecoveryserver. 6. Oncetheserverhasbooted,verifythatitisabletoseeandusetheMiraLinkrecovery unit as a data drive. Depending on your configuration, you may need to update configurationsettingsinyourapplicationstopointthemtothemiralinkdrive. 8. RebuildMirror.Ifappropriate,useyouroperatingsystem sdiskmanagementtoolsto mirrorthedatafromtherecoveryunitbacktotheserver sharddrive. Duringthetimethatyouareoperatingattheremotesite,dataisbeingchangedonthe recoveryunit.whenyouarereadytorestoreoperationsatthelocalsite,youwillneedto synchronizethedatafromtherecoveryunittothelocalunitorreplacementunit. See Chapter7forproceduraldetails. 6.3.PrimaryStorage TheinstructionsfortransferringoperationstotheremotesitewhenyouareusingtheMiraLink unitasprimarystorageareidenticaltotheinstructionsforrecoveringdatafromasystemordata mirror,withtheexceptionoftherebuildmirrorstep,whichcanbeskipped. Pleaserefertotheappropriatesectionaboveforrecoveringyourdata. 32

39 Chapter7:DisasterRecovery RestoringLocalOperations BecausethedataontheMiraLinkrecoveryunitattheremotesitehaschangedwhileyouhavebeen operatingfromtheremotesite,youwillneedtosynchronizeyourmiralinkunitsbeforeoperations canberesumedatthelocalsite. Theprocessforaccomplishingthisissimilartothestepsyoufollowedwheninstallingtheunits initially. WARNING! Itisimperativethatyoufollowtheseproceduresexactly. Failuretodoso mayresultinlossofdata! ThefirstphaseinrestoringlocaloperationsistosynchronizethedatabetweenyourMiraLink units,sothatbothunitshavethenewestdata.iftheoriginalsourceunitisinworkingorder,you willbeusingthatunit,oryouwillhaveareplacementunit.eitherway,wewillrefertothisunitas thereplacementunitforclarity. PreparingthePrimarySite IfyouroriginalserverandMiraLinkunitarefunctional,andyouareusingasystemordata mirror,youmustremovethemirrorontheserverbeforeproceeding.otherwise,whenyou laterrestoreoperationstotheprimarysite,theserverwillimmediatelybeginmirroringold datatothemiralinkunit,andyouwillhavelostthedatathatchangedwhileyouwere operatingfromtheremotesite. 1. Ontheprimaryserver,removethemirrorbetweentheserverandsourceunit. 2. If you are mirroring the system drive, configure the server to boot from the MiraLink source unit. This will prevent the introduction of old data to the MiraLinkunitafteroperationsarerestoredattheprimarysite. 3. Ifyouaremirroringdatadrives,configuretheservertousethedatadrive(s)onthe MiraLinksourceunit,ratherthanitslocaldrive(s).Thiswillenableyoutousethe up to datedata,andpreventtheintroductionofolddatatothemiralinkunitafter operationsarerestoredattheprimarysite. 4. Shutdowntheserver. 5. ConnecttotheuserinterfaceontheMiraLinkunitandchangetheroleoftheunitto destination. 6. ShutdowntheMiraLinkunit,henceforthreferredtoasthereplacementunit. 33

40 RestoringtheDatatotheReplacementMiraLinkUnit Transportthereplacementunittotheremotesite.Theunitsneedtobeinthesamelocation duringtheresynchronization.whenyouhavebothunitsatthesamesite,followthesesteps tomirrorthedatafromtherecoveryunitontothereplacementunit: 1. Connectthereplacementunittothenetworkattheremotesiteandpoweriton.It shouldnotbescsi attachedtoaserveratthistime. 2. You will likelyneed to use theuserinterfacetochangethe IP address of the replacementunittoanaddressthatisappropriatefortheremotesite snetwork. 3. Logintotherecoveryunit suserinterfaceandupdatethe PeerIPaddress inthe NetworktabtomatchtheIPaddressofthereplacementunit. 4. Intheuserinterfaceoftherecoveryunit,initiatearesynchronization. 5. Wait for the resynchronization to complete and let the Intellibuffer drain completely. OncetheresynchronizationhascompletedandtheIntellibufferhasdrainedcompletely,the recovery unit, which is still attached to the active server at the remote site, and the replacementunitaresynchronized. Thereplacementunitisreadytoberelocatedtothe primarysite. 1. Connecttotheuserinterfaceonthereplacementunittoshutdownthereplacement unit. 2. Transportthereplacementunittotheprimarysite. 3. Attheprimarysite,poweronthereplacementunit.Donotattachittotheserverat thistime.itisstillindestinationmode. 4. Youwilllikelyneedtoconnecttotheuserinterfaceonthereplacementunitto changeitsnetworksettingsbackitsoriginalsettings(theappropriatesettingsforthe networkatyourprimarysite). 5. Connecttotheuserinterfaceontherecoveryunitattheremotesiteandchangethe PeerIPaddresstothecurrentaddressofthereplacementunit.Rememberthatthis shouldbetheexternallyvisibleipaddressofthereplacementunit,whichmaynot bethesameasitsprivateipaddress. Whilethereplacementunitwasintransit,datawrittentotherecoveryunitwasqueuedin theintellibufferontherecoveryunit.youmustwaitfortheintellibufferontherecovery unittodraincompletelybeforetheunitsareonceagainsynchronized. StopOperationsatRemoteSite Restoringoperationsattheprimarysitewillrequirethatbothserversbeshutdown,soyou willneedtoscheduleamaintenancewindowtoperformtheoperation. Althoughitis possibletocompletethemaintenanceinamatterofminutes,youshouldallowseveral hourssothatyoucancarefullyverifythatyouhavefollowedallstepscorrectlyandhave 34

41 notlostanydata. IftheIntellibufferontherecoveryunithasmuchdatainit,youmust allowextratimefortheintellibuffertodrainfully(step2below). 1. Attheremotesite,shutdowntheserver.Theserverwillremainshutdownforthe durationoftheseprocedures. 2. MonitortheIntellibufferontherecoveryunitattheremotesite. Waituntilitis completelyempty(0mb)toensurethatthedataontherecoveryandreplacement unitaresynchronized. 3. When theintellibufferonthe recovery unitis empty,use the user interface to changetheroleoftherecoveryunittodestination. 4. Usetheuserinterfacetoshutdowntherecoveryunit. Leavetherecoveryunit poweredoffuntilyouhavecompletedtherestorationofoperationsatyourprimary site.thiswillensurethatyouhaveacurrentcopyofthedatafromwhichyoucan recoverifanythinggoeswrongwhileyouarefollowingtheseprocedures. 5. DisconnecttheSCSIcablebetweentherecoveryserverattheremotesiteandthe recoveryunit. RestoreOperationsatPrimarySite 1. Connecttotheuserinterfaceonthereplacementunitattheprimarysiteandchangethe roletosource. 2. Usetheuserinterfacetoshutdownthereplacementunit. 3. If your primary server is currently powered on, you must shut it down before proceeding.attachoneendoftheprovidedscsicabletotheportlabeledhostscsi Bus onthebackofthereplacementunit,andtheotherendtothescsiportonthe primary server. (If you purchased a Fibre Channel or iscsi bridge, attach the replacementunittothebridgeinsteadoftotheserver.) 4. Poweronthereplacementunit.Waitatleast90secondstoensurethatthereplacement unitisfullyoperational. 5. Powerontheprimaryserver.Ifyouwereusingasystemmirrorinitially,becertainthat itbootsfromthereplacementunit,notfromitsinternaldrive. Ifitbootsfromits internaldrive,itmayoverwritethedataonthereplacementunit,andthenyoumust returntheunittotheremotesiteandperformthestepstosynchronizetheunitsagain. 6. Ifyouwereusingadatamirrorinitially,becertainthattheserverisusingthedataon thereplacementunit,notitsinternaldrive.ifitisusingthedataonitsinternaldrive, andthemirrortothemiralinkunithasnotbeenbroken,itwilloverwritethedataon thereplacementunit,andyouwillhavetoreturntheunittotheremotesiteandperform thestepstosynchronizetheunitsagain. RestoringLocalMirrors Ifyouwereusingthesystemordatamirrorconfigurationtype,youshouldfollowthese stepstore createyourmirror: 35

42 1. Ifyouwereusingasystemmirror,youshouldre createthemirrorsothatthesystem driveismirroredfromthereplacementunittotheprimaryserver sdrive.becareful! Mirroringinthewrongdirectionwillcausethedatathatchangedwhileyou were operatingfromtheremotesitetobelost. 2. Ifyouwereusingadatamirrorinitially,re createthemirrorsothatthedataismirrored fromthereplacementunittotheprimaryserver sdatadrive.becareful!mirroringin thewrongdirectionwillcausethedatathatchangedwhileyouwereoperatingfromthe remotesitetobelost. 3. Inthecaseofasystemmirror,waitforthemirrortoberebuilt,andreconfigurethe servertobootoffofitsmaindrive.reboottheserveroffofthemaindrive. RestoringMiraLinkdatatransfer Your primary site is now fully operational. Depending on the configuration of your network,youmayneedtomakemanualchangestoyoursite sdnsorothernetwork settingsinordertobeginusingtheprimaryserveragain. Onceyouarecertainthatyouhavefollowedtheproceduressuccessfully,youarereadyto bringupthedestinationunitattheremotesiteandresumemirroringbetweenthemiralink units. Poweronthedestination(recovery)unit.Itshouldimmediatelybeginreceivingdatafrom thesource(replacement)unitattheprimarysite. Congratulations!Youhavenowrestoredoperationsastheyexistedpriortothedisaster! QuickandDirtyPath:SomeDataLoss Someorganizationshaveahighertolerancefordatalossandcanaffordtobelessrigorous whentheyrestoreoperationsatthelocalsiteafteradisaster. Ifyoudonotneedthedatathatwaswrittentotherecoveryunitattheremotesite,andyou meetthefollowingcriteria,youcanskiptheinstructionsaboveandfollowthe quickand dirty pathtorestoringlocaloperations: YouroriginalMiraLinksourceunitisstillconfiguredasasourceunit(i.e.itsrole hasnotbeenchangedtodestination YouroriginalMiraLinksourceunitisstillfunctional You donotneed thedatathatwaswrittentotherecoveryunitwhileyouwere operatingfromtheremotesite Youmaybeginusingthesourceunitatthelocalsiteimmediately.Becausetheremoteunit isnolongeraperfectmirrorofthesourceunit,youmustfollowthesestepstorestorethe mirror.notethatanydatathatwaswrittentotherecoveryunitwhileitwasinsourcemode willbediscarded. 1. Logintouserinterfaceontherecoveryunitandchangetheroletodestination. 2. Transportthedestination(recovery)unittotheprimarysite. 36

43 3. Connectthedestinationunittothenetworkattheprimarysiteandpoweriton. Youmayneedtochangeitsnetworksettingstosettingsappropriateforthe networkattheprimarysite.itisrecommendedthatyouconnectthesourceand destinationtoan isolatednetworkduringthe resynchronization,inorder to reducethetimerequiredfortheresyncandtopreventtheunitsfromusingallof thebandwidthonyourinternalnetwork. 4. Logintotheuserinterfaceonthesourceunit,updatethePeerIPaddress to pointtothedestinationunitifnecessary,andinitiateafullresynchronization. 5. AllowtheresynchronizationtocompleteandtheIntellibuffertodrainfully. Afteryoufollowthesesteps,thetwounitswillbeinsync. Reconfigurethe networksettingsfortheremotesite,shutdownthedestinationunit,transportit totheremotesite,installitattheremotesite,poweriton,anditwillbegin receivingdatafromthesourceunit. 37

44 7.1.DriveFailureDetectionandProcedures TheMiraLinkunitscandetectandreportdiskdrivesthatarefailingorhavefailed.Monitoringby meansofsnmpisalsoavailable.ifyoursystemreportsafaileddrivepleasecontactmiralink's technicalsupport. TheMiraLink1000usesaninternalSATARaidControllertocontroltheraid5array.Whenadisk hasfailedtheraidcontrollerwillgeneratealoudbeeptoalertyouofadiskfailure. RestoreaBrokenRaidArrayonaMiraLink Reboottheunit. 2. HitControl+MtoentertheRaidController. 3. Choose Configure andhitenter. 4. SelectView/AddConfigurationandhitenter. 5. Locatethefaileddrive. 6. ExittheRaidControllerandshutdownthesystem. 7. Replacethefaileddrive. 38