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

HyperClone Feature Guide for Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5110F V5, 5300 V5, 5300F V5, 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, 5800F V5, 6800 V5, 6800F V5, 18500 V5, 18500F V5, 18800 V5, and 18800F V5. This document describes the implementation principles and application scenarios of the clone feature. Also, it explains how to configure and manage clones.
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).
Adding a LUN Clone Pair

Adding a LUN Clone Pair

To obtain data copies of the same source data for data analysis, data mining, and online testing, you can create a clone and add secondary LUNs to the clone with replication parameters properly set. Then, the storage system will initiate clone pair synchronizations to copy data from the primary LUN to the secondary LUNs according to your settings.

Prerequisites

Before adding a secondary LUN to a clone, make sure:

  • The storage system has LUNs that are equally sized to the primary LUN.
  • The Running Status and Data Status of the existing clone pairs meet requirements. Table 2-11 describes the status requirements.
    Table 2-11 Status requirements for adding secondary LUNs

    Running Status

    Data Status

    Whether Secondary LUNs Can Be Added

    Synchronizing

    Synchronizing

    Yes

    Queuing

    Inconsistent

    Yes

    Queuing

    Consistent

    Yes

    Split

    Inconsistent

    Yes

    Split

    Consistent

    Yes

    Split

    Reverse inconsistent

    No

    Normal

    Consistent

    Yes

    Interrupted

    Inconsistent

    Yes

    Interrupted

    Consistent

    Yes

    Interrupted

    Reverse inconsistent

    No

    To be recovered

    Inconsistent

    Yes

    To be recovered

    Consistent

    Yes

    To be recovered

    Reverse inconsistent

    No

    Reversely synchronizing

    Reversely synchronizing

    No

Precautions

Precautions for adding secondary LUNs are as follows:

  • The owning controller of the secondary LUNs must be the same as that of the primary LUN.
  • When a clone does not have a secondary LUN, the primary LUN is read and written in the same way as a LUN that is not added to a clone.

Procedure

  1. Log in to DeviceManager.
  2. Choose Data Protection > Clone.
  3. Select the clone to which you want to add a clone pair, and choose More > Add Pair.

    The Add Pair dialog box is displayed.

  4. Set the properties of the clone pair. Table 2-12 describes the parameters of a clone pair.

    Table 2-12 Clone pair properties

    Parameter

    Description

    Value

    Copy Speed

    Speed of data synchronization between the primary and secondary LUNs. Possible values are as follows:

    • Low: When the speed is set to low, the data synchronization will take a long time. This value is applicable to scenarios where the service load is heavy. The speed is normally from 0 to 5 MB/s.
    • Medium: When the speed is set to medium, the data synchronization will take a relatively short period. This value is applicable to scenarios where the service load is relatively heavy. The speed is normally from 10 to 20 MB/s.
    • High: When the speed is set to high, the data synchronization will take a short period. This value is applicable to scenarios where the service load is relatively light. The speed is normally from 50 to 70 MB/s.
    • Highest: When the speed is set to highest, the data synchronization will take the shortest period. This value is applicable to scenarios where the service load is light. The speed is normally above 100 MB/s.

    [Example]

    Medium

    Recovery Policy

    In the event of a system problem such as a disk array fault or a LUN failure, all the pairs in a clone are interrupted. For synchronization or reverse synchronization tasks that are ongoing when a system problem occurs:

    • If Recovery Policy is Automatic, suspended tasks automatically resume once the problem is resolved.
    • If Recovery Policy is Manual, the value of Pair Running Status changes to To be recovered once the system problem is resolved. In this case, you can check the system before deciding whether to manually resume the suspended tasks.

    [Example]

    Automatic

    Enable initial synchronization

    Indicates whether to implement an initial synchronization of data from the primary LUN to the secondary LUN.

    NOTE:

    Initial synchronization ensures data consistency between the primary and secondary LUNs. You are advised to enable initial synchronization.

    [Example]

    Enable

  5. Add a clone pair.

    1. In the Available Secondary LUNs area, select the desired secondary LUN.
    2. Click .

      The secondary LUN is moved to the Selected Secondary LUNs area.

      NOTE:

      If no secondary LUN is available, click Create Secondary LUN and create a secondary LUN.

    3. Click OK.

      The security alert dialog box is displayed.

  6. Confirm the adding of the clone pair.

    1. Confirm information in the Warning dialog box carefully and select I have read and understand the consequences associated with performing this operation.
    2. Click OK.

      The Execution Result dialog box is displayed, indicating that the operation succeeded.

    3. Click Close.

      The clone management page is displayed.

Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181501

Views: 21996

Downloads: 220

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