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 Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5300 V5, 5500 V5, 5600 V5, 5800 V5, 6800 V5, 5300F V5, 5500F V5, 5600F V5, 5800F V5, 6800F V5, 18500 V5, 18800 V5, 18500F V5, and 18800F V5. 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).
Creating a Disk Domain

Creating a Disk Domain

This section describes how to create a disk domain.

Context

You are advised to use different disk domains to create storage pools for the block storage service and file storage service.

To prevent data loss or performance deterioration caused by a member disk failure, a storage system uses hot spare space to take over data from the failed member disk. The following hot spare policies are supported:

  • High

    The capacity of one disk is used as hot spare space if the number of disks at a storage tier is equal to or fewer than 12. The hot spare space non-linearly increases as the number of disks increases.

  • Low

    The capacity of one disk is used as hot spare space if the number of disks at a storage tier is equal to or fewer than 25. The hot spare space non-linearly increases as the number of disks increases.

    Number of disks of which capacity is used as hot spare space in a low hot spare policy = Number of disks of which capacity is used as hot spare space in a high hot spare policy/2 (rounded up)

  • None (not supported by 18000 or 18000F series storage systems)

    The storage system does not provide any hot spare space. In the event a member disk in a disk domain fails, the storage system uses the free capacity in the disk domain for reconstruction. If the free capacity in the disk domain is insufficient, the storage system uses the unallocated capacity in storage pools for reconstruction. If reconstruction fails, the disk domain will change to the Degrade state, which will cause the read/write performance to deteriorate, affecting the storage system reliability.

Table 4-3 describes how hot spare space changes for a single engine with the number of disks in V500R007C30 and earlier (excluding V500R007C30SPH105). The hot spare space changes at a storage tier are used as an example here. The hot spare space changes at different storage tiers are the same.

Table 4-3 Changes of hot spare space for a single engine

Number of Disks

Number of Disks of Which Capacity Is Used as Hot Spare Space in a High Hot Spare Policya

Number of Disks of Which Capacity Is Used as Hot Spare Space in a Low Hot Spare Policya

(1, 12]

1

1

(12, 25]

2

(25, 50]

3

2

(50, 75]

4

(75, 125]

5

3

(125, 175]b

6

(175, 275]

7

4

(275, 375]

8

a: Huawei storage systems use RAID 2.0+ virtualization technology. Hot spare capacity is provided by member disks in each disk domain. Therefore, the hot spare capacity is expressed in the number of disks in this table.

For example, if a disk domain is composed of 12 SSDs and the high hot spare policy is used, the hot spare space occupies the capacity of one SSD and the capacity is provided by member disks in the disk domain. If a disk domain is composed of 13 SSDs and the high hot spare policy is used, the hot spare space occupies the capacity of two SSDs.

b: When the number of disks at a storage tier reaches 175, the storage tier uses the capacity of one disk in every 100 additional disks as the hot spare space in a high hot spare policy.

Table 4-4 describes how hot spare space changes for a single engine with the number of disks in V500R007C30SPH105 and V500R007C50 and later. The hot spare space changes at a storage tier are used as an example here. The hot spare space changes at different storage tiers are the same.

Table 4-4 Changes of hot spare space for a single engine

Number of Disks

Number of Disks of Which Capacity Is Used as Hot Spare Space in a High Hot Spare Policya

Number of Disks of Which Capacity Is Used as Hot Spare Space in a Low Hot Spare Policya

(1, 12]

1

1

(12, 25]

2

(25, 125]b

3

2

(125, 325]

4

……

a: Huawei storage systems use RAID 2.0+ virtualization technology. Hot spare capacity is provided by member disks in each disk domain. Therefore, the hot spare capacity is expressed in the number of disks in this table.

For example, if a disk domain is composed of 12 SSDs and the high hot spare policy is used, the hot spare space occupies the capacity of one SSD and the capacity is provided by member disks in the disk domain. If a disk domain is composed of 13 SSDs and the high hot spare policy is used, the hot spare space occupies the capacity of two SSDs.

b: When the number of disks at a storage tier reaches 125, the storage tier uses the capacity of one disk in every 200 additional disks as the hot spare space in a high hot spare policy.

NOTE:
  • After a storage system is upgraded to V500R007C30SPH105 or V500R007C50, hot spare space in the disk domains created before the upgrade will be re-calculated according to the rules in Table 4-4.
  • Number of Disks in the above tables refers to the number of same-type disks owned by a same engine. If you select disks from multiple engines to create a disk domain, calculate the number of disks used for hot spare space on each engine and sum up the values.
  • For 18000 and 18000F series storage systems, the high hot spare policy is used by default. You are not allowed to modify the hot spare policy on DeviceManager. To modify the hot spare policy, run the change disk_domain general command in the CLI.
  • When you are creating a disk domain, ensure that the disks used to provide hot spare space are sufficient.
  • Hot spare space can be used for a specific disk domain only.
  • Common capacity changes of the hot spare space are listed in this section. The number of disks supported by a storage system and the capacity of hot spare space are based on actual specifications.

Procedure

  1. Log in to DeviceManager.
  2. Choose Provisioning > Disk Domain.
  3. Click Create.

    The Create Disk Domain dialog box is displayed.

  4. Name and describe the disk domain.

    1. Specify Name.
      NOTE:
      • The name must be unique.
      • The name can contain only letters, digits, periods (.), underscores (_), and hyphens (-).
      • The name must contain 1 to 31 characters.
    2. Specify Description.

      Descriptive information, such as the function and properties of the disk domain, helps identify the disk domain.

  5. In Encryption Type, select a type to determine whether the disk domain is created by using self-encrypting disks.

    Encryption types include:

    • Non-Encrypting Disk: creates an unencrypted disk domain.
    • Self-Encrypting Disk: creates an encrypted disk domain.
      NOTE:
      • Non-Encrypting Disk: Non-encrypting disks are common disks that do not support the encryption function.
      • Self-Encrypting Disk: When data is written into or read from a self-encrypting disk, the data is encrypted or decrypted using the hardware circuit and internal encryption key of the disk. Before using self-encrypting disks, configure the key service by following instructions in the Disk Encryption User Guide specific to your product model and version.
      • Self-encrypting and non-encrypting disks cannot co-exist in the same disk domain.

  6. Select the disks that comprise the disk domain. There are three ways to select disks:

    NOTE:

    GUIs may vary with product versions and models. The actual GUIs prevail.

    For 18000 and 18000F series storage systems, the high hot spare policy is used by default. You are not allowed to configure the hot spare policy on DeviceManager. To modify the hot spare policy, run the change disk_domain general command in the CLI.

    • Select All available disks.

      Configure the hot spare policy for each storage tier.

      NOTE:

      You are not advised to select All available disks. You are advised to select Manually select to ensure that all disks in a disk domain are from the same controller enclosure, reducing the disk failure probability and improving the read and write performance of disks.

    • Select Specify disk type or Specify the number of disks.
      NOTE:

      For some models, you can only configure Specify disk type or Specify the number of disks.

      • Select Specify disk type.
        1. Select the storage tier according to the storage media of disks.
        2. Configure the number of disks for each storage tier.
        3. Configure the hot spare policy for each storage tier.
      • Select Specify the number of disks.

        Specify the number of disks composing the storage tier.

    • Select Manually select.
      1. Click Select.
      2. In the Select Disk dialog box, select the disks you need and click .
      3. Click OK.
      4. Configure the hot spare policy for each storage tier.
    NOTE:

    If you plan to create a RAID 10 storage pool in the disk domain that you are creating, you are advised to manually select an even number of disks owned by each controller enclosure for each storage tier in the disk domain to ensure the reliability of RAID 10.

    You are advised to configure a maximum of 100 disks for each tier in a disk domain. For example, if the number of disks on a tier is D (divide D by 100 and then round off the result to N and the remainder is M), you can refer to the following configurations:

    • If D ≤ 100, configure all disks on this tier in one disk domain.
    • If D > 100, create N+1 disk domains and evenly distribute all disks to the N+1 disk domains. That is, the number of disks in each disk domain is D/(N+1). In addition, it is recommended that disk enclosures be fully configured.
    • For SmartTier, it is recommended that a maximum of 100 disks be configured for each tier in a disk domain. The configuration of disks on each tier also follows the preceding principle. Some product models do not support SmartTier. To check whether your product model support SmartTier, see its product description.

    Example 1: The total number of SSDs in a storage system is 328, which is the value of D. (Divide 328 by 100. Round off the result to 3, which is the value of N. The remainder is 28, which is the value of M). You are advised to configure four disk domains, each of which contains 328/4 = 82 SSDs.

    Example 2: The total number of SSDs in a storage system is 223, which is the value of D. (Divide 223 by 100. Round off the result to 2, which is the value of N. The remainder is 23, which is the value of M). You are advised to configure three disk domains, each of which contains 223/3 = 74.3 disks. In this case, two disk domains are configured with 74 disks respectively and the other disk domain is configured with 75 disks.

    Example 3: If a disk domain consists of SSDs, SAS disks, and NL-SAS disks, for SmartTier, the number of disks of each type cannot exceed 100.

    If a project requires a disk domain containing over 100 disks to meet capacity and service planning requirements, contact Huawei technical support engineers for evaluation.

  7. Click OK.

    A message is displayed, indicating that the operation succeeded.

  8. Click OK.
Download
Updated: 2019-08-30

Document ID: EDOC1000181506

Views: 73936

Downloads: 560

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