1 / 27

Dell Fluid Data Architecture Ease Of Use & TCO Benefit

Dell Fluid Data Architecture Ease Of Use & TCO Benefit . Ondřej Bačina Enterprise Brand Manager @OndrejAtDell. Storage Pains identified by Compellent Customer Council (2002). Out of control data growth. Wasted capacity. 80% Inactive data. Forklift upgrades & obsolescence.

maina
Download Presentation

Dell Fluid Data Architecture Ease Of Use & TCO Benefit

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. Dell Fluid Data ArchitectureEase Of Use & TCO Benefit Ondřej Bačina Enterprise Brand Manager @OndrejAtDell

  2. Storage Pains identified by Compellent Customer Council (2002) Out of control data growth Wasted capacity 80% Inactive data Forklift upgrades & obsolescence

  3. FLUID DATA TCO DELIVERSFINANCIAL SAVINGS WITH BREAK THRU ARCHITECTURE

  4. Fluid Data Ease Of Use Confidential

  5. „OLD SCHOOL“STORAGE DESIGNVS.

  6. Fluid DataNew way of using storage Confidential

  7. Sizing of „Old School“ model ? I will make for You sophisticated „crystal ball“ guess ! Confidential

  8. Issues with „Old School“ sizingPick the right box How much HDDs do i need now and in future ? Typical „Old School“ Architecture Lock-in on HDD scale-up Enteprise High-End Mid-Range Entry Level XL-XXL 1000s HDD L ~800 HDD M ~400 HDD S ~200 HDD DATA XS ~10s HDD $$$$ $$$$$$ $$$ $$

  9. Issues with „Old School“Storage Growth How do I Grow out of the box ? How i can protect my investment ? Typical „Old School“ Architecture Lock-in on HDD scale-up Enteprise High-End Mid-Range Entry Level XL-XXL 1000s HDD L ~800 HDD M ~400 HDD S ~200 HDD DATA XS ~10s HDD $$$$ $$$$$$ $$$ $$ 201`s HDD

  10. Fluid Data : One Consistent Storage One platform from TBs to PBs NO Rip&Replace & NO Fork-Lift Upgrades One Management tool One Virtual Storage SCALE OUT Storage Storage Storage SCALE UP Disks Disks Disks DATA DATA DATA Disks Disks Disks FLUID DATA

  11. Issues with „Old School“ sizingPick the Right Plug Storage offers plenty of connectivity options with pros/cons Legacy, current and in development (within storage lifecycle applicable) connectivity options that we need to consider BACK END FRONT END Network tech. STORAGE Fibre Channel Fibre Channel Protocol FCP SAS 2.0 DCB Ethernet FCoE iSCSI CIFS NFS FUTURE ? SAS 3.0 FUTURE ?

  12. „Old School“ Approach :Pick the right holes What Front End connectivity type do i need now and in future ? What Back End connectivity is used for now and are possible future upgrades ? IS YOUR STORAGE READY FOR FUTURE ? BE BE FE FE SAS 2.0 FC UNIFIED STORAGE FC „Old School“ STORAGE FC FCoE iSCSI CIFS „New School“ STORAGE FC SAS 2.0 NFS

  13. Fluid Data : Technology Upgrade Investment protection with Back End compatibility Freedom of choice in frontend connectivity ONLINE NON DISRUBTIVE NO FORK-LIFT UPGRADE BE BE FE FE Ethernet Value Proposition EqualLogic 1GBit SAS/SATA FC Freedom of choice Compellent FC FC iSCSI CIFS/NFS 10Gbit SAS 2.0 SAS 2.0 FCoE FCoE 40Gbit SAS 3.0 Future iSCSI CIFS CIFS NFS NFS Future FLUID DATA

  14. Issues with „Old School“ sizingApplication placement How important the application is to business ? Horizontal Tiering is very complicated in „Old School“ T3 SAN/NAS Storage T1 SAN Storage T2 SAN Storage Application • Focus : Cost/Perf. • SLA : Hours • Connectivity : FC/iSCSI • Capacity : Medium • Cost : Medium • Focus : Capacity • SLA : NBD • Connectivity : iSCSI/NFS/CIFS • Capacity : Large • Cost : Low • Focus : Perf.&Resiliency • SLA : Minutes • Connectivity : FC • Capacity : Low • Cost : High

  15. Fluid Data : Tiering IN&OUT the box Best-in-class Tiering on block level Vertical Tiering among various Disk types. RAID worry free Horizontal Tiering among various storage One Virtual Storage T3 Storage T2 Storage T1 Storage Vertical Tiering Horitzontal Tiering T3:SATA T2:15K T1:SSD Vol.1 Volume 1 T3:SATA T3:SATA T3:SATA FLUID DATA

  16. Issues with „Old School“ sizingDisks & RAID & Volumes Data are bound to RAID Group created on Disk Type & Capacity NO Data migration between Tiers NO Volume expansion on different Disk Capacity & Type Complicated upgrades as capacity of disks is gowing Storage Controller(s) SSD x200GB Perf. RAID Vol.1 T1 SAS@15K x146GB Perf. RAID Capacity RAID Vol.2 Vol.3 T2 SATA@7,2K x1TB Cap. RAID Archive RAID Vol.4 Vol.5 T3

  17. Issues with „Old School“Performance or Capacity Upgrade Data are bound to RAID Group created on Disk Type & Capacity NO Data migration between Tiers NO Volume expansion on different Disk Capacity & Type Complicated upgrades as capacity or performance of disks is gowing Storage Controller(s) SSD x200GB Perf. RAID Vol.1 T1 SAS@15K x300GB SAS@15K x146GB Perf. RAID Capacity RAID Capacity RAID Vol.2 Vol.3 Vol.6 Vol.3 T2 SATA@7,2K x3TB Archive RAID SATA@7,2K x1TB Cap. RAID Archive RAID Vol.4 Vol.5 Vol.7 T3

  18. Fluid Data : Performance and/or Capacity Upgrade Online Non Disrubtive Upgrades In case of performace increase add T1 Drives In case of capacity upgrade add T3 Drives One Virtual Storage Fluid Storage Vertical Tiering T1:SSD Volume 1 T3:SATA FLUID DATA

  19. Issues with „Old School“ sizingVolume Size When crating Volume we are adding future grow Some volumes i.e. Database or VMFS contains ZERO blocks How much capacity do you need and how much do you pay ? Lets look at one example 100GB Database with 30% YoY Growth rate Do you really want to pay for unused Capacity ? „Old School“ Storage 5 Years Reserve 30% YoY Grow 270GB Database Volume $ 370GB ZEROs 55GB Actual DB Size 100GB Real Data 45GB

  20. Fluid Data : Get Thin & Pay-as-You-Grow Focus on current needs & lose storage weight Size new storage on Real Data and save $ Get 5 Year Capacity with Pay-as-You-Grow Fluid Data Storage 5 Years Capacity Reserved but not consumed 30% YoY 270GB Show 370GB but consume 45GB Database Volume 370GB ZEROs 55GB * Actual DB Size 100GB Real Data 45GB * Zero Blocks are at this time Compellent only feature FLUID DATA

  21. Fluid Data : Sizing NO CRYSTAL BALL ANYMORE ! • Fluid Data sizinig is the done the same mechanism as sizing for server virtualiziation. You need to measure. • How much USED SPACE (NOT RAW) do you need ? • How many TOTAL IOPS do you need ? FLUID DATA Confidential

  22. FREEDell Performance Analysis Collection Kit http://content.dell.com/us/en/business/d/sb360/dpack-sc Confidential

  23. Fluid Data Walk The TalkDell Guarantees Performance & Capacity For Sized Solution

  24. Leverage the strengthof our comprehensive storage portfolio “Think of Dell as a storage portfolio player.” – John Webster, Evaluator Group, CNET News, March 22, 2011 FUTURE IS FLUID Dell Confidential

  25. Q&A

  26. Thank you ... Email & Linked in : ondrej_bacina@dell.com Twitter : OndrejAtDell

More Related