Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Exadata Maximum Availability Architecture

1,295 views

Published on

Exadata Maximum Availability Architecture - Harmony 2015

Published in: Technology
  • Be the first to comment

Exadata Maximum Availability Architecture

  1. 1. 1 Oracle Exadata Maximum Availability Architecture Emre Baransel – Advanced Support Engineer, Employee ACE – ORACLE
  2. 2. 2 Oracle Exadata Maximum Availability Architecture What is MAA ? • Prepared on Oracle test environment – Goes live and confirmed on customer systems. • Specifies the “Best Practices” in terms of operation and configuration. + Failure tolerance and fast solution + “Online” changes and “rolling” upgrades = Minimum downtime • High Availability (HA) • Disaster Recovery (DR) • Backup and Recovery (BR) • Oracle MAA is a project of detailed research on:
  3. 3. 3 Oracle Exadata Maximum Availability Architecture Exadata MAA Architecture Overview
  4. 4. 4 Oracle Exadata Maximum Availability Architecture Built-In MAA Components of Exadata • 2-8 Database Servers  RAC • 3-14 Storage Servers  ASM (normal-high redundancy) • REDUNDANT DB node local disks drives (4-8 disk RAID5) • // Infiniband switches & Dual-port (QDR) Host Channel Adapters • // power supply • Oracle Hardware Assisted Resilient Data (HARD) • Automatic Service Request • Rolling Upgrades • Exachk
  5. 5. 5 Oracle Exadata Maximum Availability Architecture Exadata MAA Recommendatitions After Installation • Archivelog Mode • Force Logging • Fast Recovery Area • Oracle Flashback Technologies • Flashback Database • Flashback Query, Flashback Version Query, Flashback Transaction Query, Flashback Table, Flashback Drop (Recycle Bin) • Backup/Recovery • Data Guard & Automatic Client Fialover • Corruption Protection
  6. 6. 6 Oracle Exadata Maximum Availability Architecture Backup & Recovery Backup: 25TB/hour 27 TB/hour 9 TB/hour 9 TB/hour
  7. 7. 7 Oracle Exadata Maximum Availability Architecture Disk Backup Best Practices • For the disk backup performance: - run backup on all database instances. - start with two RMAN channels to each instance and increase if needed. - Use FILESPERSET=1 for database backups. (Increases one file restore/recovery) "_file_size_increase_increment"=2143289344 (RMAN will alloacte 2GB pieces from ASM, default 64MB) "_backup_disk_bufcnt"=64 "_backup_disk_bufsz"=1048576 "_backup_file_bufcnt"=64 "_backup_file_bufsz"=1048576 Incrementally Updated Backup = Merged Backup = Image Copy + Block Change Tracking
  8. 8. 8 Oracle Exadata Maximum Availability Architecture ZFS Backup Configuration Backup and Recovery Performance and Best Practices using Oracle Sun ZFS Storage Appliance and Oracle Exadata Database Machine http://www.oracle.com/technetwork/database/features/availability/maa-wp-dbm-zfs-backup-1593252.pdf "Oracle Engineered Systems Backup Utility for Oracle ZFS Storage Appliance" tool http://www.oracle.com/technetwork/server-storage/sun-unified-storage/downloads/zfssa-plugins-1489830.html • Connected with infiniband • Exadata - ZFS configuration is tested, confirmed and supported by Oracle development. • Read-only Snapshot and read-write Clone database (No need to uncompress HCC)
  9. 9. 9 Oracle Exadata Maximum Availability Architecture Tape Backup Best Practices Tape backup is advised together with disk backup: • Data is backed up outside of the Exadata box. • It’s easier to keep backups at remote locations. • Multiple buckups can be kept with low cost. • All tape backup products compatible with RMAN are supported. • There must be media server available between Exadata and Tape Library. • Backup & Restore time is related with tape read/write speed • Higher backup rates, by using more media servers and tape drives
  10. 10. 10 Oracle Exadata Maximum Availability Architecture Exadata Backup & Recovery
  11. 11. 11 Oracle Exadata Maximum Availability Architecture Disaster Recovery • Automatic Failover • Standby-First Patch Apply (>=11.2.0.1) • Decrease load on Primary Database (Active Data Guard, backup, corruption detection, flashback database) • High recovery speed on Exadata (290 MB/s) Data Guard & Active Data Guard
  12. 12. 12 Oracle Exadata Maximum Availability Architecture Non-Exadata Standby • HCC tables must be uncompressed on Failover • More disk capacity is needed on Standby • Active Data Guard cannot be used on HCC tables
  13. 13. 13 Oracle Exadata Maximum Availability Architecture Corruption Detection and Prevention DB_BLOCK_CHECKSUM OFF (FALSE) TYPICAL (TRUE) FULL Physical Corruption DB_BLOCK_CHECKING OFF (FALSE) LOW MEDIUM FULL (TRUE) Logical Corruption Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a Data Guard Configuration [ID 1302539.1] DB_LOST_WRITE_PROTECT=TYPICAL (default TYPICAL on Exadata)
  14. 14. 14 Oracle Exadata Maximum Availability Architecture Exadata High Availability Best Practices Oracle Sun Database Machine X2-2/X2-8 , X3-2/X3-8 and X4-2 High Availability Best Practices [ID 1274322.1] • Increase ASM power limit from default for a faster rebalance when application can absorb it • Ensure the ASM Disk Repair Timer is Set Correctly • Verify there is enough diskgroup free space for a rebalance operation • Check ASM rebalance forward progress if you suspect a problem • Check forward progress on an long running ASM resync if a problem is suspected • Check that Clusterware HAIP is in use for RAC ONE node databases • Verify filesystem is healthy • ... more in the following MOS note.
  15. 15. 15 Oracle Exadata Maximum Availability Architecture Procedural MAA Recommendations • Document and validate your high availability and performance SLAs. • Test and upgrade to software recommended in My Oracle Support Note: “888828.1 - Database Machine and Exadata Storage Server 11g Release 2 (11.2) Supported Versions” • Check for any critical software issues in My Oracle Support Note: “1270094.1 - Exadata Critical Issues“. • Execute the Exadata MAA health check (exachk), as described in My Oracle Support Note: “1070954.1 - Oracle Exadata Database Machine exachk or HealthCheck ” • Execute Data Guard role transitions. • Configure Exadata Database Machine monitoring and Automatic Service Request
  16. 16. 16 Oracle Exadata Maximum Availability Architecture Exadata MAA – Related Links • Deploying Oracle Maximum Availability Architecture with Exadata Database Machine http://www.oracle.com/au/products/database/exadata-maa-131903.pdf • Best Practices for Database Consolidation On Exadata Database Machine http://www.oracle.com/technetwork/database/features/availability/exadata-consolidation-522500.pdf • Backup and Recovery Performance and Best Practices for Exadata Cell and Oracle Exadata Database Machine http://www.oracle.com/au/products/database/maa-tech-wp-sundbm-backup-11202-183503.pdf • Backup and Recovery Performance and Best Practices using Oracle Sun ZFS Storage Appliance and Oracle Exadata Database Machine http://www.oracle.com/technetwork/database/features/availability/maa-wp-dbm-zfs-backup-1593252.pdf • Oracle Data Guard: Disaster Recovery for Oracle Exadata Database Machine http://www.oracle.com/au/products/database/maa-wp-dr-dbm-130065.pdf • Exadata Maximum Availability Tests Video http://vimeo.com/62754145
  17. 17. 17 Oracle Exadata Maximum Availability Architecture Questions Q&As

×