1 / 15

EMC Centralized Storage March 14, 2003

EMC Centralized Storage March 14, 2003. John Scott. Storage Requirements. Highly Available Reduce downtime due to hardware problems EMC has redundant parts, mirrored disks and phone home system EMC support staff will arrive within 4 hours of a hardware failure to fix the problem

leola
Télécharger la présentation

EMC Centralized Storage 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. EMC Centralized StorageMarch 14, 2003 John Scott Implementation Review

  2. Implementation Review

  3. Storage Requirements • Highly Available • Reduce downtime due to hardware problems • EMC has redundant parts, mirrored disks and phone home system • EMC support staff will arrive within 4 hours of a hardware failure to fix the problem • Easily Manageable • Needs less management than current mix of multi-vendor arrays • One GUI controls the entire EMC system • Scalable without needing more infrastructure changes • 2 GB Switch has 64 ports, about half used so far • Disks can be upgraded as larger ones are put on market Implementation Review

  4. Integrating with SunFire 15K • Sun and EMC together very common in marketplace • Each domain on the SunFire will have separate connections to different EMC partitions as needed Implementation Review

  5. Space Allocation • EMC will have enough space for: • All POD files for OTFR and other highly requested data • Processing data through OPUS, DADS and OTFR • Operations, Development and Testing • All Databases for the Archive and Data Processing • Operations, Development and Testing • Catalogs and Surveys Data (CASB) • GALEX mission data Implementation Review

  6. Client 0-18 Months 18-42 Months Total Allocation (TB) Archive Operations – Archive Cache 2 6 8 Archive Operations – Verification Store 1 0 1 Archive Operations – Distribution Staging 1 0 1 Data Processing – OTFR, OPUS, Reference disk 2 3 5 ESS – Development and testing 4.6 0.4 5 GALEX Mission Archive 5 0 5 CASB – Object Catalogs 2.5 2.5 5 Development Database 0.5 1.5 2 Totals 16 16 32 Space Allocation Implementation Review

  7. Space Allocation • Putting together a policy to address allocation • Will monitor space already allocated • Will address new requests for storage • Will (re)allocate based on needs Implementation Review

  8. System Capabilities • 32 TB, total usable space – fully mirrored • Mirroring allows us to lose a drive and not lose any data or incur downtime • Business continuance volumes allow for backups and upgrades with zero downtime • PowerPath software balances load across redundant connections • Integrated EMC DLT Tape backup system (EDM) provides data security Implementation Review

  9. Still writing data to Magneto Optical Media • Disk drives and tapes are not acceptable archive media. • Catastrophic crash or building disaster would result in loss of Mission data if only writing to EMC • Writing data to MO and storing MO platters in another location provides data security. Implementation Review

  10. Data Depot • Most Archive data will be written to a portion of the EMC called the “Data Depot” • Provides fast access for users (including OTFR) to the data • No longer need to wait for jukebox hardware to mount the platter, faster read/write rates • Software changes coming soon to implement the Data Depot concept • Data will be written to Depot on Ingest • Data will be retrieved from Depot if available • More on that in the Presentation: Moving Archive Data to the EMC Storage Array Implementation Review

  11. Implementation Status • DADS VMS systems connected and operations is using EMC space for distribution and ingest • Throughput performance is meeting expectations • All DADS and OTFR Test and Development systems connected to EMC, currently testing • Loaner server hooked up and undergoing database testing using EMC space. • EMC DLT tape backup system (EDM) slow to configure, but working acceptably. Tests are ongoing. Backups being done reliably from test systems • Backups much faster Implementation Review

  12. Training Progress • “Knowledge Transfer” from EMC technical staff as they worked with us configuring system • They configured initial systems, we did later systems ourselves • Many web-based classes taken by staff • Two staff members sent to EMC for classroom training • Will develop operational procedures for CPT staff • More classes scheduled Implementation Review

  13. Remaining Tasks • Complete DADS/OTFR/OPUS testing on EMC storage • Complete backup and recovery testing/training • Test database applications • Decide on best strategy for BCV and backup systems • Test TimeFinder other specialized database applications • More on that in the Presentation: Databases Implementation Review

  14. Remaining Tasks (con’t) • Connect CASB systems • Develop efficient path to migrate their data • Turn in excess equipment • 6 large Cygnet jukeboxes • Misc hardware • Compaq StorageWorks arrays (to be kept around until the Tru64 machines are retired) Implementation Review

  15. Schedule Implementation Review

More Related