- oracle maa best practices series 1. e-business suite on exadata 2. siebel on exadata 3....

<Insert Picture Here>

Exadata MAA Best Practices SeriesSession 9: Exadata Backup & RecoveryAndrew BabbAndrew BabbPrincipal Member of Technical Staff

Exadata MAA Best Practices Series

<Insert Picture Here>1. E-Business Suite on Exadata 2. Siebel on Exadata 3. PeopleSoft on Exadata 4. Exadata and OLTP Applications 5. Using Resource Manager on Exadata6. Migrating to Exadata 7. Using DBFS on Exadata 8. Exadata Monitoring 9. Exadata Backup & Recovery 10. Exadata MAA 11. Troubleshooting Exadata 12. Exadata Patching & Upgrades 13. Exadata Health Check14. How do we address future sessions? How can

2

customers request topics?

Common Abbreviations

• Recovery Manager (RMAN)y g ( )• Oracle Secure Backup (OSB)• Linear Tape-Open v4 (LTO-4)• OpenFabrics Enterprise Distribution (OFED)• Internet Protocol over InfiniBand (IPoIB)

M i T i i U it (MTU)• Maximum Transmission Unit (MTU)• Exadata Hybrid Columnar Compression (EHCC)

3

Session TopicsAgendage da

• Key Points and Customer Take-Awaysy y

• Business Take Away

• Best Practices Take Away

4

Key Points and Customer Take-Aways

<Insert Picture Here>

Key Points and Customer Take-AwaysCustomer Take-Aways

5

Exadata Backup & Recovery

1. Exadata is backed up and

Sun Fire X4170 Oracle Secure Backup Administrative Server

recovered using RMAN

2 E d t b k d

Fiber Channel

SAN

2. Exadata backup and recovery is very fast Sun Fire X4275

Oracle Secure Media Servers

3. Validated strategy, configuration and steps

Oracle Tape

Library

Oracle ExadataStorage Servers

6

Key Point #1“Exadata is backed up and recovered using RMAN”Business Value Add“Backing up an Oracle database on Exadata is the same as backing up any other Oracle database.”

Key Point #1“E d t i b k d d d i“Exadata is backed up and recovered using RMAN”

B i V l AddBusiness Value Add“Backing up an Oracle database on Exadata is h b ki h O lthe same as backing up any other Oracle

database.”

7


• RMAN is fully integratedy g

• Comprehensive block verification

• Utilize all processing capacity

• Offload work to Exadata Storage Servers

• Utilize the same RMAN scripts

8


• Simple Operations– Simple RMAN commands to backup, restore or recover the

database – same as any other Oracle platform

• RMAN Examples

RMAN> backup database;

RMAN> restore database;RMAN> restore database;

RMAN> recover database;

9

Key Point #2“Exadata backup and recovery is very fast”p y yBusiness Value Add“Save time and resources”

Key Point #2“E d t b k d i f t”“Exadata backup and recovery is very fast”

Business Value Add“Save time and resources”

10


• Backup and Restore Internal to the Database Machine– 18 TB/Hr full image backups– 10-50 TB/Hr effective backup rate for incremental backups – 24 TB/Hr restore rates24 TB/Hr restore rates– 2.1 TB/Hr recovery rates– Above rates pertain to physical files. With compression,

effective backup/restore rates will multiplyeffective backup/restore rates will multiply

11


• Top limiting factors– Number of tape drives (applicable for the rates below)– External Network or Configuration setup outside of the Database

MachineB k d R t E t l t th D t b M hi• Backup and Restore External to the Database Machine– Backup rates

• 179MB/sec per LTO4 tape drive8 6TB/H f 14 t d i• 8.6TB/Hr for 14 tape drives

• 29TB/Hr with 64 tape drives.• Effective backup rates of between 8TB/hour and 40TB/hour

R t t– Restore rates• 162MB/sec per tape drive• 7.8TB/hr for Full Rack Configuration

12


• Summary of Key Point #2y y– Backup, Restore and Recovery operations are very fast– Most database backed up or restored in less than 4 hours

Save time and resources– Save time and resources

13

Key Point #3“Validated strategy, configuration and steps”gy, g pBusiness Value Add“More Benefits, Less Work”

Key Point #3“V lid t d t t fi ti d t ”“Validated strategy, configuration and steps”

Business Value Add“More Benefits, Less Work”

14

Exadata Backup & RecoveryBackups Internal to Database Machineac ups e a o a abase ac e

• Disk configuration layoutg y• Performance rates• Strategy and Benefits• Backup best practices• Restore best practices

S i t E l• Script Examples

15

Exadata Backup & Recovery (Internal)Disk configuration layouts co gu a o ayou

The faster (outer) 40% of the disk is assigned to the DATA AreaThe slower (inner) 60% of the disk is assigned to the RECO Area

• Recommended disk group configuration • Can be configured automatically during deployment

16

Exadata Backup & Recovery (Internal)Performance Ratese o a ce a es

• Backup rate– 18TB/Hr for Full Rack configurations– Effectively 10-50 TB/Hr for incremental backups

• Restore rate• Restore rate– 18 - 24TB/hr for Full Rack Configuration

• Typical Redo Apply (recovery) rateyp pp y ( y)– 200MB redo/sec (720GB redo/hour) for OLTP Workloads– 600MB redo/sec (2.1TB redo/hour) for Direct Load

WorkloadsWorkloads

17

Exadata Backup & Recovery (Internal)Strategy and BenefitsS a egy a d e e s

• Use RMAN incrementally updated backupsy– Image Copy created on initial backup only– Nightly Incremental Backups

Incremental merges on a 24 hour delay basis– Incremental merges on a 24 hour delay basis

• Key advantages over tape only based backups strategies– Potential for using backups directly with no restore– Reduce backup windows and resources– Faster recovery for corruptions and data file recoveryFaster recovery for corruptions and data file recovery

18

Exadata Backup & Recovery (Internal)Backup best practicesac up bes p ac ces

• Create a Database Service that runs on all instances– Use incremental backups and block change tracking– Data block inspection is offloaded to Exadata

• For highest throughput allocate 16 RMAN Channels• For highest throughput allocate 16 RMAN Channels– Listener Load Balancing across all instances– Use fewer channels if highest throughput is not needed

• Set init.ora parameter_file_size_increase_increment=2143289344

Minimal CPU Impact Observed• Minimal CPU Impact Observed

19

Exadata Backup & Recovery (Internal) Restore best practiceses o e bes p ac ces

• Create a Database Service that runs on all instances– Use 2 RMAN channels per instance for X2-2 and V2 – Use 8 RMAN channels per instance for X2-8

20

Exadata Backup & Recovery (Internal) Script ExamplesSc p a p es

• RMAN configurationconfigure default device type to disk;configure default device type to disk;configure device type disk parallelism 16;

• RMAN script for nightly incremental level 1 backupp g y prun {

recovercopy of databasewith tag full database;with tag full_database;

backupincremental level 1for recover of copy with tag full databasewith tag full_databasedatabase;

}

21

Exadata Backup & RecoveryBackups External to Database Machineac ups e a o a abase ac e

• Two validated solutions– Disk Backup on Exadata Storage– Tape Backup with OSB

• Otherwise using third party solution

22

Exadata Backup & RecoveryBackups External to Database Machine using Exadata Storageac ups e a o a abase ac e us g ada a S o age

• Configuration, Strategy and Benefitsg gy• Disk Configuration Layout

23

Exadata Backup & Recovery (External) Alternative Backup Area on Exadata Storagee a e ac up ea o ada a S o age

O l D t b O l E d tOracle Database Machine

Oracle ExadataStorage Servers

InfiniBand Network

24

Exadata Backup & Recovery (External) Disk configuration layouts co gu a o ayou


25

Exadata Backup & RecoveryBackups External to Database Machine to Tape with OSBac ups e a o a abase ac e o ape OS

• Disk Configuration Layoutg y• Performance rates• Strategy and Benefits• Backup best practices• Restore best practices

S i t• Script• OSB Benefits and best practices

26

Exadata Backup & RecoveryMAA Validated Architecturea da ed c ec u e

O l St T kO l D t b

Sun Fire X4170 Oracle Secure Backup

Oracle StorageTek SL500

Oracle Database Machine

Oracle Secure Backup Administrative Server

2 Sun Fire X42752 Sun Fire X4275 Oracle Secure Backup Media

ServersInfiniBandNetwork

Fiber ChannelSAN

27

Exadata Backup & Recovery (External) Exadata Storage Server Grid Disk layoutada a S o age Se e G d s ayou

The faster (outer) 80% of the disk is assigned to the DATA AreaThe slower (inner) 20% of the disk is assigned to the RECO Area


28

Exadata Backup & Recovery (External) Performance ratese o a ce a es

• Top limiting factors– Number of tape drives (applicable for the rates below)– External Network or Configuration setup outside of the

Exadata Database Machine• Backup rates

– 179MB/sec per LTO4 tape drive– 8.6TB/Hr for 14 tape drivesp– 29TB/Hr with Database Machine Configured with 64 LTO4

tape drives.• Restore rates

– 162MB/sec per tape drive– 7.8TB/hr for Full Rack Configuration

29

Exadata Backup & Recovery (External) Strategy and BenefitsS a egy a d e e s

• Oracle Database tape backup strategy:gy– Weekly RMAN level 0 (full) backup– Daily RMAN cumulative incremental level 1 backup

• To scale and maintain availability:• To scale and maintain availability:– Use at least 2 media servers with dual ported HCA for

bonding– Add tape drives until media server’s bandwidth is consumed– Add media server and tape drives when bandwidth consumed

• Tape based backups scale linearly by adding MediaTape based backups scale linearly by adding Media Servers and Tape Drives

30

Exadata Backup & Recovery (External) Benefits and Trade-Offs of Tape only solutione e s a d ade O s o ape o y so u o

• Benefits– Fault Isolation from Exadata Storage– Maximizes Oracle Database Machine capacity and bandwidth

Move backup off-site easily– Move backup off-site easily– Keep multiple copies of backups in a cost effective manner

• Trade-Offs– Disk-based solutions have better recovery times for data and

logical corruptions and certain tablespace point in timelogical corruptions and certain tablespace point in time recovery scenarios

– No differential incremental backups are available

31

Exadata Backup & Recovery (External) Configuration Best Practices for Tape BackupCo gu a o es ac ces o ape ac up

• Create a Database Service that runs on all instances– Use incremental backups and block change tracking

• Data block inspection is automatically offloaded to ExadataUse tape hardware compression– Use tape hardware compression

• Allocate 1 RMAN channel per tape drivep p– Listener Load Balancing between all instances

• Spreads the backup I/O’s evenly over all database nodes

32

Exadata Backup & Recovery (External) Configuration Best Practices for Tape RestoreCo gu a o es ac ces o ape es o e

• Create a Database Service that runs on all instances– Allocate 1 RMAN Channel per tape drive

33

Exadata Backup & Recovery (External) GigE v 10GigE v IPoIBG g 0G g o

• Smaller database can be backed up via GigEg– Offers backup rates of approx 960MB/sec

• Larger database can be backed up via10GigEC b t d i t i ti 10Gi E t k– Can be connected into an existing 10GigE network

– Offers backup rates of approx 8GB/sec

• Fastest database backup achieved via InfiniBandp– Get dedicated Media Servers that connect to tape library– Offers backup rates of up to 12GB/sec

34

Exadata Backup & Recovery (External) InfiniBand Configuration Best Practices for Tapea d Co gu a o es ac ces o ape

• Database nodes and Media Server configurationg– Use Oracle Enterprise Linux on the Media Server– Use same kernel and OFED packages as used on Oracle

Database MachineDatabase Machine– Enable IPoIB connected mode and MTU changes on the

media server– No changes on database nodes needed– No changes on database nodes needed

• Minimal CPU impactp– Observed less than 1 CPU Core used per instance

35

Exadata Backup & Recovery (External) Script ExamplesSc p a p es

• RMAN configurationconfigure default device type to sbt;configure default device type to sbt;configure device type sbt parallelism 14;

• RMAN script for weekly backupp y prun {

backup incremental level 0 database tag 'weekly_level0';backup archivelog all not backed up;

}}

• RMAN script for daily backuprun {

backup cumulative incremental level 1 database tag 'daily_level1‘backup archivelog all not backed up tag 'archivelogs';

}

36

Exadata Backup & Recovery (External) Oracle Secure Backup AdvantagesO ac e Secu e ac up d a ages

• Oracle Secure Backup (OSB) tape-based backup ( )advantages– Fastest database backup to tape via tight integration with

RMANRMAN• Unused block compression• Inactive Undo blocks not backed up

Very low cost– Very low cost– MAA Validated

37

Exadata Backup & Recovery (External) Oracle Secure Backup Configuration Best PracticesO ac e Secu e ac up Co gu a o es ac ces

• Configure the Preferred Network Interface (PNI) to g ( )direct the OSB traffic over the InfiniBand network interface

ob> lspni (List Preferred Network Interface)mediaserver1:

PNI 1:interface: mediaserver1 ibinterface: mediaserver1-ibclients: dbnode1, dbnode2, dbnode3, dbnode4, dbnode5, dbnode6, dbnode7, dbnode8

PNI 2:interface: mediaserver1clients: adminserver

38

Exadata Backup & Recovery (External) Oracle Secure Backup & Recovery Best PracticesO ac e Secu e ac up & eco e y es ac ces

• Backup and Recovery Performance and Best yPractices for Sun Oracle Database Machine and Exadata

– http://www.oracle.com/technetwork/database/features/availability/maa-tech-wp-sundbm-backup-11202-183503.pdf

39

Exadata Backup & Recovery (External) Third Party Media Management productsd a y ed a a age e p oduc s

• Third party vendors test and validate their own yproducts– Contact the vendor for configuration best practices

No additional certification required for databases running on– No additional certification required for databases running on the Oracle Database Machine

– Most of the best practices are applicable

• Many Oracle Database Machine customers are successfully using 3rd party tape backup productssuccessfully using 3 party tape backup products

40

Exadata Backup & Recovery (External) Using a Physical Standby database for backupsUs g a ys ca S a dby da abase o bac ups

• Backing up using a Physical Standby databaseg g y y– Offloads the backup to the standby environment– Reduce backup times with fast incremental backups

Eliminate impact to the primary environment– Eliminate impact to the primary environment

• Additional Data Guard benefits– Auto block repair with zero impact on application – Offload reads and reporting, backups, and testing

Used for planned maintenance and rolling database upgrade– Used for planned maintenance and rolling database upgrade– Used for disaster recovery or high availability with Data Guard

Fast-Start Failover

41

Business Takeaways

Business Takeaways

42

Exadata Backup & RecoveryBusiness Takeawaysus ess a ea ays

• #1: Works for any database of any size

• #2: Exadata makes backing up database faster– Potentially reducing backup windowsy g p

• #3: The investment in RMAN follows through to the Oracle Database MachineDatabase Machine

• #4: Save time and cost by being able to utilize current backup infrastructurebackup infrastructure

• #5: MAA Validated

43

Best Practice Takeaways

Best Practice Takeaways

44

Exadata Backup & RecoveryBest Practice Takeawayses ac ce a ea ays

• #1: MAA Validated– http://www.oracle.com/technetwork/database/features/availab

ility/maa-tech-wp-sundbm-backup-11202-183503.pdf– http://www.oracle.com/technetwork/database/features/availabhttp://www.oracle.com/technetwork/database/features/availab

ility/maa-tech-wp-sundbm-backup-final-129256.pdf– http://www.oracle.com/technetwork/database/features/availab

ility/maa-wp-dr-dbm-130065.pdfility/maa wp dr dbm 130065.pdf

• #2: RMAN knowledge is applicable in an Oracle D t b M hi i tDatabase Machine environment

45

Best PracticesAdditional Resources sponsored by MAA and X-TeamAdditional Resources sponsored by MAA and X Team

• MAA and Exadata OTN website contains best practices and different architectural solutions

– MAA OTN website:http://www.oracle.com/goto/MAASun Oracle Database Machine and Exadata OTN website– Sun Oracle Database Machine and Exadata OTN websitehttp://www.oracle.com/technetwork/database/exadata/index-089737.html

• Openworld presentations– http://openworld.vportal.netp p p

46

SponsorsExadata MAA Team and X TeamExadata MAA Team and X Team

• Operational and Configuration best practices g– Optimized and integrated for Exadata – Generic practices for other platforms

Examples: Migration Backup/Recovery Monitoring– Examples: Migration, Backup/Recovery, Monitoring, Troubleshooting, Patching, MAA, Consolidation, Active Data Guard, Cloning/Reporting, Application Failover

• Applications MAA and Scalability• Applications MAA and Scalability – Optimized and integrated for Exadata and Exalogic– Examples: E-Business Suite, Siebel, Peoplesoft, Fusion

Middleware

• Exadata Strategic Customer Program

47

Copyright

48

Copyright

49

- oracle maa best practices series 1. e-business suite on exadata 2. siebel on exadata 3....

Documents