Data Protection and Disaster Recovery Tips.pdf

Contents

Data Protection and Disaster Recovery Tips

Chapter1:DisasterPreparednessandYou. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

byPaulRobichaux

6CommonBackupandRestoreMistakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

UsingtheWrongBackupMethod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

NotVerifyingBackups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

MismanagingtheTransactionLogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

NotAllowingEnoughTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

ForgettingtheSmallStuff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

NotPracticing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

SpendTime,NotMoney. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

sidebar:SettingUpaSecureOffsiteBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter2:RecoveringfromanExchangeServerCrash. . . . . . . . . . . . . . . . . . . . . 7

byAlanSugano

sidebar:TaketheFirstSteptoaCompleteDRSolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter3:RecoveringfromanExchangeServerCrash. . . . . . . . . . . . . . . . . . . . . 11

Buildasolutionwithascript,asecondaryenvironment,andafile-restorestrategy

byBrianWilanskyandJeffSandler

RestorefromaBackupEnvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

ToolOptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

PortalServerBackupProcedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

RestoreStrategies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

AdditionalApproaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

NotPerfect,ButanImprovement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

sidebar:SolutionsSnapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

ii Data Protection and Disaster Recovery Tips

Chapter4:ExchangeDisasterRecoveryTips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

byMenkodenOuden

Tip1:AssessRequiredServiceLevels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Tip2:CreateaDisasterRecoveryInformationKit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Tip3:BackUptheClusterQuorumDisk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

PrepareNow;MinimizeStressLater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Tip4:IncludeADinYourRecoveryPlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Tip5:“BackUp”YourExchangeExpert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Tip6:UsetheExchangeDisasterRecoveryAnalyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter5:PuttingTogetherYourHigh-AvailabilityPuzzle. . . . . . . . . . . . . . . . . . 21

Improvesystem,database,anddataavailabilitywithSQLServer2005

byKalenDelaneyandRonTalmage

FailoverClustering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Servervs.DataRedundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

DatabaseMirroring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

MirroringRestrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

LogShipping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

MergeReplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

TransactionalReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Peer-to-PeerTransactionalReplication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

AvailabilityinaHighlyConcurrentEnvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

SnapshotIsolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

OnlineIndexCreation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

FasterRestoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

DatabaseSnapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

FinalWords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter :

Disaster Preparedness and You

ByPaulRobichaux

I’mwritingthiscolumnfromNice,France,whichisabeautifulcity.And,sofar,noonehaslaughed

atmyattemptstodustoffmyrustycollegeFrench.However,whatshouldhavebeenaperfecttriphas

beenhauntedbytheghostofdisasters,bothpastandfuture.

First,thepast.Nottoolongago,the100thanniversaryofthegreatSanFranciscoearthquakeof

1906rolledaround.SanFranciscoanditssurroundingareawereuniquelyvulnerabletothisearthquake

becauseofavarietyoffactors,includingprevailingconstructionmethods,soilcomposition,andthelack

ofeffectivefirefightingcapability.Asyouprobablyknow,thefaultsystemsthatunderlietheBayArea

(andtheircompanionfaultsinthePugetSoundarea)areoverdueforamajorearthquake,andthat’s

worrisome.

Second,I’vebeenreadingascarybook,“FiftyDegreesBelowZero,”inwhichsciencefiction

authorKimStanleyRobinsondescribessomeofthepossibleoutcomesofabruptclimatechange.

ThoseoutcomesincludedestructiveweathereventsthatarepracticallyBiblicalinscale,alongwith

desperateeffortstomitigatetheclimatechangeandretooltheeconomy.Whetherornotyouagreethat

globalwarmingisreal,thehistoricalrecordofabruptclimatechange—andthelastingaftereffects—is

abundantlyclear.

Thesetwothingshavelittleincommonexceptthis:Bothpointouttheneedforeffectivedisaster

recoveryforyourExchangeorganization,and“effective”inthiscontextimplieseffectiveandaccurate

preparation.Ashurricaneseasonapproaches,therearelotsofnervousfolksalongtheGulfCoast,in

Florida,andalongtheeasternseaboardoftheUnitedStates,butthey’realreadypreparing.Whatabout

yourownorganization?

Idon’thavespaceheretolisteverystepyoumightconceivablytaketoprotectyourExchange

organization,butIcanpointoutafewhigh-valuethingsthatyoushouldbesuretoincludeinyour

planning:

1.Haveabug-outplan.Ifadisasterhityourbusiness,howwouldyougetawayfromthearea?

Howwouldyoudecidewhenitwastimetogo?Howwouldyoutellyouremployeesnottocome

towork?Infact,howwouldyoumakethedecisiontoshutdownorrelocateoperations?

2.Keepcommunicating.Howwouldmanagementandemployeescommunicateuntilyour

emailservicecouldbereestablished?Who’sinchargeofestablishingandmaintainingdisaster

communications?

3.Grabyourgearandgo.Oneofmycustomersimplementeditsdisasterrecoveryplanfor

HurricaneKatrinabyshuttingdowntheExchangeserver,pullingallthedisksfromthestorage

enclosure,andtakingthembycartoHouston.Thiswasaningeniousandeffectivesolution,

giventhecircumstances.Whatwouldyoudoundersimilarcircumstances?

4.Nowisalwaysbetterthanlater.It’sbettertohaveafairsolutionnowthanaperfectsolution

Brought to you by CA and Windows IT Pro eBooks

Data Protection and Disaster Recovery Tips

later.Ofcourse,thisdoesn’tmeanthatyoushouldrushoutandslaptogetheradisaster-

preparednessstrategyoutofwhateverrandomproductsandtechnologiesyoucanfind.It

does,however,meanthatyoushouldpushdisasterrecoveryandpreparednessplanningtothe

forefrontofyourlistofoperationalconcerns.

It’snotpossibletoanticipateeverypossibledisaster,butyoudon’thaveto.Theresponsestomany

disasterswillbethesame;youcanmakeplansbasedontheexpecteddurationofrecovery,theimpact

ofthedisasteronyourfacilitiesandthesurroundingarea,andotherfactors.Evenifyoudon’tliveina

disaster-pronearea(Idon’t;thebiggestthreatinnorthwestOhioisapparentlyhighwayconstruction),

youshouldstillbepreparedforthingssuchasstructurefires,majortrafficaccidents(whatifagasoline

tankerblewupnearby?Thathappenedatmywedding!),andsoon.

TheBoyScoutssay“Beprepared,”butIliketheUSCoastGuard’smottobetter:“SemperParatus,”

whichisLatinfor“alwaysready.”

6 Common Backup and Restore Mistakes

ByPaulRobichaux

Nothingcompareswiththesinkingfeelingyouexperiencewhenyouneedtorestoredatafroma

backupbutcan’tforsomereason.Mostcomputerusershavethisexperienceeventually;thepainis

evenmoreacuteandfrequentforadministrators,whoareresponsibleforlargeamountsofimportant

businessdata.Althoughbackupandrestoretechnologieshaveadvancedinthepastfewyears,you

probablystillusethemonlyaslast-ditchsafetymechanisms.Whenallelsefails,youtrytorestorefrom

backup.Forthisalternativetobeviable,youmusthaveadegreeofconfidencethatyourdatawillbe

availableandreadablewhenyouneedit.However,Exchangeadministratorsmakeseveralcommon

mistakesthatpreventtheirbackupandrecoveryoperationsfromrunningsmoothly.

#1:UsingtheWrongBackupMethod

ThetwobasicmethodsforbackingupExchangedataare online and offline .Onlinebackupsusea

Microsoftinterface(suchasExtensibleStorageEngine—ESE,backupAPIs,orMicrosoftVolume

ShadowCopyService—VSS)tocopytheselectedExchangedatawhiletheExchangeservicesare

runningandwhilethetargetdatabaseismountedandactive.TheExchange-providedAPIsbackup

transactionlogsandtruncatethelogswhennecessary.

OfflinebackupscopytheExchangedatabaseandlogfileswhilethedatabaseisn’tmounted.Some

solutionspurporttocopyExchangedatawithoutusingMicrosoft’sAPIsbutalsowithoutdismounting

thedatabases.TheMicrosoftarticle“XADM:HotSplitSnapshotBackupsofExchange”(http://support.

microsoft.com/?kbid=311898)explainsthatMicrosoftconsidersthesebackupstobeoffline.

Performingonlinebackupsispreferablefortypicalproductionoperationsbecauseonlinebackups

captureaconsistentcopyoftheExchangedatabaseswithoutinterruptinguseraccess.However,offline

backupsareusefulinsomesituations.Forexample,performingacompleteofflinebackupofyour

ExchangedatabaseandlogsisagoodideabeforeinstallingaWindowsoranExchangeservicepackor

performingaforkliftupgradeofthedatabasetoanotherserver.Althoughcreatingofflinebackupsis

Brought to you by CA and Windows IT Pro eBooks

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: