OceanStor V3 HyperMetro Feature Guide For Block

OceanStor V3 Series
V300R006
HyperMetro Feature Guide for Block
Issue 05
Date 2018-01-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
Issue 05 (2018-01-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
OceanStor V3 Series
HyperMetro Feature Guide for Block About This Document
About This Document
Purpose
This document describes the working principle and application scenarios of the HyperMetro
feature. It also explains how to configure and manage the feature.
The following table lists the product models applicable to this document.
Product Series Product Model
OceanStor 2000 V3 series OceanStor 2600 V3
OceanStor 5000 V3 series OceanStor 5300 V3, 5500 V3, 5600 V3, and
5800 V3
OceanStor 6000 V3 series OceanStor 6800 V3
OceanStor 18000 V3 series OceanStor 18500 V3 and 18800 V3
Intended Audience
This document is intended for:
l Technical support engineers

l Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
WARNING
Issue 05 (2018-01-30) Huawei Proprietary and Confidential ii

OceanStor V3 Series
Symbol Description

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
NOTE Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes in earlier issues.
Issue 05 (2018-01-30)
This is the fifth official release.
Optimized descriptions about section Impact and Restrictions.
Added the following FAQ: How Can I Use OVA Templates to Quickly Deploy Virtual
Quorum Servers?
Issue 04 (2017-11-30)
This is the fourth official release.
Added the description about arbitration mechanism or configuration operations when
configuring two quorum servers.
Issue 03 (2017-08-30)
This is the third official release.
Synchronizes some software interface changes.
Issue 02 (2017-06-01)
This is the second official release.
Optimized descriptions about section Impact and Restrictions.
Synchronizes some software interface changes.
Issue 05 (2018-01-30) Huawei Proprietary and Confidential iii

OceanStor V3 Series
Issue 01 (2017-11-30)
This issue is the first official release.
Issue 05 (2018-01-30) Huawei Proprietary and Confidential iv

OceanStor V3 Series
HyperMetro Feature Guide for Block Contents
Contents
About This Document.....................................................................................................................ii

1 Feature Description....................................................................................................................... 1
1.1 Overview........................................................................................................................................................................ 1
1.2 License Requirements and Compatible Products........................................................................................................... 2
1.3 Working Principle........................................................................................................................................................... 3
1.3.1 Basic Concepts............................................................................................................................................................ 3
1.3.2 HyperMetro Solution Overview.................................................................................................................................. 5
1.3.3 Arbitration Mechanism................................................................................................................................................9
1.3.4 HyperMetro I/O Processing Mechanism................................................................................................................... 17
1.3.5 Functions of a HyperMetro Consistency Group........................................................................................................19
1.4 Impact and Restrictions................................................................................................................................................ 22
1.5 Application Scenarios...................................................................................................................................................24
2 Planning........................................................................................................................................ 27
3 Installation.................................................................................................................................... 28
3.1 Installation Process....................................................................................................................................................... 29
3.2 Preparations for Installation..........................................................................................................................................29
3.2.1 Preparing Tools, Meters, and Documentation........................................................................................................... 30
3.2.2 Quick checklist for the installation environment.......................................................................................................32
3.3 Device Installation........................................................................................................................................................ 38
3.4 Cable Connection......................................................................................................................................................... 41
3.5 Power-on.......................................................................................................................................................................46
3.6 Storage Array Initialization.......................................................................................................................................... 49
3.7 Multipathing Software Installation............................................................................................................................... 49
3.7.1 UltraPath Software Installation................................................................................................................................. 49
3.7.2 Third-party Multipathing Software Installation........................................................................................................ 49
3.8 Arbitration Software Installation.................................................................................................................................. 50
4 Configuration............................................................................................................................... 53
4.1 Configuration Process...................................................................................................................................................54
4.2 Configuration Preparations...........................................................................................................................................56
4.3 Configuring Switch.......................................................................................................................................................57
4.4 Configure Quorum Server Software.............................................................................................................................57
4.4.1 Configuring the Arbitration Software (SUSE).......................................................................................................... 57
Issue 05 (2018-01-30) Huawei Proprietary and Confidential v

OceanStor V3 Series
4.4.2 Configuring the Arbitration Software (Red Hat/Red Flag/NeoKylin/CentOS)........................................................ 62

4.4.3 Configuring the Arbitration Software (Ubuntu)........................................................................................................ 68
4.5 Configuring Basic Storage Services............................................................................................................................. 73
4.6 Creating SAN HyperMetro...........................................................................................................................................74
4.6.1 Checking the License File......................................................................................................................................... 75
4.6.2 Adding a Remote Device...........................................................................................................................................76
4.6.3 Creating a Quorum Server......................................................................................................................................... 79
4.6.4 Creating a HyperMetro Domain................................................................................................................................ 81
4.6.5 Creating a HyperMetro Pair...................................................................................................................................... 82
4.6.6 Creating a HyperMetro Consistency Group.............................................................................................................. 88
4.7 Configure a Multipathing Policy for Host.................................................................................................................... 91
4.7.1 Configuring a UltraPath Policy for Host................................................................................................................... 92
4.7.2 (Optional) Configuring a Third-party Multipathing Policy for Host........................................................................ 97
4.8 Verifying the Configuration........................................................................................................................................100
5 Management............................................................................................................................... 101
5.1 Managing a HyperMetro Pair..................................................................................................................................... 101
5.1.1 Viewing HyperMetro Pair Information................................................................................................................... 102
5.1.2 Modifying HyperMetro Pair Properties...................................................................................................................107
5.1.3 Synchronizing a HyperMetro Pair........................................................................................................................... 109
5.1.4 Suspending a HyperMetro Pair................................................................................................................................110
5.1.5 Switching the Preferred Site for a HyperMetro....................................................................................................... 110
5.1.6 Forcibly Enabling a HyperMetro Pair......................................................................................................................111
5.1.7 Deleting a HyperMetro Pair.....................................................................................................................................112
5.1.8 Expanding the Capacity of a HyperMetro LUN......................................................................................................113
5.2 Managing HyperMetro Domains................................................................................................................................ 114
5.2.1 Viewing HyperMetro Domain Information............................................................................................................. 115
5.2.2 Modifying a HyperMetro Domain...........................................................................................................................115
5.2.3 Deleting a HyperMetro Domain.............................................................................................................................. 116
5.3 Managing Quorum Servers.........................................................................................................................................117
5.3.1 Viewing Quorum Server Information...................................................................................................................... 117
5.3.2 Modifying Quorum Server Information.................................................................................................................. 118
5.3.3 Adding a Link.......................................................................................................................................................... 118
5.3.4 Removing a Link..................................................................................................................................................... 119
5.3.5 Removing a Quorum Server.................................................................................................................................... 119
5.3.6 Uninstalling the Arbitration Software..................................................................................................................... 120
5.4 Managing a HyperMetro Consistency Group.............................................................................................................121
5.4.1 Viewing the HyperMetro Consistency Group Information..................................................................................... 121
5.4.2 Modifying the Properties of a HyperMetro Consistency Group............................................................................. 124
5.4.3 Synchronizing a HyperMetro Consistency Group...................................................................................................127
5.4.4 Pausing a HyperMetro Consistency Group............................................................................................................. 128
5.4.5 Switching the Prior/Non-prior for a HyperMetro Consistency Group.................................................................... 128
5.4.6 Starting a HyperMetro Consistency Group Forcibly...............................................................................................129
Issue 05 (2018-01-30) Huawei Proprietary and Confidential vi

OceanStor V3 Series
5.4.7 Adding a HyperMetro Pair...................................................................................................................................... 130

5.4.8 Remove HyperMetro Pair........................................................................................................................................130
5.4.9 Deleting a HyperMetro Consistency Group............................................................................................................ 131
5.5 Importing Certificates.................................................................................................................................................132
6 FAQs.............................................................................................................................................135
6.1 What Can I Do If a Quorum Link Fails to Be Added Because the HyperMetro Arbitration Certificate Becomes
Invalid or the System Time Becomes Abnormal?............................................................................................................ 136
6.2 Active and Standby IP Ports Are Configured on the Quorum Server. After the Port in Use Is Down, the Quorum
Server Goes Offline. Why?...............................................................................................................................................137
6.3 How Do I Power Off Active-Active Storage Systems and Resume the HyperMetro Service?................................. 138
6.4 When Both the HyperMetro and Remote Backup Services Are Created, the Excessively Low Link Bandwidth
Between Storage Systems Causes the Remote Backup Service to Fail............................................................................139
6.5 How Can I Query HyperMetro LUN Identifiers?.......................................................................................................140
6.6 What Can I Do If the Remote Connection Fails to Be Created with the TOE Interface Module.............................. 140
6.7 In the SQL Server database scenario, how can I adjust parameters to reduce the I/O latency and achieve the optimal
performance?.................................................................................................................................................................... 141
6.8 How Can I Use OVA Templates to Quickly Deploy Virtual Quorum Servers?......................................................... 141
7 Troubleshooting........................................................................................................................ 146
7.1 A Quorum Link Fails to Be Added After the Quorum Server Is Replaced................................................................146
A How to Obtain Help.................................................................................................................148

A.1 Preparations for Contacting Huawei..........................................................................................................................148
A.1.1 Collecting Troubleshooting Information................................................................................................................ 148
A.1.2 Making Debugging Preparations............................................................................................................................ 149
A.2 How to Use the Document.........................................................................................................................................149
A.3 How to Obtain Help from Website............................................................................................................................ 149
A.4 Ways to Contact Huawei............................................................................................................................................149
B Glossary...................................................................................................................................... 150
C Acronyms and Abbreviations................................................................................................ 151
Issue 05 (2018-01-30) Huawei Proprietary and Confidential vii

OceanStor V3 Series
HyperMetro Feature Guide for Block 1 Feature Description
1 Feature Description
About This Chapter
HyperMetro provides you with disaster recovery functions and enables you to synchronize
and replicate data between storage arrays, monitor service operating status, and perform
failovers. You can switch over services and implement service load sharing while your storage
array is running.
1.1 Overview
This section describes the background, definition, and benefits of HyperMetro.
1.2 License Requirements and Compatible Products
This section describes the availability of HyperMetro in terms of the license requirement and
applicable version.
1.3 Working Principle
This section introduces the basic concepts, I/O processing mechanism, and arbitration
mechanism of HyperMetro and describes how to use HyperMetro for service switchover and
recovery.
1.4 Impact and Restrictions
This section describes the impact and restrictions of HyperMetro feature.
1.5 Application Scenarios
This section introduces the application scenarios of HyperMetro.
1.1 Overview
This section describes the background, definition, and benefits of HyperMetro.
Background
With the rapid development of the information technology (IT), storage systems are becoming
ever important for critical services in a variety of industries. Service interruptions in storage
systems may lead to severe economic loss, damaged brand images, or critical data loss,
especially in the fields of communications, finance, medical care, e-commerce, logistics, and
governments. Therefore, service continuity is critical to the construction of storage systems.
Traditionally, one production center and one disaster recovery center are constructed, and the
Issue 05 (2018-01-30) Huawei Proprietary and Confidential 1

OceanStor V3 Series
disaster recovery center is active only when the production center is down. This disaster
recovery system is facing the following challenges:
l If the production center encounters power supply failures, fires, floods, or earthquakes,
you must switch services from the production center to the disaster recovery center.
Services are interrupted for a long time and service continuity cannot be ensured.
l The disaster recovery center remains idle for most of the time, lowering resource
utilization.
Definition
HyperMetro enables storage systems in two different data centers to process services
simultaneously, establishing a mutual backup relationship. If the storage system in one data
center malfunctions, the storage system in the other data center automatically takes over
services without data loss or service interruption.
Benefits
Table 1-1 lists the benefits of HyperMetro.
Table 1-1 Benefits of HyperMetro
Benefit Description
Robust reliability If the storage system in one data center

malfunctions, the storage system in the other data
center automatically takes over services without
data loss or service interruption.
High compatibility By integrating SmartVirtualization, HyperMetro

enables full utilization of storage resources,
minimizes upgrade costs, and is fully compatible
with storage systems from most vendors,
including EMC, IBM, HDS, HP, and SUN.
1.2 License Requirements and Compatible Products

This section describes the availability of HyperMetro in terms of the license requirement and
applicable version.
License Requirement
HyperMetro is a value-added feature that requires a software license for use on both local and
remote storage systems.
Applicable products
Product Series Product Model Version
OceanStor 2000 V3 series OceanStor 2600 V3 V300R006

OceanStor V3 Series
Product Series Product Model Version
OceanStor 5000 V3 series OceanStor 5300 V3, 5500 V300R006

V3, 5600 V3, and 5800 V3
OceanStor 6000 V3 series OceanStor 6800 V3 V300R006
OceanStor 18000 V3 series OceanStor 18500 V3 and V300R006

18800 V3
Applicable Software Versions
Software Version
OceanStor When configuring HyperMetro services, use OceanStor UltraPath

UltraPath V100R008C50SPC500 or later.
OceanStor When configuring HyperMetro services, use OceanStor

QuorumServer QuorumServer V300R006 or later.
NOTE
Log in to http://support.huawei.com/enterprise/ and you can register for an account on the website. After
you log in with the applied user name and password. Choose Support > Enterprise Storage and click the
corresponding product model to access the product document page.
l Input Version Mapping in the search box and press Enter to obtain the product document.
l Enter the software name to obtain the software.
1.3 Working Principle

This section introduces the basic concepts, I/O processing mechanism, and arbitration
mechanism of HyperMetro and describes how to use HyperMetro for service switchover and
recovery.
1.3.1 Basic Concepts

This section describes basic concepts of HyperMetro, including local logical unit number
(LUN), remote LUN, dual-write, data change log (DCL), HyperMetro pair, HyperMetro
consistency group, synchronization, paused, force start, priority switchover and so on.
Local LUN and Remote LUN

Local LUNs are LUNs that belong to the local storage system. Remote LUNs are LUNs that
belong to the remote storage system.
Dual-Write
Dual-write enables the synchronization of application host I/O requests with both local and
remote LUNs.

OceanStor V3 Series
DCL
DCLs record changes in the data of storage systems.
HyperMetro Domain
A HyperMetro domain consists of the local and remote storage systems, and the quorum
server. Application servers can access data across data centers using a HyperMetro domain.
HyperMetro Pair
A HyperMetro pair indicates an active-active relationship between a local and remote LUN.
With HyperMetro configured, a local and remote LUN form a HyperMetro pair. You must
create HyperMetro pairs in a HyperMetro domain. By viewing the state of a HyperMetro pair,
you can determine whether you need to perform operation such as synchronization,
suspension, and priority switchover. After performing an operation, you can view the state of
the HyperMetro pair to determine whether the operation succeeded. Configure a HyperMetro
domain before configuring HyperMetro pairs.
HyperMetro Consistency Group

A HyperMetro consistency group is a collection of HyperMetro pairs that have a service
relationship with each other. For example, the local storage system has three local LUNs that
respectively store service data, logs, and change tracking information of a database. If data on
any of the three LUNs becomes invalid, all data on the three LUNs becomes unusable. Upon
configuration, create a consistency group and add the three HyperMetro pairs to the
consistency group.
Synchronization
Synchronization refers to the synchronization of differential data between a local LUN and a
remote LUN. Data synchronization takes place between two LUNs in a HyperMetro pair. You
can synchronize data in multiple HyperMetro pairs in a consistency group.
Pause
Pause is a state indicating the suspension of a HyperMetro pair.
Force Start
To ensure data consistency when the local and remote storage systems malfunction
simultaneously, HyperMetro stops hosts from accessing both. To quickly restore services, you
can forcibly start the local or remote storage system.
Priority Switchover
Priority switchover indicates that the preferred site takes precedence during arbitration. If the
HyperMetro replication network is down, the storage system that wins arbitration continues
providing services to hosts. After the creation of a HyperMetro pair, the local data center is by
default the preferred site and the remote data center is the non-preferred site.

OceanStor V3 Series
Locking Mechanism
To prevent different host I/Os from being written to the same location in the storage system at
the same time, the storage system uses the locking mechanism to prevent access conflicts. The
host I/O can only be written to the storage system that obtains the locking mechanism.
1.3.2 HyperMetro Solution Overview

This section describes the HyperMetro solution network and provides a logical HyperMetro
network topology to show the mapping relationship and data flows between host applications
and storage arrays.
HyperMetro enables active-active block storage services. LUN data is synchronized between
two data centers in real time and can be accessed by hosts.
If the storage array in one data center malfunctions, host services are switched to the storage
array in the other data center. If the link between two storage arrays in two data centers is
down, only one storage array can be accessed by hosts. The quorum server determines which
storage array continues providing services.
Figure 1-1 shows the HyperMetro solution network topology.
Figure 1-1 HyperMetro solution network topology
Data center A Data center B
Host cluster
Switch Switch
FC/IP
Switch Switch
Storage array A Storage array B
Switch Switch Switch Switch
LAN/WAN
Network of hosts and

storage arrays
Same-city network
Quorum server between data centers
HyperMetro
replication network
Quorum site Quorum network

OceanStor V3 Series
Network Overview
To ensure reliability of storage arrays, establish redundant links among the network between
hosts and storage arrays, HyperMetro replication network, same-city network between data
centers, and quorum network.
Table 1-2 Network Overview

Network Description
Network of hosts and Network Supports 8 Gbit/s Fibre Channel, 16 Gbit/s

storage systems type Fibre Channel, 10GE, and GE networks.
All hosts in the two data Networking l A fully interconnected network in which
centers can form a mode each host is physically and logically
cluster and host connected to the storage arrays in both data
networks can centers.
interconnect across data
centers. l A host must connect to both storage arrays
using the same type of network.
l Dual-switch networking must be used.
l The HyperMetro replication network,
storage-to-host network, and quorum
network need to be physically isolated and
common ports are not recommended.

OceanStor V3 Series
Network Description
HyperMetro replication Network l Supports 10GE, 8 Gbit/s Fibre Channel, and

network type 16 Gbit/s Fibre Channel networks.
This is the heartbeat NOTE
network between the When using the 10GE network, you are advised
to use the L2 network.
storage systems in the
two data centers. It l Network quality and bandwidth
enables the storage requirements for deploying the network:
systems to provide – Bandwidth: ≥ peak service bandwidth
services for hosts (total bandwidth of the two ends)
concurrently and
– Latency: The maximum supported RTT
ensures data
is 10 ms (distance < 300 km)
synchronization
between them. NOTE
In practice, the latency is determined by the
NOTE requirements of the application layer. The
The storage system sets active/active solution must meet the
link priorities for different minimum latency requirement. The round-trip
types of information for time (RTT) of the Oracle RAC, SQL Server,
transferring data. The link and DB2 applications is less than 1 ms (with
priority of heartbeat a distance of less than 100 km). The RTT of
information is higher than the VMware vSphere applications is less than
that of data 10 ms (with a distance of less than 300 km).
synchronization
information. – No jitter and packet loss
– BER: ≤ 10-12
Networking Each controller on every storage array in both

mode data centers has at least two redundant links. It
is recommended that you use four redundant
links.
Same-city network Network The network uses bare fibers.

between data centers type
The storage systems in
data centers A and B
provide the same
services for hosts. There
is a mutual backup
relationship between the
two storage systems. If
the storage system in
one data center
malfunctions, the
storage system in the
other data center
automatically takes over
services without data

OceanStor V3 Series
Network Description
loss or service Networking l For Fibre Channel networks:
interruption. mode – The two data centers can be directly
connected using bare fibers if their
distance is within 25 km. Ensure that the
storage and application layers each have
at least two pairs (four wires) of bare
fibers for heartbeat interconnection in the
cluster.
– If the data centers are greater than or
equal to 25 km apart, use dense
wavelength division multiplexing
(DWDM) devices to build the
interconnection network between DCs.
l For IP networks:
– The two data centers can be directly
connected using bare fibers if their
distance is within 80 km. If core switches
are deployed, ensure that at least two
pairs (four wires) of bare fibers are
connected to the core switches for
HyperMetro mirroring at the storage
layer and heartbeat interconnection at the
application layer.
– If the data centers are greater than or
equal to 80 km apart, use DWDM
devices to interconnect them.
Quorum network Network l Quorum links support GE and 10GE

If communication type networks, but not a Fibre Channel network.
between the storage l Quorum links support IPv4 and IPv6
systems in data centers addresses.
A and B is interrupted l For versions earlier than V300R006C10, the
or a storage system arbitration link port cannot use a storage
malfunctions, the device's management or maintenance
quorum server network port. For V300R006C10 and later
determines which versions, the arbitration link port can use a
storage system is storage device's management network port,
accessible. but cannot use its maintenance network port.
l Network quality and bandwidth
requirements for deploying the network:
– Latency: RTT ≤ 50 ms
– Bandwidth: ≥ 10 Mbit/s

OceanStor V3 Series
Network Description
NOTE Networking l Quorum servers are supported but quorum
A quorum server is mode disks are not.
deployed on the quorum
network. If storage arrays l You are advised to deploy the quorum server
in the two data centers at a third-place site. If there is no third-place
encounter a device fault site, you are advised to deploy the quorum
or a link between the
server at the preferred site. In this case, the
storage arrays is down,
the quorum server quorum server and related devices should
determines the access have uninterruptible power supply (UPS)
status of data center A protection.
and data center B
l A dual-switch network is recommended. A
according to the
arbitration result. GE/10GE port on each controller of a
storage array is connected to the third-place
quorum server and the service network ports
on the quorum server are connected to two
storage arrays, ensuring that the quorum
server is connected to all controllers of each
storage array.
l If each controller has two quorum ports,
connect the first quorum port on each
controller to switch 1 and configure IP
network segment 1. In addition, connect the
second quorum port on each controller to
switch 2 and configure IP network segment
2.
l The quorum server can be a physical or a
virtual server. If a virtual server is used, you
are advised to deploy VMware vSphere/
FusionSphere FT or HA to achieve high
availability.
l Huawei Enterprise Cloud (HEC) can be used
as a quorum server.
When the HEC is used as the quorum server,
apply for a VM (including the CPU,
memory, disk, and OS). The VM
specifications are the same as those of the
quorum server. Apply for 2 Mbit/s exclusive
bandwidth and one elastic IP address for
each disk array.
1.3.3 Arbitration Mechanism

If the link between the two data centers breaks down, they can no longer be synchronized and
only one will continue providing services. HyperMetro supports two arbitration modes to
determine which data center continues providing services and ensure data consistency:
l Static priority mode is used when there is no quorum server available.

l Quorum server mode is used when quorum servers have been deployed.

OceanStor V3 Series
NOTE
The quorum server mode is recommended. After a quorum server is deployed, the non-preferred site of
HyperMetro will automatically take over services once the preferred site becomes faulty, without
causing HyperMetro service interruption.
Static Priority Mode

The static priority mode applies to scenarios where no third-place quorum server is deployed.
In a HyperMetro pair, you can set one data center as the preferred site and the other as the
non-preferred site.
l If the link between the two storage arrays in the two data centers is disconnected or the
storage array at the non-preferred site breaks down, the storage array at the preferred site
continues providing services for hosts and the storage array at the non-preferred site
stops.
l If the storage array at the preferred site breaks down, the storage array at the non-
preferred site cannot automatically take over HyperMetro services from the storage array
at the preferred site. As a result, HyperMetro services stop. In this case, you must
forcibly start the storage array at the non-preferred site to provide services for hosts.
NOTE
When you use OceanStor DeviceManager or CLI to power off a storage device, it will notify its peer
storage device of taking over its services. This event is not a device fault.
In the following example, data center A is used as a preferred site. Table 1-3 describes the
arbitration mechanism in static priority mode.
NOTE
You can set the Recovery Policy for HyperMetro pair failures by Modifying HyperMetro Pair Properties.
l Automatic: The system automatically synchronizes data for data recovery.
l Manual: You must manually synchronize data for data recovery.
Table 1-3 Arbitration mechanism in static priority mode

N Fault Example Fault Type HyperM Arbitration Result
o. etro Pair
Running
Status
1 HyperMetro Pair The link To be A continues

LUN LUN between two synchroni providing services
Data center A Data center B storage arrays zed while B stops.
breaks down.
2 HyperMetro Pair The storage To be A continues

LUN LUN array in data synchroni providing services
Data center A Data center B center B (non- zed while B stops.
preferred site)
malfunctions.

OceanStor V3 Series

o. etro Pair
Running
Status
3 HyperMetro Pair The storage To be Both A and B stop.

LUN LUN array in data synchroni You must forcibly
Data center A Data center B center A zed start B to resume
(preferred providing services
site) for hosts.
malfunctions.
Black cable: HyperMetro replication network
Quorum Server Mode

In quorum server mode, the heartbeat network determines whether the storage arrays are
working properly. If a malfunction occurs, each data center sends an arbitration request to the
quorum server, and only the winner continues providing services.
The quorum site supports two quorum servers for V300R006C10 and later versions. The two
quorum servers work in active/standby mode. Once the active quorum server is faulty, the
system automatically switches to the standby quorum server to execute the arbitration
function.
In a HyperMetro pair, you can set one data center as the preferred site, which takes
precedence in arbitration, and the other as the non-preferred site. In the following example,
data center A is used as a preferred site. Table 1-4 and Table 1-5 describe the arbitration
mechanisms when one and two quorum servers are deployed, respectively.
NOTE
You can set the Recovery Policy for HyperMetro pair failures by Modifying HyperMetro Pair Properties.
l Automatic: The system automatically synchronizes data for data recovery.
l Manual: You must manually synchronize data for data recovery.
Table 1-4 Arbitration mechanism in single-quorum-server mode

o. etro Pair
Running
Status
1 Quorum server The quorum Normal Both A and B

server breaks continue providing
HyperMetro Pair
down. services.
LUN LUN
NOTE
HyperMetro
automatically
switches to static
priority arbitration.

OceanStor V3 Series

o. etro Pair
Running
Status
2 Quorum server The link Normal Both A and B

between one continue providing
HyperMetro Pair
storage array services.
LUN LUN
and the
quorum server
breaks down.
3 Quorum server One storage To be B continues

array synchroni providing services
HyperMetro Pair
malfunctions. zed while A stops.
LUN LUN
4 Quorum server The link To be Result 1: A

between two synchroni continues providing
HyperMetro Pair
storage arrays zed services while B
LUN LUN
breaks down. stops.
Data center A Data center B Result 2: B
continues providing
services while A
stops.
NOTE
l A has arbitration
priority, so the
normal result is
Result 1.
l (For
V300R006C10
and later
versions) If the
link between data
center A and the
application server
has become faulty
before the link
between the two
storage arrays
breaks down, data
center B will win
the arbitration.
5 Quorum server One storage To be Both A and B stop.

array and the synchroni NOTE
HyperMetro Pair
quorum server zed You must forcibly
LUN LUN
both start B to resume
malfunction. providing services for
Data center A Data center B hosts.

OceanStor V3 Series

o. etro Pair
Running
Status
6 Quorum server The link To be B continues

between the synchroni providing services
HyperMetro Pair
two storage zed while A stops.
LUN LUN
arrays and the
link between
one storage
array and the
quorum server
both break
down.
7 Quorum server One storage To be Both A and B stop.

array synchroni NOTE
HyperMetro Pair
malfunctions zed You must forcibly
LUN LUN
and the link start B to resume
between the providing services for
Data center A Data center B hosts.
other storage
array and the
quorum server
is down.
8 Quorum server The quorum To be Result 1: If the link

server synchroni is interrupted more
HyperMetro Pair
malfunctions zed than 60 seconds after
LUN LUN
and then the the quorum server
link between fails, A continues
two storage providing services
arrays is while B stops.
down. Result 2: If the link
is interrupted within
60 seconds of the
quorum server
failure, both A and B
stop. You must
forcibly start either
A or B to resume
providing services
for hosts.
9 Quorum server The quorum Normal Both A and B

server continue providing
HyperMetro Pair
malfunctions services.
LUN LUN
and the link NOTE
between the HyperMetro
quorum server automatically
and one switches to static
priority arbitration.
storage array
is down.

OceanStor V3 Series

o. etro Pair
Running
Status

Green cable: quorum network
Table 1-5 Arbitration mechanism in dual-quorum-server mode

o. etro Pair
Running
Status
1 Quorum server
(active)
Quorum server
(standby)
The active Normal The standby quorum
quorum server server takes over the
breaks down. arbitration services
HyperMetro
Pair
from the active
LUN LUN quorum server.
Data center A Data center B Both A and B
continue providing
services.
2 Quorum server
(active)
Quorum server
(standby)
The link Normal The active quorum
between one server runs properly.
storage array Both A and B
HyperMetro
Pair and the active continue providing
LUN LUN quorum server services.
Data center A Data cente B breaks down.
3 Quorum server
(active)
Quorum server
(standby)
One storage To be The active quorum
array synchroni server runs properly.
malfunctions. zed B continues
HyperMetro
Pair
providing services
LUN LUN while A stops.
Data center A Data cente B

OceanStor V3 Series

o. etro Pair
Running
Status
4 Quorum server
(active)
Quorum server
(standby)
The link To be The active quorum
between two synchroni server runs properly.
storage arrays zed Result 1: A
HyperMetro
Pair breaks down. continues providing
LUN LUN services while B
Data center A Data cente B
stops.
Result 2: B
continues providing
services while A
stops.
NOTE
A has arbitration
priority, so the
normal result is
Result 1.
5 Quorum server
(active)
Quorum server
(standby)
The active To be The standby quorum
quorum server synchroni server takes over the
fails and then zed arbitration services
HyperMetro
Pair the storage from the active
LUN LUN array at the quorum server.
Data center A Data cente B preferred site B continues
fails after providing services
more than 60 while A stops.
seconds.
6 Quorum server
(active)
Quorum server
(standby)
The link To be The active quorum
between the synchroni server runs properly.
two storage zed B continues
HyperMetro
Pair arrays and the providing services
LUN LUN link between while A stops.
Data center A Data cente B one storage
array and the
active quorum
server both
break down.

OceanStor V3 Series

o. etro Pair
Running
Status
7 Quorum server
(active)
Quorum server
(standby)
The link To be The standby quorum
between the synchroni server takes over the
active quorum zed arbitration services
HyperMetro
Pair server and from the active
LUN LUN non-preferred quorum server.
Data center A Data cente B site breaks B continues
down and then providing services
the storage while A stops.
array at the
preferred site
fails after
more than 60
seconds.
8 Quorum server
(active)
Quorum server
(standby)
The active To be The standby quorum
quorum server synchroni server takes over the
malfunctions zed arbitration services
HyperMetro
Pair and then the from the active
LUN LUN link between quorum server.
Data center A Data cente B two storage Result 1: If the link
arrays is is interrupted more
down. than 60 seconds
after the active
quorum server fails,
A continues
providing services
while B stops.
If the link is
interrupted within 60
seconds of the
quorum server
failure, both A and
B may win the
arbitration and
continue providing
services.
NOTE
A has arbitration
priority, so generally
A continues
providing services
while B stops.

OceanStor V3 Series

o. etro Pair
Running
Status
9 Quorum server
(active)
Quorum server
(standby)
The active Normal The standby quorum
quorum server server takes over the
malfunctions arbitration services
HyperMetro
Pair and the link from the active
LUN LUN between the quorum server.
Data center A Data cente B active quorum Both A and B
server and one continue providing
storage array services.
is down.

Green solid cable: quorum network between the active quorum server and data centers
Green dotted cable: quorum network between the standby quorum server and data centers
1.3.4 HyperMetro I/O Processing Mechanism

HyperMetro uses the dual-write and DCL technologies to synchronize data changes between
two data centers, ensuring data consistency. In addition, HyperMetro enables the storage
arrays in the two data centers to concurrently provide services for hosts.
Basic Concepts
You are advised to read about the key concepts of HyperMetro before reading about the I/O
processing mechanism. For details, see 1.3.1 Basic Concepts.
Write I/O Process

l Dual-write and DCL technologies have two ways of synchronizing data while services
are running. Dual-write enables the delivery of I/O requests from application servers to
both local and remote caches, ensuring data consistency between caches. If the storage
system in one data center malfunctions, the DCL records data changes in a data center.
After the storage system recovers, the data changes are synchronized to the storage
system, ensuring data consistency across data centers.
l Two storage systems with HyperMetro installed can process I/O requests concurrently.
The locking mechanism prevents access conflicts that occur when different hosts access
the same storage system at the same time. Data can be written to a storage system only
after the locking mechanism grants permission to the storage system. If the locking
mechanism does not grant priority, the storage system must wait until the previous I/O is
complete. It must then obtain write permission after the locking mechanism releases the
previous storage system.
Figure 1-2 shows the write I/O process of an application host delivering an I/O request and
causing data changes.
NOTE
In the following figure, the write I/O accesses the local storage system, and the local storage system
writes data to the remote storage system for dual-write purposes.

OceanStor V3 Series
Figure 1-2 Write I/O process
Host
Storage
1 5
2 HyperMetro management module

DCL LOG 4
6
6
4
3 4
3
Local Remote
cache cache
DWDM
Same-city network
Local Remote
between data centers
LUN LUN
Local storage array Remote storage array
1. An application host delivers a write I/O to the HyperMetro management module.

2. A log is recorded.
3. HyperMetro writes the write I/O to both the local and remote caches concurrently.
4. The local and remote caches return the write I/O result to HyperMetro.
5. A storage system returns the write I/O result to the application host after receiving
feedback from the local and remote caches.
6. The storage system determines whether dual-write is successful.
– If the write I/O request is processed successfully, the log is deleted.
– If the write I/O fails to be written to the local or remote cache, the log is converted
into a DCL. The DCL records the differential data between the local and remote
LUNs.
NOTE
If the write I/O fails to be written to the local or remote cache, HyperMetro services are
suspended and the storage system in each data center sends an arbitration request to the
quorum server. The storage system that wins the arbitration continues providing services and
the one that fails stops. In the background, the storage system uses the DCL to synchronize
data. Once the data on the local LUN is identical to the data on the remote LUN,
HyperMetro services are restored.
The DCL is stored on all the disks in the disk domain and four-disk RAID 1 is used for data
protection while storage system logs are stored on coffer disks.
Read I/O Process

Data on the LUNs of both storage systems is synchronized in real time and both are accessible
to hosts. If the storage system in one data center malfunctions, the storage system in the other
data center continues providing host services alone.

OceanStor V3 Series
NOTE
l UltraPath is recommended for HyperMetro. Huawei UltraPath to meet HyperMetro requirements.

After the optimization, UltraPath can identify host locations so that hosts can access the nearest
storage array, reducing cross-site accesses and latency while improving access efficiency and storage
performance.
l If the customer needs to use non-Huawei multipathing software on the application server, the
function of Uses third-party multipath software for initiators must be enabled on Huawei storage.
After this function is enabled, third-party multipathing software can identify and aggregate LUNs for
servers to access to ensure normal operation of server services.
Figure 1-3 shows the read I/O process.
Figure 1-3 Read I/O process
Application
host
1 5
HyperMetro management
module
2 4
4
3
Local Remote
LUN LUN
1. An application host applies for read permission from the HyperMetro management
module.
NOTE
If the link between the storage arrays in the two data centers is down, the quorum server
determines which storage array continues providing services for hosts.
2. The HyperMetro management module enables the local storage system to respond to the
read I/O request made by the host.
3. If the local storage system is operating properly, it returns data to the HyperMetro
management module. If not, the HyperMetro management module enables the host to
read data from the remote storage system.
4. If the local storage array is working improperly, the HyperMetro management module
enables the host to read data from the remote storage array. The remote storage array
returns data to the HyperMetro management module.
5. The read I/O request made by the host is processed successfully.
1.3.5 Functions of a HyperMetro Consistency Group

A consistency group is a collection of multiple HyperMetro pairs. It ensures that the read/
write control policies of the multiple LUNs on a storage array are synchronized.
In medium- and large-sized database applications, data, logs, and modification information
are stored on different LUNs. If data on one of the LUNs becomes unavailable, data on the
other LUNs also becomes invalid. A consistency group is a collection of multiple HyperMetro

OceanStor V3 Series
pairs. It ensures that the read/write control policies of the multiple LUNs on a storage array
are synchronized. The operation and control policies of all members that have been added to a
consistency group must be consistent with those of the consistency group.
HyperMetro applications can use a consistency group to manage multiple HyperMetro pairs
in a unified manner.
The following compares synchronization in a consistency group with synchronization without
using a consistency group to prove that a consistency group is effective in preventing data
loss.
Without a HyperMetro Consistency Group

If LUNs are not added to a HyperMetro consistency group, the possibility of data loss is quite
high for these LUNs, as shown in Figure 1-4.

OceanStor V3 Series
Figure 1-4 Without a HyperMetro consistency group

Before data changes 1. No consistency group is

created.
Local HyperMetro pair 01

Remote · Data, logs, and
LUN01 LUN01 modification information of
a database application are
stored on local LUN01,
HyperMetro pair 02 LUN02, and LUN03
Local Remote respectively.
LUN02 LUN02 · No consistency group is
created on the local
HyperMetro pair 03 storage array.
Local Remote
LUN03 LUN03
Phases in a process of data becoming invalid
After data changes 2. Synchronization fails, resulting

in data inconsistency.
HyperMetro pair 01
Local Remote
LUN01 LUN01 Data synchronization fails
between two LUNs in
HyperMetro pair 02 due to a
HyperMetro pair 02
Local Remote fault of the HyperMetro pair.
LUN02 Data synchronization
LUN02
succeeds between LUNs in
HyperMetro pairs 01 and 03.
Remote
LUN03
LUN03
Data recovery
3. Data becomes invalid.
Remote After the local storage array
LUN01 LUN01 malfunctions due to a disaster,
data on the remote storage
array is used for data
Local HyperMetro pair 02 recovery. Data in the database
Remote
LUN02 of the local storage array is still
LUN02
invalid because data on the
three local LUNs are not
Local HyperMetro pair 03 stored at the same point in
Remote time.
LUN03
LUN03
With a HyperMetro Consistency Group

If LUNs are added to a HyperMetro consistency group, no data is lost, as shown in Figure
1-5.

OceanStor V3 Series
Figure 1-5 With a HyperMetro consistency group

1. A consistency group is
Before data changes created.
· Data, logs, and
HyperMetro pair 01 modification information
Local Remote of a database application
LUN01 LUN01 are stored on local
LUN01, LUN02, and
LUN03 respectively.
Phases in a process of ensuring data validity by a consistency group
HyperMetro pair 02 · Consistency group 01 is

Local Remote
LUN02 created on the local
LUN02
storage array and three
HyperMetro pairs are
HyperMetro pair 03 added to the consistency
Local Remote group.
LUN03 LUN03
Consistency group 01
After data changes 2. The consistency group stops

the replication task.
HyperMetro pair 01
Local Remote
LUN01 LUN01 · HyperMetro pair 02
encounters a fault during
HyperMetro pair 02 data synchronization.
Local Remote · The consistency group
LUN02 LUN02 stops HyperMetro pairs
01 and 03 immediately.
HyperMetro pair 03 · After the fault is rectified,
Local Remote data is replicated.
LUN03 LUN03
Data recovery
3. The consistency group
HyperMetro pair 01 ensures data validity.
Local Remote
LUN01 LUN01 After a disaster occurs, the
data on the remote storage
array is used for data
HyperMetro pair 02 recovery. The data in the
Local Remote database is valid.
LUN02 LUN02

Remote
LUN03 LUN03
1.4 Impact and Restrictions

This section describes the impact and restrictions of HyperMetro feature.
Network Restrictions
For details about network restrictions, see HyperMetro Solution Overview.

OceanStor V3 Series
Device Restrictions
Table 1-6 Device configuration requirements
Device Configuration Requirement
Quorum server l The arbitration software can be deployed on either a physical

machine or a virtual machine (VM). The configuration
requirements are as follows:
– CPU: X86-64 architecture; 2-core 1.6 GHz CPU (minimum
configuration)
– Memory: 4 GB DDR memory (minimum configuration)
– Operating system: Asianux Server 4 SP4 for x86_64, CentOS
6.5 for x86_64, NeoKylin 6.5 for x86_64, Red Hat Enterprise
Linux 6 for x86_64, Red Hat Enterprise Linux 6.1 for
x86_64, Red Hat Enterprise Linux 6.2 for x86_64, Red Hat
Enterprise Linux 6.3 for x86_64, Red Hat Enterprise Linux
6.5 for x86_64, Red Hat Enterprise Linux 6.6 for x86_64,
Red Hat Enterprise Linux 6.7 for x86_64, Red Hat Enterprise
Linux 7.2 for x86_64, Red Hat Enterprise Linux 7.2 for
x86_64, SUSE Linux Enterprise Server 11 SP1 for x86_64,
SUSE Linux Enterprise Server 11 SP2 for x86_64, SUSE
Linux Enterprise Server 11 SP3 for x86_64, SUSE Linux
Enterprise Server 11 SP4 for x86_64, SUSE Linux Enterprise
Server 12 SP2 for x86_64, Ubuntu 14.04 LTS for x86_64,
CentOS 6.8 for x86_64
NOTE
V300R006C00SPC100 and later versions support CentOS 6.8.
The arbitration software does not support operating systems that use
CPU architectures such as MIPS, ARM, and PPC.
– Storage capacity for installing the arbitration software: ≥ 10
GB
– Number of network ports: ≥ 3
NOTE
One network port is used for operating system management and the
other two are used as arbitration ports that connect to the storage
arrays.
l In the event of virtual machine deployment, virtual machines can
only use servers' local disks or LUNs that are provided by other
storage systems instead of the active-active storage systems as
system disks and data disks.
l Arbitration granularity can be a HyperMetro pair or a consistency
group.
Storage array l The versions of the local and remote storage systems in a
HyperMetro relationship are the same. In addition, the hardware
configurations of the two storage systems are the same.
l The HyperMetro license must be available for the storage arrays
in two data centers.

OceanStor V3 Series
Compatibility
When using HyperMetro, ensure that the host operating system, multipathing software, and
arbitration software are compatible with each other. You can query the compatibility using the
OceanStor Interoperability Navigator.
1.5 Application Scenarios

This section introduces the application scenarios of HyperMetro.
Industry Application
HyperMetro is widely used in the following industries:
l Health Care
As hospital services develop, the number of beds increases, and new clinic buildings are
constructed, hospitals have higher requirements for service continuity. Once critical
services such as out-patient, in-patient, and electronic medical record (EMR) services are
interrupted, medical treatment will be delayed and hospitals will suffer from great
economic loss and inestimable damage to their reputation. Hospitals require zero
recovery point objective (RPO) and the recovery time objective (RTO) must be within
five minutes. In addition, the out-patient building and in-patient network information
center in a hospital and two hospitals in the same city are physically close to each other.
HyperMetro can meet hospitals' requirements.
l Finance
In the finance industry, banking services, 24-hour ATM services, POS services, and e-
bank services are developing quickly. These services require that banking systems
process services around the clock. Banks need a solution to meet their service
construction requirements (RPO = 0, RTO ≈ 0) and ensure business continuity. Service
interruptions damage banks' reputation, posing huge pressure on technical departments.
HyperMetro meets requirements of hospitals' class-A+ and class-A services (Class-A+
services include core system services, payment system services, counter services, and
encryption platform services and class-A services include ESB services, ECIF services,
trade system services, e-channel services, centralized operation services, and e-bank
services).
l Social Insurance
The social insurance industry also has high requirements for service continuity. Monthly
accounting and year-end settlement require 24/7 services. If social insurance systems
malfunction, livelihood issues will appear. For example, people cannot obtain their
pensions on time and health insurance problems cannot be resolved. HyperMetro is
applicable to social insurance application scenarios including the basic information
management, social insurance card system, labor relationship management, public
services, public resource management, employment, and social insurance management.
Application of HyperMetro Paired with Other Features

For the HyperMetro feature, due to distance restrictions, two data centers must be constructed
in the same city. Because the Disaster Recovery Data Center Solution (Active-Active Mode)
cannot be used to cope with regional disasters, a remote DR center is constructed to expand
the existing solution to the Disaster Recovery Data Center Solution (Geo-Redundant Mode).

OceanStor V3 Series
Figure 1-6 shows the network of the 3DC with HyperMetro and asynchronous remote
replication.
Figure 1-6 Network of the 3DC with HyperMetro and asynchronous remote replication
Site A Site B
LUN
LUN
HyperMetro
Storage system Storage system
Production center Same-city

production center
Asynchronous
remote
replication
Site C
LUN
Storage system
Optical fiber
Network cable
Remote DR center
NOTE
A remote replication relationship can be established between the remote DR center and either production
center.
Besides, HyperMetro + synchronous remote replication network can be achieved. However,

due to distance restrictions, synchronous remote replication is used to implement short-
distance DR. Figure 1-7 shows the network.

OceanStor V3 Series
Figure 1-7 Network of the 3DC with HyperMetro and synchronous remote replication
Site A Site B
LUN
LUN
HyperMetro
Storage system Storage system
Production center Same-city

production center
Synchronous
remote replication
Site C
LUN
Storage system
Optical fiber
Same-city DR
center

OceanStor V3 Series
HyperMetro Feature Guide for Block 2 Planning
2 Planning
This chapter describes the networks and data you must plan before HyperMetro configuration.
This document describes how HyperMetro works and related operations on storage devices.
For details about data planning and service configuration process, see BC&DR Solution
Product Documentation V200R001 (Active-Active Data Center).

OceanStor V3 Series
HyperMetro Feature Guide for Block 3 Installation
3 Installation
About This Chapter
This chapter describes how to install the HyperMetro feature and devices related to the
feature, connect cables, and power on devices, helping you avoid unnecessary rework during
and after installation.
3.1 Installation Process

Before the installing a storage array, view the installation process. The installation process
guides you through a smooth and complete installation.
3.2 Preparations for Installation
Preparations before installing devices include preparing tools and meters, checking the
installation environment, and unpacking and checking goods. Sufficient preparation ensures a
safe and proper installation.
3.3 Device Installation
Install devices as instructed in the following description to avoid unnecessary rework at your
site.
3.4 Cable Connection
HyperMetro cable connection involves: network between hosts and storage arrays,
HyperMetro replication network, same-city data center network, and quorum network.
3.5 Power-on
After installing all devices, power on them and check their operating status. Ensure that all
devices and their hardware are properly installed. Otherwise, do not power on them.
3.6 Storage Array Initialization
After powering on a storage array, you must initialize it.
3.7 Multipathing Software Installation
This section describes installation environment requirements, pre-installation preparations,
and the installation procedure of multipathing software.
3.8 Arbitration Software Installation
This section describes how to install the arbitration software. Quorum server software needs
to be installed only when a quorum server is used for HyperMetro.

OceanStor V3 Series
3.1 Installation Process

Before the installing a storage array, view the installation process. The installation process
guides you through a smooth and complete installation.
Figure 3-1 shows the installation process.
Figure 3-1 Installation process
Start
Preparations for Installation
Device Installation
Cable Connection
Power-on
Storage Array Initialization
Multipathing Software
Installation
Arbitration Software
Installation
End
3.2 Preparations for Installation

Preparations before installing devices include preparing tools and meters, checking the
installation environment, and unpacking and checking goods. Sufficient preparation ensures a
safe and proper installation.

OceanStor V3 Series
3.2.1 Preparing Tools, Meters, and Documentation

Before installing devices, ensure that necessary installation support materials including tools,
meters, and documentation are available. A good preparation helps ensure a correct and
smooth installation.
Table 3-1 lists the tools required in the installation process.
Table 3-1 Tools required in the installation process

Name Pictogram Function
Marker Marks a location and

scale.
Phillips screwdriver Fastens small screws or

(M3 to M6) bolts, and has a cross-
shaped head.
Flat-head screwdriver Fastens small screws or

(M3 to M6) bolts, and has a flat
head.
Diagonal pliers Cuts insulation tubes

and cable ties.
Crimping tool Crimps the metal jacket

at the end of a coaxial
cable assembly.
Segmented blade Cuts the adhesive tapes

utility knife on a carton.
Floating nut mounting Installs or removes a

bar floating nut.
Antistatic clothing Prevents operators

against electrostatic
charges.
ESD glove Prevents operators

charges.
ESD wrist strap Prevents operators

charges.

OceanStor V3 Series
Table 3-2 lists the meters required in the installation process.
Table 3-2 Meters required in the installation process

Name Pictogram Function
Multimeter Measures the insulation

of a cabinet, connection
of a cable, and electric
performance
specifications of a
device, such as the
voltage, current, and
resistance.
Network cable tester Tests whether a network

cable works properly.
Prepare the following materials before installing devices: contract/agreement, device

configuration table, equipment room design and construction drawing paper (provided by the
customer), and product documentation.
Obtaining Documentation
Before configuration, get the documentation in Table 3-3 ready.
Table 3-3 Documentation list

Document Name How to Obtain
Installation Guide For example, if you want to

obtain OceanStor UltraPath
CloudEngine 6800&5800 V100R002CXX Product for Linux V100R008C50
Documentation User Guide, log in to http://
OceanStor SNS2124&SNS2224&SNS2248 Fibre Channel support.huawei.com/
Switch V100R002CXX User Guide enterprise/, enter UltraPath
in the search bar, and press
Enter to view or download
the document of the relevant
version.

OceanStor V3 Series
Document Name How to Obtain
l OceanStor UltraPath for Linux V100R008CXX User NOTE

Guide This document uses product
versions in Table 3-3 as
l OceanStor UltraPath for AIX V100R008CXX User examples. If the onsite product
Guide versions are different from
those in the document, Log in
l OceanStor UltraPath for Solaris V100R008CXX User to http://
Guide support.huawei.com/
l OceanStor UltraPath for vSphere V100R008CXX User enterprise/, and obtain the
Version Mapping specific to
Guide the product versions at your
l OceanStor UltraPath for Windows V100R008CXX User site and complete the
Guide configuration.
Business Continuity and Disaster Recovery Solution

V200R001CXX User Guide (Active-Active Mode)
HUAWEI Rack Server Product Documentation
3.2.2 Quick checklist for the installation environment

To implement a correct and smooth device installation, ensure that the installation
environment meets requirements before installing storage devices.
Table 3-4 lists the check items and requirements on the installation environment.
Table 3-4 Quick checklist for the installation environment

No. Item Requirement
1 Site selection The site of the equipment room must be free of: high or low
temperature, heavy dust, harmful gas, inflammable or
explosive materials, electromagnetic interference (nearby
large-sized radar station, broadcast transmitting station, or
transformer station), unstable electric voltage, and large
vibration or strong noise. Therefore, during the engineering
design, you need to consider hydrology, geography,
earthquake, electric power, and transportation conditions
according to the technical requirements for communication
network planning and communication devices.
2 Civil construction The size of the equipment room must be sufficient for product
installation and capacity expansion. The floor can meet the
requirements for the bearing weight. The cable slot, cable
ladder, and cable holes are complete or ready. The decoration
is complete.

OceanStor V3 Series
3 Operating l When the altitude is lower than 1800 m (5904 feet), the
ambient room temperature of controller enclosures and disk
temperature enclosures must be kept within 5°C to 40°C (41°F to
104°F), and that of high-density disk enclosures must be
kept within 5°C to 35°C (41°F to 95°F).
l When the altitude ranges between 1800 m (5904 feet) and
3000 m (9840 feet), the room temperature must be kept
within 5°C to 30°C (41°F to 86°F).
4 Altitude l Operating altitude of disks

– HDDs: –304.8 m to +3048 m (–999.99 ft. to
+9999.99 ft.)
– SSDs: –305 m to +3048 m (–1000.64 ft. to +9999.99
ft.)
l Non-operating altitude of disks
– HDDs: –305 m to +12192 m (–1000.64 ft. to
+39999.51 ft.)
– SSDs: –305 m to +12192 m (–1000.64 ft. to
+39999.51 ft.)
5 Particle l ISOa 14664-1 Class8.

Contaminants
l You are advised to ask a professional organization to
monitor the particle contaminants in the equipment room.

OceanStor V3 Series
6 Corrosive l Copper corrosion rate: less than 300 Åb/month per ANSIc/
Airborne ISAd-71.04 severity level G1.
Contaminants l Silver corrosion rate: less than 200 Åb/month per ANSIc/
ISAd-71.04 severity level G1.
l You are advised to ask a professional organization to
monitor the corrosive airborne contaminants in the
equipment room.
l The following is an example of initial evaluation for
environmental corrosion risks.
– Whether the equipment room is near any sulfurous gas
emission sources, for example, porcelain factories,
rubber plants, tire factories, chemical factories, sewage
plants, power stations, paper mills, smelters,
automobile factories, coal mines, electroplating
factories, food factories, and tanneries? If yes,
environmental corrosion risks may exist.
– Whether the equipment room is near the sea, saline,
sewer outlets, sewage treatment tanks, and industrial/
heating boilers? If yes, environmental corrosion risks
may exist.
– Whether the equipment room was decorated in the
latest six months? If yes, environmental corrosion risks
may exist.
– Whether batteries are stocked in the equipment room?
Whether the storage battery leaks? If yes,
environmental corrosion risks may exist.
– Whether the equipment room is closed tightly?
Whether the room windows and doors are always
closed? If no, environmental corrosion risks may exist.
7 Vibration and l Operating vibration

shock 5 Hz to 300 Hz: 1.5 m/s2, 0.5 oct/min 3 axes, 1 sweep
cycles per axis; 5 Hz to 500 Hz: 0.27 Grms, 3 axes, 10 min
per axis
l Non-operating vibration
5 Hz to 20 Hz, PSD: 1.0 m2/s3; 20 Hz to 200 Hz, –3 dB/
oct; 3 axes, 30 min per axis
l Non-operating shock
Half sine, 6 ms, 300 m/s2, 6 directions, 3 times per
direction
8 Air conditioner If the temperature in the room exceeds 35°C, you are
recommended to install air conditioners (which can be
restarted after power-off). Do not let the air conditioner blow
directly toward the devices.

OceanStor V3 Series
9 Moisture-proof If the relative humidity is greater than 70%, install the

measures dehumidifying device, such as the air conditioner with the
dehumidification function or special dehumidifier. Ensure that
the equipment room is protected from water seepage and dew.
10 Heating For an environment where the average daily temperature is

lower than 5°C for at least 90 days each year, heating devices
are required. For an environment where the average
temperature is lower than 5°C for 60 to 90 days each year,
heating devices are recommended.
11 Ventilation and To ensure smooth ventilation, the cabinet should be at least

heat dissipation 100 cm (39.4 inches) away from the walls and you should
leave a clearance of at least 120 cm (47.28 inches) between
the cabinets. To keep a convective air transfer between the
cabinet and the equipment room, no enclosed space is allowed
in the cabinet. 1 U space should be left above and below each
device.
12 Dust-proof For the equipment room near dust sources (such as coal
measures mines, country roads, or farmland), use double-layer
aluminum alloy windows for proper sealing and an anti-theft
and fireproof door. Separate the devices from the door with a
partition board to avoid dust.
13 Ground resistance Less than 10 Ω. The distance between the top of the ground
terminal and the ground should be at least 0.7 m (27.58
inches). In the cold regions, the ground terminal should be
buried under the layer of frozen earth. Periodically monitor
ground resistance to ensure ground effectiveness.
14 Ground lead-in The ground bar in the equipment room should be connected to
the network of ground cables. The ground lead-in should not
be longer than 30 m (98.4 feet) and should use the zinc-coated
flat steel whose cross-sectional area is equal to or more than
40 mm (1.57 inches) x 4 mm (0.157 inches). The contact point
should be handled for insulation and anticorrosive purposes.
The above-ground steel should be provided with measures to
avoid mechanical damage and should be intact without
soldering points for the break.
15 Lightning The equipment room must be provided with lightning

protection conductors such as the lightning rod or lightning belt. The
lightning conductors share the ground bars with the protection
ground cables of the equipment room.

OceanStor V3 Series
16 AC The AC distribution switches and AC power cables are

properly installed.
The 2 U controller enclosure
l 100 V to 240 V, ±10%, 10 A to 12 A, single-phase, 50/60
Hz
l Supports dual-live-line input (2W+PE), 200 V to 240 V,
±10%
The 3 U and 6 U controller enclosure
l 200 V to 240 V, ±10%, 10 A, single-phase, 50/60 Hz
l Supports dual-live-line input (2W+PE), 200 V to 240 V,
±10%
Disk enclosure
High-density disk enclosure
17 High voltage DC The high voltage DC distribution switches and high voltage
DC power cables are properly installed.
l The high voltage DC power module of the 2 U controller
enclosure (N/A for North America and Canada): 240 V,
±20%, 6.5 A
l The high voltage DC power module of the 3 U and 6 U
controller enclosure (N/A for North America and Canada):
240 V, ±20%, 10 A
l The high voltage DC power module of the disk enclosure
(N/A for North America and Canada) : 240 V, ±20%, 10 A
18 DC The DC distribution switches and DC power cables are

properly installed.
l The DC power module of the 2 U controller enclosure: -48
V to -60 V, ±20%, 30 A
l The DC power module of the disk enclosure: -48 V to -60
V, ±20%, 18.5 A
19 Circuit breaker To prevent other devices connected to the circuit breakers

from being incorrectly powered off due to a power supply
failure of the storage device, you are advised to ensure that the
electric current of the circuit breakers of the external power
supplies to which the storage device is connected complies
with the following specifications:
l AC power supplies: greater than 16 A
l DC power supplies: greater than 32 A

OceanStor V3 Series
20 AC power ground Do not connect the neutral line of a power cable to the
protection ground bar of any communication devices in the
equipment room. It is recommended that you set leading-out
terminals for AC safety ground in the equipment room for the
connection to devices.
21 AC surge The AC power system of the equipment room must be

protection equipped with a lightning arrestor with the rated discharging
current no less than 20 kA. The arrestor must be properly
grounded.
22 DC power ground The storage device is a type of DC-I device on which the
"RTN" terminals and the ground terminal of the system
chassis are separated. The DC power module of the storage
device does not provide any ground terminals. Therefore, the
storage device is grounded through the ground terminal of the
system chassis.
23 Transmission The debugging of the transmission device is complete, and the

device capacity of the transmission device meets the engineering
requirements. The protection ground of the transmission
system must be connected to the ground bar in the equipment
room.
24 Cabinet The cabinet for installing the devices must be a standard 19-
inch cabinet. The depth of the cabinet must be at least 1000
mm (39.37 inches). The depth of a cabinet for installing high-
density disk enclosures must be at least 1100 mm (43.31
inches).
a: ISO (International Organization for Standardization)

b: Å is the international symbol for the non-SI unit ångström, a physical unit of length. One
Å is equal to ten-billionth of one meter.
c: ANSI (American National Standards Institute)
d: ISA (Instrument Society of America)
In addition, make sure that the following special requirements on the site are met:
l Ensure that doors, passageways, and elevators are of adequate dimensions to allow
passage of the cabinets.
l Before installation, check whether to submit the qualification certificate of the
installation company to the property management entity in charge of the installation site.
l Confirm the delivery time and installation time in advance, for example, from 8:00 a.m.
to 6:00 p.m.

OceanStor V3 Series
NOTICE
l Take particular care to avoid bumping into doors, walls, or shelves during transportation,
relocation, or installation of storage devices.
l Do not touch the components or uncoated metal surface of any unit with dirty gloves.
3.3 Device Installation

Install devices as instructed in the following description to avoid unnecessary rework at your
site.
Install devices in data center A, data center B, and a third-place quorum site. The following
components are used as an example. Install devices based on onsite requirements. The
installation process is as follows:
Instal Site Procedure
lation
Sequ
ence
1 Data center 1. Install the storage devices. For details about how to install it, see
A the Installation Guide of the corresponding product model.
2. Install CloudEngine 5800 series switches. For details about how
to install a CloudEngine 5800 switch, see:
l CloudEngine 7800&6800&5800 Hardware Installation and
Maintenance Guide
l CloudEngine 7800&6800&5800 V100R005C00
Configuration Guide
NOTE
If you use other switches, see the installation guide specific to the
switches at your site to install them.
3. Install SNS2248 series switches. For details about how to install
an SNS2248 switch, see the OceanStor
SNS2124&SNS2224&SNS2248 Fibre Channel Switch
V100R002C00 User Guide.
NOTE

OceanStor V3 Series
Instal Site Procedure

lation
Sequ
ence
2 Data center 1. Install the storage devices. For details about how to install it, see
B the Installation Guide of the corresponding product model.
Maintenance Guide
Configuration Guide
NOTE
3. Install SNS2248 series switches. For details about how to install
an SNS2248 switch, see the OceanStor
SNS2124&SNS2224&SNS2248 Fibre Channel Switch
V100R002C00 User Guide.
NOTE
3 Third- 1. Install the quorum server.

place NOTE
quorum For details about how to install a quorum server, see the installation
site guide specific to the quorum server at your site.
Maintenance Guide
Configuration Guide
NOTE
For details about the device layout, see Figure 3-2 or Figure 3-3. The device models and
number of devices depend on the onsite requirements.

OceanStor V3 Series
Figure 3-2 Device layout (3 U storage device)

Data center 1 Data center 2 Third-place quorum site
Cabinet: H05 Cabinet: H05 Cabinet: H01
39 1U 1U 1U 1U 1U 1U
38 1U SNS2248 1U 1U SNS2248 1U 1U Filler panel 1U
37 1U Filler panel 1U 1U Filler panel 1U 1U Filler panel 1U
36 1U SNS2248 1U 1U SNS2248 1U 1U Filler panel 1U
34 1U CE5800 1U 1U CE5800 1U 1U CE5800 1U
32 1U CE5800 1U 1U CE5800 1U 1U CE5800 1U
30 1U Filler panel 1U 1U Filler panel 1U 1U RH1288 V3 (quorum server) 1U
26 1U 1U 1U 1U 1U Filler panel 1U
RH2288(sevice host) RH2288(sevice host)
Disk enclosure Disk enclosure
16 1U Controller enclosure 1U 1U Controller enclosure 1U 1U Filler panel 1U
Figure 3-3 Device layout (6 U storage device)

Data center 1 Data center 1 Data center 2 Data center 2 Third-place quorum site
42 1U Filler panel 1U 1U 1U 1U Filler panel 1U 1U 1U 1U Filler panel 1U
41 1U Filler panel 0U 1U Disk 1U 1U Filler panel 1U 1U Disk 1U 1U Filler panel 1U
40 1U Filler panel 1U 1U enclosure 1U 1U Filler panel 1U 1U enclosure 1U 1U Filler panel 1U
35 1U Filler panel 1U 1U 1U 1U Filler panel 1U 1U 1U 1U CE5800
33 1U Filler panel 1U 1U Disk 1U 1U Filler panel 1U 1U Disk 1U 1U CE5800 1U
31 1U Filler panel 1U 1U 1U 1U Filler panel 1U 1U 1U 1U RH 1288V3 1U
KVM KVM
24 1U Filler panel 1U 1U SVP 1U 1U Filler panel 1U 1U SVP 1U 1U Filler panel 1U
23 1U SNS2248 1U 1U 1U 1U SNS2248 1U 1U 1U 1U Filler panel 1U
Engine Engine
21 1U SNS2248 1U 1U 1U 1U SNS2248 1U 1U 1U 1U Filler panel 1U
19 1U CE5800 1U 1U Filler panel 1U 1U CE5800 1U 1U Filler panel 1U 1U Filler panel 1U
18 1U Filler panel 1U 1U Filler panel 1U 1U Filler panel 1U 1U Filler panel 1U 1U Filler panel 1U
17 1U CE5800 1U 1U Filler panel 1U 1U CE5800 1U 1U Filler panel 1U 1U Filler panel 1U
14 1U 1U 1U enclosure 1U 1U 1U 1U enclosure 1U 1U Filler panel 1U
Sevice host Sevice host
13 1U 1U 1U 1U 1U 1U 1U 1U 1U Filler panel 1U

OceanStor V3 Series
l Storage device layout

– To conveniently maintain and operate a controller enclosure, install it in the middle
of the cabinet (15 U to 25 U).
– Reserve 2 U space above and below the controller enclosure to install the cable tray
(also to facilitate the operation of removing and inserting the modules in the
controller enclosure).
– Symmetrically install disk enclosures above and below the controller enclosure.
– Do not stack disk enclosures. Enable five disk enclosures to form a group. In a
cabinet, reserve at least 1 U space between disk enclosure groups for easier
management and minimum vibration transfer.
– Reserve 2 U space at the bottom of the cabinet to facilitate cabling, ventilation and
heat dissipation, and maintenance of the devices in the lower part of the cabinet.
l Switch layout
– Install two SNS2248 switches into two cabinets respectively or the same cabinet in
a data center. Use different power supplies to provide power for them.
– Reserve 1 U space below each switch for cabling.
3.4 Cable Connection

HyperMetro cable connection involves: network between hosts and storage arrays,
HyperMetro replication network, same-city data center network, and quorum network.
Figure 3-4, Figure 3-5 and Figure 3-6 show how switches, controller enclosures, and service
hosts are connected using cables in and across data centers.

OceanStor V3 Series
Figure 3-4 Cable connections in and across data centers (2 U storage device)

OceanStor V3 Series

OceanStor V3 Series
NOTE
l The ports that are numbered in digits are connected using cables in data centers and the ports that are
numbered in upper-case letters are connected using cables across data centers.
l For details about cable connections between disk enclosures and controller enclosures, see
Cascading Disk Enclosures in the Installation Guide of the corresponding product model.
l The quorum site supports two quorum servers in active/standby mode for V300R006C10 and later
versions.
Fibre Channel networking is used as an example to explain cable connection principles. For
details, see Table 3-5.

OceanStor V3 Series
Table 3-5 Cable connection principles

Network Cable Connection Principle
Type
Network l Hosts and storage devices are connected through Fibre Channel
between hosts switches. Each data center has two Fibre Channel switches.
and storage l Each Fibre Channel switch has at least N ports to connect hosts and
arrays storage devices. N = 1 x Number of Servers + 2 x Number of
Storage Devices.
l Host-Fibre Channel switch connection: Each host has at least two
Fibre Channel ports to connect two Fibre Channel switches of the
data center. It is recommended that the two ports be separated on two
HBAs.
l Storage device-Fibre Channel switch connection: Each controller has
at least two ports to connect two Fibre Channel switches of the data
center. It is recommended that the two ports be separated on two
Fibre Channel interface cards.
HyperMetro l The HyperMetro replication network between storage devices uses

replication Fibre Channel switches for connection. Each data center has two
network Fibre Channel switches.
l Storage device-Fibre Channel switch connection: Each controller has
two Fibre Channel ports to connect two Fibre Channel switches of the
data center. It is recommended that the two ports be separated on two
Fibre Channel interface cards.
Same-city l Dense wavelength division multiplexing (DWDM) devices are

network recommended for data center interconnection.
between data l If the HyperMetro replication network is a Fibre Channel network,
centers Fibre Channel switches are cascaded in one-to-one mode. If the
HyperMetro replication network is an IP network, Ethernet switches
are cascaded in one-to-one mode.
Arbitration l The quorum server is connected to storage devices through Ethernet

network switches. Each data center has two Ethernet switches.
l Each controller of a storage device has one IP port to connect to one
Ethernet switch of the data center.
l The quorum server is connected to Ethernet switches. It is
recommended that two IP ports be separated on two network adapters
to connect two Ethernet switches at the quorum site.
Management l An Ethernet switch is used for management. The management

network network ports of the host and controller are connected to one Ethernet
switch of the data center.
l You can use BCManager eReplication to manage networks. For
details, see Business Continuity and Disaster Recovery Solution
V200R001CXX User Guide (Active-Active Mode). For details about
how to obtain the documentation, see 3.2.1 Preparing Tools, Meters,
and Documentation.

OceanStor V3 Series
3.5 Power-on
After installing all devices, power on them and check their operating status. Ensure that all
devices and their hardware are properly installed. Otherwise, do not power on them.
Power-on Principles
l Both parties (Huawei and the customer) must be at the power-on site. Devices can be
powered on only after both parties confirm the power-on operation.
l Operations on power sourcing equipment (PSE), power distribution equipment (PDE),
and powered devices (PDs) must comply with standards and regulations.
l You must submit a power-on application to the customer's administrative unit. After an
approval, power on and operate devices under the assistance and supervision of power
engineers and supervision personnel assigned by the customer at the site.
l PDs must be connected to the positions specified by PSE and PDE to ensure that PSE
and PDE can provide power for PDs.
l You must use measuring instrument to check whether power supplies meet the following
requirements before powering on a device: The power supply of the device is not short-
circuited; the power cable plug is firmly connected; the output switch of the PSE is
turned off and the output voltage is within the normal range; all power switches of the
PDs are turned off; the PDs are not short-circuited.
Check Before Power-on

l Checking the device installation
Table 3-6 lists the check items.
Table 3-6 Device installation checklist

Check Normal Abnormal
Item
Controller l Stably installed on the guide l Tilted.

enclosure rails without displacement. l Screws are loose or dropped
Disk l Tightly screwed. off.
enclosure
Switch
Host
Filler The vacant slots in the cabinet are The vacant slots in the cabinet are
panel covered by filler panels. exposed.
Entirety l All devices are stably installed l One ore more devices are
without displacement. displaced.
l All screws are tightly screwed. l One or more devices are tilted.
l Screws are loose or dropped
off.

OceanStor V3 Series
l Checking the cable layout

Table 3-7 lists the check items.
Table 3-7 Cable layout checklist
No. Check Item
1 Labels are correctly attached to cables.
2 Cables are laid out in an untangled and orderly fashion.
3 When cables pass through the cable ladder, cables are secured to the beam of
the cable ladder.
4 Troughs are used to route cables outside the cabinet and cables do not
overflow the troughs.
5 The bending radius of optical fibers is equal to or larger than 50 mm.
6 The power cable and the protection ground (PGND) cable are bent smoothly.
7 The power and PGND cables are connected correctly and firmly.
8 Ground cables of a cabinet are connected correctly and firmly.
9 The diameters of the power and PGND cables meet the power distribution
requirements.
10 The power cables, grounding cables, and signal cables outside the cabinet are
laid separately with a distance of larger than 30 mm.
11 Cables are bound in a rectangular shape. (Single-core cables can be bound in

a round shape.)
12 Cables are bent with a bend radius of greater than 60 mm at turning points
and are not bundled at bend points.
13 Optical fibers are laid out without using force or having unnatural bends and
squeezes.
14 OT terminals of the power cables and grounding cables are welded or

crimped firmly.
15 Protection tubes or insulating adhesive plasters are used to wrap power

cables, naked cables, and OT terminal stems of ground cables. There should
be no bare copper wires in OT terminals.
16 All cabinets and enclosures with metal or partially metal shells are correctly
grounded and connected.
17 Cables are correctly bundled at an even spacing. After cables are bundled
with cable ties, the excess parts of the cable ties are cut off without burrs. All
the cable ties face the same direction for a neat appearance.
18 The DC power cables shipped with the storage device are black and blue,
and the PGND cable is olive or yellow.
19 Power cables and grounding cables use the entire copper core without a joint.

OceanStor V3 Series
No. Check Item
20 Labels are attached to the power cables and grounding cables in the same
direction for users' convenient check.
Power-on Procedure
l Step 1 Connect grounding cables.
a. Huawei is responsible for connecting grounding cables of storage devices and
cabinets and checking whether ground resistance connectors are connected firmly.
b. Huawei is responsible for testing the ground resistance between storage cabinets
and the equipment room and checking whether ground resistance connectors are
connected firmly.
l Step 2 Power on power distribution frames (PDFs) and array cabinets.
a. Huawei is responsible for turning on/off miniature circuit breakers (MCBs) and
switches of PDFs and array cabinets.
b. The customer is responsible for using a multimeter to check the output voltage of
array cabinets and PDFs and ensure that the output voltage is in a normal range and
PSEs have sufficient redundant power supplies to meet power requirements of
storage devices and cabinets.
l Step 3 Power on devices.
a. Huawei is responsible for turning on/off switches of power distribution units
(PDUs) and powering on devices in sequence under the supervision of the customer.
The power-on sequence is: storage devices > Fibre Channel switches > core
switches > application hosts.
NOTE
Power on the next device only after the previous device is running properly. For details
about how to power on storage devices, see Powering On Devices in the Installation Guide
of the corresponding product model.
b. The customer is responsible for checking the operating status of input power to
ensure that input power is stable during the power-on process of cabinets and
storage devices.
Check After Power-on

After powering on devices, check the following items:
l Check whether fans of the devices are working properly and air is discharged from the
air vent.
l Check whether device indicators are normal.
NOTE
For details about device indicator status, see Powering On Devices in the Installation Guide of
the corresponding product model.
l Log in to devices and check their operating status.

OceanStor V3 Series
3.6 Storage Array Initialization

After powering on a storage array, you must initialize it.
Storage array initialization includes configuring an initial IP address for the management
network port as well as applying for and importing a license. For details about how to
initialize a storage array, see Initializing the Storage System in the Installation Guide of the
corresponding product model.
3.7 Multipathing Software Installation

and the installation procedure of multipathing software.
Context
Multipathing software must be installed for the HyperMetro solution. You can use either
Huawei UltraPath or third-party multipathing software.
l In terms of multipathing, UltraPath is recommended for HyperMetro. UltraPath can
identify host locations so that hosts can access the nearest storage array, reducing cross-
site accesses and latency while improving access efficiency and storage performance.
NOTE
For details on how to install UltraPath, see UltraPath Software Installation.
l If the customer needs to use third-party multipathing software on the application server,
the function of Uses third-party multipath software for initiators must be enabled on
Huawei storage.
NOTE
For details on how to install third-party multipathing software, see Third-party Multipathing
Software Installation.
3.7.1 UltraPath Software Installation

Selecting and managing paths between an application server and the storage system can be
realized after the UltraPath software is installed.
Context
To ensure that link aggregation can be implemented in the scenario that a HyperMetro LUN is
mapped to a host, install UltraPath on the host before configuring HyperMetro pairs.
Install UltraPath software following instructions in the relevant documentation. For details
about applicable software versions, see 1.2 License Requirements and Compatible
Products. For details about how to obtain the documentation, see 3.2.1 Preparing Tools,
Meters, and Documentation.
3.7.2 Third-party Multipathing Software Installation

and the installation procedure of third-party multipathing software.

OceanStor V3 Series
Context
The operating systems type of third-party multipathing software supported by the
HyperMetro, refer to the HyperMetro Configuration Guide for Huawei SAN Storage
Using OS Native Multipathing Software.
NOTE
Log in to http://support.huawei.com/enterprise/. In the search bar, enter the document name. Search,
browse, and download the Host Connectivity Guide for corresponding operating systems to install the third-
party multipathing software.
For example, if you want to obtain HUAWEI SAN Storage Host Connectivity Guide for Oracle, log in to
http://support.huawei.com/enterprise/, enter Host Connectivity Guide Oracle in the search bar, and press
Enter to view or download the document of the relevant version.
3.8 Arbitration Software Installation

This section describes how to install the arbitration software. Quorum server software needs
to be installed only when a quorum server is used for HyperMetro.
Prerequisites
l For details about how to obtain this software, see the Availability section.
l The quorum server has been deployed and its hardware meets the requirements.
NOTE
l For the hardware requirements on the quorum server, see section Impact and Restrictions.
l If you deploy the quorum server on a VM, you can export an OVA template of this VM for
quick deployment once the VM fails. For details, see 6.8 How Can I Use OVA Templates to
Quickly Deploy Virtual Quorum Servers?.
l The validity period of the default arbitration certificate is 10 years (start from September
2015). Ensure the system time of the quorum server is correct so that the default
arbitration certificate is valid.
l Use a Secure Shell (SSH) tool such as Xshell, PuTTY to log in to the quorum server.
NOTE
To ensure security of the operating system, you are advised to harden its security. For details about
how to harden security of an operating system, see the official security operation guide of the
operating system.
Context
By default, the Ubuntu system uses dash upon the installation. However, the arbitration
software must be installed in bash mode. Therefore, you must disable dash when installing the
arbitration software in the Ubuntu system.
NOTE
In any directory of the Ubuntu system's operating system, run the sudo dpkg-reconfigure dashcommand.
Press the → key, select No, and press Enter to disable dash.
The system shell is the default command interpreter for shell scripts.
xUsing dash as the system shell will improve the system's overall performance. It
does not alter the shell presented to interactive users.
Use dash as the default system shell (/bin/sh)?
<Yes> <No>

OceanStor V3 Series
Procedure
Step 1 Log in to the quorum server.
Select a user account according to your quorum server:
l When using a third-party quorum server, log in to the server using the root user.
l When using a Huawei quorum server, perform the following operations:
a. Use the quorumAdmin user to log in to the quorum server.
NOTE
The default password of the quorumAdmin user is Huawei@SYS3. You are advised to
periodically change your password for your account's security.
b. Run the su root command to switch to user root.
NOTE
Enter the password of user root as instructed. The default password of the root user is
Huawei@SYS3. You are advised to periodically change your password for your account's
security.
Step 2 Decompress the installation package.

1. In the operating system of the quorum server, run the unzip command to decompress the
installation package.
XXX@Linux:~# unzip OceanStor/QuorumServer/
OceanStor_QuorumServer_VXXXRXXXCXX.zip
Archive: OceanStor_QuorumServer_VXXXRXXXCXX.zip
package/
package/quorum_server.sh
package/packages/
package/packages/QuorumServer-VXXXRXXXCXX-linux.x86_64.rpm
package/qs_version.ini
package/tools/
2. After decompressing the installation package, run the cd package command to go to the
directory that is decompressed.
XXX@Linux:~# cd package
3. (Optional) Run the ll command to list files in the directory.

Step 3 Install the arbitration software.
1. Log in to the quorum server as user root and run the ./quorum_server.sh -install
command to install the arbitration software.
NOTE
Perform software-related operations and management as the non-root user.

XXX@Linux:~# ./quorum_server.sh -install
Verify the QuorumServer existence.
The QuorumServer is not installed.
The current user is the root user. A quorum server administrator account
needs to be provided. Continue to install?
<Y|N>:Y #Enter "Y" to install the
arbitration software.
Enter an administrator account for the quorum server:[default:
quorumsvr]: #Press "Enter". The system installs the arbitration software
under the default user account quorumsvr.
Created new account: quorumsvr.
Changing password for quorumsvr.
New Password: #Set the password
of user quorumsvr.
Reenter New Password: #Repeat the
password.
Password changed.

OceanStor V3 Series
Installing the quorum server.

Preparing... ########################################### [100%]
1:QuorumServer ########################################### [100%]
[Notice] No old configuration need to resume.
QuorumServer install success completed.
NOTE
quorumsvr is the default user account for the arbitration software installation. If you want to install the
arbitration software under another user account, enter the user name after Enter an administrator
account for the quorum server:[default: quorumsvr], for example, Enter an administrator
account for the quorum server:[default: quorumsvr]:User_test.
For security purpose, restrict the permissions of the non-root user. In this condition, to ensure that the
arbitration software is successfully installed, create a non-root user before installing the arbitration
software and ensure that the non-root user can obtain the permissions of the following commands by
running the sudo command: cat, ps, sh, useradd, groupadd, userdel, groupdel, usermod, passwd,
sed, rm, rpm, ls, chmod, chown, find, xargs, killall, mv, ln, and unzip. For example, run the sudo cat
xxx command. In the command, xxx indicates the name of a file in the system.
Step 4 (Optional) Check whether the arbitration software is installed successfully.

1. After the arbitration software is installed, it automatically restarts. Enter the CLI of the
quorum server, go to any directory, run the qsadmin command in any directory to open
the arbitration software. If the arbitration software page is displayed, the arbitration
software restarts successfully.
XXX@Linux:~# qsadmin
start main!
Waiting for connecting to server...
admin:/>
2. Enter the CLI of the quorum server, go to any directory, run the ps -elf |grep quo*
command to check whether the arbitration software is installed successfully. If ./bin/
quorum_serverd is displayed in the command output, the arbitration software is
installed successfully.
XXX@Linux:~# ps -elf |grep quo*
0 S testUser 7013 1 0 80 0 - 3700 wait 22:56 ?

0 S testUser 7021 7013 0 80 0 - 22958 - 22:56 ?
0 S testUser 7232 6394 0 80 0 - 2452 pipe_w 22:57 pts/0
00:00:00 /bin/sh /opt/quorum_server/bin/quorum_server_monitor.sh

00:00:00 ./bin/quorum_serverd
00:00:00 grep quo*
Step 5 Optional: When two quorum servers are configured at the quorum site in V300R006C10,
perform Step 2 to Step 4 to install the arbitration software.
----End
Follow-up Procedure
After the installation is successful, you can directly close the quorum server's CLI window.
If you want to uninstall the arbitration software, see 5.3.6 Uninstalling the Arbitration
Software.

OceanStor V3 Series
HyperMetro Feature Guide for Block 4 Configuration
4 Configuration
About This Chapter
This chapter describes how to configure HyperMetro, including configuration preparations,

process, and procedures.
4.1 Configuration Process

Before configuring HyperMetro, you must know the configuration process to ensure smooth
operations.
4.2 Configuration Preparations
This section describes prerequisites and documents that you must prepare before you
configure HyperMetro.
4.3 Configuring Switch
This section describes the configuration requirements of core switches and access switches at
the network layer and configuration procedure of the Fibre Channel switches at the storage
layer.
4.4 Configure Quorum Server Software
This section describes how to configure the quorum server software. Quorum server software
needs to be configured only when a quorum server is used for HyperMetro.
4.5 Configuring Basic Storage Services
This section describes how to configure basic storage services for the HyperMetro.
4.6 Creating SAN HyperMetro
This chapter describes how to create a SAN HyperMetro.
4.7 Configure a Multipathing Policy for Host
This section describes how to configure the Multipathing software.
4.8 Verifying the Configuration
After configured, you can view the status of the data on the local and remote storage systems
to check whether HyperMetro between the local and remote storage systems is successful.

OceanStor V3 Series
4.1 Configuration Process

Before configuring HyperMetro, you must know the configuration process to ensure smooth
operations.
Figure 4-1 shows the configuration process of HyperMetro.
Figure 4-1 Configuration process of HyperMetro
Start
Configuration
Preparations.
Configuring Switch.
Configuring Quorum
Server Software. This operation is performed on
Checking the License File.
both the local and the peer remote
storage systems.
This operation is only performed on
Adding a Remote Device.
Configure Basic Storage the local storage system.
Services.
Creating a Quorum This operation is performed on
Server. both the local and the peer remote
storage systems.
Configure HyperMetro. Creating a HyperMetro This operation is only performed on
Domain. the local storage system.
Creating a HyperMetro This operation is only performed on

Pair. the local storage system.
Configure a Multipathing
Policy for Host. Creating a HyperMetro This operation is only performed on
Consistency Group. the local storage system.
Verifying the
Configuration
End Mandatory Optional Mandatory Optional

item item sub-item sub-item
Table 4-1 describes the configuration procedure of HyperMetro.

OceanStor V3 Series
Table 4-1 Configuration procedure of HyperMetro

Configuration Description Operation Location
Procedure
Configuration Describes prerequisites and Local storage systems,

Preparations. documents that you must prepare remote storage systems and
before you configure HyperMetro. third-place quorum servers.
Configuring Switch. Describes the configuration Switches.

requirements of core switches and
access switches at the network layer
and the configuration procedure of
Fibre Channel switches at the storage
layer.
Ethernet switches serve as the core
switches and access switches at the
network layer and Fibre Channel
switches are used at the storage layer.
Configuring This section describes how to Quorum servers.

Quorum Server configure, and manage the quorum
Software. server software.
Configuring Basic Configure the storage system to This operation is

Storage Services divide the storage space into LUNs performed on both the
and map them to application servers local and the peer remote
so that the application server can read storage systems.
and write the storage space provided
by the storage system.

OceanStor V3 Series
Configuration Description Operation Location

Procedure
Configure Describes how to check the 1. Check the license file.

HyperMetro: HyperMetro license, add a remote (This operation is
1. Check the device and quorum server, and create performed on both the
license file. a HyperMetro domain and local and the peer
HyperMetro pair. remote storage
2. Add a remote systems.)
device.
2. Add a remote device.
3. Add the quorum (This operation is only
server. performed on the local
4. Create a storage system.)
HyperMetro 3. Add the quorum server.
domain. (This operation is
5. Create a performed on both the
HyperMetro pair. local and the peer
6. Create a remote storage
HyperMetro systems.)
consistency 4. Create a HyperMetro
group. domain. (This operation
is only performed on
the local storage
system.)
5. Create a HyperMetro
pair. (This operation is
only performed on the
local storage system.)
6. Create a HyperMetro
consistency group.
(This operation is only
performed on the local
storage system.)
Configure a This section describes how to Host.

Multipathing Policy configure an UltraPath policy for
for Host. HyperMetro. For HyperMetro, the
UltraPath software is configured to
improve the I/O processing efficiency
and reduce the access latency.
4.2 Configuration Preparations

This section describes prerequisites and documents that you must prepare before you
configure HyperMetro.
Prerequisites for configuring HyperMetro are as follows:

l All devices have been installed.
l The IP/Fibre Channel network is working properly between the two data centers.

OceanStor V3 Series
l Storage units have been deployed at a third-place quorum site.

l If other features besides HyperMetro need to be configured for the storage system, see
the Impact and Restrictions section about the interaction among features.
l The required licenses have been applied and imported based on the license operation
guide.
4.3 Configuring Switch

This section describes the configuration requirements of core switches and access switches at
the network layer and configuration procedure of the Fibre Channel switches at the storage
layer.
Context
For the detailed configurations on switches (includes setting domain IDs, configuring the
long-distance mode for links, and creating a zone), see BC&DR Solution Product
Documentation V200R001 (Active-Active Data Center).
4.4 Configure Quorum Server Software

This section describes how to configure the quorum server software. Quorum server software
needs to be configured only when a quorum server is used for HyperMetro.
4.4.1 Configuring the Arbitration Software (SUSE)

This section describes how to configure the arbitration software in SUSE.
Prerequisites
The arbitration software must be configured in user mode.
Procedure
Step 1 Prepare for the configuration.
Before the configuration, make sure that the quorum server has been configured with service
IP address and firewall.
1. Configure a service IP address for the quorum server.

NOTE
If two ports of the quorum server are not bonded, IP addresses of the two ports must be from different
network segments. If the two ports of the quorum server are bonded, you only need to configure a
virtual IP address for arbitration.
– When deploying the arbitration software using VMs, you need to create network
adapters and switches for VMs. In this example, arbitration software is deployed on
VMs, and two ports of the quorum server are not bonded. Figure 4-2 and Table 4-2
show configuration requirements.

OceanStor V3 Series
Figure 4-2 Configuration requirements of virtual network adapters
Table 4-2 Configuration requirements of virtual network adapters

Name Configuration Example
Requirement
Networ vmnic0 connects to n Switch name: vSwitch 1

k controller A of the local n Physical adapters name: vmnic0
adapter and remote storage
2 systems in the HyperMetro n Physical adapters IP addresses and
pair. mask: 192.168.6.31/255.255.255.0

k controller B of the local n Physical adapters name: vmnic1
pair. mask: 192.168.7.31/255.255.255.0
– When deploying the arbitration software using physical machines, the two ports of
the quorum server are not bonded and you are advised to configure service IP
addresses at two different network segments for arbitration ports. In this example,
arbitration software is deployed on physical machines, and two ports of the quorum
server are not bonded. Table 4-3 lists configuration examples.
Table 4-3 Examples for configuring IP addresses of arbitration services

Arbitration Service IP Address Mask
Port
Arbitration 192.168.6.31 255.255.255.0

port 1
Arbitration 192.168.7.31 255.255.255.0

port 2
Run the vi command to open the configuration file of the network adapter used by the
quorum server for arbitration. The following uses network adapters eth1 and eth2 for

OceanStor V3 Series
arbitration ports as an example to describe how to modify the file. Modify the IPADDR
in this file and then save the file.
NOTICE
Parameter STARTMODE must be set to auto.
XXX@Linux:~# vi /etc/sysconfig/network/ifcfg-eth1
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.6.31/24'
MTU=''
NAME='82540EM Gigabit Ethernet Controller'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
XXX@Linux:~# vi /etc/sysconfig/network/ifcfg-eth2
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.7.31/24'
MTU=''
NAME='82540EM Gigabit Ethernet Controller'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
2. Check whether the service IP address configuration of the quorum server takes effect.
Enter the CLI of the quorum server, go to any directory, run the service network restart
command in any directory to enable the IP address configuration to take effect. Then run
the ifconfig command to check whether the configuration for eth1 and eth2 takes effect.
If the IP address that you configure is displayed in the command output, the
configuration takes effect.
XXX@Linux:~#ifconfig
eth1 Link encap:Ethernet HWaddr 08:00:27:45:7A:E2
inet addr: 192.168.6.31 Bcast:192.168.6.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe2e:fba6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43285954 errors:0 dropped:5051127 overruns:0 frame:0
TX packets:5819 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2916916679 (2781.7 Mb) TX bytes:720809 (703.9 Kb)
eth2 Link encap:Ethernet HWaddr 08:00:27:45:7A:EB

3. Configure a port ID for the firewall of the quorum server.
Enter the CLI of the quorum server, go to any directory, run the vi /etc/sysconfig/
SuSEfirewall2 command in any directory to open the firewall configuration file and add
the port ID of FW_SERVICES_EXT_TCP to 30002.

OceanStor V3 Series
NOTE
– If you want to enable other ports for the firewall, add the port IDs to the
FW_SERVICES_EXT_TCP configuration item. For example, if you want to enable port 22,
type FW_SERVICES_EXT_TCP="30002 22".
– If a virtual machine (VM) is used to deploy the arbitration software, enable the firewall port of
the physical machine where the VM is deployed.
XXX@Linux:~# ## Type: string
#
# 9.)
# Which TCP services _on the firewall_ should be accessible from
# untrusted networks?
#
# Format: space separated list of ports, port ranges or well known
# service names (see /etc/services)
#
# Examples: "ssh", "123 514", "3200:3299", "ftp 22 telnet 512:514"
#
# Note: this setting has precedence over FW_SERVICES_ACCEPT_*
#
FW_SERVICES_EXT_TCP="30002"
4. Check whether the firewall configuration of the quorum server takes effect.
Enter the CLI of the quorum server, go to any directory, run the rcSuSEfirewall2 restart
command in any directory to restart the firewall. Then run the iptables -L command to
check whether the firewall configuration takes effect. If the ACCEPT tcp -- anywhere
anywhere tcp dpt:pago-services2 information is displayed in the command output, the
firewall configuration takes effect.
XXX@Linux:~# iptables -L
.
.
.
.
.
.
ACCEPT tcp -- anywhere anywhere tcp dpt:pago-services2
.
.
.
.
.
.
Step 2 Go to the command-line interface (CLI) of the arbitration software.

In any directory of the quorum server's operating system, run the qsadmin command to open
the arbitration software. The arbitration software page is displayed.
start main!
admin:/>
NOTE
After the arbitration software is started, run the help command to check help information and understand
the commands that are required during the configuration process.
Step 3 Add the service IP address and port ID of the quorum server to the arbitration software.
In the CLI of the arbitration software, run the add server_ip command to add the service IP
address and port ID of the quorum server to the arbitration software for management.
admin:/>add server_ip ip=192.168.6.31 port=30002

OceanStor V3 Series
Command executed succesfully.
NOTE
l Service IP addresses of the quorum server are used for interworking with the storage array when an
arbitration server is added to the storage array. If two ports of the quorum server are not bonded, IP
addresses of the two ports must be from different network segments. If two ports of the quorum
server are bonded, IP addresses of the two ports must be the same.
l The ID of the arbitration software's listening port must be the same as that of the port enabled on the
firewall.
After configuration is complete, run the show server_ip command. If the command output
shows the IP address and port ID that are added, the configuration succeeds.
admin:/>show server_ip
Index Server IP Server Port

----- ------------ ------------------
1 192.168.6.31 30002
2 192.168.7.31 30002
Index Local IP Local Port Remote IP Remote Port State

----- ------------ --------- -------- --------- -----
Step 4 (Optional) Replace the original certificates of the quorum server with new ones.
NOTE
To further improve storage system security, you are advised to replace the default security certificate and
private key of the storage systems and those of the quorum server with your own security certificate and
private key.
1. Export the certificate request file of the quorum server.
In the CLI of the arbitration software, run the export tls_cert command to export the
device information. The qs_certreq.csr file is generated in the /opt/quorum_server/
export_import directory of the quorum server.
admin:/>export tls_cert
Command executed successfully.
NOTE
– The certificates must be replaced in user mode.

– The certificate request file of the quorum server can be used to generate certificates in a third-
party Certificate Authority (CA) organization. Copy the certificates to the /opt/
quorum_server/export_import directory of the quorum server. The certificates ensure
security of the quorum server.
– After installing the arbitration software, you are advised to grant the Secure File Transfer
Protocol (SFTP) permission only to the /opt/quorum_server/export_import/ directory to
ensure that the security certificates can be imported and exported.
2. Use the certificate request file to generate certificates.
Send the qs_certreq.csr file to a third party for the third-party CA organization to
generate certificates.
3. Copy the certificates to the quorum server.
After the certificates are generated, copy the certificate (such as qs_cert.crt) of the
quorum server and the CA certificate (such as qs_cacert.crt) to the /opt/quorum_server/
4. Import the certificates to the arbitration software.
In the CLI of the arbitration software, run the import tls_cert ca=qs_cacert.crt
cert=qs_cert.crt command to import the certificates to the arbitration software.

OceanStor V3 Series
admin:/>import tls_cert ca=qs_cacert.crt cert=qs_cert.crt

5. After replacing certificates on the quorum server, replace the certificates on the local and
remote storage arrays. For details, see Managing Certificates section.
Step 5 (Optional) Configure a whitelist.
After you replace a certificate, you must configure a whitelist.
NOTICE
The arbitration software allows a storage system to connect to the quorum server only after
you configure a whitelist and add the SN of storage system to the arbitration software. If you
replace another certificate, you do not need to configure a whitelist anymore.
1. In the CLI of the storage system, run the show system general command to query the
storage system SN.
admin:/>show system general
System Name : XXXXXX

Health Status : Normal
Running Status : Normal
Total Capacity : X.XXXTB
SN : XXXXXXXXXXXXXXXXXXXX
Location :
Product Model : XXXXX
Product Version : VX00R00XC00
High Water Level(%) : XX
Low Water Level(%) : XX
WWN : XXXXXXXXXXXXXXX
Time : XXXX-XX-XX/15:11:15 UTC+08:00
2. In the CLI of the arbitration software, run the add white_list sn=? command to add the
storage system SN to the arbitration software for management.
admin:/>add white_list sn=XXXXXXXXXXXXXXXXXXXX
3. (Optional) Run the change white_list enable_switch=no command to close the whitelist
if you do not need to configure it.
----End
4.4.2 Configuring the Arbitration Software (Red Hat/Red Flag/

NeoKylin/CentOS)
This section describes how to configure the arbitration software in Red Hat, Red Flag,
NeoKylin, or CentOS.
Prerequisites
Procedure

OceanStor V3 Series

NOTE
– When deploying the arbitration software using VMs, you need to create virtual
network adapters and switches for VMs. In this example, arbitration software is
deployed on VMs, and two ports of the quorum server are not bonded. Figure 4-3
and Table 4-4 show configuration requirements.

Requirement

pair. mask: 192.168.6.31/255.255.255.0

pair. mask: 192.168.7.31/255.255.255.0

OceanStor V3 Series

Port
Arbitration 192.168.6.31 255.255.255.0

port 1
Arbitration 192.168.7.31 255.255.255.0

port 2
Run the vi command to open the configuration file of the network adapter used by the
quorum server for arbitration. The following uses network adapters eth1 and eth2 for
arbitration ports as an example to describe how to modify the file. Modify the IPADDR
and NETMASK in this file and then save the file.
NOTICE
Parameter ONBOOT must be set to yes.
XXX@Linux:~# vi /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
HWADDR=08:00:27:45:7A:E2
TYPE=Ethernet
#UUID=e9f75670-fde9-4bf0-941e-c9a251341405
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=192.168.6.31 #IP address of network
adapter
NETMASK=255.255.255.0 #Subnet mask
XXX@Linux:~# vi /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
HWADDR=08:00:27:45:7A:EB
TYPE=Ethernet
#UUID=e9f75670-fde9-4bf0-941e-c9a251341406
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=192.168.7.31 #IP address of network
adapter
NETMASK=255.255.255.0 #Subnet mask
Enter the CLI of the quorum server, go to any directory, run the service network restart
command in any directory to enable the IP address configuration to take effect. Then run
the ifconfig command to check whether the configuration for eth1 and eth2 takes effect.
If the IP address that you configure is displayed in the command output, the
configuration takes effect.
XXX@Linux:~#ifconfig

OceanStor V3 Series

Enter the CLI of the quorum server, go to any directory, run the vi /etc/sysconfig/
iptables command in any directory to open the firewall configuration file and add the
port ID to 30002.
NOTE
If you want to enable other ports for the firewall, add the port IDs to the -I INPUT –p XXX –-
dport=XXX –j ACCEPT configuration item. For example, -I INPUT -p tcp --dport=22 -j
ACCEPT.
XXX@Linux:~# vi /etc/sysconfig/iptables
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-I INPUT -p tcp --dport=30002 -j ACCEPT

COMMIT
NOTE
– If /etc/sysconfig/iptables does not exist or is empty, write all the preceding content into the
configuration file.
– If /etc/sysconfig/iptables has content, add -I INPUT –p tcp –-dport=30002 –j ACCEPT at the
beginning of COMMIT.
– If you want to enable other ports for the firewall, add the port IDs to the -I INPUT –p XXX –-
dport=XXX –j ACCEPT configuration item. For example, if you want to enable port 22, type -I
INPUT –p tcp –-dport=22 –j ACCEPT.
– If a virtual machine (VM) is used to deploy the arbitration software, enable the firewall port of the
physical machine where the VM is deployed.
Enter the CLI of the quorum server, go to any directory, run the service iptables restart
command in any directory to restart the firewall. Then run the iptables -L command to
check whether the firewall configuration takes effect. If the ACCEPT tcp -- anywhere
anywhere tcp dpt:pago-services2 information is displayed in the command output, the
firewall configuration takes effect.
XXX@Linux:~# iptables -L
.
.
.
.
.
.
ACCEPT tcp -- anywhere anywhere tcp dpt:pago-services2
.
.
.
.
.
.

OceanStor V3 Series

start main!
admin:/>
NOTE
NOTE
firewall.

----- ------------ ------------------
1 192.168.6.31 30002
2 192.168.7.31 30002

----- ------------ --------- -------- --------- -----
NOTE
private key.

OceanStor V3 Series
NOTE

NOTICE
storage system SN.
System Name : XXXXXX

Total Capacity : X.XXXTB
Location :
Product Model : XXXXX
Product Version : VX00R00XC00
High Water Level(%) : XX
Low Water Level(%) : XX
WWN : XXXXXXXXXXXXXXX
Time : XXXX-XX-XX/15:11:15 UTC+08:00

OceanStor V3 Series
----End
4.4.3 Configuring the Arbitration Software (Ubuntu)

This section describes how to configure the arbitration software in Ubuntu.
Prerequisites
Procedure
NOTE
– When deploying the arbitration software using VMs, you need to create virtual
network adapters and switches for VMs. In this example, arbitration software is
deployed on VMs, and two ports of the quorum server are not bonded. Figure 4-4
and Table 4-6 show configuration requirements.

OceanStor V3 Series

Requirement

pair. mask: 192.168.6.31/255.255.255.0

pair. mask: 192.168.7.31/255.255.255.0

Port
Arbitration 192.168.6.31 255.255.255.0

port 1
Arbitration 192.168.7.31 255.255.255.0

port 2
Run the sudo vi /etc/network/interfaces command to open the configuration file of the
network adapter used by the quorum server for arbitration. The following uses network
adapters eth1 and eth2 for arbitration ports as an example to describe how to modify the
file. Modify the address and netmask in this file and then save the file.
NOTICE
The start mode must be set to auto.
XXX@ubuntu:~$sudo vi /etc/network/interfaces
auto eth1 //The parameter must be set to auto.
iface eth1 inet static
address 192.168.6.31
gateway 192.168.6.1
netmask 255.255.255.0
auto eth2 //The parameter must be set to auto.

iface eth2 inet static
address 192.168.7.31

OceanStor V3 Series
gateway 192.168.7.1
netmask 255.255.255.0
Enter the CLI of the quorum server, go to any directory, run sudo ifdown eth1 and sudo
ifup eth1 command in any directory to restart the network adapter. Then run the ifconfig
eth1 command to check whether the configuration takes effect. If the IP address that you
configure is displayed in the command output, the configuration takes effect.
XXX@ubuntu:~$ifconfig eth1
Enter the CLI of the quorum server, go to any directory, run sudo ifdown eth2 and sudo
ifup eth2 command in any directory to restart the network adapter. Then run the ifconfig
eth2 command to check whether the configuration takes effect. If the IP address that you
configure is displayed in the command output, the configuration takes effect.
XXX@ubuntu:~$ifconfig eth2

Enter the CLI of the quorum server, go to any directory, (take ufw as example), run the
sudo ufw allow 30002/tcp command in any directory to add the port to 30002.
NOTE
– If you want to enable other ports for the firewall, run the sudo ufw allow XXX/XXX
command to add the port IDs to the firewall. For example, if you want to enable port 22, run
the sudo ufw allow 22/tcp command.
– If a virtual machine (VM) is used to deploy the arbitration software, enable the firewall port of
the physical machine where the VM is deployed.
XXX@ubuntu:~$sudo ufw allow 30002/tcp
Rule added
Rule added (v6)
Enter the CLI of the quorum server, go to any directory, run the sudo ufw status
command to check whether the firewall configuration takes effect. If the 30002/tcp
ALLOW Anywhere and 30002/tcp(v6) ALLOW Anywhere (v6) information is
displayed in the command output, the firewall configuration takes effect.
XXX@ubuntu:~$sudo ufw status
To Action From
-- ------ ----
.
.
.
.
30002/tcp ALLOW Anywhere

OceanStor V3 Series
.
.
.
30002/tcp (v6) ALLOW Anywhere (v6)

start main!
admin:/>
NOTE
NOTE
firewall.

----- ------------ ------------------
1 192.168.6.31 30002
2 192.168.7.31 30002

----- ------------ --------- -------- --------- -----
NOTE
private key.

OceanStor V3 Series
NOTE

NOTICE
storage system SN.
System Name : reppub_10.103.20.176

Total Capacity : 2.025TB
Location :
Product Model : S5800T
Product Version : V200R003C00
High Water Level(%) : 80
Low Water Level(%) : 20
WWN : 21000022a1072506
Time : 2015-06-27/15:11:15 UTC+08:00

OceanStor V3 Series
----End
4.5 Configuring Basic Storage Services

This section describes how to configure basic storage services for the HyperMetro.
Context
This document describes how to configure basic storage services for the HyperMetro. For
details about configuration process, see OceanStor V3 Series V300R006 Basic Storage
Service Guide for Block.
Table 4-8 describes each step of the configuration process.

NOTE
You are advised to use the same configuration when configuring basic storage services on the local storage
array and remote storage array.
Table 4-8 Storage space configuration procedures
Configuration Operation Location

Procedure
Create a disk This operation is performed on both the local and the peer remote
domain. storage systems.
NOTE
You are advised to use the same configuration when creating disk domains on
the local storage array and remote storage array.
Create a storage This operation is performed on both the local and the peer remote
pool. storage systems.
NOTE
You are advised to use the same configuration when creating storage pools on
the local storage array and remote storage array.
Create a LUN. This operation is performed on both the local and the peer remote
storage systems.
NOTICE
l It is recommended that the local LUN and remote LUN have the same
attributes such as the owning controller, capacity, and block size.
l In the VMware ESXi 6.5 GA version, the host LUN ID of the two LUNs
in a HyperMetro pair must be the same when the LUNs map to the same
host. You can run the show host lun host_id=xx command on the storage
array to query information about LUNs mapping to a host. (xx indicates
the host ID).
Create a LUN This operation is performed on both the local and the peer remote
group. storage systems.

OceanStor V3 Series
Configuration Operation Location

Procedure
Configure host This operation is performed on both the local and the peer remote
connectivity. storage systems.
Create a host. This operation is performed on both the local and the peer remote
storage systems.
Create a host group. This operation is performed on both the local and the peer remote
storage systems.
(Optional) This operation is performed on both the local and the peer remote
Configure storage systems.
Challenge
Handshake
Authentication
Protocol (CHAP)
authentication
(iSCSI connection).
(Optional) Create a This operation is performed on both the local and the peer remote
port group. storage systems.
Create a mapping This operation is performed on both the local and the peer remote
view. storage systems.
NOTICE
Both the local and remote LUNs in a HyperMetro pair must be mapped to a
host. However, before creating a HyperMetro pair, ensure that the remote
LUN to be added to the HyperMetro pair is not mapped to a host. Otherwise,
the HyperMetro pair may fail to be created. After the HyperMetro pair is
created and the Pair Running Status becomes Normal, map the remote
LUN to the host.
NOTE
When a large number of HyperMetro LUNs are created, to ensure that all
HyperMetro LUNs are mapped to the host, you can run the show lun
hyper_metro_pair lun_mapped=no command on the storage devices to
view the HyperMetro LUNs that are not mapped to the host.
Enable an This operation is performed on the host. After creating the

application server HyperMetro pair, enable an application server to use storage space.
to use storage NOTE
space. When LUNs provide storage space for SQL Server databases, you can adjust
relevant parameters to reduce the I/O latency and achieve the optimal
performance. For details, see 6.7 In the SQL Server database scenario,
how can I adjust parameters to reduce the I/O latency and achieve the
optimal performance?.
4.6 Creating SAN HyperMetro

This chapter describes how to create a SAN HyperMetro.

OceanStor V3 Series
4.6.1 Checking the License File

Before configuring HyperMetro, ensure that the license file in use grants the permission to use
HyperMetro.
Prerequisites
A license file that contains the HyperMetro license information has been imported into the
storage system and activated.
Context
This operation is performed on both the local and the peer remote storage systems.
On the DeviceManager interface, HyperMetro is displayed in Feature of HyperMetro (for

LUN).
In a scenario where both SAN HyperMetro and NAS HyperMetro are required, you can
purchase the license for both file system and LUN. In the license file, HyperMetro License
(for FS&LUN) is displayed.
Precautions
The capacity of the HyperMetro license for 18500 V3&18800 V3 storage systems must be
equal to or larger than the total capacity of LUNs equipped with this feature. However, if the
total capacity of the LUNs in a storage pool equipped with this feature is larger than that of
the storage pool, use the capacity of the storage pool to calculate the capacity required for the
HyperMetro license. The following is a capacity calculation example.
Storage LUN Capacity Capacity of the License Capacity Total
Pool Name (Total Storage Pool To You Must Apply License
Capacity of Which LUNs for the Storage Capacity
Thin and Belong Pool You
Thick LUNs) Must
Apply
StoragePool 5 GB 10 GB 5 GB ≥25 GB
001
StoragePool 10 GB 10 GB 10 GB
002
StoragePool 20 GB 10 GB 10 GB
003
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > License Management.
Step 3 Check the active license files.

OceanStor V3 Series
1. In the navigation tree on the left, choose Active License.

2. In the middle information pane, verify the information about active license files.
----End
Follow-up Procedure
If a suitable HyperMetro license is unavailable, apply for and import a license file as
instructed in the Installation Guide of the corresponding product model.
4.6.2 Adding a Remote Device

This operation enables you to establish a logical connection between a local storage device
and a remote storage device for data transfer between the two devices.
Prerequisites
l A local storage device is normally connected to a remote storage device.
l To add remote devices when firewalls are configured, enable ports 36061 and 3260.
Context
This operation is only performed on the local storage system.
The link between a local storage device and a remote storage device can be a Fibre Channel
link or an iSCSI link.
NOTE
l On a Fibre Channel network, clear zone configurations of ports connecting to the storage system
from the switch before adding the remote device. You are advised to allocate two ports in one zone
to prevent excessive remote links because too many ports exist in one zone.
l A maximum of eight available links can be identified between a controller and the remote device,
and at most eight of these links can be used for replication when you add a remote device.
Procedure
Step 2 Choose Data Protection > HyperMetro.
Step 3 Click Add Remote Device.

The Add Remote Device Wizard dialog box is displayed.
NOTE
When a large number of remote storage devices exist, you can select desired remote devices through
their WWNs. Click Home on DeviceManager. In the Basic Information area, you can view WWN.
Step 4 Set up the connection to the remote device.

OceanStor V3 Series
NOTICE
l If Running Status of an added link is Invalid, delete and add the link again.
l To ensure data transfer security among storage systems, you are advised to use a device
such as a security gateway to encrypt links to prevent information leakage.
l If the version of the local device is different from that of the remote device, you need to
add a remote device on the newer version device. Otherwise the operation may fail.
l In HyperMetro scenarios, the two storage arrays need redundant links. Therefore, add
two Fibre Channel links or iSCSI links.
l Add an iSCSI Link

a. Set Link Type to iSCSI.
b. Set parameters for the iSCSI link. Table 4-9 lists related parameters.
Table 4-9 iSCSI link parameters
Parameter Description Setting
Immediate Data The immediate data [Example]

function can speed up Enable
data transfer in the
scenario where iSCSI
replication links transfer
service data between
storage arrays.
Controller Name of the local [Example]

storage device's XXX0.A
controller connected to
the remote storage
device.
Local Port Local storage device's [Example]

Ethernet port connected XXX0.A0.P0
to the remote storage
device.
NOTE
This host port cannot be
used for Ethernet port
bonding. Otherwise, the
HyperMetro service fails.
IP Address IP address of the [Example]

Ethernet port on the 192.168.26.12
remote storage device.
NOTE
This host port cannot be
used for Ethernet port
bonding. Otherwise, the
HyperMetro service fails.

OceanStor V3 Series
Username The user name of the [Value]

machine-machine user. mm_user
Password The password of the [Value]

machine-machine user. mm_user@storage
TCP/IP Port Ethernet port number on [Example]

the remote storage 3260
device.
l Add an FC Link
a. Set Link Type to FC.
b. In the Fibre Channel link list, select one or multiple Fibre Channel links.
c. Set parameters for the FC link. Table 4-10 lists related parameters.
Table 4-10 FC link parameters

Username The user name of the [Value]

machine-machine user. mm_user
Password The password of the [Value]

machine-machine user. mm_user@storage
Step 5 Click Next.

The information summary is displayed.
Step 6 Click Finish.

The Execution Result dialog box is displayed indicating that the operation succeeded.
Step 7 Click Close.
----End
Follow-up Procedure
In the HyperMetro, if the distance between the local and remote storage devices exceeds 25
km, you can run the following command to enable the fast write function to ensure link
transfer efficiency.
l FC link: By default, this function is disabled. This function is only enabled for 4-port 8
Gbit/s Fibre Channel links. You can run the change port fc fc_port_id=XXX
fast_write_enable=yes command to enable the fast write function. To obtain the value
of fc_port_id, run show port general. The function needs to be enabled on both the
local and remote storage system. Run the show port general port_id=XXX command.
When the status of Fast Write Enable in the output is Yes, this function is successfully
enabled.

OceanStor V3 Series
l iSCSI link: By default, this function is enabled. You are advised to enable this function.
You can run the change remote_device link link_type=iSCSI link_id=XXX
fast_write_enable=no command to disable the fast write function. To obtain the value of
link_id, run show remote_device link. The function needs to be enabled only on the
local storage system. You can run the show remote_device link link_type=iSCSI
link_id=XXX command to query the status of this function. When the status of Fast
Write Enable in the output is Yes, this function is successfully enabled.
For details, see the Command Reference of the corresponding product model.
4.6.3 Creating a Quorum Server

Through this operation, you can create a third-party quorum server for HyperMetro domains.
When the communication between storage devices in a HyperMetro pair becomes abnormal,
the quorum server decides which site continues to provide services, thereby greatly improving
service continuity.
Prerequisites
To enable quorum links to be added to storage arrays successfully, ensure the following items
before creating a quorum server.
l The system time of the storage arrays and quorum server is correct. The validity period
of the default arbitration certificate is 10 years (start from September 2015). Ensure the
system time of the quorum server is correct so that the default arbitration certificate is
valid.
l The service IP addresses of the quorum server are correctly configured and correct
firewall ports (30002) are enabled.
l The white list of the quorum server is configured correctly. (You do not need to check
this item if the default security policy is used.)
l Service IP addresses have been configured for the service ports that are used to connect
storage arrays and the quorum server. In addition, the service IP address of the storage
arrays and quorum server can ping through with each other. For details about how to
configure service IP addresses for storage arrays, see OceanStor V3 Series V300R006
Basic Storage Service Guide for Block. After configuring the service IP addresses, query
and record the IP addresses' ports. Then perform the operation in step 7 to select a port.
Perform the following operation to query the ports: On DeviceManager management
page, choose Provisioning > Port > Ethernet Ports.
Context
l To ensure the reliability between quorum servers and storage devices, you are advised to
add at least one link between each controller of storage devices and a quorum server.
l This operation is performed on both the local and the peer remote storage systems.
l The quorum site supports two quorum servers for V300R006C10 and later versions. In
following operations, the first added quorum server becomes the active quorum server
and the other becomes the standby quorum server.
Procedure

OceanStor V3 Series
Step 2 Choose Data Protection > HyperMetro > Quorum Server.
Step 3 Click Create.

The Create Quorum Server dialog box is displayed.
Step 4 Set Name and Description of the quorum server and click Next.
NOTE
l The name contains 1 to 31 characters.

l The name can contain only letters, digits, underscores (_), periods (.), and hyphens (-).
Step 5 Set the properties of the quorum server and click Next.
Table 4-11 lists related configuration parameters.
Table 4-11 Quorum server parameters

Parameter Description Example Value
Active IP Address Primary IP address of a [Example]

quorum server. 192.168.0.8
Active Port Primary port ID of a quorum [Value Range]

server. The default port ID is The value ranges from 1 to
30002. 65535.
[Example]
30002
Standby IP Address Standby IP address of a [Example]

Standby Port Standby port ID of a [Value Range]

quorum server. The default The value ranges from 1 to
port ID is 30002. 65535.
[Example]
30002
Step 6 Optional: If you select Configure Later, you can configure the links between the quorum
server and controllers of storage devices later.
NOTE
If no quorum server link is configured, the quorum server cannot communicate with either of storage devices.
When the communication is abnormal between the two storage devices, services are provided by the preferred
site.
If you want to add the quorum server subsequently, modify the HyperMetro domain to add it.
Step 7 Select Controller and Port of storage devices to be connected and click Add. Select Port
Type of storage devices to be connected, configure corresponding settings, and click Add.
l If the port type is Host port, select Controller and Port.
l If the port type is Management port, select Port. (To use a management network port as
an arbitration port, the storage system version must be V300R006C10 or later.)

OceanStor V3 Series
NOTE
To ensure the reliability between quorum servers and storage devices, you are advised to add at least one link
between each controller of storage devices and a quorum server.
Step 8 Click Next.

NOTE
The Summary page is displayed. Confirm the newly added link information and click Finish.
Step 9 Optional: If two quorum servers are configured, perform Step 3 to Step 8 to add another
quorum server.
Step 10 Log in to the remote storage device, execute the steps above to configure quorum server for
the remote storage device.
----End
Follow-up Procedure
By default, a quorum server does not have policy routes. It can only receive and send data via
one IP port although it has two IP ports on the same network segment. As a result, after the
port in use goes down, the other port cannot take over services. Log in to the quorum server
and configure routing policies for it. For details, see Active and Standby IP Ports Are
Configured on the Quorum Server. After the Port in Use Is Down, the Quorum Server
Goes Offline. Why?
4.6.4 Creating a HyperMetro Domain

After configuring a remote device and a quorum server, you need to create a HyperMetro
domain for the remote and local devices, and the quorum server. When creating a HyperMetro
domain, you determine the relationships among the local device, remote device, and quorum
server in the domain.
Prerequisites
l In V300R006C00, a HyperMetro domain can have only one quorum server. In
V300R006C10 and later versions, a HyperMetro domain can have two quorum servers.
l If you need to configure a quorum server for the HyperMetro domain, you must add
quorum server for both local and remote storage devices.
NOTE
Log in to the quorum server. In the CLI of the quorum server, run command qsadmin to open the
arbitration software. Then, run command show server_ip to view the status of the local and
remote storage devices. If they are both in the Established state, the quorum server has been
added successfully.
Context
l A HyperMetro Domain supports one quorum server at most.
l This operation is only performed on the local storage system.
Procedure

OceanStor V3 Series
Step 2 Choose Data Protection > HyperMetro > HyperMetro Domain.

The Create HyperMetro Domain wizard is displayed.
Step 4 Set Name and Description of the HyperMetro domain and click Next.
NOTE
l The name contains 1 to 31 characters.

l The name can contain only letters, digits, underscores (_), periods (.), and hyphens (-) and it must start
with a letter or digit.
Step 5 In the Remote Device area, select a remote device that you want to add to the HyperMetro
domain and click Next.
NOTE
Click Add Remote Device to add a remote device in the dialog box that is displayed.
Step 6 In the Quorum server area, select a quorum server that you want to add to the HyperMetro
domain and click Next.
NOTE
If you select Configure Later, you can add the quorum server to the HyperMetro domain later. If a fault
occurs, the local and remote devices in the HyperMetro domain cannot use the arbitration mechanism
provided by the quorum server to determine which site can continue to provide services. By default, the
device in Prior Service Site provides services.
Step 7 Click Next.

The information summary is displayed.
Step 8 Click Finish.
Step 9 Click Close.
----End
4.6.5 Creating a HyperMetro Pair

After specifying a HyperMetro domain (including local and remote devices and a quorum
server), device resources at two storage arrays, and data synchronization properties, you can
create HyperMetro relationships for devices at the two storage arrays. After the HyperMetro
relationships are established, the quorum server and preferred site mechanism determine
which site continues to provide services if a disaster occurs.
Prerequisites
l The local and remote devices work normally and correctly communicate with each other.
l These devices must support the HyperMetro feature.
l The remote LUN of HyperMetro pair is not mapped to host.
Context
l After HyperMetro pair is created, the WWN of the remote LUN is changed to the WWN
of the local LUN.

OceanStor V3 Series
l This operation is only performed on the local storage system.
Procedure
Step 2 Choose Data Protection > HyperMetro > HyperMetro Pair.
Step 3 Select the HyperMetro Pair tab.

The HyperMetro Pair management page is displayed.
The Create HyperMetro Pair Wizard dialog box is displayed.
Step 5 Select HyperMetro Domain, Resource Type and Host Multipathing Software for the
HyperMetro and click Next.
Step 6 In Available Local Resources and Available Remote Resources, select local and remote
LUNs for which you want to configure the HyperMetro feature and click Add to Pairs.
NOTE
Local and remote LUNs must have the same number of sectors.
Step 7 Click Next.
Step 8 Set the data synchronization properties for the HyperMetro. Table 4-12 describes related
parameters.

OceanStor V3 Series
Table 4-12 HyperMetro parameters

Speed Data replication speed of a [Value range]

HyperMetro. Possible values are Low,
l Low: When the speed is Medium, High, and
set to low, remote Highest.
replication will take a NOTE
long time. This value is If the LUN for which you want
applicable to scenarios to implement HyperMetro is
where the service load is carrying host services and it is
difficult to determine when the
heavy. The speed is
system is busy or idle, you are
normally from 0 to 5 advised to set the parameter to
MB/s. Medium to minimize the
l Medium: When the impact on host services.
speed is set to medium, [Default value]
remote replication will Medium
take relatively short
period. This value is
applicable to scenarios
where the service load is
heavy. The speed is
normally from 10 to 20
MB/s.
l High: When the speed is
set to high, remote
replication will take a
short period. This value
is applicable to scenarios
relatively light. The
speed is normally from
50 to 70 MB/s.
l Highest: When the speed
is set to highest, remote
replication will be
complete in the shortest
light. The speed is
normally above 100
MB/s.

OceanStor V3 Series
Recovery Policy A recovery policy [Value range]

determines whether the Possible values are
system automatically Automatic and Manual.
synchronizes data after a
HyperMetro fault is [Default value]
rectified. Automatic
l Automatic: The system
automatically
synchronizes data.
l Manual: The
synchronization
operation must be
performed manually.
Initial Synchronization Initial synchronization [Value range]

method for data at local and l Local and remote data is
remote ends. inconsistent. After the
creation is complete,
manually synchronize
data.
l Data at the local and
remote ends is
consistent.
Synchronization is not
required after the
creation is complete.
l Local and remote data is
inconsistent. After the
creation is complete, data
is automatically
synchronized.
[Example]
Local and remote data is
inconsistent. After the
creation is complete, data is
automatically synchronized.
Step 9 Click Next.
Step 10 Optional: Add the HyperMetro pair into consistency group.

NOTE
The Running Status of the consistency group you want to pause must be Paused.
1. Choose Select a consistency group and add HyperMetro pairs to it.
2. Choose the consistency group you want to add the HyperMetro pair, or click Create
HyperMetro Consistency Group. Table 4-13 describes related parameters.

OceanStor V3 Series
Table 4-13 Consistency group parameters

Name The name of the HyperMetroGroup_001

HyperMetro consistency
group.
Description The description of the —

group.

OceanStor V3 Series

– Low: When the speed Medium, High, and
is set to low, remote Highest.
replication will take a NOTE
long time. This value is If the LUN for which you
applicable to scenarios want to implement
where the service load HyperMetro is carrying host
services and it is difficult to
is heavy. The speed is
determine when the system
normally from 0 to 5 is busy or idle, you are
MB/s. advised to set the parameter
– Medium: When the to Medium to minimize the
impact on host services.
speed is set to medium,
remote replication will
take relatively short
where the service load
is heavy. The speed is
MB/s.
– High: When the speed
is set to high, remote
replication will take a
short period. This value
is applicable to
scenarios where the
service load is
relatively light. The
speed is normally from
50 to 70 MB/s.
– Highest: When the
speed is set to highest,
remote replication will
be complete in the
shortest period. This
value is applicable to
scenarios where the
service load is light.
The speed is normally
above 100 MB/s.

OceanStor V3 Series

HyperMetro fault is [Default value]
rectified. Automatic
– Automatic: The
system automatically
synchronizes data.
– Manual: The
synchronization
operation must be
performed manually.
3. Click OK.
4. Click Close.
Step 11 Click Next.
The Information Summary page is displayed.
Step 12 Confirm the newly created HyperMetro information and click Finish.
The security alert dialog box is displayed.
Step 13 Select I have read and understand the consequences associated with performing this
operation. and click OK.
----End
Follow-up Procedure
Both the local and remote LUNs in a HyperMetro pair must be mapped to a host. However,
before creating a HyperMetro pair, ensure that the remote LUN to be added to the
HyperMetro pair is not mapped to a host. Otherwise, the HyperMetro pair may fail to be
created. After the HyperMetro pair is created and the Pair Running Status becomes Normal,
map the remote LUN to the host. For details about how to scan for LUNs, see the UltraPath
User Guide specific to your host operating system.
4.6.6 Creating a HyperMetro Consistency Group

If an application or one type of services requires multiple HyperMetro LUNs and a preferable
service site needs to be determined by the system or quorum server upon faults, you need to
add owning HyperMetro LUNs of the application and services to a same HyperMetro
consistency group for unified maintenance.
Prerequisites
l The HyperMetro pairs in a HyperMetro consistency group must belong to the same
HyperMetro domain.
l HyperMetro pairs in a HyperMetro consistency group must have the same Data
Synchronization Direction and Pair Running Status as the HyperMetro consistency
group.

OceanStor V3 Series
l Before creating a HyperMetro consistency group, stop the HyperMetro pair to be added
to the consistency group.
Context
This operation is only performed on the local storage system.
Procedure
Step 2 Choose Data Protection > HyperMetro > HyperMetro Pair > HyperMetro
Consistency Group.
The Create HyperMetro Consistency Group Wizard page is displayed.
Step 4 Set the name, description and HyperMetro domain of the HyperMetro consistency group.
Table 4-14 describes related parameters.
Table 4-14 HyperMetro consistency group parameters

Name The name of the HyperMetro HyperMetroGroup_001

consistency group.
Description The description of the —

group.
HyperMetro Domain HyperMetro domain to which HyperMetroDomain_001

the HyperMetro consistency
group belongs. The
HyperMetro pair in
HyperMetro consistency group
must belong to the same
HyperMetro domain.
NOTE
Click Create to create a
HyperMetro domain in the dialog
box that is displayed.
Step 5 Click Next.
Step 6 Set the properties for the HyperMetro consistency group. Table 4-15 describes related
parameters.

OceanStor V3 Series
Table 4-15 HyperMetro consistency group properties


l Low: When the speed is set Medium, High, and Highest.
to low, remote replication NOTE
will take a long time. This If the LUN for which you want to
value is applicable to implement HyperMetro is
scenarios where the service carrying host services and it is
difficult to determine when the
load is heavy. The speed is
system is busy or idle, you are
normally from 0 to 5 MB/s. advised to set the parameter to
l Medium: When the speed Medium to minimize the impact
is set to medium, remote on host services.
replication will take [Default value]
relatively short period. This Medium
scenarios where the service
load is heavy. The speed is
MB/s.
l High: When the speed is
set to high, remote
replication will take a short
relatively light. The speed
is normally from 50 to 70
MB/s.
l Highest: When the speed is
set to highest, remote
replication will be complete
in the shortest period. This
scenarios where the service
load is light. The speed is
normally above 100 MB/s.

OceanStor V3 Series
Recovery Policy A recovery policy determines [Value range]

whether the system Possible values are Automatic
automatically synchronizes and Manual.
data after a HyperMetro fault
is rectified. [Default value]
l Automatic: The system Automatic

automatically synchronizes
data.
l Manual: The
synchronization operation
must be performed
manually.
Step 7 Click Next.
Step 8 In Available HyperMetro Pairs select the HyperMetro pair, and click to add the
selected HyperMetro pair into Selected HyperMetro Pairs area, and click Next.
Step 9 In Summary page, confirm the information and click Finish.
Step 10 Click Close.
----End
4.7 Configure a Multipathing Policy for Host

This section describes how to configure the Multipathing software.
Context
Multipathing software must be installed for the HyperMetro solution. You can use either
Huawei UltraPath or third-party multipathing software.
l In terms of multipathing, UltraPath is recommended for HyperMetro. UltraPath can
identify host locations so that hosts can access the nearest storage array, reducing cross-
site accesses and latency while improving access efficiency and storage performance.
NOTE
For details on how to configure UltraPath, see Configuring an UltraPath Policy for Host.
l If the customer needs to use third-party multipathing software on the application server,
the function of Uses third-party multipath software for initiators must be enabled on
Huawei storage.
NOTE
For details on how to configure third-party multipathing software, see Configuring a Third-party
Multipathing Policy for Host.

OceanStor V3 Series
4.7.1 Configuring a UltraPath Policy for Host

This section describes how to configure the UltraPath software. For HyperMetro, the
UltraPath software is configured to improve the I/O processing efficiency and reduce the
access latency.
Context
In UltraPath, the local storage array is granted with the prior read and write permission. The
local storage array is preferentially used to process host services. If the local storage array
malfunctions, the remote storage array will be used. In this way, service response efficiency is
improved and access latency is reduced.
UltraPath must be configured on all application servers.
When configuring UltraPath, ensure that Uses third-party multipath software is disabled as
it is not needed.
NOTE
For details about how to disable Uses third-party multipath software, see section Configuring a Third-
party Multipathing Policy for Host.
Procedure
Step 1 Set the HyperMetro working mode.
The commands for setting the HyperMetro working mode vary with OSs on application
servers.
l For Linux, Windows, AIX, and Solaris OSs,
a. Log in to the application server.
b. Log in to the CLI of OceanStor UltraPath.
n In Linux OSs, run upadmin to log in to the CLI of OceanStor UltraPath.
n In Windows, AIX, and Solaris OSs, run upadm to log in to the CLI of
OceanStor UltraPath.
c. Run set hypermetro workingmode={ priority | balance } primary_array_id=ID
[vlun_id={ ID | ID1,ID2... | ID1-ID2 } ]. Table 4-16 describes the key parameters
in the command.
Table 4-16 Parameter description
Keyword and Description Default Value

Parameter
workingmode={ priorit Used to specify the priority

y | balance } HyperMetro working priority is
mode. recommended. balance
n priority: preferred is applicable to scenarios
storage array mode where the two active-
n balance: load active data centers are in
balancing mode the same building.

OceanStor V3 Series

Parameter
primary_array_id=ID ID of the preferred None

storage array. The ID is NOTE
allocated by UltraPath. Mapping relationship
The storage array in the between application hosts
data center in which the and storage arrays:
application hosts reside n If the preferred storage
is selected. array is configured for
all application hosts in
Run the command to data center A, select
obtain the ID of the storage array A.
storage array: n If the preferred storage
n Linux: upadmin array is configured for
show array
data center B, select
n Windows/AIX/ storage array B.
Solaris: upadm show
array
NOTE
n When workingmode
is set to priority, the
value of the parameter
indicates the storage
array to which I/Os are
preferentially
delivered.
n When workingmode
is set to balance, the
value of the parameter
array where the first
slice section resides.
vlun_id={ ID | ID of a virtual None

ID1,ID2... | ID1-ID2 } HyperMetro LUN. The
ID is allocated by
UltraPath.
Run show vlun
type=hypermetro to
obtain the ID of a virtual
HyperMetro LUN.
Instruction for Use

This command is used to set the HyperMetro working mode of storage arrays and
virtual LUNs. For example:
n To set the HyperMetro working mode of an array to priority and specify the
ID of the preferred storage array to 0, run set hypermetro
workingmode=priority primary_array_id=0.
n To set the HyperMetro working mode of virtual LUN 0 to balance and specify
array 0 as the storage array where the first slice section resides, run set
hypermetro workingmode=balance primary_array_id=0 vlun_id=0.

OceanStor V3 Series
The HyperMetro working mode of a virtual LUN has a higher priority than that set
for all storage systems. To obtain better performance, you are advised to set the
HyperMetro working mode for arrays only.
l For vSphere OSs,
a. Log in to the application server.
b. Run esxcli upadm to log in to the CLI of OceanStor UltraPath.
c. Run set hypermetro workingmode -m mode -p primary_array_id [-l vlun_id].
Table 4-17 describes the key parameters in the command.
Table 4-17 Parameter description

Parameter
-m mode Used to specify the priority

HyperMetro working priority is
mode. recommended. balance
n priority: preferred is applicable to scenarios
storage array mode where the two active-
n balance: load active data centers are in
balancing mode the same building.
-p primary_array_id ID of the preferred None

storage array. The ID is NOTE
allocated by UltraPath. Mapping relationship
The storage array in the between application hosts
data center in which the and storage arrays:
application hosts reside n If the preferred storage
is selected. array is configured for
Run esxcli upadm show data center A, select
diskarray to obtain the storage array A.
ID of the storage array. n If the preferred storage
NOTE array is configured for
n When -m is set to
data center B, select
priority, the value of
storage array B.
the parameter
array to which I/Os are
preferentially
delivered.
n When -m is set to
balance, the value of
the parameter
array where the first
slice section resides.

OceanStor V3 Series

Parameter
[-l vlun_id] ID of a virtual None

HyperMetro LUN. The
ID is allocated by
UltraPath.
Run show vlun
type=hypermetro to
obtain the ID of a virtual
HyperMetro LUN.
Instruction for Use

This command is used to set the HyperMetro working mode of storage arrays and
virtual LUNs. For example:
n To set the HyperMetro working mode of an array to priority and specify the
ID of the preferred storage array to 0, run set hypermetro -m priority -p 0.
n To set the HyperMetro working mode of virtual LUN 0 to balance and specify
array 0 as the storage array where the first slice section resides, run set
hypermetro -m balance -p 0 -l 0.
The HyperMetro working mode of a virtual LUN has a higher priority than that set
for all storage systems. To obtain better performance, you are advised to set the
HyperMetro working mode for arrays only.
Step 2 Verify that UltraPath is configured correctly.
To check whether the configuration succeeds, run the command based on the operating
system type:
l Linux: upadmin show upconfig
l Windows/AIX/Solaris: upadm show upconfig
l vSphere: esxcli upadm show upconfig
NOTE
In Linux, add the upadmin prefix to a command to log in to the CLI of OceanStor UltraPath. In
Windows/AIX/Solaris, add the upadm prefix to a command to log in to the CLI of OceanStor UltraPath.
In vSphere, add the esxcli upadm prefix to a command to log in to the CLI of OceanStor UltraPath.
If the following command output is displayed, the configuration is successful. Otherwise,

execute configuration again. Figure 4-5 shows the command output in vSphere as an
example.
HyperMetro WorkingMode : read write within primary array

OceanStor V3 Series
Figure 4-5 Querying UltraPath configurations
Step 3 Optional: (for vSphere) Enable the APD to PDL function of ESXi hosts.
NOTE
The APD to PDL function is disabled by default.
l If ESXi hosts are in non-cluster deployment, skip this operation.
l If ESXi hosts are in cluster deployment and the storage system version is
V300R006C00SPC100 or later, skip this operation.
l If ESXi hosts are in cluster deployment and the storage system version is earlier than
V300R001C00SPC100, perform the following steps.
1. Run the esxcli upadm set apdtopdl —m on command.
2. Run the esxcli show upconfig command to view the configuration result. If APD to
PDL Mode is on, the APD to PDL function of ESXi hosts is enabled.
vSphere Security documentation for more information
~ # esxcli upadm show upconfig
===============================================================

OceanStor V3 Series
UltraPath Configuration
===============================================================
Basic Configuration
Working Mode : load balancing within controller
LoadBanlance Mode : min-queue-depth
Loadbanlance io threshold : 1
LUN Trespass : on
Advanced Configuration
Io Retry Times : 10
Io Retry Delay : 0
Faulty path check interval : 10
Idle path check interval : 60
Failback Delay Time : 600
Max io retry timeout : 1800
Path reliability configuration

Timeout degraded statistical time : 600
Timeout degraded threshold : 1
Timeout degraded path recovery time : 1800
Intermittent IO error degraded statistical time : 300
Min. I/Os for intermittent IO error degraded statistical : 5000
Intermittent IO error derraded threshold : 20
Intermittent IO error derraded path recovery time : 1800
Intermittent fault degraded statistical time : 1800
Intermittent fault degraded threshold : 3
Intermittent fault degraded path recovery time : 3600
High latency degraded statistical time : 300
High latency degraded threshold : 1000
High latency degraded path recovery time : 3600
APDtoPDL configuration
APD to PDL Mode : on
APD to PDL Timeout : 10
Step 4 Optional: (for Windows) Set the timeout period for an iSCSI initiator.
NOTE
l If you are using a Hyper-V cluster for HyperMetro's upper-layer environment and employing a 10GE
SAN, you must set the timeout period to 5 seconds for the iSCSI initiator of every host in the cluster.
l If the upper-layer environment of HyperMetro is not a Hyper-V cluster or does not use a 10GE SAN, skip
this step.
NOTE
Perform the following steps on each Hyper-V host.

1. Run the iscsiConfig set timeout 5 command.
2. Run the iscsiConfig set linkdowntime 5 command.
3. Restart the host.
----End
4.7.2 (Optional) Configuring a Third-party Multipathing Policy

for Host
This section introduces the operation procedure for configuring third-party multipathing
software.
Context
If the customer needs to use non-Huawei multipathing software (such as HP-UNIX NMP and
PV-Links, OpenVMS DM-MultiPath, and Oracle DM-MultiPath) on the application server,

OceanStor V3 Series
the function of using third-party multipathing software for initiators must be enabled on
Huawei storage.
This configuration must be performed on all initiators with HyperMetro enabled.
Procedure
Step 2 Choose Provisioning > Host.
Step 3 In the lower left corner, select the initiator used for HyperMetro, click Modify.
The Modify Initiator dialog box is displayed.
Step 4 Modify the properties of the initiator. Figure 4-6 lists related parameters.
NOTE
You need to restart the host after modifying the host initiator information for the configuration to take effect.

OceanStor V3 Series
Figure 4-6 Modify Initiator
For third-party multipathing policies of different operating systems, see the HyperMetro
Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software
to set the parameters in Figure 4-6.
Step 5 Confirm the modification of the initiator's properties.

1. Click OK.
The Success dialog box is displayed, indicating that the operation succeeded.
2. Click OK.
Step 6 Configuring third-party multipathing software policies of the hosts.

OceanStor V3 Series
This document only describes the configuration required for connecting Huawei storage to
third-party multipathing software. For details about third-party multipathing software
configuration for host, refer to the HyperMetro Configuration Guide for Huawei SAN
Storage Using OS Native Multipathing Software.
----End
4.8 Verifying the Configuration

After configured, you can view the status of the data on the local and remote storage systems
to check whether HyperMetro between the local and remote storage systems is successful.
After the HyperMetro configuration is complete, synchronize the HyperMetro pair. If Pair
Running Status is Normal after the synchronization, HyperMetro has been configured
successfully.
To verify the reliability and business continuity–related functions of HyperMetro, see section
Acceptance of HyperMetro in the Acceptance Test Guide of the corresponding product
model.

OceanStor V3 Series
HyperMetro Feature Guide for Block 5 Management
5 Management
About This Chapter
This chapter describes how to manage HyperMetro, HyperMetro domains, and the quorum
server.
5.1 Managing a HyperMetro Pair

After creating a HyperMetro, you may need to manage it due to service adjustment, disaster
recovery, data testing, or new data security requirements.
5.2 Managing HyperMetro Domains
By managing HyperMetro domains, you can modify quorum servers configured in
HyperMetro domains, and delete unnecessary HyperMetro domains as required.
5.3 Managing Quorum Servers
By managing quorum servers, you can create and delete quorum servers, and add links for
quorum servers.
5.4 Managing a HyperMetro Consistency Group
A consistency group consists of multiple HyperMetro pairs and manages all pairs in it
centrally.
5.5 Importing Certificates
When the storage system is communicating with an external device, you are advised to use
the certificate verification mode to improve service security. This chapter describes how to
generate and export a certificate signing request, and import and activate the signed
certificate.
5.1 Managing a HyperMetro Pair

After creating a HyperMetro, you may need to manage it due to service adjustment, disaster
recovery, data testing, or new data security requirements.

OceanStor V3 Series
5.1.1 Viewing HyperMetro Pair Information

Through this operation, you can view information about a HyperMetro including its basic
information and HyperMetro pair information, so that you can effectively monitor the
operating status of the HyperMetro.
Context
l On the HyperMetro management page, you can click Refresh to refresh HyperMetro
information.
l On the HyperMetro management page, click Keyword to search for keywords that are
required for HyperMetro information viewing.
l On the HyperMetro management page, click and select HyperMetro information that
you want to view.
Procedure
Step 3 Click the HyperMetro Pair tab.

Step 4 View the basic information about a HyperMetro. Table 5-1 describes related parameters.
Table 5-1 HyperMetro parameters

Local Resource Name Name of a local resource. None
Local Resource ID ID of a local resource. None
Remote Resource Name Name of a remote resource. None
Remote Resource ID ID of a remote resource. None
Pair ID A pair of IDs of local and None

remote resources in a
HyperMetro.
Pair Health Status Displays whether a pair of [Example]

local and remote resources Normal
in a HyperMetro are healthy.
Possible values can be
Normal and Fault.

OceanStor V3 Series
Pair Running Status Running status of a pair of [Example]

local and remote resources. Normal
Possible values can be
Normal, To be
synchronized, Paused,
Synchronizing, Force
Start, and Invalid.
Time Remaining for Time required for [Example]

Synchronization synchronization to 00:01:29
complete.
NOTE
Some product models and file
systems do not support this
parameter.
Link Status Status of a link connected to [Example]

a HyperMetro. Connected
Configuration Status Whether primary and [Example]

secondary site Normal
configurations are
synchronized. The value can
be Synchronizing, Normal,
or To Be Synchronized.
Because SAN HyperMetro
does not support
Configuration Status, -- is
displayed in the
Configuration Status
column.
HyperMetro Consistency Name of the owning [Example]

Group consistency group of the ConsistentGroup001
HyperMetro pair.
Local Resource Role Whether the local resource [Example]

is provided by the preferred Preferred
site.
Activation Status Activation status of site. The [Example]

value can be Active or Active
Passive.

OceanStor V3 Series
Recovery Policy A recovery policy supports [Example]

the following recovery Automatic
modes:
l Manual: If a
HyperMetro pair is in the
To be synchronized
state, management and
maintenance personnel
need to manually
perform the Synchronize
operation on the
HyperMetro pair based
on site requirements, so
that data synchronization
can be performed
between the local and
remote resources.
l Automatic: If a
HyperMetro pair is in the
Synchronizing state, the
system automatically and
incrementally
synchronizes differential
data from the primary
resource to the secondary
resource based on site
requirements.
Owning HyperMetro HyperMetro domain to [Example]

Domain which a HyperMetro domain01
belongs.
Local Resource Data Status Data status of a local [Example]

resource. Consistent
Remote Resource Data Data status of a remote [Example]

Status resource. Consistent
Local Resource Host Access Host access status of a local [Example]

Status resource. Read-Write
Remote Resource Host Host access status of a [Example]

Access Status remote resource. Read-Write

OceanStor V3 Series
Isolation Switch After the Isolation Switch [Example]

is turned on, the system will Disabled
suspend the HyperMetro
pair when the difference
between the write I/O
latency of the two storage
arrays is greater than the
isolation switch. The storage
array with the longer write
I/O latency will stop
providing services.
Isolation Threshold (ms) Write I/O latency difference [Value range]

between the host and The value must be an
HyperMetro storage arrays. integer from 10 to 30000.
The unit is millisecond.
Data Synchronization Data synchronization [Example]

Direction direction. Possible values Local to Remote
are Local to Remote and
Remote to Local.
Step 5 Click a HyperMetro whose information you want to view and view its HyperMetro pair
information in the lower area of the page. Table 5-2 describes the related parameters.
Table 5-2 HyperMetro pair parameters

Local Device Name of a local device. None
Local Resource Name of the local resource. None
Remote Resource Name of the remote None

resource.
Remote Device Name of a remote device. None

OceanStor V3 Series
Recovery Policy A recovery policy [Example]

determines whether the Automatic
HyperMetro fault is
rectified.
automatically
synchronizes data.
l Manual: The
synchronization
operation must be
performed manually.
Speed Speed of data [Example]

synchronization between the High
primary resource and
secondary resource. Possible
values are Low, Medium,
High, and Highest.
Start Time Time when data [Format]

synchronization for a YYYY-MM-DD hh:mm:ss
HyperMetro starts. UTC+hh:mm
[Example]
2014-05-30 16:51:32 UTC
+08:00
End Time Time when data [Format]

synchronization for a YYYY-MM-DD hh:mm:ss
HyperMetro ends. UTC+hh:mm
[Example]
2014-05-30 20:51:32 UTC
+08:00

providing services.
----End

OceanStor V3 Series
5.1.2 Modifying HyperMetro Pair Properties

Through this operation, you can modify the speed and recovery policy of a HyperMetro pair.
Prerequisites
A HyperMetro pair has been successfully configured for the storage system.
Procedure

Step 4 Select a HyperMetro pair whose properties you want to modify and click Properties.
The Properties of HyperMetro Pair dialog box is displayed.
Step 5 On the General tab page, you can view the link information about the HyperMetro pair. Click
the Synchronize Information tab to modify related parameters. Table 5-3 explains the
related parameters.

OceanStor V3 Series
Table 5-3 Parameters of HyperMetro properties


HyperMetro pair. Possible values are Low,
l Low: Data replication Medium, High, and
takes a relatively long Highest.
time. This value is
heavy. The speed ranges
from 0 MB/s to 5 MB/s.
l Medium: Data
replication takes a
relatively short time.
This value is applicable
to scenarios where the
service load is relatively
from 10 MB/s to 20
MB/s.
l High: Data replication
takes a short time. This
scenarios where the
light. The speed ranges
from 50 MB/s to 70
MB/s.
l Highest: Data replication
takes the shortest time.
service load is light. The
speed is greater than 100
MB/s.

HyperMetro fault is
rectified.
automatically
synchronizes data.
l Manual: The
synchronization
operation must be
performed manually.

OceanStor V3 Series

providing services.
Isolation Threshold (ms) Write I/O latency difference [Example]

between the host and 500
HyperMetro storage arrays.
----End
5.1.3 Synchronizing a HyperMetro Pair

Through this operation, ensuring data consistency between the storage arrays in two data
centers.
Prerequisites
The running status of a HyperMetro pair must be Paused, To be synchronized, or Force
Start (The connection of devices is normal).
Procedure

Step 4 Right-click a HyperMetro pair whose data you want to synchronize and choose Synchronize
from the short-cut menu.
Step 5 Confirm the operation to synchronize data in the HyperMetro pair.

1. Confirm the information in the dialog box and select I have read and understand the
consequences associated with performing this operation.. Then click OK.
2. Click OK.
----End

OceanStor V3 Series
5.1.4 Suspending a HyperMetro Pair

If you need to stop service for one site due to site failure or other reasons, select the
corresponding site of the HyperMetro pair. Pausing may cause the data inconsistency on both
sites.
Prerequisites
The Running Status of HyperMetro pair is Normal or Synchronizing (The connection of
devices is normal).
The HyperMetro pair is not added to the HyperMetro consistency group.
Procedure
Step 3 Right-click a HyperMetro pair that you want to suspend, and choose Pause from the shortcut
menu.
Step 4 Select Preferred or Non-Preferred site and click OK.

Step 5 Confirm the operation of pausing the HyperMetro pair.

1. Carefully read the contents of the dialog box, and click OK.
The Execution Result dialog box is displayed indicating that the operation successded.
2. Click Close.
NOTE
After the HyperMetro pair is suspended, data synchronization between the two storage arrays is also
suspended.
----End
5.1.5 Switching the Preferred Site for a HyperMetro

Through this operation, you can switch the preferred site for a HyperMetro. If a fault occurs,
services will be provided by the preferred site after the switchover.
Prerequisites
Running Status of a HyperMetro Pair must be Normal, Synchronizing, To be
synchronized, Force Start or Paused (The connection of devices is normal).
Procedure

OceanStor V3 Series
Step 3 Right-click a HyperMetro for which you want to switch the preferred site and choose Prior/
Non-prior Switchover from the short-cut menu.
Step 4 Confirm the operation to switch the preferred site.
2. Click OK.
----End
5.1.6 Forcibly Enabling a HyperMetro Pair

If a system fault occurs or the quorum server fails, you can forcibly enable the local or remote
site to allow it to continue to provide services.
Prerequisites
l The following requirements must be met before performing this operation: Link Status
and Running Status of the HyperMetro pair is Disconnected and Paused or To be
synchronized, respectively and the local resource data is unreadable and unwritable.
l To ensure data security, shut down the service host and disconnect it from the quorum
server before forcibly starting the HyperMetro pair. After the HyperMetro pair is started,
restart the service host and reconnect it to the quorum server.
l To ensure data consistency, check whether the host access status of the remote LUN is
Access denied before forcibly starting a HyperMetro pair.
On the remote storage system, run the show hyper_metro_pair general
pair_id=XXXXX command to query the host access status of the remote LUN.
admin:/>show hyper_metro_pair general pair_id=e4a8b61a08bd0000
ID : 3400a30d9a6c0000
Running Status : Paused
Link Status : Linkup
Domain ID : 3400a30d9a6c0100
Domain Name : hdm
Type : LUN
Size : 5.000GB
WWN : 63400a31000d9a6c00e4cb3000000000
IP(s) : --
Role : Non-preferred
Local ID : 0
Local Name : gtlun0000
Local Data Status : Consistent
Local Access Status : No Access
Remote ID : 0
Remote Name : gtlun0000
Remote Data Status : Consistent
Remote Access Status : Read and Write
Recovery Policy : Automatic
Sync Progress(%) : --
Sync Direction : Remote to Local
Sync Rate : Highest
Start Time : 2017-11-24/14:24:24 UTC+08:00
End Time : 2017-11-24/14:24:24
Consistency Group ID :
Consistency Group Name :
Isolation Switch : Close
Isolation Threshold(ms) : 1000

OceanStor V3 Series
Lock Mode : Optimistic Mode

Time Remaining for Synchronization : --
Write Secondary Timeout(s) : 30
– If Local Access Status is No Access, the host access status of the remote LUN is
Access denied. You can forcibly start the pair at the local end.
– If Local Access Status is Read and Write, the host can read and write the remote
LUN. You are not advised to forcibly start the pair. If forcible start is required,
contact Huawei technical support engineers.
Context
If HyperMetro works in Static Priority Mode or the HyperMetro service encounters
concurrent faults, the storage array at the preferred site malfunctions and cannot take over the
HyperMetro service. As a result, the HyperMetro service stops. Forcibly start the service at
the non-preferred site to restore the HyperMetro service.
When HyperMetro works in Static Priority Mode or the HyperMetro service encounters
concurrent faults, if one storage system can carry services, do not forcibly start the faulty
storage system to carry host services.
Procedure

Step 4 Right-click a HyperMetro pair that you want to enable forcibly and choose Force Start from
the short-cut menu.
Step 5 Confirm the operation to forcibly enable the HyperMetro pair.

2. Click OK.
----End
5.1.7 Deleting a HyperMetro Pair

If a HyperMetro is no longer needed, you can delete it.
Prerequisites
You can delete the HyperMetro pair only when its Pair Running Status is Paused, Force
Start or To be synchronized, and its secondary LUNs are not mapped.

OceanStor V3 Series
Procedure
Step 3 Select a HyperMetro that you want to delete and click Delete.
Step 4 Optional: Select Only delete the configuration information about the local device if the
HyperMetro pair fails or the remote device is disconnected. based on site requirements.
NOTE
If you do not select this option, you cannot delete the HyperMetro domain when the local device is
disconnected from the remote device.
Step 5 Optional: Select Stop the LUN service of this device based on site requirements.
NOTE
This operation must be performed on the local site or remote site (you are advised to set "Local Resource
Host Access Status" as an "Access denied" storage device). After this operation, the WWN of the LUN on the
storage device will change. Rescan the LUN on the host. If the LUN service is not stopped on both
HyperMetro sites, there is risk of data inconsistency.
Step 7 The Execution Result dialog box is displayed indicating that the operation succeeded.
NOTE
After deleting a HyperMetro pair, scan for storage resources on the host to ensure that the host can correctly
identify the storage resources mapped to it.
----End
5.1.8 Expanding the Capacity of a HyperMetro LUN

If LUN space is insufficient to store service data, you can expand the LUN capacity to meet
your service requirements.
Context
Before expanding the capacities of HyperMetro LUNs, you must delete the HyperMetro pair
where the LUNs reside. The following describes how to expand the capacities of HyperMetro
LUNs.
NOTE
In the following, the primary LUN is the HyperMetro LUN that provides services and the secondary LUN is
the HyperMetro LUN that stops providing services.
Procedure
l Offline expansion (In scenarios where the CPU usage and disk usage exceed 50%, the
HyperMetro replication bandwidth is insufficient, or the distance between data centers
exceeds 25 km).
a. Stop upper-layer services.

OceanStor V3 Series
b. Remove the primary and secondary LUNs from their owning LUN groups.
c. Pause the HyperMetro pair.
d. Delete the HyperMetro pair.
e. Expand the capacities of the primary and secondary LUNs.
NOTE
l After the expansion, capacities of the primary and secondary LUNs must be consistent.
l For details about how to expand a LUN, see the Capacity Expansion Guide of the
f. Create a HyperMetro pair.
NOTE
l Select The data at the local and remote ends is consistent. Synchronization is not
required after the creation is complete. option.
l The storage arrays on which a HyperMetro pair is created before or after capacity expansion
must be the same to ensure that the data synchronization directions of the HyperMetro pair are
the same. For example, if you create a HyperMetro pair on the storage array at the preferred
site before capacity expansion, create it again on the storage array at the preferred site after
capacity expansion.
g. Map the primary and secondary LUNs to the host.
h. On the host, scan for LUNs.
i. Restart services.
l Online expansion (In scenarios where the CPU usage and disk usage do not exceed 50%,
the HyperMetro replication bandwidth is sufficient, or the distance between data centers
is relatively short).
a. Pause the HyperMetro pair.
NOTE
In the Pause HyperMetro Pair dialog box, select Non-preferred.
b. Remove the secondary LUN from its owning LUN group.
c. Delete the HyperMetro pair.
d. Expand the capacities of the primary and secondary LUNs.
NOTE
l After the expansion, capacities of the primary and secondary LUNs must be consistent.
l For details about how to expand a LUN, see the Capacity Expansion Guide of the
e. On the storage array of the preferred site, create a HyperMetro pair.
NOTE
Select the Local and remote data is inconsistent. After the creation is complete, data is
automatically synchronized. option.
f. Map the secondary LUN to the host.
g. On the host, scan for LUNs.
----End
5.2 Managing HyperMetro Domains

By managing HyperMetro domains, you can modify quorum servers configured in
HyperMetro domains, and delete unnecessary HyperMetro domains as required.

OceanStor V3 Series
5.2.1 Viewing HyperMetro Domain Information

Through this operation, you can view remote device and quorum server information in a
HyperMetro domain, and monitor the operating status of the HyperMetro domain.
Prerequisites
A HyperMetro domain has been successfully configured for the storage system.
Procedure
Step 3 View the basic information about a HyperMetro domain. Table 5-4 explains the related
parameters.
Table 5-4 HyperMetro domain parameters
Parameter Description
ID ID of a HyperMetro domain.
Name Name of a HyperMetro domain.
Running Status Running status of a HyperMetro domain.
Remote Device Remote device in a HyperMetro domain.
Quorum Mode Quorum mode of a quorum server.

NOTE
The Quorum Mode is Static Priority if no
quorum server is created.
Quorum Server Quorum server in a HyperMetro domain.

NOTE
When two quorum servers are configured in
V300R006C10 and later versions, information
about both will be displayed.
----End
5.2.2 Modifying a HyperMetro Domain

When a quorum server in a HyperMetro domain has been modified, you can modify the
HyperMetro domain to modify the quorum server in the domain.
Prerequisites
A HyperMetro domain has been successfully configured for the storage system.

OceanStor V3 Series
Procedure
Step 3 Choose Properties. The Properties of HyperMetro Domain dialog box is displayed.
NOTE
Alternatively, you can right-click the HyperMetro domain and choose Properties.
Step 4 In Name and Description, change the name and description of the HyperMetro domain.
Step 5 In the Quorum Server area, modify the quorum server information.
NOTE
Click Add or Remove to add or remove the quorum server. In V300R006C00, a maximum of one quorum
servers can be added. In V300R006C10 and later versions, a maximum of two quorum servers can be added.
Step 6 Click OK.
----End
5.2.3 Deleting a HyperMetro Domain

If a HyperMetro domain is no longer needed, you can delete it.
Prerequisites
The related HyperMetro Pair has being deleted.
Procedure
Step 3 Select a HyperMetro domain that you want to delete and click Delete.
Step 4 Select Only delete the configuration information about the local device if the local device
is disconnected from the remote device based on site requirements.
NOTE
Step 6 The Execution Result dialog box is displayed indicating that the operation succeeded.
Step 7 Click Close.
----End

OceanStor V3 Series
5.3 Managing Quorum Servers

By managing quorum servers, you can create and delete quorum servers, and add links for
quorum servers.
5.3.1 Viewing Quorum Server Information

Through this operation, you can view information about existing quorum servers as well as
links of the quorum server.
Procedure
Step 3 View information about existing quorum servers. Table 5-5 describes related parameters.
Name Name of a quorum server.
Active IP Address Primary IP address of a quorum server.
Standby IP Address Standby IP address of a quorum server.
Running Status Running status of a quorum server.
Step 4 Select a quorum server and view its link information in the lower area. Table 5-6 describes
related parameters.
Table 5-6 Quorum server link parameters
Controller Controller of a local device connecting to a

quorum server.
Port Controller port of a local device connecting

to a quorum server.
IP Address The IP address of a quorum server.
Running Status Running status of a link.
----End

OceanStor V3 Series
5.3.2 Modifying Quorum Server Information

Through this operation, you can modify the properties of a quorum server and authentication
information for connecting the quorum server.
Procedure

Step 3 Select a quorum server that you want to modify and click Properties.
The Quorum Server Properties dialog box is displayed.
Step 4 On the General and Settings tab pages, modify the quorum server information. Table 5-7
explains the related parameters.

Name Name of a quorum server. [Example]

QuorumServer_001
Description Description of a quorum [Example]

server. None
Active IP Address Primary IP address of a [Example]

Primary Port Primary port ID of a quorum [Example]

server. The default port ID is 30002
30002.
NOTE
The port ID ranges from 1 to
65535.
Standby IP Address Standby IP address of a [Example]

quorum server. None
Standby Port Standby port ID of a [Example]

quorum server. None
NOTE
The port ID ranges from 1 to
65535.
Step 5 Click OK.
----End
5.3.3 Adding a Link

Through this operation, you can add a link for a quorum server.

OceanStor V3 Series
Procedure
Step 3 Select a quorum server for which you want to add a link and click Add in the Link area.
The Add Link dialog box is displayed.
Step 4 Select Controller and Port of storage devices to be connected and click Add.
NOTE
To ensure the reliability between quorum servers and storage systems, you are advised to add at least one link
between each controller of storage systems and a quorum server.
Step 5 Click OK.
----End
5.3.4 Removing a Link

Through this operation, you can remove a link configured for a quorum server.
Procedure
Step 3 Select a quorum server from which you want to remove a link and click Remove in the Link
area.
NOTE
To ensure the reliability between quorum servers and storage systems, you are advised to add at least one link
between each controller of storage systems and a quorum server.
Step 5 Click Close.
----End
5.3.5 Removing a Quorum Server

Through this operation, you can delete quorum servers that have been created.
Prerequisites
The quorum server has not been created to the Hypermetro domain.
Procedure

OceanStor V3 Series
Step 3 Select a quorum server that you want to remove and click Delete.
Step 5 Click Close.
----End
5.3.6 Uninstalling the Arbitration Software

This section describes how to uninstall the arbitration software.
Prerequisites
The arbitration software has been correctly installed, and the arbitration software package
exists. Only user root or the arbitration software management user can uninstall the
arbitration software.
NOTE
The arbitration software management user is the user created during the arbitration software installation. You
can run the ls -l /opt/quorum_server/bin/quorum_serverd command to query information about the
arbitration software management user.
Procedure
Step 1 Decompress the installation package.
1. In the operating system of the quorum server, run the unzip command to decompress the
installation package.
XXX@Linux:~# unzip OceanStor\ QuorumServer\ VXXXRXXXCXX.zip
package/
package/quorum_server.sh
package/packages/
package/packages/QuorumServer-VXXXRXXXCXX-linux.x86_64.rpm
package/qs_version.ini
package/tools/
2. After decompressing the installation package, run the cd package command to go to the
decompressed directory.
XXX@Linux:~# cd package/
Step 2 Uninstall the arbitration software.

Run the ./quorum_server.sh -uninstall command to uninstall the arbitration software.
XXX@Linux:~/package # ./quorum_server.sh -uninstall
Uninstall quorum server.
The QuorumServer uninstallation starts.
Uninstall... ########################################### [100%]
QuorumServer ########################################### [100%]
Do you want to backup configuration and log?
<Y|N>:y
QuorumServer install success completed.
Step 3 (Optional) Check whether the arbitration software is uninstalled successfully.

OceanStor V3 Series
1. When the uninstallation progress is completed, run the ps -elf | grep quorum_serverd
command to check whether the arbitration software is uninstalled successfully.
2. If the quorum_serverd process does not exist, the arbitration software is uninstalled
successfully.
XXX@Linux:~/package # ps -elf | grep quorum_serverd
0 S root 3326 32197 50 80 0 - 2449 pipe_w 17:03 pts/0 00:00:00
grep quorum_serverd
XXX@Linux:~/package #
----End
5.4 Managing a HyperMetro Consistency Group

A consistency group consists of multiple HyperMetro pairs and manages all pairs in it
centrally.
5.4.1 Viewing the HyperMetro Consistency Group Information

This operation allows you to view information about consistency groups to monitor the status
of consistency groups.
Context
Operating status of consistency groups: The operating status of a consistency group and its
HyperMetro pairs must be the same. Only HyperMetro pairs in the Paused or Normal state
can be added to consistency groups.
Procedure
Consistency Group.
Step 3 View the HyperMetro consistency group information. Table 5-8 describes related parameters.
Table 5-8 HyperMetro consistency group parameters

Name The name of the HyperMetro consistency

group.
ID The ID of the HyperMetro consistency

group.

OceanStor V3 Series
Health Status Indicates whether the consistency group is

functioning normally. The values include:
l Normal: The consistency group is
functioning normally.
l Fault: The consistency group
malfunctions or the replication link is
down.
Running Status Indicates the consistency group is running

properly. The values include:
l Normal: Consistency group has
completed synchronization successfully.
l To be synchronized: The data of
consistency group is inconsistent and
need to be synchronized.
l Paused: Consistency group is in the
pause status, and the synchronization is
suspended.
l Synchronizing: Consistency group is
synchronizing data.
l Force Start: Consistency group forcibly
enables the local or remote site to
manually allow the local or remote site
to continue to provide services.
l Invalid: Consistency group is useless
and cannot be restored in this status,
except deleting it.
Local Resource Role Whether the local site is prior service site or
not. Including Preferred and Non-
Preferred.
Recovery Policy A recovery policy determines whether the

system automatically synchronizes data
after a HyperMetro consistency group fault
is rectified.
l Automatic: The system automatically
synchronizes data.
l Manual: The synchronization operation
must be performed manually.

OceanStor V3 Series
Speed Data replication speed of a HyperMetro

consistency group.
l Low: Data replication takes a relatively
long time. This value is applicable to
scenarios where the service load is
heavy. The speed ranges from 0 MB/s to
5 MB/s.
l Medium: Data replication takes a
relatively short time. This value is
applicable to scenarios where the service
load is relatively heavy. The speed
ranges from 10 MB/s to 20 MB/s.
l High: Data replication takes a short
time. This value is applicable to
scenarios where the service load is
relatively light. The speed ranges from
50 MB/s to 70 MB/s.
l Highest: Data replication takes the
shortest time. This value is applicable to
scenarios where the service load is light.
The speed is greater than 100 MB/s.
Activation Status Activation status of site. The value can be

Active or Passive.
Owning HyperMetro Domain HyperMetro domain to which the

HyperMetro consistency group belongs.
Data Synchronization Direction The data synchronization direction of all

HyperMetro pairs in one HyperMetro
consistency group. Including Remote to
Local and Local to Remote.
Isolation Switch After the Isolation Switch is turned on, the

system will suspend the HyperMetro pair
when the difference between the write I/O
latency of the two storage arrays is greater
than the isolation switch. The storage array
with the longer write I/O latency will stop
providing services.
Isolation Threshold (ms) Write I/O latency difference between the

host and HyperMetro storage arrays.
Step 4 Click the HyperMetro consistency group you want view, in HyperMetro Pair area, view the
HyperMetro pair information. Table 5-9 describes related parameters.

OceanStor V3 Series
Table 5-9 HyperMetro pair parameters
Local Resource Name of a local resource.
Local Resource ID ID of a primary resource.
Remote Resource Name of a remote resource.
Remote Resource ID ID of a secondary resource.
Pair ID ID of the HyperMetro pair.
Pair Health Status Indicates whether the HyperMetro pair is

functioning normally. The values include:
l Normal: The pair is functioning
normally.
l Fault: The pair malfunctions or the
replication link is down.
Pair Running Status Running status of a pair of local and remote

resources. Possible values can be
l Normal: HyperMetro pair has
completed synchronization successfully.
l To be synchronized: The data of
HyperMetro pair is inconsistent and need
to be synchronized.
l Suspended: HyperMetro pair is in the
pause status, and the synchronization is
suspended.
l Synchronizing: HyperMetro pair is
synchronizing data.
l Force Start: HyperMetro pair forcibly
enables the local or remote site to
manually allow the local or remote site
to continue to provide services.
l Invalid: HyperMetro pair is useless and
cannot be restored in this status, except
deleting it.
Activation Status Activation status of site. The value can be

Active or Passive.
----End
5.4.2 Modifying the Properties of a HyperMetro Consistency

Group
This operation enables you to change the name, description, recovery policy and rate of a
HyperMetro consistency group.

OceanStor V3 Series
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group you want to modify, and click Properties.
The Properties of Consistency Group dialog box is displayed.
Step 4 In General tab, modify the related parameters. Table 5-10 describes the related parameters.
Table 5-10 Parameters of Consistency Group

Name The name of the [Example]

HyperMetro consistency HyperMetroGroup_005
group.
Description The description of the [Example]

HyperMetro consistency —
group.

OceanStor V3 Series
Speed Data replication speed of a [Example]

HyperMetro consistency Medium
group.
l Low: Data replication
takes a relatively long
time. This value is
from 0 MB/s to 5 MB/s.
l Medium: Data
replication takes a
relatively short time.
from 10 MB/s to 20
MB/s.
l High: Data replication
takes a short time. This
scenarios where the
light. The speed ranges
from 50 MB/s to 70
MB/s.
l Highest: Data replication
takes the shortest time.
service load is light. The
speed is greater than 100
MB/s.
Recovery Policy A recovery policy [Example]

determines whether the Automatic
HyperMetro fault is
rectified.
automatically
synchronizes data.
l Manual: The
synchronization
operation must be
performed manually.

OceanStor V3 Series

providing services.
Isolation Threshold (ms) Write I/O latency difference [Example]

between the host and 50
HyperMetro storage arrays.
Step 5 Click OK.
Step 6 Click Close.
----End
5.4.3 Synchronizing a HyperMetro Consistency Group

This operation allows you to synchronize all HyperMetro pairs in the consistency group. The
synchronization ensures the consistency of data on the local and remote devices at the
synchronization point and protects the data validity of LUNs.
Prerequisites
The running status of a HyperMetro consistency group must be Paused, To be synchronized
or Force Start.
Context
If controllers of storage systems reset during the synchronization of HyperMetro consistency
groups, the synchronization of some HyperMetro pairs may fail. As a result, data consistency
of LUNs cannot be ensured.
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group, and click Synchronize.
Step 4 Confirm the synchronization operation.

OceanStor V3 Series
1. Carefully read the contents of the dialog box. Then click the check box next to the
statement I have read and understand the consequences associated with performing
this operation. and click OK to confirm the information.
2. Click Close.
----End
5.4.4 Pausing a HyperMetro Consistency Group

Pausing a HyperMetro consistency group will stop data written into the non-prior service
sites, causing the data difference between prior service site and non-prior service site.
Prerequisites
The Running Status of the consistency group you want to pause must be Paused, Normal,
Synchronizing, or To be synchronized.
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group you want to pause, and choose More > Pause.
Step 4 Select Preferred or Non-Preferred site you want pause, and click OK.
Step 5 Confirm the operation of pausing the HyperMetro consistency group.

2. Click Close.
NOTE
After a HyperMetro consistency group is suspended, you can execute Synchronizing a HyperMetro
Consistency Group to restart it.
----End
5.4.5 Switching the Prior/Non-prior for a HyperMetro Consistency

Group
This operation allows you to switch the preferable site of HyperMetro consistency groups. If a
fault occurs, services will be provided by the preferred site after the switchover.
Prerequisites
The Running Status of the consistency group you want to pause must be Paused, Normal,
Synchronizing, Force Start, or To be synchronized.

OceanStor V3 Series
Context
After a HyperMetro pair is added to a consistency group, the preferred and non-preferred sites
of the pair are determined by the consistency group's preference settings.
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group you want to switch the prior/non-prior, and choose
More > Prior/Non-prior Switchover.
Step 4 Confirm the operation of switching the prior/non-prior.
2. Click Close.
----End
5.4.6 Starting a HyperMetro Consistency Group Forcibly

After system failure or the problem of the quorum server cannot which is prior service site is
fixed, determine local site or remote site to provide service by starting the HyperMetro
consistency group forcibly.
Prerequisites
l The Running Status of the consistency group you want to pause must be Paused, Force
Start or To be synchronized.
l To ensure data security, shut down the service host before forcibly starting HyperMetro
consistency group. After the HyperMetro consistency group is started, restart the host
and services on it.
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group you want to forcibly start, and choose More >
Force Start.
Step 4 Confirm the operation of forcibly start the HyperMetro consistency group.
1. Carefully read the contents of the dialog box. Then click the check box next to the
statement I have read and understand the consequences associated with performing
this operation. and click OK to confirm the information.

OceanStor V3 Series
2. Click Close.
----End
5.4.7 Adding a HyperMetro Pair

This operation enables you to add HyperMetro pairs to a HyperMetro consistency group.
Prerequisites
l The HyperMetro pairs in an HyperMetro consistency group must belong to the same
HyperMetro domain and have the same data synchronization direction.
l The Running Status of the consistency group you want to pause must be Paused.
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group you want to add HyperMetro pair, and choose More
> Add HyperMetro Pair.
The Add HyperMetro Pair dialog box displayed.
Step 4 In Available HyperMetro Pairs, select the HyperMetro pair you want to add, and click
to add the HyperMetro pair to Selected HyperMetro Pairs, then click OK.
Step 5 Click Close.
----End
5.4.8 Remove HyperMetro Pair

This operation enables you to remove a HyperMetro pair from a HyperMetro consistency
group.
Prerequisites
The Running Status of the consistency group you want to pause must be Paused or Normal.
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group you want to remove HyperMetro pair, and choose
More > Remove HyperMetro Pair.

OceanStor V3 Series
The Remove HyperMetro Pair dialog box displayed.
Step 4 In Available HyperMetro Pairs, select the HyperMetro pair you want to remove, and click
to move the HyperMetro pair to Selected HyperMetro Pairs, then click OK.
Step 5 Confirm that you want to remove the HyperMetro pair.

1. Confirm the information in the dialog box and select I have read and understood the
consequences associated with performing this operation.
2. Click OK.
The Execution Result dialog box is displayed.
3. Click Close.
----End
5.4.9 Deleting a HyperMetro Consistency Group

You can delete a HyperMetro consistency group once you do not need it.
Prerequisites
All HyperMetro pairs of HyperMetro consistency group have been removed.
Context
Only consistency groups of HyperMetro pairs are deleted but not the HyperMetro pairs.
Procedure
Consistency Group.
Step 3 Select the HyperMetro consistency group you want to delete, and click Delete.
Step 4 Optional: Select Only delete the configuration information about the local device if the
HyperMetro consistency group fails or the remote device is disconnected. based on site
requirements.
NOTE
Step 5 Carefully read the contents of the dialog box. Then click the check box next to the statement I
have read and understand the consequences associated with performing this operation.
and click OK to confirm the information.
Step 6 Click Close.
----End

OceanStor V3 Series
5.5 Importing Certificates

When the storage system is communicating with an external device, you are advised to use
the certificate verification mode to improve service security. This chapter describes how to
generate and export a certificate signing request, and import and activate the signed
certificate.
Procedure
Step 2 Choose Settings > Storage Settings > Value-added Service Settings >
Credential Management.
Step 3 Select the type of a certificate signing request that you want to export and select an
appropriate certificate key algorithm, then click Generate and Export.
Step 4 Import and activate the signed certificate.
1. Send the certificate request file to the certificate authority for signing or use the
enterprise's root certificate for signing. Then click Import and Activate.
The Import Certificate dialog box is displayed.
2. Configure certificate parameters. Table 5-11 describes the related parameters.
Table 5-11 Add certificate parameters

Certificate Type Certificate types, including device

management certificate, domain
authentication certificate, KMC
certificate, HyperMetro certificate,
HTTPS certificate, FTPS certificate,
Syslog certificate, NTP certificate, and
Call Home certificate.
Certificate File Certificate file that has been exported and

signed.
CA Certificate File Certificate file of a server.
Private Key File Private key file of a device.
3. Click OK.
4. Confirm the information of the dialog box and select I have read and understand the
The Success dialog box is displayed.
5. Click OK.
The certificate list shows imported certificates.

OceanStor V3 Series
NOTE
The CA certificate is not displayed in the certificate list.
Step 5 View the certificate information, Table 5-12 describes the related parameters.
Table 5-12 Certificate parameters

Certificate Type Certificate types, including device

management certificate, domain
authentication certificate, KMC certificate,
HyperMetro certificate, HTTPS certificate,
FTPS certificate, Syslog certificate, NTP
certificate, and Call Home certificate.
Status The status of certificate, including Valid,

Not exist, and Invalid.
Expire Time The expire time of certificate.
Expiration Warning Days Days before certificate expiration. When the

period starts, the system sends warning to
users about the expiration.
CA Certificate Fingerprint Hashed value of the certificate content. This

value is unique for every certificate. The
CA certificate fingerprint is required to
obtain the CA certificate to ensure that
content in the CA certificate has not been
modified illegally. If the CA certificate
fingerprint is different from the fingerprint
configured in the PKI domain, the device
will refuse the CA certificate.
Step 6 Modify a certificate file.

1. Select a certificate file that you want to modify and click Modify.
The Modify Certificate dialog box is displayed.
2. Modify the expiration warning days of a certificate and the encrypted password of a
private key file. Table 5-13 describes the related parameters.
Table 5-13 Parameters for modifying a certificate

Expiration Warning Days Days before certificate expiration. When

the period starts, the system sends
warning to users about the expiration.
NOTE
The value ranges from 7 to 180.
New Private Key Encryption Password Encrypted password of a new private key
file.

OceanStor V3 Series
Confirm Password Confirms the newly typed encrypted

password of a new private key file.
3. Click OK.
The Success dialog box is displayed.
4. Click OK.
Step 7 Manage Certificate Revocation Lists (CRLs)
l Import a CRL.
a. In the CRL Management area, click Import.
b. In the dialog box that is displayed, select the CRL type and CRL file, and click OK.
c. The security alert dialog box is displayed. Read information in the dialog box and
select I have read and understand the consequences associated with
performing this operation if it is tolerable.
d. Click OK.
A dialog box is displayed indicating that the operation succeeded.
l View the CRL to check the CA certificate availability. Related parameters are described
in Table 5-14.
Table 5-14 Parameters related to a CRL

Type Type of a CRL, including domain

authentication certificate, KMC
certificate and HyperMetro certificate.
NO. No. of a CRL
Name Name of a CRL
Status Status of a CRL, which can be Valid, Not

exist and Invalid.
Expire time Time when a CRL expires
----End

OceanStor V3 Series
HyperMetro Feature Guide for Block 6 FAQs
6 FAQs
About This Chapter
This chapter describes frequently asked questions (FAQs) about the HyperMetro feature. If a
problem occurs when you configure and maintain the feature, you can browse this chapter for
the answer to the problem.
6.1 What Can I Do If a Quorum Link Fails to Be Added Because the HyperMetro Arbitration
Certificate Becomes Invalid or the System Time Becomes Abnormal?
6.2 Active and Standby IP Ports Are Configured on the Quorum Server. After the Port in Use
Is Down, the Quorum Server Goes Offline. Why?
6.3 How Do I Power Off Active-Active Storage Systems and Resume the HyperMetro
Service?
6.4 When Both the HyperMetro and Remote Backup Services Are Created, the Excessively
Low Link Bandwidth Between Storage Systems Causes the Remote Backup Service to Fail
6.5 How Can I Query HyperMetro LUN Identifiers?
6.6 What Can I Do If the Remote Connection Fails to Be Created with the TOE Interface
Module
6.7 In the SQL Server database scenario, how can I adjust parameters to reduce the I/O
latency and achieve the optimal performance?
6.8 How Can I Use OVA Templates to Quickly Deploy Virtual Quorum Servers?
When a quorum server virtual machine (VM) becomes faulty, you can use an OVA template
to deploy it again quickly.

OceanStor V3 Series
6.1 What Can I Do If a Quorum Link Fails to Be Added

Because the HyperMetro Arbitration Certificate Becomes
Invalid or the System Time Becomes Abnormal?
Question
The quorum server software is newly installed, the quorum server communicates with storage
arrays properly, and the configurations on the quorum server are correct. However, a quorum
link of the quorum server fails to be added on a storage array. The storage array reports a
communication error or an invalid certificate. What can I do if the problem occurs?
Answer
The validity period of the default HyperMetro arbitration certificate is 10 years (start from
September 2015). The arbitration certificate will become invalid if the system time of the
quorum server or a storage array is incorrectly set to a value that exceeds the validity period
of the certificate.
Possible causes are as follows:
l The system time of the quorum server is incorrectly set to a value that exceeds the
validity period of the default arbitration certificate. As a result, the quorum link fails to
be added.
l The system time of a storage array is incorrectly set to a value that exceeds the validity
period of the default arbitration certificate. As a result, the quorum link fails to be added.
Perform the following operations:
Step 1 Check whether the HyperMetro arbitration certificate on the quorum server is valid.
1. In any directory of the quorum server's operating system, run the qsadmin command to
open the arbitration software.
2. In the CLI of the arbitration software, run the show tls_cert command to check whether
the HyperMetro arbitration certificate is valid.
NOTE
If State is Valid, the HyperMetro arbitration certificate is valid.

– If the HyperMetro arbitration certificate is valid, go to Step 3.
– If the HyperMetro arbitration certificate is invalid, go to Step 2.
Step 2 Check whether the system time of the quorum server is incorrectly set.
Run the date command to check the system time of the quorum server.
l If the system time of the quorum server is correct, go to Step 3.
l If the system time of the quorum server is incorrect, modify the system time and restart
the quorum server. Then add the certificates again. If the quorum link still fails to be
added after the quorum server is restarted, go to Step 3.
Step 3 Check whether the HyperMetro arbitration certificate on the storage array is valid.
1. Log in to OceanStor DeviceManager of the storage array. Choose Settings > Storage
Settings > Value-added Service Settings > Credential Management to go to the
certificate management page.

OceanStor V3 Series
2. On the certificate management page, check the validity of the HyperMetro arbitration
certificate.
– If the HyperMetro arbitration certificate is valid, go to Step 5.
– If the HyperMetro arbitration certificate is invalid, go to Step 4.
Step 4 Check whether the system time of the storage array is incorrectly set.
Log in to OceanStor DeviceManager of the storage array. Choose Settings > Basic
Information > Device Time to check the system time of the storage array.
l If the system time of the storage array is correct, go to Step 5.

l If the system time of the storage array is incorrect, modify the system time. Then add the
certificates again. If the quorum link still fails to be added after the system time of the
storage array is modified, go to Step 5.
Step 5 Contact Huawei technical support.
----End
6.2 Active and Standby IP Ports Are Configured on the

Quorum Server. After the Port in Use Is Down, the
Quorum Server Goes Offline. Why?
Question
The quorum server has two IP ports that work in active/standby mode and are on the same
network segment. After the port in use is down, why does the quorum server go offline?
Answer
By default, a quorum server does not have policy routes. It can only receive and send data via
one IP port although it has two IP ports on the same network segment. As a result, after the
port in use goes down, the other port cannot take over services.
Step 1 Create a policy routing table for the quorum server.
In the CLI of the quorum server, run ip route add under any directory.
XXX@Linux:~# ip route add 192.168.0.0/16 dev eth5 table 20 XXX@Linux:~# ip route
add 192.168.0.0/16 dev eth6 table 21
NOTE
In the preceding example:
l The IP addresses in the 192.168.0.0/16 segment receive and send data via the eth5 port. The routing table
is named table 20.
l The IP addresses in the 192.168.0.0/16 segment receive and send data via the eth6 port. The routing table
is named table 21.
Step 2 Add the active and standby IP ports on the quorum server to the policy routing tables.
In the CLI of the quorum server, run ip rule add under any directory.
XXX@Linux:~# ip rule add from 192.168.1.5 table 20 priority XXX XXX@Linux:~# ip
rule add from 192.168.1.6 table 21 priority XXX

OceanStor V3 Series
NOTE
l The active port whose IP address is 192.168.1.5 is added to table 20.
l The standby port whose IP address is 192.168.1.6 is added to table 21.
l The priority XXX of the active and standby IP ports must be the same.
l If either IP port is down, the policy routing table must be configured for it again.
Step 3 Check whether the policy routes are configured successfully.
In the CLI of the quorum server, run ip rule under any directory. If the following information
is returned, the configuration is successful.
XXX@Linux:~# ip rule
100: from 192.168.1.5 lookup 20
100: from 192.168.1.6 lookup 21
NOTE
l 100 is the value of priority.
l 20 and 21 indicate table 20 and table 21, respectively.
----End
6.3 How Do I Power Off Active-Active Storage Systems

and Resume the HyperMetro Service?
Question
If active-active storage systems must be temporarily stopped due to equipment room
relocation or power supply link failure, how do I correctly power off the storage systems?
Answer
Step 1 Power off the active-active storage systems.

1. Stop host services related to the HyperMetro service.
2. Power off the storage systems.
Power off one storage system first. After the storage system is powered off, power off
the other storage system.
For details about how to power off a storage system, see Powering off the Storage
Device in Administrator Guide of the corresponding product model.
3. Power off the quorum server.
For details about how to power off the quorum server, see the power-off document
delivered with the quorum server.
4. (Optional) Power off switches.
The networking varies with the specific services. Based on actual service requirements,
determine whether to power off switches.
Step 2 Resume the HyperMetro service.

OceanStor V3 Series
1. (Optional) Power on switches.

For details about how to power on switches, see the power-on document delivered with
the switches.
2. Power on the quorum server.
For details about how to power on the quorum server, see the power-on document
delivered with the quorum server.
3. Power on the storage systems.
For details about how to power on a storage system, see Powering on the Storage
Device in Administrator Guide of the corresponding product model.
NOTICE
The active-active storage systems can be powered on at the same time. After they are
powered on, wait until HyperMetro Pair and HyperMetro Consistency Group
become Normal. Then, you are allowed to power on service hosts.
The consistency group does not support the NAS HyperMetro pair.
4. Power on service hosts and enable host services.
----End
6.4 When Both the HyperMetro and Remote Backup

Services Are Created, the Excessively Low Link
Bandwidth Between Storage Systems Causes the Remote
Backup Service to Fail
Question
Only one replication link is established between storage systems, and both the HyperMetro
and remote backup services are created. In this scenario, why does the remote backup service
fail?
When the host service bandwidth is higher than the replication network bandwidth between
storage systems, the service with a high priority is preferentially processed. In the preceding
scenario, the link bandwidth is too low. As a result, the service with a low priority fails.
NOTE
HyperMetro and synchronous remote replication take precedence over HyperVault and asynchronous
remote replication.
Answer
Step 1 Increase the replication link bandwidth or the number of replication links to ensure that the
replication network bandwidth is higher than or equal to the peak service bandwidth.

OceanStor V3 Series
Step 2 Check whether the remote backup service is normal.

l If the remote backup service is normal, no further action is required.
l If the remote backup service is abnormal, contact Huawei technical support.
----End
6.5 How Can I Query HyperMetro LUN Identifiers?

Question
How can I query HyperMetro LUN identifiers?
Answer
After the AIX host scans for LUNs, the LUN information will be solidified in the system
database. Users can use the lscfg command to query the information. Storage system faults,
upgrade, or the modification of mapping relationships do not change the LUN information.
For HyperMetro LUNs, the AIX host only saves the LUN identifier information of one site.
When this site breaks down, users cannot use the lscfg command to query the LUN identifier
information of other site.
The application of the lscfg command is limited in the HyperMetro scenarios. In this case,
users can use the lspv -u command to query the HyperMetro LUN WWNs.
6.6 What Can I Do If the Remote Connection Fails to Be

Created with the TOE Interface Module
Question
What can I do if the remote connection fails to be created with the TOE interface module?
Answer
When a remote device whose type is Replication is added, or the iSCSI link is added to the
remote device, if error code 1073804034 occurs or the connection fails to be created, the
cause may be that the storage system uses the TOE interface module to connect. When the
local storage system uses the TOE interface module to connect to the remote storage system,
since protocols of the TOE and non-TOE interface modules process data in different ways, the
two systems may have different connection methods, causing connection failure.
NOTE
If the remote storage system uses the TOE interface module but the local storage system uses non-TOE
interface module, the above problem does not occur.
Perform the following operations to locate and handle the problem:
1. On a network where the TOE interface module connects the non-TOE interface module,
if the link fails to be created on the storage system where the TOE interface module
resides, and a communication exception error is returned, then the problem is what has
been described above. If you need to further confirm the problem, contact technical
support engineers to confirm with the system log.

OceanStor V3 Series
2. After the confirmation, handle the problem with any of the following methods.
Method 1: Select the non-TOE interface module as the end for starting the connection.
The TOE interface module is the receiving end of the connection. Establish the
connection oppositely. This method helps establish the link.
Method 2: On the storage system where the non-TOE interface module resides, run the
tcp_recycle_switch.sh command to disable the function of quickly recycling
TIME_WAIT socket in the TCP connection. After the link is established, enable the
function.
a. Enter minisystem mode, run the tcp_recycle_switch.sh off command.
b. Add the remote device and establish the replication link.
c. Enter minisystem mode, run the tcp_recycle_switch.sh on command.
6.7 In the SQL Server database scenario, how can I adjust

parameters to reduce the I/O latency and achieve the
optimal performance?
Question
In the SQL Server database scenario, how can I adjust parameters to reduce the I/O latency
and achieve the optimal performance?
Answer
You can set target_recovery_time to 60 according to the SQL official suggestion. For details,
seehttps://docs.microsoft.com/zh-cn/sql/relational-databases/logs/database-checkpoints-
sql-server#IndirectChkpt.
6.8 How Can I Use OVA Templates to Quickly Deploy

Virtual Quorum Servers?
When a quorum server virtual machine (VM) becomes faulty, you can use an OVA template
to deploy it again quickly.
Exporting an OVA Template

After a quorum server VM has been deployed and works properly with storage systems, you
can export an OVA template of this VM for quick deployment once the VM fails.
Step 1 Log in to VMware vSphere Client.
Step 2 Record the MAC addresses of the quorum server VM.

1. Select the quorum server VM, right-click, and choose Edit Settings from the shortcut
menu.
2. Click the Hardware tab.
3. Select Network adapter.
Record the MAC Address displayed on the right side.

OceanStor V3 Series
Step 3 Shut down the quorum server VM.

1. Select the quorum server VM, right-click, and choose Power > Power off.
The Confirm Power Off dialog box is displayed.
2. Confirm the information in the dialog box and click Yes.
Step 4 Export an OVA template.
1. Select the quorum server VM and choose File > Export > Export OVF Template.
The Export OVF Template dialog box is displayed.
2. In the Export OVF Template dialog box, set Format to Single file(OVA).
3. In Directory, specify a save path of the OVA template.
4. Click OK.
The system starts generating the OVA template and displays the progress. The OVA
template is in the *.ova format.
NOTE
After the export is complete, power on the quorum server VM.
----End
Importing an OVA Template

You can deploy a new quorum server VM by importing an OVA template.
Step 1 Import an OVA template.
1. Choose File > Deploy OVF Template.... Click Browser and select an OVA template
from Deploy from a file or URL.

OceanStor V3 Series
2. Specify the Name and Location, Host/Cluster, Resource Pool, Disk Format, and
Network Mapping for the VM.
NOTE
– The new VM that is deployed using the OVA template cannot use the same name as the
original VM.
– The new VM must have the same Location, Host/Cluster, Resource Pool, Disk Format, and
Network Mapping as the original VM.
3. Click Finish.
The system starts deploying the VM.
Step 2 Configure the MAC addresses for the new VM.
1. Select the new VM. In the Resources area, right-click datastore and choose Browse
Datastore from the shortcut menu.

OceanStor V3 Series
2. Download the XXX.vmx file to a local directory. Right-click the file and choose
Download.
NOTE
XXX is the name of the new VM.
3. Edit the .vmx file. Change the MAC addresses in the file to the same values as the
original VM's MAC addresses.

OceanStor V3 Series
4. Upload the modified .vmx file to the new VM's datastore to overwrite the original file.
Step 3 Delete the faulty quorum server VM.
Step 4 Select the new VM and choose Power > Power On.
Step 5 After power-on, log in to the storage system that connects to the quorum server and check the
quorum server's running status.
1. If the quorum server is online, the configuration is correct and no further action is
required.
2. If the quorum server is offline, its MAC addresses are incorrect and you must
reconfigure them.
----End

OceanStor V3 Series
HyperMetro Feature Guide for Block 7 Troubleshooting
7 Troubleshooting
About This Chapter
This chapter describes how to troubleshoot common problems that occur on the HyperMetro
feature. If a problem occurs when you configure and maintain the feature, you can browse this
chapter for the problem.
7.1 A Quorum Link Fails to Be Added After the Quorum Server Is Replaced
7.1 A Quorum Link Fails to Be Added After the Quorum

Server Is Replaced
Symptom
If the quorum server in the HyperMetro solution breaks down and cannot be recovered, you
must replace the quorum server. When a quorum link is added on a storage array after the
quorum server is replaced, the quorum link fails to be added.
Alarm Information
None
Possible Causes
The storage array's SN is not added to the white list of the new quorum server.
The original storage array and quorum server use third-party certificates for authentication.
After the quorum server is replaced with a new one, the certificate of the new quorum server
does not match that of the storage array.
Procedure
Step 1 Check whether the white list of the new quorum server contains the SN of the storage array.
1. On the quorum server, run the qsadmin command to go to the CLI of the quorum server.

OceanStor V3 Series
HyperMetro Feature Guide for Block 7 Troubleshooting
2. In the CLI of the quorum server, run the show white_list command to check whether the
white list of the quorum server contains the SNs of the two storage arrays in the
HyperMetro solution.
– If yes, go to Step 2.
– If no, run the add white_listsn=? command in the CLI of the quorum server to add
the SNs of the storage arrays to the white list of the quorum server. If the quorum
link still fails to be added, go to Step 2.
Step 2 Replace the certificates of the storage array and quorum server.
1. In OceanStor DeviceManager of the storage array, export certificates used in the
HyperMetro scenario for a third-party Certificate Authority (CA) organization to
generate certificates. SeeConfigure Quorum Server Software to replace the certificates
for the storage array and quorum server.
2. After replacing the certificates, add the quorum link again.
– If the link is added successfully, no further action is needed.
– If the link fails to be added, contact Huawei technical support.
----End
Suggestion and Summary

None

OceanStor V3 Series
HyperMetro Feature Guide for Block A How to Obtain Help
A How to Obtain Help
If a tough or critical problem persists in routine maintenance or troubleshooting, contact

Huawei for technical support.
A.1 Preparations for Contacting Huawei

To better solve the problem, you need to collect troubleshooting information and make
debugging preparations before contacting Huawei.
A.2 How to Use the Document
Huawei provides guide documents shipped with the device. The guide documents can be used
to handle the common problems occurring in daily maintenance or troubleshooting.
A.3 How to Obtain Help from Website
Huawei provides users with timely and efficient technical support through the regional
offices, secondary technical support system, telephone technical support, remote technical
support, and onsite technical support.
A.4 Ways to Contact Huawei
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and
service. For any assistance, contact our local office or company headquarters.
A.1 Preparations for Contacting Huawei

To better solve the problem, you need to collect troubleshooting information and make
debugging preparations before contacting Huawei.
A.1.1 Collecting Troubleshooting Information

You need to collect troubleshooting information before troubleshooting.
You need to collect the following information:

l Name and address of the customer
l Contact person and telephone number
l Time when the fault occurred
l Description of the fault phenomena
l Device type and software version

OceanStor V3 Series
HyperMetro Feature Guide for Block A How to Obtain Help
l Measures taken after the fault occurs and the related results
l Troubleshooting level and required solution deadline
A.1.2 Making Debugging Preparations

When you contact Huawei for help, the technical support engineer of Huawei might assist you
to do certain operations to collect information about the fault or rectify the fault directly.
Before contacting Huawei for help, you need to prepare the boards, port modules,
screwdrivers, screws, cables for serial ports, network cables, and other required materials.
A.2 How to Use the Document

Huawei provides guide documents shipped with the device. The guide documents can be used
to handle the common problems occurring in daily maintenance or troubleshooting.
To better solve the problems, use the documents before you contact Huawei for technical
support.
A.3 How to Obtain Help from Website

Huawei provides users with timely and efficient technical support through the regional
offices, secondary technical support system, telephone technical support, remote technical
support, and onsite technical support.
Contents of the Huawei technical support system are as follows:
l Huawei headquarters technical support department
l Regional office technical support center
l Customer service center
l Technical support website: http://support.huawei.com/enterprise/
You can query how to contact the regional offices at http://support.huawei.com/enterprise/.
A.4 Ways to Contact Huawei

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and
service. For any assistance, contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of
China
Website: http://enterprise.huawei.com/

OceanStor V3 Series
HyperMetro Feature Guide for Block B Glossary
B Glossary
If you want to obtain information about glossaries, visit http://support.huawei.com/

enterprise/. In the search field, enter a product model, and select a path from the paths that
are automatically displayed to go to the document page of the product. Browse or download
the OceanStor V3 Series V300R006 Glossary.

OceanStor V3 Series
HyperMetro Feature Guide for Block C Acronyms and Abbreviations
C Acronyms and Abbreviations
B
BP Block Pointer
C
CLI Command Line Interface
CPU Central Processing Unit
F
FC Fibre Channel
G
GUI Graphical User Interface
I
I/O Input/Output
L
LUN Logical Unit Number
R
RAID Redundant Arrays of Independent Disks
ROW Redirect on Write

OceanStor V3 Series
HyperMetro Feature Guide for Block C Acronyms and Abbreviations
S
SAS Serial Attached SCSI
SCSI Internet Small Computer Systems Interface
SSD Solid State Drive


OceanStor V3 HyperMetro Feature Guide For Block

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OceanStor V3 HyperMetro Feature Guide For Block

Uploaded by

Copyright:

Available Formats

OceanStor V3 Series

HyperMetro Feature Guide for Block

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 05 (2018-01-30) Huawei Proprietary and Confidential i

About This Document

OceanStor 2000 V3 series OceanStor 2600 V3

OceanStor 6000 V3 series OceanStor 6800 V3

OceanStor 18000 V3 series OceanStor 18500 V3 and 18800 V3

l Technical support engineers

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 05 (2018-01-30) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

NOTE Calls attention to important information, best practices and

Issue 05 (2018-01-30) Huawei Proprietary and Confidential iii

Issue 05 (2018-01-30) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

Issue 05 (2018-01-30) Huawei Proprietary and Confidential v

4.4.2 Configuring the Arbitration Software (Red Hat/Red Flag/NeoKylin/CentOS)........................................................ 62

Issue 05 (2018-01-30) Huawei Proprietary and Confidential vi

5.4.7 Adding a HyperMetro Pair...................................................................................................................................... 130

A How to Obtain Help.................................................................................................................148

Issue 05 (2018-01-30) Huawei Proprietary and Confidential vii

About This Chapter

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 1

Table 1-1 Benefits of HyperMetro

Robust reliability If the storage system in one data center

High compatibility By integrating SmartVirtualization, HyperMetro

1.2 License Requirements and Compatible Products

OceanStor 2000 V3 series OceanStor 2600 V3 V300R006

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 2

Product Series Product Model Version

OceanStor 5000 V3 series OceanStor 5300 V3, 5500 V300R006

OceanStor 6000 V3 series OceanStor 6800 V3 V300R006

OceanStor 18000 V3 series OceanStor 18500 V3 and V300R006

Applicable Software Versions

OceanStor When configuring HyperMetro services, use OceanStor UltraPath

OceanStor When configuring HyperMetro services, use OceanStor

1.3 Working Principle

1.3.1 Basic Concepts

Local LUN and Remote LUN

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 3

HyperMetro Consistency Group

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 4

1.3.2 HyperMetro Solution Overview

Figure 1-1 HyperMetro solution network topology

Data center A Data center B

Storage array A Storage array B

Switch Switch Switch Switch

Network of hosts and

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 5

Table 1-2 Network Overview

Network of hosts and Network Supports 8 Gbit/s Fibre Channel, 16 Gbit/s

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 6

HyperMetro replication Network l Supports 10GE, 8 Gbit/s Fibre Channel, and

Networking Each controller on every storage array in both

Same-city network Network The network uses bare fibers.

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 7

Quorum network Network l Quorum links support GE and 10GE

Issue 05 (2018-01-30) Huawei Proprietary and Confidential 8