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).
What Can I Do if the Logical Bandwidth and the Replication Link Bandwidth Are Not the Same in Asynchronous Remote Replication?

What Can I Do if the Logical Bandwidth and the Replication Link Bandwidth Are Not the Same in Asynchronous Remote Replication?

Question

What can I do if the logical bandwidth and the replication link bandwidth are not the same in asynchronous remote replication?

Answer

Data replication involves following three conditions based on the types of primary and secondary LUNs:

  • The primary LUN is a thin LUN not configured with SmartDedupe and SmartCompression and the secondary LUN is a thin LUN with no space allocated. During initial synchronization, data for which space is not allocated on the primary LUN will not be synchronized to the secondary LUN.
  • The primary LUN is a thick LUN or a thin LUN configured with SmartDedupe and SmartCompression and the secondary LUN is a thin LUN with no space allocated. During initial synchronization, data in the primary LUN is read in sequence and the consecutive 64 KB all-zero data will not be synchronized to the secondary LUN.
  • In other scenarios, during initial synchronization, the system reads data from the primary LUN in sequence. The 64 KB all-zero data is compressed to 4 KB (16:1), synchronized to the secondary LUN, decompressed to 64 KB, and then written to the secondary LUN. Other data is written to the secondary LUN in sequence.

The amount of data to be transmitted is reduced to fully tap into bandwidth resources. As a result, the logical bandwidth and the replication link bandwidth are not the same.

In addition, the logical bandwidth of asynchronous remote replication varies greatly from the replication link bandwidth after link compression is enabled and the performance of asynchronous remote replication drops sharply. Inline compression automatically compresses data when data is sent through links and decompresses data when the secondary storage system receives the data. Inline compression also reduces the amount of data transferred over a network.

Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181492

Views: 48424

Downloads: 363

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