1 / 29

Databases March 14, 2003

Databases March 14, 2003. Goals for Database Architecture Changes. Simplify hardware architecture Improve performance Improve system reliability Provide better capabilities for full load testing in development environment Improve capacity planning ability. Current Database Architecture.

kaemon
Télécharger la présentation

Databases March 14, 2003

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. DatabasesMarch 14, 2003

  2. Goals for Database Architecture Changes • Simplify hardware architecture • Improve performance • Improve system reliability • Provide better capabilities for full load testing in development environment • Improve capacity planning ability Implementation Review

  3. Current Database Architecture • Independent Sun Servers • 2 Operational Database Servers • Pipeline Processing/Archive Ingest/ Distribution • 4 cpu server with MTI RAID Array • Archive Catalog Browsing • 2 cpu server with MTI RAID Array Implementation Review

  4. Current Database Architecture • 2 Development/Test Database Servers • Original DADS dev/test server • 2 cpu server with JBOD (Just a Bunch of Disks) • Original OPUS dev/test server • 2 cpu server with JBOD Implementation Review

  5. Current Database Architecture Implementation Review

  6. Implementation Review

  7. Implementation Review

  8. Current Storage Issues • MTI RAID Arrays – Operations • Starting to age – had planned to start replacing MTI with more current technology • Poor tools for performance monitoring • JBOD (Just a Bunch of Disks) - Development • Much slower than RAID • No fault tolerance Implementation Review

  9. Current Server Issues • Sparc Servers • Highly reliable • Lack redundant hardware components • Unable to perform throughput tests on development systems since they are undersized compared to the operational servers. • No good performance monitoring tools Implementation Review

  10. Data Processing/Ingest/Distribution DB Server Performance Implementation Review

  11. Archive Catalog Browsing DB Server Performance Implementation Review

  12. Archive Dev/Test DB Server Performance Implementation Review

  13. Opus Dev/Test DB Server Performance Implementation Review

  14. Current Database Backup Strategy • Full database backups to local DLTs • Tran Log dumps to local disks • Operator Intensive Implementation Review

  15. New Database Architecture • Consolidate 4 servers to 3 domains on Sun Fire 15K • Domain 1 – Data Processing/ Archive Ingest/ Distribution • 8 CPUs – EMC • Should provide significantly improved performance • Doubles the number of CPUs • Significantly more memory • Faster RAID • Anticipate extra performance will be needed to handle: • New Instruments • Object catalogs • New MAST catalogs Implementation Review

  16. New Database Architecture • Consolidate 4 servers to 3 domains on Sun Fire 15K • Domain 2 – Archive Catalog Browsing • 4 CPUs – EMC • Should provide significantly improved performance • Doubles the number of CPUs • Significantly more memory • Faster RAID • Anticipate extra performance will be needed to handle: • New Instruments • Object catalogs • New MAST catalogs Implementation Review

  17. New Database Architecture • Consolidate 4 servers to 3 domains on Sun Fire 15K • Domain 3 – Development/Test • 4 CPUs - EMC • Should provide improved performance • Faster CPUs • Significantly more memory • RAID • Improved performance will be needed to allow more thorough throughput testing • Domains can be reconfigured to provide 8 cpu test environment for full up test Implementation Review

  18. New Database Architecture Implementation Review

  19. 7 Dynamically Re-Configurable Domains EMC OPUS/Archive OPS Opus/Archive EMC Databases OPS EMC Databases OPS EMC Code Development EMC System Test EMC Database Test EMC OS/Security Test SUN FIRE 15K Domain Config New Database Architecture Implementation Review

  20. Implementation Review

  21. New Storage Benefits • EMC RAID used for both Development, Test, Ops • Same Performance across domains • EMC storage easier to configure for both System Administrators and Database Administrators • Better performance monitoring tools • EMC switch will allow failover of disks to an alternate domain Implementation Review

  22. New Storage Benefits • EMC allows for new database backup strategies • Timefinder Snapshot  Backup to Centralized tape system • May facilitate snapshot refreshes of database to development/test server Implementation Review

  23. New Server Benefits • Consolidation of Database servers • Simplifies management for both SAs and DBAs • Redundant hardware systems should reduce downtime • Better performance monitoring tools • Domains can be reconfigured to provide extra resources on demand Implementation Review

  24. Database Transition Plans • Storage • EMC Training Underway • Testing EMC with loaner Sun 4800 • How to layout database partitions • Database backup strategies • Snapshot refreshes • Backup recovery from tape Implementation Review

  25. Database Transition Plans • Sun Fire 15K Server • System Administrator Training Underway • Testing with loaner Sun 4800 • Need 64 bit Sybase to utilize >4GB Memory • ST-ECF had experienced problems with initial release of 64 bit Sybase under v12.0 • They report having no problems with Sybase v12.5 • We will run full regression test with this version. Implementation Review

  26. Database Transition Plans • Sun Fire 15K Server • Testing with Sun Fire 15K • Will set up initial configuration of Dev/Test Server using database configuration parameters that are similar to existing servers. • This will allow us to duplicate current performance requirements. • We then plan to test the benefit of large amounts of memory within the database server and to further tune configuration parameters. • This tuning work will not impact the rollout of the other servers, since they can be brought on-line with the initial tuning configuration. Implementation Review

  27. Database Transition Plans • Order of Migration • Development Server (Opus Dev Server) • Merge in 2nd Development/Test Server (Archive Dev Server) onto same domain • Archive Catalog Browsing Server • Data Processing/ Archive Ingest/ Distribution Server Implementation Review

  28. Database Contingency Plans • Original hardware will be kept available should it be necessary to roll back • No trade in required for this equipment • Roll back would consist of a simple database load onto the original server • Roll back will be tested. Implementation Review

  29. Database Testing and Migration Schedule Implementation Review

More Related