Exadata Backup
Download as PPTX, PDF7 likes6,357 views
This document discusses backup and recovery strategies for Oracle Exadata systems. It outlines the fundamental principles of backups including having multiple copies of data stored on different media with one copy offsite. It then describes the various backup options for Exadata, including using additional Exadata storage cells for the fastest backups, using a ZFS storage appliance for flexibility, or backing up to tape for economical long-term storage with removable offline copies. Key metrics like backup and restore speeds are provided for each option.
Exadata Backup
- 1. Backup & Recovery for Exadata Fran Navarro Principal Sales Consultant Feb 2012
- 2. Agenda • Backup & Recovery Fundamentals • Oracle Backup Tools • Backup Strategies for Exadata
- 3. Business Drivers Behind Backup What keeps our customers awake at night… • Data loss exposure - ESG estimates that 1 in 7 (14%) backups and 1 in 6 (17%) restores fail.* • Meeting SLA’s - Shrinking backup windows; slow recovery processes • Reducing costs - Reducing both CAPEX & OPEX while improving staff efficiency • Complexity - Complexity of BU&R process and the storage environment • Data growth - Compounding year over year *Enterprise Strategy Group 2008
- 4. Fundamental Data Protection Rule of 3 “3 Copies of the Data on 2 different medias with 1 offsite” • 1st Line of Defense (Applications, Systems) – Typically data deletion, logical corruption or a virus – Look at the RPO. The majority of critical application recovery is likely to come from the snapshot on the same tier of storage • 2nd Line of Defense (Building, Site, Region) – HW failure & Disaster Recovery - failover to a remote site – Circumstances will dictate whether it should be disk and/or tape – Remote disk mirroring provides a physical copy of the data, but does not provide logical data protection (it replicates corruption immediately!) • Last Line of Defense – TAPE! – The last chance to avoid permanent data loss – Data preservation much more important than recovery time
- 5. Fundamental Backup and Recovery Wks Days Hrs Mins Secs Secs Mins Hrs Days Wks Data Loss Downtime (Recovery Point Objective) (Recovery Time Objective)
- 6. Flashback Database Fast point-in-time recovery strategy Database Eliminate the need to restore a whole Instance database backup Continuous data protection for database Write Optimized, before-change block logging Restores just changed blocks New Old Replay log to restore DB to desired time Block Block It‟s fast - recover in minutes, not hours Version Version It‟s easy - single command restore Flashback Database to „2:05 PM‟` Data Files Flashback Log “Rewind” button for the Database
- 7. Oracle Recovery Manager (RMAN) Oracle-integrated Backup & Recovery Engine • Intimate knowledge of database file Oracle Enterprise Manager formats and recovery procedures • Manages and automates the backup, restore, and recovery policies and process Oracle • Catalog all backup and recovery RMAN Secure activities Backup • Operates online and in parallel for fast processing • Corrupt block detection during backup and restore with the ability Tape Drives to validate backups Fast Recovery Area • Integrated with Enterprise Database Manager, Oracle Secure Backup, and third party backup products
- 8. Oracle Secure Backup (OSB) Enterprise Tape Backup Management Oracle Protects Entire IT Enterprise Manager Environment • Built-in Oracle Integration Oracle Secure Backup • 25 – 40% faster than Oracle Database File System Data leading competition RMAN Integration • 4X less expensive than comparable products Tape Virtual • Supports Oracle Library Tape Library Database 11g through Oracle 9i
- 9. Centralized Tape Backup Management
- 10. Exadata Backup Backup Options for Exadata Exadata Exadata ZFS Oracle Sun Database Expansion Storage StorageTek Machine Appliance Tape Library (ZFS-SA)
- 11. Backup Options for Exadata Customer choice depending upon objectives & budget Exadata Backup (Fastest) • RTO: Immediate • RPO: Lossless • Fastest option using Inifiniband to another Exadata machine ZFS Storage Appliance Backup (Most Flexible) • RTO: Next to Immediate • RPO: Last transaction • Multiple network connectivity & data service options Tape Backup (Most Economical) • RTO: Hours • RPO: Last Transaction Backup • Best economics on cost/GB and offers removable offsite capability
- 12. Exa-Backup with Exadata Using additional Storage Cells - Highest Performance Oracle Exadata Oracle Exadata Database Machine Storage Cells • Requirements for immediate data restore capabilities and reduced backup windows • Primarily data protection against InfiniBand user/logical errors (Flashback) Network • Allocate additional 2TB HDD Exadata Storage Servers for a dedicated Fast Recovery Area Quarter* Half* Full** Backup 8.5 18.5 27.0 • Additional Exadata Storage Servers Rate TB/hr TB/hr TB/hr must be installed in another rack Restore 18.0 28.5 28.5 • External backup still recommended Rate TB/hr TB/hr TB/hr FC * Full Exadata Rack to a Quarter, Half Storage Expansion Rack ** Estimated rate Full Exadata to Full Storage Expansion Rack
- 13. Exa-Backup and ZFS Storage Appliance Most Flexible Oracle Exadata Sun ZFS Storage • Various Connectivity Options Database Machine Appliance - 1 GigE, 10 GigE, IB!! RMAN • ZFS works with RMAN to secure against data corruption - RMAN ensures that backups are not corrupt, ZFS ensures they stay that way IB / 10Gig E • Enables ZFS Snapshot and RMAN Network incremental backup strategy • Leveraging ZFS Storage data services and capabilities Image Incremental - Thin provisioning Copies Backups* - Compression - Snapshot and cloning Backup Rate 6.5 TB/hr 42.0 TB/hr - Replication Restore Rate 6.2 TB/hr 7.0 TB/hr - Performance Analytics *Effective Rate = Rate * Change Rate Backup = 8.5 TB/hr * 20% Change = 42 TB/hr
- 14. Exa-Backup to Tape Most Economical Backup Option • High efficiency Exadata protection Oracle Exadata StorageTek Database Machine • Scalable – capacity and Tape Library performance • Simplified data recovery Oracle Secure 6 x LTO4 6 x LTO5 IB / 10Gb E Backup (OSB) FC / SAS Network Backup Rate 4.7 Network 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)
- 15. Exadata Backup Putting it all together Oracle Exadata Oracle Exadata ZFS Storage OSB or other, 3rd StorageTek Database Machine Storage Cells Appliance Party, Backup Tape Storage Admin. RMAN Backups Backup Area
- 16. Some performance numbers Disk and Tape • Exadata for the most demanding RPO/RTO – Backup up to 18TB/hr (full rack), 20-50TB/hr for incrementals – Restore 18-24 TB/hr (full rack) • ZFS Storage Appliance Beats NetApp and EMC Data Domain! – Over 3x the backup throughput of NetApp – Up to 1.3x the restore throughput of NetApp – Over 3x the backup throughput of Data Domain – Over 3x the restore throughput of Data Domain • T10000C and Oracle Storagetek Libraries beat IBM ! – T1000C 25% greater capacity, 33% lower TCO, and 50% less floor space 16
- 17. Backup and Restore for Exadata Value Proposition Speed: Complete backups within shorter windows Faster backup and recovery (flashback and incremental forever RMAN strategy) Speedy Implementation Leverages Exadata's internal IB network for extreme performance Already tested, validated and supported by Oracle Simplicity: Avoiding complexity • No third party SW backup to manage required for disk backup • Preserves incremental backups optimizing Database and network performance • ZFS Storage Appliance 30% easier to manage than third party vendors Savings: Reduced Capex and Opex • Simple architecture reduces costs • No backup and recovery license fees and no media server for disk-based backup • Storage hierarchy that balances cost and performance • T1000C 25% greater capacity, 33% lower TCO, and 50% less floor space
- 18. Who better than Oracle to protect Oracle Three different ways to protect Exadata Exadata Backup (Fastest) Immediate Restore ZFS Storage Appliance Backup (Most Flexible) Easier integration Tape Backup (Most Economical) Oracle/StorageTek is #1 in tape
- 21. Exa-Backup and ZFS Storage Appliance Most Flexible Database Backups Level 0 IMAGE backup Day 1 Level 1 incremental backup Day 2 Day 3 Pros Cons Faster recovery from up-to-date image copy Can not recover data older than 24 hours Less data to backup = shortened backup windows
- 22. Exa-Backup and ZFS Storage Appliance Leveraging the ZFS Storage Appliance’s SnapShot Database Backups Level 0 IMAGE backup Day 1 Level 1 incremental backup Day 2 SnapShot Day 3
Editor's Notes
- #6: Value of DataThe Business value of data is rarely understoodRecovery Point ObjectiveTolerance for data loss (sec’s, hours, days); determines frequency of backupsRecovery Time ObjectiveThe shorter the Recovery Time Objective (RTO) the quicker you get back to businessBackup WindowStatic, but needing to accommodate an ever increasing amount of data
- #11: There are several options for backing up Exadata. These are not “either or” recommendations. The following architectures may be combined in several ways to best address the customers RPO (Recovery Point Objective)/RTO (Recovery Time Objective) and budget.
- #12: Summary of each supported backup option with benefits of each. (FYI Exadata to tape is a MAA architecture, Exadata to ZFS Storage Appliance is Optimised Solution)ZFS Storage Appliance data service options = compression, deduplication, snapshots, clones, mirroring etc.
- #14: Here we see the RMAN backup up to the ZFS storage appliance which is part of the listed Oracle Optimized Solutions listed. By leveraging the 7000’s snapshot technology allows you snapshot your full backup, run and incremental, then apply the changed block to the full – this basically rolls forward you full backups each night. But with the snap shots you have also stored as many previous full backups as desired. Remember the 7000 snap shots only copy pointers not actual data. So each night only the incremental new/change blocks are stored.Also leverage compression from either RMAN (11g) or within the 7000. Additionally customers can take advantage of deduplication (if it fits) and data replication. OSB can then offload data to tape for long term secure (encrypted) storage.
- #15: The following architecture is covered in an Oracle Maximum Availability Architecture White Paper.The Sun Oracle Database Machine Fast Recovery Area internal in DB Machine – this is where RMAN will backup to disk, Oracle Secure Backup is use to backup to tape. Solutions offers very high performance backups and recovery from both disk and tape.Easily scalable
- #16: Here we see the RMAN backup up to the ZFS storage appliance which is part of the listed Oracle Optimized Solutions listed. By leveraging the 7000’s snapshot technology allows you snapshot your full backup, run and incremental, then apply the changed block to the full – this basically rolls forward you full backups each night. But with the snap shots you have also stored as many previous full backups as desired. Remember the 7000 snap shots only copy pointers not actual data. So each night only the incremental new/change blocks are stored.Also leverage compression from either RMAN (11g) or within the 7000. Additionally customers can take advantage of deduplication (if it fits) and data replication. OSB can then offload data to tape for long term secure (encrypted) storage. Data movement to TapeRMAN Archive to tape – managed and tracked by RMANNDMP direct to FC tape – no database server resourcesThird Party backup server – reading snapshot and write to tape
- #19: Summary of each supported backup option with benefits of each. (FYI Exadata to tape is a MAA architecture, Exadata to ZFS Storage Appliance is Optimised Solution)ZFS Storage Appliance data service options = compression, deduplication, snapshots, clones, mirroring etc.
- #22: Let take a look at an example where we can leverage these data services.Here’s an example that looks at the Oracle RMAN suggested backup strategy. First we take a level 0 (or Full) Image copy backup on day 1. Next day a level 1 image copy backup is taken – so I have a full and an Incremental. The next day I take another Level 1 incremental and roll the previous incremental into the Full, thus updating the concurrency of the Full backupPros for this method are: - faster recoveries and shorter backup windows – but there are 2 major drawbacks. 1, You can’t recover the data base beyond 24 hours. With the Roll forward of the full backup – older versions of the DB no longer exist. Secondly the strategy uses Image Copy backups which are byte for byte copies of the data files, which means you can’t take advantage of RMANs compression capability as you can with Backup sets.
- #23: So let’s take a little different approach and exploit the ZFS Storage Appliance’s snapshot capability.First day we have the Level 0 image copy backup. Day 2 we take the incremental backup – no changes so far. On the next day we’ll take a snapshot of the day 1’s Level 0 and Level1 backup, then run the nightly level 1 incremental backup and do the normal roll forward of the full. Continuing to do this I will have as many FULL and incremental image backups to recover from as the customer deem necessary.