Detailed description of ibm_v7000 underlying structure and data recovery cases

Detailed description of ibm_v7000 underlying structure and data recovery cases

Ibm_v7000 (full name: IBM Storwize V7000) is a next-generation mid-end storage system launched by IBM. Despite positioning the mid-end, Storwize V7000 provides powerful storage management capabilities that were previously provided by high-end storage. Common models include IBM Storwize v3700, IBM Storwize v5000, and IBM Storwize V7000. Its underlying storage structure supports Riad 0, raid 10, RAID 5, and raid 6. Upper-layer volumes support General volumes, thin-Mode Volumes, mirror-mode volumes, and thin-image-mode volumes. Although V7000 does a good job in the overall storage structure, some physical faults or other operations may damage the volume or storage, therefore, the data recovery technology of the series of storage can be used.

 

[Configure ibm_v7000]

1. Use the management IP address to connect to ibm_v7000, and enter the user name (default: superuser) and password (password: passw0rd ).

650) This. length = 650; "src =" http://s3.51cto.com/wyfs02/M00/47/19/wKioL1P2x4ex6vBnAAGNZj2wWpU984.jpg "Title =" 1.jpg" width = "700" Height = "276" border = "0" hspace = "0" vspace = "0" style = "width: 700px; Height: 276px; "alt =" wkiol1p2x4ex6vbnaagnzj2wwpu984.jpg "/>

2. There is no configuration by default. mdisk, pool, and volume must be configured first, and host ing volumes must be added.

650) This. length = 650; "src =" http://s3.51cto.com/wyfs02/M02/47/17/wKiom1P2xoeRkzZaAAGePMHJKr8421.jpg "Title =" 2.jpg" width = "700" Height = "315" border = "0" hspace = "0" vspace = "0" style = "width: 700px; Height: 315px; "alt =" wkiom1p2xoerkzzaaagepmhjkr8421.jpg "/>

3. Create an mdisk. The mdisk types include raid0, raid0, RAID5, and raid6.

650) This. length = 650; "src =" http://s3.51cto.com/wyfs02/M02/47/19/wKioL1P2x7-RE4aNAAHFT1T73b4097.jpg "Title =" 3.jpg" width = "556" Height = "400" border = "0" hspace = "0" vspace = "0" style = "width: 556px; Height: 400px; "alt =" wKioL1P2x7-RE4aNAAHFT1T73b4097.jpg "/>

4. Create a pool to divide multiple mdisks into one pool.

650) This. length = 650; "src =" http://s3.51cto.com/wyfs02/M01/47/17/wKiom1P2xr6B0rR4AAHquWkokWo246.jpg "Title =" 4.jpg" width = "700" Height = "288" border = "0" hspace = "0" vspace = "0" style = "width: 700px; Height: 288px; "alt =" wkiom1p2xr6b0rr4aahquwkokwo246.jpg "/>

5. Create a volume. The volume is configured on the basis of the pool. The volume type is generic, automatic, image, and image.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/47/17/wKiom1P2xtziL4H5AAFiz50QDMk062.jpg "Title =" 5.jpg" alt = "wkiom1p2xtzil4h5aafiz50qdmk062.jpg"/>

6. Create a host and map the volume. The host types include Fiber Channel hosts and iSCSI hosts.

650) This. length = 650; "src =" http://s3.51cto.com/wyfs02/M00/47/19/wKioL1P2yAbhY77mAAD7au0Mgl4931.jpg "Title =" 6.jpg" width = "700" Height = "302" border = "0" hspace = "0" vspace = "0" style = "width: 700px; Height: 302px; "alt =" wkiol1p2yabhy77maad7au0mgl4931.jpg "/>

So far, the general configuration process is complete, but we do not know how the logical volumes allocated to the host are actually distributed on the disk. How are they distributed? The structure and principles described below are similar to those of the HP lefthand series of storage products. For details, see the author's article HP-lefthand underlying structure and storage disaster recovery.

 

[Structure and principle]

In fact, the underlying principle of ibm_v7000 is not complicated. The entire storage structure is divided into four layers.

Level 1: physical hard disks are the locations where data is actually stored.

Layer 2: ibm_v7000 is named as mdisk. In fact, it is raid, which is a collection of multiple physical disks.

Layer 3: pool, which combines multiple mdisks into a large logical container.

Layer 4: volume, the space allocated from the pool, the user-oriented storage unit, the volume cannot cross-pool.

The structure is as follows:

650) This. length = 650; "src =" http://s3.51cto.com/wyfs02/M02/47/19/wKioL1P2yBKT_mx0AAGFj6VT8Xc182.jpg "Title =" 7.jpg" width = "600" Height = "345" border = "0" hspace = "0" vspace = "0" style = "width: 600px; Height: 345px; "alt =" wkiol1p2ybkt_mx0aagfj6vt8xc182.jpg "/>

In terms of the overall storage structure, disks are the final places where data is stored. The so-called mdisk, pool, and volume all Virtualize physical disks. On the physical disk layer, data is stored in blocks. N multiple disk groups form one mdisk, data stored in mdisk is divided into N blocks and evenly distributed across all disks. At the mdisk layer, data is stored in segments (sections). Multiple mdisks form a pool, the volumes created in the pool are divided into several segments and placed in different mdisks. The types of different volumes vary in the pool, however, it is stored in the midsk in segments.

 

During the entire storage process, the user stores the data in the volume, and the volume is divided into several segments and distributed in different mdisks, mdisk divides segments into several blocks and distributes them in different disks. The final data is all distributed in blocks on different disks.

 

[Data recovery case]

1. Storage Architecture

Storage Model: ibm_v7000

Disk quantity: 24 600 gb sas Disks

Number of mdisks: Two mdisks, both RAID 5

Volume quantity: 2 General Mode 2 TB, 1 3 TB simplified mode.

2. Fault Cause

Due to the aging of the disk, several disks in the mdisk are offline. As a result, the mdisk is unavailable and the upper volume cannot be accessed. However, because only one global hot backup is set, after the disk is offline, the Administrator does not change the disk in time, causing the entire fault.

3. Solutions

First, mirror all disks and then analyze which disks are a group of mdisks.

Find the mdiskd disk in the same group and analyze whether the disk is offline.

If a disk is offline, remove the disk from the mdisk group.

Generate mdisk and analyze the structure between mdisks.

Generate a pool and analyze the volume structure. Because different volumes have different types, the storage structure is also different.

After analyzing the volume structure, you can generate data for each volume.

4. Data Recovery successful

Because several disks in mdisk are offline, no other operations are performed. Therefore, the entire data recovery is complete and the customer is satisfied.

 

Because of the thorough research on the underlying structure of the IBM V7000 series storage, data in this series of storage failures can almost be saved. However, there is a situation where data cannot be saved, that is, all disks are rebuilt and initialized. After the mdisk is created, the system initializes the mdisk, that is, clearing it. For example

650) This. length = 650; "src =" http://s3.51cto.com/wyfs02/M01/47/19/wKioL1P2yB6ShbNvAAEgMuZLYCA889.jpg "Title =" 8.jpg" width = "700" Height = "229" border = "0" hspace = "0" vspace = "0" style = "width: 700px; Height: 229px; "alt =" wkiol1p2yb6shbnvaaegmuzlyca889.jpg "/>

Therefore, if the storage is re-built and the initialization is complete, it is basically useless.

 

Deng Qi (North Asia server data recovery Engineer)

Email: [email protected]

Contact info: 010-4006505808-801

This article is from "Deng Qi's blog" blog, please be sure to keep this source http://dengqi.blog.51cto.com/5685776/1543456

Detailed description of ibm_v7000 underlying structure and data recovery cases