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.


Event Reference

OceanStor Dorado V3 Series V300R001

This document is applicable to OceanStor Dorado5000 V3, Dorado6000 V3 and Dorado18000 V3. This document describes the basic knowledge about the events of storage system in terms of event definition, event level, impact on the system, possible cause, and handling procedure. The document that you browse online matches the latest C version of the product. Click Download to download documents of other C versions.
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).
0xF00270039 Remote Replication Is Unavailable

0xF00270039 Remote Replication Is Unavailable


The properties of the local and remote storage devices of a remote replication pair are inconsistent, causing the remote replication pair to be unavailable.

Applicable Model

Applicable to all models.



Event Level

Automatically Cleared




Impact on the System

Data cannot be backed up correctly.

Possible Causes

  • If you choose to ensure the data integrity of secondary resources when deleting data after pair splitting during incremental synchronization of asynchronous remote replication, the data on secondary LUNs will be rolled back and the remote replication service becomes invalid.
  • The remote replication is deleted on the local end after being interrupted.
  • When the secondary LUN of an asynchronous remote replication session is set to writable, the secondary LUN rollback fails.


  1. Check whether the data on the secondary LUNs of the invalid remote replication is being rolled back.

    1. If yes, wait until the rollback is completed. Then, the alarm will automatically be cleared.
    2. If no=> Step2.

  2. Check whether an alarm is reported indicating a data rollback failure on the secondary LUNs.

    1. If yes, perform recommended actions to handle alarms.
    2. If no=> Step3.

  3. Collect all related information and contact technical support engineers.
Updated: 2018-10-19

Document ID: EDOC1000141827

Views: 84939

Downloads: 168

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