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

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).
Member LUNs in a HyperMetro Pair Cannot Be Accessed by Hosts

Member LUNs in a HyperMetro Pair Cannot Be Accessed by Hosts

Symptom

The member LUNs in a HyperMetro pair cannot be accessed by hosts and HyperMetro services are interrupted. In OceanStor DeviceManager, the status of the HyperMetro pair is Access denied.

Alarm Information

HyperMetro is disconnected or the HyperMetro pair is disconnected.

Possible Causes

  • Storage arrays at two sites are faulty.
  • The quorum server breaks down and a storage array or a link is down.
  • A LUN fault or I/O timeout occurs on both storage arrays.
  • After HyperMetro synchronization is complete, a link of the quorum server is down or a link between storage arrays is down within two minutes.

Fault Diagnosis

  1. Check whether a storage array and a controller are reset and locate the causes. Determine whether the storage array and controller are reset concurrently.
    NOTE:

    In static priority mode, if two storage arrays are reset, the storage array at the preferred site wins the arbitration. After the storage array is restarted, it takes over services. This problem does not occur in this situation.

    Cause: An arbitration request is submitted after the storage arrays are reset. However, the arbitration request fails to be submitted because links are disconnected.

  2. After confirming that no storage array and controller are reset, perform the following operations:
    1. Run the show hyper_metro_domain general command to check whether the quorum server is faulty. Check whether the name of the quorum server is displayed (you can also check the name in OceanStor DeviceManager). If the name of the quorum server is not displayed, locate the causes of the quorum server fault and rectify the faults. Then check whether an alarm is generated indicating the disconnection of a quorum server link.

    2. Run the show remote_device general command or use OceanStor DeviceManager to check the link status. If the link status is normal, check whether an alarm is generated indicating the disconnection of a HyperMetro replication link.
    3. Run the show port general command to check port status. If a Fibre Channel port is disconnected, locate the causes.

      Cause: All links are disconnected and the arbitration requests of the two storage arrays fail. As a result, member LUNs in HyperMetro pairs of the two storage arrays cannot be accessed by hosts and HyperMetro services are interrupted.

  3. If the preceding two problems do not exist, check whether LUNs are faulty or I/Os time out.
    1. Run the show lun general command to check whether a LUN is faulty. If the LUNs of two storage arrays are faulty, locate the causes.
    2. If no LUN is faulty, view the storage array logs to check whether an I/O timeout occurs. Download the logs and search for lun io timeout. If an I/O timeout occurs, the health status is Faulty and the running status is To Be Synchronized.

      Cause: I/Os time out and the storage arrays at two sites are set as secondary storage arrays. As a result, member LUNs in HyperMetro pairs of the two storage arrays cannot be accessed by hosts and HyperMetro services are interrupted.

  4. If a link of the quorum server is down or a link between storage arrays is down within two minutes after HyperMetro synchronization is complete, perform the following operations:
    1. Run the show hyper_metro_pair general command to check the completion time of HyperMetro pair synchronization.
    2. Check whether the links between the primary storage array and quorum server or the links between the primary and secondary storage arrays are down within two minutes and whether the primary storage array is faulty.

      Cause: The primary storage array is faulty within two minutes or the quorum server is disconnected from the primary and secondary storage arrays. The quorum server will reserve two minutes for the priority of the primary storage array. If the secondary storage array sends an arbitration request, arbitration will fail. As a result, member LUNs in HyperMetro pairs of the two storage arrays cannot be accessed by hosts and HyperMetro services are interrupted.

Procedure

  1. Restore the environment according to the specific fault causes.
  2. If the HyperMetro pair status is To Be Synchronized, restore HyperMetro services to normal status.

    1. In OceanStor DeviceManager, check the HyperMetro pair status.

      NOTE:

      To prevent data inconsistency caused by forcible startup of the two storage arrays, ensure that one storage array cannot be accessed by hosts before forcibly starting the other storage array. Otherwise, data may be inconsistent.

    2. Check whether the management links are normal. Check the management link status in OceanStor DeviceManager.

    3. If the management links are normal, check the HyperMetro pair IDs. Run the show hyper_metro_pair general and create hyper_metro_pair verificatian_session pair_id=?(pair_ID) commands in admin view.
    4. In OceanStor DeviceManager, choose Data Protection > HyperMetro, select a HyperMetro pair to forcibly start it, and wait the execution request.

      NOTICE:

      Only unilateral forcible startup is allowed.

    5. If a link fault exists, rectify the fault. Then run the show hyper_metro_pair general pair_id=? (HyperMetro pair ID) command to check the management link status.

      If the Link Status is Link Up, the management link status is normal.

    6. Synchronize data from the locate site to the remote site using OceanStor DeviceManager.
    7. Check whether HyperMetro pair status is normal.

  3. Check whether host services are running properly.

Suggestion and Summary

None

Translation
Download
Updated: 2018-09-03

Document ID: EDOC1000106183

Views: 26256

Downloads: 269

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