1 / 20

SAN Storage for Database Systems

SAN Storage for Database Systems. Future storage subsystem options for database systems. Topics. Current CSS SAN Unaddressed Issues Next Generation Arrays NFS Costs. Current CSS SAN. Conventional RAID Groups Standard Luns (<=2TB) Centralized Management Dynamically allocate storage

liam
Download Presentation

SAN Storage for Database Systems

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. SAN Storage for Database Systems Future storage subsystem options for database systems

  2. Topics • Current CSS SAN • Unaddressed Issues • Next Generation Arrays • NFS • Costs

  3. Current CSS SAN • Conventional RAID Groups • Standard Luns (<=2TB) • Centralized Management • Dynamically allocate storage • Cluster able

  4. Unaddressed Issues • Downtimes • Maintenance • Tuning/Optimization • Restructuring • Unscheduled • Amount of storage use • Cost

  5. Next Generation Arrays • 3PAR Data and Compellent • Reduce amount of storage use • Thin provisioning • R/W snapshots • Reduce maintenance outages • Dynamic Optimization/Tuning • Non-disruptive upgrades • Reduce cost • Non-disruptive tiered-storage

  6. Reducing Amount of Storage Use: Thin Provisioning Existing Projects New Projects 1TB 1TB 1TB 1TB 1TB 1TB 6TB 5.25TB 5TB 4.35TB 3.25TB 4TB 2TB 3TB Year 1 Year 2 Year 3 Year 4

  7. Reducing Amount of Storage Use:R/W Snapshots Traditional 3x Storage Needed Integration Production Development Delta from Integrators New Much smaller in size than production DB Delta from Developers 1+x storage needed Refresh DB for Dev and Int much faster Development R/W Snapshot Integration R/W Snapshot Production

  8. Reduce Amount of Storage Use • Thin Provisioning • Recover unused storage which has been allocated • Allows projects to purchase storage as needed vs. all up front • R/W Snapshots • Copy of actual data but much smaller • Can be used for development, integration and/or DR recovery • Guidelines for using snapshot storage systems for Oracle Databases http://www.oracle.com/technology/deploy/availability/pdf/oscp_snapshot_use.pdf

  9. Reducing Maintenance Downtimes Traditional 4+1 RAID5 Group I/O Bound/Disk Change Add Storage Copy Data off Recreate RAID Group Downtime Repopulate new storage Dynamic Optimization 4+1 RAID5 Group I/O Bound/Disk Change Add Storage Dynamically Optimize across new storage NO DOWNTIME

  10. Reducing DR Recovery:R/W Snapshots for near CDP 2:00PM 2:15PM SNAP 2:30PM 2:45PM Production DB 3:00PM New S/W @ 2:35PM 3:15PM Corruption at ~3:00PM? Detection at 3:15PM 3:30PM Determine course of action 3:45PM Recover to 2:30 PM Snapshot Mount 2:45 + 3:00PM Snapshots for analysis

  11. Reduce maintenance outages • Dynamic Optimization/Tuning • Increase bandwidth, IOPS, size of storage dynamically w/o disrupting application • Move from one RAID level to another as needed • Non-disruptive upgrades • F/W upgrades are non-disruptive to application if multi-attached

  12. Reduce Cost:Non-disruptive Tiered Storage Fibre Channel Storage New, high-value data on Fibre-Channel disk High Value Data Move older data to lower Tier storage Hold current FC growth Older Data Expand only in lower Tier? ~2.5:1 cost advantage Lower-Cost FATA Storage

  13. Reduce Cost • Non-disruptive Tiered Storage • Tiered storage = Place data on appropriate storage type relative to data’s importance and requirements • Move from expensive Fibre-Channel disk to lower-cost Fibre ATA drives as data ages. Movement is transparent to applications.

  14. Oracle over NFS File services for: Directorate, CD, FESS, ESH, LSS, etc. Subnet 111 FCC2 Core Rest of FNAL Network FC FCP IP IP CSS SAN Storage Email and IMAP Services

  15. Oracle over NFS • Oracle over NFS • Best if CPUs are < 70% utilized • Snapshots, thin provisioning, dynamic growth • Virtualized across many disks • Non-disruptive tiering on a lun basis • Lower-cost connection option

  16. Oracle over NFS • Titan SiliconServer for Oracle 9i http://hosteddocs.ittoolbox.com/VC051305a.pdf • Database Performance with NAS: Optimizing Oracle on NFS http://www.netapp.com/library/tr/3322.pdf • Oracle Compatible NAS storage http://www.oracle.com/technology/deploy/availability/htdocs/vendors_nfs.html

  17. Costs + Risks See handouts for quotes • HDS • AMS-500: 4.38TB FC, 12TB SATA • NSC55+WMS100: 4.67TB FC, 12TB SATA (NSC55 has 100% uptime guarantee) • EMC • CX500: 4.38TB FC, 2.5TB SATA

  18. Costs + Risks • Compellent: 4.67TB FC, 12TB FATA • 3PAR: 4.67TB FC, 12TB FATA Risks: • Newer, privately held companies • Longevity? • Buyout?

  19. Costs + Risks • NFS: • Cost of one of the HDS options Risks: • Oracle + NFS unknown at lab • Network switch not redundant

  20. Questions Send email to rayp@fnal.gov

More Related