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

SmartTier Feature 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, 18500 V5, and 18800 V5. This document describes the working principle and application scenarios of the SmartTier (for block) feature. It also explains how to configure and manage the feature.
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).
Modifying a SmartTier Policy

Modifying a SmartTier Policy

You can modify the LUNs' SmartTier policy by batch to meet the actual requirements.

Prerequisites

eDevLUN does not support SmartTier.

Procedure

  1. Log in to DeviceManager.
  2. Go to the LUN page.

    The operation path varies with user types:

    • System user: Click vStore, select the desired vStore, and click Details to go to the vStore view. Choose Provisioning > LUN.
    • vStore user: In the vStore view, choose Provisioning > LUN.

  3. Select a LUN and choose More > Modify SmartTier Policy.

    The Modify SmartTier Policy dialog box is displayed. The related policies are shown in Table 3-6.

    Table 3-6 SmartTier policy parameters

    Parameter

    Description

    Value

    SmartTier Policy

    The data migration policies include:

    • Automatic relocation

      SmartTier relocates data based on the ranking order of data blocks and activity levels of LUNs in a storage pool. Automatic relocation relies on the analysis result from the I/O monitoring. Thus I/O monitoring must be enabled and the service monitoring period must be set before automatic relocation.

    • Relocation to high-performance tier

      The relocation to high-performance tier policy is recommended for the applications (such as OLTP databases) sensitive to response time, IOPS, and bandwidth. This policy preferentially promotes data blocks to the high-performance tier and the performance tier. If the capacity of the data blocks to be relocated is larger than the capacity of the high-performance tier (or performance tier), only data blocks with the most activities are promoted to the high-performance tier (or the performance tier).

    • Relocation to low-performance tier

      The relocation to low-performance tier policy is recommended for applications (such as file sharing) insensitive to performance requirements. This policy preferentially demotes data blocks to the performance tier and the capacity tier, regardless of the activity levels of these data blocks.

    • No relocation

      The no relocation policy does not relocate data blocks among storage tiers, and data can be relocated only when the data relocation policy is changed.

    [Example]

    Automatic relocation

  4. Select a new policy and click OK.

    The Execution Result dialog box is displayed.

  5. Click Close to finish modifying policy.
Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181474

Views: 14318

Downloads: 307

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