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 18500, 18800, and 18800F Storage System V100R001C30 Remote Replication Feature Guide 09

This document describes the remote replication feature, in terms of the implementation principle, application scenario, configuration process, and reference information.
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).
Viewing Remote Replication Information

Viewing Remote Replication Information

This operation enables you to view information about existing remote replication pairs, so that you can effectively monitor the status of remote replication.

Context

  • On the remote replication management page, you can click Refresh to refresh remote replication pair information.
  • On the remote replication management page, you can click Keyword and enter keywords to search for the desired remote replication pair information.
  • On the remote replication management page, you can click and select the pair information items you want to view.

Procedure

  1. Go to the remote replication management page.
    1. On the right navigation bar, click .

      The data protection page is displayed.

    2. In the left function pane, click Remote Replication.
    3. Click the Remote Replication tab.

      The remote replication management page is displayed.

  2. View basic information about an existing remote replication. Table 4-14 describes related parameters.

    Table 4-14  Remote replication parameters

    Parameter

    Description

    Value

    Local LUN Name

    Name of a local LUN.

    [Example]

    LUN001_001

    Local LUN ID

    ID of a local LUN.

    [Example]

    2

    Remote LUN Name

    Name of a remote LUN.

    [Example]

    memlunName01

    Remote LUN ID

    ID of a remote LUN.

    [Example]

    42

    Remote Device Name

    Name of a remote device.

    [Example]

    testname01

    Remote Device SN

    SN of a remote device.

    [Example]

    210235G6LLZ0B8000005

    Pair ID

    ID of a remote replication pair.

    [Example]

    200bc71fa9c20000

    Role

    The local LUN of the remote replication pair is the primary LUN or not. If the local LUN is the primary LUN, it displays as Primary. Otherwise, it displays as Secondary.

    [Example]

    Primary

    Pair Health Status

    Indicates whether the remote replication pair is functioning normally. The values include:
    • Normal: The pair is functioning normally. You can perform the synchronization operation.
    • Fault: The primary LUN or secondary LUN of the pair malfunctions or the replication link is down, you cannot perform the synchronization operation.

    [Example]

    Normal

    Pair Running Status

    Indicates whether the remote replication pair is running properly. The values include:
    • Normal: Pair has completed synchronization successfully.
    • Synchronizing: Pair is synchronizing data.
    • Split: Pair is in the split status, and the synchronization is suspended.
    • Interrupted: The remote replication internal I/O error or the replication link is down, and you cannot perform the synchronization operation temporarily.
    • To be recovered: After the remote replication internal I/O error is rectified or the replication link is up, and if Recovery Policy is Manual, the pair enters this status. You need to manually start synchronization for the pair to synchronize data.
    • Invalid: The pair is useless and cannot be restored in this status, except deleting it. You must delete the pair on both primary and secondary storage devices. Otherwise, the pair creation may fail.

    [Example]

    Normal

    Remote Replication Consistency Group

    Name of the owning consistency group of the remote replication pair.

    [Example]

    ConsistentGroup001

    Replication Mode

    Mode of the data replication. The values include:
    • Synchronous: When data is written on a primary LUN, the write request is also sent to the secondary LUN. Only after the data is written on both the primary and secondary LUNs successfully, does the host receive a successful data write message. Synchronous mode ensures that the data on the primary LUN and secondary LUN synchronize in real-time.
    • Asynchronous: When data is written on a primary LUN successfully, the host receive a successful data write message. In the meanwhile, the primary site records the data difference between the written data and the secondary LUN. In the data synchronization later, only the different data the primary site records are synchronized to the secondary site, reducing the write latency of application server to the minimum.

    [Example]

    Synchronous

    Recovery Policy

    After the remote replication internal I/O error is rectified or the replication link is up, the remote replication pair automatically synchronizes data or not. The values include:
    • Manual: The pair enters the To be recovered state. You need to manually synchronize the data from the primary LUN to the secondary LUN in the pair.
    • Automatic: The pair enters the Synchronizing state. The system will automatically synchronize data from the primary LUN to the secondary LUN in the pair.

    [Example]

    Automatic

    Primary LUN Data Status

    Status of data on the primary LUN.

    [Example]

    Consistent

    Secondary LUN Data Status

    Status of the secondary LUN. The data status between the primary LUN and secondary LUN includes:

    • Synchronized: Data in the secondary LUN is the same as that in the primary LUN. Data availability is the highest.
    • Consistent: Data in the secondary LUN is a duplicate of the data in the primary LUN (at the time the latest successful synchronization starts). In this state, data in the secondary LUN is available but not necessarily the same as the current data in the primary LUN.
    • Inconsistent: Data in the secondary LUN is not a duplicate of the data in the primary LUN (at the current point in time or at the time the previous synchronization is ended). In this state, data in the secondary LUN is unavailable. You can synchronize the data to ensure data consistency between the primary LUN and secondary LUN.

    [Example]

    Consistent

Download
Updated: 2019-01-28

Document ID: EDOC1000077758

Views: 10962

Downloads: 65

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