Search the VMware Knowledge Base (KB)
View by Article ID

Deploying a Metro Storage Cluster across two sites using HUAWEI OceanStor V3 HyperMetro and VMware vSphere (2150903)

  • 1 Ratings

Purpose

This article provides information about deploying a Metro Storage Cluster across two sites using HUAWEI HyperMetro and VMware vSphere.

Resolution

HUAWEI OceanStor V3 and HyperMetro:

The OceanStor V3 storage platform is newly developed by Huawei Technologies Co., Ltd (Huawei for short) include mid-range and high-end storage systems. It meets medium and large-sized enterprises' storage requirements for speed data access, high availability, high utilization, energy saving, and ease-of-use.

HyperMetro delivers the active-active service capabilities based on two storage arrays. Data on the active-active LUNs/File Systems at both ends is synchronized in real time, and both ends process read and write I/Os from application servers to provide the servers with non-differentiated parallel active-active access.

Huawe OceanStor V3 HyperMetro supports both SAN and NAS.

Minimum Requirements:

These are the minimum system requirements for a vMSC solution with HyperMetro:
  • Huawei OceanStor V300R003C00 storage system or newer when using UltraPath.
  • Huawei OceanStor V300R003C20 storage system or newer when using VMware NMP.
  • Huawei OceanStor V300R006C00 storage system or newer when using HyperMetro for File.
  • HyperMetro is a value-added feature that requires a software license for use on both OceanStor V3 arrays.
  • Huawei OceanStor V3 should be connected with ESXi via FC, iSCSI or NFS protocol.
  • ESXi 5.1 and later.
  • Huawei UltraPath (V100R008 or newer) or VMware NMP.

Solution Overview:



Figure 1: HyperMetro Configuration

In HyperMetro configurations:
  • LUN_1 and LUN_2 on OceanStor V3 arrays are Read/Write accessible to hosts.
  • Hosts could read/write to both devices in a HyperMetro Pair.
  • LUN_2 devices assume the same external device identity (geometry, device WWN) as their LUN_1.
  • This shared identity causes the LUN_1 and LUN_2 devices to appear to hosts(s) as a single virtual device across the two arrays.
  • FS_01 and FS_02 form a NAS HyperMetro pair.
  • FS_01 and FS_02 share all the same file system attributes, including logical port address, access control list and etc.
  • If FS_01 malfunctions, FS_02 automatically takes over services without data loss or service interruption, and vice versa.


Arbitration server:

HyperMetro supports arbitration by pair or by consistency group. In the event of link or other failures, HyperMetro provides two arbitration modes (Only one Arbitration server required for both Block and File in a HyperMetro Domain):
  • Static priority mode: This mode is mainly used in scenarios where no third-party arbitration servers are deployed. In this mode, you can set either end as the preferred site based on active-active pairs or consistency groups and the other end the non-preferred site.
    If the link between the storage arrays or the non-preferred site encounters a fault, LUNs at the preferred site are accessible, and those at the non-preferred site are inaccessible.

    If the preferred site encounters a fault, the non-preferred site is not accessible to hosts.

  • Arbitration server mode: In this mode, an independent physical or virtual machine is used as the arbitration device, which determines the type of failure, and uses the information to choose one side of the device pair to remain R/W accessible to the host. The Arbitration server mode is the default option.

Note: Either of the following can be used as an Arbitration Server:

  • The operation system that could be RedHat Linux 6.x, SUSE Linux 11.x, Asianux Server 4 SP4, Ubuntu 14.04 LTS or CentOS 6.5.
  • Arbitration server could be built on a physical or virtual machine.


Recommendations and Limitations:

It is required that the Host LUN ID from both storage systems should be the same for same LUN.

When using VMware NMP, it is recommended to upgrade to ESXi 6.0 U2 for ESXi 6.0 version. Please refer to this VMware KB article: Storage PDL responses may not trigger path failover in vSphere 6.0 (2144657).

It’s also recommended that the user mapping the LUN_2 device to ESXi host only after the Pair is success configured. User can use the rescan command to detect the new path, paths are detected automatically by UltraPath or VMware NMP. There might be some delay in automatic detection. Please refer to this VMware KB article for instructions on updating this tunable: Changing the polling time for datastore paths (1004378).

For more information on configuration guidelines, see the latest OceanStor V3 Product Guide.

For more in depth information of HyperMetro, see the technical notes with part number “OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R006 HyperMetro Feature Guide for Block”, “OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R006 HyperMetro Feature Guide for File ”,  “OceanStor 18500 V3&18800 V3 Mission Critical Storage System V300R006 HyperMetro Feature Guide for Block” or “OceanStor 18500 V3&18800 V3 Mission Critical Storage System V300R006 HyperMetro Feature Guide for File” on HUAWEI Support.

A certified configuration of OceanStor V3 is available, and is listed in the VMware Compatibility Guide.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.


Tested Scenarios:

This table outlines the tested and supported failure scenarios when using a Huawei OceanStor V3 Storage Cluster for VMware vSphere:

Scenario
Operation
Observed VMware behavior
Cross-data-center VM migration
Migrate a VM from site A to site B
No Impact
Physical server breakdown
Unplug the power supply for a host in site A
VMware High Availability failover virtual machines to other available hosts
Single-link failure of physical server
Unplug the physical link that connects a host in site A to an FC or IP switch No Impact
Storage failure in site A Unplug the power supply for the storage system in site A No Impact
All-link failure of storage in site A Unplug all service links that connect site A's storage array to an FC or IP switch No Impact
All-link failure of all hosts in site A Unplug all physical links that connect all hosts in site A to an FC or IP switch VMware High Availability failover virtual machines to available site B hosts
Failure of storage replication links Unplug replication links between sites No Impact
Failure of storage management network Unplug network cable from network port of host in site A No Impact
All-link failure between sites Disconnect the DWDM links between sites Virtual machines in site B hosts are automatically Powered off in site B hosts
and Powered on in available site A hosts.(ps: The perfect site is site A)
Failure of site A Power off all devices in site A VMware High Availability failover virtual machines to available site B hosts
Failure of site B Power off all devices in site B VMware High Availability failover virtual machines to available site A hosts

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: