太太药业SAP备份及恢复流程.docx

太太药业SAP备份及恢复流程.docx

《太太药业SAP备份及恢复流程.docx》由会员分享，可在线阅读，更多相关《太太药业SAP备份及恢复流程.docx（27页珍藏版）》请在冰豆网上搜索。

太太药业SAP备份及恢复流程

SAP备份及恢复流程

Author:

陶朝晖

Date:

May.23,2002

Version:

1.0

Content

Purpose3

BackupStrategy3

BackupTool3

BackupDevice3

BackupContents3

BackupScheme4

TapeStorage5

Therearetwowaystocheckstatusofbackup5

RecoveryStrategy6

RestoreTool6

RestoreDevice6

RestoreContents6

RecoveryScheme6

CompleteRecovery6

IncompleteRecovery8

Specialcases10

Appendix13

I.StepsofSAPArchive13

II.StepsofSAPOnlineBackup14

III.StepsofSAPOfflineBackup16

IV.DailyRecorderReport18

V.Contentsintape19

VI.Tapemanagement21

VII.StructureChanges（ControlFiles）23

VIII.ORA-01149orORA-01113formissing"endbackup"24

Purpose

Thisdocumentdefinesthebackuppolicytoensureregular,correctbackupproceduresarecarriedoutanddataintegrityiskept.

Thisdocumentdescribesbackupstrategy.Intheeventoflossofdataoccurring,thesystemcanthereforeberestoredasquicklyandasfullyaspossible.

Thisdocumentalsodefinestherecoveryprocedurestoensuresystemwouldbeupasquicklyandasfullyaspossibleincaseofsystemdown.

BackupStrategy

Therecommendedmethodistapebackup.

BackupTool

•UsingtheDBAPlanningCalendar（transactionDB13）

•UsingtheSAPdatabaseadministrationtoolSAPDBAatoperatingsystemlevel

•Directly,attheoperatingsystemlevel（brarchive/brbackup,tar/dump）

•Usinghpbackuptoolsomni.

BackupDevice

Tapedriver:

24GBDLT

BackupContents

∙DataFiles

∙Controlfiles

∙Profiles

∙Onlineredologfiles

∙Offlineredologfiles

∙Operatingsystemfiles

TapeNameConventionandInitialization

⏹Tapeusedforbrbackuparealwaysnamedasfollows,

B01,B02,B03,B04,B05,B06,

Tapeusedforbrarchivearealwaysnamedasfollows,

A01,A02,A03,A04A05,A06,

⏹Performthetapeinitializationprocedureasfollows:

•Settheinit.sapparametersvolume_backupandvolume_archive.Inthisexample:

volume_backup=（B01,B02,B03,B04）

volume_archive=（A01,A02,A03,A04）

•Toinitializethetapepools,useSAPDBAorBRBACKUPandBRARCHIVEwithcalloption-iforce（where-i=initializeandforce=donotevaluatetapelabel）.

•Inthisexample,tapelabelsB01,B02,B03,B04andA01,A02,A03,A04areinitialized.

⏹Tooverwritethedefaultsettingsdefinedinvolume_backuporvolume_archive,useBRBACKUPandBRARCHIVEwithcalloption-v/-volume.

BackupScheme

Thebackupschemeshouldguaranteethatproductiondataberecoveredwithinadayanddevelopmentdataberecoveredwithinsixdaysafteradisaster.

Asystematicapproachofmaintainingbackupsonadaily,weekly,andmonthlybasisisstronglyrecommended:

∙ThefirstbackupisalwaysaFullbackup.

∙Daily:

PRD:

OnlineBackup（nighttime）+Redologarchive（daytime）

Othersystem:

Redologarchive（daytime）

∙Weekly:

OfflineBackup

∙Monthly:

UnixlevelBackup

Ifitisinfollowingcases,backupunderunixlevelmustbecarriedout,

∙R/3releaseupgrade

∙Kernelupgrade

∙Oracleupgrade

∙OSupgrade

Allbackupsshouldbescheduledduringofftime,e.g.atthenightofeachdayoratweekend.TheadministratorshouldSTICKTOthescheme.Occasionally,theadministratorwillhavetoscheduletheschemetorunwhennoonewillbearoundtoinsertthecorrectmediaintothetapedrive,forexample,onholidays.Itisrecommendedthattheadministratorchangetheschemesothathe/shehasacurrentfullbackupofthesetbeforethescheduledclosing,thenshutoffbackupforthatday.Whenhereturns,hecanreverttothestandardset-upforthatset.

Theadministratorshouldemployappropriatetapestoensuretheywillholdalldataneedingbackup.AlltapesshouldbelabeledwithcertainSAPnamingconventionwhichwillreflectsBackuptypeandDate.Oncetheadministratorhavesetuptherotationscheme,heneedtomakesuretherightmediaisinthetapedriveforeachdayoftheweek.

Theadministratorshouldcheckbackuplogsafterbackupcomplete.Logsareveryimportantinassuringdataintegrity.Iftheadministratorneedstorestoredatainadisastersituation,he’llhaveareferencefromwhichtostart.

TapeStorage

Threegroupsoftapemediashouldbestoredseparatelyinappropriateplace.Atapeshouldnotberotatedexceedingtheguaranteedlifetime.Foradditionalsecurity,themonthlytapesandIdfloppycopiesshouldbeplacedinafireproofsafeandstoredoff-site（Awayfromcomputerroom）.

VerificationandFailedBackups

Afterthebackuphasrun,backedupfilesshouldbeverifiedagainsttheoriginals.Toverifyboththedatatobebackedupaswellasthedatabasebackups,thefollowingtwowayscheckshouldbeused,

∙PerformalogicaldatachecktoverifytheconsistencyoftheOracledatabaseandvoidoracleblockscorrupted.Foroptimalperformance,performthischeckduringperiodsoflowsystemactivity,suchasweekends.Thestatementusedforcheckingis

sapdba-check

∙Performaphysicaldatachecktoverifythetapesusedforadatabasebackup.Tocheckthephysicalcorrectnessofthedatatransferred,readthetapesafterasuccessfulbackuponceaquarter.

Ifabackupfails,theexplanationneedstobefoundandtheproblemremediedbeforethenextbackup.Inanycase,thebackuplogshouldbeexamined.Aproblemmayhavearisenwiththebackupmedium,thebackupsoftwareorthesystemitself.Theadministratorshouldcheckeverydaythatallbackupshaverunsuccessfully.

Therearetwowaystocheckstatusofbackup

∙UsingtheDBAPlanningCalendar（transactionDB13）

∙UsingtheLoginfoOverview（transactionDB24）

RecoveryStrategy

Inthischapter,weonlytalkaboutrecoveryforSAPData（DatabaseDataFiles）.

RestoreTool

•UsingtheSAPdatabaseadministrationtoolSAPDBAatoperatingsystemlevel

•Directly,attheoperatingsystemlevel（brarchive/brbackup,tar/dump）

RestoreDevice

Tapedriver:

40-80GBDLT

RestoreContents

∙DataFiles

∙Controlfiles

∙Profiles

∙Onlineredologfiles

∙Offlineredologfiles

∙Operatingsystemfiles

RecoveryScheme

Thebackupschemeshouldguaranteethatproductiondataberecoveredwithinadayanddevelopmentdataberecoveredwithintwodaysafteradisaster.

CompleteRecovery

Generalflow

1.sqldbalmode=y

SQLDBA>SHUTDOWN[NORMAL|IMMEDIATE|ABORT]

SQLDBA>EXIT

2.MakeanOFFLINEbackupofthewholeDB,butatleastofthecurrentcontrolfileandthoseonlineredo-logfileswhichwerenotyetarchived（seeV$LOG）incasetherecoverywillhavetoberepeated!

3.Restoreonlythedefectivedatafilesfromthelastbackup（whetherONLINEorOFFLINEbackup）.Fortheresult,itisofnoimportanceifallthedatafilesarerestored,butrestoringandrecoveringsinglefilesisfaster.

（Iftherewerestructurechangessincethelastbackupwhichaffectthedefectivefiles,youmustusethelastbackupsAFTERthestructurechanges!

Pleaserefertoappendix）

4.sqldbalmode=y

SQLDBA>CONNECTINTERNAL

SQLDBA>STARTUPMOUNT

SQLDBA>ALTERDATABASECREATEDATAFILE''（withpath）

[AS''][SIZE];

Createallthefilesforwhichnobackupexists,butonlyifalltheredo-log-filessincefilegenerationexistandiftherehasbeenno"CREATECONTROLFILE"sincethen（->ORA-01178）.The"AS"optioncanbeusedifthenewfileshouldalsoberenamed,"SIZE",ifthefilesizewaschanged.

SQLDBA>SELECTNAMEFROMV$DATAFILEWHERESTATUSIN（'OFFLINE','SYSOFF'）;

SQLDBA>ALTERDATABASEDATAFILE''ONLINE;（withpath）

SetallpreviouslyselecteddatafilesONLINE!

SQLDBA>RECOVERDATABASE[USINGBACKUPCONTROLFILE];

Provideredo-log-files（ifneeded）andconfirmthemwithuntil"Mediarecoverycomplete."

isreported.

"USINGBACKUPCONTROLFILE"isnecessaryifabackupofthecontrolfileshouldbereloadedorif

"CREATECONTROLFILE"wasexecutedwithoption"RESETLOGS".

Generally,"CREATECONTROLFILE"willbeexecutedwith"NORESETLOGS"

（specialcase:

e.g.changedb_name,seeORACLEdocu.）.

SQLDBA>ALTERDATABASEOPEN[RESETLOGS];

"RESETLOGS"isnecessaryafter"USINGBACKUPCONTROLFILE".

SQLDBA>EXIT

TheDBisnowcompletelyrecreated.

IftheDBwasopenedwith"RESETLOGS",youmustshutitdownatonceandmakeacompleteOFFLINEbackupinordertobeabletorestoreandrecoverinthefutureaswell.

IncompleteRecovery

Thefollowing3optionsareavailableforanincompleterecovery:

-uptoaparticulardateandtime（"UNTILTIME"）

-uptoaparticularSCN='systemchangenumber'（"UNTILCHANGE"）

-uptoaparticularredologfile（"UNTILCANCEL"）

CAUTION:

Ifyouwanttoperformanotherrecovery（i.e.importredologfiles）aftertherestore（restoredatabasebackup）,youmayNOTOPENthedatabaseuntilyouhaveimportedalltheredologfilesrequired;seenumber4furtherbelow.

GeneralProcedure:

-------------------

1.sqldbalmode=y

SQLDBA>SHUTDOWN[NORMAL|IMMEDIATE|ABORT]

SQLDBA>EXIT

2.PerformanOFFLINEbackupoftheentiredatabase.Atleastsavethecurrentcontrolfilesandthenotarchivedonlineredologfiles（seeV$LOG）,incasetherecoveryneedstoberepeated!

3.Reloadallthebacked-updatafilesoftheentireDB（restore）.

-Alsoreloadundamagedfiles.AlldatafilesmusthavebeensavedBEFOREtherecover-untiltime!

-Exception:

UndamageddatafilesneedNOTbereloaded,ifdespite

choosingtheoption"UNTIL"thedatabaseistoberecoveredtothe

end,thatistoitscurrentstate.

（e.g.WhenUNTILonlyservesthepurposeofenablingthedatabase

tobereopenedwithRESETLOGSaftertherecovery.）

-Fortherecoveryitisinsignifican