Exadata MAA Best Practices Series Session 9: Exadata

Exadata MAA Best Practices Series Session 9: Exadata
<Insert Picture Here>
Exadata MAA Best Practices Series
Session 9: Exadata Backup & Recovery
Andrew Babb
Principal Member of Technical Staff
Exadata MAA Best Practices Series
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
E-Business Suite on Exadata
Siebel on Exadata
PeopleSoft on Exadata
Exadata and OLTP Applications
Using Resource Manager on Exadata
Migrating to Exadata
Using DBFS on Exadata
Exadata Monitoring
Exadata Backup & Recovery
Exadata MAA
Troubleshooting Exadata
Exadata Patching & Upgrades
Exadata Health Check
How do we address future sessions? How can
customers request topics?
<Insert Picture Here>
2
Common Abbreviations
•
•
•
•
•
•
•
Recoveryy Manager
g ((RMAN))
Oracle Secure Backup (OSB)
Linear Tape-Open v4 (LTO-4)
OpenFabrics Enterprise Distribution (OFED)
Internet Protocol over InfiniBand (IPoIB)
M i
Maximum
T
Transmission
i i U
Unit
it (MTU)
Exadata Hybrid Columnar Compression (EHCC)
3
Session Topics
Agenda
ge da
• Keyy Points and Customer Take-Aways
y
• Business Take Away
• Best Practices Take Away
4
Key Points and Customer Take-Aways
<Insert Picture Here>
Key Points and
Customer Take-Aways
5
Exadata Backup & Recovery
Sun Fire X4170
Oracle Secure Backup
Administrative Server
1. Exadata is backed up and
recovered using RMAN
Fiber
Channel
SAN
2 E
2.
Exadata
d t backup
b k and
d
recovery is very fast
Sun Fire X4275
Oracle Secure
Media Servers
3. Validated strategy,
configuration and steps
Oracle Exadata
Storage Servers
Oracle
Tape
Library
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
“Exadata
“E
d t is
i backed
b k d up and
d recovered
d using
i
RMAN”
B i
Business
Value
V l Add
“Backing up an Oracle database on Exadata is
the
h same as backing
b ki up any other
h Oracle
O l
database.”
7
Exadata Backup & Recovery
• RMAN is fullyy integrated
g
• Comprehensive block verification
• Utilize all processing capacity
• Offload work to Exadata Storage Servers
• Utilize the same RMAN scripts
8
Exadata Backup & Recovery
• 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> recover database;
9
Key Point #2
“Exadata backup
p and recovery
y is very
y fast”
Business Value Add
“Save time and resources”
Key Point #2
“E d t backup
“Exadata
b k and
d recovery is
i very fast”
f t”
Business Value Add
“Save time and resources”
10
Exadata Backup & Recovery
• 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 rates
2.1 TB/Hr recovery rates
Above rates pertain to physical files. With compression,
effective backup/restore rates will multiply
11
Exadata Backup & Recovery
• Top limiting factors
– Number of tape drives (applicable for the rates below)
– External Network or Configuration setup outside of the Database
Machine
• Backup
B k and
d Restore
R t
External
E t
l to
t the
th Database
D t b
Machine
M hi
– Backup rates
• 179MB/sec per LTO4 tape drive
• 8.6TB/Hr
8 6TB/H for
f 14 ttape drives
di
• 29TB/Hr with 64 tape drives.
• Effective backup rates of between 8TB/hour and 40TB/hour
– Restore
R t
rates
t
• 162MB/sec per tape drive
• 7.8TB/hr for Full Rack Configuration
12
Exadata Backup & Recovery
• Summaryy of Keyy Point #2
– Backup, Restore and Recovery operations are very fast
– Most database backed up or restored in less than 4 hours
– Save time and resources
13
Key Point #3
“Validated strategy,
gy, configuration
g
and steps”
p
Business Value Add
“More Benefits, Less Work”
Key Point #3
“V lid t d strategy,
“Validated
t t
configuration
fi
ti and
d steps”
t
”
Business Value Add
“More Benefits, Less Work”
14
Exadata Backup & Recovery
Backups
ac ups Internal
e a to
o Database
a abase Machine
ac e
•
•
•
•
•
•
Disk configuration
g
layout
y
Performance rates
Strategy and Benefits
Backup best practices
Restore best practices
S i tE
Script
Examples
l
15
Exadata Backup & Recovery (Internal)
Disk
s co
configuration
gu a o layout
ayou
The faster (outer) 40% of the disk is assigned to the DATA Area
The 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
e o a ce Rates
a es
• Backup rate
– 18TB/Hr for Full Rack configurations
– Effectively 10-50 TB/Hr for incremental backups
• Restore rate
– 18 - 24TB/hr for Full Rack Configuration
• Typical
yp
Redo Apply
pp y (recovery)
(
y) rate
– 200MB redo/sec (720GB redo/hour) for OLTP Workloads
– 600MB redo/sec (2.1TB redo/hour) for Direct Load
Workloads
17
Exadata Backup & Recovery (Internal)
Strategy
S
a egy a
and
d Benefits
e e s
• Use RMAN incrementallyy updated backups
– Image Copy created on initial backup only
– Nightly Incremental Backups
– 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 recovery
18
Exadata Backup & Recovery (Internal)
Backup
ac up bes
best p
practices
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
– 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
19
Exadata Backup & Recovery (Internal)
Restore
es o e bes
best p
practices
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
Sc
p Examples
a p es
• RMAN configuration
configure default device type to disk;
configure device type disk parallelism 16;
• RMAN script
p for nightly
g y incremental level 1 backup
p
run {
recover
copy of database
with tag full_database;
full database;
backup
incremental level 1
for recover of copy
with tag full_database
full database
database;
}
21
Exadata Backup & Recovery
Backups
ac ups External
e a to
o Database
a abase Machine
ac e
• Two validated solutions
– Disk Backup on Exadata Storage
– Tape Backup with OSB
• Otherwise using third party solution
22
Exadata Backup & Recovery
Backups
ac ups External
e a to
o Database
a abase Machine
ac e us
using
g Exadata
ada a S
Storage
o age
• Configuration,
g
Strategy
gy and Benefits
• Disk Configuration Layout
23
Exadata Backup & Recovery (External)
Alternative
e a e Backup
ac up Area
ea o
on Exadata
ada a S
Storage
o age
Oracle
O
l Database
D t b
Machine
Oracle
O
l Exadata
E d t
Storage Servers
InfiniBand Network
24
Exadata Backup & Recovery (External)
Disk
s co
configuration
gu a o layout
ayou
• Recommended disk group configuration
• Can be configured automatically during deployment
25
Exadata Backup & Recovery
Backups
ac ups External
e a to
o Database
a abase Machine
ac e to
o Tape
ape with OS
OSB
•
•
•
•
•
•
•
Disk Configuration
g
Layout
y
Performance rates
Strategy and Benefits
Backup best practices
Restore best practices
S i t
Script
OSB Benefits and best practices
26
Exadata Backup & Recovery
MAA Validated
a da ed Architecture
c ec u e
Oracle
O
l StorageTek
St
T k
SL500
Oracle
O
l Database
D t b
Machine
Sun Fire X4170
Oracle Secure Backup
Administrative Server
InfiniBand
Network
2 Sun Fire X4275
Oracle Secure
Backup Media
Servers
Fiber Channel
SAN
27
Exadata Backup & Recovery (External)
Exadata
ada a S
Storage
o age Se
Server
e G
Grid
d Disk
s layout
ayou
The faster (outer) 80% of the disk is assigned to the DATA Area
The slower (inner) 20% of the disk is assigned to the RECO Area
• Recommended disk group configuration
• Can be configured automatically during deployment
28
Exadata Backup & Recovery (External)
Performance
e o a ce rates
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
p drives
– 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
S
a egy a
and
d Benefits
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:
– 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 Media
Servers and Tape Drives
30
Exadata Backup & Recovery (External)
Benefits
e e sa
and
d Trade-Offs
ade O s of
o Tape
ape o
only
y so
solution
u o
• Benefits
–
–
–
–
Fault Isolation from Exadata Storage
Maximizes Oracle Database Machine capacity and bandwidth
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 time
recovery scenarios
– No differential incremental backups are available
31
Exadata Backup & Recovery (External)
Configuration
Co
gu a o Best
es Practices
ac ces for
o Tape
ape Backup
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 Exadata
– Use tape hardware compression
• Allocate 1 RMAN channel p
per tape
p drive
– Listener Load Balancing between all instances
• Spreads the backup I/O’s evenly over all database nodes
32
Exadata Backup & Recovery (External)
Configuration
Co
gu a o Best
es Practices
ac ces for
o Tape
ape Restore
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
G
g v 10GigE
0G g v IPoIB
o
• Smaller database can be backed up via GigE
g
– Offers backup rates of approx 960MB/sec
• Larger database can be backed up via10GigE
– Can
C b
be connected
t d iinto
t an existing
i ti 10Gi
10GigE
E network
t
k
– Offers backup rates of approx 8GB/sec
• Fastest database backup
p achieved via InfiniBand
– Get dedicated Media Servers that connect to tape library
– Offers backup rates of up to 12GB/sec
34
Exadata Backup & Recovery (External)
InfiniBand
a d Co
Configuration
gu a o Best
es Practices
ac ces for
o Tape
ape
• Database nodes and Media Server configuration
g
– Use Oracle Enterprise Linux on the Media Server
– Use same kernel and OFED packages as used on Oracle
Database Machine
– Enable IPoIB connected mode and MTU changes on the
media server
– No changes on database nodes needed
• Minimal CPU impact
p
– Observed less than 1 CPU Core used per instance
35
Exadata Backup & Recovery (External)
Script
Sc
p Examples
a p es
• RMAN configuration
configure default device type to sbt;
configure device type sbt parallelism 14;
• RMAN script
p for weekly
y backup
p
run {
backup incremental level 0 database tag 'weekly_level0';
backup archivelog all not backed up;
}
• RMAN script for daily backup
run {
backup cumulative incremental level 1 database tag 'daily_level1‘
backup archivelog all not backed up tag 'archivelogs';
}
36
Exadata Backup & Recovery (External)
Oracle
O
ac e Secu
Secure
e Backup
ac up Advantages
d a ages
• Oracle Secure Backup ((OSB)) tape-based backup
advantages
– Fastest database backup to tape via tight integration with
RMAN
• Unused block compression
• Inactive Undo blocks not backed up
– Very low cost
– MAA Validated
37
Exadata Backup & Recovery (External)
Oracle
O
ac e Secu
Secure
e Backup
ac up Co
Configuration
gu a o Best
es Practices
ac ces
• Configure
g
the Preferred Network Interface ((PNI)) to
direct the OSB traffic over the InfiniBand network
interface
ob> lspni (List Preferred Network Interface)
mediaserver1:
PNI 1:
interface:
mediaserver1 ib
mediaserver1-ib
clients:
dbnode1, dbnode2, dbnode3, dbnode4, dbnode5, dbnode6, dbnode7, dbnode8
PNI 2:
interface:
mediaserver1
clients:
adminserver
38
Exadata Backup & Recovery (External)
Oracle
O
ac e Secu
Secure
e Backup
ac up & Recovery
eco e y Best
es Practices
ac ces
• Backup and Recoveryy Performance and Best
Practices for Sun Oracle Database Machine and
Exadata
– http://www.oracle.com/technetwork/database/features/availab
ility/maa-tech-wp-sundbm-backup-11202-183503.pdf
39
Exadata Backup & Recovery (External)
Third
d Party
a y Media
ed a Management
a age e p
products
oduc s
• Third partyy vendors test and validate their own
products
– Contact the vendor for configuration best practices
– 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 products
40
Exadata Backup & Recovery (External)
Using
Us
g a Physical
ys ca S
Standby
a dby da
database
abase for
o bac
backups
ups
• Backing
g up using
g a Physical
y
Standby
y database
– Offloads the backup to the standby environment
– Reduce backup times with fast incremental backups
– 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 disaster recovery or high availability with Data Guard
Fast-Start Failover
41
Business Takeaways
Business Takeaways
42
Exadata Backup & Recovery
Business
us ess Takeaways
a ea ays
• #1: Works for any database of any size
• #2: Exadata makes backing up database faster
– Potentiallyy reducing
g backup
p windows
• #3: The investment in RMAN follows through to the Oracle
Database Machine
• #4: Save time and cost by being able to utilize current
backup infrastructure
• #5: MAA Validated
43
Best Practice Takeaways
Best Practice Takeaways
44
Exadata Backup & Recovery
Best
es Practice
ac ce Takeaways
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/availab
ility/maa-tech-wp-sundbm-backup-final-129256.pdf
– http://www.oracle.com/technetwork/database/features/availab
ility/maa wp dr dbm 130065.pdf
ility/maa-wp-dr-dbm-130065.pdf
• #2: RMAN knowledge is applicable in an Oracle
D t b
Database
M
Machine
hi environment
i
t
45
Best Practices
Additional Resources sponsored by MAA and X-Team
X Team
• MAA and Exadata OTN website contains best practices and
different architectural solutions
– MAA OTN website:
http://www.oracle.com/goto/MAA
– Sun Oracle Database Machine and Exadata OTN website
http://www.oracle.com/technetwork/database/exadata/index-089737.html
• Openworld presentations
– http://openworld.vportal.net
p p
p
46
Sponsors
Exadata MAA Team and X Team
• Operational and Configuration
g
best practices
– Optimized and integrated for Exadata
– Generic practices for other platforms
– Examples: Migration
Migration, Backup/Recovery
Backup/Recovery, Monitoring
Monitoring,
Troubleshooting, Patching, MAA, Consolidation, Active Data
Guard, Cloning/Reporting, Application Failover
• 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
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising