markingexchange2007

WhitePaperEMCSolutionsGroupAbstractTheEMCProtectionforMicrosoftExchangeServer2010solutionisanExchangebusinesscontinuitysolutiondesignedforenterpriseswithtwoormoreactivedatacentersatdifferentgeographiclocations.
Thesolutionoffershighavailabilityateverylocationandnear-instantaneousrecoveryfromadisasteratanylocation.
ThesolutionleveragesEMCVNX5700storagewiththeVNXTotalProtectionPack(EMCRecoverPoint,EMCReplicationManager,andEMCDataProtectionAdvisor)andVMwarevSphere5withvCenterSiteRecoveryManager(SRM)5.
December2011EMCPROTECTIONFORMICROSOFTEXCHANGESERVER2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFullyautomatedrecoveryforMicrosoftExchangeServer2010UnlimitedsnapshotstoprotectfromlogicaldatabasecorruptionIn-depthmonitoringandreportingEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager2Copyright2011EMCCorporation.
AllRightsReserved.
EMCbelievestheinformationinthispublicationisaccurateasofitspublicationdate.
Theinformationissubjecttochangewithoutnotice.
Theinformationinthispublicationisprovided"asis.
"EMCCorporationmakesnorepresentationsorwarrantiesofanykindwithrespecttotheinformationinthispublication,andspecificallydisclaimsimpliedwarrantiesofmerchantabilityorfitnessforaparticularpurpose.
Use,copying,anddistributionofanyEMCsoftwaredescribedinthispublicationrequiresanapplicablesoftwarelicense.
Forthemostup-to-datelistingofEMCproductnames,seeEMCCorporationTrademarksonEMC.
com.
VMware,ESX,VMwarevCenter,andVMwarevSphereareregisteredtrademarksortrademarksofVMware,Inc.
intheUnitedStatesand/orotherjurisdictions.
Allothertrademarksusedhereinarethepropertyoftheirrespectiveowners.
PartNumberH88913EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerTableofcontentsExecutivesummary.
6Businesscase.
6Solutionoverview6Introduction.
7Purpose7Scope7Audience7Technologyoverview8Overview.
8EMCVNX5700storagesystem8EMCRecoverPoint.
9RecoverPointappliances(RPA)9RecoverPointsplitter10RecoverPointjournals.
10RecoverPointconsistencygroups10EMCReplicationManager11EMCDataProtectionAdvisor.
12EMCPowerPath/VE13VMwarevSphere.
13VMwarevCenterSiteRecoveryManager.
13EMCRecoverPointStorageReplicationAdapterforVMwarevCenterSRM.
14Overallsolutionarchitectureanddesign.
15Clarificationofterminology15Designattributes15Virtualization16Active/activesiteconfiguration.
16Dataprotection.
17ExchangeServer2010Design.
17Exchangestoragedesign19Buildingblockdesignapproach.
20Mailboxservervirtualmachinebuildingblockdetails.
20Aboutstoragepools.
21VNXstoragepooldesign22vSphereserverdesign.
23Exchangelocalprotection.
25EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager4RecoverPointdesign.
26RecoverPointconsistencygroupdesign26RecoverPointstoragerequirements.
27RecoverPointjournaldesign.
27Considerationswhensizingjournalvolumes28Sizingjournalvolumes.
28ConsistencygrouppolicyconfigurationformanagementbySRM.
30RecoverPointgroupsets.
30GroupSetsconfiguration30ReplicationManagerconfigurationandintegrationwithRecoverPoint.
32ReplicationManagerprocessoverview32VSSAPIandKVSSutility32ExchangetasksthatcanbeautomatedbyRM.
32HowthissolutionusesRM.
33RMapplicationsetconfiguration.
33SpecialRMenvironmentvariablerequired.
34Aboutreplicationoptions.
34Replicationoptionconfiguration.
34vCenterSiteRecoveryManagerconfiguration36Prerequisites.
36SRMrequirementsforvSphere.
36SRMconfigurationsteps36Step1–InstallandconfigureSRMwiththeRecoverPointSRAadapter.
37Step2–Configuretheconnectionbetweentheprotectedandrecoverysites37Step3–ConfigureRecoverPointarraymanagers37Step4–Configureresourceinventorymappings38Step5–Configureprotectiongroups.
39Step6–Createtherecoveryplan.
40Step7–Customizevirtualmachinerecoveryoptions,includingIPcustomization41Exchangeconfigurationtosupportdatacenterfailover42AnalysisandreportingwithEMCDataProtectionAdvisor(DPA)43DPAintegrationwithRecoverPoint43DPA/RecoverPointsamplereports.
44DPAintegrationwithVMwarevSphere48Registeringtheplug-in48Viewingtheplug-inreports.
48DPA/vSpheresamplereport.
48DPAintegrationwithVNX/CLARiiON.
495EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerDPA/VNXsamplereports49DPAintegrationwithMicrosoftExchangeServer.
50Solutionvalidationandtestresults.
51RecoverPointjournalusageunderExchangeload.
51AboutMicrosoftLoadGen.
51RecoverPointjournalspaceusageduringtesting51SRMrecoveryplantesting53Recoveryplantesting.
53ExchangefailoverwithSRM.
55ChangingtheDAGIPaddress.
56Validatingclientaccess57ExchangefailbackwithSRM58Resynchronizationoptions.
58Failbacksteps.
59ExchangedatabaserecoverywithReplicationManager.
60Restoreoptions.
60Consistencygrouprestoreoptions.
61Conclusion62Summary62Findings.
62References63Whitepapers63Productdocumentation.
63Otherdocumentation.
63EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager6ExecutivesummaryIntheenterprise,email,calendaring,andunifiedmessaginghavebecomemission-criticalapplications,withtheleadingplatformbeingMicrosoftExchange.
ITresourcesfacetheconflictingchallengesofreducingadministrationcostswhiledeliveringgreaterprotectionforboththeapplicationandtheuserdata.
Becauseanyunplanneddowntimecanhaveadramaticimpactonthecontinuityofbusiness,ITcustomersaredemandingimprovedlevelsofservice,includingcontinuousapplicationavailability.
What'smore,enterpriseswithdatacentersatmultiplegeographiclocationswanttheabilitytoweatheranaturalorman-madedisasteratanydatacentersitewithoutanydisruptiontobusiness.
TheEMCProtectionforMicrosoftExchangeServer2010solutionisanExchangebusinesscontinuitysolutiondesignedforenterprisesthatrequireapplicationprotectionbothlocally,withinadatacenter,andalsoacrossmultipledatacenterswithinametropolitanareaoracrosstheglobe.
Thesolutionoffershighavailabilityateverylocationandautomatedrecoveryfromadisasteratanylocation.
Thesolutionleverages:EMCVNX5700storagewiththeVNXTotalProtectionPack,whichincludes:EMCRecoverPoint/SEEMCReplicationManagerEMCDataProtectionAdvisorforreplicationanalysisVMwarevSphere5withvCenterSiteRecoveryManager(SRM)5BusinesscaseSolutionoverview7EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerIntroductionThepurposeofthiswhitepaperistodemonstratehowEMCandVMwaretechnologiescanbeleveragedtoprovidehighavailabilityanddisasterrecoveryprotectionforMicrosoftExchangeServer2010enterprisedeploymentsatmultiple,active,geographicallydistributeddatacenters.
Thescopeofthispapercorrespondstothescopeofthesolutionvalidation(build,test,anddocument)activitiesperformedbyEMCengineersinanEMClaboratory.
Whatwasbuiltandtestedisdescribedand,wherepossible,recommendationsandguidelinesareprovidedforprofessionalstodesignanidenticalorsimilarsolutionforacustomer.
Theconcepts,instructions,procedures,recommendations,andguidelinespresentedinthisdocumentarebynomeansexhaustive.
Thetargetaudienceforthiswhitepaperisbusinessexecutives,ITdirectors,andinfrastructureadministratorswhoareresponsiblefortheircompany'sExchangelandscape.
Thetargetaudiencealsoincludesprofessionalservicesgroups,systemintegrationpartners,andotherEMCteamstaskedwithdeployingExchangesystemsinacustomerenvironment.
Ahigh-levelunderstandingofExchangesolutionsandExchangelandscapesisbeneficial.
Familiaritywithvirtualizationconceptsisalsobeneficial.
PurposeScopeAudienceEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager8TechnologyoverviewThissectionprovidesanoverviewoftheprimarytechnologiesusedinthissolution.
ThetightintegrationoftheseproductsandtechnologiesmakepossibleallofthebenefitsoftheExchangebusinesscontinuitysolutiondescribedinthispaper.
EMCVNX5700storagesystemEMCRecoverPointEMCReplicationManagerEMCDataProtectionAdvisorEMCPowerPath/VEVMwarevSphereVMwarevCenterSiteRecoveryManager(vCenterSRM)TheEMCVNX5700storagesystemisamemberoftheVNXseriesnext-generationstorageplatform,poweredbyIntelprocessors.
TheVNXseriesispoweredbyIntelXeonProcessors,forintelligentstoragethatautomaticallyandefficientlyscalesinperformance,whileensuringdataintegrityandsecurity.
TheVNXseriesisdesignedtodelivermaximumperformanceandscalabilityformid-tierenterprises,enablingthemtogrow,share,andcost-effectivelymanagemultiprotocolfileandblocksystems.
VNXarraysincorporatetheRecoverPointsplitter,whichsupportsunifiedfileandblockreplicationforlocaldataprotectionanddisasterrecovery.
EMCUnisphereisthecentralmanagementplatformfortheEMCVNXseries,providingasinglecombinedviewoffileandblocksystems,withallfeaturesandfunctionsavailablethroughacommoninterface.
Unisphereisoptimizedforvirtualapplicationsandprovidesindustry-leadingVMwareintegration,automaticallydiscoveringvirtualmachinesandESXiserversandprovidingend-to-end,virtual-to-physicalmapping.
ForadditionalVNXspecifications,refertotheEMCVNXSeriesUnifiedStorageSystemsSpecificationSheet(http://www.
emc.
com).
OverviewEMCVNX5700storagesystem9EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerTheEMCRecoverPointfamilyprovidesacost-effectivesolutionforprotectionofcriticalproductiondataatbothlocalandremotesites,andprovidescustomerswithacentralizedmanagementinterfacethatallowstherecoveryofdatatopracticallyanypointintime.
EMCRecoverPointisanenterprise-classdataprotection,replication,anddisasterrecoverysolutiondesignedtoprotectapplicationdataonheterogeneousSAN-attachedserversandstoragearrays.
RecoverPointrunsonanout-of-bandapplianceandcombinesindustry-leadingContinuousDataProtection(CDP)technologywithuniquebandwidthreductiontechnology,no-data-lossreplicacreation,andupdatingtoprotectdatabothlocallyandremotely.
RecoverPointprovidesthefollowingreplicationoptionsforbothphysicalandVMwarevirtualizedenvironments:ContinuousDataProtection(CDP)—CDPcontinuouslycapturesandstoresdatamodificationslocally,enablinglocalrecoveryfromanypointintime,withnodataloss.
Bothsynchronousandasynchronousreplicationsaresupported.
ContinuousRemoteReplication(CRR)—CRRsupportssynchronousandasynchronousreplicationbetweenremotesitesoverFCandaWAN.
SynchronousreplicationissupportedwhentheremotesitesareconnectedthroughFCandprovidesazerorecoverypointobjective(RPO).
Asynchronousreplicationprovidescrash-consistentprotectionandrecoverytospecificpointsintime,withasmallRPO.
ConcurrentLocalandRemoteReplication(CLR)—CLRisacombinationofCRRandCDPandprovidesconcurrentlocalandremotedataprotection.
InRecoverPoint,CDPisnormallyusedforoperationalrecovery,whileCRRisnormallyusedfordisasterrecovery.
ThesolutiondescribedinthiswhitepaperusesaRecoverPointCLRconfiguration.
WithRecoverPoint,datarecoverycanbeperformedlocallyand/orremotelybyrewindingthetargetvolumesbacktoaselectedpointintimethroughtheuseofearlierversionsofdatasavedinthejournal.
RecoverPointuseseitherFCoranIPnetworktosenddataoveraWAN.
ThissolutionusesanIPnetworkforreplicationofdatabetweensites.
EMCRecoverPoint/SE,usedinthissolution,istheentry-levelofferingthatallowsreplicationandContinuousDataProtectionfortheEMCVNXseriesarrays.
RecoverPointappliances(RPA)TheRecoverPointappliance(RPA)isa1UserverthatrunsRecoverPointsoftwareandincludesfour4gigabitFCconnectionsandtwo1gigabitEthernetconnections.
Forlocal-onlyreplication,twoRPAsareinstalledattheprotectedsite.
Forremotereplication(orbothlocalandremotereplication),fourRPAsareinstalled,twoattheprotectedsiteandtwoattherecoverysite.
EMCRecoverPointEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager10RecoverPointsplitterRecoverPointuseslightweightsplittingtechnologyontheapplicationserver,inthefabric,orinthearraytomirrorapplicationwritestotheRecoverPointcluster.
CLARiiONandVNXarrayshaveintegratedRecoverPointsplittersthatoperateineachstorageprocessor,ensuringthattheRecoverPointapplicationreceivesacopyofeachwrite.
Thearray-basedsplitteristhemosteffectivewritesplitterforVMwarereplication,enablingreplicationofVMwareVirtualMachineFileSystem(VMFS)andrawdevicemapping(RDM)volumeswithoutthecostorcomplexityofadditionalhardware.
ThesplittersupportsbothFCandiSCSIvolumespresentedbytheCLARiiON/VNXarraystoanyhost,includinganESXserver.
Forthissolution,array-basedwritesplittersruninsidethestorageprocessorsontheVNX5700array.
RecoverPointjournalsRecoverPointjournalsstoretime-stampedapplicationwritesforlaterrecoverytoselectedpointsintime.
Threejournalsareprovisionedforlocalandremotereplication—aproductionjournalattheproductionsite,andahistoryjournalatboththeproductionandrecoverysites.
Forsynchronousreplication,everywriteisretainedinthehistoryjournalforrecoverytoanypointintime.
Forasynchronousreplication,severalwritesaregroupedbeforedeliverytothehistoryjournal—thissupportsrecoverytosignificantpointsintime.
Bookmarkedpointsintimecanbecreatedautomaticallyormanuallytoenablerecoverytospecificapplicationorsystemevents.
Theproductionjournals,oneperconsistencygroup,recordthesystemdelta-markinginformation.
Productionjournalsdonotcontainsnapshotsforpoint-in-timerecovery.
RecoverPointconsistencygroupsRecoverPointusesreplicationsetsandconsistencygroupstoensuretheconsistencyandwrite-orderfidelityofpoint-in-timeimages.
Areplicationsetdefinesanassociationbetweenaproductionvolumeandthelocaland/orremotevolumestowhichitisreplicating.
Aconsistencygrouplogicallygroupsreplicationsetsthatmustbeconsistentwithoneanother.
Theconsistencygroupensuresthatupdatestotheproductionvolumesarewrittentothereplicasinconsistentwriteorderandthatthereplicascanalwaysbeusedtocontinueworkingfromortorestoretheproductionsource.
RecoverPointreplicationispolicy-driven.
Areplicationpolicy,basedonaparticularbusinessneed,canbeuniquelyspecifiedforeachconsistencygroup.
Thispolicygovernsthereplicationparametersfortheconsistencygroup—forexample,theRPOandrecoverytimeobjective(RTO)fortheconsistencygroup,anditsdeduplication,datacompression,andbandwidthreductionsettings.
11EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerEMCReplicationManagermanagesEMCpoint-in-timereplicationtechnologiesthroughacentralizedmanagementconsole.
ReplicationManagercoordinatestheentiredatareplicationprocess—fromdiscoveryandconfigurationtothemanagementofmultiple,application-consistent,disk-basedreplicas.
ReplicationManagerisusedtosafeguardandprotectyourbusiness-criticalapplications,suchasOracle,MicrosoftExchangeServer,MicrosoftSQLServer,andVMware-basedvirtualmachines.
EMCReplicationManager,whenusedwithEMCRecoverPoint,providessolutionsthateliminatebackupwindowswithoutimpactingproduction.
Thisintegrationhelpsyoutocreateapplication-consistentcopiesofbusiness-criticaldata—atspecificspointsintime—locallywithRecoverPointCDP,remotelywithRecoverPointCRR,orbothlocallyandremotelywithRecoverPointCLR.
WithReplicationManager,RecoverPointreplicascanberestoredtoanysignificantpointintimethatfallswithintheprotectionwindow.
Additionally,ReplicationManagercancreatemorepoint-in-timecopiesofthesameproductionvolumesusingotherEMCreplicationtechnologies.
Forexample,inadditiontocreatingspecificpoint-in-timecopiesofproductionvolumesusingCDP/CRR/CLR,ReplicationManagercanalsocreateclonesorsnapsofthesamevolumesusingEMCSnapViewtechnology,whichisavailableonVNXandCLARiiONstoragesystems.
ReplicationManagerleveragesMicrosoftVolumeShadowCopyService(VSS)toprovidepoint-in-timerecoveryandroll-forwardrecoveryforMicrosoftExchangeServer2010byusingCopyandFullbackupmodes.
Bothmodesbackupthedatabasesandtransactionlogs,butonlyFullmodetruncatesthelogsafterasuccessfulreplicavalidation.
Becausethesesnapshotsaretransportable,theycanbeusedforrepurposing.
Forexample,ifyourserverattachestoaSAN,youcanmasktheshadowcopyfrom(makeitinvisibleto)theproductionserverbutunmaskitfrom(makeitvisibleto)anotherserversothatthecopycanbereusedforbackupormailbox-levelrecovery.
FormoreinformationaboutEMCRecoverPointandEMCReplicationManagerintegrationpoints,reviewthewhitepaperentitledEMCReplicationManagerandEMCRecoverPointathttp://www.
emc.
com.
FormoreinformationaboutEMCReplicationManagerintegrationwithMicrosoftExchangeServer,reviewtheReplicationManagerProductGuideandReplicationManagerSupportforExchange2010TechnicalNotesavailableonEMCPowerlinkathttp://powerlink.
emc.
com.
EMCReplicationManagerEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager12EMCDataProtectionAdvisor(DPA)providesthevisibilitynecessaryforyourorganizationtounderstandallofthedetailsinvolvedinmanaginglargeandcomplexdataprotectionenvironments.
DPAsoftwareautomaticallymonitors,analyzes,andprovidesalertsonmanyaspectsofacompany'sITinfrastructure.
Inthissolution,DPAisusedtoanalyzeandmonitorthereplicationenvironment.
DPAisasophisticatedreportingandanalyticsplatformthatprovidescustomerswithfullvisibilityintotheeffectivenessoftheirdataprotectionstrategy.
DPAdoesthisbymonitoringallofthetechnologiesthatacustomerusestoprotectdata,includingbackupsoftware,storagearrays,fileservers,andtapelibraries.
DPA'ssophisticatedreportingengineprovideshighlycustomizablereportstohighlightproblemswithintheenvironmentandenablescustomerstoperformcapacitymanagement,servicelevelreporting,chargeback,changemanagement,andtroubleshooting.
DPA'sPredictiveAnalysisEngineprovidescustomerswithearlywarningofproblemsthatmightoccurandgeneratesalertsthatenablecustomerstoresolveproblemssoonertoreducebusinessimpact.
DPAisdesignedtohelpusersidentifyandfixperformanceandcapacitymanagement(PCM)issueswithinlargeenterprises.
DPAconsistsofanumberofloosely-coupledprocessesanddatastoresforholdingconfigurationandgathereddata.
Inaddition,DPAhasanumberofinterfacestoimportandexportinformation,whichallowforintegrationwithotheraspectsofalargeenterpriseandtoprovideasignificantpartofanoveralldistributedsystemsmanagementstrategy.
EMCDataProtectionAdvisor13EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerEMCPowerPath/VEprovidesintelligent,high-performancepathmanagementwithpathfailoverandloadbalancingoptimizedforEMCandselectedthird-partystoragesystems.
PowerPath/VEsupportsmultiplepathsbetweenavSpherehostandanexternalstoragedevice.
HavingmultiplepathsenablesthevSpherehosttoaccessastoragedeviceevenifaspecificpathisunavailable.
MultiplepathscanalsosharetheI/Otraffictoastoragedevice.
PowerPath/VEisparticularlybeneficialinhighlyavailableenvironmentsbecauseitcanpreventoperationalinterruptionsanddowntime.
ThePowerPath/VEpathfailovercapabilityavoidshostfailurebymaintaininguninterruptedapplicationsupportonthehostintheeventofapathfailure(ifanotherpathisavailable).
VMwarevSphereusesthepowerofvirtualizationtotransformdatacentersintosimplifiedcloudcomputinginfrastructuresandenablesITorganizationstodeliverflexibleandreliableITservices.
vSpherevirtualizesandaggregatestheunderlyingphysicalhardwareresourcesacrossmultiplesystemsandprovidespoolsofvirtualresourcestothedatacenter.
Asacloudoperatingsystem,vSpheremanageslargecollectionsofinfrastructure(suchasCPUs,storage,andnetworking)asaseamlessanddynamicoperatingenvironmentandalsomanagesthecomplexityofadatacenter.
VMwarevCenterSiteRecoveryManager(SRM)isadisasterrecoveryframeworkthatintegrateswithEMCRecoverPointtoautomaterecoveryofvirtualmachinesandtheirstoragesothatrecoverybecomesassimpleaspressingasinglebutton.
SRMisanextensiontoVMwarevCenterthatenablesintegrationwitharray-basedreplication,discoveryandmanagementofreplicateddatastores,andautomatedmigrationofinventoryfromonevCenterinstancetoanother.
SRMitselfdoesnotreplicateanydata.
Forthis,SRMleveragesanexternalreplicationsolutionsuchasRecoverPoint.
SRMserverscoordinatetheoperationsofthereplicatedstoragearraysandvCenterserversattheproductionandrecoverysitessothat,asvirtualmachinesattheproductionsiteshutdown,virtualmachinesattherecoverysitestartupandassumeresponsibilityforprovidingthesameservices,usingthedatareplicatedfromtheproductionsite.
Migrationofprotectedinventoryandservicesfromonesitetotheotheriscontrolledbyarecoveryplanthatspecifiestheorderinwhichvirtualmachinesshutdownandstartup,thecomputeresourcesthatareallocated,andthenetworkstheycanaccess.
NewSRMversion5cannowleveragenativeVMwarevSpherereplicationorthird-party,storage-basedreplication(RecoverPointinthissolution)toprovidecentralizedmanagementofrecoveryplans,enablenon-disruptivetesting,andautomatesiterecoveryandmigrationprocesses.
OneofthekeynewfeaturesinSRMversion5isitsautomatedfailbackcapabilities,whichprovideautomaticfailbackandre-protectionofvirtualmachinesbyautomaticallyreversingreplicationtotheoriginalsite.
EMCPowerPath/VEVMwarevSphereVMwarevCenterSiteRecoveryManagerEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager14VMwarevCenterSRMintegrateswiththeunderlyingreplicationproduct,RecoverPoint,throughaRecoverPointStorageReplicationAdapter(SRA).
TheadapterenablesSRMtoidentifywhichvirtualmachinesarebeingreplicatedandtocoordinatetheexecutionofrecoveryplanswiththereplicationlayer.
SRMrequiresseparatevCenterServerinstancesatboththeproductionandfailoversite.
SRMinstancesaredeployedatbothsitesandintegratedirectlywiththeirlocalvCenterserverinstances.
NewfeaturesintheRecoverPointSRAadapterincludefullyautomatedfailback(withouttheneedforaseparateplug-in).
Formoreinformation,refertoEMCRecoverPointStorageReplicationAdapterforVMwareSiteRecoveryManagerVersion2.
0ReleaseNotes.
TheRecoverPointSRAsupportsthediscoveryofarraysattachedtoRecoverPointandthediscoveryofconsistencygroupsenabledformanagementbySRM.
SRAalsosupportsSRMfunctions,suchasfailoverandfailovertesting,bymappingSRMrecoveryplanstotheappropriateRecoverPointactions.
EMCRecoverPointStorageReplicationAdapterforVMwarevCenterSRM15EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerOverallsolutionarchitectureanddesignThissolutiondemonstrateshowEMCandVMwaretechnologiescanbeleveragedtoprovidehighavailabilityanddisasterrecoveryprotectionforMicrosoftExchangeServer2010enterprisedeploymentsatmultiple,geographicallydistributedsites.
Thesolution,asvalidated,demonstratesthereplicationandactivationofanentireExchangeServer2010DatabaseAvailabilityGroup(DAG),alongwithitsassociatedExchangevirtualmachines,acrossaWANbetweentwo(simulated)activedatacenters.
Inanactive/activesiteconfiguration,suchastheonethissolutionrepresents,bothsites(orallsites,iftherearemorethantwo)areactiveproductionsites,thatarelocallyprotectedandalsogloballyprotectedbyeveryothersite.
Inotherwords,eachsitecanbereferredtoasbothaprotectedsiteandarecoverysite.
Withthisinmind,thesubsequentsectionsrefertoapairofprotected/recoverysites,buteachsitecanreverseroleswiththeother,dependingonwherethedisastereventoccurs.
Further,inaconfigurationwithmorethantwoactivesites,everysiteisbothaprotectedsiteandapotentialrecoverysiteforanypeersiteaffectedbyadisaster.
Note:Eventhoughthissolutiondemonstratestheprotectionofanactive/activesiteconfiguration,thesolutioncanalsobeusedtoprotectactive/passivesiteconfigurations.
Table1presentsattributesofthesolutiondesign,includingspecificprotectionrequirements.
Table1.
SolutiondesignattributesAttributeDescriptionNumberofsites2sitesNumberofuserspersite10,000userspersite20,000userssupportedateachsiteduringDReventExchange2010userprofile150messagessent/received/day(0.
15IOPS)Mailboxsize2GBDatabaseread/writeratio3:2inMailboxResiliencyconfigurationHighavailabilitydesign1ExchangeDAGpersite4MailboxserversperDAG2databasecopiesperDAGMailboxserverdesign5,000usersperserver(2,500activeusers/2,500passiveusers)10databasesperserver500usersperdatabase6vCPUs,32GBRAMperMailboxservervirtualmachineClarificationofterminologyDesignattributesEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager16AttributeDescriptionStoragedesign1VNX5700storagearraypersite2TBNL-SAS(7.
2krpm)disksforExchangedatabaseandlogs(RDM/P)2TBNL-SAS(7.
2krpm)disksforvirtualmachineOS(VMFS)600GBSAS(10krpm)disksforRecoverPointjournalsvSpherehostdesign4Intel-basedserverswith4six-coreXeonX7460processors@2.
66GHz(24CPUs)and128GBRAM.
2serverspersite,eachsupports4ExchangeMailboxRolevirtualmachines.
4Intelbasedserverswith4six-coreXeonX7350Processors@2.
93GHz(16CPUs)and64GBRAM.
2serverspersite,eachsupports4ExchangeClientAccessandHubTransportRolevirtualmachines.
SimulatedRTOandRPOLocalandremoteRPO:5minutesLocalRTO:30minutesRemoteRTO:2hoursConnectivitybetweensites1Gb/sEthernetStorageconnectivitytophysicalhost2x8Gb/sFCportsDataprotectionDailyfullbackups(hardwareVSS)24application-consistentsnapshotsperday(24hours)Unlimitedcrash-consistentsnapshotsperday(24hours)**Note:Thenumberofcrash-consistentsnapshotsdependsonthesizeoftheRecoverPointjournal,theapplicationchangerate,andpolicysettings.
RefertoRecoverPointdesignonpage26.
ThissolutionvirtualizesExchange2010onVMwarevSphere5andleveragesEMC,Microsoft,andVMwarebestpracticesandguidelinesfordeployingExchangeinvirtualconfigurations.
FormoreinformationonExchangeServer2010deploymentsforhighavailabilityandsiteresiliency,refertohttp://technet.
microsoft.
com/en-us/library/dd638121.
aspx.
FormoredetailsonExchangeServer2010deploymentsonVMwarevSphere,refertoMicrosoftExchange2010onVMwareBestPracticesGuide(http://www.
vmware.
com).
Figure1illustratestheExchangeServer2010environmentdeployedforthissolution.
TheenvironmentrepresentstwoactivesiteswithfourvSpherehostsateachsite.
Eachsiteprovidesenoughperformanceandcapacitytosupportupto20,000activeusers(10,000usersduringnormaloperationsandanother10,000usersduringadisasterrecoveryevent).
Forthissolution,theActiveDirectoryandDNSservicesateachsiteareprovidedoutsideofthevirtualinfrastructure.
TheActiveDirectoryisconfiguredtomeetalloftherequirementsforthisExchangedeployment.
RedundantActiveDirectoryservers,aswellasDNSservers,areprovisionedatbothsites.
VirtualizationActive/activesiteconfiguration17EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerDataprotectionforbothsitesisprovidedbyRecoverPoint,withReplicationManagerinitiatingapplication-consistent(VSS)copiesforExchangedatabasesandlogs.
Intheeventofasite-specificdisaster,orifyouwanttomovetheserversortestdisasterrecovery,vCenterSRMisusedtocoordinateanentireExchangeserverfailoverfromonesitetoanothersiteandbackagain.
Figure1.
SolutionarchitecturediagramOneDAGwithfourMailboxserversisdeployedateachsite.
ADAGisasetofmailboxservers(upto16)thatreplicatetoeachother,providingdatabase-levelprotectionfromoutages.
DAGusesExchangeContinuousReplication(logshipping)andasubsetofWindowsfailoverclusteringtechnologiestoprovidecontinuoushighavailability(HA)andsiteresiliency.
ItreplacesearlierExchangeandWindowsfailovercluster-basedtechnologiesusedforHAinExchange2007,suchassinglecopyclusters(SCC),continuousclusterreplication(CCR),andstandbycontinuousreplication(SCR).
DAGmemberscanresideinthesamedatacenterortheycanbeconfiguredacrossmultiplesitesincross-site,"stretched"configurations.
DataprotectionExchangeServer2010DesignEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager18AnExchangeManagementConsolescreenshot,presentedinFigure2,showsdetailsabouttheExchangeDAGsconfiguredforthissolution.
AnExchange2010DAGisdeployedateachsitewithfourmemberserversandtwodatabasecopies.
EachExchangeMailboxserverisdesignedtosupport5,000userswithaprofileof150messages/user/dayat0.
15IOPS.
Duringnormaloperation,eachserverprovidesserviceto2,500activeusersandcanserviceanadditional2,500usersduringalocalswitchover.
Figure2.
ExchangeManagementConsoleGUI:ExchangeServer2010DatabaseAvailabilityGroupconfigurationEachMailboxserverisconfiguredwith10databases,fiveactiveandfivepassive.
AlldatabasesarebalancedanddistributedbetweenMailboxserverswithintheDAGandbetweenvSpherehoststoeliminateasinglepointoffailure.
ThisdesigneliminatesdowntimeduringvSpherehostorMailboxservervirtualmachinemaintenance.
Figure3.
ExchangeServer2010DAGdesign:DatabasedistributionbetweenMailboxserversandvSpherehosts19EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure4presentsascreenshotfromtheExchangeManagementConsoleshowingthedatabaseconfigurationforoneMailboxserver.
ItshowsthattendatabasesaredeployedonMailboxserverMBX1,wherefiveofthesedatabasesareactiveandtheotherfivearepassive.
Figure4.
ExchangeManagementConsoleGUI:MailboxserverconfigurationTosupporttheExchangeServer2010userprofileandmailboxsizerequirementsforthissolution(seeTable1fordetails),eachsiteusesanEMCVNX5700storagearraywith2TB7.
2krpmNL-SASdrivestohousedatabasesandlogs.
Tosimplifydesignanddeployment,aMailboxserverbuildingblockforeachMailboxserverisdesignedandconfiguredwiththeappropriatenumberofdrivestosupporttherequiredperformanceandcapacity.
ExchangestoragedesignEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager20AMailboxserverbuildingblockrepresentstheamountofstorage(I/Oandcapacity)andservercompute(CPU,memory)resourcesrequiredtosupportaspecificnumberofExchangeServer2010users.
Theamountofrequiredresourcesisderivedfromaspecificuserprofiletype(messagessent/received,IOPSperuser,andmailboxsize).
UsingthebuildingblockapproachsimplifiesthedesignandimplementationofExchangeServer2010.
Oncetheinitialbuildingblockisdesigned,itcanbeeasilyreproducedtosupporttherequirednumberofusersinyourenterprise.
Byusingthisapproach,EMCcustomerscannowcreatetheirownbuildingblocksthatarebasedontheircompany'sspecificExchangeenvironmentrequirements.
ThisapproachisveryhelpfulwhenfuturegrowthisexpectedbecauseitmakesExchangeenvironmentexpansionsimpleandstraightforward.
EMCbestpracticesinvolvingthebuildingblockapproachforExchangeServerdesignhaveproventobeverysuccessfulinmanycustomerimplementations.
FormoredetailsonhowtousetheEMCbuilding-blockmethodologyforExchange2010deployments,seetheMicrosoftExchange2010:StorageBestPracticesandDesignGuidanceforEMCStorage(http://www.
emc.
com).
Forthissolution,theExchangeMailboxservervirtualmachinedesignisbasedonabuildingblockfor5,000users.
Thestorage,CPU,andmemoryresourcesforthisbuildingblockarederivedfromthedesignattributespresentedinTable1onpage15.
ForadditionalMicrosoftguidelinesconsideredforthissolution'sdesign,seehttp://technet.
microsoft.
com/en-us/library/ee712771.
aspx.
Table2presentsasummaryoftheExchangeMailboxservervirtualmachinebuildingblockfor5,000userswitha150-messageprofileanda2GBmailboxquota.
Table2.
MailboxserverbuildingblocksummaryUsersperExchangeMailboxservervirtualmachineDisksperExchangeMailboxservervirtualmachinevCPUsperExchangeMailboxservervirtualmachineMemoryperExchangeMailboxservervirtualmachine5,00020(16+4)16x2TBNL-SASdisksinRAID1/0fordatabases4x2TBNL-SASdisksinRAID1/0forlogs6CPUs32GBBuildingblockdesignapproachMailboxservervirtualmachinebuildingblockdetails21EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerTable3presentsstoragedesigndetailsforaMailboxserverbuildingblockwith5,000users.
Table3.
Storagedesigndetailsfora5,000-userMailboxserverbuildingblockAttributeDetailsNumberofusers5,000(inaswitchovercondition)Userprofile150messagessent/received(0.
15IOPS)Mailboxsize2GBDisktype2TBNL-SAS,7.
2krpmStorageconfiguration/RAIDtype20disksperbuildingblockforExchangedata:16disksinaRAID1/0storagepoolfordatabases4disksinaRAID1/0RAIDgroupforlogsDatabasesperserver/usersperdatabase10databasesperserver,500usersperdatabaseLUNs/LUNsizes21LUNsperMailboxservervirtualmachine:10databaseLUNs(1.
6TB)(RDM/P)10logLUNs(100GB)(RDM/P)1LUNforvirtualmachineOS(200GB)(VMFS)WhendeployingstorageforExchangeServer2010inavirtualizedenvironmentonaVNXsystem,youcanchoosetouseeitherstoragepoolsortraditionalRAIDgroups.
Theuseofstoragepoolssimplifiesstorageprovisioning.
TraditionalstorageprovisioningwithonlyRAIDgroupsrestrictsthenumberofdisksyoucanhaveinagroupto16.
Storagepools,ontheotherhand,enableyoutomanagepotentiallyhundredsofdisksatatime.
Suchpool-basedprovisioningprovidesbenefitssimilartometaLUNstripingacrossmanydrivesbut,unlikemetaLUNs,storagepoolsrequireminimalplanningandmanagementeffort.
StoragepoolssupportthesameRAIDprotectionlevelsasRAIDgroupsdo:RAID5,RAID6,andRAID1/0.
Usinghomogeneousthickstoragepools(poolswiththesamedisktype)fordeployingExchangestorageonVNXsystemscanhelptosimplifydesignandLUNprovisioning.
TherearethreemainmodelsthatcanbeusedwhendesigningstoragepoolstobeusedforExchange2010deployedinphysicalorvirtualenvironments.
OnestoragepoolperMailboxserver—Inthismodel,asinglestoragepoolisdeployedforeachExchangeMailboxservervirtualmachine.
Thisoptionprovidesmoregranularityandeasydeploymentwithabuildingblockmethodology,anditalsoprovidesdatabasecopyisolationiftheserverisdeployedinaDAGwithmultiplecopies.
ThisdeploymentmodelalsoworkswellwhenExchangeServer2010isdeployedwithoutmailboxresiliency(noDAG).
AboutstoragepoolsEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager22OnestoragepoolpervSpherehost—ThismodelworkswellwhenExchangeisdeployedinavirtualenvironmentwithmultipleDAGcopies.
Thismodelcanhelpreducethenumberofstoragepoolsdeployedintheenvironment.
ItisimportanttobesurethatcopiesofthesamedatabasereplicatedtodifferentvirtualmachinesarenothostedbythesameESXserver.
Withcarefuldesign,thismodelcanprovidedatabasecopyisolationandbalancedperformance.
Onestoragepoolperdatabasecopy—Thismodelprovidesdatabasecopyisolationand,inmanycases,canminimizethenumberofpoolsthatmustbedeployed.
However,thismodelrequirescarefuldistributionofLUNstovSpherehostsandvirtualmachines.
DatabasecopiesfromeachpoolaredistributedtomultipleMailboxservervirtualmachines.
Forthissolution,onehomogeneousRAID1/0storagepoolwith40NL-SASdisksisdeployedforeachvSpherehosthostingExchangeMailboxServerRolevirtualmachines.
ThisconfigurationsupportsdatabasesfortwoMailboxServerRolevirtualmachinesoneachvSpherehost.
Itprovidesjustover36.
6TBofusablestorageandmeetstheIOPSandtotalmailboxcapacityrequirementsfortwobuildingblocks,eachwith5,000veryheavyusersanda2GBmailboxlimit.
Tosupportlogcapacityrequirements,four2TBNL-SASdrivesaredeployedinaRAID1/0(2+2)RAIDgroupconfigurationforeachvSpherehostwithtwoExchangeMailboxServerRolevirtualmachines.
Fromeachdatabasestoragepool,20x1.
6TBdatabaseLUNsareconfiguredtoaccommodatea1TBdatabaseandindex.
TheLUNsaredistributedamongExchangeMailboxservervirtualmachinesonthesamevSpherehost,andtheLUNsareconfiguredasRDM/Pvolumes.
ThesameapproachisusedforlogLUNs.
20x100GBLUNsarecreatedfromeachRAIDgroup.
TheLUNsaredistributedamongMailboxservervirtualmachinesonthesamevSpherehost,andtheLUNsareconfiguredasRDM/Pvolumes.
Note:LogsanddatabasesinthissolutionareseparatedondifferentdiskstosatisfytheprotectionrequirementspresentedinTable3.
Ateachsite,200GBvirtualmachineoperatingsystem(OS)volumesareconfiguredonthesameVNX5700storagearraywith2TBNL-SASdrivesconfiguredasRAID1(2+2)RAIDgroups.
EachOSLUNisformattedasaVMFSvolumeonthevSpherehost.
VNXstoragepooldesign23EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure5illustratesstorageconfigurationusedfortheMailboxservervirtualmachinesinthissolution.
Figure5.
StoragedesignforExchangeServer2010MailboxserversTosatisfytherequirementtocontinuetosupportall20,000Exchangeusersintheeventofadisasterateithersite,fourvSphereserversaredeployedateachsite.
TwovSphereserverswith32CPUsand128GBofRAMcapacitysupporteightMailboxServerRolevirtualmachines(withfourvirtualmachinespervSphereserver).
AnothertwovSphereserverswith16CPUsand128GBofRAMsupporteightExchangeClientAccessandHubTransportRolevirtualmachines(again,withfourvirtualmachinespervSphereserver).
Table4providesadditionaldetailsaboutthehost/roleassociationsatthetwosites(referredtointhetableasSiteAandSiteB).
vSphereserverdesignEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager24Note:Greyrowsindicateserver/computeresourcesactiveonlyduringsitefailover.
Table4.
vSpherehostandExchangeServerroleassociationsSitevSpherehostExchangeServerRole/hostnameCPUsMemory(GB)AESX1(24CPUs,128GBRAM)MailboxRole-MBX1632MailboxRole-MBX2632MailboxRole-MBX5fromSiteB632MailboxRole-MBX6fromSiteB632ESX2(24CPUs,128GBRAM)MailboxRole-MBX3632MailboxRole-MBX4632MailboxRole-MBX7fromSiteB632MailboxRole-MBX8fromSiteB632AESX3(16CPUs,64GBRAM)ClientAccessandHubTransport-CAS-HUB1416ClientAccessandHubTransport-CAS-HUB2416ClientAccessandHubTransport-CAS-HUB3416ClientAccessandHubTransport-CAS-HUB4416ESX4(16CPUs,64GBRAM)ClientAccessandHubTransport-CAS-HUB5416ClientAccessandHubTransport-CAS-HUB6416ClientAccessandHubTransport-CAS-HUB7416ClientAccessandHubTransport-CAS-HUB8416BESX5(24CPUs,128GBRAM)MailboxRole-MBX5632MailboxRole-MBX6632MailboxRole-MBX1fromSiteA632MailboxRole-MBX2fromSiteA632ESX6(24CPUs,128GBRAM)MailboxRole-MBX7632MailboxRole-MBX8632MailboxRole-MBX3fromSiteA632MailboxRole-MBX4fromSiteA632BESX7(16CPUs,64GBRAM)ClientAccessandHubTransport-CAS-HUB9416ClientAccessandHubTransport-CAS-HUB10416ClientAccessandHubTransport-CAS-HUB11416ClientAccessandHubTransport-CAS-HUB12416ESX8(16CPUs,64GBRAM)ClientAccessandHubTransport-CAS-HUB13416ClientAccessandHubTransport-CAS-HUB14416ClientAccessandHubTransport-CAS-HUB15416ClientAccessandHubTransport-CAS-HUB1641625EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerForlocalprotectionandhighavailability,anExchange2010DAGisdeployedateachsite.
Inmostcases,thisissufficienttoprotectExchangeduringMailboxserverfailureormaintenance.
However,DAGdoesnotprovideprotectionfromlogicaldatabasecorruption,becausesuchcorruptioncanbereplicatedtoothercopies.
Toprotectfromlogicalcorruption,VSSbackupsorapoint-in-timerecoverysolutioncanbeimplemented.
Note:AnExchangeServer2010laggedcopycanalsoprovideprotectionfromdatabasecorruption.
Butlaggedcopiescannotprovidepoint-in-timerecovery.
Afteralaggedcopyisusedforrecovery,itmustbere-created(seeded)again.
ForadditionalinformationaboutExchangedatabasecorruptiontypesandlaggedcopylimitations,visithttp://technet.
microsoft.
com/en-us/library/dd335158.
aspx.
Inthissolution,EMCRecoverPointCLRprovidesprotectionfromlogicaldatabasecorruption.
RecoverPointusesbookmarks("namedsnapshots")toprovidepoint-in-timerecovery.
EachbookmarkisstoredinaRecoverPointjournalconfiguredatbothsites(CDPandCRRcopies)anddatacanberecoveredfromeithersite.
EMCoffersalternativestoRecoverPointforprotectingagainstlogicaldatabasecorruption,includingEMCVNXSnapViewsnapshotsandclones.
Thealternativethatisbestforyoudependsonyourspecificrequirements.
ExchangelocalprotectionEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager26RecoverPointdesignInthissolutionEMCRecoverPointprovidesprotectionfromExchangelogicaldatabasecorruption,whichcanpotentiallyreplicatetootherExchangedatabasecopieswithintheDAG.
RecoverPointalsoprovidesnear-instantaneouspoint-in-timerecoverywithminimaldataloss.
Inthissolution,RecoverPointisconfiguredasfollows:ThereplicationmethodisConcurrentLocalandRemoteReplication(CLR).
ThiscombinesbothCDPandCRRtechnologiesandprovidespoint-in-timerecoveryfromeitherCDPorCRRcopies.
EachMailboxservervirtualmachineisplacedintoitsownconsistencygroupwithallreplicateddatabaseandlogLUNs,includingtheLUNcontainingtheguestOS.
ThisconfigurationensuresfullconsistencyacrossallvolumesusedbytheMailboxServerRolevirtualmachines.
Threejournalsaresetupforeachconsistencygroup.
Twojournalsresideattheprotectedsitetosupporttheprotectedvolumesandtheirlocalreplicas,andonejournalresidesattherecoverysitetosupporttheremotereplica.
Note:RecoverPointCRRalonecanprovideprotectionfromlogicaldatabasecorruption,butCRRcanreplicateonlyasingleDAGcopy.
WithCRR,replicatedExchangedatabasescanbemountedattherecoverysiteonanyExchangeDAGmemberserver,butthedatabasesthenrequireseedingtoprovidelocalnativehighavailabilityforExchangeattherecoverysite.
RecoverPointconsistencygroupsarecreatedforeachreplicatedMailboxservervirtualmachine.
Separatingreplicatedvirtualmachinesintomultipleconsistencygroupsmakesitpossibletoplanfordifferentdisasterrecoveryscenarios.
Forexample,eachExchangeMailboxservervirtualmachinecanbefailedoverseparatelyfromtheothervirtualmachines,ortheentireprotectedenvironmentcanbefailedoverinasingleprocess.
Note:Thisapproachdoesnotpreventtherecoveryofasingledatabase.
RefertoExchangedatabaserecoverywithReplicationManageronpage60.
RecoverPointconsistencygroupdesign27EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure6showsthedetailsfortheconsistencygroupconfigurationwithreplicationsetsforonereplicatedExchangeMailboxservervirtualmachine.
Figure6.
RecoverPointconsistencygroupconfigurationInadditiontotherequirementofhavingreplicationvolumesateachsite,RecoverPointrequiresaverysmallvolume,knownastherepositoryvolume,whichmustbeconfiguredontheSAN-attachedstorageateachsiteforeachRPAcluster.
TherepositoryvolumestoresconfigurationinformationabouttheRPAsandconsistencygroups,whichenablesaproperlyfunctioningRPAtoseamlesslyassumethereplicationactivitiesfromafailingRPAinthesamecluster.
RecoverPointjournalvolumesstoreconsistentpoint-in-timesnapshots(orbookmarks)toenablepoint-in-timerecoveryofExchangedata.
ThesebookmarksallowDVR-likerollbacksofthedatatodifferentpointsintime.
ForeachconsistencygroupintheRecoverPointCLRconfiguration,threejournalsaresetup,twoatthelocalsitetosupporttheprotectedvolumesandtheirlocalreplicas,andoneattheremotesitetosupporttheremotereplica.
Theproductionjournals,oneforeachconsistencygroup,containsystemdelta-markinginformation.
Productionjournalsdonotcontainsnapshotsforpoint-in-timerecovery.
RecoverPointstoragerequirementsRecoverPointjournaldesignEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager28Thetwomostimportantconsiderationswhensizingstorageforjournalvolumesare:PerformanceProtectionwindowForoptimaljournalperformance,ensurethatyouchoosetheappropriateRAIDanddrivetypes.
Thesolution,asvalidated,uses600GB10krpmSASdrivesinaRAID1/0configurationforjournalvolumes,whicharedeployedinRAID1/0RAIDgroups.
TheprotectionwindowdependsonthechangerateoftheapplicationandRPOrequirements(howfarbackExchangeadministratorswanttogotoforpoint-in-timerecovery).
Bothofthesefactorsdeterminetherequiredjournalsize.
EMCrecommendssizingyourjournalstomeetyourRPOrequirements.
Determiningthejournalsizerequiresyoutocalculatetheexpectedpeakchangerateinyourenvironment.
Twentypercentofthejournalmustbereservedforthetargetsidelogandfivepercentforinternalsystemneeds.
Usethefollowingformulatocalculatejournalvolumesizebasedontheexpectedchangerateandrequiredrollbacktimeperiod:Forexample,tosupporta3-day(72-hour)rollbackrequirement(259,200seconds),with5Mbpsofnewdatawritestothereplicationvolumesinaconsistencygroup,thecalculationisasfollows:Journalsize=5Mbpsx259,200seconds/0.
8x1.
05=1,701,000Mb(~213GB)Inthiscalculation,259,200secondsrepresentsa72-hourrollbackwindow,and0.
8represents20percentforreservedjournalspace.
Asageneralrule,EMCrecommendsmakingthejournalsizeatleast20percentofsizeofthedatabeingreplicated,whenchangeratesarenotavailable.
ForfulldetailsaboutconfiguringandsizingRecoverPointjournalvolumes,seetheEMCRecoverPointAdministrator'sGuideavailableonhttp://powerlink.
emc.
com.
ForthisRecoverPointCLRconfiguration,500GBjournalspaceisallocatedforeachlocalandremotecopyofeachconsistencygroup.
(Inthissolution,eachconsistencygroupcontainsallLUNsforoneMailboxserver.
)The500GBjournaliscomposedoffive100GBjournalvolumes.
Thedeploymentofsmallervolumesenablesjournalspacetobeincreased,seamlessly,bysmallerincrements.
Forbestperformance,itisabestpracticetocreateandgrowjournalsbyusingvolumesthatareidenticalinsize,becauseRecoverPointre-stripesthevolumesduringexpansion.
Productionjournals,whichdonotcontainsnapshotsforpoint-in-timerecovery,areallocated20GBofstorage.
Thesejournalsarecomposedoffour5GBjournalvolumes.
ConsiderationswhensizingjournalvolumesSizingjournalvolumes29EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure7showsdetailsofthejournalvolumesdeployedinthissolutionasviewedwiththeRecoverPointManagementConsole.
Figure7.
RecoverPointjournalvolumeconfigurationNote:EMCstronglyrecommendsadheringtotheRecoverPointguidelinespresentedintheEMCRecoverPointAdministrator'sGuidetoensurethatyourjournalvolumesmeetyourspecificRPOrequirements.
Table5providesasummaryoftheRecoverPointstorageconfigurationforthissolution.
ForvalidationofjournalspaceunderExchangeload,seeRecoverPointjournalusageunderExchangeloadonpage51.
Note:Journalvolumesizes(seeTable5)wereconfiguredtoaccommodatemultipletestscenariosandmightdifferfromguidelineslistedintheEMCRecoverPointAdministrator'sGuide.
RefertothesectionRecoverPointjournalusageunderExchangeloadforinformationaboutjournalusageduringExchangeworkloadvalidationtesting.
Table5.
RecoverPointstorageconfigurationforthissolutionVolumetypeSiteAandSiteBCommentsRepository3GB1volumeperstoragearray/RPAclusterJournal40x100GB32x5GBJournalLUNsconfiguredfromRAID1/0groups.
500GBjournalperconsistencygroup:5x100GBvolumesforeachlocalandremotecopy.
20GBjournalperconsistencygroup:4x5GBvolumesforeachproductioncopy.
Replication80x1.
6TBfordatabasevolumes80x100GBforlogvolumesReplicationvolumesizesmustbeequalorlargerthanproductionvolumes.
EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager30WhenRecoverPointisdeployedwithVMwarevCenterSRM,RecoverPointmustbeconfiguredtoenableautomaticfailovercapability.
Thisconfigurationisaccomplishedbyusingthe"GroupismanagedbySRM,RecoverPointcanonlymonitor"policysettingintheRecoverPointManagementConsole,asshowninFigure8.
Figure8.
ConsistencygrouppolicyconfigurationformanagementbySRMForadditionaldetailsonconfiguringRecoverPoint,consulttheEMCRecoverPointReleaseNotesandEMCRecoverPointAdministrator'sGuide.
ARecoverPointgroupsetisasetofconsistencygroupstowhichthesystemappliesparallelbookmarksatauser-definedfrequency.
Agroupsetallowsyoutoautomaticallybookmarkasetofconsistencygroupssothatthebookmarkrepresentsthesamerecoverypointineachconsistencygroupinthegroupset.
ThisallowsyoutodefineconsistentrecoverypointsforconsistencygroupsdistributedacrossdifferentRPAs.
Groupsetsareusefulforconsistencygroupsthatdependononeanotherorthatmustworktogetherasasingleunit.
Forthissolution,twogroupsetsareconfigured,whereeachgroupsetismadeupoffourconsistencygroups,eachrepresentingMailboxserversinaDAGateachsite.
Thisconfigurationenableseasyrecovery,becauseallbookmarksforeveryconsistencygroupwithinagroupsethavethesameRPOandtimestampwithafrequencyof15minutes.
ConsistencygrouppolicyconfigurationformanagementbySRMRecoverPointgroupsetsGroupSetsconfiguration31EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure9showsthegroupsetinformationconfiguredforthissolution.
Figure9.
RecoverPointgroupsetsEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager32ReplicationManagerconfigurationandintegrationwithRecoverPointThissolutionintegratesEMCRecoverPointwithEMCReplicationManager.
ReplicationManager'sbuilt-inapplicationintelligenceandautomationenablesyoutoleverageRecoverPoint'sreplicationtechnologytoscheduleandcreateVSScopiesofExchange,bothlocallyandremotely.
ReplicationManagerfreezestheproductionExchangedatabase,requestsaVSScopy,flushesExchangeServer'scachetodisk,andcreatesaVSSbookmarkforRecoverPointandReplicationManager.
Exchangeisthenthawed,allwithintherequiredVSSwindowoftime.
Oncethawed,productionresumes.
MeanwhiletheRecoverPointVSSbookmarkiscapturedinthelocalCDPjournalaswellastheremoteCRRjournal.
MicrosoftExchangeServersupportstheVSSAPIthatenablesRecoverPointtointegratewithExchange.
RecoverPointprovidesautilitycalledKVSSthatinvokestheMicrosoftVSSframeworktoprepareaVSSimage.
ForfulldetailsonusingKVSSutilityforprotectingExchange,refertoReplicatingMicrosoftExchangeServerwithEMCRecoverPoint–TechnicalNotes.
Inthissolution,ReplicationManagerprovidesanadditionallevelofautomationbycoordinatingapplication-consistentsnapshots.
ReplicationManager(RM)canautomateExchange2010taskssuchas:CreateExchangedatabaseapplicationsetsCreateandmanagemultiple-siteapplication-consistentreplicasofExchangedatabasesRunafullExchangejobtocreateaVSSbookmark,runtheMicrosoftExchangeutilityeseutil,andthentruncatetheExchangelogsRunanExchangecopyjobthatcreatesaVSSbookmarkStartanon-demandmountanddismountofanExchangedatabaseRestoreExchangedatabasesfromeitherlocalorremotebookmarkstotheproductionExchangeserverinsecondsItisveryeasytouseReplicationManager'sGUIinterfacetoautomatetherestoreofExchangetoanapplication-consistentpointintime.
ReplicationManagerhandlestherestorelocallybyusingtheRecoverPointCDPreplicaor,ifnecessary,RMcanrestorebacktoproductionbyusingtheRecoverPointCRRExchangereplica.
ReplicationManagerprocessoverviewVSSAPIandKVSSutilityExchangetasksthatcanbeautomatedbyRM33EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerInthissolution,ReplicationManagerautomatesRecoverPointapplication-consistentreplicasandperformsExchangelogtruncation.
TosatisfythesolutionrequirementspresentedinTable1,thedesignsupports24application-consistent(VSS)snapshotsina24-hourcycle.
Note:Inadditiontomaintaininghourlyapplication-consistentreplicas(snapshots)initiatedbyReplicationManager,theRecoverPointjournalmaintainsmanymorecrash-consistentsnapshotsfromwhichExchangedatabasescanbeeasilyrecovered.
Thenumberofcrash-consistentsnapshotsinthejournaldependsonthesizeofthejournalandtheapplicationchangerate.
RefertoRecoverPointjournalusageunderExchangeload,whichdescribestestingofjournalusageunderanExchangeworkload.
Forthissolution,anRMapplicationsetiscreatedforeachExchangeMailboxservervirtualmachine.
Theapplicationsetincludesalltendatabasesconfiguredontheserver.
ThisdesignalignswiththeRecoverPointconsistencygroupdesign,whereeachconsistencygroupcontainsalloftheExchangedatabasesandlogsforaspecificMailboxserver.
Figure10showstheRMapplicationsetpropertiesforMailboxserverMBX1.
Figure10.
RMapplicationsetpropertiesforoneExchangeMailboxserverHowthissolutionusesRMRMapplicationsetconfigurationEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager34Forthissolution,eachRecoverPointconsistencygroupisconfiguredwithanadditionalreplicationsetfortheMailboxserverOSLUNthatresidesontheVMwareVMFSdatastorevolume.
ThiscreatesapotentialconflictbetweenReplicationManagerandRecoverPoint,becausetheMicrosoftVSSframeworkdoesnotsupportVMFSdatastores.
Toresolvethisconflict,thefollowingenvironmentvariableiscreatedoneachExchangeMailboxservervirtualmachinewithReplicationManagerAgentinstalled:ERM_RP_EXTRA_DEVS_ALLOWED=1Withthissettinginplace,RecoverPointcontinuestoprovidecrash-consistentreplicasofallLUNsattachedtotheExchangeMailboxservervirtualmachine,includingtheOSVMFSvolume,andReplicationManagercontinuestoprovideapplication-consistentreplicasofallExchangeRDMvolumes.
InanExchange/VSSenvironment,ExchangeadministratorscanselecttheOnlineFullorOnlineCopyreplicationoption.
FortheOnlineFulloption,ReplicationManagerreplicatesthedatabasesandtransactionlogs,verifiestheconsistencyofthedatabasesandlogs(optionalforExchange2010),andthentruncatesthelogs.
FortheOnlineCopyoption,ReplicationManagerreplicatesthedatabasesandtransactionlogsinthesamewayitdoesduringanOnlineFulloption;however,itdoesnottruncatethelogs.
Inthissolution,ReplicationManagerjobsareconfiguredwithtwoReplicaTypeoptionstoprotecttheExchangeServer2010databases,OnlineFullandOnlineCopy.
ReplicationManagerusestheVSSframeworktoinitiatebothofthesereplicatypes.
OnlineFulljobsaresetupfordailybackups,andOnlineCopyjobsaresetuptorunathourlyintervalsduringbusinesshourstoprovideapplication-consistentrecovery.
SpecialRMenvironmentvariablerequiredAboutreplicationoptionsReplicationoptionconfiguration35EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure11showstheReplicationManagerOnlineFulljobconfigurationsettingstoperformdailybackupofMailboxserverMBX1.
AdvancedreplicationsettingsenableReplicationManagertoverifydatabasestatesbeforeperformingthisjob.
Figure11.
ReplicationManagerjobadvancedreplicationsettingsEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager36vCenterSiteRecoveryManagerconfigurationThissectiondescribeshowvCenterSiteRecoveryManager(SRM)version5isconfiguredforautomaticfailoveroftheprotectedsitetotherecoverysite.
Whendesigningadisasterrecoverysolution,itisessentialthatallsoftwarecomponentsareconfiguredandworkingcorrectly.
CarefulplanningandcoordinationofITpersonnelresponsiblefortheseactivitiesisalsoessentialforasuccessfulrecoveryplanexecutionforaplannedorunplannedfailover.
ThisensurestheshortestRTOandcompliancewithSLAs.
SRMhasseveralrequirementsforthevSphereconfigurationateachsite:EachsitemustincludeavCenterservercontainingatleastonevSpheredatacenter.
Therecoverysitemustsupportarray‐basedreplicationwiththeprotectedsite,andtherecoverysitemusthavehardwareandnetworkresourcesthatcansupportthesamevirtualmachinesandworkloadsastheprotectedsite.
AtleastonevirtualmachinemustbelocatedonadatastorethatisreplicatedbyRecoverPointattheprotectedsite.
TheprotectedandrecoverysitesmustbeconnectedbyareliableIPnetwork.
Storagearraysmayhaveadditionalnetworkrequirements.
Therecoverysitemusthaveaccesstothesamepublicandprivatenetworksastheprotectedsite,althoughtherecoverysitedoesnotnecessarilyrequireaccesstothesamerangeofnetworkaddresses.
VMwaretoolsmustbeinstalledonallvirtualmachines.
InstallingandconfiguringVMwarevCenterSiteRecoveryManager(SRM)forautomatedsiterecoveryusingRecoverPointinvolvesthesesteps:1.
InstallandconfigureSRMwiththeRecoverPointSRAadapter.
2.
Configuretheconnectionbetweentheprotectedandrecoverysites.
3.
ConfigureRecoverPointarraymanagers.
4.
Configureresourceinventorymappings.
5.
Configureprotectiongroups.
6.
Createtherecoveryplan.
7.
Customizevirtualmachinerecoveryoptions,includingIPcustomization.
MostofthesestepsareexecutedfromtheSRMinterfaceinvCenter,whereintelligentwizardssupportquickandeasyconfiguration.
Forfulldetailsofthesesteps,consulttheVMwarevCenterSiteRecoveryManagerAdministrationGuide5.
0(http://www.
vmware.
com).
PrerequisitesSRMrequirementsforvSphereSRMconfigurationsteps37EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerInstallingandconfiguringSRMinvolvesthefollowingtasks:1.
ConfigureSRMdatabasesatbothsites.
Thesedatabasesstoretherecoveryplans,inventoryinformation,andsoon.
2.
InstalltheSRMserveratbothsites.
3.
InstalltheRecoverPointStorageReplicationAdapterontheSRMserveratbothsites.
ThisadapterenablesSRMandRecoverPointintegration.
4.
InstalltheSRMclientplug-inononeormorevSphereclientsatbothsites.
RecoverPointStorageReplicationAdapterisincludedintheSRMinstallationpackagewhichisavailablefordownloadfromtheVMwarewebsite.
Installationandconfigurationinstructionsareprovidedintheproductreleasenotes,whichareincludedintheinstallationpackage.
WiththeSRMdatabaseandSRMserverinstalledateachsite,youthenneedtoconfiguretheconnectionfromtheprotectedsitetotherecoverysite.
ThisisaccomplishedbyspecifyingtheremoteSRMserverIPdetailsintheConnecttoRemoteSitewizardattheprotectedsite.
ForSRMtointegratewithRecoverPoint,RecoverPointarraymanagersmustbeconfiguredatboththeprotectedandrecoverysites.
UsetheSRMconfigurationwizardtoconfigurepropertiesforRecoverPointSRA.
ThewizarddiscoversthereplicatedstoragedevicesattheprotectedandrecoverysitesandidentifiestheVMFSdatastoresthattheysupport.
Whenfinished,thewizardpresentsalistofreplicateddatastoregroups.
Figure12showspropertiesforRecoverPointSRAmanagerattheprotectedsite.
TheconnectionparametersforRecoverPointattheprotectedsitearespecified.
ThesameparametersmustbespecifiedforSRMattherecoverysite.
Figure12.
SRMRecoverPointArrayManagerconfigurationStep1–InstallandconfigureSRMwiththeRecoverPointSRAadapterStep2–ConfiguretheconnectionbetweentheprotectedandrecoverysitesStep3–ConfigureRecoverPointarraymanagersEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager38Afteranarraymanagerisconfiguredforeachsite,arraypairsmustbeenabledforusewithSRM.
Thiscanbedonefromeithersite.
Figure13.
EnabledRecoverPointarraymanagerAfterthearraymanagersareenabled,the"local"and"remote"devicesforeachenabledarraypairaredisplayed.
Figure14.
ReplicateddevicesshowninRecoverPointSRMarraymanagerOnceSRMandarraymanagersareconfigured,mappingsbetweensiteresourcesmustbedefined.
Step4–Configureresourceinventorymappings39EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerAprotectiongroupisacollectionofvirtualmachinesthatallusethesamedatastoregroup(thesamesetofreplicatedLUNs)andthatallfailovertogether.
Tocreateaprotectiongroup,selectthedatastoregroupstoprotect,andspecifyadatastoregroupattherecoverysitewhereSRMcancreateplaceholdersformembersoftheprotectiongroup.
UsetheCreateProtectionGroupwizardtodothis.
ThewizardautomaticallydetectsthedatastorescurrentlyprotectedbyRecoverPointandallowsyoutoselecttheonestoincludeintheprotectiongroup.
Eightprotectiongroupswerecreatedforthissolution,oneforeachExchangeMailboxservervirtualmachine.
Figure15showstheprotectiongroupscreatedforthesolution.
Figure15.
SRMprotectiongroupscreatedforthissolutionAfteraprotectiongroupiscreated,shadowvirtualmachinesareautomaticallycreatedintherecoverysitevCenterinventory.
TheseactasplaceholdersforthevirtualmachinesthatcanbefailedoverwithSRM.
TheshadowvirtualmachinescannotbestartedindependentlyfromSRMandareremovediftheirprotectiongroupisdeleted.
Figure16illustratesthis.
Figure16.
ShadowvirtualmachinesarecreatedfollowingthecreationofprotectiongroupsStep5–ConfigureprotectiongroupsEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager40Afterprotectiongroupsarecreated,thenextstepistocreaterecoveryplans.
Youcancreatemultiplerecoveryplanstoaccommodatemanydifferentrecoveryscenarios.
AsshowninFigure17,tenrecoveryplansarecreatedforthissolution,twotofailovertheentireenvironmentfromeachsite,andtheothereighttofailoverindividualExchangeMailboxservervirtualmachinesindependently.
ThefigurealsoshowstheSRMoptionforcreatingarecoveryplanthatcontainsindividualprotectiongroupsfromoneofthesites.
Figure17.
SRMrecoveryplanconfigurationoptionsStep6–Createtherecoveryplan41EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerTherecoveryoptionsforindividualvirtualmachinescanbecustomizedtosatisfyspecificrequirements.
Theavailablecustomizationoptionsconstituteapowerfultoolforensuringthatcomplexrecoveryplanscanbeimplementedwithease.
Forexample,iftherearemultiplevirtualmachinesinaprotectiongroup,theirstartupsequencecanbecustomizedbyassigningthemdifferentrecoverypriorities.
OptionsincludetheabilitytochangevirtualmachineIPaddressessothattheypointtospecificsubnetsattherecoverysite.
Optionscanalsobesettorunspecificpre-orpost-processingscriptsbeforeoraftertheexecutionofarecoveryplan.
ToensurethattheentireExchangeDAGattheprotectedsitesuccessfullyfailsovertotherecoverysite,theIPaddressofeachMailboxservervirtualmachineattherecoverysiteisspecified.
TheoriginalIPaddressesoftheprotectedvirtualmachinesarealsospecifiedtoensuresuccessfulandseamlessfailback.
Figure18showsthevirtualmachinecustomizationwizardforoneExchangeMailboxservervirtualmachinewheretheIPaddressesandDNSinformationarespecified.
Figure18.
ExchangevirtualmachineIPcustomizationpropertiesforSRMrecoveryplansStep7–Customizevirtualmachinerecoveryoptions,includingIPcustomizationEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager42ExchangeconfigurationtosupportdatacenterfailoverMicrosoftExchangeServeristightlycoupledwiththedomaincontrollerandusestheActiveDirectoryservicetoprovideauthorizationandauthenticationservicesfortheExchangeserversandusers.
DisasterrecoveryforExchangeServerrequiresthattheActiveDirectoryserviceisavailableattheboththeprotectedsiteandtherecoverysite.
EMCrecommendsensuringthatadomaincontrollerrunningActiveDirectoryisconfiguredattheremotesitebeforebeginningRecoverPointreplication.
ThisfacilitatesbettercommunicationbetweentheActiveDirectoryserverandtheExchangeserverduringtheExchangeinstallationprocess.
Inaddition,intheeventofatotalsource-sidefailureduringremotereplication,thiseliminatesthepotentialservicedelaythatcanresultfromtheneedtoconstructanewActiveDirectoryserveratthetargetsite.
Toachieveasuccessfulfailover,itisveryimportanttoensurethattheExchange2010DAGsandallunderlyingclusterandActiveDirectorycomponentsareconfiguredcorrectly.
DAGpropertyvaluesarestoredinboththeActiveDirectoryandtheclusterdatabase.
However,somepropertiesarestoredonlyintheclusterdatabase.
Inthissolution,anentireDAG(withunderlyingWindowsFailoverClustercomponents)ismovedfromoneactiveproductionsitetoanotheractiveproductionsitewhereExchangeservicesarecurrentlyconfiguredforusersservicedbythatsite.
ForcompleteinstructionsonconfiguringExchange2010DAGsandallunderlyingclusterandActiveDirectorycomponents,refertothearticlesManagingHighAvailabilityandSiteResilienceathttp://technet.
microsoft.
com/en-us/library/dd638215.
aspxandConfigureDatabaseAvailabilityGroupPropertiesathttp://technet.
microsoft.
com/en-us/library/dd297985.
aspx.
43EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerAnalysisandreportingwithEMCDataProtectionAdvisor(DPA)EMCDataProtectionAdvisor(DPA)isasophisticatedreportingandanalyticsplatformthatprovidescustomerswithfullvisibilityintotheeffectivenessoftheirdataprotectionstrategy.
DPAdoesthisbymonitoringallofthetechnologiesthatacustomerusestoprotectdata,includingbackupsoftware,storagearrays,fileservers,andtapelibraries.
DPA'ssophisticatedreportingengineprovideshighlycustomizablereportstohighlightproblemswithintheenvironmentandenablescustomerstoperformcapacitymanagement,servicelevelreporting,chargeback,changemanagement,andtroubleshooting.
DPA'sPredictiveAnalysisEngineprovidescustomerswithearlywarningofproblemsthatmightoccurandgeneratesalertsthatenablecustomerstoresolveproblemssoonertoreducebusinessimpact.
DPAisdesignedtohelpusersidentifyandfixperformanceandcapacitymanagement(PCM)issueswithinlargeenterprises.
DPAconsistsofanumberofloosely-coupledprocessesanddatastoresforholdingconfigurationandgathereddata.
Inaddition,DPAhasanumberofinterfacestoimportandexportinformation,whichallowforintegrationwithotheraspectsofalargeenterpriseandtoprovideasignificantpartofanoveralldistributedsystemsmanagementstrategy.
DPAgathersconfiguration,status,andperformanceinformationfromaRecoverPointsysteminyourenvironment.
TheCollectorcomponentisaprocessthatgathersdatafromanapplicationordevice.
ACollectorisautomaticallyinstalledontheDataProtectionAdvisorserverwhenyouinstalltheServercomponent.
YoucaninstalltheCollectorcomponentonotherdevicesintheenvironmenttoprovideenhanceddatacollection.
DataProtectionAdvisorstoresthreetypesofdata:Configurationdata,whichincludesinformationontheconfigurationofDataProtectionAdvisoritself—Thisinformationismaintainedbythecontrollerprocessandisgenerallystaticandsmallinsize.
Gathereddata,whichisthedatagatheredbyCollectors—Thesizeofthisdatacanbecomequitelargeduetothedynamicnatureofthecollecteddata.
Asaresult,itismaintainedseparatelyfromtheconfigurationdata.
Recoverabilityanalysisdata,whichisgatheredbytherecoverabilityengine—RecoverabilityanalysisisonlyavailableforaDPAServerinstalledonaWindowsorSolarisplatform.
ItisnotavailableforDPAserversinstalledonRedHatorSUSEEnterpriseLinux.
Thedefaultnamesforthedatastoresareconfig,datamine,andilluminator.
DPAintegrationwithRecoverPointEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager44MonitoringofRecoverPointrequiresadditionallicensingbeyondwhatisincludedinthestandardDPAlicense.
FormoreinformationonhowtoobtainlicensesforRecoverPointreporting,contactanEMCrepresentative.
RecoverPointcomponentsaredisplayedinthenavigationtreeinahierarchyunderStorage>Replication,withthemanaginghostatthetoplevel.
RecoverPointappliances(RPAs)andsplittersaredividedbysite,ifthereismorethanonesiteinyourRecoverPointsystem.
Consistencygroupcopiesaremappedinthehierarchytotheirconsistencygroups.
ToviewreportsforRecoverPoint,right-clickthehost,RPA,orRPAcomponentnodeinthenavigationtree.
Figure19throughFigure25presentsomesampleDPAreportsbasedonthemonitoringofaRecoverPointsystem.
Figure19showstheRecoverPointconsistencygroupjournallagforanRPAovera30-dayperiod.
Figure19.
DPA/RecoverPointsamplereport:RecoverPointconsistencygroupjournallagDPA/RecoverPointsamplereports45EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure20showstheSANthroughputandtheWANthroughputatbothsitesforasinglenightlybackup.
Figure20.
DPA/RecoverPointsamplereport:RecoverPointRPAthroughputEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager46Figure21showstheRecoverPointconsistencygroupcopystatus,includingGroupName,StorageAccess,JournalUsage,andsoon.
Figure21.
DPA/RecoverPointsamplereport:RecoverPointconsistencygroupcopystatus47EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerFigure22showsanoverviewofRecoverPointevents,includingwarnings,errors,andinformationalmessages.
Figure22.
DPA/RecoverPointsamplereport:RecoverPointeventsoverviewEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager48DPAcanbeintegratedwithVMwarevSpherewithaVMwareplug-in.
Thisplug-inallowsyoutoviewreportsfromavSphereclientthatprovidesinformationonvirtualizationhostsandvirtualmachines.
Registeringtheplug-inAfteryouconfigureavirtualizationnodeinDPA,registertheVMwareplug-infromtheDPAGUItoviewreportsfromtheinfrastructureclient.
Viewingtheplug-inreportsAfterregisteringtheplug-in,tabsareavailablefromthevSphereclientregisteredwiththeplug-in.
ThetabsdisplayreportsthatdifferaccordingtowhetheravirtualizationhostorvirtualmachineisselectedintheVMwarehierarchy.
Figure23presentsasamplereportgeneratedbyDPAtomonitorresourceutilizationinavSphereenvironment.
Figure23.
DPA/vSpheresamplereport:ResourceutilizationoverviewDPAintegrationwithVMwarevSphereDPA/vSpheresamplereport49EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerDPAcanintegratewithEMCSymmetrixVNXseriesandEMCCLARiiONstoragearrays.
VNXandCLARiiONstoragearraysreplicatedwithEMCRecoverPointrequireadditionalconfigurationtoenablecompleterecoverabilityanalysis.
Forconfigurationinstructions,refertotheDPAHelpsystem.
Figure24andFigure25showsampleDPAreportsbasedonthemonitoringofanEMCVNXseriesstoragearray.
Figure24showsanoverviewofchangesmadetothestorage,forexample,changesmadetoLUNsizes.
Figure24.
DPA/VNXsamplereport:VNXchangesummaryreportDPAintegrationwithVNX/CLARiiONDPA/VNXsamplereportsEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager50Figure25showsanoverviewofoverallstoragecapacity,rawcapacity,andusercapacity.
Figure25.
DPA/VNXsamplereport:VNXcapacityoverviewMicrosoftExchangeServercanbemonitoredforrecoverabilityfromacollectorinstalledonthesamemachineasExchangeorfromacollectorinstalledremotely.
Note:ExchangecanbemonitoredforrecoverabilityanalysisandforsysteminformationonlyfromtheExchangeServerhost.
TheaccountusedtoconnectDPAtotheExchangeservermustbeadomainuserwithExchangeread-onlyadministratorrightsandlocaladministratorrights.
DPAsupportsrecoverabilityanalysisforonlyoneExchangeinformationstoreinacluster.
DPAintegrationwithMicrosoftExchangeServer51EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerSolutionvalidationandtestresultsThefollowingsectionsprovidedetailsandresultsfortestsperformedaspartofthissolutionvalidation.
Thetestresultsinclude:RecoverPointjournalusageunderloadSRMrecoveryplantestingExchangefailoverwithSRMExchangefailbackwithSRMExchangedatabaserecoverywithReplicationManagerRecoverPointjournalusageunderExchangeloadOneofthemostimportantquestionsthatneedtobeansweredduringaRecoverPointdeploymentforExchange2010ishowmuchjournalspaceisrequiredtoprotecttheExchangedata.
Ifyouallocatetoolittlejournalspace,youcannotmeetyourRPOrequirementsandmightlosethebookmarks(point-in-timesnapshots),becausenewbookmarksarelikelytooverwritethecurrentones.
Ifyouallocatetoomuchjournalspace,youmightwastevaluablestorageresources.
Aspartoftesting,a24-hourMicrosoftLoadGenerator(LoadGen)testwasruntomeasurethejournalusageunderload.
LoadGendoesnotrepresentreal-worldworkloads.
LoadGenisasimulationtooltomeasuretheeffectsofMAPI,OWA,ActiveSync,IMAP,POP,andSMTPclientsonExchange2010and2007servers.
ThetoolallowsyoutotesthowaserverrunningExchangerespondstoemailloads.
Tosimulatethedeliveryofmessagingrequests,LoadGentestsrunonclientcomputers.
LoadGenisausefultoolforadministratorswhensizingserversandvalidatingadeploymentplan.
Specifically,LoadGenhelpsyoudetermineifeachservercanhandletheloaditisintendedtocarry.
AnotheruseforLoadGenistohelpvalidateanoverallsolution.
ForadditionalinformationaboutusingLoadGen,visitMicrosoftTechNetathttp://technet.
microsoft.
com/en-us/library/dd335108.
aspx.
Table6showsjournalspaceusageinfour-hourincrementsobservedduringa24-hourLoadGentest.
125GB(25percent)ofthe500GBjournalwasreservedspace,thusonlyabout375GBofcapacitywasavailableforusebythetest.
Duringthetest,especiallyduringthefirsteightto10hoursofbusy"daytime"activitygeneratedbyLoadGen,almost46percentofthejournalwasutilized.
Bytheendofthetest,thejournalhadnearlyreacheditsmaximumusablecapacity.
Thetestresultsshowedthatthejournalscouldprovideonlya24-hourmaximumprotectionwindowbecausethechangerategeneratedbyLoadGenwasalmostthreetimesmorethanthe5Mb/schangerateoriginallyusedtosizethejournals.
Thus,thejournalsizeestablishedfortestingwasnotsufficienttoprovidethethreedaysofrollbackprotectionoriginallyplanned.
Toprovidethreedaysofprotection,1.
5TBjournalsneedtobedeployedforanExchangeenvironmentwherethechangerateis15Mb/s.
AboutMicrosoftLoadGenRecoverPointjournalspaceusageduringtestingEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager52ThenumberspresentedinTable6areintendedtoserveonlyasanapproximateguidelinetosizeRecoverPointjournalsforExchange2010.
Itisrecommendedtosizejournalsbasedonactualchangeratesinyourproductionenvironment.
Theresultspresentedinthetablearebasedonthefollowing:LoadGenworkloadfor5,000usersperserverwith150sent/receivedmessagesperuserHourlyapplication-consistent(VSS)bookmarksforaRecoverPointconsistencygroupwithalloftheLUNsforasingleMailboxserverwith10databasesAutomaticcrash-consistent(VSS)bookmarksforaRecoverPointconsistencygroupwithalloftheLUNsforasingleMailboxserverwith10databasesNightlyscheduledbackupjobinitiatedbyReplicationManagerPercentagesarebasedona375GBusablejournalspace(500GBminus25percentreservedbyRecoverPoint)provisionedforeachconsistencygroupand13.
6TBofreplicatedExchangedata(80percentof17TBprovisionedstorage).
Table6.
RecoverPointjournalusagewithExchangeServer2010underloadTesttimelineJournalusage(GB)Journalusageperuser(MB)Journalusage(percentage)Start0.
20GB----0.
05%4hrs.
(daytime)113GB23MB30.
1%8hrs.
(daytime)174GB36MB46.
4%12hrs.
(nighttime)184GB38MB49.
0%16hrs.
(nighttime)228GB47MB60.
8%20hrs.
(daytime)279GB57MB74.
4%24hrs.
(daytime)345GB71MB92.
0%Note:Performanceismeasuredbasedon375GBofusablejournalspaceanda15Mb/schangerategeneratedbytheLoadGentool.
53EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerSRMrecoveryplantestingHavingadisasterrecoveryplaninplaceisthefirststeptowardensuringthatyouarepreparedfortheworst-casescenario.
However,theonlywaytoknowifyourdisasterrecoveryplanworksistotestit.
TheabilityofSRMtoexecuterecoveryplansintestmodeallowsyoutodothis.
Recoveryplanscanbetestedatanytimewithoutinterruptingreplicationorthebusiness'sRPO.
Accuratetimemeasurementofrecoveryplantestingenablesadministratorstopredicthowmuchtimetherecoveryofthevirtualenvironmentislikelytotake.
Administratorscanquicklyaccessareplicaoftheentireprotectedenvironmentfortestingpurposes.
Automaticallygeneratedsummaryreportscanbeusedtodemonstratecompliancewithregulatoryrequirements.
Allrecoveryplansweresuccessfullytestedaspartofthevalidationofthissolution.
TodemonstratethefailoverprocesswithSRMandRecoverPoint,bothfailoverandfailbackofeachsiteinitsentiretywasperformed.
Whentestingarecoveryplan,SRMcreatesanisolatedtestnetworkattherecoverysiteandenablesimageaccessfortheRecoverPointconsistencygroup.
SRMalsostartsthevirtualmachinesreplicatedbyRecoverPointandperformsanyreconfigurationnecessarytoaccessthedisksonthearrayattherecoverysite.
Note:Duringtesting,somevirtualmachinescouldnotpoweronautomaticallyinvCenteraspartoftheSRMrecoveryplan.
Asaworkaround,thevirtualmachineswerepoweredonbyconnectingthevSphereclientdirectlytothevSphereserver.
EMChasopenedasupportrequestwithVMware(SR11105524210)andVMwareiscurrentlyinvestigatingtheissue.
EMCrecommendscheckingtheVMwaresupportsiteperiodicallyforhotfixesrelatedtothisissue.
FortheMBX1protectiongroupfailovertest,thestatusviewintheRecoverPointmanagementapplicationshowsthatRecoverPointimageaccessisenabled,asshowninFigure26(onthenextpage).
ThismeansthatthevSpherehostandMBX1ExchangeMailboxServerRolevirtualmachinehaveaccesstotheRecoverPointpoint-in-timebookmarkinitiatedbySRM.
Theentiretesttookjustover17minutesincludingIPaddresschanges.
TherecoverytestforallfourMailboxserverstookjust25minutes.
Table7providesadditionaldetailsaboutresultsfromthemultiplerecoveryplantests.
Table7.
SRMRecoveryPlantestingresultsSRMRecoveryPlanTimeelapsed(minutes)RTOMetSingleMailboxserver17YesFourMailboxserversinaDAG25YesRecoveryplantestingEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager54Figure26.
RecoverPointmanagementapplicationshowingimageaccessenabledonthehostattherecoverysiteFollowingtherecoverytest,SRMgeneratedaRecoveryPlanHistoryreport.
Thisreportcanbeusedtodemonstrateaccuratetimingofrecoveryplansandrecoveryreliabilityforauditing,compliance,systemadministration,andotherbusinesspurposes.
Figure27showsanextractfromtheRecoveryPlanHistoryreport.
Figure27.
SRMRecoveryPlanHistoryReportsample55EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerExchangefailoverwithSRMThissectiondescribesafailoverprocessforExchangeMailboxserversdeployedinaDAGatSiteAtotheactiverecoverySiteB,whereanotherproductionExchangeDAGisalreadyrunning.
(ThesectionvCenterSiteRecoveryManagerconfigurationinthiswhitepaperdescribeshowthisrecoveryplanwascreatedandtested.
)ThesuccessfulexecutionofanSRMrecoveryplaninstillsconfidencethatrecoveryfromareal-worlddisasterislikelytobesuccessful.
EMCstronglyrecommendsperiodictestingofrecoveryplanstoensurethattheyoperateasexpected.
Forthissolution,remotesiterecoveryoccursastheresultoftheintegrationofRecoverPointContinuousRemoteReplication(CRR)withVMwarevCenterSRM.
SRMautomatestherecoveryprocesssothatexecutingfailoverbecomesassimpleaspressingasinglebutton.
ThereisnoneedtointeractwiththeRecoverPointconsole.
AnSRMplug-in,installedonthevCenterinstanceattherecoverysite,isallthatisrequiredtotriggertheexecutionofarecoveryplan.
Inthissolution,MicrosoftExchangeisdesignedandconfiguredforlongdistancedisasterrecovery;therefore,thesubnetatSiteAdoesnotextendtoSiteB.
TheExchangeconfigurationincludesasingleActiveDirectoryforestandtwodifferentAD/DNSsites.
TheActiveDirectoryconfigurationautomaticallyreplicatesbetweenthesitesduringnormaloperation.
Whenadisasteroccursatoneofthesites,thereplicationisinterrupted.
SitefailoverthenoccursasaresultoftheexecutionofaVMwareSRMrecoveryplanfortheentireExchangeDAG.
FailingoverallprotectiongroupsinaprotectedExchangeDAG(atSiteA)toitsrecoverysite(SiteB)involvesactivatingthe"Recovery"optionontheSRMserverattherecoverysite,asshowninFigure28.
Figure28.
RunningsitefailovertorecoverExchangeDAGfromSite-AEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager56ItisessentialtoensurethattheExchangeDAGIPaddressisupdatedintheDNSbeforethefirstMailboxservermemberoftheDAGispoweredonattherecoverysite.
IftheDNSisnotupdated,theunderlyingWindowsFailoverClusterDAGresourcenameisnotbroughtonline.
TheDAGnodewiththe"ClusterGroup"actsasthePrimaryActiveManager.
ThePrimaryActiveManageristheDAGnoderesponsibleforchoosingwhichdatabasesareactivatedinafailover.
FormoreinformationonthePrimaryActiveManager,refertotheMicrosoftTechNetarticleathttp://technet.
microsoft.
com/en-us/library/dd776123.
aspx.
TochangetheDAGIPaddress,runthefollowingExchangePowerShellcommandontheSRMserver.
Set-DatabaseAvailabilityGroup-Identity-DatabaseAvailabilityGroupIPAddressesisthenameoftheExchangeDAGfromSiteA(inthissolutionitis),andistheaddressprovidedfortherecoverysitesubnetthatisdifferentfromtheprotectedsitesubnet.
Note:ExchangeManagementToolsmustbeinstalledontheSRMserverinordertorunExchangeManagementShellcmdlets.
TosimplifytheDAGIPaddresschangeprocessduringSRMfailover,anadditionalstepthatcallsanExchangePowerShellscriptcanbeaddedtoarecoveryplan.
Figure29showsastepthatissuesaPowerShellcommandtocallabatchfiletochangetheDAGIPaddress.
Figure29.
ScriptaddedtoarecoveryplantochangetheDAGIPaddressChangingtheDAGIPaddress57EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerWhenallvirtualmachinesarerunning,modifytheCASarrayentryontheDNSserverandchangetheIPaddresstoreflectthenewsubnet.
Next,useWindowstoolstochangetheclusterIPaddressandthehostIPaddressontheNetworkLoadBalancerontheHUB/CASserverstoreflectthenewCASarrayclusterIPandhostIPaddresses.
VerifythatExchangeisrunningandthatuserscannowsendandreceiveemail.
Note:InthissolutionExchangeCAS/HUBserverswerenotreplicated.
Instead,CAS/HUBserversdeployedateachsiteprovidedenoughresourcestosupportusersfromtheothersiteduringthefailoverevent.
Table8providesdetailsabouttestresultsobtainedfromusingSRMtoperformfailoverofanentireExchangeenvironmentfromSiteAtoSiteB.
Table8.
SRMrecoveryplantestresultsSRMrecoveryplanTimeelapsed(min)RTOmetFourMailboxserversinaDAG38YesValidatingclientaccessEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager58ExchangefailbackwithSRMVMwareSiteRecoveryManagerversion5nowprovidesautomaticfailbackfunctionality.
Thisfunctionalityenablesyoutoperformanautomatedfailbackoperationafteraplannedorunplannedfailover.
A"reprotect"processautomaticallyreversesreplicationandsynchronizesanychangesfromtherecoverysitebacktotheprotectedsite.
Figure30showsascreenshotfromtheSRMManagementConsole,fromwhichyoucaninitiateafailbackoperation.
vCenterSRM,integratedwiththeRecoverPointSRAplug-in,automaticallyinitiatesstoragereplication.
Figure30.
SRMFailbackoperationavailablefromvCenterSRMInthecaseofanunplannedfailoverfollowinganactualdisaster,ifallstoragewaslostatthestrickensite(thesiterequiredatotalrebuild),itislikelythataverylargeamountofdatawillneedtobereplicatedfromtherecoverysitebacktothenewlyrebuilt,originalprotectedsite.
Thisprocessistimeconsumingandmustbeverycarefullyplanned.
EventhoughyoucanusetheSRMautomaticreprotectprocesstoinitiateresynchronizationofthedataandconfigurationsettingsautomatically,youcaninsteadexercisegreatercontrolovertheresynchronizationbyinitiatingreplicationusingtheRecoverPointorUnispheremanagementconsoles.
Note:Forthepurposesofvalidatingthissolution,theprotecteddatawasnotdestroyedfollowingthefailover.
Thus,thefailbackandreprotectoperationrequiredRecoverPointtoreplicateonlyminimalchangestothedata.
TheSRMfailbackprocessfortheentireExchangeDAGwithtwocopiestookjustover30minutes.
Resynchronizationoptions59EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerToperformfailback,followthesehigh-levelsteps:1.
Verifyallnetworkcommunicationsbetweentherecoverysiteandtheoriginalprotectedsite.
2.
VerifyconnectivitybetweenvCenterservers.
3.
Ensureallresourcemappingsareinplace.
4.
EnsurenochangesneedtobemadetoSRMprotectiongroupsorprotectedvirtualmachines.
5.
Modifytherecoveryplantoupdateanycustomscripts.
Forexample,updateExchangeDAGIPaddressesthathavechanged.
AlsoupdateCASarrayIPaddressesiftheCASarraywaspreviouslyreplicated.
Note:Forthepurposesofvalidatingthissolution,ExchangeCAS/HUBserverswerenotreplicated.
Instead,theCAS/HUBserversdeployedateachsiteprovidedenoughresourcestosupportusersfromothersitefollowingafailoverevent.
6.
Toperformfailbackincrementally,specifyingwhichdatatoreplicateandinwhatsequence,usetheRecoverPointorUnispheremanagementconsoletoreplicatedataandresynchronizeconfigurationsettingsfromtherecoverysitebacktotheoriginallyprotectedsite.
Alternatively,tohaveSRMperformthefailbackautomatically,initiate"Reprotect"fromtheSRMmanagementinterface.
7.
Whenthefailbackprocessiscomplete,ensurethatallMicrosoftExchangeservicesarestartedandthedatabasesaremounted.
8.
Verifyemailflowanduseraccess.
FailbackstepsEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager60ExchangedatabaserecoverywithReplicationManagerInthissolution,ReplicationManagerisusedtoautomateRecoverPointapplication-consistentreplicasandtoperformExchangeServer2010logtruncation.
WithExchange2010,ReplicationManagerallowsyoutorestoreasingledatabasewithorwithoutitslogvolume.
Thisoptionappliesonlyifyouhaveisolatedthedatabasefromitslogsbyplacingthemonseparatedevicesorvolumes.
Figure31showstheRMrestoreoptionsforoneMailboxserverinthecontextoftheRestoreWizard.
Youcanselectanyapplication-consistentbookmark(snapshot)fromalocalorremotecopy,andthenselectspecificdatabasesforrecovery.
Ifpoint-in-timerecoveryisrequiredforabookmarkotherthanthosecreatedbyRMjobs,usetheRecoverPointConsoleinstead.
ForadditionalinformationonusingReplicationManagerwithExchange2010,refertotheReplicationManagerProductGuideandEMCReplicationManagerSupportforMicrosoftExchange2010TechnicalNoteavailableonEMCPowerlink.
Figure31.
ReplicationManagerrestoreoptionsforExchange2010Restoreoptions61EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerBeforeExchangecanberestored,youmustchangethepolicyoptionfortheRecoverPointconsistencygroupfrom"GroupismanagedbySRM…"to"Groupisinmaintenancemode.
.
.
"Figure32showstheRecoverPointconsistencygrouppolicyoptions.
Figure32.
RecoverPointconsistencygrouppolicyoptionsConsistencygrouprestoreoptionsEMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManager62ConclusionTheEMCProtectionforMicrosoftExchangeServer2010solutionisanExchangebusinesscontinuitysolutiondesignedforenterpriseswithtwoormoreactivedatacentersatdifferentgeographiclocations.
Thesolutionoffershighavailabilityateverylocationandnear-instantaneousrecoveryfromadisasteratanylocation.
ThesolutionusesEMCVNX5700storagewiththeVNXTotalProtectionPack(EMCRecoverPoint,EMCReplicationManager,andEMCDataProtectionAdvisor)andVMwarevSphere5withvCenterSiteRecoveryManager(SRM)5.
TheEMCProtectionforMicrosoftExchangeServer2010solutiondemonstratesthereplicationandactivationofanentireExchangeServer2010DatabaseAvailabilityGroup(DAG)anditsassociatedExchangevirtualmachinesacrossaWANbetweenmultiple,active/activedatacenters.
Thesolutioncanhelpachievethemostambitiousrecoverypointobjectives(RPO),recoverytimeobjectives(RTO),andtotalcostofownership(TCO)goals.
Specifically,thesolutiondemonstratestheadvantagesofdeployingExchangeon:EMCVNXseriesstorageVMwarevSphereplatformFurther,thesolutiondemonstratesvariousprotectionoptionsforamulti-site,active/activeExchangedeployment:HighavailabilityatallsitesBackupandrestoreatanysiteRecoveryfromadisasteratanysiteRigoroustestingofthissolutionachievedthefollowingresults:Eachsiteprovidedenoughperformanceandcapacitytosupportupto20,000activeusers(10,000usersduringnormaloperationsandanother10,000usersduringadisasterrecoveryevent).
RecoveryforallfourMailboxserverscompletedinjust25minuteswithSRM.
RTOoflessthanonehourwasachievedduringsitefailovertestingwithSRM.
SummaryFindings63EMCProtectionForMicrosoftExchangeServer2010EMCVNX5700,EMCRecoverPoint,EMCReplicationManager,EMCDataProtectionAdvisor,VMwarevSphere,andVMwarevCenterSiteRecoveryManagerReferencesIfyoudonothaveaccesstohttp://powerlink.
emc.
com,contactyourEMCrepresentative.
EMCandVMwarewhitepapers:EMCReplicationManagerandEMCRecoverPoint(http://www.
emc.
com)ReplicationManagerSupportforExchange2010TechnicalNotes(http://powerlink.
emc.
com)EMCRecoverPointStorageReplicationAdapterforVMwareSiteRecoveryManagerVersion2.
0ReleaseNotes(http://powerlink.
emc.
com)MicrosoftExchange2010onVMwareBestPracticesGuide(http://www.
vmware.
com)MicrosoftExchange2010:StorageBestPracticesandDesignGuidanceforEMCStorage(http://www.
emc.
com)EMCReplicationManagerSupportforMicrosoftExchange2010TechnicalNotes(http://powerlink.
emc.
com)EMCandVMwareproductdocumentation:EMCVNXSeriesUnifiedStorageSystemsSpecificationSheet(http://www.
emc.
com)EMCReplicationManagerProductGuide(http://powerlink.
emc.
com)EMCRecoverPointAdministrator'sGuide(http://powerlink.
emc.
com)VMwarevCenterSiteRecoveryManagerAdministrationGuide5.
0(http://www.
vmware.
com)MicrosoftTechNetarticles:ExchangeServer2010deploymentsforhighavailabilityandsiteresiliency,http://technet.
microsoft.
com/en-us/library/dd638121.
aspxMicrosoftguidelinesconsideredforthissolution'sdesign,http://technet.
microsoft.
com/en-us/library/ee712771.
aspxExchangedatabasecorruptiontypesandlaggedcopylimitations,http://technet.
microsoft.
com/en-us/library/dd335158.
aspxLoadGen,http://technet.
microsoft.
com/en-us/library/dd335108.
aspxConfiguringExchange2010DAGsandallunderlyingclusterandActiveDirectorycomponents,http://technet.
microsoft.
com/en-us/library/dd638215.
aspxandhttp://technet.
microsoft.
com/en-us/library/dd297985.
aspxUnderstandingActiveManager,http://technet.
microsoft.
com/en-us/library/dd776123.
aspxWhitepapersProductdocumentationOtherdocumentation