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

OceanStor 9000 V300R005C00 File System Feature Guide 11

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).
Configuring InfoTier

Configuring InfoTier

InfoTier configurations include the configuration of tiers, node pools, and file pool policies. After InfoTier configuration, data that is newly written to the storage system is stored to the specified location based on the rules, and data that has been stored in the storage system is automatically migrated based on the migration policy.

Creating a Storage Tier

Different logical storage tiers can be created for different storage services.

Procedure

  1. Log in to DeviceManager.
  2. Choose Provisioning > InfoTier > Tier Management.
  3. Click Create in the upper part of the page as shown in Figure 3-11.

    Figure 3-11  Creating a storage tier

  4. In the Create Tier window that is displayed, enter a name for the storage tier in Name, and click OK.

    A policy name can contain 1 to 127 letters, digits, periods (.), hyphens (-), and underscores (_), and it must start with a letter and cannot end with a period (.), a hyphen (-), or an underscore (_).

  5. In the Success dialog box that is displayed, click OK. The added storage tier is displayed in the function pane.

Creating a Node Pool

The system combines nodes of the same type into node pools, which can then be combined into one tier. Different tier types deliver different performance.

Procedure

  1. Log in to DeviceManager.
  2. Select Choose Settings > Cluster Settings > Cluster Node Settings > Node Pool Settings.
  3. Create a node pool.
    1. Click Create.
    2. In the Create Node Pool dialog box that is displayed, set all planned node pool parameters. Then click OK, as shown in Figure 3-12.

      Table 3-10 describes the related parameters.

      Figure 3-12  Create Node Pool

      Table 3-10  Information about a node pool
      Parameter Description Setting

      Name

      Defines the name of a node pool to facilitate the management and maintenance of the node pool.

      [Description]

      • A node pool name contains 1 to 127 characters among letters, digits, hyphens (-), underscores (_), and periods (.).
      • It must start with a letter and cannot end with a hyphen (-), underscore (_), or period (.).

      [Example]

      NodePool_C

      Owning Tier

      Defines the storage tier to which a node pool belongs.

      [Example]

      tierC

      Read-only watermark alarm threshold(%)

      After the node pool capacity usage exceeds the read-only watermark threshold, the system reports an alarm and no data can be written to the node pool. If data is being written to the node pool, the system returns a failure message.

      [Description]

      By default, Read-only watermark means that 90% of the total disk capacity of a node pool is used. Administrators can modify Read-only watermark. The value ranges from 85% to 100%.

      When the node pool capacity usage is recovered from Read-only watermark to Recovery read-only watermark, the system clears the alarm generated when the read-only watermark threshold is reached and the node pool is not in the read-only state. However, no new data can be written to the node pool.

      [Default value]

      90%

      High watermark alarm threshold(%)

      After the node pool capacity usage exceeds the high watermark threshold, the system reports an alarm.

      [Description]

      By default, High watermark means that 85% of the total disk capacity of a node pool is used. Administrators can modify High watermark. The value ranges from 80% to 95%. High watermark must be lower than Read-only watermark.

      When the node pool capacity usage is recovered from High watermark to Recovery watermark, the system clears the alarm generated when the high-watermark threshold is reached and new data can be written to the node pool.

      [Default value]

      85%

      Recovery read-only watermark recovery threshold(%)

      After the node pool capacity usage exceeds the recovery read-only watermark threshold, the system clears the alarm generated when the read-only watermark threshold is reached and the node pool is not in the read-only state. The new data can be written to the node pool.

      [Description]

      By default, Recovery read-only watermark means that 85% of the total disk capacity of a node pool is used. Administrators can modify Recovery read-only watermark. The value ranges from 80% to 95%. Recovery read-only watermark must be lower than Read-only watermark.

      [Default value]

      85%

      High Watermark Recovery threshold(%)

      After the node pool capacity usage exceeds the recovery watermark threshold, the system clears the alarm generated when the high-watermark threshold is reached.

      [Description]

      By default, Recovery watermark means that 80% of the total disk capacity of a node pool is used. Administrators can modify Recovery watermark. The value ranges from 75% to 90%. Recovery watermark must be lower than Recovery read-only watermark and High watermark.

      [Default value]

      80%

      Enable Spillover

      Specifies whether files can be stored to a migration node pool when the capacity usage of the node pool specified for storing the files exceeds Read-only watermark.

      [Description]

      • Disable Spillover: When new files need to be stored but the capacity usage of the node pool specified for storing the files exceeds Read-only watermark alarm threshold, the files fail to be stored.
      • Enable Spillover: When new files need to be stored but the capacity usage of the node pool specified for storing the files exceeds Read-only watermark alarm threshold, the files will be stored in a migration node pool.

      Multi-tier Spillover is not allowed. If node pool A is configured to spill over to node pool B, node pool B cannot be configured to spill over to node pool C.

      [Default value]

      Disable Spillover

      Target Node Pool

      After Spillover is enabled, a node pool must be selected for storing migrated files.

      Click Select. In the Select Target Node Pool dialog box that is displayed, select a node pool for storing migrated files.

      Only one node pool can be selected for storing migrated files.

      • Any node pool: When the used capacity of a node pool reaches the read-only watermark and Spillover is specified, data can no longer be written into the node pool and is written into other node pools.
      • Specified node pool: When the used capacity of a node pool reaches the read-only watermark and Spillover is specified, data can no longer be written into the node pool and is written to the specified node pool.

      [Description]

      Any Node Pool

    3. Click OK after the Success dialog box is displayed.

      In the function pane, view the node pool that you have added.

Configuring a File Pool Policy

An administrator can configure a file pool policy to fully utilize the InfoTier function. When the system automatically migrates files across storage tiers, the storage performance is improved and the total cost of storage is reduced.

Prerequisites

At least one storage tier exists.

Do not specify an empty node pool when configuring the policy.

Procedure

  1. Log in to DeviceManager.
  2. Choose Provisioning > InfoTier > File Pool Policy.
  3. Click Create. The Create File Pool Policy Wizard page is displayed.
  4. In Name, enter a name for the file pool policy that you want to create, and click Next.

    A policy name can contain 1 to 127 characters, chosen from letters, digits, periods (.), hyphens (-), and underscores (_). It must start with a letter and cannot end with a period (.), a hyphen (-), or an underscore (_).

  5. Optional: Set the following optional parameters if necessary to further customize the file properties as shown in Figure 3-13, and then click Next.

    • File path: specifies a storage tier and a node pool for a specific path.
    • File name: specifies storage policies for files with same properties by defining the common parts of file names. Wildcard characters * and ? are supported.
    • Users/Groups: specifies the owning user or user group of a file to determine the storage tier of the file.
    • File size: specifies a storage tier for a file according to its file size (unit: KB, MB, or GB).
    Figure 3-13  Setting a file property policy

  6. Optional: Set the following optional parameters if necessary to further customize the time policy, and then click Next.

    • Modified on: specifies a storage tier based on the time interval between the latest file modification time and the current time (unit: hour or day).
    • Created on: specifies a storage tier based on the time interval between the file creation time and the current time (unit: hour or day).
    • Lastly accessed on: specifies a storage tier based on the time interval between the last file access time and the current time (unit: hour or day).

  7. Optional: Set the following optional parameters if necessary to further customize the performance policy as shown in Figure 3-14, and then click Next.

    • I/O count: specifies a storage tier based on the times that a file is accessed within a specific statistical period. A statistical period can be 1 to 7 days.
      NOTE:
      The methods of calculating I/O counts vary when different protocols or versions are used.
      • When the NFSv3 protocol is used, each read/write operation is considered as an I/O count. For example, if you open a file and close the file after performing 10 write operations for the file, the value of the I/O count is 10.
      • When the NFSv4 protocol is used, each complete file operation, that is, opening and closing a file, is considered as an I/O count. For example, if you open a file and close the file after performing 10 write operations for the file, the value of the I/O count is 1.
    • I/O popularity: specifies a storage tier based on the access popularity of a file within a specific statistical period. A statistical period can be 1 to 7 days.

      The I/O popularity indicates the ratio of the access bytes to the file size within a specific statistical period. Calculation formula: I/O popularity = (Access bytes/File size) x 100.

    • Enable SSD Acceleration: After SSD acceleration is enabled, the files that comply with the file pool policy will be stored to the SSDs for the highest storage performance. You are advised to enable this function for the files smaller than 256 KB.
    Figure 3-14  Setting performance policy

  8. Select a file storage tier that matches the policy, and then click Next.

    NOTE:

    If any or all of parameters File path, File name, and Users/Groups are specified, the node pool for file storage can be specified. If parameters other than the preceding three are specified, you can only specify the storage tier and cannot specify the node pool for file storage.

    • Set Operation Type to Save to Any Tier, indicating that files matching the policy can be randomly stored on all storage tiers according to system capacity.
    • Set Operation Type to Save to Specific Tier and select an existing storage tier, indicating that files matching the policy can only be stored on the selected storage tier.
    • Set Operation Type to Save to Specific Node Pool and select an existing node pool, indicating that files matching the policy can only be stored on the selected node pool.

  9. Confirm the file pool policy and then click Finish.

    The Execution Result dialog box is displayed, and click Close. The file pool policy is created.

Translation
Download
Updated: 2019-03-30

Document ID: EDOC1000101823

Views: 19619

Downloads: 99

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