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


To have a better experience, please upgrade your IE browser.


OceanStor 2600 V3 Storage System V300R005 HyperMetro Feature Guide 06

"This document describes the implementation principles and application scenarios of theHyperMetro feature. Also, it explains how to configure and manage HyperMetro."
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).


This section describes basic concepts of HyperMetro, including local logical unit number (LUN), remote LUN, dual-write, data change log (DCL), HyperMetro pair, HyperMetro consistency group, synchronization, paused, force start, priority switchover and so on.

Local LUN and Remote LUN

Local LUNs are LUNs that belong to the local storage system. Remote LUNs are LUNs that belong to the remote storage system.


Dual-write enables the synchronization of application host I/O requests with both local and remote LUNs.


DCLs record changes in the data of storage systems. The DCL is stored on all the disks in the disk domain and four-disk RAID 1 is used for data protection.

HyperMetro Domain

A HyperMetro domain consists of the local and remote storage systems, and the quorum server. Application servers can access data across data centers using a HyperMetro domain.

HyperMetro Pair

A HyperMetro pair indicates an active-active relationship between a local and remote LUN. With HyperMetro configured, a local and remote LUN form a HyperMetro pair. You must create HyperMetro pairs in a HyperMetro domain. By viewing the state of a HyperMetro pair, you can determine whether you need to perform operation such as synchronization, suspension, and priority switchover. After performing an operation, you can view the state of the HyperMetro pair to determine whether the operation succeeded. Configure a HyperMetro domain before configuring HyperMetro pairs.

HyperMetro Consistency Group

A HyperMetro consistency group is a collection of HyperMetro pairs that have a service relationship with each other. For example, the local storage system has three local LUNs that respectively store service data, logs, and change tracking information of a database. If data on any of the three LUNs becomes invalid, all data on the three LUNs becomes unusable. Upon configuration, create a consistency group and add the three HyperMetro pairs to the consistency group.


Synchronization refers to the synchronization of differential data between a local LUN and a remote LUN. Data synchronization takes place between two LUNs in a HyperMetro pair. You can synchronize data in multiple HyperMetro pairs in a consistency group.


Pause is a state indicating the suspension of a HyperMetro pair.

Force Start

To ensure data consistency when the local and remote storage systems malfunction simultaneously, HyperMetro stops hosts from accessing both. To quickly restore services, you can forcibly start the local or remote storage system.

Priority Switchover

Priority switchover indicates that the preferred site takes precedence during arbitration. If the HyperMetro replication network is down, the storage system that wins arbitration continues providing services to hosts. After the creation of a HyperMetro pair, the local data center is by default the preferred site and the remote data center is the non-preferred site.

Locking Mechanism

To prevent different host I/Os from being written to the same location in the storage system at the same time, the storage system uses the locking mechanism to prevent access conflicts. The host I/O can only be written to the storage system that obtains the locking mechanism.

Updated: 2018-09-03

Document ID: EDOC1000106183

Views: 26738

Downloads: 269

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