Backup_exadata_update

1 Copyright © 2011, Oracle and/or its affiliates. All rights
reserved.
Oracle Exadata: Backup and Recovery of Oracle Exadata:

reserved.
Exadata Database Machine
• Extreme Performance for:
– Data Warehousing
– OLTP
– Database Consolidation
• Requires a well architected and
tested backup and recovery plan
Exadata
Database
Machine
X2-2
Exadata
Storage
Expansion
Rack

reserved.
Exadata Backup & Recovery
The Pieces of the Puzzle
• Managing the backup & recovery process 
Software
– Recovery Manager (RMAN) manages the entire process
of backing up and recovering the database
– Media Management software manages the location and
life cycle of the backups and locates the backup when a
restore is required
• Oracle Secure Backup (OSB) or third party products
• Choosing the backup destination  Hardware
– Exadata storage
– Non-Exadata disk storage: Oracle or third party products
– Tape: Oracle or third party products

reserved.
Exadata Database Machine Backup
Backup Destinations Options
Exadata
Database
Machine
Exadata Storage
Expansion Rack
Oracle Sun
StorageTek Tape
Library
ZFS Storage
Appliance
Fastest
Up to 50 TB/hour for incremental
Flexible Economical
21 TB/hour 27 TB/hour
6 - 8TB/hour
Snapshots & Clones
5 – 6TB/hour
(Dependent on # of tape drives)

reserved.
Exadata Backup and Recovery
Key Benefits: Fast and Simple
• Full Backup/Restore rates up to 27-28 TB/hour
• Simple Operations
– Simple RMAN commands to backup, restore or recover the
database
• The same as any other Oracle platform
– Automatically parallelized across all storage servers

reserved.
Exadata Backup and Recovery
Database and Exadata Features Are Data Aware and Integrated
• Data Aware
– Detection of block corruptions
– Auto repair and manual block repair options
• Integrated and works transparently
– OLTP and Data Warehouse Applications
– RAC, Data Guard, Flashback technologies, ASM, Exadata
– Oracle native compression capabilities
• OLTP (typically 3 X compression)
• Hybrid Columnar Compression (typically 10-15 X compression)

reserved.
Oracle Data Protection Strategies
Backup & Recovery Recovery Time Objective (RTO)
Physical Data Protection
• Recovery Manager (RMAN)
• Oracle Secure Backup (OSB)
Days/Hours
Logical Data Protection - Flashback Technologies Hours/Minutes
Recovery Analysis - Data Recovery Advisor Minimizes time for problem identification & recovery
planning
Disaster Recovery Recovery Time Objective (RTO)
Physical Data Protection - Data Guard Minutes/Seconds

reserved.
What are Your Recovery Requirements?
• Recovery Time Objective (RTO)
– How quickly do you need to recover?
• Recovery Point Objective (RPO)
– How much data, if any, can be lost?
• Backup Retention Policy
– What are the onsite, offsite and long-term retention objectives?
• What is the acceptable performance
– Do you need to minimize the impact of the backup?
Begin by Asking Questions

reserved.
Exadata Backup Targets
• 20 – 25 TB / hour
• All Exadata smart
features
Considerations - Performance and Cost Trade-offs
Highest Performance High Performance and Added Flexibility
Cost – Varies with hardware configuration
Exadata
Storage
Exadata
Storage
Expansion
Rack
ZFS
Storage
Appliance
(ZFS/SA)
StorageTek
Tape
Library
 27 TB / hour
 Fastest Backup and Restore
 ILM Historical Archive
 Second DATA2 Disk Group
 13 TB / hour
 Backups of database &
non-database files
 Snapshots
 Clones
 9 TB hour*
 Backup of database and
non-database files
 Offsite Backups
 Vaulting
Note*: Backup Rate limited by number of tape drives – 8 x T10000C Drives

reserved.
RMAN Backup Stategy Overview
Full Backups Incremental Backups
-Online or offline backups
-Faster restore
-Higher overheads on the servers
-Reduces backup window
-Reduced overhead on the servers
-Ideal with low-medium change rate e.g. < 20%
-Enable BLOCK CHANGE TRACKING for fast incremental backups
-Database must be in archived log mode
Image Copy or Backup Set Incrementally Updated Backups Full / Incremental Backup Strategy
Image copy:
• Must be on Disk
• Same size as database less temp files
Backup set:
• Disk or tape
• Smaller than an image copy
• Can be compressed
• Disk only
• Recovery window: typically 1 – 7 days
• Incremental forever strategy after initial
copy
• Disk or tape
• Typically - weekly fulls and daily
incrementals
• Retention:
• On-disk: days to weeks
• Tape: weeks to years
• Can be compressed

reserved.
Architecting an Exadata
Backup and Recovery
Solution

reserved.
Fast Recovery Area (FRA)
• Unified storage location for all recovery files
– Resides on Exadata Storage in an Exadata environment
– Contains archived logs and flashback logs
– May contain control files, online redo log files and backups
• Minimize the number of initialization parameters to set
when you create a database
Database Manages the Disk Space

reserved.
Fast Recovery Area
All databases:
Control file backups
Databases in archived log mode:
Online redo and archived logs
Assign Databases to Tier(s) of Storage
Based on Recovery Requirements and Available Resources
Tier 5
Tape
Weekly full only
D2D2T as required
Tier 1
Exadata Storage
Incrementally Updated Backups
Flashback logs
Active / Data Guard
Optional:
Offload backups
from production to
standbyTier 3
ZFS Storage Appliance RMAN Disk Backup
ZFS
Storage
Appliance
Tier 2
Exadata Expansion Rack
Exadata
Expansion
Rack
Tier 4
Tape
Full / Incremental
StorageTek
Tape Library
Offsite
Location

reserved.
Considerations and Trade-offs
Strategy Advantage Disadvantage
RMAN backup compression • Reduces space consumption – 4 levels:
• BASIC included in Enterprise Edition
• LOW, MEDIUM, HIGH available with Oracle
Advanced Compression Option (ACO)
• Incurs CPU overhead on database server
• Typically 1 CPU core per channel
RMAN backup encryption • Secures backup prior to files leaving the database • Incurs CPU overhead on database server
Incremental backup strategy • Reduces backup window with fast incrementals • Dependency on full backup for restoration
Full backup strategy • Improves recovery time (potentially) • More overhead on the servers
Integrated D2D2T • Seamless restore from disk or tape • Database server involved in both disk and tape
backup operation

reserved.
Backup of Compressed Data
• Compressed data remains compressed in the backup
– This data will not benefit from further compression during the
backup (e.g. RMAN backup or tape drive compression)
– Deduplication software cannot deduplicate compressed data
Effects on Sizing and Processes
HCC Data
OLTP Compressed Tables
SecureFiles
Compressed/Deduplicated
 RMAN backup compression is effective on non-compressed database files
 Avoid using RMAN backup compression on HCC tablespaces by separating the
backups as shown below:
 Restore is no different than if the backups had not been separated
CONFIGURE EXCLUDE FOR TABLESPACE historical_data;
CONFIGURE COMPRESSION ALGORITHM 'low’;
BACKUP TABLESPACE historical_data;
BACKUP AS COMPRESSED BACKUPSET database;

reserved.
Complete – Backup and Recovery
Who Better to Backup Oracle Than Oracle?
Fiber Channel
SAN
10GigE or
InfiniBand
Network
Oracle Secure Backup
Media Servers
Admin Server
SL3000 tape library
•Offsite Backups
•Vaulting
ZFS Storage Appliance
•Backups of database & non-database files
•Snapshots
•Clones
InfiniBand
Network
Storage Expansion Rack
•Fastest Backup and Restore
•ILM Historical Archive
•Second DATA2 Disk Group
10GigE or
InfiniBand
Network
Ethernet

reserved.
Create a Plan
Group Databases by RTO / RPO
Exadata
Expansion Rack
•RTO < 6 hours, RPO < 1 hour
•Full / Incremental backup – 1 week retention on disk
• Disk backup to ZFS Storage Appliance
• Fast recovery area on Exadata
•RMAN backup compression or ZFS compression RMAN Disk Backup
ZFS
Storage
Appliance
FRA
•RTO < 5 minutes, RPO = Near-zero data loss
•Incrementally Updated Backup Strategy – 2 day recovery on disk
• Fast recovery area on Exadata or Exadata Expansion Rack
•Backup to tape from the standby – 7 year retention period
•Backups encrypted on tape via tape drive encryption
Active Data Guard
StorageTek Tape Library
Remote
Standby
•RTO > 6 hours, RPO < 1 day
•Backup directly to tape – 3 month
retention period
•Remember Archived Log sweep
Tape
Backup Offsite
Location
Note: Solutions may vary based on database size (e.g. 100 TB data warehouse)

reserved.
Fast Recovery Area (FRA)
Sizing – Depend on What Is Kept in It
Note: Fast Recovery Area is not required for backups
Recovery Files Comments
Control file and archived log
backups
Estimate total size of all archived logs generated between successive
backups on the busiest days x 2 (in case of unexpected redo spikes)
Flashback logs (Redo rate x Flashback retention target time) x 2
Image copy backup Size of database minus temporary files
Backup set backups (full) # of full backups x estimated size
Incremental backups # of incremental backups x estimated size
Further details:
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmconfb.htm#i1019211

reserved.
Utilize a Single FRA Location
• Set each DB FRA location to
<consolidated RECO disk group name>
• Simplify backup storage management
– Ensure that consolidated RECO disk group
>= Sum {FRA size for each DB}
• Set each database’s FRA size according to individual
space requirements
– Each database has a separate subdirectory within the FRA for all its files
• Upon first file creation within the FRA, an <DB_NAME> subdirectory is created
automatically
Backup to Exadata Storage
DB 1
DB 2
DB1
DB2
RECO
FRA

reserved.
Sizing Backup Server(s)
• Media servers - workload is focused on data
movement, not processing power
• Assume about 2GB/s throughput via IB (TCP/IP)
per media server
• Administrative / Master Server requires enough
disk space for catalog growth
Administrative
Server
Media Server(s)
What if multiple databases are consolidated on Exadata?
• Bandwidth, throughput and capacity remain the same whether one or more
databases – No effect on media server sizing
For more information on sizing an Exadata tape backup environment, refer to:
http://www.oracle.com/technetwork/database/focus-areas/availability/maa-exadata-backup-methodology-495297.pdf

reserved.
Backup
Throughput =
8 TB / hour
Backup
Throughput = 8 TB
/ hour
Schedule Accordingly
Based on Available Hardware Throughput and Requirements
One 80 TB database
Backup takes 15 hoursDatabase grows to 120 TB
Backup takes 10 hours
80 TB = 10 hours then
40 TB = 5 hours
Total backup time = 15 hours
Two databases:
1 = 80 TB and 2 = 40 TB
Stagger backups to run
sequentially
Run backups concurrently
Backups complete in 15 hours
although unpredictable as to
when each completes
Tape environment - assign tape
drives to each database
(Assume 8 drives at 1TB/h
each): 5 to DB 1 would
complete in 16 hrs and 3 drives
to DB 2 would complete in 13.3
hours
Two databases:
1 = 80 TB and 2 = 40 TB
Backup window = 5 hours
Purchase additional hardware
increasing total backup
throughput to 24 TB / hour

reserved.
Ratios
• Backup & Recovery Internal to Exadata
• Backup & Recovery to Storage Expansion Rack
• Backup & Recovery to ZFS Storage Appliance
• Backup & Recovery to StorageTek Tape Library
• Backup & Recovery: the complete story

reserved.
Backup & Recovery Internal to Exadata
• Available usable space
– A
– A
– A
• Backup & Restore rates
Quarter Half Full
DATA (High) 3 TB 7 TB 14 TB
RECO (Normal) 5 TB 12 TB 23 TB
Quarter Half Full
Backup Rate 4.7 TB/hr 11.0 TB/hr 21.5 TB/hr
Restore Rate 3.5 TB/hr 8.2 TB/hr 16.5 TB/hr

reserved.
Backup & Recovery to Storage Expansion Rack
– a
– a
– a
– a
Quarter Half Full
DATA (Normal) 7TB 16TB 32TB
RECO (High) 2TB 4TB 8TB
BKUP (Normal) 42 TB 97 TB 194 TB
InfiniBand
Network
Quarter* Half* Full**
Backup Rate 8.5 TB/hr 18.5 TB/hr 27.0 TB/hr
Restore Rate 18.0 TB/hr 28.5 TB/hr 28.5 TB/hr * Full Exadata Rack to a Quarter, Half Storage Expansion Rack
** Estimated rate Full Exadata to Full Storage Expansion Rack

reserved.
Backup & Recovery to ZFS Storage Appliance
• a
– a
– a
– a
Quarter Half Full
ZFS /SA RAID-Z 40 TB scaling to 1.1 PB
InfiniBand
Network
Image Copies Incremental Backups*
Backup Rate 6.5 TB/hr 42.0 TB/hr
Restore Rate 6.2 TB/hr 7.0 TB/hr
*Effective Rate = Rate * Change Rate
Backup = 8.5 TB/hr * 20% Change = 42 TB/hr

reserved.
• ZFS/SA 7420 can be connected to two different DB
Machines fabrics via InfiniBand
– Requires 8 free IB ports on each fabric
– Keep primary and standby databases on different IB fabrics
– Keep critical applications on different IB fabrics
• ZFS/SA configured with 10GigE provides a centralized
Backup & Recovery solution for the enterprise
Considerations

reserved.
• Supports large amounts of usable space for backups,
snapshots and clones (up to 1.1 PB)
• Supports non-database and database files
– Coming soon – support for Hybrid Columnar Compression (HCC)
• Snapshot and cloning capabilities
– Snapshots created in seconds
– Coming soon - Best Practices and scripted solution
Tips, Tricks and Best Practices

reserved.
Backup & Recovery to StorageTek Tape Library
– a
– a
– a
Media Servers
InfiniBand
Network
Fiber Channel
SAN
Admin Server
Quarter Half Full
6 x LTO4 6 x LTO5
Backup Rate 4.7 TB/hr 5.7 TB/hr
Restore Rate 4.8 TB/hr 5.7 TB/hr
SL3000 up to 24 drive base (up to 56 drives with expansion for LTO or Enterprise T10K and 200 to over 5000 slots)
SL8500 up to 64 drive base (up to 640 drives LTO or Enterprise T10K drives and from 1500 to over 100,000 slots)

reserved.
Backup & Recovery : the complete story
Fiber Channel
SAN
10GigE or
InfiniBand
Network
Media Servers
Admin Server
SL3000 tape library
•Offsite Backups
•Vaulting
ZFS Storage Appliance
•Backups of database & non-database files
•Snapshots
•Clones
InfiniBand
Network
Storage Expansion Rack
•Fastest Backup and Restore
•ILM Historical Archive
•Second DATA2 Disk Group
10GigE or
InfiniBand
Network
Ethernet

reserved.
Backup & Recovery
• MAA Best Practices – Exadata Database Machine
– http://www.oracle.com/goto/MAA
– Backup and Recovery Performance and Best Practices for Exadata Cell and
Oracle Exadata Database Machine
– Oracle Exadata Database Machine - Backup & Recovery Sizing: Tape Backups
• Oracle Technology Network
– Protecting Oracle Exadata with the Sun ZFS Storage Appliance: Configuration
Best Practices (http://www.oracle.com/technetwork/articles/systems-hardware-
architecture/exadata-7000-367640.pdf)
• My Oracle Support
– Troubleshooting Backups External to the Database Machine (1275894.1)
– RMAN backup from Exadata to ZFS Storage Appliance (1354980.1)
– High Redundancy Disk Groups in an Exadata Environment (1339373.1)
Resources

reserved.
Q&A

reserved.

Backup_exadata_update

More Related Content

What's hot

Similar to Backup_exadata_update

More from Fran Navarro

Recently uploaded

Backup_exadata_update

Editor's Notes