Oracle ZFS Storage Appliance for Exadata Backup & Recovery

Husnu Sensoy Global Maksimum Data & Information Technologies

1
Friday, December 14, 12

Husnu Sensoy

• Chief VLDB Specialist in Global Maksimum
Data & Information Technologies

• Oracle ACED in BI domain • Oracle Magazine DBA of the Year 2009
2
Friday, December 14, 12

Global Maksimum Data & Information Technologies
Just focus on Data & Information in it...

Three strategic areas we focus on

• •

Complex Event Processing

• • • • • • •

Oracle CEP Making 500 different business decisions for 1.2 Millions of events in a second Oracle Data Mining and Oracle R Enterprise Edition Churn Prediction Models for Telcos Marketing Target Selection Models Ten billion rows in a week Exadata

Data Mining

Large scale data analytics (what people say Big Data)

• •

120+ TB Exadata migration from UNIX systems. Exadata Master Class all over the EMEA region for Exadata customers, Oracle partners, and Oracle at the region.

3
Friday, December 14, 12

Backup & Recovery Challenges of Exadata Environments

• RMAN still does not provide a mechanism to compress image backups • No footprint optimized way to store multiple copies of the same data • RAC node utilization during ternary backup • Backup replication to remote site
4
Friday, December 14, 12

000 feet.. 12 . ZFS Oracle Solaris Hardware 5 Friday.ZFS Storage Appliance 10. December 14..

ZFS Hybrid Storage Pool A Combination of different skills Application ZFS Hybrid Storage Pool ZIL L2ARC Pool Write SSDs Read SSDs HDDs 6 Friday. 12 . December 14.

December 14. 12 .RMAN Incrementally Updated Backup Strategy Byte by byte copy of your Exadata 7 Friday.

December 14. } 7 Friday.RMAN Incrementally Updated Backup Strategy Byte by byte copy of your Exadata Image backup/Backupset Level 0 One Week Ago run { RESTORE DATABASE FROM TAG WEEKLY_FULL_BCKP. 12 .

RMAN Incrementally Updated Backup Strategy Byte by byte copy of your Exadata Now Image backup/Backupset Level 0 #1 #2 #3 #4 One Week Ago Three Days Before run { RESTORE DATABASE FROM TAG WEEKLY_FULL_BCKP. } 7 Friday. December 14. } run { [SET UNTIL SCN x|SEQUENCE x|TIME ‘x’] RECOVER DATABASE FROM TAG DAILY_INC_BCKP. 12 .

December 14. } 7 Friday.RMAN Incrementally Updated Backup Strategy Byte by byte copy of your Exadata Now Image backup/Backupset Level 0 #1 #2 #3 #4 One Week Ago Three Days Before Recovery Range run { RESTORE DATABASE FROM TAG WEEKLY_FULL_BCKP. 12 . } run { [SET UNTIL SCN x|SEQUENCE x|TIME ‘x’] RECOVER DATABASE FROM TAG DAILY_INC_BCKP.

December 14. 12 . But ZFS provides a file system level compression mechanism 8 Friday.Storage Overhead of Image Copies ZFS Storage File System Level Compression One problem with using incrementally updated backup strategy is that RMAN does not provide a mechanism to compress image copies.

Compression ZFS Compression vs RMAN Compression over uncompressed data 100 75 50 25 0 100 75 50 25 0 None LOW MEDIUM None LZJB GZIP L1 GZIP L4 GZIP L9 RMAN Compression 9 Friday. December 14. 12 ZFS Compression .

12 . December 14.Flexibility to Travel in Time ZFS Compression can let you to keep multiple image copies ? Now Image #4 #30 Image #3 … #8 #9 #10 #11 #12 #13 #14 #15 #30 Image #2 … … #30 Image #1 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 #30 One Month Ago Two Weeks Ago Last Night One Week Ago 10 Friday.

5 TB •1 Full + 7 incremental = 13.5 TB •1 Full + 15 incremental = 17.Flexibility to Travel in Time (Con’t) ZFS Compression can let you to keep multiple image copies ? No matter how much you compress. keeping multiple copies of your database is not a clever idea in terms of utilizing your ZFS Storage Appliance.5 TB This value theoretically can be reduced to •1 Full + 30 incremental = 25 TB using deduplication þ . By previous slide I wish to store: •1 Full + 1 incremental = 10. December 14.5 TB •1 Full + 30 incremental = 25 TB •Total of 63. ZFS has a solution to that problem also: Deduplication 11 Friday. 12 Assume a database of size 10 TB with a daily of 500 GB.

Replication with ZFS Appliance Painless Data Replication Exadata ZFS Storage Appliance LAN/WAN ZFS Storage Appliance DR Exadata DR Ternary Storage 12 Friday. 12 . December 14.

December 14. 12 .Optimizing Ternary Backups Silent Tape Backup by NDMP Exadata Ternary Storage Exadata ZFS Storage Appliance ZFS Storage Appliance Snapshot NDMP Ternary Storage 13 Friday.

Configuration & Management Tips 14 Friday. December 14. 12 .

Keep in mind that deduplication & ZFS compression require extra CPU power. Ensure that you use DNFS client. Use RMAN compression whenever possible unless you have a bottleneck on Exadata RAC nodes. Prefer LOW or MEDIUM for performance To utilize backup parallelism use SECTION option for BIGFILE tablespace data files 15 Friday. Set Synchronous write bias to Throughput Ensure that your ZFS Database record size is 128K Design multiple shares differentiated depending on their characteristics Cleanup unused snapshot & clones. 12 . Do not use cache devices for neither metadata nor data caching. December 14.ZFS Storage Configuration & Management Best Practices • • • • • • • • • • • • ZFS Storage Share Configuration Remove Update access time on read attribute.

12 . December 14.Monitoring Performance using Oracle Storage Analytics Keep your eyes on 3 metrics 16 Friday.

trunc((sysdate .open_time) * 24 * 3600))) / 1024 / 1024 mb_per_sec. 17 Friday. bai. substr(filename. '/'. io_count from gv$backup_async_io bai where bai.2) elaps.'999.24/32. buffer_count. nvl(effective_bytes_per_second. to_char(bytes / 1024 / 1024/10. (bytes / ((sysdate . December 14.status.99') mb_sofar. bai.1. to_char(bytes / 1024 / 1024. 12 .Monitoring Performance using SQL Query RMAN Catalog Views set linesize 5000 column filename format a50 set pagesize 64 select bai.inst_id.type = 'INPUT' and close_time is null order by "%" desc.3)+1) filename.99') "%".sid. total_bytes / 1024 / 1024 / 1024 total_gb. instr(filename.open_time) * 24 * 60.'09999.

12 .Backup Performance A real value based on previous generation 7410 2000 1500 MB/s 1000 500 0 Before  Tunining +Infrastructure  Tuning +Oracle  Advanced  Compression -­‐Index  Segments 18 Friday. December 14.

Two Real Backup Strategies using ZFS Storage Appliance 19 Friday. 12 . December 14.

12 . December 14.Simple Design Creating your FRA on ZFS Storage Appliance 20 Friday.

December 14.Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. 12 . 20 Friday.

20 Friday.Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. • A single disk copy is sufficient. December 14. 12 .

12 .Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. • A single disk copy is sufficient. December 14. 20 Friday. • Quick recovery from failure is necessary in case of a primary storage loss.

12 . • Quick recovery from failure is necessary in case of a primary storage loss. • A single disk copy is sufficient. • Database size very small with compared to ZFS Storage pool size.Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. 20 Friday. December 14.

Image Copies Incremental Backupsets Archivelogs Controlfile Autobackup FRA Open Storage 7000 20 Friday. • A single disk copy is sufficient. • Quick recovery from failure is necessary in case of a primary storage loss. • Database size very small with compared to ZFS Storage pool size. December 14.Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. 12 .

Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. • Database size very small with compared to ZFS Storage pool size. December 14. • Quick recovery from failure is necessary in case of a primary storage loss. 12 . Controlfile Autobackup Image Copies Incremental Backupsets Archivelogs FRA Open Storage 7000 20 Friday. • A single disk copy is sufficient. ALTER SYSTEM SET DB_RECOVERY_DEST=‘/export/fra’.

12 . December 14. } Controlfile Autobackup Image Copies Incremental Backupsets Archivelogs FRA Open Storage 7000 20 Friday. BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG ‘DAILY_BACKUP‘ DATABASE. • Quick recovery from failure is necessary in case of a primary storage loss. • A single disk copy is sufficient.Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. • Database size very small with compared to ZFS Storage pool size. ALTER SYSTEM SET DB_RECOVERY_DEST=‘/export/fra’. RUN { RECOVER COPY OF DATABASE WITH TAG ‘DAILY_BACKUP'.

• A single disk copy is sufficient. BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG ‘DAILY_BACKUP‘ DATABASE. RECOVER DATABASE. ALTER DATABASE OPEN. • Database size very small with compared to ZFS Storage pool size. • Quick recovery from failure is necessary in case of a primary storage loss. SWITCH DATABASE TO COPY. RUN { RECOVER COPY OF DATABASE WITH TAG ‘DAILY_BACKUP'. ALTER SYSTEM SET DB_RECOVERY_DEST=‘/export/fra’. December 14.Simple Design Creating your FRA on ZFS Storage Appliance • A system already running on NFS or another storage with a comparable performance. 12 . } RUN { ALTER DATABASE MOUNT. } Controlfile Autobackup Image Copies Incremental Backupsets Archivelogs FRA Open Storage 7000 20 Friday.

December 14.Advanced Design Multiple Image Copies for Multiple Recovery Points 21 Friday. 12 .

Advanced Design Multiple Image Copies for Multiple Recovery Points • Quick recovery using SWITCH is not an option 21 Friday. 12 . December 14.

Advanced Design Multiple Image Copies for Multiple Recovery Points • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary 21 Friday. December 14. 12 .

12 . December 14.Advanced Design Multiple Image Copies for Multiple Recovery Points • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now 21 Friday.

December 14.Advanced Design Multiple Image Copies for Multiple Recovery Points • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now • To somewhere in last week 21 Friday. 12 .

21 Friday. 12 .Advanced Design Multiple Image Copies for Multiple Recovery Points • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now • To somewhere in last week • ZFS Storage pool is at comparable size with production size. December 14.

Advanced Design Multiple Image Copies for Multiple Recovery Points Image Copies DEDUP Incremental Backupsets Archivelogs • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now • To somewhere in last week • ZFS Storage pool is at comparable size with production size. 12 LZJB FRA INC Open Storage 7000 ARCH LZJB . 21 Friday. December 14.

Advanced Design Multiple Image Copies for Multiple Recovery Points ALTER SYSTEM SET DB_RECOVERY_DEST=‘/export/fra’. Image Copies DEDUP Incremental Backupsets Archivelogs • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now • To somewhere in last week • ZFS Storage pool is at comparable size with production size. December 14. 21 Friday. 12 LZJB FRA INC Open Storage 7000 ARCH LZJB .

21 Friday. RUN { RECOVER COPY OF DATABASE WITH TAG ‘DAILY_BACKUP'. BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG ‘DAILY_BACKUP‘ DATABASE TO DESTINATION ‘/export/inc’.Advanced Design Multiple Image Copies for Multiple Recovery Points ALTER SYSTEM SET DB_RECOVERY_DEST=‘/export/fra’. 12 LZJB FRA INC Open Storage 7000 ARCH LZJB . December 14. } Image Copies DEDUP Incremental Backupsets Archivelogs • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now • To somewhere in last week • ZFS Storage pool is at comparable size with production size.

BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG ‘DAILY_BACKUP‘ DATABASE TO DESTINATION ‘/export/inc’. RESTORE DATABASE FROM TAG ‘DAILY_BACKUP’ RECOVER DATABASE. 21 Friday. December 14.Advanced Design Multiple Image Copies for Multiple Recovery Points ALTER SYSTEM SET DB_RECOVERY_DEST=‘/export/fra’. ALTER DATABASE OPEN. RUN { RECOVER COPY OF DATABASE WITH TAG ‘DAILY_BACKUP'. 12 LZJB FRA INC Open Storage 7000 ARCH LZJB . } RUN { ALTER DATABASE MOUNT. } Image Copies DEDUP Incremental Backupsets Archivelogs • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now • To somewhere in last week • ZFS Storage pool is at comparable size with production size.

} RUN { ALTER DATABASE MOUNT. 21 Friday. BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG ‘WEEKLY_BACKUP‘ DATABASE TO DESTINATION ‘/export/inc’. December 14. RUN { RECOVER COPY OF DATABASE WITH TAG ‘DAILY_BACKUP'. RECOVER COPY OF DATABASE WITH TAG ‘WEEKLY_BACKUP‘ UNTIL TIME ‘SYSDATE-7’. BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG ‘DAILY_BACKUP‘ DATABASE TO DESTINATION ‘/export/inc’. } RUN { SET COMPRESSION ALGORITHM ‘MEDIUM’.Advanced Design Multiple Image Copies for Multiple Recovery Points ALTER SYSTEM SET DB_RECOVERY_DEST=‘/export/fra’. ALTER DATABASE OPEN. 12 LZJB FRA INC Open Storage 7000 ARCH LZJB . } Image Copies DEDUP Incremental Backupsets Archivelogs • Quick recovery using SWITCH is not an option • Two recovery capabilities are necessary • To Just now • To somewhere in last week • ZFS Storage pool is at comparable size with production size. RESTORE DATABASE FROM TAG ‘DAILY_BACKUP’ RECOVER DATABASE.

Thanks husnu.com @husnusensoy .sensoy@globalmaksimum.com Friday.wordpress.com husnu. 12 http://husnusensoy. December 14.sensoy@gmail.