EMC TimeFinder and SRDF

Page 1
EMCTimeFinderandSRDF
BestPracticesforOracleDatabase10gAutomatic
StorageManagementSymmetrixDMX
Page 2
Abstract:Thepurposeofthisdocumentistoprovideacomprehensivesetofbestpracticesand
procedureswhendeployingOracleDatabase10gandtheAutomaticStorageManagement(ASM)feature
withEMCSymmetrixstoragebasedreplicationtechnologies.
Page 3
2/5/2006
2
TableofContents
Introduction.........................................................................................................3
RelatedDocuments............................................................................................3
OracleAutomaticStorageManagement...........................................................3
OracleRecoveryManager(RMAN)....................................................................4
OracleFlashRecoveryArea..............................................................................4
EMCConsistencyTechnology...........................................................................4
EMCTimeFinderOverview.................................................................................4
TimeFinderConsistentSplit..............................................................................5
EMCSRDFOverview..........................................................................................5
SRDFProtectionModes..............................................................................................................6
SRDFSynchronousMode.....................................................................................................6
SRDFAsynchronousMode...................................................................................................6
DisasterRestartandDisasterRecovery...........................................................6
RebalancingandConsistencyTechnology..................................................................................7
TestCasesandBestPractices..........................................................................7
GeneralTestsConfiguration........................................................................................................7
Hardware.................................................................................................................................8
ASMDiskGroups/MountPoints.........................................................................................8
ASMInstanceParameterFile..............................................................................................10
DatabaseInstanceParameterFile......................................................................................10
Case1:OracleDatabase10gHotBackupwithTimeFinder/Mirror...........................................10
Case2:DatabaseCloningwithTimeFinder/Mirror....................................................................13
Case3:RemoteDatabaseCloningwithTimeFinder/MirrorandSRDF....................................14
Case4:OracleDatabase10gHotBackupwithTimeFinder/MirrorandSRDF.........................16
Case5:RestoringaDatabaseontheProductionHost.............................................................20
Page 4
2/5/2006
3
Introduction
Thepurposeofthisdocumentistoprovideacomprehensivesetofbestpracticesandprocedureswhen
deployingOracleDatabase10gandAutomaticStorageManagement(ASM)withEMCSymmetrix
storage
basedreplicationandConsistencyTechnologies.ThisincludesEMCTimeFinder/Mirrorand
Symmetrix
RemoteDataFacility(SRDFAsynchronousandSynchronous),whichhavebeenvalidatedin
accordance
withtheOraclesStorageCompatibilityProgram(OSCP)already,andnowbeingextendedtoinclude
validationwhenusingOracleDatabase10gAutomaticStorageManagement.
Thispaperwilldocumenttheproceduresandbestpracticesforthefollowingusecases:
OracleDatabase10gHotBackupwithTimeFinder/MirrorforDatabaseBackup

TimeFinder/MirrorforDatabaseCloning
SRDFandTimeFinder/MirrorforDRandRemoteDatabaseCloning
OracleDatabase10gHotBackupwithSRDFandTimeFinder/MirrorforDRandRemote
DatabaseBackup
ThisdocumentassumesthereaderhasabasicunderstandingofOracleDatabase10gAutomatic
Storage
ManagementandEMCTimeFinder/MirrorandSRDFtechnologies.
RelatedDocuments
UsingOracle10gsAutomaticStorageManagementwithEMCStorageTechnology
UsingSYMCLItoPerformConsistentSplitswiththeTimeFinderProductFamily.
UnderstandingEMCConsistentSplitwithOracleDatabases
OracleDatabase10gAutomaticStorageManagementBestPractices
OracleAutomaticStorageManagement
AutomaticStorageManagement(ASM)isastoragemanagerthatprovidesfilesystem,volume
managementandclusteringcapabilitiesintegratedintotheOracleDatabase10gatnoadditionalcost.
ASM
lowersyourtotalcostofownership,increasesstorageutilizationwithoutcompromisingperformanceor
availability.WithASM,afractionofthetimeisneededtomanageyourdatabasefiles.
ASMeliminatesoverprovisioningandmaximizesstorageresourceutilizationfacilitatingdatabase
consolidation.TheASMselftuningfeatureevenlydistributesthedatafilesacrossallavailablestorage.
It
delivershighperformancesimilartoraw,sustainedovertime,withtheeaseofuseofafilesystem.
ASMs
intelligentmirroringtechnologyenablesuptotripledataprotection,evenonnonRAIDstoragearrays.
ASMbenefitsare:
Simplifyandautomatestoragemanagement
Increasestorageutilizationandagility
Predictablydeliveronperformanceandavailabilityservicelevelagreements
ASMsimplifiesstoragemanagementtasks,suchascreating/layingoutdatabasesanddiskspace
management.SinceASMallowsdiskmanagementtobedoneusingfamiliarcreate/alter/dropSQL
statements,DBAsdonotneedtolearnanewskillsetormakecrucialdecisionsonprovisioning.
Additionally,ASMoperationscanbecompletelymanagedwith10gEnterpriseManager.ASMisa
managementtoolspecificallybuilttosimplifythejoboftheDBA.Itprovidesasimplestorage
managementinterfaceacrossallserverandstorageplatforms.ASMprovidestheDBAflexibilityto
manageadynamicdatabaseenvironmentwithincreasedefficiency.ThisfeatureisakeyaspectofGrid
Computing.FormoreinformationaboutASM,pleaserefertotheOTNASMhomepage:
http://www.oracle.com/technology/products/database/asm/index.html
Page 5
2/5/2006
4
OracleRecoveryManager(RMAN)
RecoveryManagerisOraclesutilitytomanagethebackup,andmoreimportantlytherecovery,ofthe
database.Iteliminatesoperationalcomplexitywhileprovidingsuperiorperformanceandavailabilityof
the
database.RecoveryManagerdebutedwithOracle8toprovideDBAsanintegratedbackupand
recovery
solution.RecoveryManagerdeterminesthemostefficientmethodofexecutingtherequestedbackup,
restore,orrecoveryoperation,andthenexecutestheseoperationsinconcertwiththeOracledatabase
server.RecoveryManagerandtheserverautomaticallyidentifymodificationstothestructureofthe
databaseanddynamicallyadjusttherequiredoperationtoadapttothechanges.
OracleFlashRecoveryArea
TheFlashRecoveryAreaisaunifiedstoragelocationforallrecoveryrelatedfilesandactivitiesinan
Oracledatabase.Bydefiningoneinit.oraparameter,allRMANbackups,archivelogs,controlfile
autobackups,anddatafilecopiesareautomaticallywrittentoaspecifiedfilesystemorASMdisk
group.In
addition,RMANautomaticallymanagesthefilesintheFlashRecoveryAreabydeletingobsolete
backups
andarchivelogsthatarenolongerrequiredforrecovery.AllocatingsufficientspacetotheFlash
Recovery
Areawillensurefaster,simpler,andautomaticrecoveryoftheOracledatabase.
EMCConsistencyTechnology
BeginningwithEMCSolutionsEnablerversion5.1,youcanusetheEnginuityConsistencyAssist
(ECA)
featuretoperformconsistentsplitsonBCVpairsacrossmultiple,heterogeneoushosts.Consistentsplit
is
animplementationofinstantsplitthatavoidsinconsistenciesandrestartproblemsthatcanoccurifyou
splitadatabaserelatedBCVwithoutfirstquiescingthedatabase.Thedifferencebetweenanormal
instant
splitandaconsistentsplitisthatduringconsistentsplitthedatabasewritesareheldatthestoragelevel
for
averyshorttimewhiletheforegroundsplitoccurs,maintainingdependentwriteorderconsistencyon
the
targetdevices.
Consistencytechnology,whetherappliedtoSRDF,TimeFinderBCVs,clones,orsnaps,providesthe
capabilitytocreateanimageofoneormoredatabasesthatareDBMSrestartablecopies.Itdoesthisby
momentarilyholdingallwriteIOtothespecifiedSymmetrixvolumeswhileperformingasplit
operation.
Theresultantdatabasesonthetargetvolumesareinadatastatethatisequivalenttothestatethey
wouldbe
inafterapowerfailure.InanOraclecontext,amoreappropriateanalogywouldbethattheylookthe
same
asifalldatabaseinstancesperformedshutdownabortsimultaneously.
SincerestartinganabortedinstancedoesnotinanywayrequirethedatabasetobeinOracleshot
backup
mode,weareabletoprovidecustomerswithawaytocreaterestartabledatabasecloneswithout
requiring
theusertoplacethedatabasestablespacesinhotbackupmode.
EMCTimeFinderOverview
TimeFindersoftwareworksbycreatingmultiple,independentlyaddressablebusinesscontinuance
volumes
(BCVs)forindependentstorage.TheBCVisaSymmetrixdevicewithspecialattributescreated
whenthe
Symmetrixisconfigured.ItcanfunctioneitherasanadditionalmirrortoaSymmetrixlogicalvolume
oras
anindependent,hostaddressablevolume.EstablishingBCVdevicesasmirrorimagesofactive
production
volumesallowsyoutorunmultiplesimultaneousbusinesscontinuancetasksinparallel.Theprincipal
device,knownasthestandarddevice,remainsonlineforregularSymmetrixoperationfromthe
production
server.EachBCVcontainsauniquehostaddress,makingitaccessibletoaseparatebackup/recovery
server.WhenyouestablishaBCVasamirrorofastandarddevice,thatrelationshipisknownasa
BCV
pair.AnytimeyousplitoneoftheBCVsfromthestandarddevice,theBCVhasthemirroreddata
fromthe
standarddeviceandsoitisavailableforbackup,testing,analysis,orsnapping(makinginstantcopies).
Page 6
2/5/2006
5
TimeFinderconsistentsplitisusedtocreatevalidpointintimerestartableimagesoftheOracle
database.
ThesepointintimerestartableimagesarenotvalidOraclebackups;Oraclebackupsrequire
additional
procedures,suchasputtingthetablespace(s)intohotbackupmodepriortosplittingtheBCVs.
TimeFinderConsistentSplit
TimeFindersoftwareprovidesaconsistentsplitimplementationofinstantsplitthatallowsyoutosplit
offa
consistent,DBMSrestartableBCVcopyofyourdatabasewithouthavingtoshutdownthedatabaseor
put
thedatabasefilesintohotbackupmode.ItisabletodothisbysimultaneouslyholdingallwriteI/Oto
databasedevicesmomentarilybeforesplittingtheBCVs.AftermountingtheBCVstoahost,a
subsequent
Oraclestartupwillperforminstancecrashrecovery,ensuringtheintegrityofthedatabaseimage.
ApointintimedatabaseimagetakenwithaconsistentsplitisnotavalidOraclebackupwithout
additional
proceduressuchasputtingthedatabaseinhotbackupmodepriortothesplit.Aconsistentsplitisused
for
thepurposeofcreatingarestartableimageofthedatabaseataspecificpointintime.Formore
information
aboutTimeFinderconsistentsplits,refertothewhitepaperUsingSYMCLItoPerformConsistent
Splits
withtheTimeFinderProductFamily(P/N300000283).
EMCSRDFOverview
SymmetrixRemoteDataFacility(SRDF)isaSymmetrixbasedbusinesscontinuanceanddisaster
restart
solution.Insimplestterms,SRDFisaconfigurationofmultipleSymmetrixunitswhosepurposeisto
maintainrealtimecopiesoflogicaldatavolumeinmorethanonelocation.TheSymmetrixunitscan
bein
thesameroom,indifferentbuildingswithinthesamecampus,orhundredsofmilesapart.SRDF
provides
datamobilityanddisasterrestartspanningmultiplehostplatforms,operatingsystems,andapplications.
ThelocalSRDFdevice,knownasthesource(R1)device,isconfiguredinapairingrelationshipwitha
remotetarget(R2)device,forminganSRDFpair.WhiletheR2deviceismirroredwiththeR1device,
the
R2deviceiswritedisabledtothehost.Afterthe(R2)devicebecomessynchronizedwithits(R1)
device,
youcansplitthe(R2)devicefromthe(R1)deviceatanytime,makingthe(R2)devicefullyaccessible
againtoitshost.Afterthesplit,thetarget(R2)devicecontains(R1)dataandisavailablefor
performing
businesscontinuancetasksthroughitsoriginaldeviceaddressorrestoring(copying)databacktothe
source
(R1)device.Figure1showsatypicalSRDFconfiguration.
Figure1TypicalSRDFConfiguration
Page 7
2/5/2006
6
SRDFProtectionModes
SRDFcurrentlysupportsthefollowingmodesofoperationsfordatabaserestartordatabaserecovery
solutionswithOracleDatabases.
SRDFSynchronousMode
InSRDFsynchronousmode,everyI/OfromtheproductionhostisfirstwrittentothelocalSymmetrix
cache,andisthensentovertheSRDFlinkstotheremoteSymmetrixunit.OncetheremoteSymmetrix
unit
reportsthatthedatahasreacheditscachesuccessfully,theI/Oisacknowledgedtotheproductionhost.
Synchronousmodeguaranteesthattheremoteimageisacompleteduplicationofthesourceimage.
SRDFAsynchronousMode
ManySRDFcustomersusesynchronousmodetoprotectdataonaprimarystoragesystem.
Synchronous
modecreatesaconsistentcopyofdataonthesecondarystoragesystem(R2),butcarriesaprice,both
in
performance(responsetimeontheR1sidehost),andcost(highcapacitylinks).Themainpremiseof
SRDFasynchronousmodeistoprovideaconsistent,pointintimeimageonthe(R2)side,whichisnot
toofarbehindthe(R1)side,andthatresultsinminimaldatalossintheeventofadisasteratthe
primary
site.
DisasterRestartandDisasterRecovery
Classicaldisasterrecoverytechniqueshaveevolvedoverseveraldecades.Inmostcases,adisaster
recovery
activityimpliesusageofdatatapesthathavebeenstoredoffsiteinasecurelocation.Fullbackuptapes
of
diskdataareusuallytakenperiodicallyoftenduringalowtransactionperiod,suchasaSaturdayor
Sundaynight.Duringtherestoftheweek,incremental(ortapescapturingchangeddiskdatasincethe
last
fullorpreviousincrementalbackup)aregatheredandsentoffsite.Bybeingstoredoffsite,thesetapes
use
geographicseparationtoguardagainstanylocaldisaster,suchasafireoraflood.Inadisaster
situation,
theusermustgatherallthetapesandapplytheminsequence.Consideringthetimesassociatedwith
runningthefullandincrementaltapebackupsfromdisk,packagingthetapesforoffsitetransport,
gathering
themintheeventofadisaster,andrecoveringthembacktodiskstorageatthebackupsite,48hours
may
beconsideredarealisticexpectationforthedurationofadisasterrecoveryactivity.Theseactivitiesare
also
susceptibletohumanerror,suchasthetapesincorrectlyappliedinthedisasterrecoverysequence,lost
tapes,damagedtapes,incompatibletapes,etc.Oncetheremotesiteisrunning,asimilarlylengthy
outage
(usuallyinvolvingtapes)occurstogohomeoncerepairshavebeenmadeattheoriginaldatacenter.
Disasterrestart,ontheotherhand,doesnotusecomputertapes.Rather,dataistransportedby
communicationslinkstoremotedatastorage.Theremotereplicaofdataservesastherestartpoint,and
the
usermayrestarttheapplicationusingdiskimagesattheremotesite.
OraclesrecommendeddisasterrestartandrecoverysolutionisOracleDataGuard,whichisabuiltin
featureoftheOracleDatabase.However,forthisdocument,thedisasterrestartandrecovery
discussions
willfocusonEMCSRDF.
Amajorissueiswhetherthedataintheremotelocationislogicallyconsistent.EMCSRDF
synchronous
modeandEMCSRDFasynchronousmodeensurethedependentwriteorderconsistencyofthe
replication
bysynchronizingeachandeverydependentI/O(SRDFsynchronousmode)orbysynchronizingdelta
sets
ofdata(SRDFasynchronousmode).Inatruephysicaldisasteratthesourcelocation,databaserestart
operationscanbecompletedattheremotesitewithoutthedelaysassociatedwithfindingandapplying
tapesinthecorrectsequence.Becausetheremotesitehasphysicaldiskreplicas,thegohomeactivity
is
likewiseveryfastandeasy.
Inadditiontodisasterrestartbenefits,SRDFsignificantlyenhancesdisasterrecoveryoperationsby
using
fastandreliablereplicationtechnologytooffloadtheOraclebackupoperationstoaremotesiteand
later
returntherestoreddatatothelocalsite.
Page 8
2/5/2006
7
Whenadisasterrecoverysolutionisrequired,inordertocreatevalidOraclebackupswithanysplit
mirror
orsnapshottechnologyadditionalproceduresarerequired,suchastoensurethatthedatabaseisinhot
backupmodeduringthesplitorbyusingOracleRecoveryManager(RMAN).RefertoOracle
documentationforfurtherdetailsregardingRMAN.
RebalancingandConsistencyTechnology
ASMprovidesaseamlessandnonintrusivemechanismtoexpandandshrinkthediskgroupstorage.
When
diskstorageisaddedorremoved,ASMwillperformaredistribution(rebalancing)ofthestripeddata
1
.
Thisentirerebalanceoperationisdonewhilethedatabaseisonline,thusprovidinghigheravailability
to
database.Themainobjectiveoftherebalanceoperationistoalwaysprovideanevendistributionoffile
extentsandspaceusageacrossalldisksinthediskgroup.
ItisconsideredabestpracticetouseASMexternalredundancyfordataprotectionwhenusingEMC
arrays.TheSymmetrixwillprovideprotectionagainstlossofmedia,aswellastransparentfailoverin
the
eventofaspecificdiskorcomponentfailure.
Thesplitoperationofstoragebasedreplicasissensitivetotherebalancingprocesswhichmaycause
ASM
diskgroupinconsistenciesifthediskgroupdevicemembersaresplitatslightlydifferenttimes.These
inconsistenciesarearesultofASMmetadatachangesoccurringwhileasplitoperationisinprocess..
In
additionOracleprovidestoolsandproceduralstepstoavoidinconsistencieswhensplittingstorage
based
replicas,howevertheseprocedurecanbesimplifiedandstreamlinedwiththeuseofEMCConsistency
Technology.
SinceEMCconsistentsplittechnologysuspendsdatabaseI/Otopreservewriteorderconsistency,it
also
hasthesideeffectofpreventinganyASMmetadatachangesduringthesplit.Performingaconsistent
split
willpreventASMmetadatainconsistenciesduringthereplicationprocesseliminatingtheotherwise
extra
stepsorpossibleunusablereplicaifASMrebalancewasactivewhileperforminganonconsistentsplit.
TestCasesandBestPractices
ThefollowingtestcasesandresultsshowthatOracle10gdatabaseandAutomaticStorage
Management
canbedeployednondisruptivelywithEMCTimeFinder/MirrorandSRDFfamilyofproducts.Ifa
rebalanceoperationistriggeredwhileaconsistentsplitisbeingperformed,anyASMmetadata
changesare
helduntilthesourceandtargetareinasynchronousstate.
GeneralTestsConfiguration
Hostnames:
ThetermProductionhostreferstotheprimaryhostwherethesourcedevicesareused,andTarget
orBackuphostreferstothehostwheretheBCV,R2orRemoteBCV(RBCV)devicesareused.
Assumptions:
ThetargethostisconfiguredwithOperatingSystemlevel,userandgroupid,Oraclebinariesand
directorystructuresimilartoproductionandisalsoconfiguredforASM
Acopyoftheproductioninit.orafilesfortheASMinstanceandthedatabaseinstancewerecopied
tothebackuphost(targethost)andmodifiedifrequiredtofitthetargethostenvironment
(specificallyASM_DISKSTRINGcontainstheappropriateBCV,R2orremoteBCVdevices).
Thecopyoftheproductionorapwdfileisavailableonthetargethost.
TheappropriateBCV,R2orRemoteBCV(whicheverisappropriateforthetest)areaccessibleby
thetargethostandhaveOraclepermissions.

AnRMANrecoverycatalogisconfiguredandoperational.
Thebackupserver(targethost)hasOracleNettotherecoverycatalogdatabase.
FlashRecoveryAreaisused
1
Note,adiskfailure,willalsotriggerarebalanceactivityifASMredundancyisnotexternal.
Page 9
2/5/2006
8
ThetargethosthasconnectivitytoaLANbasedTapeBackupSystem(applicabletobackupto
tapescenariosbelow)
Testconditionswere:
OLTPloadwasrunningduringthesplit
Transactionintegritytest(definedbyOSCPtestkit)wasrunningduringthesplit.
ASMrebalancewasactiveduringthesplit
Testsuccesswasmeasuredby:
ASManddatabaseinstancewereopenedsuccessfullyontargethostwithoutanyerrorsreported.
Transactionintegritytestpassed
Rebalanceoperationcontinuedautomaticallyandcompletedsuccessfullyontargethost.
DatabaseVerificationutilityverifiedtheintegrityofallthedatafilesandnoerrorswerefound.
Normally,whenconsistentsplititused,TimeFinderandSRDFcommandsareissuedfromacontrol
host
connectedtotheSymmetrix.Howeverinthefollowingtestcasesforthesakeofsimplicity,unless
specified
otherwise,theywereissuedfromtheproductionhost.
Hardware
Model
OS
OracleVersion
LocalProductionHost
SUN
Solaris2.8
10gRelease2(10.2.0.1)
BackuporTargetHost
SUN
Solaris2.8
10gRelease2(10.2.0.1)
Name/Serial
Number
Type
EnginuityVersion
LocalSymmetrix
000187900754
DMX800M2
5671
RemoteSymmetrix
000187900671
DMX800M2
5671
ASMDiskGroups/MountPoints
Inallcases,thedatabaseswerebuiltusingthreedistinctASMdiskgroups.
TheDatafilediskgroupthatcontainedalldatafiles
TheFlashRecoveryArea(FRA)diskgroupthatcontainedfilessuchasmultiplexedcontrolfiles,
backupsets,archivelogsandflashbacklogs.Oraclerecommendsthatarchivelogsbeplacedin
theFlashRecoveryArea.
TheOnlineRedodiskgroupthatcontainedonlineredologsforthedatabase
Page 10
2/5/2006
9
DiskGroup
Purpose
DiskGroupName/
MountPoint
Path(on
productionhost)
TimeFinder
Standard/R1
Device
TimeFinder
BCV
Device
SRDF
R2
Device
TimeFinde
rRemote
BCV
/dev/rdsk/c3t2d0s6
003
07B
003
07B
Flash
Recovery
Area
RECOVERY_AREA
/dev/rdsk/c3t2d1s6
004
07C
004
07C
/dev/rdsk/c3t2d2s6
005
07E
005
07E
OnlineRedo
Logs
REDO_AREA
/dev/rdsk/c3t2d3s6
006
07F
006
07F
/dev/rdsk/c3t2d4s6
007
080
007
080
/dev/rdsk/c3t2d5s6
008
081
008
081
/dev/rdsk/c3t2d6s6
009
082
009
082
/dev/rdsk/c3t2d7s6
00A
083
00A
083
/dev/rdsk/c3t2d8s6
00B
084
00B
084
/dev/rdsk/c3t2d9s6
00C
085
00C
085
/dev/rdsk/c3t2d10s600D
086
00D
086
/dev/rdsk/c3t2d11s600E
087
00E
087
/dev/rdsk/c3t2d12s600F
088
00F
088
/dev/rdsk/c3t2d13s6010
089
010
089
08A
011
08A
08B
012
08B
08C
013
08C
08D
014
08D
DataFiles
DATA_AREA
08E
015
08E
Noteeachdevicesizewasapproximately8.6GB.TheStandarddevicesweremirroredandtheBCV
were
Raid5protected.
Example:QuerythecontentsoftheDATA_AREAdiskgroup.
SQL>selectpath,dk.name"diskname",dg.name"diskgroupname"
fromv$asm_diskdk,v$asm_diskgroupdgwhere
dk.group_number=dg.group_numberanddg.name='DATA_AREA;'
PATH
DISKGROUP_NAME
DISK_NAME
/dev/rdsk/c3t2d4s6
DATA_AREA
DATA_AREA_0000
/dev/rdsk/c3t2d5s6
DATA_AREA
DATA_AREA_0001
/dev/rdsk/c3t2d6s6
DATA_AREA
DATA_AREA_0002
/dev/rdsk/c3t2d7s6
DATA_AREA
DATA_AREA_0003
/dev/rdsk/c3t2d8s6
DATA_AREA
DATA_AREA_0004
/dev/rdsk/c3t2d9s6
DATA_AREA
DATA_AREA_0005
/dev/rdsk/c3t2d10s6DATA_AREA
DATA_AREA_0006
DATA_AREA_0007
DATA_AREA_0008
DATA_AREA_0009
DATA_AREA_0010
DATA_AREA_0011
DATA_AREA_0012
DATA_AREA_0013
DATA_AREA_0014
Page 11
2/5/2006
10
ASMInstanceParameterFile
INSTANCE_TYPE=ASM
ASM_DISKSTRING='/dev/rdsk/*s6'
ASM_DISKGROUPS='DATA_AREA','REDO_AREA','RECOVERY_AREA'
DatabaseInstanceParameterFile
(Theseparametersarespecifictothetestenvironmentonly)
db_name=hrd10g
control_files=+DATA_AREA/control_001
DB_RECOVERY_FILE_DEST=+RECOVERY_AREA
LOG_ARCHIVE_DEST_1=LOCATION=USE_DB_RECOVERY_FILE_DEST
Case1:OracleDatabase10gHotBackupwithTimeFinder/Mirror
WhiletheOracledatabaseisinHotBackupmodeontheproductionhost,aTimeFinder/Mirror
consistent
splitisperformedtocreateanimageoftheactivedatabasewhichcanbeusedtoperformabackupto
tape
byoffloadingthisprocesstoatargetorbackupserver..
CreateSymmetrixDeviceGroupsandAssociateBCVdevices
Twodevicegroupswerecreatedbecausehot(online)backuprequiresthearchivelogstobesplitata
differenttimethanthedatafiles:oneforthedatabasefiles(DBFILES_DG)andtheotherforarchive
logs
(RECOV_DG).IngeneralitisbestpracticeforonlinebackupstoonlyincludetheOracledatafiles.
HoweverwithASMitispossiblethatcontrol,redo,tempanddatafilesmaybeallmixedtogetherin
small
numberofASMdiskgroups.NotethattheSymmetrixdevicegroupshouldalwaystreatASMdisk
groups
asaunitandincludeallmembers.
#symdgcreateDBFILES_DG
#symldgDBFILES_DGaddallrange007:015
#symbcvgDBFILES_DGassociatealldevrange080:08E
#symdgcreateRECOV_DG
#symldgRECOV_DGaddallrange003:004
#symbcvgRECOV_DGassociatealldevrange07B:07C
Establish(synchronize)TheDeviceGroups
Usefulloptiononlywiththefirstestablish.Consecutiveestablisharedoneincrementally.
WaitforthesynchronizationtocompletebeforeperformingaTimeFinderSplit.
#symmirgDBFILES_DGestablish[full]
#symmirgDBFILES_DGverifyi30
#symmirgRECOV_DGestablish[full]
#symmirgRECOV_DGverifyi30
ONLINEBACKUPONPRODUCTIONHOST:
BeginBackupMode
#exportORACLE_SID=hrd10g
#sqlplus/assysdba
SQL>alterdatabasebeginbackup;
Page 12
2/5/2006
11
PerformaConsistentSplitSnapshotforDatabaseFiles
#symmirDBFILES_DGsplitconsistent
EndBackupMode
SQL>alterdatabaseendbackup;
SwitchLogsandCreatebackupControlfiles
Createtwocopiesofthecontrolfile.Onecopy(control_start)willbeusedtostartupthedatabasein
mount
modeonthetargetserver.Thesecondcopy(control_bakup)isavalidcontrolfilecopythatwillbepart
of
thebackupsetusedbyRMAN.
SQL>altersystemarchivelogcurrent;
RMAN>run{
Allocatechannelctl_filetypedisk;
Copycurrentcontrolfileto
+RECOVERY_AREA/control_file/control_start;
+RECOVERY_AREA/control_file/control_bak;
ReleaseChannelctl_file;
}
ResynchronizetheRMANCatalog
Thisaddsthemostrecentarchivelogtotherecoverycatalog.
RMAN>resynccatalog;
PerformaConsistentSplitSnapshotoftheRecoveryAreatocapturetheArchiveLog
#symmirRECOV_DGsplitconsistent
BACKUPPROCEDURES
OntheBackuphostthesnapshotcanbeusedasadiskbackuporasourceforatapebackup.Some
backup
applicationsrequirethedatabasetobemountedtoperformbackups.
OncetheBCVsaresplit,checkthat:
TheBCVsonbackuphosthavecorrectOraclepermissions
ASMinit.orafileparameterASM_DISKSTRINGdoesntexcludethepathtotheBCVs.
ASMinit.orafileparameterASM_DISKGROUPScontainsthenamesofthediskgroups.
StartASMInstance
WhentheASMinstanceisstarted,sincetheBCVphysicalnamesareincludedinthe
ASM_DISKSTRING
parameter,itwillidentifythemasthediskgroupsfromproductiondatabase.Alsosincethe
ASM_DISKGROUPSparametercontainsthediskgroupnamestheywillbemountedautomatically.
#exportORACLE_SID=+ASM
#sqlplus/assysdba
SQL>startup
Page 13
2/5/2006
12
MountDatabaseInstance
Adatabasebackupthatwastakenwithhotbackupmodeisvalidforbackuponlyaslongasitwasnt
open
withresetlogsoptionsoropenedforread/write.Forthatreasonitshouldbeeithermounted(pre
requisite
formediarecoveryandmanybackupapplications)oropenreadonly(afteratleastenoughrecovery
was
donetoallowthedatabasetoopen).
BeforethedatabaseismountedchangetheBackupdatabaseinstanceinit.oraCONTROL_FILE
parameter
topointtothecopiedcontrolfile.Forexample:
control_files=+RECOVERY_AREA/control_file/control_start
#sqlplus/assysdba
SQL>startupmount
BackingUpTheDatabaseInstance
PerformaRMANbackupontheBackuphost.Thecontrolfilecopythatwasnotusedtomountthe
instance(control_bk)shouldbepartofthebackupset.Thecontrol_startcontrolfileshouldnotbe
backed
up,becauseoncethedatabaseinmountedtheSCNwillbeupdatedandisisinconsistentwith
production
controlfile.
RMAN>run{ALLOCATECHANNELt1TYPESBT_TAPE
BACKUPFORMATctl%d/%s/%p/%t
CONTROLFILECOPY+RECOVERY_AREA/control_file/control_bak;
BACKUP
FULL
FORMATctl%d/%s/%p/%t
(database);
BACKUP
FORMATal%d/%s/%p/%t
(archiveall);
RELEASECHANNELt1
}
Note:Theformatspecifier%disreplacedwithdate,%tisreplacedwithafourbytetimestamp,%s
with
thebackupsetnumber,and%pwiththebackuppiecenumber.
Page 14
2/5/2006
13
Case2:DatabaseCloningwithTimeFinder/Mirror
WhileOracleisopenforread/writeontheproductionhost,aTimeFinder/Mirrorconsistentsplitis
performedonanestablishedTimeFinder/MirrorBCVs.Thisoperationwillcreatearestartableimage
ofthe
activedatabasethatcanserveasarepurposeddatabase.TheSymmetrixdevicesincludedinthe
ALLDB_DGdevicegroupmatchtheASMdiskgroupsthatcontainredologs,datafilesanda
controlfiles.
Archivelogsarenotusedwithcloning;howeveritmaybebeneficialtoincludetherecoveryareaas
well
(especiallyifflashbacklogsareactive).Ifrecoveryareaistobemadeavailabletothetargethostas
well
thenincludetherecoveryareadevicesintheALLDBSymmetrixdevicegroupsotheywillbepartof
the
consistentsplit,operationtogetherwiththedatabasefiles.
CreateSymmetrixDeviceGroupandAssociateBCVdevices
CreateasingledevicegroupfortheOracledatafiles,controlfilesandOnlineRedologfilesbecause
consistentsplitrequiresallthedatabasefilestobesplittogether.
#symdgcreateALLDB_DG
#symldgALLDB_DGaddallrange003:015
#symbcvgALLDB_DGassociatealldevrange07B:08E
Establish(synchronize)TheDeviceGroup
WaitforthesynchronizationtocompletebeforeperformingaTimeFinderSplit.
#symmirgALLDB_DGestablish[full]
#symmirgALLDB_DGverifyi30
#symmirALLDB_DGsplitconsistent
ONTARGETHOST:
Onthetargethost,oncetheBCVsaresplit,checkthat:
TheBCVshaveOraclepermissions
StartASMInstance
WhentheASMinstanceisstarted,sincetheBCVsareincludedintheASM_DISKSTRINGparameter,
it
willidentifythemasthediskgroupsfromproductiondatabase.AlsosincetheASM_DISKGROUPS
parametercontainsthediskgroupnamestheywillbemountedautomatically.
#sqlplus/assysdba
SQL>startup
StartDatabaseInstance
Startupandrecovertheclonedatabase.Oncetheclonedatabaseisrecovered,itshouldbeassigneda
new
DBIDandrestartedwithresetlogs.Thefollowingstepsillustratethesesteps.
connecttoRMAN
RMAN>startupmount
RMAN>recoverdatabase;
Page 15
2/5/2006
14
RMAN>exit
nidtarget=sys/manager1
optionallythedb_namecanbechangedaswell,seethe
OracleRecoveryGuidefordetailsonthenidutility.
SQL>startupmount
SQL>alterdatabaseopenresetlogs
Attheendofthisstepthedatabaseisopenedandavailableforuserconnections.
Case3:RemoteDatabaseCloningwithTimeFinder/Mirrorand
SRDF
WhenusingSRDF/SorSRDF/AfordatabaseprotectionthereisanadvantageforusingremoteBCVs.
The
remoteBCVsallowSRDFtoremainsynchronizedandmaintainingdatabaseprotection,whileatthe
same
timetheremoteBCVscanbesplitasadatabaseclonefortest,developmentorreporting.Itispossible
to
usethemforbackupincombinationwithOraclehotbackup(asdescribedinthenextsection).Also
they
canserveasagoldcopyforenhancedprotectioninsituationswhenSRDFisabouttostartfailback
operationandtheremotesitecontainsavalidimageofthedatabase.Itisabestpracticetosplitthe
remote
BCVsbeforesynchronizingtheSRDFforthepossibilitythatbeforeSRDFisfullysynchronizedand
the
databaseregainprotection,asecondfailureoccurs(alsoreferredasrollingdisaster).
Note:ThefollowingsolutionaddressestheuseofremoteBCVs.However,torestartthedatabase
directly
fromtheR2devices,usethesamestepsasdescribedbelow.Theonlydifferenceisthatinsteadofthe
remoteBCVsitistheR2devicesthatareusedtostarttheASManddatabaseinstances.Ifthiswasnta
plannedfailoverandtheR1siteisnotaccessible,issueasymrdffailovercommandfromtheR2siteto
maketheR2devicesreadwritable.
CreateSymmetrixDeviceGroupandAssociateRemoteBCVdevices
Becauseconsistentsplitrequiresallthedatabasefilestobesplittogethercreateasingledevicegroup
for
theOracledatafiles,controlfilesandOnlineRedologfiles.Tothesamedevicegroupaddtheremote
BCVs(remoteisindicatedbyusingtherdfflag.ThatmeansthattheBCVsarethoseattachedtothe
R2
devicesontheremoteSymmetrix).
#symdgcreateALLDB_DGtypeR1
#symldgALLDB_DGaddallrange003:015
#symbcvgALLDB_DGrdfassociatealldevrange07B:08E
Establish(synchronize)SRDFandRemoteBCVdevices
WaitforthesynchronizationtocompletebeforeperformingaTimeFinderSplit.Thesynchronization
of
SRDFandtheremoteBCVscanhappensimultaneously.
ForSRDF/A,oncetheSRDFisinaconsistentstateusetheEnableSRDFcommandtoguarantee
device
levelconsistency.
ForSRDF/Sprotection:
Note:SRDF/SisthedefaultSRDFmode.Ifitwaschangeduse:
#symrdfgALLDB_DGsetmodesync
#symrdfgALLDB_DGestablish[full]
#symrdfgALLDB_DGverifyi30
Page 16
2/5/2006
15
#symmirgALLDB_DGrdfestablish[full]
#symmirgALLDB_DGrdfverifyi30
ForSRDF/Aprotection:
#symrdfgALLDB_DGsetmodeasync
#symrdfgALLDB_DGestablish[full]
#symrdfgALLDB_DGverifyi30
#symrdfgALLDB_DGenable
#symmirgALLDB_DGrdfestablish[full]
#symmirgALLDB_DGrdfverifyi30
#symmirALLDB_DGrdfsplitconsistent
ONTARGETHOST:
Onthetargethost,oncetheBCVsaresplit,checkthat:
TheBCVshaveOraclepermissions.NotethatifthesamehosthasbothremoteBCVsaswellas
R2devicesmappedtoitthentheR2devicesshouldnothaveOraclepermissions.Thereasonis
thatASMwritesdiskgroupinformationtotheASMmembers.AsbothR2andRemoteBCV
containstheexactsameOracleinformationASMcannotdifferentiatebetweenthemifbothhave
Oraclepermissions.
ASMinit.orafileparameterASM_DISKSTRINGincludesthepathtotheBCVs.
StartASMInstance
it
#sqlplus/assysdba
SQL>startup
StartDatabaseInstance
Startupandrecovertheclonedatabase.Oncetheclonedatabaseisrecovered,itshouldbeassigneda
new
DBIDandrestartedwithresetlogs.Thefollowingstepsillustratethesesteps.
connecttoRMAN
RMAN>startupmount
RMAN>recoverdatabase;
RMAN>exit
nidtarget=sys/manager1
optionallythedb_namecanbechangedaswell,seethe
OracleRecoveryGuidefordetailsonthenidutility.
SQL>startupmount
SQL>alterdatabaseopenresetlogs
Attheendofthisstepthedatabaseisopenedandavailableforuserconnections.
Page 17
2/5/2006
16
Case4:OracleDatabase10gHotBackupwithTimeFinder/Mirror
andSRDF
WhenusingSRDF/SorSRDF/AfordatabaseprotectionthereisanadvantageforusingremoteBCVs.
The
remoteBCVsallowSRDFtoremainsynchronizedandmaintainingdatabaseprotection,whileatthe
same
timetheremoteBCVscanbesplitasadatabaseclonefortest,devorreporting.Itispossibletouse
them
forbackupincombinationwithOraclehotbackup(asdescribedinthissection).Alsotheycanserveas
a
goldcopyforenhancedprotectioninsituationswhenSRDFisabouttostartfailbackoperationandthe
remotesitecontainsavalidimageofthedatabase.ItisbestpracticetosplittheremoteBCVsbefore
synchronizingtheSRDFforthepossibilitythatbeforeSRDFisfullysynchronizedandthedatabase
regain
protection,asecondfailureoccurs(alsoreferredasrollingdisaster).
CreateSymmetrixDeviceGroupsandAssociateRemoteBCVdevices
TwodevicegroupswerecreatedforremoteTimeFinderoperationsbecausehot(online)backup
requires
thearchivelogstobesplitatadifferenttimethanthedatafiles:onedevicegroupwascreatedforthe
databasefiles(DBFILES_DG)andtheotherforarchivelogs(RECOV_DG).Ingeneralitisbest
practice
foronlinebackupstoonlyincludetheOracledatafiles.HoweverwithASMitispossiblethatcontrol,
redo,
tempanddatafilesmaybeallmixedtogetherinsmallnumberofASMdiskgroups.Notethatthe
SymmetrixdevicegroupshouldalwaystreatASMdiskgroupsasaunitandincludeallmembers.
NotethatremoteBCVsareestablishedwiththeR2devices(remoteisindicatedbyusingtherdfflag.
That
meansthattheBCVsarethoseattachedtotheR2devicesontheremoteSymmetrix).
#symdgcreateDBFILES_DGtypeR1
#symldgDBFILES_DGaddallrange007:015
#symbcvgDBFILES_DGrdfassociatealldevrange080:08E
#symdgcreateRECOV_DGtypeR1
#symldgRECOV_DGaddrange003:004
#symbcvgRECOV_DGassociatealldevrange07B:07C
Establish(synchronize)SRDFandRemoteBCVdevices
WaitforthesynchronizationtocompletebeforeperformingaTimeFinderSplit.Thesynchronization
of
SRDFandtheremoteBCVscanhappensimultaneously.
ForSRDF/A,oncetheSRDFisinaconsistentstateusetheEnableSRDFcommandtoguarantee
device
levelconsistency.
Note:Ingeneral,SRDFisrequiredtoincludealldata,controlandredologfilestogethertocreatea
write
orderconsistentandrestartableimageofthedatabase.Inaddition,controloperationswheninSRDF/A
modealwayshavetoincludeALLtheSRDF/AdevicesinanRDFgrouptogether.If(likeinthis
example)
TimeFinderoperationsrequiretwodevicegroups:DBFILES_DGcontainingdatafilesand
RECOV_DG
containingarchivelogs,andSRDFrequiresadifferent(larger)setofdevicestooperateon,adevice
fileis
usedfortheSRDFcontroloperations.ThedevicefilecontainsthelistofR1devicesincludingdata,
redo
andcontrolfiledevices.ItmayalsocontainarchivelogdevicesiftheSRDFisusedtoreplicatearchive
logs.Otherwiseitispossibletoshiparchivelogsoverthenetworktotheremotehost.
WhenusingadevicefileinSRDFcontrolcommandstheSymmetrixIDandSRDFgrouparespecified
in
thecommandline.
ForSRDF/Sprotection:
Page 18
2/5/2006
17
Note:SRDF/SisthedefaultSRDFmode.Ifitwaschangeduse:
#symrdfgDBFILES_DGsetmodesync
#symrdfsid754rdfg3file./dev_srdfestablish[full]
#symrdfsid754rdfg3file./dev_srdfverifyi30
ForSRDF/Aprotection:
#symrdfsid754rdfg3file./dev_srdfsetmodeasync
#symrdfsid754rdfg3file./dev_srdfestablish[full]
#symrdfsid754rdfg3file./dev_srdfverifyi30
#symrdfsid754rdfg3file./dev_srdfenable
ForTimeFinder:
#symmirgDBFILES_DGrdfestablish[full]
#symmirgDBFILES_DGrdfverifyi30
ONLINEBACKUPONPRODUCTIONHOST:
BeginBackupMode
#sqlplus/assysdba
SQL>alterdatabasebeginbackup;
Note:WhenusingSRFD/A,sincetheR2isalways2cyclesbehindtheR1,inorderforthebeginhot
backupmarkinthedatafilestobeincludedintheremoteBCVsimage(forbackupandrecoverysake)
we
usetheSRDFcheckpointcommandthatmakesuretheinformationontheR1hasreachedtheR2
beforewe
issuetheremoteBCVssplit.
#symrdfsid754rdfg3file./dev_srdfcheckpoint
#symmirgDBFILES_DGrdfsplitconsistent
EndBackupMode
SQL>alterdatabaseendbackup;
SwitchLogsandCreateControlfiles
Createtwocopiesofthecontrolfile.Onecopy(control_start)willbeusedtostartupthedatabasein
mount
modeonthebackupserver.Thesecondcopy(control_bakup)willbeusedasacomponentofthe
backup
setusedbyRMAN.
SQL>altersystemarchivelogcurrent;
RMAN>run{
Allocatechannelctl_filetypedisk;
+RECOVERY_AREA/control_file/control_start;
+RECOVERY_AREA/control_file/control_bakup;
}
ResynchronizetheRMANCatalog
Thisaddsthemostrecentarchivelogtotherecoverycatalog.
Page 19
2/5/2006
18
RMAN>resynccatalog;
PerformaConsistentSplitSnapshotoftheRecoveryAreatocaptureArchiveLogs
#symrdfsid754rdfg3file./dev_srdfcheckpoint
#symmirRECOV_DGrdfsplitconsistent
BACKUPPROCEDURES:
Onthebackuphost,oncetheBCVsaresplit,checkthat:
TheBCVshaveOraclepermissions.NotethatifthesamehosthasbothremoteBCVsaswellas
R2devicesmappedtoitthentheR2devicesshouldnothaveOraclepermissions.Thereasonis
thatASMwritesdiskgroupinformationtotheASMmembers.AsbothR2andRemoteBCV
containstheexactsameOracleinformationASMmayconfusebetweenthemiftheybothhave
Oraclepermissions.
StartASMInstance
it
#sqlplus/assysdba
SQL>startup
MountDatabaseInstance
Beforethedatabaseismountedchangethetargetdatabaseinstanceinit.oraCONTROL_FILE
parameterto
pointtothecopiedcontrolfile.Forexample:
control_files=+RECOVERY_AREA/control_file/control_start
#control_files=+DATA_AREA/control_001
#sqlplus/assysdba
SQL>startupmount
BackuptargetDatabaseInstance
Performarmanbackuponthebackuphost.Thepreviouslybackedupcontrolfilemustbepartofthe
backupsetbecauseoncethedatabaseinmountedtheSCNwillbeupdatedandisnolongerreflectsthe
initialstateofthecontrolfile.
RMAN>run{ALLOCATECHANNELt1TYPESBT_TAPE
BACKUPFORMATctl%d/%s/%p/%t
CONTROLFILECOPY+RECOVERY_AREA/control_file/control_bak;
BACKUP
FULL
FORMATctl%d/%s/%p/%t
(database);
BACKUP
FORMATal%d/%s/%p/%t
Page 20
2/5/2006
19
(archiveall);
RELEASECHANNELt1
}
Note:Theformatspecifier%disreplacedwithdate,%tisreplacedwithafourbytetimestamp,%s
with
thebackupsetnumber,and%pwiththebackuppiecenumber.
Page 21
2/5/2006
20
Case5:RestoringaDatabaseontheProductionHost
Ifrecoverytimeiscritical,therecoveryshouldbedoneontheproductionhost.Thismethodwill
provide
minimaldowntime,whileprotectingthegoldcopy(BCV)ofthedatabase.Thiscasewillrestorethe
databasefromCase1.ThistechniqueisveryfastsinceonlythechangedtracksontheLUNsthatmake
up
thedatafilesarerestored.Onlytheadditionalarchivelogssincelastbackuptimeneedtobeappliedfor
recovery.Itisrecommendedthattherestoreprocessisdoneusingprotectoption.Thisensuresthat
any
writestothestandarddeviceswillnottainttheBCVs.Ifcorruptionisreintroduced,oramistakeis
made
duringtherecoveryprocedure,theBCVcanonceagainbeusedtoperformaquickrestoreofthe
productionhostsdatabase..
Shutdownthedatabaseinstanceontheproductionhost
#sqlplus/assysdba
SQL>shutdown[immediate]
DismounttheASMDatafilesdiskgroup
SQL>alterdiskgroupDATA_AREAdismount;
Note:Inthiscaseweonlyrestoredatafilesimagetoproductionhost.Wedonotwanttooverwritethe
onlineredologs(iftheystillavailableonproduction)astheycontainthelastcommittedtransactions.
Also
wedonotwanttooverwritetheFlashRecoveryArea,whichcontainsrecentarchivelogs.IfFlash
RecoveryAreaswasdamagedaswellthendismountandrestoreitsASMdiskgroupsaswell(ifonline
redologsaredamagedonproductionthenrecreatetheirdiskgroup.Thelogswillberecreatedwhenthe
databaseisopenedwithresetlogs).
PerformaTimeFinderRestoreonthedatafilesdiskgroup
TheRecoveryAreamustnotberestoredtotheproductionserver
#symmirgDBFILES_DGrestore
MounttheASMDiskgroups
#sqlplus/assysdba
SQL>alterdiskgroupDATA_AREAmount;
StartuptheLocalDatabaseinMOUNT
#sqlplus/assysdba
SQL>startupmount
PerformcompleteorpointintimerecoverywithRMAN.
Ifyouareperformingincompleterecovery,thensettheuntiltimeoruntilSCNmarkers.
Page 22
2/5/2006
21
RMAN>run{
SETUNTILTIME06dec0513:00;
RECOVERDATABASE;
}
OpeningtheDatabase
Afteryouaresurethatallfilesarecorrectlyrestoredandrecovered,youcanopenthedatabaseusing
the
resetlogsoption.Afteryouaresurethatallfilesarecorrectlyrestoredandrecovered,youcanopen
thedatabaseusingtheresetlogsoption.Theopenwithoptionresetlogswillcreateanew
incarnationofthedatabase,whichmustbealsoregisteredintheRMAN.
RMAN>alterdatabaseopenresetlogs;

EMC TimeFinder and SRDF

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

EMC TimeFinder and SRDF

Încărcat de

Drepturi de autor:

Formate disponibile

Page 1

S-ar putea să vă placă și