Zero Data Loss Recovery Appliance: Development · Backup Best Practices • Create Incremental L0 (full) as first backup • Create subsequent Cumulative L1 backups “Incremental

Copyright©2017, Oracleand/oritsaffiliates.Allrightsreserved.

ZeroDataLossRecoveryAppliance:DeepDiveandBestPracticesfromDevelopmentCON6679

KellySmith,Sr.PrincipalProductManager,OracleJonySafi,ConsultingMemberofTechnicalStaff,OracleGabrielNitulescu,ITProjectLeader– Database,CapitalFundManagement

October4,2017


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

3


RecoveryApplianceAgenda

4

Overview

BestPractices– Manageability

BestPractices– Configuration

BestPractices– BackupandRecovery

BestPractices– Validation,SecurityandTroubleshooting

CapitalFundManagement– CustomerSuccessStory

1

2

3

4

5

6


RecoveryApplianceAgenda

5

Overview






1

2

3

4

5

6


RecoveryApplianceUniqueBenefitsforBusinessandI.T.

MinimalImpactBackupsProductiondatabasesonlysendchanges.AllbackupandtapeprocessingoffloadedSavings,BackupTimeShrinks

EliminateDataLossReal-timeredotransportprovidesinstantprotectionofongoingtransactionsZerotoSub-1sRPO

Cloud-ScaleProtectionEasilyprotectalldatabasesinthedatacenterusingmassivelyscalableserviceHAandScalableArchitecture

DatabaseLevelRecoverabilityEnd-to-endreliability,visibility,andcontrolofdatabases- notdisjointfilesRecoveryReadiness,Validations

6


1010001001101001010101010001010101

0010101010100010101010010101010010100010101010010101000101010100

0011010010101010100010101010010

101000100110100101010101000101

DesignedbyOracleDatabase

DevelopmentTeamforOracleDatabase

DirectDatabaseToDatabase

Communication

ContinuallyValidatesRecoveryStatus

RecoverToAnyPointIn

Time

Code-levelIntegrationwithDataGuard,RMAN,OSB

EngineeredDataProtectionForTheOracleDatabase

ZeroDataLossRecoveryAppliance

7


ZeroDataLossRecoveryAppliance

8

ProtectedDatabases

ProtectsallDBsinDataCenter•RMANDrivenFramework•Petabytesofdata•Oracle10.2-12c,anyplatform•NoexpensiveDBbackupagents

DeltaStore• Storesvalidated,compresseddataondisk• Fastrestorestoanypoint-in-time•BuiltonExadatascalingandresilience•EnterpriseManagerend-to-endcontrol

RecoveryAppliance

ReplicatestoRemoteRecoveryAppliance

OffloadsTapeBackupDeltaPush

• SendonlyIncrementalchangesandnomorefullbackups

•Real-timetransactionscopiedoverforcontinuousdataprotection

IntegratedMediaManager/ThirdPartyBackupClientSW


RecoveryApplianceBestPracticesJonySafi

9


RecoveryApplianceProgramAgendaOverview






1

2

3

4

5

10

6


BeforeYouStart• TheRecoveryApplianceisanAPPLIANCE

– PerformanceTuned– Resilient– HighlyAvailable

• UseEnterpriseManagerforManagementMonitoring,&Alerting• UsetheRecoveryApplianceInformationCenter• RunExachk monthlytoensureRecoveryApplianceHealth• SubscribetoMOSalertsandreferperiodicallytothefollowingnotes:

– RecoveryApplianceCriticalIssuesMOSnoteforcriticalissuesalerts– RecoveryApplianceSupportedVersionsMOSnoteforlatestsoftwareupdates

11

Copyright©2017, Oracleand/oritsaffiliates.Allrightsreserved. 12

BestPractices– UnifiedManagementDashboard


Exachk &RAInformationCenter

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1683791.2








1

2

3

4

5

14

6

Copyright©2017, Oracleand/oritsaffiliates.Allrightsreserved.|

NetworkConfigurationOptions

• 10GEandIB– ZDLRAsupports10GigE(recommended)andInfiniBand–Owner’sGuide,Chapter9hasdetailsonhowtoconfigureBackupIngestoverIB

• Note:Real-TimeRedoTransportuses10GigEnetworkONLY

• VLANforsecurity– BackupandrestoretrafficfromdifferentVLANsisnotrouted.– RecoveryAppliancesupportsVLANtaggingontheingestnetwork

• ProtectedDBhostsondifferentandisolatedVLANscanbeconnecteddirectlytotheRA

15


AdjustingDefaultSettings• DonotmakeanychangestoRecoveryAppliance

– IT’SANAPPLIANCEandit’salreadyoptimized– RestrictionsandsupportedconfigurationexceptionsinMOSnote2172842.1

• UseMAX_RETENTION_WINDOW toenforcehardlimitsondataretentionforalldatabaseswithinaprotectionpolicy.–Useincaseswheretherearestringentcompliance/regulatoryrequirements

• BestpracticesistosetthevaluehigherthantheRecoveryWindowGoal.

– Backupsareforciblyremovedafterexceedingwindow– RecoveryWindowGoalsshouldbeusedtomanagebackupspaceconsumption

16








1

2

3

4

5

17

6

Copyright©2017, Oracleand/oritsaffiliates.Allrightsreserved.| 18

Backup&ConfigurationOverview

• StepstoBackup&ConfigureaDatabaseusingEnterpriseManagerCloudControl– CreateProtectionPolicyonRecoveryAppliance(RA)– AddProtectedDatabasetoRA– ConfigureBackupSettingsforProtectedDatabase– Scheduleone-timeLevel0(Full)Backupwith“CustomBackup”,thenLevel1swith“Oracle-SuggestedRecoveryApplianceBackup”


BackupBestPractices• CreateIncrementalL0(full)asfirstbackup• CreatesubsequentCumulativeL1backups“IncrementalForever”• UseSectionSizeforLargeDatafiles (e.g.1+TB)

– Use64GBasstartingpointandevaluateupto(aggregatedatafilessize/#channels)

• VirtualFullBackupCreationMonitoring– AfteraL1incrementalbackuptheRAindexesitandbuildsthecorrespondingVirtualFull.CheckEMforerrormessageslike“ORA-64760:DatabaseXYZhashadtasksinorderingwaitstateforoverXdays.”• RefertoMOSnote: DiagnosticSQLscriptfortasksinORDERING_WAITstatusonRecoveryAppliance(DocID2095949.1)

19


BackupBestPractices– Cont.• UseTransparentDataEncryption(TDE)insteadofRMANencryption• UsenativedatabasecompressioninsteadofRMANcompression• Useblockchangetrackingforallprotecteddatabases

20

– $rman target<targetstring>catalog<catalogstring>backup devicetypesbtcumulativeincrementallevel1filesperset 1sectionsize64gdatabaseplusarchivelog notbackedupfilesperset 32;


WhatToDoWithExistingBackups?

• RMANbackupstodiskorNFSshare(includingDataDomainshare)– CanbeimportedintotheRecoveryAppliancevia“polling”– BecomepartoftheIncrementalForeverstrategyontheRA

• Backupstakenusing3rd partybackupsoftware– LeavetheagentinplaceontheprotectedDBhostsuntilretentionexpires– Leveragedualbackup(disk &tape)strategyifneededininterim– Removingagentssavessystemresources

21


Restore&RecoveryBestPractices• UseRMANRestoreDatabase/RecoverDatabaseasyouwouldtoday

– NonewRMANcommandstolearn.Intelligentbuilt-inrecoverycataloginRA– RMANisawareofthevalidatedbackupsondisk,tapeorreplica.Restoreistransparentandsimple– RestoredirectlyfromtapeorRAReplicawithoutstagingonlocalRAiflocaldiskbackupsarenotpresent

• Performanceconsiderations– Maximize#ofRMANchannelsforRestoreunlesstheyareotheractivedatabasesonthetarget– RestoreoperationsarealwaysautoprioritizedwithinRAwithoutpreventingotherbackupoperations

• Bigfile Tablespace PracticesandConsiderations(recallbackupbestpracticeusingSECTIONSIZE)– Oracle11gdatabasescanrestoreinitialL0withSECTIONSIZEtoparallelizesectionsacrosschannels

• Restoringvirtualfulls (createdfromL1s)doesnotparallelizesections– Oracle12cdatabasescanrestoreL0andvirtualfulls withSECTIONSIZEparallelismacrosschannels

22


RecoveryApplianceandDataGuard

PrimaryDatabase

RemoteStandbyDatabase

DataGuardTransportsync/async

FastIncremental FastIncremental

Redo(ASYNC)

Redo(ASYNC)

MAARecommendations:• OneRecoveryAppliance(RA)perdatacenter• BackupprimaryandstandbydatabasestothelocalRA• NoRAreplicationforanydatabaseswitharemotestandbyneeded• RestoreoperationcanuseanyRAinanylocation

StandbyLocationPrimaryLocation

RAReal-TimeRedodoesNOTrequireaDataGuardLicense


RecoveryApplianceandDataGuard

• PostDataGuardroletransition– Nochangeinbackupoperations.ContinuetobackupboththeprimaryandstandbydatabasestothelocalRA

• DeployingtheZeroDataLossRecoveryApplianceinaDataGuardConfiguration– Refertohttp://www.oracle.com/technetwork/database/availability/recovery-appliance-data-guard-2767512.pdf orDeployingZeroDataLossRecoveryApplianceinaDataGuardConfiguration (UpdatedAugust2017)

MaximumAvailabilityArchitecture(MAA)WhitePaper

24


Backup&RedoFailovertoAlternateAppliance• Alternateapplianceservesasbackupstagingareawhenprimaryapplianceisunavailable,thensyncswithprimaryafterwards– Novirtualfulls createdonalternate,hencerecoverabilitynotsupported

– Spacesizedfor‘n’incrementals andarchivedlogbackupsduringprimarydowntimeperiod

• Benefits:–Preservesbackupcontinuityduringplannedmaintenance/upgrades

–PreventslocalFastRecoveryAreasfromfillingupwitharchivedlogs

25

PrimaryAppliance

XAlternateAppliance


Backup&RedoFailovertoAlternateAppliance• Backupandredofailoverdestinationwhenprimaryapplianceisunavailable(e.g.duringpatching)

26

“BF_FORWARD”PolicyonAlternateRA:STORE_AND_FORWARD=‘YES’

Incrementals

Redo

RAOsaka

RATokyo

BFOSAKA

“BF_BACKUP”PolicyonPrimaryRA

VirtualFullsMetadataSyncUp

RAOsaka->RATokyo

ReplicationServer


BackupFailovertoAlternateAppliance• Backupandredofailoverdestinationwhenprimaryapplianceisunavailable– Alternateappliancetakesoverbackupsandredotransport

27


RAOsaka

XBFOSAKA


RATokyo



–Whenprimaryapplianceisbackonline,allinterimbackupsarereplicatedfromalternateandvirtualfullbackupsarecreatedonprimary

28


RAOsaka

BFOSAKA


RATokyo



–Whenprimaryapplianceisbackonline,allinterimbackupsarereplicatedfromalternateandvirtualfullbackupsarecreatedonprimary

–Onceallvirtualfulls arecompleted,backupsandredotransportcanrestarttotheprimaryappliance

29


Incrementals

Redo

RAOsaka

RATokyo

BFOSAKA







BestPractices– Reporting,SecurityandTroubleshooting


1

2

3

4

5

30

6


RecoveryApplianceBIReports• ReportsareavailabletohelptheRecoveryApplianceadministratorunderstandresourceutilization,alerts,andhistoricaloperations

• Reportsexamplesinclude:– ActiveIncidents– APIHistory– CapacityPlanning– RecoveryWindowSummary– Top10DatabasesbyDataTransfer– ProtectedDatabasesDetails– ChargebackReports

31


ProtectedDatabase

32

KNOWthatyoudatabaseisprotected!

Topsectioncontainsthefollowinginformation:

- ProtectedDatabase- SpaceUsed- RPO/RecoveryWindow- UnprotectedWindow- LastBackuptime- LastTapeCopy- LastReplication


ChargebackReport– PayasRAStorageisUtilized(Least)

• Scenario:Thinkofthisassimilartoanmeteredmodelwherethecustomeronlypaysforutilization.Thedatabasebeingprotectedischargedonlyforthespaceutilized.

• Example:A6monthretentionwouldrampupincostsinceutilizationonmonth1islowerthanmonth6.

33

ChargeforspaceasitisusedontheRecoveryAppliance


ChargebackReport- PayasRAStorageisUtilized-cont’d

• MonthlyRAStoragespaceconsumptionforthisdatabase.

• DisplayofRAspaceusedtocalculatethechargeback.

34



• MonthlycostforthisdatabaseonRAStorage.

35



• Monthlycostforthisdatabaseontape.

36


RecoveryApplianceSecurity

• ClienttoRecoveryAppliance,orRecoveryAppliancetoClient– Upcoming:SecurityinFlight(TCPS,HTTPS)– AddingaprotecteddatabaseRecoveryApplianceVPCusercredentialstoanexistingOIDwallet(DocID2211759.1)

• SecurityintheRecoveryAppliance– RecoveryApplianceadministratorsresponsibilities

• CreateVirtualPrivateCatalog(VPC)User• AssignprotecteddatabasestoaspecificVPCUser• TheprotecteddatabaseadministratorcanseealldatabasesthatshareacommonVPCuser

Customersrequiringendtoendsecurity

37


RecoveryApplianceImportantNotes

• Wheneveryouopenaservicerequest– SRDC- ZeroDataLossRecoveryAppliance(ZDLRA)DataCollection(DocID2154189.1)

• FortroubleshootingRecoveryApplianceissuesreferto– ZDLRADetailedTroubleshootingMethodology(DocID2066528.1)– ZDLRASystemActivityScript(DocID2275176.1)

• WhenupgradingtheRecoveryApplianceSoftware– ZeroDataLossRecoveryApplianceSupportedVersions(DocID1927416.1)– ZeroDataLossRecoveryApplianceUpgradeandPatching(DocID2028931.1)

38






BestPractices– Reporting,SecurityandTroubleshooting


1

2

3

4

5

39

6

CFM

www.cfm.fr www.cfm.fr

Presented by

ZDLRA implementation at CFM

© CFM 2017

Gabriel NitulescuProject Leader

October 04, 2017

CFM

www.cfm.fr

Fundamental research applied to financial marketsCFM invests in Science, Technology and Finance25 years of experience in managing trading systemsA rational process that produces robust Trading AlgorithmsProprietary software able to execute & control large volumes of data180 PeopleOffices in Paris, London, New York, Tokyo

Who Are We?

© CFM 2017 41

CFM

www.cfm.fr

Data Protection Desired Architecture

© CFM 2017 42

FREP

host@frep

DB_A_frep_00

host@frcn

DB_A_frcn_00DataGuard

Dat

abas

eba

ckup

Arch

ived

logs

bac

kup

data

base

back

up

Arch

ived

log

back

up

Backup system @ FREP Backup System @ FRCN

FREP

CFM

www.cfm.fr

Workload Characterization

© CFM 2017 43

CFM

www.cfm.fr

Oracle Best Practices Disk to Disk to Tape► Daily to Disk

RUN {

RECOVER COPY OF DATABASE WITH TAG 'UPDATABLE';

BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'UPDATABLE' DATABASE;

BACKUP DEVICE TYPE SBT ARCHIVELOG ALL NOT BACKED UP ; }

► Weekly to TapeRUN { BACKUP DEVICE TYPE SBT RECOVERY AREA; }

MAA Best Practices Architecture► Two Independent Data Centers with Data Guard► No special procedures in case of disaster or maintenanceProduction Impacts► Large FRA size (1,7 DB Size)► High CPU Utilization During Backup► High Bandwidth Utilization for Weekly Backups

Legacy Data Protection Strategy

© CFM 2017 44

+RECO

+DATA

BD_A DB_B

Image copy 24 TB 38 TB

Inc0 5 TB 12 TB

Inc1 0.3 TB 0.2 TB

Archives / day 3 TB 1 TB

Flashback logs / day 1 TB 0.3 TB

CFM

www.cfm.fr

Technical advantages (Virtual Full & Real-Time Redo Transport)► Reduce CPU required for backup => no more backup window => sizing => licenses

► Backup & Recovery performances

Financial Aspects (Lower TCO)► Zero Data Loss Recovery Appliance Lower Cost than Primary Storage (FRA on Production Server)

> Savings of 40%

Why ZDLRA?

© CFM 2017 45

CFM

www.cfm.fr

White Paper Deploying the Zero Data Loss Recovery Appliance in a Data Guard Configuration► OEM based implementation

► Minimize downtime

OEM implementation

© CFM 2017 46

CFM

www.cfm.fr

SQL> exec DBMS_RA.ADD_DB (db_unique_name=> 'PRODOMR_FRCN_00', protection_policy_name => 'CFM_003_DAYS', reserved_space=>'51G');SQL> exec DBMS_RA.GRANT_DB_ACCESS (db_unique_name => 'PRODOMR_FRCN_00',username => 'vpccfm');SQL> select DB_UNIQUE_NAME,DBID,DB_KEY from ra_database ORDER BY DB_UNIQUE_NAME;

DGMGRL> switchover to 'prodomr_frcn_00';

[oracle@<DB_server_FREP>]$ rman target /@PRODOMR_FRCN_00_DR catalog /@zfrcn00_catalogRMAN> register database;database registered in recovery catalogstarting full resync of recovery catalogfull resync completeRMAN> show all;RMAN configuration parameters for database with db_unique_name PRODOMR_FRCN_00 are:CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';CONFIGURE CONTROLFILE AUTOBACKUP ON;CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%U' PARMS "SBT_LIBRARY=/u01/app/oracle/product/12.1.0.2/dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/wallet credential_alias=ZFRCN00_CATALOG')";CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FRCN_00' CONNECT IDENTIFIER 'PRODOMR_FRCN_00_DR';CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FREP_00' CONNECT IDENTIFIER 'PRODOMR_FREP_00_DR';CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO 'SBT_TAPE';

DGMGRL> switchover to 'prodomr_frep_00';

Enrolling Protected Databases

© CFM 2017 47

SQL> exec DBMS_RA.ADD_DB (db_unique_name=> 'PRODOMR_FREP_00', protection_policy_name => 'CFM_003_DAYS', reserved_space=>'51G');SQL> exec DBMS_RA.GRANT_DB_ACCESS (db_unique_name => 'PRODOMR_FREP_00',username => 'vpccfm');SQL> select DB_UNIQUE_NAME,DBID,DB_KEY from ra_database ORDER BY DB_UNIQUE_NAME;

[oracle@<DB_server_FREP>]$ rman target /@PRODOMR_FREP_00_DR catalog /@zfrep00_catalogRMAN> register database;database registered in recovery catalogstarting full resync of recovery catalogfull resync completeRMAN> show all;RMAN configuration parameters for database with db_unique_name PRODOMR_FREP_00 are:CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';CONFIGURE CONTROLFILE AUTOBACKUP ON;CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%U' PARMS "SBT_LIBRARY=/u01/app/oracle/product/12.1.0.2/dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/wallet credential_alias=ZFREP00_CATALOG')";CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FRCN_00' CONNECT IDENTIFIER 'PRODOMR_FRCN_00_DR';CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FREP_00' CONNECT IDENTIFIER 'PRODOMR_FREP_00_DR';CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO 'SBT_TAPE';

Enrolling Primary Protected Database with Recovery Appliance Repeat for Standby Protected Database with Recovery Appliance

CFM

www.cfm.fr

CLI Backup Scripts

© CFM 2017 48

$ cat backup_inc_l0.rman

run {

backup device type sbt tag 'INCFOREVER' cumulative incremental level 0 filesperset 1 section size 64g database plus archivelog not backed up filesperset 32;}

$ cat backup_inc_l1.rman

run {

backup device type sbt tag 'INCFOREVER' cumulative incremental level 1 filesperset 1 section size 64g database plus archivelog not backed up filesperset 32;}

$time rman target /@PRODOMR_FREP_00_DR catalog /@zfrep00_catalog cmdfile=backup_inc_l1.rman log=backup_inc_l1_${ORACLE_SID}.`date +"%Y%m%d%H%M%S"`.log &

allocated channel: ORA_SBT_TAPE_1

channel ORA_SBT_TAPE_1: RA Library (ZFREP) SID=47483A6E3C363BB5E053345B430A24E2

…

$time rman target /@PRODOMR_FRCN_00_DR catalog /@zfrcn00_catalog cmdfile=backup_inc_l1.rman log=backup_inc_l1_${ORACLE_SID}.`date +"%Y%m%d%H%M%S"`.log &

channel ORA_SBT_TAPE_1: RA Library (ZFRCN) SID=480AB266A1C90E9EE0533E5B460A5440

…

skipping archived logs of thread 1 from sequence 43350 to 43535; already backed up

…

Level 0: One time

Level 1: Daily

Actual OEM limitation

RMAN Backup Job Output

RMAN Backup Job Scripts

CFM

www.cfm.fr

Data Protection Architecture with Recovery Appliance

© CFM 2017 49

FREP

efrep00-vm01

DB_A_frep_00

back

up

FREP

efrcn00-vm01

DB_A_frcn_00

back

up

DataGuard

CFM

www.cfm.fr

Data Guard Concepts and Administration ► 6 Redo Transport Services

> 6.2.1.2 Redo Transport Authentication Using a Password File

SQL> create user vpccfm identified by xxxxxx;SQL> grant sysoper to VPCCFM;SQL> select * from V$PWFILE_USERS;USERNAME SYSDB SYSOP SYSAS------------------------ ----- -----SYS TRUE TRUE FALSEVPCCFM FALSE TRUE FALSESQL> ALTER SYSTEM SET redo_transport_user = 'VPCCFM' SCOPE=SPFILE;

SQL> ho scp orapwd${ORACLE_SID}

SQL> shutdown immediate;SQL> startup;SQL> show parameter redoNAME TYPE VALUE----------------------------------- ------------------------------redo_transport_user string VPCCFM

CLI real time redo: Redo Transport Authentication Using a Password File

© CFM 2017 50

All standby databases

Same User for Redo Transport and Backup (VPC)

CFM

www.cfm.fr

Enable Real-Time Redolog Shipping

© CFM 2017 51

@ FREP SQL> alter system set log_archive_dest_4='SERVICE=zfrep00_catalog VALID_FOR=(ALL_LOGFILES, ALL_ROLES) ASYNC DB_UNIQUE_NAME=zfrep' scope=both sid='*';

@ FRCN SQL> alter system set log_archive_dest_4='SERVICE=zfrcn00_catalog VALID_FOR=(ALL_LOGFILES, ALL_ROLES) ASYNC DB_UNIQUE_NAME=zfrcn' scope=both sid='*';

DGMGRL> add recovery_appliance ZFREP as connect identifier is 'ZFREP00_CATALOG';DGMGRL> enable recovery_appliance ZFREP;DGMGRL> add recovery_appliance ZFRCN as connect identifier is 'ZFRCN00_CATALOG';DGMGRL> enable recovery_appliance ZFRCN;DGMGRL> show configuration;Configuration - prodomr_dgProtection Mode: MaxPerformanceMembers:prodomr_frep_00 - Primary databaseprodomr_frcn_00 - Physical standby database zfrep - Backup appliance zfrcn - Backup appliance

No cascade redo propagation

SQL as rasys@ZFRCN00 > selectDB_UNIQUE_NAME, NZDL_ACTIVE, SPACE_USAGE/1024 as SPACE_USAGE_TB, DISK_RESERVED_SPACE/1024 as DISK_RESERVED_SPACE_TB, round(DEDUPLICATION_FACTOR,2)

fromRA_DATABASE

order by DB_UNIQUE_NAME;

DB_UNIQUE_NAME NZD SPACE_USAGE_TB DISK_RESERVED_SPACE_TB ROUND(DEDUPLICATION_FACTOR,2)-------------------------------- --- -------------- ---------------------- ---------------------------------------PRODOMR_FRCN_00 YES .01 .05 2.04

Configuring Log Archive Destination to RAUpdating DGMGRL Configuration

Confirming Configuration

CFM

www.cfm.fr

Real-Time Data Protection Architecture with Recovery Appliance

© CFM 2017 52

FREP

efrep00-vm01

DB_A_frep_00

back

up

FREP

efrcn00-vm01

DB_A_frcn_00

back

up

DataGuard

Rea

l tim

e R

edo

Ship

ping

Red

oSh

ippi

ng

CFM

www.cfm.fr

efrcn00-vm01efrep00-vm01

Real-Time Data Protection with Recovery Appliance & Data Guard Broker

© CFM 2017 53

FREP

DB_A_frep_00

back

up

FREP

DB_A_frcn_00

back

up

DataGuard

Rea

l tim

e R

edo

Ship

ping

* RDBMS <= 12.1.0.2

* RDBMS >= 12.1.0.2Active far Sync

Rea

l tim

e R

edo

Ship

ping

CFM

www.cfm.fr

Backup Elapsed Time & Resource Usage

© CFM 2017 54

• DB Size = 12TB• RMAN Backup Channels = 8

CFM

www.cfm.fr

Results 1 of 2

© CFM 2017 55

CFM

www.cfm.fr

Results 1 of 2

© CFM 2017 56

CFM

www.cfm.fr

Results 2 of 2

© CFM 2017 57

CFM

www.cfm.fr

Results 2 of 2

© CFM 2017 58

CFM

www.cfm.fr

Summary

© CFM 2017 59

Technical:Minimized Backup WindowOffloaded Database Server CPUIncreased Recovery Performance

o Virtual full backup, Compression

Ability to implement the desired architecture

Price:Lower TCOReduce impact of CPU for backup => licenses« User TB » on RA vs FRA

Project:Implementation is less complex than first impression

Better OEM integrationMore Detailed DocumentationMore Oracle University CoursewareImproved Support Skills

Positive Results Improvements Needed


Summary/Q&A


Summary• It’sallaboutsimplification• Simplerenvironment=betterstability• Followthebestpractices

– It’sanAppliance!– FollowMOSnotes– Patchregularly


MeetusinthePlatformShowcaseAreainMosconeWest!

Copyright©2017, Oracleand/oritsaffiliates.Allrightsreserved.| 63

StayInformedAfterOpenWorld

Twitter:@OracleZDLRA and@OracleZFS

LinkedIn:OracleITInfrastructuregroup


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

64


Documents

Zero Data Loss Recovery Appliance: Development · Backup Best Practices • Create Incremental L0 (full) as first backup • Create subsequent Cumulative L1 backups “Incremental