DAHA AKILLI BĐR DÜNYA ĐÇĐN BĐLGĐ ALTYAPILARIMIZI DEĞĐŞTĐRECEĞĐZ

Transcription

1 Information Infrastructure Forum, Istanbul DAHA AKILLI BĐR DÜNYA ĐÇĐN BĐLGĐ ALTYAPILARIMIZI DEĞĐŞTĐRECEĞĐZ 2010 IBM Corporation

2 Information Infrastructure Forum, Istanbul IBM XIV Veri Depolama Sistemleri Veri Depolamada Keşif Vladimir Atanaskovik Veri Depolama Sistemleri Satış Müdürü, IBM CEE 2010 IBM Corporation

3 If you think of a storage system that gives you the maximum just right out of the box helps you save 80% of your floor space, power and cooling costs helps you save 70% - 80% of your operating costs helps you to achieve shorter time to market optimizes itself heals itself gives you the best performance now and always

4 then you think about the IBM XIV Storage System then you think about a system that reinvents storage

5

6 Data Growth and your budget Data continues to grow? Opex Data So does Capex required but not so fast Moores Law Capex available today or Must be reduced by X% Capex Required Operating costs keep rising driven by more data to manage Capex Budget time How can we manage this growth and risk with less Capex and Opex available?

7 Average Storage TCO for Storage Systems Source: Gartner Group Performance management Capacity management Time for storage provisioning Administration 13% Hardware Management 3% Backup / Restore 30% Backup capacity Automation Backup time Restore time Environmental 14% Purchase 20% Downtime 20% Hardware costs Storage resource utilization Floor space, power consumption, cooling Out of space conditions Availability issues Performance hot spots

8 Capacity utilization: The hidden waste 100% ARRAY HOST 75% 50% 25% Utilization: Only 12.5% of storage deployed Raw Storage Storage after RAID RAID 3+1 as standard loss 25% Storage after LUN creation loss 10% Storage in use 80% of available LUNs Storage with file system 10% loss Usage on file system 50% utilized Data in databases 50% utilized TB

9 The Answer

10

11 IBM XIV True high-end system: Performance Reliability Scalability Feature rich (snapshots, mirroring) Manageability Overall low TCO (cost management, power, space) A true single-tier system Single solution for all storage needs

12 IBM XIV: Standard Features Virtualized grid storage Data distribution across all drives No RAID groups to manage Automatic load balancing Consistent performance No manual tuning Thin Provisioning High Performance, flexible Snapshots Remote Replication Browser based management Innovative data migration Raid Groups Tiered Disk Complex Mgmt.

13 IBM XIV Storage System HW Details Full Rack Half Rack Modules 15 6 Disks Cache 120 GB 48 GB Net Capacity 79,1 TB 27,2 TB FC-Ports 24 8 iscsi-ports 6 0 Redundant UPS yes yes

14

15 IBM XIV architecture and functions

16 IBM XIV Storage Architecture Design principles: Massive parallelism Granular distribution Off-the-shelf components Coupled disk, disk, RAM RAM and and CPU CPU User User simplicity Scale Out Out Interface Interface Interface Interface Interface Switching Data Module Data Module Data Module Data Module Data Module Data Module Data Module

17 IBM XIV Storage is a Grid Architecture Host Host Host Host User Switch (FC/Ethernet) Interface Module Interface Module Internal Switch 1 Interface Module Internal Switch 2 Host

18 Processing the data Legacy Storage Systems The way how legacy storage systems process data can be compared to a luggage deposit service with a desk. A desk clerk takes the luggage, brings it to the storage room and also delivers the luggage back. Since everything has to be done by one clerk it is not unusual to see long queues in front of such service. Similar with legacy storage systems: There are one or two control units having, the entire intelligence, of the system. Every piece of data that is read or written to the storage is processed through this one or two control units. vs. IBM XIV The way how XIV processes data can be compared to a self service locker based luggage deposit service. There are many lockers available and many lockers can be accessed by many persons simultaneously. You never see queues in front of lockers due to the massive parallelism they allow. Besides that a locker based luggage deposit service is much cheaper to operate then the desk/clerk based. Similar the IBM XIV system uses a storage grid that allows massive parallelism in processing data. Workload and intelligence is spread among many control units that operate simultaneously.

19 IBM XIV Storage Distribution Algorithm Each volume is spread across all drives Data is cut into 1MB partitions and stored on the disks XIV algorithm automatically distributes partitions across all disks in the system pseudo-randomly Data Module 1 Data Module 2 Data Module 3 Data Module 3

20 Comparison: Data placement Legacy Architectures XIV MANUAL Process REQUIRES Pre-Planning RISK to existing production Can create hotspots REQUIRES monitoring & tuning COMPLETELY Automated Process NO Pre-Planning AUTOMATIC load balancing

21 IBM XIV Storage Distribution Technique System Change Data distribution only changes when the system changes Equilibrium is kept when new hardware is added Equilibrium is kept when hardware is removed Data Module 1 Data Module 2 Data Module 3 Data Node Module 4 4 [ hardware upgrade ]

22 IBM XIV Storage Distribution Technique System Change Data distribution only changes when the system changes Equilibrium is kept when new hardware is added The The fact fact that that distribution is is full fulland automatic ensures that that all all disks join join the the effort of of data data re-distribution after after configuration change. Equilibrium is kept when hardware is removed [hardware removal] Tremendous performance gains are are seen seen in in recovery/optimization times thanks to to this this fact. fact. Data Module 1 Data Module 2 Data Module 3 Data Module 4

23 Comparison: Data placement after system change Legacy Architectures XIV COMPLEXITY GROWS WITH CAPACITY REQUIRES MORE Pre-Planning INCREASED RISK to existing production REQUIRES MORE monitoring & tuning LOWER capacity utilization COMPLETELY Automated Process NO Pre-Planning AUTOMATIC load balancing HIGHEST capacity utilization

24 IBM XIV architecture and functions

25 IBM XIV Snapshots - Virtually without Limits Snapshot creation/deletion is instantaneous High performance WITH snapshots Unlimited High number of snapshots High performance snapshots provide: Differential snapshots save 15-30% of storage capacity Snapshots on Easier snapshots Physical Backup (with clones) to to Tape Tape Instant recovery from from Logical Backup Easy Easy creation of of Test Test Environment Boot-from-SAN with with easy easy rollback Easy Easy Data-Mining on on Production data data Volume Distributed Distributed snapshots snapshots on on each each server. server. Extremely Extremely fast fast memory memory operations operations Accessing Accessing snaps snaps is is as as fast fast as as accessing accessing production production volumes volumes XIV Physical View Snap volume snap As Each Restore Host Server Volume Writes has from data, pointers shapshot it is placed in memory copy On a snapshot, each server simply to randomly the points disks to that original across hold system volume. the data in memory 1MB locally chunks only operation Data Module Data Module Data Module Data Module

26 IBM XIV architecture and functions

27 Thin Provisioning What is it? Users define volumes with any logical size Users acquire only the physical capacity of XIV Storage needed for data that is actually written The part of the volume that contains no data does not consume any physical space Volume 50GB Volume 70GB 150 GB Amount of physical storage required Volume 50GB Volume 70GB Volume 30GB Actual Data Written 10GB Actual Data Written 30GB Actual Data Written 20GB 60 GB Volume 30GB Actual Data Written 10GB Actual Data Written 30GB Fat provisioned Thin provisioned Actual Data Written 20GB

28 Stretching a Terabyte to the Max Real-life capacity gain with XIV Meet the the same functional needs with much less net net Terabytes

29 How Capacity Efficiency Translates to Savings Serve the same applications with fewer Terabytes Fewer Terabytes means less power Fewer Terabytes means less floor space

30 IBM XIV architecture and functions

31 IBM XIV Storage Remote Mirroring Remote Mirroring for Disaster Recovery Granularity at volume level Every I/O is committed to local and remote copies before Automatic Snap is used to keep copies self-consistent even during resync after link failure Flexible restore options completion Host write I/O 2. Write replication to secondary 3. Secondary acknowledges I/O 4. Primary sends I/O complete to host 2 3

32 IBM XIV architecture and functions

33 Data Migration Feature XIV allows data migration from legacy storage systems Data migration happens while production is ongoing Writes and updates are propagated to the legacy system and XIV Host Switch Legacy Storage e.g. EMC, HDS Migrate

34 IBM XIV architecture and functions

35 Ease of use IBM

36

37 IBM XIV Storage Provides Exceptional Value Grid Grid technology providing one one (Plug in in the the wall) wall) platform for for all all enterprise storage requirements with with self-healing and and self-tuning XIV Support Value Up to 80% decrease in power, space and cooling costs/tb (SATA) Up to 70% savings on Tier 1 storage costs (commodity components, Thin Provisioning, snaps, DR - all included) 70-80% reduction in operating cost (Virtual volume management, Elimination of storage tiering, data classification and performance tuning) Rapid roll out of new applications (Snap Shots and Seamless migration) Capacity Savings Thick to Thin Migration Problems XIV Solves Data centre power, space and cooling constraints High cost, complexity, management and risk associated with tiered storage New application time to market Virtual Server roll outs (VMWare) Database and OLTP consistent performance issues Compliance and regulatory issues by backup and archiving to Disk via high performance VTL (Diligent)

38 Thank You