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.


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).
Functions of a Consistency Group

Functions of a Consistency Group

In medium- and large-sized database applications, data, logs, and modification information are stored on different LUNs that have relationships with each other. If data on one of the LUNs becomes unavailable, data on the other LUNs also becomes unavailable. Adding LUN pairs to a consistency group ensures the availability of data on the LUNs.

Users can perform synchronization, splitting, and primary/secondary switchovers for a single remote replication pair or perform these operations for multiple remote replication pairs using a consistency group. Note the following when using a consistency group:

  • Remote replication pairs can be added to a consistency group only on the primary storage system. In addition, secondary LUNs in all remote replication pairs must reside in the same remote storage system.
  • LUNs in different remote replication pairs in a consistency group can belong to different working controllers.
  • Remote replication pairs in one consistency group must work in the same remote replication mode.

The following compares remote replication without using a consistency group with remote replication using a consistency group to show how a consistency group is used to prevent data from becoming unusable.

Remote Replication Without Using a Consistency Group

Associated LUNs that are not added to a consistency group are at a risk of becoming unavailable, as shown in Figure 1-6.

Figure 1-6 Remote replication without using a consistency group

Remote Replication Using a Consistency Group

If associated LUNs are added to a consistency group, data unavailability is prevented, as shown in Figure 1-7.

Figure 1-7 Remote replication using a consistency group
Updated: 2019-07-11

Document ID: EDOC1000181492

Views: 50957

Downloads: 375

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