Let's take a look at the most basic concepts in XIV:
Partitions
The fundamental building block of a logical volume is known asPartition.
Partition is 1 MB (kb), including a primary copy or secondary copy of data. Each Partition corresponds to a region of a separate physical disk, the storage administrator does not know which disk a Partition corresponds to. It is controlled by the system algorithm. Secondary Copy is placed in a Module different from Primary Copy.
650) this. width = 650; "title =" image "style =" border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; padding-right: 0px; border-top-width: 0px; "border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201411/7/731446_1415339407QVy6.png "width =" 500 "height =" 484 "/>
Logical volumes
1. Each Volume is composed of N 1 MB partitions.
2. The Logical Volume capacity is a multiple of 17 GB, because Volume is distributed across all disks of the system.
Storage pools
While the hardware resources within the bm xiv Storage System are already alized in a global sense, the available capacity in the system can be administratively portioned into separate and independent storage pools.
Essential, storage pools function as a means to define tively manage a related group of similarly provisioned logical volumes and their snapshots.
Storage Pools are Logical
-Allocates hardware resources
-Same performance for all storage pools
-Volumes can be moved between Storage Pools
-Volumes and their clones moved together
-No data movement involved... Immediate results
Storage Pools control the storage resources
-Use for specific applications or other ments
-Physical and Virtual storage used by volumes
-Limits physical space for clones
-Can be resized as needed... Depending on available resources
Is the relationship between Storage Pool and Logical Volume
650) this. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/4D/E8/wKioL1RcX6Dx2Rl3AAIr1wrywOw730.jpg "title =" 1.PNG" alt = "wKioL1RcX6Dx2Rl3AAIr1wrywOw730.jpg"/>
Distribution table
The distribution table is created when the system is started, including the ing between Primary and Secondary Partition, and the mapping between the Module and the corresponding Disk. When the hardware is changed, a new distribution table is created and then deliver to each Module. Each Module contains a distribution table.
XIV Running state
When both copies (Primary Copy and Secondary Copy) are presentFull RedundancyStatus.
When the full redundancy of data is compromised due to a disk or module failure, the XIV Storage System immediately identifies the non-redundant partitions and begins the rebuild process. the rebuild process consists of the following activities:
-- Creates a new target data distribution
-- Makes a copy of the non-redundant partitions and writes them according to the new target distribution. This process is knownRebuilding.
-- Simultaneously begins to redistribute the redundant data according to the new target data distribution. This process is knownRedistributing.
Important:After an XIV Storage System component failure, rebuild and redistribution begin immediately and at the same time.
This article is from the "star & storage" blog, please be sure to keep this source http://taotao1240.blog.51cto.com/731446/1574015
XIV (2) -- Logical system concepts