No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Basic Storage Service Configuration Guide for File

OceanStor V3 Series V300R006

This document is applicable to OceanStor 2200 V3, 2600 V3, 5300 V3, 5500 V3, 5600 V3, 5800 V3, 6800 V3, 18500 V3, and 18800 V3. It describes the basic storage services and explains how to configure and manage them.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Planning Storage Pools

Planning Storage Pools

This section describes how to plan storage pools, including their usage, storage tiers, and RAID levels.

Planning Usage

  • Usage of a storage pool is unchangeable after being configured.
  • If Usage of a storage pool is set to Block Storage Service, the storage pool can only be used to create LUNs.
  • If Usage of a storage pool is set to File Storage Service, the storage pool can only be used to create file systems.
  • You are advised to use different disk domains to create storage pools for the block and file storage services.

Planning Storage Tiers

A storage pool is a logical combination of one or more storage tiers. A storage pool supports a maximum of three storage tiers. A storage tier is a set of storage media that has the same performance and uses the same RAID level. Various storage tiers provide different performance at different costs.

Table 2-9 lists the specifications of each storage tier.

Table 2-9 Specifications of each storage tier

Storage Tier

Storage Medium

Response Speed

Per-GB Cost

Per-I/O Cost

High-performance tier

SSD

Fast

High

High

Performance tier

SAS disk

Medium

Medium

Medium

Capacity tier

NL-SAS disk

Slow

Low

Low

Functions of different storage tiers are as follows:

  • High-performance tier: delivers the highest performance among the three tiers. As the cost of SSDs is high and the capacity of a single SSD is small, the high-performance tier is suitable for applications that require high random read/write performance, for example, database indexes.
  • Performance tier: delivers high performance. As the cost of SAS disks is moderate and the capacity of a single SAS disk is large, the performance tier has good reliability and is suitable for common online applications.
  • Capacity tier: delivers the lowest performance among the three tiers. As the cost of NL-SAS disks is the lowest and the capacity of a single NL-SAS disk is large, the capacity tier is suitable for non-critical services, for example, backup.

Planning RAID Levels

Consider the following requirements when selecting RAID levels:

  • Reliability
  • Read/Write performance
  • Disk utilization

Different RAID levels provide different reliability, read/write performance, and disk utilization, as described in Table 2-10.

Table 2-10 RAID levels

RAID Level

Redundancy and Data Recovery Capability

Read Performance

Write Performance

Typical Disk Utilization

Maximum Number of Allowed Faulty Disks

RAID 0

No data redundancy is provided and corrupted data cannot be recovered.

High

High

100%

0

RAID 1

High. RAID 1 provides complete redundancy. If a CK fails, the mirror CK can be used to recover the data.

Relatively high

Relatively low

  • 2Da: about 50%
  • 4D: about 25%

N-1 (in a RAID 1 disk array with N disks)

RAID 3

Relatively high. Each CKG has one CK as the parity CK. Data on any data CK can be recovered using the parity CK. If two or more CKs fail, RAID 3 protection can no longer be provided.

High

Low

RAID 3 supports flexible configurations. Specifically, a RAID 3 policy allows data block and parity block policies ranging from 2D+1P to 13D+1P. The following examples show disk utilization of several configurations commonly used by RAID 3:

  • 4D+1Pb: about 80%
  • 2D+1P: about 66.67%
  • 8D+1P: about 88.89%

1

RAID 5

Relatively high. Parity data is distributed on different CKs. In each CKG, the parity data occupies space of a CK. RAID 5 allows the failure of only one CK. If two or more CKs fail, RAID 5 protection can no longer be provided.

Relatively high

Relatively high

RAID 5 supports flexible configurations. Specifically, a RAID 5 policy allows data block and parity block policies ranging from 2D+1P to 13D+1P. The following examples show disk utilization of several configurations commonly used by RAID 5:

  • 2D+1P: about 66.67%
  • 4D+1P: about 80%
  • 8D+1P: about 88.89%

1

RAID 6

Relatively high. Two groups of parity data are distributed on different CKs. In each CKG, the parity data occupies space of two CKs. RAID 6 allows two CKs to fail simultaneously. If three or more CKs fail, RAID 6 protection can no longer be provided.

Medium

Medium

RAID 6 supports flexible configurations. Specifically, a RAID 6 policy allows data block and parity block policies ranging from 2D+2P to 26D+2P. The following examples show disk utilization of several configurations commonly used by RAID 6:

  • 2D+2P: about 50%
  • 4D+2P: about 66.67%
  • 8D+2P: about 80%
  • 16D+2P: about 88.89%

2

RAID 10

High. RAID 10 allows multiple CKs to fail simultaneously. If a CK fails, the mirror CK can be used to recover the data. If a CK and its mirror CK fail simultaneously, RAID 10 protection can no longer be provided.

Relatively high

Relatively high

50%

N (in a RAID 10 disk array with 2N disks)

RAID 50

Relatively high. Parity data is distributed on different CKs of each RAID 5 sub-group. In each RAID 5 sub-group, only one CK is allowed to fail. If two or more CKs of a RAID 5 sub-group fail simultaneously, RAID 50 protection can no longer be provided.

Relatively high

Relatively high

  • (2D+1P) x 2: about 66.67%
  • (4D+1P) x 2: about 80%
  • (8D+1P) x 2: about 88.89%

1

a: D indicates a data block.

b: P indicates a parity block.

NOTE:

For a flexibly configured RAID policy xD+yP, the disk utilization is [x/(x + y)] x 100%.

You can configure RAID policies according to the following rules:

  • For critical service systems, such as billing systems of operators and class-A financial online transaction systems, you are advised to configure RAID 6 (8D+2P) for the performance tier. For non-critical service systems, you are advised to configure RAID 5 (8D+1P) for the performance tier.
  • You are advised to configure RAID 6 for the capacity tier (NL-SAS disks).

You do not need to reserve any capacity for value-added features applied to a file system in the storage pool where the file system resides. This is because the capacity for value-added features is allocated from the file system.

Translation
Download
Updated: 2019-07-12

Document ID: EDOC1000138856

Views: 62140

Downloads: 830

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next