Database Platform Migration Using ZDLRA - Oracle · Cross-Endian Database Migration using ZDLRA 1. Performing incremental backups as normal from the source database to ZDLRA 2. Create

Copyright©2018,Oracleand/oritsaffiliates.Allrightsreserved.|

DatabasePlatformMigrationUsingZDLRA

OracleServerTechnologyHighAvailabilitySystemsDevelopmentMaximumAvailabilityArchitectureNovember2018


SafeHarborStatementThefollowingisintendedtooutlineourgeneralproductdirection.Itisintendedforinformationpurposesonly,andmaynotbeincorporatedintoanycontract.Itisnotacommitmenttodeliveranymaterial,code,orfunctionality,andshouldnotberelieduponinmakingpurchasingdecisions.Thedevelopment,release,andtimingofanyfeaturesorfunctionalitydescribedforOracle’sproductsremainsatthesolediscretionofOracle.

3


ProgramAgenda

SolutionOverview

ZDLRABackupandRestoreStrategy

DatabaseMigrationProcessusingdbmigusera.pl

CustomerCaseStudy

1

2

3

4

4


SolutionOverview

5

• Databasemigrationistheprocessofmovingdatabasestoanewplatform,includingExadata andExaCC

• ZeroDataLossRecoveryAppliance(ZDLRA)providesasimple,reliable,andfastmigrationsolutionwithminimaldowntime

Thispresentationoutlinesthestepstoexecute:

• Cross-endianplatformDBmigrationusingZDLRA

• Same-endianplatformDBmigration– evensimplerandfasterwithZDLRA


ProgramAgenda

SolutionOverview


DatabaseMigrationProcessusingZDLRA

Overview– RealLifeScenario

1

2

3

4

6


ZeroDataLossRecoveryApplianceOverview

DeltaPush•DBsaccessandsendonlychanges• Minimalimpactonproduction

•Real-timeredotransportinstantlyprotectsongoingtransactions

ProtectedDatabases

ProtectsallDBsinDataCenter•Petabytesofdata•RMAN-drivenbackup&restore•Oracle10.2-12.2,anyplatform•NoexpensiveDBbackupagents

DeltaStore• Storesvalidated,compressedDBchangesondisk• Fastrestorestoanypoint-in-timeusing‘virtualfull’•BuiltonExadatascalingandresilience•EnterpriseManagerend-to-endcontrol

RecoveryAppliance

ReplicatestoRemoteRecoveryAppliance

OffloadsCloud/TapeBackup

7

DBBackupCloudService

Copyright©2018, Oracleand/oritsaffiliates.Allrightsreserved.|

Space-Efficient “Virtual”FullBackups

• Afterone-timefullbackup,incrementalsusedtocreatevirtual fulldatabasebackupsonadailybasis• Pointer-basedrepresentationofphysicalfullbackupasofincrementalbackuptime

• Virtualbackupstypically10xspaceefficient• Enableslongbackuphistorytobekeptwiththesmallestpossiblespaceconsumption• “TimeMachine”fordatabase

DeltaStoreProtectedDatabases

DayNIncr

Day1VirtualFull

DayNVirtualFull

Day1Incr

Day0Full

NoMoreFullBackups:IncrementalsForeverArchitecture

8

Copyright©2018, Oracleand/oritsaffiliates.Allrightsreserved.|

FastRestoretoAnyPoint-in-TimeNoIncrementalApply=NoLoadonProductionServer

• Directlyrestoreanyvirtualfullbackup• Allblocksreferencedfromvirtualfullareefficientlyretrieved• Eliminatesproductionserveroverheadoftraditionalrestoreandmergeofincrementals

• InheritsscalabilityandperformanceviaExadata-basedhardwareplatform

DeltaStoreProtectedDatabases

RESTORE DATABASE TO DAY ‘N’

Day0Full

Day1Incr

DayNIncr

Day‘N’FullBackup


ProgramAgenda

Abstract



Overview– RealLifeScenario

1

2

3

4

10



11

Databasemigrationcanbeeither:

1. Cross-Endian– BigEndiantoSmallEndian,orviceversa.2. AcrosstheSame-Endian.

Wheredidthewordendiannesscamefrom?FromapassageinGulliver'sTravels inwhichanemperor,aftercuttinghisfingerafteropeninganeggatthelargeend,commandshissubjectstoopenthematthesmallend;thosewhocomplyarecalled“Little-Endians”,whilethosewhorebelbyopeningtheireggsatthelargeendarecalled“Big-Endians.”

Incomputerarchitecture:•Inbig-endianformat,wheneveraddressingmemoryorsending/storingwordsbyte-wise,themostsignificantbyte—thebytecontainingthemostsignificantbit—isstoredfirst(hasthelowestaddress)orsentfirst,thenthefollowingbytesarestoredorsentindecreasingsignificanceorder,withtheleastsignificantbyte—theonecontainingtheleastsignificantbit—storedlast(havingthehighestaddress)orsentlast.

•Little-endianformatreversesthisorder:thesequenceaddresses/sends/storestheleastsignificantbytefirst(lowestaddress)andthemostsignificantbytelast(highestaddress).


Cross-EndianDatabaseMigrationusingZDLRA1. Performingincrementalbackupsasnormalfromthesourcedatabase toZDLRA

2. Createanewdatabaseonthedestinationplatform.

3. Onthedestinationdatabase,restorethelatestvirtuallevel0backupfromtheZDLRAforthesourcetablespaces.– Therestoreoperationwillconvertandcopythedatafilestothenewdestinationdatabasestorage.

– Themigrationprocedurewillalsocreateanexportdatapumpfiletopluginthetablespacesatthedestination.

4. Recoverthedestinationdatafileswithincrementals (i.e.datachanges)takenatthesourceasmanytimesasdesiredtokeepthedatainsyncascloseaspossiblebetweenthetwodatabases– Ideally,therecoveroperationshouldberunonregularbasis(e.g.daily),untilittakeslessthan2hours.

5. Selectafinalmigrationwindowtothedestinationdatabase,ideallywherethereareminimalsourcedatabaseactivities:– Onthesourcedatabase:

1. Putthetablespaces onthesourcedatabaseinreadonlymode2. Takeafinalincrementallevel1backuptotheZDLRA3. Exportthetransportabletablespacesdefinition(metadatadumpfile)

– Onthedestinationdatabase:1. Recoverthedatafileswiththefinalincrementalbackupandexportthetransportabletablespaces2. Importthetablespacemetadatadumpfiletopluginthetablespaces3. Activatedestinationdatabaseandenableservices

12


SourceDB(11g-12c) DestinationDB(12c)

SOETBS Day1:FullBackup

Export Import

Read-only

MetaData

SOETBS

DatabaseMigrationusingZDLRA• DramaticallyReduceRead-onlyDowntime– SeveralHours+toFewHoursorLess

• Minimaldowntime– DBremainsread-write throughoutprocess• Tablespaces areonlyplacedinread-onlypriortofinalincremental

• Dailyincrementalbackups->virtualfullbackupsonRecoveryAppliance• Restorelatestvirtualfullbackuppriortostartofmigrationwindow

• RESTOREFROMPLATFORMXXXFOREIGNDATAFILEYYY• Finalincrementaltakeninread-only,thenrestored&recoveredontodestinationfiles

• RECOVERFROMPLATFORMXXXFOREIGNDATAFILECOPYYYY• Datapumpmetadataexportatsourceandimportofmetadatadumpfileatdestination

VirtualFullRestore

Restore&RecoverFinalIncremental

Day2->N:IncrementalBackups

Dayn:FinalIncremental

Read-write


CrossPlatformDBMigrationusingZDLRA- Benefits

14

Primarybenefits:1. Significantreductionindowntime(Potentiallylessthantwohoursofservicedowntime)12. ApplicationserviceisREADONLYduringmostoftheservicedowntime3. NewZDLRAtool(dbmigusera.pl)simplifiescrossplatformmigrationbyautomatingsteps,

especiallyusefulforlargedatabases4. Migrationtimeisnotimpactedbythesizeofthedatabase

Read-onlydowntimebasedon:1. Finalincrementalbackupandrecoverystep– incrementalsizeshouldbe<5%ofDBsize2. Finaltablespacemetadataexport/importduration(onlynecessaryforcrossplatform)3. Numberoftargettablespaces– importisdoneserially4. Applicationserviceswitchoverfromsourcetodestinationdatabase

RefertoMOSNote:CrossPlatformDatabaseMigrationusingZDLRA(DocID2460552.1)1Downtimedoesnot includetheuserobjectstobeimportedonthedestination.


Same-EndianDBMigrationusingZDLRA• LeverageDataGuardandZDLRAforminimaldowntimemigration– ByusingthesourcedatabasebackupsavailableontheZDLRA,instantiatenewdatabaseonthedestinationplatformusingRMANDUPLICATEFORSTANDBY.

– StartMRPtosynchronizestandbywithprimarydatabase– Verifydestinationdatabyopeningstandbyread-only– Performswitchoverandredirectapplicationclientstonewprimarydatabase– RefertoMOSNote:CreatingaPhysicalStandbyDatabaseinan11.2,12.1,12.2orlaterenvironment(DocID2275154.1)1

• Advantages:– Near-ZerotoZerodowntimeduringswitchovertodestinationdatabase– Increasedavailabilityduringthemigrationprocessvstransportabletablespaceapproach–WithActiveDataGuard,standbydatabasecanbeusedtooffloadread-onlyactivitiesfromprimary(e.g.reporting),untilswitchoverisperformed

1WhenusingRMANDUPLICATE,connecttotheZDLRAasCATALOGandconfiguretheRMANAUXILIARYSBTchannelstoconnecttotheZDLRA.

15


ProgramAgenda

Abstract


DatabaseMigrationProcessusingdbmigusera.pl

CustomerCaseStudy

1

2

3

4

16


CustomerCaseStudy

17


LeadingGlobalSemiconductorManufacturer

BusinessNeeds• AccelerateGrowth• DriveOperationalExcellence

• CustomerExperience• OperationalEfficiency

• Groworganizationalcapabilities– optimizeinnovation

• Addresscurrent&plannedbusinessgrowthobjectives

SolutionNeeds• Stability• ZeroPreventableOutages• FocusonBusinessOps• IncreaseITagility,self-

serviceandalignmenttobusinessdrivers

Exadata X4-2 Exadata X2-2

ActiveDataGuard

WeeklyFullanddailyincrementalbackup

NASDevice

LegacyArchitecture

ResultsAchieved• Consolidateandstandardize– ConsolidatedseveralDBs to

ExaCC +Multi-Tenantoption• ImprovedthetimeandcosttobuildandmaintainAnalyticsplatform

• NearzerodowntimeDBmigrationtoExaCC usingRA+RMANDUPLICATE.

• Deliverexceptionalservicetobusinessusers

• Eliminatedfullbackups• Reducedincrementalbackuptimeby2X

• ImprovedRTOby4X

Exadata X4-2 Exadata X2-2

CascadeStandby

Incrementalforeverbackups

ActiveDataGuard

Exadata C@C

NewArchitecture

Copyright©2018,Oracleand/oritsaffiliates.Allrightsreserved.| 19


CurrentArchitecture

OracleDatabasesonIBM/AIX

Exadata C@C

FutureArchitecture


BusinessGoals

Enhancethecustomershoppingexperience

§ Providearobustplatformforthepoint-of-saledatabases

§ Improveoverallperformance

§ Increasetimetomarket§ Datacentermodernization

§ MigratingfromIBMAIXtoExadata

§ Databaseconsolidation

LeadingEuropeanRetailer

Copyright©2018,Oracleand/oritsaffiliates.Allrightsreserved.| 20

Database Platform Migration Using ZDLRA - Oracle · Cross-Endian Database Migration using ZDLRA 1. Performing incremental backups as normal from the source database to ZDLRA 2. Create

Documents