1 / 14

Configuring Large Disk Arrays in an Oracle Environment

Configuring Large Disk Arrays in an Oracle Environment. Glenn Fellin The Regence Group. The Regence Group. Sixth Largest Healthcare Plan Affiliation in the Nation Not-for-Profit Companies Main Locations: Seattle, Washington Portland, Oregon Salt Lake City, Utah Lewiston, Idaho

swinders
Download Presentation

Configuring Large Disk Arrays in an Oracle Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Configuring Large Disk Arrays in an Oracle Environment Glenn Fellin The Regence Group

  2. The Regence Group • Sixth Largest Healthcare Plan Affiliation in the Nation • Not-for-Profit Companies • Main Locations: • Seattle, Washington • Portland, Oregon • Salt Lake City, Utah • Lewiston, Idaho • Tacoma, Washington • Salem, Oregon • 60,000 Claims Processed per Day

  3. The Portland Site • Mainly Solaris and AIX UNIX Environment • 80 UNIX Servers • 5 TB of UNIX Data, mostly VM Managed • Oracle Database with Custom Applications

  4. VM in the Test Lab

  5. Hardware RAID Levels

  6. Why DBAs like Small Spindles • Up to 20% Slowdown: 9 -> 18 GB Drives • Spindles Dedicated to a Read / Write Process • More Buses to share the load

  7. Large Storage Lessons Learned • Host ‘yoda’: The Blob method • Host ‘c3po’: Balancing I/O • Host ‘antares’: Partitioning the I/O • Host ‘droid’: Independent Data Paths

  8. Problems with Large Storage • Large Spindle Sizes • Fewer Host Interfaces • Very Large LUNS • “SAN” Expertise Needed

  9. Why Change? • Our Data Warehouse has 514 Disks • Many MTBF Failures • Unmanageable Growth • Need fewer, Larger Disks • Performance Must be Better

  10. “Secret” Methods • Offloading Mirroring • “Fast Writes” • Mirror Reads • Striped Read RAID 5 • Pre-fetch Read Algorithms • Advanced Write Algorithms

  11. Balancing Factors • Availability • Reliability • Performance • Manageability

  12. Critical Performance Factors • I/O Processes Sharing Storage • “Independent Data Paths” • Controller to Drive Ratio • Cache Size • Array Algorithm • SAN Architecture

  13. Opportunities for Improvement • Vendor Connectivity Incompatibility • Infrastructure Management • Standards

  14. The Performance Bottom Line • Know Where the Data is • Optimize for Your Environment • “As Fast as Necessary”

More Related