hypermetro feature guide for block - exclusive networks · oceanstor v3 series v300r006 hypermetro...

OceanStor V3 SeriesV300R006

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 writtenconsent 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 respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 orrepresentations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://e.huawei.com

Issue 05 (2018-01-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://e.huawei.com

About This Document

PurposeThis document describes the working principle and application scenarios of the HyperMetrofeature. 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, and5800 V3

OceanStor 6000 V3 series OceanStor 6800 V3

OceanStor 18000 V3 series OceanStor 18500 V3 and 18800 V3

Intended AudienceThis document is intended for:

l Technical support engineersl Maintenance engineers

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

DANGERIndicates an imminently hazardous situation which, if notavoided, will result in death or serious injury.

WARNINGIndicates a potentially hazardous situation which, if notavoided, could result in death or serious injury.

OceanStor V3 SeriesHyperMetro Feature Guide for Block About This Document


ii

Symbol Description

Indicates a potentially hazardous situation which, if notavoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if notavoided, could result in equipment damage, data loss,performance deterioration, or unanticipated results.NOTICE is used to address practices not related topersonal injury.

NOTE Calls attention to important information, best practices andtips.NOTE is used to address information not related topersonal injury, equipment damage, and environmentdeterioration.

Change HistoryChanges between document issues are cumulative. The latest document issue contains all thechanges 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 VirtualQuorum Servers?

Issue 04 (2017-11-30)This is the fourth official release.

Added the description about arbitration mechanism or configuration operations whenconfiguring 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.



iii

Issue 01 (2017-11-30)This issue is the first official release.



iv

Contents

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

1 Feature Description....................................................................................................................... 11.1 Overview........................................................................................................................................................................ 11.2 License Requirements and Compatible Products........................................................................................................... 21.3 Working Principle...........................................................................................................................................................31.3.1 Basic Concepts............................................................................................................................................................ 31.3.2 HyperMetro Solution Overview.................................................................................................................................. 51.3.3 Arbitration Mechanism................................................................................................................................................91.3.4 HyperMetro I/O Processing Mechanism................................................................................................................... 171.3.5 Functions of a HyperMetro Consistency Group........................................................................................................191.4 Impact and Restrictions................................................................................................................................................ 221.5 Application Scenarios...................................................................................................................................................24

2 Planning........................................................................................................................................ 27

3 Installation.................................................................................................................................... 283.1 Installation Process....................................................................................................................................................... 293.2 Preparations for Installation..........................................................................................................................................293.2.1 Preparing Tools, Meters, and Documentation........................................................................................................... 303.2.2 Quick checklist for the installation environment.......................................................................................................323.3 Device Installation........................................................................................................................................................383.4 Cable Connection......................................................................................................................................................... 413.5 Power-on.......................................................................................................................................................................463.6 Storage Array Initialization.......................................................................................................................................... 493.7 Multipathing Software Installation...............................................................................................................................493.7.1 UltraPath Software Installation................................................................................................................................. 493.7.2 Third-party Multipathing Software Installation........................................................................................................ 493.8 Arbitration Software Installation.................................................................................................................................. 50

4 Configuration............................................................................................................................... 534.1 Configuration Process...................................................................................................................................................544.2 Configuration Preparations...........................................................................................................................................564.3 Configuring Switch.......................................................................................................................................................574.4 Configure Quorum Server Software.............................................................................................................................574.4.1 Configuring the Arbitration Software (SUSE).......................................................................................................... 57

OceanStor V3 SeriesHyperMetro Feature Guide for Block Contents


v

4.4.2 Configuring the Arbitration Software (Red Hat/Red Flag/NeoKylin/CentOS)........................................................ 624.4.3 Configuring the Arbitration Software (Ubuntu)........................................................................................................684.5 Configuring Basic Storage Services............................................................................................................................. 734.6 Creating SAN HyperMetro...........................................................................................................................................744.6.1 Checking the License File......................................................................................................................................... 754.6.2 Adding a Remote Device...........................................................................................................................................764.6.3 Creating a Quorum Server.........................................................................................................................................794.6.4 Creating a HyperMetro Domain................................................................................................................................ 814.6.5 Creating a HyperMetro Pair...................................................................................................................................... 824.6.6 Creating a HyperMetro Consistency Group.............................................................................................................. 884.7 Configure a Multipathing Policy for Host....................................................................................................................914.7.1 Configuring a UltraPath Policy for Host................................................................................................................... 924.7.2 (Optional) Configuring a Third-party Multipathing Policy for Host........................................................................ 974.8 Verifying the Configuration........................................................................................................................................100

5 Management............................................................................................................................... 1015.1 Managing a HyperMetro Pair..................................................................................................................................... 1015.1.1 Viewing HyperMetro Pair Information................................................................................................................... 1025.1.2 Modifying HyperMetro Pair Properties...................................................................................................................1075.1.3 Synchronizing a HyperMetro Pair...........................................................................................................................1095.1.4 Suspending a HyperMetro Pair................................................................................................................................1105.1.5 Switching the Preferred Site for a HyperMetro....................................................................................................... 1105.1.6 Forcibly Enabling a HyperMetro Pair......................................................................................................................1115.1.7 Deleting a HyperMetro Pair.....................................................................................................................................1125.1.8 Expanding the Capacity of a HyperMetro LUN......................................................................................................1135.2 Managing HyperMetro Domains................................................................................................................................ 1145.2.1 Viewing HyperMetro Domain Information............................................................................................................. 1155.2.2 Modifying a HyperMetro Domain...........................................................................................................................1155.2.3 Deleting a HyperMetro Domain.............................................................................................................................. 1165.3 Managing Quorum Servers.........................................................................................................................................1175.3.1 Viewing Quorum Server Information...................................................................................................................... 1175.3.2 Modifying Quorum Server Information.................................................................................................................. 1185.3.3 Adding a Link.......................................................................................................................................................... 1185.3.4 Removing a Link..................................................................................................................................................... 1195.3.5 Removing a Quorum Server.................................................................................................................................... 1195.3.6 Uninstalling the Arbitration Software..................................................................................................................... 1205.4 Managing a HyperMetro Consistency Group.............................................................................................................1215.4.1 Viewing the HyperMetro Consistency Group Information..................................................................................... 1215.4.2 Modifying the Properties of a HyperMetro Consistency Group............................................................................. 1245.4.3 Synchronizing a HyperMetro Consistency Group...................................................................................................1275.4.4 Pausing a HyperMetro Consistency Group............................................................................................................. 1285.4.5 Switching the Prior/Non-prior for a HyperMetro Consistency Group.................................................................... 1285.4.6 Starting a HyperMetro Consistency Group Forcibly...............................................................................................129



vi

5.4.7 Adding a HyperMetro Pair...................................................................................................................................... 1305.4.8 Remove HyperMetro Pair........................................................................................................................................1305.4.9 Deleting a HyperMetro Consistency Group............................................................................................................ 1315.5 Importing Certificates.................................................................................................................................................132

6 FAQs.............................................................................................................................................1356.1 What Can I Do If a Quorum Link Fails to Be Added Because the HyperMetro Arbitration Certificate BecomesInvalid or the System Time Becomes Abnormal?............................................................................................................ 1366.2 Active and Standby IP Ports Are Configured on the Quorum Server. After the Port in Use Is Down, the QuorumServer Goes Offline. Why?...............................................................................................................................................1376.3 How Do I Power Off Active-Active Storage Systems and Resume the HyperMetro Service?................................. 1386.4 When Both the HyperMetro and Remote Backup Services Are Created, the Excessively Low Link BandwidthBetween Storage Systems Causes the Remote Backup Service to Fail............................................................................1396.5 How Can I Query HyperMetro LUN Identifiers?.......................................................................................................1406.6 What Can I Do If the Remote Connection Fails to Be Created with the TOE Interface Module.............................. 1406.7 In the SQL Server database scenario, how can I adjust parameters to reduce the I/O latency and achieve the optimalperformance?.................................................................................................................................................................... 1416.8 How Can I Use OVA Templates to Quickly Deploy Virtual Quorum Servers?......................................................... 141

7 Troubleshooting........................................................................................................................ 1467.1 A Quorum Link Fails to Be Added After the Quorum Server Is Replaced................................................................146

A How to Obtain Help.................................................................................................................148A.1 Preparations for Contacting Huawei..........................................................................................................................148A.1.1 Collecting Troubleshooting Information................................................................................................................ 148A.1.2 Making Debugging Preparations............................................................................................................................ 149A.2 How to Use the Document.........................................................................................................................................149A.3 How to Obtain Help from Website............................................................................................................................ 149A.4 Ways to Contact Huawei............................................................................................................................................149

B Glossary...................................................................................................................................... 150

C Acronyms and Abbreviations................................................................................................ 151



vii

1 Feature Description

About This Chapter

HyperMetro provides you with disaster recovery functions and enables you to synchronizeand replicate data between storage arrays, monitor service operating status, and performfailovers. You can switch over services and implement service load sharing while your storagearray is running.

1.1 OverviewThis section describes the background, definition, and benefits of HyperMetro.

1.2 License Requirements and Compatible ProductsThis section describes the availability of HyperMetro in terms of the license requirement andapplicable version.

1.3 Working PrincipleThis section introduces the basic concepts, I/O processing mechanism, and arbitrationmechanism of HyperMetro and describes how to use HyperMetro for service switchover andrecovery.

1.4 Impact and RestrictionsThis section describes the impact and restrictions of HyperMetro feature.

1.5 Application ScenariosThis section introduces the application scenarios of HyperMetro.

1.1 OverviewThis section describes the background, definition, and benefits of HyperMetro.

BackgroundWith the rapid development of the information technology (IT), storage systems are becomingever important for critical services in a variety of industries. Service interruptions in storagesystems 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, andgovernments. Therefore, service continuity is critical to the construction of storage systems.Traditionally, one production center and one disaster recovery center are constructed, and the

OceanStor V3 SeriesHyperMetro Feature Guide for Block 1 Feature Description


1

disaster recovery center is active only when the production center is down. This disasterrecovery 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 resourceutilization.

Definition

HyperMetro enables storage systems in two different data centers to process servicessimultaneously, establishing a mutual backup relationship. If the storage system in one datacenter malfunctions, the storage system in the other data center automatically takes overservices 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 centermalfunctions, the storage system in the other datacenter automatically takes over services withoutdata loss or service interruption.

High compatibility By integrating SmartVirtualization, HyperMetroenables full utilization of storage resources,minimizes upgrade costs, and is fully compatiblewith storage systems from most vendors,including EMC, IBM, HDS, HP, and SUN.

1.2 License Requirements and Compatible ProductsThis section describes the availability of HyperMetro in terms of the license requirement andapplicable version.

License Requirement

HyperMetro is a value-added feature that requires a software license for use on both local andremote storage systems.

Applicable products

Product Series Product Model Version

OceanStor 2000 V3 series OceanStor 2600 V3 V300R006



2

Product Series Product Model Version

OceanStor 5000 V3 series OceanStor 5300 V3, 5500V3, 5600 V3, and 5800 V3

V300R006

OceanStor 6000 V3 series OceanStor 6800 V3 V300R006

OceanStor 18000 V3 series OceanStor 18500 V3 and18800 V3

V300R006

Applicable Software Versions

Software Version

OceanStorUltraPath

When configuring HyperMetro services, use OceanStor UltraPathV100R008C50SPC500 or later.

OceanStorQuorumServer

When configuring HyperMetro services, use OceanStorQuorumServer V300R006 or later.

NOTELog in to http://support.huawei.com/enterprise/ and you can register for an account on the website. Afteryou log in with the applied user name and password. Choose Support > Enterprise Storage and click thecorresponding 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 PrincipleThis section introduces the basic concepts, I/O processing mechanism, and arbitrationmechanism of HyperMetro and describes how to use HyperMetro for service switchover andrecovery.

1.3.1 Basic ConceptsThis section describes basic concepts of HyperMetro, including local logical unit number(LUN), remote LUN, dual-write, data change log (DCL), HyperMetro pair, HyperMetroconsistency 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 thatbelong to the remote storage system.

Dual-Write

Dual-write enables the synchronization of application host I/O requests with both local andremote LUNs.



3

http://support.huawei.com/enterprise/

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 quorumserver. 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 mustcreate 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 ofthe HyperMetro pair to determine whether the operation succeeded. Configure a HyperMetrodomain before configuring HyperMetro pairs.

HyperMetro Consistency Group

A HyperMetro consistency group is a collection of HyperMetro pairs that have a servicerelationship with each other. For example, the local storage system has three local LUNs thatrespectively store service data, logs, and change tracking information of a database. If data onany of the three LUNs becomes invalid, all data on the three LUNs becomes unusable. Uponconfiguration, create a consistency group and add the three HyperMetro pairs to theconsistency group.

Synchronization

Synchronization refers to the synchronization of differential data between a local LUN and aremote LUN. Data synchronization takes place between two LUNs in a HyperMetro pair. Youcan 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 malfunctionsimultaneously, HyperMetro stops hosts from accessing both. To quickly restore services, youcan forcibly start the local or remote storage system.

Priority Switchover

Priority switchover indicates that the preferred site takes precedence during arbitration. If theHyperMetro replication network is down, the storage system that wins arbitration continuesproviding services to hosts. After the creation of a HyperMetro pair, the local data center is bydefault the preferred site and the remote data center is the non-preferred site.



4

Locking MechanismTo prevent different host I/Os from being written to the same location in the storage system atthe same time, the storage system uses the locking mechanism to prevent access conflicts. Thehost I/O can only be written to the storage system that obtains the locking mechanism.

1.3.2 HyperMetro Solution OverviewThis section describes the HyperMetro solution network and provides a logical HyperMetronetwork topology to show the mapping relationship and data flows between host applicationsand storage arrays.

HyperMetro enables active-active block storage services. LUN data is synchronized betweentwo 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 storagearray in the other data center. If the link between two storage arrays in two data centers isdown, only one storage array can be accessed by hosts. The quorum server determines whichstorage array continues providing services.

Figure 1-1 shows the HyperMetro solution network topology.

Figure 1-1 HyperMetro solution network topology

Switch

Switch

Storage array A

Switch

Switch

Host cluster

Storage array B

Switch Switch

Quorum server

Switch Switch

LAN/WAN

Data center A Data center B

Network of hosts and storage arrays

HyperMetro replication network

Same-city network between data centers

Quorum networkQuorum site

FC/IP



5

Network OverviewTo ensure reliability of storage arrays, establish redundant links among the network betweenhosts and storage arrays, HyperMetro replication network, same-city network between datacenters, and quorum network.

Table 1-2 Network Overview

Network Description

Network of hosts andstorage systemsAll hosts in the two datacenters can form acluster and hostnetworks caninterconnect across datacenters.

Networktype

Supports 8 Gbit/s Fibre Channel, 16 Gbit/sFibre Channel, 10GE, and GE networks.

Networkingmode

l A fully interconnected network in whicheach host is physically and logicallyconnected to the storage arrays in both datacenters.

l A host must connect to both storage arraysusing the same type of network.

l Dual-switch networking must be used.l The HyperMetro replication network,

storage-to-host network, and quorumnetwork need to be physically isolated andcommon ports are not recommended.



6

Network Description

HyperMetro replicationnetworkThis is the heartbeatnetwork between thestorage systems in thetwo data centers. Itenables the storagesystems to provideservices for hostsconcurrently andensures datasynchronizationbetween them.NOTE

The storage system setslink priorities for differenttypes of information fortransferring data. The linkpriority of heartbeatinformation is higher thanthat of datasynchronizationinformation.

Networktype

l Supports 10GE, 8 Gbit/s Fibre Channel, and16 Gbit/s Fibre Channel networks.NOTE

When using the 10GE network, you are advisedto use the L2 network.

l Network quality and bandwidthrequirements for deploying the network:– Bandwidth: ≥ peak service bandwidth

(total bandwidth of the two ends)– Latency: The maximum supported RTT

is 10 ms (distance < 300 km)NOTE

In practice, the latency is determined by therequirements of the application layer. Theactive/active solution must meet theminimum latency requirement. The round-triptime (RTT) of the Oracle RAC, SQL Server,and DB2 applications is less than 1 ms (witha distance of less than 100 km). The RTT ofthe VMware vSphere applications is less than10 ms (with a distance of less than 300 km).

– No jitter and packet loss

– BER: ≤ 10-12

l The HyperMetro replication network,storage-to-host network, and quorumnetwork need to be physically isolated andcommon ports are not recommended.

Networkingmode

Each controller on every storage array in bothdata centers has at least two redundant links. Itis recommended that you use four redundantlinks.

Same-city networkbetween data centersThe storage systems indata centers A and Bprovide the sameservices for hosts. Thereis a mutual backuprelationship between thetwo storage systems. Ifthe storage system inone data centermalfunctions, thestorage system in theother data centerautomatically takes overservices without data

Networktype

The network uses bare fibers.



7

Network Description

loss or serviceinterruption.

Networkingmode

l For Fibre Channel networks:– The two data centers can be directly

connected using bare fibers if theirdistance is within 25 km. Ensure that thestorage and application layers each haveat least two pairs (four wires) of barefibers for heartbeat interconnection in thecluster.

– If the data centers are greater than orequal to 25 km apart, use densewavelength division multiplexing(DWDM) devices to build theinterconnection network between DCs.

l For IP networks:– The two data centers can be directly

connected using bare fibers if theirdistance is within 80 km. If core switchesare deployed, ensure that at least twopairs (four wires) of bare fibers areconnected to the core switches forHyperMetro mirroring at the storagelayer and heartbeat interconnection at theapplication layer.

– If the data centers are greater than orequal to 80 km apart, use DWDMdevices to interconnect them.

Quorum networkIf communicationbetween the storagesystems in data centersA and B is interruptedor a storage systemmalfunctions, thequorum serverdetermines whichstorage system isaccessible.

Networktype

l Quorum links support GE and 10GEnetworks, but not a Fibre Channel network.

l Quorum links support IPv4 and IPv6addresses.

l For versions earlier than V300R006C10, thearbitration link port cannot use a storagedevice's management or maintenancenetwork port. For V300R006C10 and laterversions, the arbitration link port can use astorage device's management network port,but cannot use its maintenance network port.

l Network quality and bandwidthrequirements for deploying the network:– Latency: RTT ≤ 50 ms– Bandwidth: ≥ 10 Mbit/s

l The HyperMetro replication network,storage-to-host network, and quorumnetwork need to be physically isolated andcommon ports are not recommended.



8

Network Description

NOTEA quorum server isdeployed on the quorumnetwork. If storage arraysin the two data centersencounter a device faultor a link between thestorage arrays is down,the quorum serverdetermines the accessstatus of data center Aand data center Baccording to thearbitration result.

Networkingmode

l Quorum servers are supported but quorumdisks are not.

l You are advised to deploy the quorum serverat a third-place site. If there is no third-placesite, you are advised to deploy the quorumserver at the preferred site. In this case, thequorum server and related devices shouldhave uninterruptible power supply (UPS)protection.

l A dual-switch network is recommended. AGE/10GE port on each controller of astorage array is connected to the third-placequorum server and the service network portson the quorum server are connected to twostorage arrays, ensuring that the quorumserver is connected to all controllers of eachstorage array.

l If each controller has two quorum ports,connect the first quorum port on eachcontroller to switch 1 and configure IPnetwork segment 1. In addition, connect thesecond quorum port on each controller toswitch 2 and configure IP network segment2.

l The quorum server can be a physical or avirtual server. If a virtual server is used, youare advised to deploy VMware vSphere/FusionSphere FT or HA to achieve highavailability.

l Huawei Enterprise Cloud (HEC) can be usedas a quorum server.When the HEC is used as the quorum server,apply for a VM (including the CPU,memory, disk, and OS). The VMspecifications are the same as those of thequorum server. Apply for 2 Mbit/s exclusivebandwidth and one elastic IP address foreach disk array.

1.3.3 Arbitration MechanismIf the link between the two data centers breaks down, they can no longer be synchronized andonly one will continue providing services. HyperMetro supports two arbitration modes todetermine 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.



9

NOTE

The quorum server mode is recommended. After a quorum server is deployed, the non-preferred site ofHyperMetro will automatically take over services once the preferred site becomes faulty, withoutcausing HyperMetro service interruption.

Static Priority ModeThe 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 thenon-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 sitecontinues providing services for hosts and the storage array at the non-preferred sitestops.

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 arrayat the preferred site. As a result, HyperMetro services stop. In this case, you mustforcibly start the storage array at the non-preferred site to provide services for hosts.

NOTEWhen you use OceanStor DeviceManager or CLI to power off a storage device, it will notify its peerstorage 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 thearbitration mechanism in static priority mode.

NOTEYou 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

No.

Fault Example Fault Type HyperMetro PairRunningStatus

Arbitration Result

1

Data center A Data center BLUN LUN

HyperMetro Pair The linkbetween twostorage arraysbreaks down.

To besynchronized

A continuesproviding serviceswhile B stops.

2


HyperMetro Pair The storagearray in datacenter B (non-preferred site)malfunctions.

To besynchronized

A continuesproviding serviceswhile B stops.



10

No.


Arbitration Result

3


HyperMetro Pair The storagearray in datacenter A(preferredsite)malfunctions.

To besynchronized

Both A and B stop.You must forciblystart B to resumeproviding servicesfor hosts.

Black cable: HyperMetro replication network

Quorum Server ModeIn quorum server mode, the heartbeat network determines whether the storage arrays areworking properly. If a malfunction occurs, each data center sends an arbitration request to thequorum server, and only the winner continues providing services.

The quorum site supports two quorum servers for V300R006C10 and later versions. The twoquorum servers work in active/standby mode. Once the active quorum server is faulty, thesystem automatically switches to the standby quorum server to execute the arbitrationfunction.

In a HyperMetro pair, you can set one data center as the preferred site, which takesprecedence 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 arbitrationmechanisms when one and two quorum servers are deployed, respectively.

NOTEYou 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

No.


Arbitration Result

1 Quorum server


LUNLUN

HyperMetro Pair

The quorumserver breaksdown.

Normal Both A and Bcontinue providingservices.NOTE

HyperMetroautomaticallyswitches to staticpriority arbitration.



11

No.


Arbitration Result

2 Quorum server


LUNLUN

HyperMetro Pair

The linkbetween onestorage arrayand thequorum serverbreaks down.

Normal Both A and Bcontinue providingservices.

3 Quorum server


LUNLUN

HyperMetro Pair

One storagearraymalfunctions.

To besynchronized

B continuesproviding serviceswhile A stops.

4 Quorum server


LUNLUN

HyperMetro Pair

The linkbetween twostorage arraysbreaks down.

To besynchronized

Result 1: Acontinues providingservices while Bstops.Result 2: Bcontinues providingservices while Astops.NOTE

l A has arbitrationpriority, so thenormal result isResult 1.

l (ForV300R006C10and laterversions) If thelink between datacenter A and theapplication serverhas become faultybefore the linkbetween the twostorage arraysbreaks down, datacenter B will winthe arbitration.

5 Quorum server


LUNLUN

HyperMetro Pair

One storagearray and thequorum serverbothmalfunction.

To besynchronized

Both A and B stop.NOTE

You must forciblystart B to resumeproviding services forhosts.



12

No.


Arbitration Result

6 Quorum server


LUNLUN

HyperMetro Pair

The linkbetween thetwo storagearrays and thelink betweenone storagearray and thequorum serverboth breakdown.

To besynchronized

B continuesproviding serviceswhile A stops.

7 Quorum server


LUNLUN

HyperMetro Pair

One storagearraymalfunctionsand the linkbetween theother storagearray and thequorum serveris down.

To besynchronized

Both A and B stop.NOTE

You must forciblystart B to resumeproviding services forhosts.

8 Quorum server


LUNLUN

HyperMetro Pair

The quorumservermalfunctionsand then thelink betweentwo storagearrays isdown.

To besynchronized

Result 1: If the linkis interrupted morethan 60 seconds afterthe quorum serverfails, A continuesproviding serviceswhile B stops.Result 2: If the linkis interrupted within60 seconds of thequorum serverfailure, both A and Bstop. You mustforcibly start eitherA or B to resumeproviding servicesfor hosts.

9 Quorum server


LUNLUN

HyperMetro Pair

The quorumservermalfunctionsand the linkbetween thequorum serverand onestorage arrayis down.

Normal Both A and Bcontinue providingservices.NOTE

HyperMetroautomaticallyswitches to staticpriority arbitration.



13

No.


Arbitration Result

Black cable: HyperMetro replication networkGreen cable: quorum network

Table 1-5 Arbitration mechanism in dual-quorum-server mode

No.


Arbitration Result

1 Quorum server (active)


LUNLUN

HyperMetro Pair

Quorum server (standby)

The activequorum serverbreaks down.

Normal The standby quorumserver takes over thearbitration servicesfrom the activequorum server.Both A and Bcontinue providingservices.


Data center A Data cente B

LUNLUN

HyperMetro Pair


The linkbetween onestorage arrayand the activequorum serverbreaks down.

Normal The active quorumserver runs properly.Both A and Bcontinue providingservices.



LUNLUN

HyperMetro Pair


One storagearraymalfunctions.

To besynchronized

The active quorumserver runs properly.B continuesproviding serviceswhile A stops.



14

No.


Arbitration Result



LUNLUN

HyperMetro Pair


The linkbetween twostorage arraysbreaks down.

To besynchronized

The active quorumserver runs properly.Result 1: Acontinues providingservices while Bstops.Result 2: Bcontinues providingservices while Astops.NOTE

A has arbitrationpriority, so thenormal result isResult 1.



LUNLUN

HyperMetro Pair


The activequorum serverfails and thenthe storagearray at thepreferred sitefails aftermore than 60seconds.

To besynchronized

The standby quorumserver takes over thearbitration servicesfrom the activequorum server.B continuesproviding serviceswhile A stops.



LUNLUN

HyperMetro Pair


The linkbetween thetwo storagearrays and thelink betweenone storagearray and theactive quorumserver bothbreak down.

To besynchronized

The active quorumserver runs properly.B continuesproviding serviceswhile A stops.



15

No.


Arbitration Result



LUNLUN

HyperMetro Pair


The linkbetween theactive quorumserver andnon-preferredsite breaksdown and thenthe storagearray at thepreferred sitefails aftermore than 60seconds.

To besynchronized

The standby quorumserver takes over thearbitration servicesfrom the activequorum server.B continuesproviding serviceswhile A stops.



LUNLUN

HyperMetro Pair


The activequorum servermalfunctionsand then thelink betweentwo storagearrays isdown.

To besynchronized

The standby quorumserver takes over thearbitration servicesfrom the activequorum server.Result 1: If the linkis interrupted morethan 60 secondsafter the activequorum server fails,A continuesproviding serviceswhile B stops.If the link isinterrupted within 60seconds of thequorum serverfailure, both A andB may win thearbitration andcontinue providingservices.NOTE

A has arbitrationpriority, so generallyA continuesproviding serviceswhile B stops.



16

No.


Arbitration Result



LUNLUN

HyperMetro Pair


The activequorum servermalfunctionsand the linkbetween theactive quorumserver and onestorage arrayis down.

Normal The standby quorumserver takes over thearbitration servicesfrom the activequorum server.Both A and Bcontinue providingservices.

Black cable: HyperMetro replication networkGreen solid cable: quorum network between the active quorum server and data centersGreen dotted cable: quorum network between the standby quorum server and data centers

1.3.4 HyperMetro I/O Processing MechanismHyperMetro uses the dual-write and DCL technologies to synchronize data changes betweentwo data centers, ensuring data consistency. In addition, HyperMetro enables the storagearrays in the two data centers to concurrently provide services for hosts.

Basic ConceptsYou are advised to read about the key concepts of HyperMetro before reading about the I/Oprocessing mechanism. For details, see 1.3.1 Basic Concepts.

Write I/O Processl 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 toboth local and remote caches, ensuring data consistency between caches. If the storagesystem 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 storagesystem, 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 accessthe same storage system at the same time. Data can be written to a storage system onlyafter the locking mechanism grants permission to the storage system. If the lockingmechanism does not grant priority, the storage system must wait until the previous I/O iscomplete. It must then obtain write permission after the locking mechanism releases theprevious storage system.

Figure 1-2 shows the write I/O process of an application host delivering an I/O request andcausing data changes.

NOTE

In the following figure, the write I/O accesses the local storage system, and the local storage systemwrites data to the remote storage system for dual-write purposes.



17

Figure 1-2 Write I/O process

Host

LOG

2

6

3

4

3

6DCL

4

51

Local LUN

Local cache

DWDM

Storage

Remote LUN

Remote cache

HyperMetro management module

4

Local storage array Remote storage array

Same-city network between data centers

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 receivingfeedback 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 convertedinto a DCL. The DCL records the differential data between the local and remoteLUNs.

NOTE

If the write I/O fails to be written to the local or remote cache, HyperMetro services aresuspended and the storage system in each data center sends an arbitration request to thequorum server. The storage system that wins the arbitration continues providing services andthe one that fails stops. In the background, the storage system uses the DCL to synchronizedata. 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 dataprotection 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 accessibleto hosts. If the storage system in one data center malfunctions, the storage system in the otherdata center continues providing host services alone.



18

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 neareststorage array, reducing cross-site accesses and latency while improving access efficiency and storageperformance.

l If the customer needs to use non-Huawei multipathing software on the application server, thefunction 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 forservers 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

Data center A

Local LUN

Data center B

Remote LUN

HyperMetro managementmodule

1 5

23 4 4

1. An application host applies for read permission from the HyperMetro managementmodule.

NOTEIf the link between the storage arrays in the two data centers is down, the quorum serverdetermines which storage array continues providing services for hosts.

2. The HyperMetro management module enables the local storage system to respond to theread I/O request made by the host.

3. If the local storage system is operating properly, it returns data to the HyperMetromanagement module. If not, the HyperMetro management module enables the host toread data from the remote storage system.

4. If the local storage array is working improperly, the HyperMetro management moduleenables the host to read data from the remote storage array. The remote storage arrayreturns 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 GroupA 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 informationare stored on different LUNs. If data on one of the LUNs becomes unavailable, data on theother LUNs also becomes invalid. A consistency group is a collection of multiple HyperMetro



19

pairs. It ensures that the read/write control policies of the multiple LUNs on a storage arrayare synchronized. The operation and control policies of all members that have been added to aconsistency group must be consistent with those of the consistency group.

HyperMetro applications can use a consistency group to manage multiple HyperMetro pairsin a unified manner.

The following compares synchronization in a consistency group with synchronization withoutusing a consistency group to prove that a consistency group is effective in preventing dataloss.

Without a HyperMetro Consistency GroupIf LUNs are not added to a HyperMetro consistency group, the possibility of data loss is quitehigh for these LUNs, as shown in Figure 1-4.



20

Figure 1-4 Without a HyperMetro consistency group

Remote storage array

HyperMetro pair 01

HyperMetro pair 02

HyperMetro pair 03

Local storage array

HyperMetro pair 01

HyperMetro pair 02

HyperMetro pair 03

HyperMetro pair 01

HyperMetro pair 02

HyperMetro pair 03

Local LUN01

Local LUN02

Local LUN03

Local LUN01

Local LUN02

Local LUN03

Local LUN01

Local LUN02

Local LUN03

Remote LUN01

Remote LUN02

Remote LUN03

Remote LUN01

Remote LUN02

Remote LUN03

Remote LUN01

Remote LUN02

Remote LUN03

1. No consistency group is created.

2. Synchronization fails, resulting in data inconsistency.

3. Data becomes invalid.

· Data, logs, and modification information of a database application are stored on local LUN01, LUN02, and LUN03 respectively.

· No consistency group is created on the local storage array.

Data synchronization fails between two LUNs in HyperMetro pair 02 due to a fault of the HyperMetro pair. Data synchronization succeeds between LUNs in HyperMetro pairs 01 and 03.

After the local storage array malfunctions due to a disaster, data on the remote storage array is used for data recovery. Data in the database of the local storage array is still invalid because data on the three local LUNs are not stored at the same point in time.

Before data changes

After data changes

Data recovery

Pha

ses

in a

pro

cess

of d

ata

beco

min

g in

valid

With a HyperMetro Consistency GroupIf LUNs are added to a HyperMetro consistency group, no data is lost, as shown in Figure1-5.



21

Figure 1-5 With a HyperMetro consistency group

Remote storage array

HyperMetro pair 01

HyperMetro pair 02

HyperMetro pair 03

Local storage array

HyperMetro pair 01

HyperMetro pair 02

HyperMetro pair 03

HyperMetro pair 01

HyperMetro pair 02

HyperMetro pair 03Local LUN03

Remote LUN01

Remote LUN02

Remote LUN03

Remote LUN01

Remote LUN02

Remote LUN03

Remote LUN01

Remote LUN02

Remote LUN03

1. A consistency group is created.

2. The consistency group stops the replication task.

3. The consistency group ensures data validity.

· Data, logs, and modification information of a database application are stored on local LUN01, LUN02, and LUN03 respectively.

· Consistency group 01 is created on the local storage array and three HyperMetro pairs are added to the consistency group.

· HyperMetro pair 02 encounters a fault during data synchronization.

· The consistency group stops HyperMetro pairs 01 and 03 immediately.

· After the fault is rectified, data is replicated.

After a disaster occurs, the data on the remote storage array is used for data recovery. The data in the database is valid.

Local LUN01

Local LUN02

Local LUN03

Local LUN01

Local LUN02

Local LUN03

Local LUN01

Local LUN02

Consistency group 01



Pha

ses

in a

pro

cess

of e

nsur

ing

data

val

idity

by

a co

nsis

tenc

y gr

oup

Before data changes

After data changes

Data recovery

1.4 Impact and RestrictionsThis section describes the impact and restrictions of HyperMetro feature.

Network Restrictions

For details about network restrictions, see HyperMetro Solution Overview.



22

Device Restrictions

Table 1-6 Device configuration requirements

Device Configuration Requirement

Quorum server l The arbitration software can be deployed on either a physicalmachine or a virtual machine (VM). The configurationrequirements 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 EnterpriseLinux 6 for x86_64, Red Hat Enterprise Linux 6.1 forx86_64, Red Hat Enterprise Linux 6.2 for x86_64, Red HatEnterprise Linux 6.3 for x86_64, Red Hat Enterprise Linux6.5 for x86_64, Red Hat Enterprise Linux 6.6 for x86_64,Red Hat Enterprise Linux 6.7 for x86_64, Red Hat EnterpriseLinux 7.2 for x86_64, Red Hat Enterprise Linux 7.2 forx86_64, SUSE Linux Enterprise Server 11 SP1 for x86_64,SUSE Linux Enterprise Server 11 SP2 for x86_64, SUSELinux Enterprise Server 11 SP3 for x86_64, SUSE LinuxEnterprise Server 11 SP4 for x86_64, SUSE Linux EnterpriseServer 12 SP2 for x86_64, Ubuntu 14.04 LTS for x86_64,CentOS 6.8 for x86_64NOTE

V300R006C00SPC100 and later versions support CentOS 6.8.

The arbitration software does not support operating systems that useCPU architectures such as MIPS, ARM, and PPC.

– Storage capacity for installing the arbitration software: ≥ 10GB

– Number of network ports: ≥ 3NOTE

One network port is used for operating system management and theother two are used as arbitration ports that connect to the storagearrays.

l In the event of virtual machine deployment, virtual machines canonly use servers' local disks or LUNs that are provided by otherstorage systems instead of the active-active storage systems assystem disks and data disks.

l Arbitration granularity can be a HyperMetro pair or a consistencygroup.

Storage array l The versions of the local and remote storage systems in aHyperMetro relationship are the same. In addition, the hardwareconfigurations of the two storage systems are the same.

l The HyperMetro license must be available for the storage arraysin two data centers.



23

Compatibility

When using HyperMetro, ensure that the host operating system, multipathing software, andarbitration software are compatible with each other. You can query the compatibility using theOceanStor Interoperability Navigator.

1.5 Application ScenariosThis 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 areconstructed, hospitals have higher requirements for service continuity. Once criticalservices such as out-patient, in-patient, and electronic medical record (EMR) services areinterrupted, medical treatment will be delayed and hospitals will suffer from greateconomic loss and inestimable damage to their reputation. Hospitals require zerorecovery point objective (RPO) and the recovery time objective (RTO) must be withinfive minutes. In addition, the out-patient building and in-patient network informationcenter 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 systemsprocess services around the clock. Banks need a solution to meet their serviceconstruction requirements (RPO = 0, RTO ≈ 0) and ensure business continuity. Serviceinterruptions 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, andencryption platform services and class-A services include ESB services, ECIF services,trade system services, e-channel services, centralized operation services, and e-bankservices).

l Social Insurance

The social insurance industry also has high requirements for service continuity. Monthlyaccounting and year-end settlement require 24/7 services. If social insurance systemsmalfunction, livelihood issues will appear. For example, people cannot obtain theirpensions on time and health insurance problems cannot be resolved. HyperMetro isapplicable to social insurance application scenarios including the basic informationmanagement, social insurance card system, labor relationship management, publicservices, 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 constructedin 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 expandthe existing solution to the Disaster Recovery Data Center Solution (Geo-Redundant Mode).



24

http://support-open.huawei.com/ready/pages/user/compatibility/support-matrix.jsf

Figure 1-6 shows the network of the 3DC with HyperMetro and asynchronous remotereplication.

Figure 1-6 Network of the 3DC with HyperMetro and asynchronous remote replication

Asynchronous remote

replication

Optical fiber

Network cable

Site C

LUN

Remote DR center

Storage system

Storage system

LUN

Production center

Site A

Storage system

Same-city production center

Site B

LUN

HyperMetro

NOTE

A remote replication relationship can be established between the remote DR center and either productioncenter.

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.



25

Figure 1-7 Network of the 3DC with HyperMetro and synchronous remote replication

Synchronous remote replication

Optical fiber

Site C

LUN

Same-city DR center

Storage system

Storage system

LUN

Production center

Site A

Storage system

Same-city production center

Site B

LUN

HyperMetro



26

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 SolutionProduct Documentation V200R001 (Active-Active Data Center).

OceanStor V3 SeriesHyperMetro Feature Guide for Block 2 Planning


27

http://support.huawei.com/ehedex/hdx.do?docid=DOC1000120824&lang=en&clientWidth=1639&browseTime=1490269969411


3 Installation

About This Chapter

This chapter describes how to install the HyperMetro feature and devices related to thefeature, connect cables, and power on devices, helping you avoid unnecessary rework duringand after installation.

3.1 Installation ProcessBefore the installing a storage array, view the installation process. The installation processguides you through a smooth and complete installation.

3.2 Preparations for InstallationPreparations before installing devices include preparing tools and meters, checking theinstallation environment, and unpacking and checking goods. Sufficient preparation ensures asafe and proper installation.

3.3 Device InstallationInstall devices as instructed in the following description to avoid unnecessary rework at yoursite.

3.4 Cable ConnectionHyperMetro cable connection involves: network between hosts and storage arrays,HyperMetro replication network, same-city data center network, and quorum network.

3.5 Power-onAfter installing all devices, power on them and check their operating status. Ensure that alldevices and their hardware are properly installed. Otherwise, do not power on them.

3.6 Storage Array InitializationAfter powering on a storage array, you must initialize it.

3.7 Multipathing Software InstallationThis section describes installation environment requirements, pre-installation preparations,and the installation procedure of multipathing software.

3.8 Arbitration Software InstallationThis section describes how to install the arbitration software. Quorum server software needsto be installed only when a quorum server is used for HyperMetro.

OceanStor V3 SeriesHyperMetro Feature Guide for Block 3 Installation


28

3.1 Installation ProcessBefore the installing a storage array, view the installation process. The installation processguides you through a smooth and complete installation.

Figure 3-1 shows the installation process.

Figure 3-1 Installation process

Device Installation

Start

Preparations for Installation

Power-on

Cable Connection

Storage Array Initialization

End

Multipathing Software Installation

Arbitration Software Installation

3.2 Preparations for InstallationPreparations before installing devices include preparing tools and meters, checking theinstallation environment, and unpacking and checking goods. Sufficient preparation ensures asafe and proper installation.



29

3.2.1 Preparing Tools, Meters, and DocumentationBefore installing devices, ensure that necessary installation support materials including tools,meters, and documentation are available. A good preparation helps ensure a correct andsmooth 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 andscale.

Phillips screwdriver(M3 to M6)

Fastens small screws orbolts, and has a cross-shaped head.

Flat-head screwdriver(M3 to M6)

Fastens small screws orbolts, and has a flathead.

Diagonal pliers Cuts insulation tubesand cable ties.

Crimping tool Crimps the metal jacketat the end of a coaxialcable assembly.

Segmented bladeutility knife

Cuts the adhesive tapeson a carton.

Floating nut mountingbar

Installs or removes afloating nut.

Antistatic clothing Prevents operatorsagainst electrostaticcharges.

ESD glove Prevents operatorsagainst electrostaticcharges.

ESD wrist strap Prevents operatorsagainst electrostaticcharges.



30

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 insulationof a cabinet, connectionof a cable, and electricperformancespecifications of adevice, such as thevoltage, current, andresistance.

Network cable tester Tests whether a networkcable works properly.

Prepare the following materials before installing devices: contract/agreement, deviceconfiguration table, equipment room design and construction drawing paper (provided by thecustomer), and product documentation.

Obtaining DocumentationBefore 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 toobtain OceanStor UltraPathfor Linux V100R008C50User Guide, log in to http://support.huawei.com/enterprise/, enter UltraPathin the search bar, and pressEnter to view or downloadthe document of the relevantversion.

CloudEngine 6800&5800 V100R002CXX ProductDocumentation

OceanStor SNS2124&SNS2224&SNS2248 Fibre ChannelSwitch V100R002CXX User Guide



31




Document Name How to Obtain

l OceanStor UltraPath for Linux V100R008CXX UserGuide

l OceanStor UltraPath for AIX V100R008CXX UserGuide

l OceanStor UltraPath for Solaris V100R008CXX UserGuide

l OceanStor UltraPath for vSphere V100R008CXX UserGuide

l OceanStor UltraPath for Windows V100R008CXX UserGuide

NOTEThis document uses productversions in Table 3-3 asexamples. If the onsite productversions are different fromthose in the document, Log into http://support.huawei.com/enterprise/, and obtain theVersion Mapping specific tothe product versions at yoursite and complete theconfiguration.

Business Continuity and Disaster Recovery SolutionV200R001CXX User Guide (Active-Active Mode)

HUAWEI Rack Server Product Documentation

3.2.2 Quick checklist for the installation environmentTo implement a correct and smooth device installation, ensure that the installationenvironment 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 lowtemperature, heavy dust, harmful gas, inflammable orexplosive materials, electromagnetic interference (nearbylarge-sized radar station, broadcast transmitting station, ortransformer station), unstable electric voltage, and largevibration or strong noise. Therefore, during the engineeringdesign, you need to consider hydrology, geography,earthquake, electric power, and transportation conditionsaccording to the technical requirements for communicationnetwork planning and communication devices.

2 Civil construction The size of the equipment room must be sufficient for productinstallation and capacity expansion. The floor can meet therequirements for the bearing weight. The cable slot, cableladder, and cable holes are complete or ready. The decorationis complete.



32





3 Operatingambienttemperature

l When the altitude is lower than 1800 m (5904 feet), theroom temperature of controller enclosures and diskenclosures must be kept within 5°C to 40°C (41°F to104°F), and that of high-density disk enclosures must bekept within 5°C to 35°C (41°F to 95°F).

l When the altitude ranges between 1800 m (5904 feet) and3000 m (9840 feet), the room temperature must be keptwithin 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 ParticleContaminants

l ISOa 14664-1 Class8.l You are advised to ask a professional organization to

monitor the particle contaminants in the equipment room.



33


6 CorrosiveAirborneContaminants

l Copper corrosion rate: less than 300 Åb/month per ANSIc/ISAd-71.04 severity level G1.

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 tomonitor the corrosive airborne contaminants in theequipment room.

l The following is an example of initial evaluation forenvironmental corrosion risks.– Whether the equipment room is near any sulfurous gas

emission sources, for example, porcelain factories,rubber plants, tire factories, chemical factories, sewageplants, power stations, paper mills, smelters,automobile factories, coal mines, electroplatingfactories, 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 risksmay exist.

– Whether the equipment room was decorated in thelatest six months? If yes, environmental corrosion risksmay 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 alwaysclosed? If no, environmental corrosion risks may exist.

7 Vibration andshock

l Operating vibration5 Hz to 300 Hz: 1.5 m/s2, 0.5 oct/min 3 axes, 1 sweepcycles per axis; 5 Hz to 500 Hz: 0.27 Grms, 3 axes, 10 minper axis

l Non-operating vibration5 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 shockHalf sine, 6 ms, 300 m/s2, 6 directions, 3 times perdirection

8 Air conditioner If the temperature in the room exceeds 35°C, you arerecommended to install air conditioners (which can berestarted after power-off). Do not let the air conditioner blowdirectly toward the devices.



34


9 Moisture-proofmeasures

If the relative humidity is greater than 70%, install thedehumidifying device, such as the air conditioner with thedehumidification function or special dehumidifier. Ensure thatthe equipment room is protected from water seepage and dew.

10 Heating For an environment where the average daily temperature islower than 5°C for at least 90 days each year, heating devicesare required. For an environment where the averagetemperature is lower than 5°C for 60 to 90 days each year,heating devices are recommended.

11 Ventilation andheat dissipation

To ensure smooth ventilation, the cabinet should be at least100 cm (39.4 inches) away from the walls and you shouldleave a clearance of at least 120 cm (47.28 inches) betweenthe cabinets. To keep a convective air transfer between thecabinet and the equipment room, no enclosed space is allowedin the cabinet. 1 U space should be left above and below eachdevice.

12 Dust-proofmeasures

For the equipment room near dust sources (such as coalmines, country roads, or farmland), use double-layeraluminum alloy windows for proper sealing and an anti-theftand fireproof door. Separate the devices from the door with apartition board to avoid dust.

13 Ground resistance Less than 10 Ω. The distance between the top of the groundterminal and the ground should be at least 0.7 m (27.58inches). In the cold regions, the ground terminal should beburied under the layer of frozen earth. Periodically monitorground resistance to ensure ground effectiveness.

14 Ground lead-in The ground bar in the equipment room should be connected tothe network of ground cables. The ground lead-in should notbe longer than 30 m (98.4 feet) and should use the zinc-coatedflat steel whose cross-sectional area is equal to or more than40 mm (1.57 inches) x 4 mm (0.157 inches). The contact pointshould be handled for insulation and anticorrosive purposes.The above-ground steel should be provided with measures toavoid mechanical damage and should be intact withoutsoldering points for the break.

15 Lightningprotection

The equipment room must be provided with lightningconductors such as the lightning rod or lightning belt. Thelightning conductors share the ground bars with the protectionground cables of the equipment room.



35


16 AC The AC distribution switches and AC power cables areproperly installed.The 2 U controller enclosurel 100 V to 240 V, ±10%, 10 A to 12 A, single-phase, 50/60

Hzl Supports dual-live-line input (2W+PE), 200 V to 240 V,

±10%The 3 U and 6 U controller enclosurel 200 V to 240 V, ±10%, 10 A, single-phase, 50/60 Hzl Supports dual-live-line input (2W+PE), 200 V to 240 V,

±10%Disk enclosurel 100 V to 240 V, ±10%, 10 A, single-phase, 50/60 HzHigh-density disk enclosurel 100 V to 127 V, ±10%, 10 A, single-phase, 50/60 Hzl 200 V to 240 V, ±10%, 5 A, single-phase, 50/60 Hz

17 High voltage DC The high voltage DC distribution switches and high voltageDC 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 Ucontroller 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 areproperly installed.l The DC power module of the 2 U controller enclosure: -48

V to -60 V, ±20%, 30 Al 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 breakersfrom being incorrectly powered off due to a power supplyfailure of the storage device, you are advised to ensure that theelectric current of the circuit breakers of the external powersupplies to which the storage device is connected complieswith the following specifications:l AC power supplies: greater than 16 Al DC power supplies: greater than 32 A



36


20 AC power ground Do not connect the neutral line of a power cable to theprotection ground bar of any communication devices in theequipment room. It is recommended that you set leading-outterminals for AC safety ground in the equipment room for theconnection to devices.

21 AC surgeprotection

The AC power system of the equipment room must beequipped with a lightning arrestor with the rated dischargingcurrent no less than 20 kA. The arrestor must be properlygrounded.

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 systemchassis are separated. The DC power module of the storagedevice does not provide any ground terminals. Therefore, thestorage device is grounded through the ground terminal of thesystem chassis.

23 Transmissiondevice

The debugging of the transmission device is complete, and thecapacity of the transmission device meets the engineeringrequirements. The protection ground of the transmissionsystem must be connected to the ground bar in the equipmentroom.

24 Cabinet The cabinet for installing the devices must be a standard 19-inch cabinet. The depth of the cabinet must be at least 1000mm (39.37 inches). The depth of a cabinet for installing high-density disk enclosures must be at least 1100 mm (43.31inches).

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.



37

NOTICEl 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 InstallationInstall devices as instructed in the following description to avoid unnecessary rework at yoursite.

Install devices in data center A, data center B, and a third-place quorum site. The followingcomponents are used as an example. Install devices based on onsite requirements. Theinstallation process is as follows:

InstallationSequence

Site Procedure

1 Data centerA

1. Install the storage devices. For details about how to install it, seethe Installation Guide of the corresponding product model.

2. Install CloudEngine 5800 series switches. For details about howto install a CloudEngine 5800 switch, see:l CloudEngine 7800&6800&5800 Hardware Installation and

Maintenance Guidel CloudEngine 7800&6800&5800 V100R005C00

Configuration GuideNOTE

If you use other switches, see the installation guide specific to theswitches at your site to install them.

3. Install SNS2248 series switches. For details about how to installan SNS2248 switch, see the OceanStorSNS2124&SNS2224&SNS2248 Fibre Channel SwitchV100R002C00 User Guide.NOTE




38

InstallationSequence

Site Procedure

2 Data centerB

1. Install the storage devices. For details about how to install it, seethe Installation Guide of the corresponding product model.





3. Install SNS2248 series switches. For details about how to installan SNS2248 switch, see the OceanStorSNS2124&SNS2224&SNS2248 Fibre Channel SwitchV100R002C00 User Guide.NOTE


3 Third-placequorumsite

1. Install the quorum server.NOTE

For details about how to install a quorum server, see the installationguide specific to the quorum server at your site.





For details about the device layout, see Figure 3-2 or Figure 3-3. The device models andnumber of devices depend on the onsite requirements.



39

Figure 3-2 Device layout (3 U storage device)

39 1U 1U 1U 1U 1U 1U38 1U 1U 1U 1U 1U 1U37 1U 1U 1U 1U 1U 1U36 1U 1U 1U 1U 1U 1U35 1U 1U 1U 1U 1U 1U34 1U 1U 1U 1U 1U 1U33 1U 1U 1U 1U 1U 1U32 1U 1U 1U 1U 1U 1U31 1U 1U 1U 1U 1U 1U30 1U 1U 1U 1U 1U 1U29 1U 1U 1U 1U 1U 1U28 1U 1U 1U 1U 1U 1U27 1U 1U 1U 1U 1U 1U26 1U 1U 1U 1U 1U 1U25 1U 1U 1U 1U 1U 1U24 1U 1U 1U 1U 1U 1U23 1U 1U 1U 1U 1U 1U22 1U 1U 1U 1U 1U 1U21 1U 1U 1U 1U 1U 1U20 1U 1U 1U 1U 1U 1U19 1U 1U 1U 1U 1U 1U18 1U 1U 1U 1U 1U 1U17 1U 1U 1U 1U 1U 1U16 1U 1U 1U 1U 1U 1U15 1U 1U 1U 1U 1U 1U14 1U 1U 1U 1U 1U 1U13 1U 1U 1U 1U 1U 1U12 1U 1U 1U 1U 1U 1U11 1U 1U 1U 1U 1U 1U10 1U 1U 1U 1U 1U 1U9 1U 1U 1U 1U 1U 1U8 1U 1U 1U 1U 1U 1U7 1U 1U 1U 1U 1U 1U6 1U 1U 1U 1U 1U 1U5 1U 1U 1U 1U 1U 1U4 1U 1U 1U 1U 1U 1U3 1U 1U 1U 1U 1U 1U2 1U 1U 1U 1U 1U 1U1 1U 1U 1U 1U 1U 1U

Data center 1Cabinet: H05

SNS2248Filler panel

Filler panelFiller panel

RH2288(sevice host)

Data center 2Cabinet: H05



Filler panel

Disk enclosure

Filler panel


Filler panel

SNS2248Filler panel

CE5800Filler panel

CE5800Filler panel


SNS2248

Filler panel

RH2288(sevice host)

Filler panel

Third-place quorum siteCabinet: H01

SNS2248 Filler panelFiller panel Filler panel

Filler panelFiller panel Filler panel

CE5800 CE5800Filler panel Filler panel

CE5800 CE5800Filler panel

Filler panel RH1288 V3 (quorum server)Filler panel Filler panelFiller panel Filler panelFiller panel Filler panel


Filler panel Filler panel

Disk enclosureFiller panelFiller panel

Disk enclosure Disk enclosureFiller panelFiller panelFiller panel

Filler panel Filler panel Filler panel

Controller enclosure Controller enclosureFiller panelFiller panelFiller panel

Filler panel Filler panelFiller panel Filler panel

Disk enclosure Disk enclosureFiller panelFiller panel

Disk enclosure Disk enclosureFiller panelFiller panel

Filler panel Filler panelFiller panel Filler panel Filler panelFiller panel Filler panel Filler panelFiller panel Filler panel Filler panel

Filler panel Filler panelFiller panel Filler panelFiller panel Filler panelFiller panel Filler panel

Figure 3-3 Device layout (6 U storage device)

42 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U41 1U 0U 1U 1U 1U 1U 1U 1U 1U 1U40 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U39 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U38 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U37 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U36 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U35 1U 1U 1U 1U 1U 1U 1U 1U 1U34 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U33 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U32 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U31 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U30 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U29 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U28 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U27 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U26 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U25 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U24 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U23 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U22 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U21 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U20 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U19 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U18 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U17 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U16 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U15 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U14 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U13 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U12 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U11 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U10 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U9 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U8 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U7 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U6 1U 1U 1U 1U 1U 1U 1U 1U 1U 1U

Diskenclosure

Filler panelFiller panel Filler panelFiller panel Filler panel

Diskenclosure

Filler panelFiller panel Filler panel

Sevice host Sevice host Filler panelFiller panel

Filler panelDisk

enclosure

Filler panelDisk

enclosure

Filler panelFiller panel Filler panel Filler panelFiller panel Filler panel Filler panel


Filler panelDisk

enclosure

Filler panel

Filler panel Filler panelFiller panel Filler panel Filler panel Filler panel Filler panel

CE5800 Filler panel CE5800 Filler panel Filler panel

CE5800 Filler panel CE5800

Engine

Filler panelFiller panel Filler panel Filler panelSNS2248 SNS2248 Filler panel


Engine

SNS2248

KVM Filler panelFiller panel Filler panel

Filler panel SVP Filler panel SVP Filler panel

KVM Filler panel

CE5800

Diskenclosure

Filler panelDisk

enclosure

Filler panelFiller panel CE5800Filler panel Filler panelFiller panel

Diskenclosure

Filler panelDisk

enclosureFiller panel Filler panelFiller panel Filler panelFiller panel Filler panel

RH 1288V3Filler panel

Data center 2 Third-place quorum siteFiller panel

Diskenclosure

Filler panelDisk

enclosure

Filler panelFiller panel Filler panel Filler panel

Filler panel Filler panelFiller panel Filler panel

Diskenclosure

Filler panelDisk

enclosure

Filler panelFiller panel Filler panelFiller panel Filler panel

Filler panelFiller panelFiller panel

SNS2248

Data center 1 Data center 1 Data center 2

Filler panel


Diskenclosure

Filler panel


Filler panelFiller panelFiller panelFiller panel

Filler panel

Filler panel

Filler panel


Filler panel




40

l Storage device layout

– To conveniently maintain and operate a controller enclosure, install it in the middleof 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 thecontroller 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 easiermanagement and minimum vibration transfer.

– Reserve 2 U space at the bottom of the cabinet to facilitate cabling, ventilation andheat 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 ConnectionHyperMetro 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 servicehosts are connected using cables in and across data centers.



41

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



42




43


NOTE

l The ports that are numbered in digits are connected using cables in data centers and the ports that arenumbered in upper-case letters are connected using cables across data centers.

l For details about cable connections between disk enclosures and controller enclosures, seeCascading 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 laterversions.

Fibre Channel networking is used as an example to explain cable connection principles. Fordetails, see Table 3-5.



44

Table 3-5 Cable connection principles

NetworkType

Cable Connection Principle

Networkbetween hostsand storagearrays

l Hosts and storage devices are connected through Fibre Channelswitches. Each data center has two Fibre Channel switches.

l Each Fibre Channel switch has at least N ports to connect hosts andstorage devices. N = 1 x Number of Servers + 2 x Number ofStorage Devices.

l Host-Fibre Channel switch connection: Each host has at least twoFibre Channel ports to connect two Fibre Channel switches of thedata center. It is recommended that the two ports be separated on twoHBAs.

l Storage device-Fibre Channel switch connection: Each controller hasat least two ports to connect two Fibre Channel switches of the datacenter. It is recommended that the two ports be separated on twoFibre Channel interface cards.

HyperMetroreplicationnetwork

l The HyperMetro replication network between storage devices usesFibre Channel switches for connection. Each data center has twoFibre Channel switches.

l Storage device-Fibre Channel switch connection: Each controller hastwo Fibre Channel ports to connect two Fibre Channel switches of thedata center. It is recommended that the two ports be separated on twoFibre Channel interface cards.

Same-citynetworkbetween datacenters

l Dense wavelength division multiplexing (DWDM) devices arerecommended for data center interconnection.

l If the HyperMetro replication network is a Fibre Channel network,Fibre Channel switches are cascaded in one-to-one mode. If theHyperMetro replication network is an IP network, Ethernet switchesare cascaded in one-to-one mode.

Arbitrationnetwork

l The quorum server is connected to storage devices through Ethernetswitches. Each data center has two Ethernet switches.

l Each controller of a storage device has one IP port to connect to oneEthernet switch of the data center.

l The quorum server is connected to Ethernet switches. It isrecommended that two IP ports be separated on two network adaptersto connect two Ethernet switches at the quorum site.

Managementnetwork

l An Ethernet switch is used for management. The managementnetwork ports of the host and controller are connected to one Ethernetswitch of the data center.

l You can use BCManager eReplication to manage networks. Fordetails, see Business Continuity and Disaster Recovery SolutionV200R001CXX User Guide (Active-Active Mode). For details abouthow to obtain the documentation, see 3.2.1 Preparing Tools, Meters,and Documentation.



45

3.5 Power-onAfter installing all devices, power on them and check their operating status. Ensure that alldevices and their hardware are properly installed. Otherwise, do not power on them.

Power-on Principlesl 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 powerengineers 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 PSEand PDE can provide power for PDs.

l You must use measuring instrument to check whether power supplies meet the followingrequirements 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 isturned off and the output voltage is within the normal range; all power switches of thePDs are turned off; the PDs are not short-circuited.

Check Before Power-onl Checking the device installation

Table 3-6 lists the check items.

Table 3-6 Device installation checklist

CheckItem

Normal Abnormal

Controllerenclosure

l Stably installed on the guiderails without displacement.

l Tightly screwed.

l Tilted.l Screws are loose or dropped

off.Diskenclosure

Switch

Host

Fillerpanel

The vacant slots in the cabinet arecovered by filler panels.

The vacant slots in the cabinet areexposed.

Entirety l All devices are stably installedwithout displacement.

l All screws are tightly screwed.

l One ore more devices aredisplaced.

l One or more devices are tilted.l Screws are loose or dropped

off.



46

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 ofthe cable ladder.

4 Troughs are used to route cables outside the cabinet and cables do notoverflow 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 distributionrequirements.

10 The power cables, grounding cables, and signal cables outside the cabinet arelaid separately with a distance of larger than 30 mm.

11 Cables are bound in a rectangular shape. (Single-core cables can be bound ina round shape.)

12 Cables are bent with a bend radius of greater than 60 mm at turning pointsand are not bundled at bend points.

13 Optical fibers are laid out without using force or having unnatural bends andsqueezes.

14 OT terminals of the power cables and grounding cables are welded orcrimped firmly.

15 Protection tubes or insulating adhesive plasters are used to wrap powercables, naked cables, and OT terminal stems of ground cables. There shouldbe no bare copper wires in OT terminals.

16 All cabinets and enclosures with metal or partially metal shells are correctlygrounded and connected.

17 Cables are correctly bundled at an even spacing. After cables are bundledwith cable ties, the excess parts of the cable ties are cut off without burrs. Allthe 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.



47

No. Check Item

20 Labels are attached to the power cables and grounding cables in the samedirection for users' convenient check.

Power-on Procedurel Step 1 Connect grounding cables.

a. Huawei is responsible for connecting grounding cables of storage devices andcabinets and checking whether ground resistance connectors are connected firmly.

b. Huawei is responsible for testing the ground resistance between storage cabinetsand the equipment room and checking whether ground resistance connectors areconnected 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) andswitches of PDFs and array cabinets.

b. The customer is responsible for using a multimeter to check the output voltage ofarray cabinets and PDFs and ensure that the output voltage is in a normal range andPSEs have sufficient redundant power supplies to meet power requirements ofstorage 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 > coreswitches > application hosts.

NOTE

Power on the next device only after the previous device is running properly. For detailsabout how to power on storage devices, see Powering On Devices in the Installation Guideof the corresponding product model.

b. The customer is responsible for checking the operating status of input power toensure that input power is stable during the power-on process of cabinets andstorage 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 theair vent.

l Check whether device indicators are normal.

NOTEFor details about device indicator status, see Powering On Devices in the Installation Guide ofthe corresponding product model.

l Log in to devices and check their operating status.



48

3.6 Storage Array InitializationAfter powering on a storage array, you must initialize it.

Storage array initialization includes configuring an initial IP address for the managementnetwork port as well as applying for and importing a license. For details about how toinitialize a storage array, see Initializing the Storage System in the Installation Guide of thecorresponding product model.

3.7 Multipathing Software InstallationThis section describes installation environment requirements, pre-installation preparations,and the installation procedure of multipathing software.

Context

Multipathing software must be installed for the HyperMetro solution. You can use eitherHuawei 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.

NOTEFor 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 onHuawei storage.

NOTEFor details on how to install third-party multipathing software, see Third-party MultipathingSoftware Installation.

3.7.1 UltraPath Software InstallationSelecting and managing paths between an application server and the storage system can berealized after the UltraPath software is installed.

Context

To ensure that link aggregation can be implemented in the scenario that a HyperMetro LUN ismapped to a host, install UltraPath on the host before configuring HyperMetro pairs.

Install UltraPath software following instructions in the relevant documentation. For detailsabout applicable software versions, see 1.2 License Requirements and CompatibleProducts. For details about how to obtain the documentation, see 3.2.1 Preparing Tools,Meters, and Documentation.

3.7.2 Third-party Multipathing Software InstallationThis section describes installation environment requirements, pre-installation preparations,and the installation procedure of third-party multipathing software.



49

Context

The operating systems type of third-party multipathing software supported by theHyperMetro, refer to the HyperMetro Configuration Guide for Huawei SAN StorageUsing 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 tohttp://support.huawei.com/enterprise/, enter Host Connectivity Guide Oracle in the search bar, and pressEnter to view or download the document of the relevant version.

3.8 Arbitration Software InstallationThis section describes how to install the arbitration software. Quorum server software needsto be installed only when a quorum server is used for HyperMetro.

Prerequisitesl 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 forquick deployment once the VM fails. For details, see 6.8 How Can I Use OVA Templates toQuickly Deploy Virtual Quorum Servers?.

l The validity period of the default arbitration certificate is 10 years (start from September2015). Ensure the system time of the quorum server is correct so that the defaultarbitration certificate is valid.

l Use a Secure Shell (SSH) tool such as Xshell, PuTTY to log in to the quorum server.

NOTETo ensure security of the operating system, you are advised to harden its security. For details abouthow to harden security of an operating system, see the official security operation guide of theoperating system.

Context

By default, the Ubuntu system uses dash upon the installation. However, the arbitrationsoftware must be installed in bash mode. Therefore, you must disable dash when installing thearbitration 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>



50

http://support.huawei.com/enterprise/docinforeader.action?contentId=DOC1000131291




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 toperiodically 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 isHuawei@SYS3. You are advised to periodically change your password for your account'ssecurity.

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 thedirectory 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 -installVerify 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.



51

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 thearbitration software under another user account, enter the user name after Enter an administratoraccount for the quorum server:[default: quorumsvr], for example, Enter an administratoraccount 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 thearbitration software is successfully installed, create a non-root user before installing the arbitrationsoftware and ensure that the non-root user can obtain the permissions of the following commands byrunning 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 catxxx 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 openthe arbitration software. If the arbitration software page is displayed, the arbitrationsoftware restarts successfully.XXX@Linux:~# qsadminstart 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 isinstalled 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.sh00:00:00 ./bin/quorum_serverd00: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 ProcedureAfter 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 ArbitrationSoftware.



52

4 Configuration

About This Chapter

This chapter describes how to configure HyperMetro, including configuration preparations,process, and procedures.

4.1 Configuration ProcessBefore configuring HyperMetro, you must know the configuration process to ensure smoothoperations.

4.2 Configuration PreparationsThis section describes prerequisites and documents that you must prepare before youconfigure HyperMetro.

4.3 Configuring SwitchThis section describes the configuration requirements of core switches and access switches atthe network layer and configuration procedure of the Fibre Channel switches at the storagelayer.

4.4 Configure Quorum Server SoftwareThis section describes how to configure the quorum server software. Quorum server softwareneeds to be configured only when a quorum server is used for HyperMetro.

4.5 Configuring Basic Storage ServicesThis section describes how to configure basic storage services for the HyperMetro.

4.6 Creating SAN HyperMetroThis chapter describes how to create a SAN HyperMetro.

4.7 Configure a Multipathing Policy for HostThis section describes how to configure the Multipathing software.

4.8 Verifying the ConfigurationAfter configured, you can view the status of the data on the local and remote storage systemsto check whether HyperMetro between the local and remote storage systems is successful.

OceanStor V3 SeriesHyperMetro Feature Guide for Block 4 Configuration


53

4.1 Configuration ProcessBefore configuring HyperMetro, you must know the configuration process to ensure smoothoperations.

Figure 4-1 shows the configuration process of HyperMetro.

Figure 4-1 Configuration process of HyperMetro

Start

Configuration Preparations.

Configuring Switch.

Configure a Multipathing Policy for Host.

Configure HyperMetro.

End

Configuring Quorum Server Software.

Mandatory sub-item

Optional sub-item

Mandatory item

Optional item

This operation is only performed on the local storage system.

Creating a HyperMetro Pair.


Creating a HyperMetro Domain.


Creating a Quorum Server.

This operation is performed on both the local and the peer remote storage systems.

Adding a Remote Device. This operation is only performed on the local storage system.

Checking the License File. This operation is performed on both the local and the peer remote storage systems.

Configure Basic Storage Services.

Verifying the Configuration

Creating a HyperMetro Consistency Group.

Table 4-1 describes the configuration procedure of HyperMetro.



54

Table 4-1 Configuration procedure of HyperMetro

ConfigurationProcedure

Description Operation Location

ConfigurationPreparations.

Describes prerequisites anddocuments that you must preparebefore you configure HyperMetro.

Local storage systems,remote storage systems andthird-place quorum servers.

Configuring Switch. Describes the configurationrequirements of core switches andaccess switches at the network layerand the configuration procedure ofFibre Channel switches at the storagelayer.Ethernet switches serve as the coreswitches and access switches at thenetwork layer and Fibre Channelswitches are used at the storage layer.

Switches.

ConfiguringQuorum ServerSoftware.

This section describes how toconfigure, and manage the quorumserver software.

Quorum servers.

Configuring BasicStorage Services

Configure the storage system todivide the storage space into LUNsand map them to application serversso that the application server can readand write the storage space providedby the storage system.

This operation isperformed on both thelocal and the peer remotestorage systems.



55


Description Operation Location

ConfigureHyperMetro:1. Check the

license file.2. Add a remote

device.3. Add the quorum

server.4. Create a

HyperMetrodomain.

5. Create aHyperMetro pair.

6. Create aHyperMetroconsistencygroup.

Describes how to check theHyperMetro license, add a remotedevice and quorum server, and createa HyperMetro domain andHyperMetro pair.

1. Check the license file.(This operation isperformed on both thelocal and the peerremote storagesystems.)

2. Add a remote device.(This operation is onlyperformed on the localstorage system.)

3. Add the quorum server.(This operation isperformed on both thelocal and the peerremote storagesystems.)

4. Create a HyperMetrodomain. (This operationis only performed onthe local storagesystem.)

5. Create a HyperMetropair. (This operation isonly performed on thelocal storage system.)

6. Create a HyperMetroconsistency group.(This operation is onlyperformed on the localstorage system.)

Configure aMultipathing Policyfor Host.

This section describes how toconfigure an UltraPath policy forHyperMetro. For HyperMetro, theUltraPath software is configured toimprove the I/O processing efficiencyand reduce the access latency.

Host.

4.2 Configuration PreparationsThis section describes prerequisites and documents that you must prepare before youconfigure 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.



56

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, seethe Impact and Restrictions section about the interaction among features.

l The required licenses have been applied and imported based on the license operationguide.

4.3 Configuring SwitchThis section describes the configuration requirements of core switches and access switches atthe network layer and configuration procedure of the Fibre Channel switches at the storagelayer.

Context

For the detailed configurations on switches (includes setting domain IDs, configuring thelong-distance mode for links, and creating a zone), see BC&DR Solution ProductDocumentation V200R001 (Active-Active Data Center).

4.4 Configure Quorum Server SoftwareThis section describes how to configure the quorum server software. Quorum server softwareneeds 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 serviceIP address and firewall.

1. Configure a service IP address for the quorum server.

NOTEIf two ports of the quorum server are not bonded, IP addresses of the two ports must be from differentnetwork segments. If the two ports of the quorum server are bonded, you only need to configure avirtual IP address for arbitration.

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



57



Figure 4-2 Configuration requirements of virtual network adapters

Table 4-2 Configuration requirements of virtual network adapters

Name ConfigurationRequirement

Example

Networkadapter2

vmnic0 connects tocontroller A of the localand remote storagesystems in the HyperMetropair.

n Switch name: vSwitch 1n Physical adapters name: vmnic0n Physical adapters IP addresses and

mask: 192.168.6.31/255.255.255.0

Networkadapter3

vmnic1 connects tocontroller B of the localand remote storagesystems in the HyperMetropair.


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 IPaddresses at two different network segments for arbitration ports. In this example,arbitration software is deployed on physical machines, and two ports of the quorumserver are not bonded. Table 4-3 lists configuration examples.

Table 4-3 Examples for configuring IP addresses of arbitration services

ArbitrationPort

Service IP Address Mask

Arbitrationport 1

192.168.6.31 255.255.255.0

Arbitrationport 2

192.168.7.31 255.255.255.0

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



58

arbitration ports as an example to describe how to modify the file. Modify the IPADDRin this file and then save the file.

NOTICEParameter STARTMODE must be set to auto.

XXX@Linux:~# vi /etc/sysconfig/network/ifcfg-eth1BOOTPROTO='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-eth2BOOTPROTO='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 restartcommand in any directory to enable the IP address configuration to take effect. Then runthe 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, theconfiguration takes effect.

XXX@Linux:~#ifconfigeth1 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 inet addr: 192.168.7.31 Bcast:192.168.7.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe2e:fba7/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)

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 addthe port ID of FW_SERVICES_EXT_TCP to 30002.



59

NOTE

– If you want to enable other ports for the firewall, add the port IDs to theFW_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 ofthe 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 restartcommand in any directory to restart the firewall. Then run the iptables -L command tocheck whether the firewall configuration takes effect. If the ACCEPT tcp -- anywhereanywhere tcp dpt:pago-services2 information is displayed in the command output, thefirewall 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 openthe arbitration software. The arbitration software page is displayed.

XXX@Linux:~# qsadminstart main!Waiting for connecting to server...admin:/>

NOTEAfter the arbitration software is started, run the help command to check help information and understandthe 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 IPaddress and port ID of the quorum server to the arbitration software for management.

admin:/>add server_ip ip=192.168.6.31 port=30002



60

Command executed succesfully.



NOTE

l Service IP addresses of the quorum server are used for interworking with the storage array when anarbitration server is added to the storage array. If two ports of the quorum server are not bonded, IPaddresses of the two ports must be from different network segments. If two ports of the quorumserver 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 thefirewall.

After configuration is complete, run the show server_ip command. If the command outputshows 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 300022 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 andprivate key of the storage systems and those of the quorum server with your own security certificate andprivate 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 thedevice information. The qs_certreq.csr file is generated in the /opt/quorum_server/export_import directory of the quorum server.admin:/>export tls_certCommand 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 ensuresecurity of the quorum server.

– After installing the arbitration software, you are advised to grant the Secure File TransferProtocol (SFTP) permission only to the /opt/quorum_server/export_import/ directory toensure 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 togenerate certificates.

3. Copy the certificates to the quorum server.After the certificates are generated, copy the certificate (such as qs_cert.crt) of thequorum server and the CA certificate (such as qs_cacert.crt) to the /opt/quorum_server/export_import directory of the 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.crtcert=qs_cert.crt command to import the certificates to the arbitration software.



61

admin:/>import tls_cert ca=qs_cacert.crt cert=qs_cert.crtCommand executed successfully.

5. After replacing certificates on the quorum server, replace the certificates on the local andremote storage arrays. For details, see Managing Certificates section.

Step 5 (Optional) Configure a whitelist.

After you replace a certificate, you must configure a whitelist.

NOTICEThe arbitration software allows a storage system to connect to the quorum server only afteryou configure a whitelist and add the SN of storage system to the arbitration software. If youreplace 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 thestorage 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 thestorage system SN to the arbitration software for management.admin:/>add white_list sn=XXXXXXXXXXXXXXXXXXXX

Command executed successfully.

3. (Optional) Run the change white_list enable_switch=no command to close the whitelistif 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

The arbitration software must be configured in user mode.

Procedure




62




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




Example

Networkadapter2



mask: 192.168.6.31/255.255.255.0

Networkadapter3



mask: 192.168.7.31/255.255.255.0





63


ArbitrationPort


Arbitrationport 1

192.168.6.31 255.255.255.0

Arbitrationport 2

192.168.7.31 255.255.255.0

Run the vi command to open the configuration file of the network adapter used by thequorum server for arbitration. The following uses network adapters eth1 and eth2 forarbitration ports as an example to describe how to modify the file. Modify the IPADDRand NETMASK in this file and then save the file.

NOTICEParameter ONBOOT must be set to yes.

XXX@Linux:~# vi /etc/sysconfig/network-scripts/ifcfg-eth1DEVICE=eth1 HWADDR=08:00:27:45:7A:E2 TYPE=Ethernet #UUID=e9f75670-fde9-4bf0-941e-c9a251341405ONBOOT=yes NM_CONTROLLED=noBOOTPROTO=static IPADDR=192.168.6.31 #IP address of network adapterNETMASK=255.255.255.0 #Subnet mask

XXX@Linux:~# vi /etc/sysconfig/network-scripts/ifcfg-eth2DEVICE=eth2 HWADDR=08:00:27:45:7A:EB TYPE=Ethernet #UUID=e9f75670-fde9-4bf0-941e-c9a251341406ONBOOT=yes NM_CONTROLLED=noBOOTPROTO=static IPADDR=192.168.7.31 #IP address of network adapterNETMASK=255.255.255.0 #Subnet mask


Enter the CLI of the quorum server, go to any directory, run the service network restartcommand in any directory to enable the IP address configuration to take effect. Then runthe 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, theconfiguration takes effect.

XXX@Linux:~#ifconfigeth1 Link encap:Ethernet HWaddr 08:00:27:45:7A:E2 inet addr: 192.168.6.31 Bcast:192.168.255.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



64

RX bytes:2916916679 (2781.7 Mb) TX bytes:720809 (703.9 Kb)

eth2 Link encap:Ethernet HWaddr 08:00:27:45:7A:EB inet addr: 192.168.7.31 Bcast:192.168.255.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe2e:fba7/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)


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 theport 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 -jACCEPT.

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 ACCEPTCOMMIT

NOTE

– If /etc/sysconfig/iptables does not exist or is empty, write all the preceding content into theconfiguration file.

– If /etc/sysconfig/iptables has content, add -I INPUT –p tcp –-dport=30002 –j ACCEPT at thebeginning 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 -IINPUT –p tcp –-dport=22 –j ACCEPT.

– If a virtual machine (VM) is used to deploy the arbitration software, enable the firewall port of thephysical machine where the VM is deployed.


Enter the CLI of the quorum server, go to any directory, run the service iptables restartcommand in any directory to restart the firewall. Then run the iptables -L command tocheck whether the firewall configuration takes effect. If the ACCEPT tcp -- anywhereanywhere tcp dpt:pago-services2 information is displayed in the command output, thefirewall configuration takes effect.

XXX@Linux:~# iptables -L . . . . . .ACCEPT tcp -- anywhere anywhere tcp dpt:pago-services2 . . . . . .



65











NOTE







NOTE





66

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 ensuresecurity of the 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.crtcert=qs_cert.crt command to import the certificates to the arbitration software.admin:/>import tls_cert ca=qs_cacert.crt cert=qs_cert.crtCommand executed successfully.






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 thestorage system SN to the arbitration software for management.



67

admin:/>add white_list sn=XXXXXXXXXXXXXXXXXXXX

Command executed successfully.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.3 Configuring the Arbitration Software (Ubuntu)This section describes how to configure the arbitration software in Ubuntu.

PrerequisitesThe arbitration software must be configured in user mode.

Procedure





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




68



Example

Networkadapter2



mask: 192.168.6.31/255.255.255.0

Networkadapter3



mask: 192.168.7.31/255.255.255.0




ArbitrationPort


Arbitrationport 1

192.168.6.31 255.255.255.0

Arbitrationport 2

192.168.7.31 255.255.255.0

Run the sudo vi /etc/network/interfaces command to open the configuration file of thenetwork adapter used by the quorum server for arbitration. The following uses networkadapters eth1 and eth2 for arbitration ports as an example to describe how to modify thefile. Modify the address and netmask in this file and then save the file.

NOTICEThe start mode must be set to auto.

XXX@ubuntu:~$sudo vi /etc/network/interfacesauto eth1 //The parameter must be set to auto.iface eth1 inet staticaddress 192.168.6.31gateway 192.168.6.1netmask 255.255.255.0

auto eth2 //The parameter must be set to auto.iface eth2 inet staticaddress 192.168.7.31



69

gateway 192.168.7.1netmask 255.255.255.0


Enter the CLI of the quorum server, go to any directory, run sudo ifdown eth1 and sudoifup eth1 command in any directory to restart the network adapter. Then run the ifconfigeth1 command to check whether the configuration takes effect. If the IP address that youconfigure is displayed in the command output, the configuration takes effect.

XXX@ubuntu:~$ifconfig eth1 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)

Enter the CLI of the quorum server, go to any directory, run sudo ifdown eth2 and sudoifup eth2 command in any directory to restart the network adapter. Then run the ifconfigeth2 command to check whether the configuration takes effect. If the IP address that youconfigure is displayed in the command output, the configuration takes effect.

XXX@ubuntu:~$ifconfig eth2 eth1 Link encap:Ethernet HWaddr 08:00:27:45:7A:EB inet addr: 192.168.7.31 Bcast:192.168.7.255 Mask:255.255.0.0 inet6 addr: fe80::a00:27ff:fe2e:fba7/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)


Enter the CLI of the quorum server, go to any directory, (take ufw as example), run thesudo 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/XXXcommand to add the port IDs to the firewall. For example, if you want to enable port 22, runthe sudo ufw allow 22/tcp command.

– If a virtual machine (VM) is used to deploy the arbitration software, enable the firewall port ofthe physical machine where the VM is deployed.

XXX@ubuntu:~$sudo ufw allow 30002/tcpRule addedRule added (v6)


Enter the CLI of the quorum server, go to any directory, run the sudo ufw statuscommand to check whether the firewall configuration takes effect. If the 30002/tcpALLOW Anywhere and 30002/tcp(v6) ALLOW Anywhere (v6) information isdisplayed in the command output, the firewall configuration takes effect.

XXX@ubuntu:~$sudo ufw statusTo Action From-- ------ ---- . . . . 30002/tcp ALLOW Anywhere



70

. . .30002/tcp (v6) ALLOW Anywhere (v6)











NOTE







NOTE





71

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 ensuresecurity of the 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.crtcert=qs_cert.crt command to import the certificates to the arbitration software.admin:/>import tls_cert ca=qs_cacert.crt cert=qs_cert.crtCommand executed successfully.






System Name : reppub_10.103.20.176 Health Status : Normal Running Status : Normal Total Capacity : 2.025TB SN : XXXXXXXXXXXXXXXXXXXX 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

2. In the CLI of the arbitration software, run the add white_list sn=? command to add thestorage system SN to the arbitration software for management.



72

admin:/>add white_list sn=XXXXXXXXXXXXXXXXXXXX


3. (Optional) Run the change white_list enable_switch=no command to close the whitelistif you do not need to configure it.

----End

4.5 Configuring Basic Storage ServicesThis section describes how to configure basic storage services for the HyperMetro.

Context

This document describes how to configure basic storage services for the HyperMetro. Fordetails about configuration process, see OceanStor V3 Series V300R006 Basic StorageService 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 storagearray and remote storage array.

Table 4-8 Storage space configuration procedures


Operation Location

Create a diskdomain.

This operation is performed on both the local and the peer remotestorage systems.NOTE

You are advised to use the same configuration when creating disk domains onthe local storage array and remote storage array.

Create a storagepool.

This operation is performed on both the local and the peer remotestorage systems.NOTE

You are advised to use the same configuration when creating storage pools onthe local storage array and remote storage array.

Create a LUN. This operation is performed on both the local and the peer remotestorage systems.NOTICE

l It is recommended that the local LUN and remote LUN have the sameattributes 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 LUNsin a HyperMetro pair must be the same when the LUNs map to the samehost. You can run the show host lun host_id=xx command on the storagearray to query information about LUNs mapping to a host. (xx indicatesthe host ID).

Create a LUNgroup.

This operation is performed on both the local and the peer remotestorage systems.



73


Operation Location

Configure hostconnectivity.


Create a host. This operation is performed on both the local and the peer remotestorage systems.

Create a host group. This operation is performed on both the local and the peer remotestorage systems.

(Optional)ConfigureChallengeHandshakeAuthenticationProtocol (CHAP)authentication(iSCSI connection).


(Optional) Create aport group.


Create a mappingview.

This operation is performed on both the local and the peer remotestorage systems.NOTICE

Both the local and remote LUNs in a HyperMetro pair must be mapped to ahost. However, before creating a HyperMetro pair, ensure that the remoteLUN 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 iscreated and the Pair Running Status becomes Normal, map the remoteLUN to the host.

NOTEWhen a large number of HyperMetro LUNs are created, to ensure that allHyperMetro LUNs are mapped to the host, you can run the show lunhyper_metro_pair lun_mapped=no command on the storage devices toview the HyperMetro LUNs that are not mapped to the host.

Enable anapplication serverto use storagespace.

This operation is performed on the host. After creating theHyperMetro pair, enable an application server to use storage space.NOTE

When LUNs provide storage space for SQL Server databases, you can adjustrelevant parameters to reduce the I/O latency and achieve the optimalperformance. For details, see 6.7 In the SQL Server database scenario,how can I adjust parameters to reduce the I/O latency and achieve theoptimal performance?.

4.6 Creating SAN HyperMetroThis chapter describes how to create a SAN HyperMetro.



74

4.6.1 Checking the License FileBefore configuring HyperMetro, ensure that the license file in use grants the permission to useHyperMetro.

Prerequisites

A license file that contains the HyperMetro license information has been imported into thestorage 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 (forLUN).

In a scenario where both SAN HyperMetro and NAS HyperMetro are required, you canpurchase the license for both file system and LUN. In the license file, HyperMetro License(for FS&LUN) is displayed.

PrecautionsThe capacity of the HyperMetro license for 18500 V3&18800 V3 storage systems must beequal to or larger than the total capacity of LUNs equipped with this feature. However, if thetotal capacity of the LUNs in a storage pool equipped with this feature is larger than that ofthe storage pool, use the capacity of the storage pool to calculate the capacity required for theHyperMetro license. The following is a capacity calculation example.

StoragePool Name

LUN Capacity(TotalCapacity ofThin andThick LUNs)

Capacity of theStorage Pool ToWhich LUNsBelong

License CapacityYou Must Applyfor the StoragePool

TotalLicenseCapacityYouMustApply

StoragePool001

5 GB 10 GB 5 GB ≥25 GB

StoragePool002

10 GB 10 GB 10 GB

StoragePool003

20 GB 10 GB 10 GB

Procedure

Step 1 Log in to DeviceManager.

Step 2 Choose Settings > License Management.

Step 3 Check the active license files.



75

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 asinstructed in the Installation Guide of the corresponding product model.

4.6.2 Adding a Remote DeviceThis operation enables you to establish a logical connection between a local storage deviceand a remote storage device for data transfer between the two devices.

Prerequisitesl 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


The link between a local storage device and a remote storage device can be a Fibre Channellink or an iSCSI link.

NOTE

l On a Fibre Channel network, clear zone configurations of ports connecting to the storage systemfrom the switch before adding the remote device. You are advised to allocate two ports in one zoneto 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.

NOTEWhen a large number of remote storage devices exist, you can select desired remote devices throughtheir WWNs. Click Home on DeviceManager. In the Basic Information area, you can view WWN.

Step 4 Set up the connection to the remote device.



76

NOTICEl 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 devicesuch 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 toadd 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, addtwo 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 datafunction can speed updata transfer in thescenario where iSCSIreplication links transferservice data betweenstorage arrays.

[Example]Enable

Controller Name of the localstorage device'scontroller connected tothe remote storagedevice.

[Example]XXX0.A

Local Port Local storage device'sEthernet port connectedto the remote storagedevice.NOTE

This host port cannot beused for Ethernet portbonding. Otherwise, theHyperMetro service fails.

[Example]XXX0.A0.P0

IP Address IP address of theEthernet port on theremote storage device.NOTE

This host port cannot beused for Ethernet portbonding. Otherwise, theHyperMetro service fails.

[Example]192.168.26.12



77


Username The user name of themachine-machine user.

[Value]mm_user

Password The password of themachine-machine user.

[Value]mm_user@storage

TCP/IP Port Ethernet port number onthe remote storagedevice.

[Example]3260

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 themachine-machine user.

[Value]mm_user

Password The password of themachine-machine user.

[Value]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 25km, you can run the following command to enable the fast write function to ensure linktransfer 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=XXXfast_write_enable=yes command to enable the fast write function. To obtain the valueof fc_port_id, run show port general. The function needs to be enabled on both thelocal 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 successfullyenabled.



78

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=XXXfast_write_enable=no command to disable the fast write function. To obtain the value oflink_id, run show remote_device link. The function needs to be enabled only on thelocal storage system. You can run the show remote_device link link_type=iSCSIlink_id=XXX command to query the status of this function. When the status of FastWrite 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 ServerThrough 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 improvingservice continuity.

Prerequisites

To enable quorum links to be added to storage arrays successfully, ensure the following itemsbefore 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 thesystem time of the quorum server is correct so that the default arbitration certificate isvalid.

l The service IP addresses of the quorum server are correctly configured and correctfirewall ports (30002) are enabled.

l The white list of the quorum server is configured correctly. (You do not need to checkthis item if the default security policy is used.)

l Service IP addresses have been configured for the service ports that are used to connectstorage arrays and the quorum server. In addition, the service IP address of the storagearrays and quorum server can ping through with each other. For details about how toconfigure service IP addresses for storage arrays, see OceanStor V3 Series V300R006Basic Storage Service Guide for Block. After configuring the service IP addresses, queryand 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 toadd 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 serverand the other becomes the standby quorum server.

Procedure




79

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 aquorum server.

[Example]192.168.0.8

Active Port Primary port ID of a quorumserver. The default port ID is30002.

[Value Range]The value ranges from 1 to65535.[Example]30002

Standby IP Address Standby IP address of aquorum server.

[Example]192.168.1.8

Standby Port Standby port ID of aquorum server. The defaultport ID is 30002.

[Value Range]The value ranges from 1 to65535.[Example]30002

Step 6 Optional: If you select Configure Later, you can configure the links between the quorumserver 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 preferredsite.

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 PortType 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.)



80

NOTETo ensure the reliability between quorum servers and storage devices, you are advised to add at least one linkbetween 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 anotherquorum server.

Step 10 Log in to the remote storage device, execute the steps above to configure quorum server forthe remote storage device.

----End

Follow-up Procedure

By default, a quorum server does not have policy routes. It can only receive and send data viaone IP port although it has two IP ports on the same network segment. As a result, after theport in use goes down, the other port cannot take over services. Log in to the quorum serverand configure routing policies for it. For details, see Active and Standby IP Ports AreConfigured on the Quorum Server. After the Port in Use Is Down, the Quorum ServerGoes Offline. Why?

4.6.4 Creating a HyperMetro DomainAfter configuring a remote device and a quorum server, you need to create a HyperMetrodomain for the remote and local devices, and the quorum server. When creating a HyperMetrodomain, you determine the relationships among the local device, remote device, and quorumserver in the domain.

Prerequisitesl 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 thearbitration software. Then, run command show server_ip to view the status of the local andremote storage devices. If they are both in the Established state, the quorum server has beenadded successfully.

Context

l A HyperMetro Domain supports one quorum server at most.l This operation is only performed on the local storage system.

Procedure




81

Step 2 Choose Data Protection > HyperMetro > HyperMetro Domain.

Step 3 Click Create.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 startwith a letter or digit.

Step 5 In the Remote Device area, select a remote device that you want to add to the HyperMetrodomain 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 HyperMetrodomain and click Next.

NOTE

If you select Configure Later, you can add the quorum server to the HyperMetro domain later. If a faultoccurs, the local and remote devices in the HyperMetro domain cannot use the arbitration mechanismprovided by the quorum server to determine which site can continue to provide services. By default, thedevice in Prior Service Site provides services.

Step 7 Click Next.The information summary is displayed.

Step 8 Click Finish.The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 9 Click Close.

----End

4.6.5 Creating a HyperMetro PairAfter specifying a HyperMetro domain (including local and remote devices and a quorumserver), device resources at two storage arrays, and data synchronization properties, you cancreate HyperMetro relationships for devices at the two storage arrays. After the HyperMetrorelationships are established, the quorum server and preferred site mechanism determinewhich site continues to provide services if a disaster occurs.

Prerequisitesl 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.

Contextl After HyperMetro pair is created, the WWN of the remote LUN is changed to the WWN

of the local LUN.



82

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.

Step 4 Click Create.The Create HyperMetro Pair Wizard dialog box is displayed.

Step 5 Select HyperMetro Domain, Resource Type and Host Multipathing Software for theHyperMetro and click Next.

Step 6 In Available Local Resources and Available Remote Resources, select local and remoteLUNs 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 relatedparameters.



83

Table 4-12 HyperMetro parameters


Speed Data replication speed of aHyperMetro.l Low: When the speed is

set to low, remotereplication will take along time. This value isapplicable to scenarioswhere the service load isheavy. The speed isnormally from 0 to 5MB/s.

l Medium: When thespeed is set to medium,remote replication willtake relatively shortperiod. This value isapplicable to scenarioswhere the service load isheavy. The speed isnormally from 10 to 20MB/s.

l High: When the speed isset to high, remotereplication will take ashort period. This valueis applicable to scenarioswhere the service load isrelatively light. Thespeed is normally from50 to 70 MB/s.

l Highest: When the speedis set to highest, remotereplication will becomplete in the shortestperiod. This value isapplicable to scenarioswhere the service load islight. The speed isnormally above 100MB/s.

[Value range]Possible values are Low,Medium, High, andHighest.NOTE

If the LUN for which you wantto implement HyperMetro iscarrying host services and it isdifficult to determine when thesystem is busy or idle, you areadvised to set the parameter toMedium to minimize theimpact on host services.

[Default value]Medium



84


Recovery Policy A recovery policydetermines whether thesystem automaticallysynchronizes data after aHyperMetro fault isrectified.l Automatic: The system

automaticallysynchronizes data.

l Manual: Thesynchronizationoperation must beperformed manually.

[Value range]Possible values areAutomatic and Manual.[Default value]Automatic

Initial Synchronization Initial synchronizationmethod for data at local andremote ends.

[Value range]l Local and remote data is

inconsistent. After thecreation is complete,manually synchronizedata.

l Data at the local andremote ends isconsistent.Synchronization is notrequired after thecreation is complete.

l Local and remote data isinconsistent. After thecreation is complete, datais automaticallysynchronized.

[Example]Local and remote data isinconsistent. After thecreation is complete, data isautomatically synchronized.

Step 9 Click Next.

Step 10 Optional: Add the HyperMetro pair into consistency group.

NOTEThe 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.



85

Table 4-13 Consistency group parameters


Name The name of theHyperMetro consistencygroup.

HyperMetroGroup_001

Description The description of theHyperMetro consistencygroup.

—



86


Speed Data replication speed of aHyperMetro.– Low: When the speed

is set to low, remotereplication will take along time. This value isapplicable to scenarioswhere the service loadis heavy. The speed isnormally from 0 to 5MB/s.

– Medium: When thespeed is set to medium,remote replication willtake relatively shortperiod. This value isapplicable to scenarioswhere the service loadis heavy. The speed isnormally from 10 to 20MB/s.

– High: When the speedis set to high, remotereplication will take ashort period. This valueis applicable toscenarios where theservice load isrelatively light. Thespeed is normally from50 to 70 MB/s.

– Highest: When thespeed is set to highest,remote replication willbe complete in theshortest period. Thisvalue is applicable toscenarios where theservice load is light.The speed is normallyabove 100 MB/s.

[Value range]Possible values are Low,Medium, High, andHighest.NOTE

If the LUN for which youwant to implementHyperMetro is carrying hostservices and it is difficult todetermine when the systemis busy or idle, you areadvised to set the parameterto Medium to minimize theimpact on host services.



87


Recovery Policy A recovery policydetermines whether thesystem automaticallysynchronizes data after aHyperMetro fault isrectified.– Automatic: The

system automaticallysynchronizes data.

– Manual: Thesynchronizationoperation must beperformed manually.

[Value range]Possible values areAutomatic and Manual.[Default value]Automatic

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 thisoperation. and click OK.

----End

Follow-up ProcedureBoth 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 theHyperMetro pair is not mapped to a host. Otherwise, the HyperMetro pair may fail to becreated. 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 UltraPathUser Guide specific to your host operating system.

4.6.6 Creating a HyperMetro Consistency GroupIf an application or one type of services requires multiple HyperMetro LUNs and a preferableservice site needs to be determined by the system or quorum server upon faults, you need toadd owning HyperMetro LUNs of the application and services to a same HyperMetroconsistency group for unified maintenance.

Prerequisitesl 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 consistencygroup.



88

l Before creating a HyperMetro consistency group, stop the HyperMetro pair to be addedto the consistency group.

ContextThis operation is only performed on the local storage system.

Procedure


Step 2 Choose Data Protection > HyperMetro > HyperMetro Pair > HyperMetroConsistency Group.

Step 3 Click Create.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 HyperMetroconsistency group.

HyperMetroGroup_001


—

HyperMetro Domain HyperMetro domain to whichthe HyperMetro consistencygroup belongs. TheHyperMetro pair inHyperMetro consistency groupmust belong to the sameHyperMetro domain.NOTE

Click Create to create aHyperMetro domain in the dialogbox that is displayed.

HyperMetroDomain_001

Step 5 Click Next.

Step 6 Set the properties for the HyperMetro consistency group. Table 4-15 describes relatedparameters.



89

Table 4-15 HyperMetro consistency group properties


Speed Data replication speed of aHyperMetro.l Low: When the speed is set

to low, remote replicationwill take a long time. Thisvalue is applicable toscenarios where the serviceload is heavy. The speed isnormally from 0 to 5 MB/s.

l Medium: When the speedis set to medium, remotereplication will takerelatively short period. Thisvalue is applicable toscenarios where the serviceload is heavy. The speed isnormally from 10 to 20MB/s.

l High: When the speed isset to high, remotereplication will take a shortperiod. This value isapplicable to scenarioswhere the service load isrelatively light. The speedis normally from 50 to 70MB/s.

l Highest: When the speed isset to highest, remotereplication will be completein the shortest period. Thisvalue is applicable toscenarios where the serviceload is light. The speed isnormally above 100 MB/s.

[Value range]Possible values are Low,Medium, High, and Highest.NOTE

If the LUN for which you want toimplement HyperMetro iscarrying host services and it isdifficult to determine when thesystem is busy or idle, you areadvised to set the parameter toMedium to minimize the impacton host services.

[Default value]Medium



90


Recovery Policy A recovery policy determineswhether the systemautomatically synchronizesdata after a HyperMetro faultis rectified.l Automatic: The system

automatically synchronizesdata.

l Manual: Thesynchronization operationmust be performedmanually.

[Value range]Possible values are Automaticand Manual.[Default value]Automatic

Step 7 Click Next.

Step 8 In Available HyperMetro Pairs select the HyperMetro pair, and click to add theselected 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 HostThis section describes how to configure the Multipathing software.

ContextMultipathing software must be installed for the HyperMetro solution. You can use eitherHuawei 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.

NOTEFor 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 onHuawei storage.

NOTEFor details on how to configure third-party multipathing software, see Configuring a Third-partyMultipathing Policy for Host.



91

4.7.1 Configuring a UltraPath Policy for HostThis section describes how to configure the UltraPath software. For HyperMetro, theUltraPath software is configured to improve the I/O processing efficiency and reduce theaccess latency.

Context

In UltraPath, the local storage array is granted with the prior read and write permission. Thelocal storage array is preferentially used to process host services. If the local storage arraymalfunctions, the remote storage array will be used. In this way, service response efficiency isimproved 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 asit is not needed.

NOTEFor 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 applicationservers.

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 ofOceanStor 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 parametersin the command.

Table 4-16 Parameter description

Keyword andParameter

Description Default Value

workingmode={ priority | balance }

Used to specify theHyperMetro workingmode.n priority: preferred

storage array moden balance: load

balancing mode

prioritypriority isrecommended. balanceis applicable to scenarioswhere the two active-active data centers are inthe same building.



92



primary_array_id=ID ID of the preferredstorage array. The ID isallocated by UltraPath.The storage array in thedata center in which theapplication hosts resideis selected.Run the command toobtain the ID of thestorage array:n Linux: upadmin

show arrayn Windows/AIX/

Solaris: upadm showarray

NOTEn When workingmode

is set to priority, thevalue of the parameterindicates the storagearray to which I/Os arepreferentiallydelivered.

n When workingmodeis set to balance, thevalue of the parameterindicates the storagearray where the firstslice section resides.

NoneNOTE

Mapping relationshipbetween application hostsand storage arrays:

n If the preferred storagearray is configured forall application hosts indata center A, selectstorage array A.

n If the preferred storagearray is configured forall application hosts indata center B, selectstorage array B.

vlun_id={ ID |ID1,ID2... | ID1-ID2 }

ID of a virtualHyperMetro LUN. TheID is allocated byUltraPath.Run show vluntype=hypermetro toobtain the ID of a virtualHyperMetro LUN.

None

Instruction for UseThis command is used to set the HyperMetro working mode of storage arrays andvirtual 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 hypermetroworkingmode=priority primary_array_id=0.

n To set the HyperMetro working mode of virtual LUN 0 to balance and specifyarray 0 as the storage array where the first slice section resides, run sethypermetro workingmode=balance primary_array_id=0 vlun_id=0.



93

The HyperMetro working mode of a virtual LUN has a higher priority than that setfor all storage systems. To obtain better performance, you are advised to set theHyperMetro 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



-m mode Used to specify theHyperMetro workingmode.n priority: preferred

storage array moden balance: load

balancing mode

prioritypriority isrecommended. balanceis applicable to scenarioswhere the two active-active data centers are inthe same building.

-p primary_array_id ID of the preferredstorage array. The ID isallocated by UltraPath.The storage array in thedata center in which theapplication hosts resideis selected.Run esxcli upadm showdiskarray to obtain theID of the storage array.NOTEn When -m is set to

priority, the value ofthe parameterindicates the storagearray to which I/Os arepreferentiallydelivered.

n When -m is set tobalance, the value ofthe parameterindicates the storagearray where the firstslice section resides.

NoneNOTE

Mapping relationshipbetween application hostsand storage arrays:

n If the preferred storagearray is configured forall application hosts indata center A, selectstorage array A.

n If the preferred storagearray is configured forall application hosts indata center B, selectstorage array B.



94



[-l vlun_id] ID of a virtualHyperMetro LUN. TheID is allocated byUltraPath.Run show vluntype=hypermetro toobtain the ID of a virtualHyperMetro LUN.

None

Instruction for UseThis command is used to set the HyperMetro working mode of storage arrays andvirtual 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 sethypermetro -m balance -p 0 -l 0.

The HyperMetro working mode of a virtual LUN has a higher priority than that setfor all storage systems. To obtain better performance, you are advised to set theHyperMetro 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 operatingsystem type:l Linux: upadmin show upconfigl Windows/AIX/Solaris: upadm show upconfigl vSphere: esxcli upadm show upconfig

NOTEIn Linux, add the upadmin prefix to a command to log in to the CLI of OceanStor UltraPath. InWindows/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 anexample.HyperMetro WorkingMode : read write within primary array



95

Figure 4-5 Querying UltraPath configurations

Step 3 Optional: (for vSphere) Enable the APD to PDL function of ESXi hosts.

NOTEThe 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===============================================================



96

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 10GESAN, 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, skipthis 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 Policyfor Host

This section introduces the operation procedure for configuring third-party multipathingsoftware.

ContextIf the customer needs to use non-Huawei multipathing software (such as HP-UNIX NMP andPV-Links, OpenVMS DM-MultiPath, and Oracle DM-MultiPath) on the application server,



97

the function of using third-party multipathing software for initiators must be enabled onHuawei 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.

NOTEYou need to restart the host after modifying the host initiator information for the configuration to take effect.



98

Figure 4-6 Modify Initiator

For third-party multipathing policies of different operating systems, see the HyperMetroConfiguration Guide for Huawei SAN Storage Using OS Native Multipathing Softwareto 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.



99



This document only describes the configuration required for connecting Huawei storage tothird-party multipathing software. For details about third-party multipathing softwareconfiguration for host, refer to the HyperMetro Configuration Guide for Huawei SANStorage Using OS Native Multipathing Software.

----End

4.8 Verifying the ConfigurationAfter configured, you can view the status of the data on the local and remote storage systemsto check whether HyperMetro between the local and remote storage systems is successful.

After the HyperMetro configuration is complete, synchronize the HyperMetro pair. If PairRunning Status is Normal after the synchronization, HyperMetro has been configuredsuccessfully.

To verify the reliability and business continuity–related functions of HyperMetro, see sectionAcceptance of HyperMetro in the Acceptance Test Guide of the corresponding productmodel.



100



5 Management

About This Chapter

This chapter describes how to manage HyperMetro, HyperMetro domains, and the quorumserver.

5.1 Managing a HyperMetro PairAfter creating a HyperMetro, you may need to manage it due to service adjustment, disasterrecovery, data testing, or new data security requirements.

5.2 Managing HyperMetro DomainsBy managing HyperMetro domains, you can modify quorum servers configured inHyperMetro domains, and delete unnecessary HyperMetro domains as required.

5.3 Managing Quorum ServersBy managing quorum servers, you can create and delete quorum servers, and add links forquorum servers.

5.4 Managing a HyperMetro Consistency GroupA consistency group consists of multiple HyperMetro pairs and manages all pairs in itcentrally.

5.5 Importing CertificatesWhen the storage system is communicating with an external device, you are advised to usethe certificate verification mode to improve service security. This chapter describes how togenerate and export a certificate signing request, and import and activate the signedcertificate.

5.1 Managing a HyperMetro PairAfter creating a HyperMetro, you may need to manage it due to service adjustment, disasterrecovery, data testing, or new data security requirements.

OceanStor V3 SeriesHyperMetro Feature Guide for Block 5 Management


101

5.1.1 Viewing HyperMetro Pair InformationThrough this operation, you can view information about a HyperMetro including its basicinformation and HyperMetro pair information, so that you can effectively monitor theoperating status of the HyperMetro.

Context

l On the HyperMetro management page, you can click Refresh to refresh HyperMetroinformation.

l On the HyperMetro management page, click Keyword to search for keywords that arerequired for HyperMetro information viewing.

l On the HyperMetro management page, click and select HyperMetro information thatyou want to view.

Procedure



Step 3 Click the HyperMetro Pair tab.The HyperMetro Pair management page is displayed.

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 andremote resources in aHyperMetro.

None

Pair Health Status Displays whether a pair oflocal and remote resourcesin a HyperMetro are healthy.Possible values can beNormal and Fault.

[Example]Normal



102


Pair Running Status Running status of a pair oflocal and remote resources.Possible values can beNormal, To besynchronized, Paused,Synchronizing, ForceStart, and Invalid.

[Example]Normal

Time Remaining forSynchronization

Time required forsynchronization tocomplete.NOTE

Some product models and filesystems do not support thisparameter.

[Example]00:01:29

Link Status Status of a link connected toa HyperMetro.

[Example]Connected

Configuration Status Whether primary andsecondary siteconfigurations aresynchronized. The value canbe Synchronizing, Normal,or To Be Synchronized.Because SAN HyperMetrodoes not supportConfiguration Status, -- isdisplayed in theConfiguration Statuscolumn.

[Example]Normal

HyperMetro ConsistencyGroup

Name of the owningconsistency group of theHyperMetro pair.

[Example]ConsistentGroup001

Local Resource Role Whether the local resourceis provided by the preferredsite.

[Example]Preferred

Activation Status Activation status of site. Thevalue can be Active orPassive.

[Example]Active



103


Recovery Policy A recovery policy supportsthe following recoverymodes:l Manual: If a

HyperMetro pair is in theTo be synchronizedstate, management andmaintenance personnelneed to manuallyperform the Synchronizeoperation on theHyperMetro pair basedon site requirements, sothat data synchronizationcan be performedbetween the local andremote resources.

l Automatic: If aHyperMetro pair is in theSynchronizing state, thesystem automatically andincrementallysynchronizes differentialdata from the primaryresource to the secondaryresource based on siterequirements.

[Example]Automatic

Owning HyperMetroDomain

HyperMetro domain towhich a HyperMetrobelongs.

[Example]domain01

Local Resource Data Status Data status of a localresource.

[Example]Consistent

Remote Resource DataStatus

Data status of a remoteresource.

[Example]Consistent

Local Resource Host AccessStatus

Host access status of a localresource.

[Example]Read-Write

Remote Resource HostAccess Status

Host access status of aremote resource.

[Example]Read-Write



104


Isolation Switch After the Isolation Switchis turned on, the system willsuspend the HyperMetropair when the differencebetween the write I/Olatency of the two storagearrays is greater than theisolation switch. The storagearray with the longer writeI/O latency will stopproviding services.

[Example]Disabled

Isolation Threshold (ms) Write I/O latency differencebetween the host andHyperMetro storage arrays.

[Value range]The value must be aninteger from 10 to 30000.The unit is millisecond.

Data SynchronizationDirection

Data synchronizationdirection. Possible valuesare Local to Remote andRemote to Local.

[Example]Local to Remote

Step 5 Click a HyperMetro whose information you want to view and view its HyperMetro pairinformation 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 remoteresource.

None

Remote Device Name of a remote device. None



105





[Example]Automatic

Speed Speed of datasynchronization between theprimary resource andsecondary resource. Possiblevalues are Low, Medium,High, and Highest.

[Example]High

Start Time Time when datasynchronization for aHyperMetro starts.

[Format]YYYY-MM-DD hh:mm:ssUTC+hh:mm[Example]2014-05-30 16:51:32 UTC+08:00

End Time Time when datasynchronization for aHyperMetro ends.

[Format]YYYY-MM-DD hh:mm:ssUTC+hh:mm[Example]2014-05-30 20:51:32 UTC+08:00


[Example]Disabled

----End



106

5.1.2 Modifying HyperMetro Pair PropertiesThrough this operation, you can modify the speed and recovery policy of a HyperMetro pair.

PrerequisitesA 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. Clickthe Synchronize Information tab to modify related parameters. Table 5-3 explains therelated parameters.



107

Table 5-3 Parameters of HyperMetro properties


Speed Data replication speed of aHyperMetro pair.l Low: Data replication

takes a relatively longtime. This value isapplicable to scenarioswhere the service load isheavy. The speed rangesfrom 0 MB/s to 5 MB/s.

l Medium: Datareplication takes arelatively short time.This value is applicableto scenarios where theservice load is relativelyheavy. The speed rangesfrom 10 MB/s to 20MB/s.

l High: Data replicationtakes a short time. Thisvalue is applicable toscenarios where theservice load is relativelylight. The speed rangesfrom 50 MB/s to 70MB/s.

l Highest: Data replicationtakes the shortest time.This value is applicableto scenarios where theservice load is light. Thespeed is greater than 100MB/s.

[Value range]Possible values are Low,Medium, High, andHighest.




[Value range]Possible values areAutomatic and Manual.



108



[Example]Disabled


[Example]500

----End

5.1.3 Synchronizing a HyperMetro PairThrough this operation, ensuring data consistency between the storage arrays in two datacenters.

Prerequisites

The running status of a HyperMetro pair must be Paused, To be synchronized, or ForceStart (The connection of devices is normal).

Procedure




Step 4 Right-click a HyperMetro pair whose data you want to synchronize and choose Synchronizefrom the short-cut menu.The security alert dialog box is displayed.

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.The Success dialog box is displayed, indicating that the operation succeeded.

2. Click OK.

----End



109

5.1.4 Suspending a HyperMetro PairIf you need to stop service for one site due to site failure or other reasons, select thecorresponding site of the HyperMetro pair. Pausing may cause the data inconsistency on bothsites.

Prerequisites

The Running Status of HyperMetro pair is Normal or Synchronizing (The connection ofdevices 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 shortcutmenu.

Step 4 Select Preferred or Non-Preferred site and click OK.The security alert dialog box is displayed.

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 alsosuspended.

----End

5.1.5 Switching the Preferred Site for a HyperMetroThrough 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 besynchronized, Force Start or Paused (The connection of devices is normal).

Procedure





110

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.The security alert dialog box is displayed.

Step 4 Confirm the operation to switch the preferred site.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.The Success dialog box is displayed, indicating that the operation succeeded.

2. Click OK.

----End

5.1.6 Forcibly Enabling a HyperMetro PairIf a system fault occurs or the quorum server fails, you can forcibly enable the local or remotesite to allow it to continue to provide services.

Prerequisites

l The following requirements must be met before performing this operation: Link Statusand Running Status of the HyperMetro pair is Disconnected and Paused or To besynchronized, 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 quorumserver 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 isAccess denied before forcibly starting a HyperMetro pair.On the remote storage system, run the show hyper_metro_pair generalpair_id=XXXXX command to query the host access status of the remote LUN.admin:/>show hyper_metro_pair general pair_id=e4a8b61a08bd0000 ID : 3400a30d9a6c0000 Health Status : Normal 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



111

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 isAccess 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 remoteLUN. 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 encountersconcurrent faults, the storage array at the preferred site malfunctions and cannot take over theHyperMetro service. As a result, the HyperMetro service stops. Forcibly start the service atthe non-preferred site to restore the HyperMetro service.

When HyperMetro works in Static Priority Mode or the HyperMetro service encountersconcurrent faults, if one storage system can carry services, do not forcibly start the faultystorage system to carry host services.

Procedure




Step 4 Right-click a HyperMetro pair that you want to enable forcibly and choose Force Start fromthe short-cut menu.The security alert dialog box is displayed.

Step 5 Confirm the operation to forcibly enable the HyperMetro pair.

1. Confirm the information in the dialog box and select I have read and understand theconsequences associated with performing this operation.. Then click OK.The Success dialog box is displayed, indicating that the operation succeeded.

2. Click OK.

----End

5.1.7 Deleting a HyperMetro PairIf 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, ForceStart or To be synchronized, and its secondary LUNs are not mapped.



112

Procedure



Step 3 Select a HyperMetro that you want to delete and click Delete.The security alert dialog box is displayed.

Step 4 Optional: Select Only delete the configuration information about the local device if theHyperMetro 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 isdisconnected from the remote device.

Step 5 Optional: Select Stop the LUN service of this device based on site requirements.

NOTEThis operation must be performed on the local site or remote site (you are advised to set "Local ResourceHost Access Status" as an "Access denied" storage device). After this operation, the WWN of the LUN on thestorage device will change. Rescan the LUN on the host. If the LUN service is not stopped on bothHyperMetro sites, there is risk of data inconsistency.


Step 7 The Execution Result dialog box is displayed indicating that the operation succeeded.

NOTEAfter deleting a HyperMetro pair, scan for storage resources on the host to ensure that the host can correctlyidentify the storage resources mapped to it.

----End

5.1.8 Expanding the Capacity of a HyperMetro LUNIf LUN space is insufficient to store service data, you can expand the LUN capacity to meetyour service requirements.

Context

Before expanding the capacities of HyperMetro LUNs, you must delete the HyperMetro pairwhere the LUNs reside. The following describes how to expand the capacities of HyperMetroLUNs.

NOTEIn the following, the primary LUN is the HyperMetro LUN that provides services and the secondary LUN isthe HyperMetro LUN that stops providing services.

Procedurel Offline expansion (In scenarios where the CPU usage and disk usage exceed 50%, the

HyperMetro replication bandwidth is insufficient, or the distance between data centersexceeds 25 km).a. Stop upper-layer services.



113

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

corresponding product model.

f. Create a HyperMetro pair.

NOTE

l Select The data at the local and remote ends is consistent. Synchronization is notrequired after the creation is complete. option.

l The storage arrays on which a HyperMetro pair is created before or after capacity expansionmust be the same to ensure that the data synchronization directions of the HyperMetro pair arethe same. For example, if you create a HyperMetro pair on the storage array at the preferredsite before capacity expansion, create it again on the storage array at the preferred site aftercapacity 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 centersis relatively short).a. Pause the HyperMetro pair.

NOTEIn 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

corresponding product model.

e. On the storage array of the preferred site, create a HyperMetro pair.

NOTESelect the Local and remote data is inconsistent. After the creation is complete, data isautomatically synchronized. option.

f. Map the secondary LUN to the host.g. On the host, scan for LUNs.

----End

5.2 Managing HyperMetro DomainsBy managing HyperMetro domains, you can modify quorum servers configured inHyperMetro domains, and delete unnecessary HyperMetro domains as required.



114

5.2.1 Viewing HyperMetro Domain InformationThrough this operation, you can view remote device and quorum server information in aHyperMetro 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 relatedparameters.

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 noquorum server is created.

Quorum Server Quorum server in a HyperMetro domain.NOTE

When two quorum servers are configured inV300R006C10 and later versions, informationabout both will be displayed.

----End

5.2.2 Modifying a HyperMetro DomainWhen a quorum server in a HyperMetro domain has been modified, you can modify theHyperMetro domain to modify the quorum server in the domain.

Prerequisites

A HyperMetro domain has been successfully configured for the storage system.



115

Procedure



Step 3 Choose Properties. The Properties of HyperMetro Domain dialog box is displayed.

NOTEAlternatively, 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 quorumservers 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 DomainIf 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.The security alert dialog box is displayed.

Step 4 Select Only delete the configuration information about the local device if the local deviceis 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



116

5.3 Managing Quorum ServersBy managing quorum servers, you can create and delete quorum servers, and add links forquorum servers.

5.3.1 Viewing Quorum Server InformationThrough this operation, you can view information about existing quorum servers as well aslinks 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 describesrelated parameters.

Table 5-6 Quorum server link parameters


Controller Controller of a local device connecting to aquorum server.

Port Controller port of a local device connectingto a quorum server.

IP Address The IP address of a quorum server.

Running Status Running status of a link.

----End



117

5.3.2 Modifying Quorum Server InformationThrough this operation, you can modify the properties of a quorum server and authenticationinformation 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-7explains the related parameters.



Name Name of a quorum server. [Example]QuorumServer_001

Description Description of a quorumserver.

[Example]None

Active IP Address Primary IP address of aquorum server.

[Example]192.168.0.1

Primary Port Primary port ID of a quorumserver. The default port ID is30002.NOTE

The port ID ranges from 1 to65535.

[Example]30002

Standby IP Address Standby IP address of aquorum server.

[Example]None

Standby Port Standby port ID of aquorum server.NOTE

The port ID ranges from 1 to65535.

[Example]None

Step 5 Click OK.

----End

5.3.3 Adding a LinkThrough this operation, you can add a link for a quorum server.



118

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.

NOTETo ensure the reliability between quorum servers and storage systems, you are advised to add at least one linkbetween each controller of storage systems and a quorum server.

Step 5 Click OK.

----End

5.3.4 Removing a LinkThrough 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 Linkarea.

NOTETo ensure the reliability between quorum servers and storage systems, you are advised to add at least one linkbetween each controller of storage systems and a quorum server.

Step 4 Select I have read and understand the consequences associated with performing thisoperation. and click OK.The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 5 Click Close.

----End

5.3.5 Removing a Quorum ServerThrough this operation, you can delete quorum servers that have been created.

PrerequisitesThe quorum server has not been created to the Hypermetro domain.

Procedure




119


Step 3 Select a quorum server that you want to remove and click Delete.The security alert dialog box is displayed.

Step 4 Select I have read and understand the consequences associated with performing thisoperation. and click OK.The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 5 Click Close.

----End

5.3.6 Uninstalling the Arbitration SoftwareThis section describes how to uninstall the arbitration software.

Prerequisites

The arbitration software has been correctly installed, and the arbitration software packageexists. Only user root or the arbitration software management user can uninstall thearbitration software.

NOTE

The arbitration software management user is the user created during the arbitration software installation. Youcan run the ls -l /opt/quorum_server/bin/quorum_serverd command to query information about thearbitration 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.zippackage/package/quorum_server.shpackage/packages/package/packages/QuorumServer-VXXXRXXXCXX-linux.x86_64.rpmpackage/qs_version.inipackage/tools/

2. After decompressing the installation package, run the cd package command to go to thedecompressed 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 -uninstallUninstall quorum server.The QuorumServer uninstallation starts.Uninstall... ########################################### [100%] QuorumServer ########################################### [100%]Do you want to backup configuration and log?<Y|N>:yQuorumServer install success completed.

Step 3 (Optional) Check whether the arbitration software is uninstalled successfully.



120

1. When the uninstallation progress is completed, run the ps -elf | grep quorum_serverdcommand to check whether the arbitration software is uninstalled successfully.

2. If the quorum_serverd process does not exist, the arbitration software is uninstalledsuccessfully.XXX@Linux:~/package # ps -elf | grep quorum_serverd0 S root 3326 32197 50 80 0 - 2449 pipe_w 17:03 pts/0 00:00:00 grep quorum_serverdXXX@Linux:~/package #

----End

5.4 Managing a HyperMetro Consistency GroupA consistency group consists of multiple HyperMetro pairs and manages all pairs in itcentrally.

5.4.1 Viewing the HyperMetro Consistency Group InformationThis operation allows you to view information about consistency groups to monitor the statusof consistency groups.

ContextOperating status of consistency groups: The operating status of a consistency group and itsHyperMetro pairs must be the same. Only HyperMetro pairs in the Paused or Normal statecan be added to consistency groups.

Procedure



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 consistencygroup.

ID The ID of the HyperMetro consistencygroup.



121


Health Status Indicates whether the consistency group isfunctioning normally. The values include:l Normal: The consistency group is

functioning normally.l Fault: The consistency group

malfunctions or the replication link isdown.

Running Status Indicates the consistency group is runningproperly. The values include:l Normal: Consistency group has

completed synchronization successfully.l To be synchronized: The data of

consistency group is inconsistent andneed to be synchronized.

l Paused: Consistency group is in thepause status, and the synchronization issuspended.

l Synchronizing: Consistency group issynchronizing data.

l Force Start: Consistency group forciblyenables the local or remote site tomanually allow the local or remote siteto continue to provide services.

l Invalid: Consistency group is uselessand cannot be restored in this status,except deleting it.

Local Resource Role Whether the local site is prior service site ornot. Including Preferred and Non-Preferred.

Recovery Policy A recovery policy determines whether thesystem automatically synchronizes dataafter a HyperMetro consistency group faultis rectified.l Automatic: The system automatically

synchronizes data.l Manual: The synchronization operation

must be performed manually.



122


Speed Data replication speed of a HyperMetroconsistency group.l Low: Data replication takes a relatively

long time. This value is applicable toscenarios where the service load isheavy. The speed ranges from 0 MB/s to5 MB/s.

l Medium: Data replication takes arelatively short time. This value isapplicable to scenarios where the serviceload is relatively heavy. The speedranges from 10 MB/s to 20 MB/s.

l High: Data replication takes a shorttime. This value is applicable toscenarios where the service load isrelatively light. The speed ranges from50 MB/s to 70 MB/s.

l Highest: Data replication takes theshortest time. This value is applicable toscenarios where the service load is light.The speed is greater than 100 MB/s.

Activation Status Activation status of site. The value can beActive or Passive.

Owning HyperMetro Domain HyperMetro domain to which theHyperMetro consistency group belongs.

Data Synchronization Direction The data synchronization direction of allHyperMetro pairs in one HyperMetroconsistency group. Including Remote toLocal and Local to Remote.

Isolation Switch After the Isolation Switch is turned on, thesystem will suspend the HyperMetro pairwhen the difference between the write I/Olatency of the two storage arrays is greaterthan the isolation switch. The storage arraywith the longer write I/O latency will stopproviding services.

Isolation Threshold (ms) Write I/O latency difference between thehost and HyperMetro storage arrays.

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



123

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 isfunctioning 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 remoteresources. Possible values can bel Normal: HyperMetro pair has

completed synchronization successfully.l To be synchronized: The data of

HyperMetro pair is inconsistent and needto be synchronized.

l Suspended: HyperMetro pair is in thepause status, and the synchronization issuspended.

l Synchronizing: HyperMetro pair issynchronizing data.

l Force Start: HyperMetro pair forciblyenables the local or remote site tomanually allow the local or remote siteto continue to provide services.

l Invalid: HyperMetro pair is useless andcannot be restored in this status, exceptdeleting it.

Activation Status Activation status of site. The value can beActive or Passive.

----End

5.4.2 Modifying the Properties of a HyperMetro ConsistencyGroup

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



124

Procedure



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 theHyperMetro consistencygroup.

[Example]HyperMetroGroup_005


[Example]—



125


Speed Data replication speed of aHyperMetro consistencygroup.l Low: Data replication

takes a relatively longtime. This value isapplicable to scenarioswhere the service load isheavy. The speed rangesfrom 0 MB/s to 5 MB/s.

l Medium: Datareplication takes arelatively short time.This value is applicableto scenarios where theservice load is relativelyheavy. The speed rangesfrom 10 MB/s to 20MB/s.

l High: Data replicationtakes a short time. Thisvalue is applicable toscenarios where theservice load is relativelylight. The speed rangesfrom 50 MB/s to 70MB/s.

l Highest: Data replicationtakes the shortest time.This value is applicableto scenarios where theservice load is light. Thespeed is greater than 100MB/s.

[Example]Medium




[Example]Automatic



126



[Example]Disabled


[Example]50

Step 5 Click OK.

Step 6 Click Close.

----End

5.4.3 Synchronizing a HyperMetro Consistency GroupThis operation allows you to synchronize all HyperMetro pairs in the consistency group. Thesynchronization ensures the consistency of data on the local and remote devices at thesynchronization point and protects the data validity of LUNs.

Prerequisites

The running status of a HyperMetro consistency group must be Paused, To be synchronizedor Force Start.

ContextIf controllers of storage systems reset during the synchronization of HyperMetro consistencygroups, the synchronization of some HyperMetro pairs may fail. As a result, data consistencyof LUNs cannot be ensured.

Procedure



Step 3 Select the HyperMetro consistency group, and click Synchronize.The security alert dialog box is displayed.

Step 4 Confirm the synchronization operation.



127

1. Carefully read the contents of the dialog box. Then click the check box next to thestatement I have read and understand the consequences associated with performingthis operation. and click OK to confirm the information.The Execution Result dialog box is displayed indicating that the operation succeeded.

2. Click Close.

----End

5.4.4 Pausing a HyperMetro Consistency GroupPausing a HyperMetro consistency group will stop data written into the non-prior servicesites, 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



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.The security alert dialog box is displayed.

Step 5 Confirm the operation of pausing the HyperMetro consistency group.1. Carefully read the contents of the dialog box, and click OK.

The Execution Result dialog box is displayed indicating that the operation succeeded.2. Click Close.

NOTEAfter a HyperMetro consistency group is suspended, you can execute Synchronizing a HyperMetroConsistency Group to restart it.

----End

5.4.5 Switching the Prior/Non-prior for a HyperMetro ConsistencyGroup

This operation allows you to switch the preferable site of HyperMetro consistency groups. If afault 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.



128

ContextAfter a HyperMetro pair is added to a consistency group, the preferred and non-preferred sitesof the pair are determined by the consistency group's preference settings.

Procedure



Step 3 Select the HyperMetro consistency group you want to switch the prior/non-prior, and chooseMore > Prior/Non-prior Switchover.The security alert dialog box is displayed.

Step 4 Confirm the operation of switching the prior/non-prior.1. Carefully read the contents of the dialog box, and click OK.


----End

5.4.6 Starting a HyperMetro Consistency Group ForciblyAfter system failure or the problem of the quorum server cannot which is prior service site isfixed, determine local site or remote site to provide service by starting the HyperMetroconsistency group forcibly.

Prerequisitesl 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 hostand services on it.

Procedure



Step 3 Select the HyperMetro consistency group you want to forcibly start, and choose More >Force Start.The security alert dialog box is displayed.

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 performingthis operation. and click OK to confirm the information.



129


----End

5.4.7 Adding a HyperMetro PairThis operation enables you to add HyperMetro pairs to a HyperMetro consistency group.

Prerequisitesl 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



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 clickto add the HyperMetro pair to Selected HyperMetro Pairs, then click OK.The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 5 Click Close.

----End

5.4.8 Remove HyperMetro PairThis operation enables you to remove a HyperMetro pair from a HyperMetro consistencygroup.

PrerequisitesThe Running Status of the consistency group you want to pause must be Paused or Normal.

Procedure



Step 3 Select the HyperMetro consistency group you want to remove HyperMetro pair, and chooseMore > Remove HyperMetro Pair.



130

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 GroupYou can delete a HyperMetro consistency group once you do not need it.

PrerequisitesAll HyperMetro pairs of HyperMetro consistency group have been removed.

ContextOnly consistency groups of HyperMetro pairs are deleted but not the HyperMetro pairs.

Procedure



Step 3 Select the HyperMetro consistency group you want to delete, and click Delete.The security alert dialog box is displayed.

Step 4 Optional: Select Only delete the configuration information about the local device if theHyperMetro consistency group fails or the remote device is disconnected. based on siterequirements.

NOTE


Step 5 Carefully read the contents of the dialog box. Then click the check box next to the statement Ihave read and understand the consequences associated with performing this operation.and click OK to confirm the information.The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 6 Click Close.

----End



131

5.5 Importing CertificatesWhen the storage system is communicating with an external device, you are advised to usethe certificate verification mode to improve service security. This chapter describes how togenerate and export a certificate signing request, and import and activate the signedcertificate.

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 anappropriate 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 devicemanagement certificate, domainauthentication certificate, KMCcertificate, HyperMetro certificate,HTTPS certificate, FTPS certificate,Syslog certificate, NTP certificate, andCall Home certificate.

Certificate File Certificate file that has been exported andsigned.

CA Certificate File Certificate file of a server.

Private Key File Private key file of a device.

3. Click OK.

The security alert dialog box is displayed.4. Confirm the information of the dialog box and select I have read and understand the

consequences associated with performing this operation.. Then click OK.The Success dialog box is displayed.

5. Click OK.The certificate list shows imported certificates.



132

NOTEThe 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 devicemanagement certificate, domainauthentication certificate, KMC certificate,HyperMetro certificate, HTTPS certificate,FTPS certificate, Syslog certificate, NTPcertificate, 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 theperiod starts, the system sends warning tousers about the expiration.

CA Certificate Fingerprint Hashed value of the certificate content. Thisvalue is unique for every certificate. TheCA certificate fingerprint is required toobtain the CA certificate to ensure thatcontent in the CA certificate has not beenmodified illegally. If the CA certificatefingerprint is different from the fingerprintconfigured in the PKI domain, the devicewill 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. Whenthe period starts, the system sendswarning to users about the expiration.NOTE

The value ranges from 7 to 180.

New Private Key Encryption Password Encrypted password of a new private keyfile.



133


Confirm Password Confirms the newly typed encryptedpassword 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 withperforming 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 describedin Table 5-14.

Table 5-14 Parameters related to a CRL


Type Type of a CRL, including domainauthentication certificate, KMCcertificate and HyperMetro certificate.

NO. No. of a CRL

Name Name of a CRL

Status Status of a CRL, which can be Valid, Notexist and Invalid.

Expire time Time when a CRL expires

----End



134

6 FAQs

About This Chapter

This chapter describes frequently asked questions (FAQs) about the HyperMetro feature. If aproblem occurs when you configure and maintain the feature, you can browse this chapter forthe answer to the problem.

6.1 What Can I Do If a Quorum Link Fails to Be Added Because the HyperMetro ArbitrationCertificate 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 UseIs Down, the Quorum Server Goes Offline. Why?

6.3 How Do I Power Off Active-Active Storage Systems and Resume the HyperMetroService?

6.4 When Both the HyperMetro and Remote Backup Services Are Created, the ExcessivelyLow 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 InterfaceModule

6.7 In the SQL Server database scenario, how can I adjust parameters to reduce the I/Olatency 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 templateto deploy it again quickly.

OceanStor V3 SeriesHyperMetro Feature Guide for Block 6 FAQs


135

6.1 What Can I Do If a Quorum Link Fails to Be AddedBecause the HyperMetro Arbitration Certificate BecomesInvalid or the System Time Becomes Abnormal?

QuestionThe quorum server software is newly installed, the quorum server communicates with storagearrays properly, and the configurations on the quorum server are correct. However, a quorumlink of the quorum server fails to be added on a storage array. The storage array reports acommunication error or an invalid certificate. What can I do if the problem occurs?

AnswerThe validity period of the default HyperMetro arbitration certificate is 10 years (start fromSeptember 2015). The arbitration certificate will become invalid if the system time of thequorum server or a storage array is incorrectly set to a value that exceeds the validity periodof 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 tobe added.

l The system time of a storage array is incorrectly set to a value that exceeds the validityperiod 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 beadded 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 thecertificate management page.



136

2. On the certificate management page, check the validity of the HyperMetro arbitrationcertificate.– 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 > BasicInformation > 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 thestorage array is modified, go to Step 5.

Step 5 Contact Huawei technical support.

----End

6.2 Active and Standby IP Ports Are Configured on theQuorum Server. After the Port in Use Is Down, theQuorum Server Goes Offline. Why?

Question

The quorum server has two IP ports that work in active/standby mode and are on the samenetwork segment. After the port in use is down, why does the quorum server go offline?

AnswerBy default, a quorum server does not have policy routes. It can only receive and send data viaone IP port although it has two IP ports on the same network segment. As a result, after theport in use goes down, the other port cannot take over services.Perform the following operations:

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

NOTEIn 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 tableis 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 tableis 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



137


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 informationis 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


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 Systemsand Resume the HyperMetro Service?

Question

If active-active storage systems must be temporarily stopped due to equipment roomrelocation or power supply link failure, how do I correctly power off the storage systems?

AnswerPerform the following operations:

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 offthe other storage system.

For details about how to power off a storage system, see Powering off the StorageDevice 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 documentdelivered 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.



138

1. (Optional) Power on switches.

For details about how to power on switches, see the power-on document delivered withthe switches.

2. Power on the quorum server.

For details about how to power on the quorum server, see the power-on documentdelivered with the quorum server.

3. Power on the storage systems.

For details about how to power on a storage system, see Powering on the StorageDevice in Administrator Guide of the corresponding product model.

NOTICEThe active-active storage systems can be powered on at the same time. After they arepowered on, wait until HyperMetro Pair and HyperMetro Consistency Groupbecome 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 BackupServices Are Created, the Excessively Low LinkBandwidth Between Storage Systems Causes the RemoteBackup Service to Fail

Question

Only one replication link is established between storage systems, and both the HyperMetroand remote backup services are created. In this scenario, why does the remote backup servicefail?

When the host service bandwidth is higher than the replication network bandwidth betweenstorage systems, the service with a high priority is preferentially processed. In the precedingscenario, 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 asynchronousremote replication.

AnswerPerform the following operations:

Step 1 Increase the replication link bandwidth or the number of replication links to ensure that thereplication network bandwidth is higher than or equal to the peak service bandwidth.



139

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?

QuestionHow can I query HyperMetro LUN identifiers?

Answer

After the AIX host scans for LUNs, the LUN information will be solidified in the systemdatabase. 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 identifierinformation 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 BeCreated 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 theremote device, if error code 1073804034 occurs or the connection fails to be created, thecause may be that the storage system uses the TOE interface module to connect. When thelocal 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, thetwo 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-TOEinterface 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 moduleresides, and a communication exception error is returned, then the problem is what hasbeen described above. If you need to further confirm the problem, contact technicalsupport engineers to confirm with the system log.



140

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 theconnection oppositely. This method helps establish the link.Method 2: On the storage system where the non-TOE interface module resides, run thetcp_recycle_switch.sh command to disable the function of quickly recyclingTIME_WAIT socket in the TCP connection. After the link is established, enable thefunction.

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 adjustparameters to reduce the I/O latency and achieve theoptimal performance?

Question

In the SQL Server database scenario, how can I adjust parameters to reduce the I/O latencyand achieve the optimal performance?

AnswerYou 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 DeployVirtual Quorum Servers?

When a quorum server virtual machine (VM) becomes faulty, you can use an OVA templateto deploy it again quickly.

Exporting an OVA TemplateAfter a quorum server VM has been deployed and works properly with storage systems, youcan 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.



141

https://docs.microsoft.com/zh-cn/sql/relational-databases/logs/database-checkpoints-sql-server#IndirectChkpt

https://docs.microsoft.com/zh-cn/sql/relational-databases/logs/database-checkpoints-sql-server#IndirectChkpt

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 OVAtemplate is in the *.ova format.

NOTE

After the export is complete, power on the quorum server VM.

----End

Importing an OVA TemplateYou 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.



142

2. Specify the Name and Location, Host/Cluster, Resource Pool, Disk Format, andNetwork Mapping for the VM.

NOTE

– The new VM that is deployed using the OVA template cannot use the same name as theoriginal VM.

– The new VM must have the same Location, Host/Cluster, Resource Pool, Disk Format, andNetwork 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.



143

2. Download the XXX.vmx file to a local directory. Right-click the file and chooseDownload.

NOTEXXX is the name of the new VM.

3. Edit the .vmx file. Change the MAC addresses in the file to the same values as theoriginal VM's MAC addresses.



144

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 thequorum 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



145

7 Troubleshooting

About This Chapter

This chapter describes how to troubleshoot common problems that occur on the HyperMetrofeature. If a problem occurs when you configure and maintain the feature, you can browse thischapter 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 QuorumServer Is Replaced

Symptom

If the quorum server in the HyperMetro solution breaks down and cannot be recovered, youmust replace the quorum server. When a quorum link is added on a storage array after thequorum 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 serverdoes 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 SeriesHyperMetro Feature Guide for Block 7 Troubleshooting


146

2. In the CLI of the quorum server, run the show white_list command to check whether thewhite list of the quorum server contains the SNs of the two storage arrays in theHyperMetro 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 quorumlink 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 togenerate certificates. SeeConfigure Quorum Server Software to replace the certificatesfor 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 SummaryNone

OceanStor V3 SeriesHyperMetro Feature Guide for Block 7 Troubleshooting


147

A How to Obtain Help

If a tough or critical problem persists in routine maintenance or troubleshooting, contactHuawei for technical support.

A.1 Preparations for Contacting HuaweiTo better solve the problem, you need to collect troubleshooting information and makedebugging preparations before contacting Huawei.

A.2 How to Use the DocumentHuawei provides guide documents shipped with the device. The guide documents can be usedto handle the common problems occurring in daily maintenance or troubleshooting.

A.3 How to Obtain Help from WebsiteHuawei provides users with timely and efficient technical support through the regionaloffices, secondary technical support system, telephone technical support, remote technicalsupport, and onsite technical support.

A.4 Ways to Contact HuaweiHuawei Technologies Co., Ltd. provides customers with comprehensive technical support andservice. For any assistance, contact our local office or company headquarters.

A.1 Preparations for Contacting HuaweiTo better solve the problem, you need to collect troubleshooting information and makedebugging preparations before contacting Huawei.

A.1.1 Collecting Troubleshooting InformationYou need to collect troubleshooting information before troubleshooting.

You need to collect the following information:l Name and address of the customerl Contact person and telephone numberl Time when the fault occurredl Description of the fault phenomenal Device type and software version

OceanStor V3 SeriesHyperMetro Feature Guide for Block A How to Obtain Help


148

l Measures taken after the fault occurs and the related resultsl Troubleshooting level and required solution deadline

A.1.2 Making Debugging PreparationsWhen you contact Huawei for help, the technical support engineer of Huawei might assist youto 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 DocumentHuawei provides guide documents shipped with the device. The guide documents can be usedto handle the common problems occurring in daily maintenance or troubleshooting.

To better solve the problems, use the documents before you contact Huawei for technicalsupport.

A.3 How to Obtain Help from WebsiteHuawei provides users with timely and efficient technical support through the regionaloffices, secondary technical support system, telephone technical support, remote technicalsupport, and onsite technical support.

Contents of the Huawei technical support system are as follows:l Huawei headquarters technical support departmentl Regional office technical support centerl Customer service centerl 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 HuaweiHuawei Technologies Co., Ltd. provides customers with comprehensive technical support andservice. 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 ofChina

Website: http://enterprise.huawei.com/

OceanStor V3 SeriesHyperMetro Feature Guide for Block A How to Obtain Help


149



http://enterprise.huawei.com/

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 thatare automatically displayed to go to the document page of the product. Browse or downloadthe OceanStor V3 Series V300R006 Glossary.

OceanStor V3 SeriesHyperMetro Feature Guide for Block B Glossary


150



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 SeriesHyperMetro Feature Guide for Block C Acronyms and Abbreviations


151

S

SAS Serial Attached SCSI

SCSI Internet Small Computer Systems Interface

SSD Solid State Drive

OceanStor V3 SeriesHyperMetro Feature Guide for Block C Acronyms and Abbreviations


152

hypermetro feature guide for block - exclusive networks · oceanstor v3 series v300r006 hypermetro...

Documents