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

HyperReplication 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. It describes the working principle and application scenarios of the HyperReplication feature (for block). Also, it 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).
Creating a Consistency Group

Creating a Consistency Group

Remote replication can implement data backup and DR in a scenario where a host writes data to a single or multiple independent primary LUNs. However, remote replication cannot implement data backup and DR in a scenario where a host writes data to multiple dependent primary LUNs. A consistency group ensures data consistency of secondary LUNs of all remote replication pairs in the group at the same point in time (for example, the data of all secondary LUNs are the data copies of its primary LUNs at 3:00 PM today), thereby ensuring data availability of primary LUNs after DR.

Prerequisites

  • The Role of remote replication pairs to be added to a consistency group must be Primary.
  • The secondary resources in remote replication pairs to be added to a consistency group must be from the same storage device.
  • The Replication Mode of remote replication pairs to be added to a consistency group must be the same as the Replication Mode of the consistency group.

Precautions

  • If a remote replication pair is not in split status, the system will split the remote replication pair first and then add it to a consistency group.
  • A consistency group does not support a remote replication pair whose resource type is file system.
  • After a remote replication pair has been added to a consistency group, the remote replication pair will function according to the replication properties of the consistency group (the properties are Recovery Policy, Speed, Link Compression, Synchronization Method, and Interval), and is not relevant to the properties of the remote replication pair itself.

Procedure

  1. Log in to DeviceManager.
  2. Go to the remote replication consistency group 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 Data Protection > Remote Replication > Remote Replication Consistency Group.
    • vStore user: In the vStore view, choose Data Protection > Remote Replication > Remote Replication Consistency Group.

  3. Click Create.

    The Create Consistency Group Wizard dialog box is displayed.

  4. Configure basic information about the consistency group. Table 4-10 describes related parameters.

    Table 4-10 Consistency group parameters

    Parameter

    Description

    Setting

    Name

    Name of a consistency group.

    [Value range]

    • The name must be unique.
    • The name can contain letters, digits, periods (.), underscores (_), and hyphens (-), and must start with a digit or letter.
    • The name contains 1 to 31 characters.

    [Example]

    ConsistentGroup001

    Description

    Description of a consistency group.

    None

    Replication Mode

    Data replication mode of the consistency group. The value can be:

    • Synchronous

      When data is written on a primary resource, the write request is also sent to the secondary resource. The host receives a successful data write message only after the data is written on both the primary and secondary resources successfully. Synchronous mode ensures that the data on the primary resource and secondary resource is synchronized in real time.

    • Asynchronous

      When data is written to the primary resource successfully, the host receives a successful data write message. In the meanwhile, the primary site records the data difference between the written data and the secondary resource data. In the data synchronization later, only the different data recorded by the primary site is synchronized to the secondary site, reducing the write latency of application server to the minimum.

    [Default value]

    Asynchronous

    Recovery Policy

    After an internal I/O error is rectified or the replication link is up, the consistency group automatically synchronizes data or not. The value can be:

    • Manual

      The consistency group enters the To be recovered state. You need to manually synchronize the data from the primary resource to the secondary resource.

    • Automatic

      The consistency group enters the Synchronizing state. The system will automatically synchronize the data from the primary resource to the secondary resource.

      NOTE:

      For V500R007C30 and later versions, if the write policy of LUNs is write through, remote replication consistency groups cannot be automatically recovered. Check whether the device has a fault. For details, see alarm 0xF0DD0001 in the Event Reference specific to your product model.

    [Default value]

    Automatic

    Speed

    Rate of data synchronization of the consistency group. The value can be:

    • Low

      When the speed is set to low, remote replication 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, remote replication 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, remote replication 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, remote replication will be complete in the shortest period. This value is applicable to scenarios where the service load is light. The speed is normally above 100 MB/s.

    [Default value]

    Medium

    Link Compression

    During data synchronization for the consistency group, data is compressed or not. If you select data compression, the bandwidth pressure of replication links is reduced and the replication performance is improved. The value can be:

    • Compression
    • No compression
    NOTE:

    This parameter is available only when Replication Mode is set to Asynchronous.

    [Default value]

    No compression

    Synchronization Method

    Mode of data synchronization of the consistency group. The value can be:

    • Manual

      Synchronization is performed manually.

    • Timed wait after synchronization begins

      The system starts timing as soon as a synchronization begins. When the time specified in Interval has elapsed, the system automatically starts to synchronize data between the primary resource and secondary resource again.

    NOTE:

    If the latest synchronization is still being executed after the time specified in Interval has elapsed, the data synchronization will start after the latest synchronization finishes.

    • Timed wait after synchronization ends

      The system starts timing as soon as a synchronization ends. When the time specified in Interval has elapsed, the system starts to synchronize data again.

    NOTE:

    This parameter is available only when Replication Mode is set to Asynchronous.

    [Default value]

    Manual

    Interval

    Waiting time for the two synchronization methods: Timed wait after synchronization begins and Timed wait after synchronization ends.

    NOTE:

    This parameter is available only when Synchronization Method is set to Timed wait after synchronization begins or Timed wait after synchronization ends.

    [Value range]

    • An integer ranging from 1 to 1440 (inclusive), when minutes is used as the unit.
    • An integer ranging from 10 to 59 (inclusive), when seconds is used as the unit.

    [Default value]

    60, when minutes is used as the unit.

    30, when seconds is used as the unit.

  5. Select the remote replication pair that you want to add to the consistency group.

    1. Click Next, and in Owning Remote Device of Secondary Resource of Pair, select the remote device.
      NOTE:

      The remote device is the storage device to which the secondary resource of the remote replication pair to be added into the consistency group belongs.

    2. From the Available Remote Replication Pairs list, select one or multiple remote replication pairs and click to add.

  6. Confirm the consistency group creation.

    1. Click Next and view the configuration summary of the consistency group to be created.
    2. Click Finish to create the consistency group.

      The security alert dialog box is displayed.

    3. Read the content in the dialog box carefully, and select I have read and understand the consequences associated with performing this operation.
    4. Click OK.

      The Execution Result page is displayed.

    5. On Execution Result page, check whether the consistency group is created successfully.
    6. Click Close.

Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181492

Views: 51309

Downloads: 376

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