XIV(1)—Hardware Overview

IBM XIV被业内称为革命性的新一代存储架构,它是采用了大规模并行的分布式网格存储技术,使用了“Scale out”(横向扩展)的存储架构,利用多路网格模块并行分担存储负荷,并通过细粒度数据分布算法保证数据的恒定均衡分布,它不但提高了系统的可靠性、可用性和存取效率,还易于扩展。

1,System models and components

Machine type 2812-A14    
Machine type 2810-A14    
Machine type 2812-114    
Machine type 2810-114

IBM XIV-A14 Storage System components: Front and rear view [(also known as Generation 2 systems) ]

IBM XIV-114 Storage System components: Front and rear view[also known as Gen3 systems]

2,Hardware elements

2.1,Modules    
Module是XIV中最基本的概念,有3种Module:

Data Modules--存数据,处理数据    
At a conceptual level, the Data Modules function as the elementary “building blocks” of the system, providing storage capacity, processing power, and caching, in addition to advanced system-managed services. The Data Module’s ability to share and manage system software and services are key elements of the physical architecture

Interface Modules--提供IO接口    
Interface Modules are equivalent to Data Modules in all aspects, with the following exceptions:    
In addition to disk, cache, and processing resources, Interface Modules are designed to include both Fibre Channel and iSCSI interfaces for host system connectivity, remote mirroring, and data migration activities.

Module interconnect switches--连接各个Module    
The XIV Storage System contains a redundant switched network that transmits both data and metadata traffic between the modules. Traffic can flow in any of the following ways:    
Between two Interface Modules    
Between two Data Modules    
Between an Interface Module and a Data Module

Architectural overview

3, Scalability

Design principles    
The IBM XIV Storage System grid architecture, by virtue of its distributed topology and “off the shelf” Intel components, ensures that the following design principles are possible:

Performance:    
– The relative effect of the loss of a single component is minimized.    
– All modules are able to participate equally in handling the total workload.    
This design principle is true regardless of access patterns. The system architecture enables excellent load balancing, even if certain applications access certain volumes,or certain parts within a volume, more frequently.

Compatibility:    
– Modules consist of standard “off the shelf” components.    
Because components are not specifically engineered for the system, the resources and time required for the development of newer hardware technologies are minimized.    
This benefit, coupled with the efficient integration of computing resources into the grid architecture, enables the system to realize the rapid adoption of newer hardware technologies available without the need to deploy a whole new subsystem.

Scalability:    
– Computing resources can be dynamically changed    
– “Scaled out” by adding new modules to accommodate both new capacity and new performance demands    
– “Scaled up” by upgrading modules

IBM XIV Storage System scalable conceptual grid architecture

Proportional scalability    
Within the IBM XIV Storage System, each module contains all of the pertinent hardware elements that are necessary for a grid topology (processing, caching, and storage). All modules are connected through a scalable network. This aspect of the grid infrastructure enables the relative proportions of cache, processor, disk, and interconnect bandwidth to remain optimal even in the event that modules are added or removed:

Linear cache growth: The total system cache size and cache bandwidth increase linearly with disk capacity, because every module is a self-contained computing resource that houses its own cache. Note that the cache bandwidth scales linearly in terms of both host-to-cache and cache-to-disk throughput, and the close proximity of cache, processor, and disk is maintained.

Proportional interface growth: Interface Modules house Ethernet and Fibre Channel host interfaces and are able to access not only the local resources within the module, but also the entire system. With every Interface Module added, the system proportionally scales both the number of host interfaces and the bandwidth to the internal resources.

Constant switching capacity: The internal switching capacity is designed to scale proportionally as the system grows, preventing bottlenecks regardless of the number of modules. This capability ensures that internal throughput scales proportionally to capacity.

Embedded processing power: Because each module incorporates its own processing power in conjunction with cache and disk components, the ability of the system to perform processor-intensive tasks, such as aggressive prefetch caching, sophisticated cache updates, snapshot management, and data distribution, is always maintained regardless of of the system capacity.

参考书籍《SG24-7659-03,IBM XIV Storage System:Architecture, Implementation,and Usage》.

时间: 2024-08-11 07:50:06

XIV(1)—Hardware Overview的相关文章

XIV(1)—Hardware Overview Cont.

接第一篇<XIV(1)- Hardware Overview>讲述了XIV系统的大体的硬件组成,本篇继续讲XIV系统的Hardware Architecture. 1,Data Module/Interface Module XIV Model A14 Data Module/Interface Module Data Module和Interface Module的区别在于Interface Module有主机IO适配器和G网卡适配器,还有就是Data Module是一个Low voltag

XIV(1)- Hardware Overview

IBM XIV被业内称为革命性的新一代存储架构,它是采用了大规模并行的分布式网格存储技术,使用了"Scale out"(横向扩展)的存储架构,利用多路网格模块并行分担存储负荷,并通过细粒度数据分布算法保证数据的恒定均衡分布,它不但提高了系统的可靠性.可用性和存取效率,还易于扩展. 1,System models and components Machine type 2812-A14 Machine type 2810-A14 Machine type 2812-114 Machine

XIV(3)--Read/Write Operations

XIV系列: <XIV(1)-Hardware Overview> <XIV (2)--Logical system concepts> 之前的文章曾经说过HOST发过来的data会在XIV上存2份,即Primary Copy和Secondary Copy.只有当这2份都同时存在时,系统才是Full Redundancy状态.那主机在XIV上读写数据分别是怎么进行的呢?请看本篇: -Each write is written to the cache of two data mod

XIV(4)--Flash caching

1,Flash Cache简介 Flash cache 本身是Facebook的一个开源项目,(准确的说是一个Linux的模块),可以动态加载.Flashcache通过在文件系统(VFS)和设备驱动之间新增了一次缓存层,来实现对热门的缓存.Flashcache是另一种缓存,一般用SSD作为介质的缓存(一般的缓存用的是内存),通过将传统硬盘上的热门数据缓存到SSD上,然后利用SSD优秀的读性能,来加速系统.这个方法较之内存缓存,没有内存快,但是空间可以比内存大很多.如下图: 现在很多硬件厂商也会在

XIV (2)--Logical system concepts

先来看看几个XIV中最基本的概念: Partitions     The fundamental building block of a logical volume is known as a partition. Partition是1MB(1024KB),包括a primary copy 或者 secondary copy of data,每个Partition都对应一个单独的物理磁盘的某个区域,存储管理员不知道也无法控制一个Partition对应到哪个disk,它是由系统算法控制的.Se

XIV(5)-- Data Recovery Protection (XDRP)

和大多数存储系统一样,XIV也提供多地容灾的解决方案.XIV Data Recovery Protection (XDRP)有三种实现方式, Synchronous Mirroring; ASynchronous Mirroring; Data Migration.除此之外,当然也支持Flashcopy,VolumeCopy 一.Synchronous Mirroring XDRP是在两个或多个XIV系统之间做real-time copy,支持 Fiber Channel 或iSCSI link

天马行空云计算(二)-Hardware&amp;Hypervisor介绍

天马行空云计算系列一介绍了总体抽象视图,本篇展开Hardware&Hypervisor 介绍.如下是介绍大纲: 原文地址:https://www.cnblogs.com/hrbeu05/p/9085179.html

linux系统基础(一)

Linux简介与安装Unix ;windows; linux; apple(mac) linux=kernel (内核)=OSlinux全是文件==================================================IDE硬盘(支持4块):hd(a-d) [非IDE硬盘]SCSI硬盘,SATA硬盘,u盘(支持16块):sd(a-p) device 设备 (运行) hardware 硬件 /dev/hda /dev/sdc 分区:主分区(一块磁盘物理支持4个)c d e

Android 5.0内核和源代码学习(2)——源码下载和系统启动过程分析

一.Android源码下载 上一次简单介绍了Android系统的层次结构,这次开始动真格了--下载源码和分析源码! 那么,Android的源码从哪下?当然是谷歌官网,下载方法官网也讲得很详细,但是奈何中国的墙比较厚,所以上面的办法是没用的,当然,有些是有用的,地址:http://source.android.com/source/downloading.html 谷歌官网没办法下,幸好还有一些国内网站,废话不多说,直接开始步骤: 工具和环境:VM虚拟机+Ubantu14系统 第一步:Ubantu