Recovery Manager ArchitectureWord文档下载推荐.docx
- 文档编号:3011650
- 上传时间:2023-05-01
- 格式:DOCX
- 页数:13
- 大小:21.54KB
Recovery Manager ArchitectureWord文档下载推荐.docx
《Recovery Manager ArchitectureWord文档下载推荐.docx》由会员分享,可在线阅读,更多相关《Recovery Manager ArchitectureWord文档下载推荐.docx(13页珍藏版)》请在冰点文库上搜索。
1-1listspossiblecomponentsoftheRMANenvironment.
Table1-1ComponentsoftheRMANEnvironment
Component
Description
Required?
Targetdatabase
Thecontrolfiles,datafiles,andoptionalarchivedredologsthatRMANisinchargeofbackinguporrestoring.RMANusesthetargetdatabasecontrolfiletogathermetadataaboutthetargetdatabaseandtostoreinformationaboutitsownoperations.Theworkofbackupandrecoveryisperformedbyserversessionsrunningonthetargetdatabase.
Yes
RMANclient
Theclientapplicationthatmanagesbackupandrecoveryoperationsforatargetdatabase.TheRMANclientcanuseOracleNettoconnecttoatargetdatabase,soitcanbelocatedonanyhostthatisconnectedtothetargethostthroughOracleNet.
Recoverycatalogdatabase
Adatabasecontainingtherecoverycatalogschema,whichcontainsthemetadatathatRMANusestoperformitsbackupandrecoveryoperations.
No
Recoverycatalogschema
TheuserwithintherecoverycatalogdatabasethatownsthemetadatatablesmaintainedbyRMAN.RMANperiodicallypropagatesmetadatafromthetargetdatabasecontrolfileintotherecoverycatalog.
Standbydatabase
Acopyoftheprimarydatabasethatisupdatedusingarchivedlogscreatedbytheprimarydatabase.RMANcancreateorbackupastandbydatabase.Youcanfailovertothestandbydatabaseiftheprimarydatabasegoesdown.
Duplicatedatabase
Acopyoftheprimarydatabasethatyoucanusefortestingpurposes.
Mediamanagementapplication
Avendor-specificapplicationthatallowsRMANtobackuptoastoragesystemsuchastape.
Mediamanagementcatalog
Avendor-specificrepositoryofinformationaboutamediamanagementapplication.
EnterpriseManager
Abrowser-basedinterfacetotheOracledatabase,includingbackupandrecoverythroughRMAN.
TheonlyrequiredcomponentsinanRMANenvironmentarethetargetdatabaseandtheRMANclient,butmostreal-worldconfigurationsaremorecomplicated.OnemightuseanRMANclientconnectingtomultiplemediamanagersandmultipletarget,recoverycatalog,andauxiliarydatabases,allaccessedthroughEnterpriseManager.
RMANSessionArchitecture
TheRMANclientapplicationdirectsdatabaseserversessionstoperformallbackupandrecoverytasks.Themeaningof"
session"
inthissensedependsontheoperatingsystem.Forexample,onUNIX,aserversessioncorrespondstoaserverprocess,whileonWindowsitcorrespondstoathreadwithinthedatabaseservice.
TheRMANclientitselfdoesnotperformbackup,restore,orrecoveryoperations.WhenyouconnecttheRMANclienttoatargetdatabase,RMANallocatesserversessionsonthetargetinstanceanddirectsthemtoperformtheoperations.TheRMANclientusesinternal,undocumentedPL/SQLpackagestocommunicatewiththetargetdatabaseandrecoverycatalog.
RMANCommandLineClient
UsetheRMANcommandlineclienttoentercommandsthatyoucanusetomanageallaspectsofbackupandrecoveryoperations.
EvenwhenyouusethebackupandrecoveryfeaturesinEnterpriseManagerthatarebuiltontopofRMAN,anRMANclientexecutesbehindthescenes.
Note:
AllRMANcommandsforOraclerelease8.1andhigheralsoworkinOracleDatabseRelease10g.
HowRMANCompilesandExecutesCommands
RMANprocessesmostcommandsinthetwophasesdiscussedinthissection:
CompilationPhase
Duringthecompilationphase,RMANdetermineswhichobjectsthecommandwillaccess(forexample,resolvingatablespacenameintoitscomponentdatafiles).Then,RMANconstructsasequenceofremoteprocedurecalls(RPCs)thatinstructtheserversessionsonthetargetdatabasetoperformthedesiredoperation.
ExecutionPhase
Duringtheexecutionphase,RMANsendstheRPCcallstothetargetdatabase,monitorstheirprogress,andcollectstheresults.Ifmorethanonechannelisallocated,thenRMANcanexecutecertaincommandsinparallelsothatallofthechannels'
targetdatabasesessionsareconcurrentlyexecutinganRPCcall.
IssuingRMANCommands
RMANusesacommandlanguageinterpreter(CLI)thatcanexecutecommandsininteractiveorbatchmode.
EnteringCommandsattheRMANPrompt
TorunRMANcommandsinteractively,startRMANandthentypecommandsintothecommand-lineinterface.Forexample,youcanstartRMANfromtheUNIXcommandshellandthenexecuteinteractivecommandsasfollows:
%rmanTARGETSYS/oracle@trgtCATALOGrman/cat@catdb
AftertheRMANpromptisdisplayed,youcanentercommandssuchasthefollowing:
RMAN>
BACKUPDATABASE;
UsingRMANwithCommandFiles
AcommandfileisatextfilewhichcontainsRMANcommandsasyouwouldenterthematthecommandline.Youcanruntheacommandfilebyspecifyingitsnameonthecommandline.Thecontentsofthecommandfilewillbeinterpretedasifenteredatthecommandline.IftheLOGcommandlineargumentisspecified,RMANdirectsoutputtothenamedlogfile.Commandfilesareonewaytoautomatescheduledbackupsthroughanoperatingsystemjobcontrolfacility.
Inthisexample,asampleRMANscriptisplacedintoacommandfilecalledcommandfile.rcv.Youcanrunthisfilefromtheoperatingsystemcommandlineandwritetheoutputintothelogfileoutfile.txtasfollows:
%rmanTARGET/CATALOGrman/cat@catdbCMDFILEcommandfile.rcvLOGoutfile.txt
SeeAlso:
OracleDatabaseRecoveryManagerReferenceformoreinformationaboutRMANcommandlineoptions
StoredScripts
AstoredscriptisablockofRMANjobcommandsthatisstoredintherecoverycatalog.Bystoringscriptsintherecoverycatalog,thescriptisavailabletoanyRMANclientthatconnectstothecatalogandthetargetdatabase.Storedscriptscanbeassociatedwithasingledatabaseinthecatalog,ortheycanbeglobalstoredscripts,whichcanbeexecutedagainstanytargetdatabaseinthecatalog.
"
WorkingwithRMANStoredScriptsintheRecoveryCatalog"
formoreonstoredscripts.Alsorefertothesamplescriptsinthe?
/rdbms/demodirectory.
CommandsValidOnlyinRUNBlocks
ThereareRMANcommandswhichareonlyvalidinRUNblocks.ThesetypicallyinvolvesettinguptheenvironmentwithinwhichthestatementsintheRUNblockwillexecute.TypicalofthisgroupareALLOCATECHANNELandSETNEWNAMEFORDATAFILE.UsingthesecommandsoutsideofaRUNblockwillgenerateanerror.
ThesyntaxdiagramsfortheRUNcommandinOracleDatabaseRecoveryManagerReferenceregardingwhichcommandsarevalidinRUNblocks
CommandsNotValidinRUNBlocks
ThereareanumberofRMANcommandswhichcannotbeusedinRUNblocks.TypicallytheseareusedtocontroltheRMANenvironment(connectingtodifferentdatabases,orconfiguringRMANdefaults),ortomanageorquerytherecoverycatalog(includingcreatingandusingstoredscripts).Herearesomeexamples:
∙CONNECT
∙CONFIGURE
∙CREATECATALOG,DROPCATALOG,UPGRADECATALOG
∙CREATESCRIPT,DELETESCRIPT,REPLACESCRIPT
∙LIST
∙REPORT
Youcanincludethesecommandsinsidecommandfiles,aslongastheyarenotwrappedinsideaRUNblock.Youcannotusetheminsideastoredscriptfromtherecoverycatalog,becausethecontentsofastoredscriptareexecutedwithinaRUNblock.
ControllingRMANOutput
WhenyourunRMANincommandlinemode,itsendstheoutputtotheterminal.IfyouspecifytheLOGoption,thenRMANwritestheoutputtoaspecifiedlogfileinstead.
OutputforcurrentlyexecutingRMANjobsisalsostoredintheV$RMAN_OUTPUTview,whichreadsonlyfrommemory(thatis,theinformationisnotstoredinthecontrolfile).TheV$RMAN_STATUSviewstoresmetadataaboutjobsinprogressaswellascompletedjobs.Themetadataforcompletedjobsisstoredinthecontrolfile.
RMANPipeInterface
TheRMANpipeinterfaceisanalternativemethodforissuingcommandstoRMANandreceivingtheoutputfromthosecommands.Withthisinterface,RMANobtainscommandsandsendsoutputbyusingtheDBMS_PIPEPL/SQLpackage.RMANdoesnotreadorwriteanydatausingtheoperatingsystemshell.Byusingthisinterface,itispossibletowriteaportableprogrammaticinterfacetoRMAN.
ThepipeinterfaceisinvokedbyusingthePIPEcommand-lineparameter.RMANusestwoprivatepipes:
oneforreceivingcommandsandtheotherforsendingoutput.ThenamesofthepipesarederivedfromthevalueofthePIPEparameter.Forexample,youcaninvokeRMANwiththefollowingcommand:
%rmanPIPEabcTARGETSYS/oracle@trgt
RMANopensthetwopipesinthetargetdatabase:
ORA$RMAN_ABC_IN,whichRMANusestoreceiveusercommands,andORA$RMAN_ABC_OUT,whichRMANusestosendalloutputbacktoRMAN.
AllmessagesonboththeinputandoutputpipesareoftypeVARCHAR2.
NotethatRMANdoesnotpermitthepipeinterfacetobeusedwithpublicpipes,becausetheyareapotentialsecurityproblem.Withapublicpipe,anyuserwhoknowsthenameofthepipecansendcommandstoRMANandinterceptitsoutput.
ExecutingRMANCommandsThroughaPipe"
tolearnhowtoexecuteRMANcommandsthroughapipe
RMANRepository
TheRMANrepositoryis
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- Recovery Manager Architecture