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).
Why Information About the Primary Device and Secondary Device in a Remote Replication Relationship Cannot Be Updated in Real Time?

Why Information About the Primary Device and Secondary Device in a Remote Replication Relationship Cannot Be Updated in Real Time?

Question

Why information about the primary device and secondary device in a remote replication relationship cannot be updated in real time?

Answer

The symptoms and reasons are as follows:

  • Symptom 1

    After data synchronization between the primary LUN and the secondary LUN is initiated, the secondary device does not display the synchronization progress in real time.

    To display the synchronization progress in real time during data synchronization, the secondary device must send a query task to the primary device. This affects system performance.

  • Symptom 2

    After the name of the primary device is changed, the name in remote replication is not updated in real time.

    The name of the primary device in a remote replication task is obtained by invoking the interface of the system management module rather than using the remote replication module. Therefore, after the device name is changed, remote replication cannot detect the change. In this case, you can refresh the information manually or log in to the DeviceManager again. Then, the name of the primary device will be updated.

To obtain the latest information about the primary device and the secondary device in a timely manner, you can log in to the DeviceManager and click Refresh on the remote replication management page.

Download
Updated: 2019-07-11

Document ID: EDOC1000181492

Views: 51483

Downloads: 376

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