HyperMetro Feature Guide for File - Exclusive Networks · 2019-01-25 · OceanStor V3 Series V300R006 HyperMetro Feature Guide for File Issue 05 Date 2018-01-30 HUAWEI TECHNOLOGIES

OceanStor V3 SeriesV300R006

HyperMetro Feature Guide for File

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 File 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..............................................................................................................................................101.3.4 HyperMetro I/O Processing Mechanism................................................................................................................... 251.4 Impact and Restrictions................................................................................................................................................ 291.5 Application Scenarios...................................................................................................................................................30

2 Planning........................................................................................................................................ 342.1 Network Planning......................................................................................................................................................... 342.2 Data Planning............................................................................................................................................................... 34

3 Installation.................................................................................................................................... 363.1 Installation Process....................................................................................................................................................... 373.2 Preparations for Installation..........................................................................................................................................373.2.1 Preparing Tools, Meters, and Documentation........................................................................................................... 373.2.2 Quick checklist for the installation environment.......................................................................................................403.3 Device Installation........................................................................................................................................................453.4 Cable Connection......................................................................................................................................................... 483.5 Power-on.......................................................................................................................................................................533.6 Storage Array Initialization.......................................................................................................................................... 563.7 Arbitration Software Installation.................................................................................................................................. 56

4 Configuration............................................................................................................................... 594.1 Configuration Process...................................................................................................................................................594.2 Configuration Preparations...........................................................................................................................................644.3 Configuring Switch.......................................................................................................................................................654.4 Configure Quorum Server Software.............................................................................................................................654.4.1 Configuring the Arbitration Software (SUSE).......................................................................................................... 654.4.2 Configuring the Arbitration Software (Red Hat/Red Flag/NeoKylin/CentOS)........................................................ 704.4.3 Configuring the Arbitration Software (Ubuntu)........................................................................................................76

OceanStor V3 SeriesHyperMetro Feature Guide for File Contents


v

4.5 Configuring Basic Storage Services............................................................................................................................. 814.5.1 Creating a Disk Domain............................................................................................................................................ 814.5.2 Creating a Storage Pool............................................................................................................................................. 854.5.3 Creating a vStore....................................................................................................................................................... 934.5.4 Creating a File System...............................................................................................................................................934.5.5 Creating a Logical Port............................................................................................................................................ 1104.5.6 Sharing a File System.............................................................................................................................................. 1144.6 Creating NAS HyperMetro.........................................................................................................................................1144.6.1 Checking the License File........................................................................................................................................1144.6.2 Adding a Remote Device.........................................................................................................................................1154.6.3 Creating a Quorum Server....................................................................................................................................... 1184.6.4 Creating a HyperMetro Domain.............................................................................................................................. 1214.6.5 Creating a HyperMetro vStore Pair......................................................................................................................... 1224.6.6 Creating a NAS HyperMetro Pair........................................................................................................................... 1234.6.7 (Optional) Creating a Quota Tree............................................................................................................................ 1264.6.8 (Optional) Creating a Quota.................................................................................................................................... 1284.6.9 (Optional) Creating a Snapshot............................................................................................................................... 1314.6.9.1 Manually Creating a Snapshot..............................................................................................................................1314.6.9.2 Creating a Periodic Snapshot................................................................................................................................1334.7 Verifying the Configuration........................................................................................................................................134

5 Management............................................................................................................................... 1355.1 Managing HyperMetro in the System View............................................................................................................... 1355.1.1 Managing a HyperMetro vStore Pair.......................................................................................................................1355.1.1.1 Viewing HyperMetro vStore Pair Information..................................................................................................... 1355.1.1.2 Checking HyperMetro vStore Pair Information................................................................................................... 1385.1.1.3 Deleting a HyperMetro vStore Pair...................................................................................................................... 1395.1.1.4 Primary/Secondary Switchover............................................................................................................................ 1405.1.1.5 Forcible Start........................................................................................................................................................ 1415.1.1.6 Modifying the Owning Tenant of an Existing File System.................................................................................. 1425.1.2 Managing HyperMetro Domains.............................................................................................................................1435.1.2.1 Viewing HyperMetro Domain Information.......................................................................................................... 1435.1.2.2 Modifying a HyperMetro Domain........................................................................................................................1435.1.2.3 Deleting a HyperMetro Domain........................................................................................................................... 1445.1.3 Managing a HyperMetro Pair.................................................................................................................................. 1455.1.3.1 Viewing HyperMetro Pair Information................................................................................................................ 1455.1.3.2 Modifying HyperMetro Pair Properties................................................................................................................1505.1.3.3 Synchronizing a HyperMetro Pair........................................................................................................................1525.1.3.4 Suspending a HyperMetro Pair.............................................................................................................................1535.1.3.5 Deleting a HyperMetro Pair................................................................................................................................. 1535.1.4 Managing Quorum Servers......................................................................................................................................1545.1.4.1 Viewing Quorum Server Information...................................................................................................................1545.1.4.2 Modifying Quorum Server Information............................................................................................................... 155



vi

5.1.4.3 Adding a Link.......................................................................................................................................................1565.1.4.4 Removing a Link.................................................................................................................................................. 1565.1.4.5 Removing a Quorum Server................................................................................................................................. 1575.1.4.6 Uninstalling the Arbitration Software.................................................................................................................. 1575.1.5 Importing Certificates..............................................................................................................................................1585.2 Managing HyperMetro in the Tenant View................................................................................................................ 1615.2.1 Viewing HyperMetro Pair Information................................................................................................................... 1615.2.2 Modifying HyperMetro Pair Properties...................................................................................................................1675.2.3 Synchronizing a HyperMetro Pair...........................................................................................................................1695.2.4 Suspending a HyperMetro Pair................................................................................................................................1705.2.5 Deleting a HyperMetro Pair.................................................................................................................................... 170

6 FAQs.............................................................................................................................................1726.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?............................................................................................................ 1726.2 Active and Standby IP Ports Are Configured on the Quorum Server. After the Port in Use Is Down, the QuorumServer Goes Offline. Why?...............................................................................................................................................1746.3 How Do I Power Off Active-Active Storage Systems and Resume the HyperMetro Service?................................. 1756.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............................................................................1766.5 What Can I Do If the Remote Connection Fails to Be Created with the TOE Interface Module.............................. 1776.6 How Can I Use OVA Templates to Quickly Deploy Virtual Quorum Servers?......................................................... 177

7 Troubleshooting........................................................................................................................ 1827.1 A Quorum Link Fails to Be Added After the Quorum Server Is Replaced................................................................182

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

B Glossary...................................................................................................................................... 186

C Acronyms and Abbreviations................................................................................................ 187



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 File 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 tenant, HyperMetro tenantpair, local file system, remote file system, synchronization, pause, data status, and others.

TenantMultiple virtual storage systems can be created in one physical storage system and multipletenants can share the same storage hardware resources without affecting data security andprivacy of each other. Tenants enable flexible, easy-to-manage, and cost-effective sharedstorage in a multi-protocol unified storage architecture.

HyperMetro Tenant PairA HyperMetro tenant pair indicates a HyperMetro relationship between tenants of the localand remote storage arrays. The HyperMetro arbitration is implemented in the unit of a



3

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

HyperMetro tenant pair. If a fault occurs in a HyperMetro tenant pair, ensure the arbitrationresults of all file systems in the tenants of the HyperMetro tenant pair are the same and theenvironments in which the file systems are running are consistent between the tenants.

Logical Port

Logical ports are created based on physical Ethernet ports, bond ports, or VLANs and usedfor file service operation.

Local File System and Remote File System

In a HyperMetro pair, the file system on the local storage array is called local file system andthe file system on the remote storage array is called remote file system.

Dual-Write

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

DCL

DCLs record changes in the data of storage arrays.

Quorum Server

For NAS HyperMetro, if the heartbeats between two storage arrays are interrupted, thequorum server decides which storage array continues providing services, thereby greatlyimproving host service continuity.

HyperMetro Domain

A HyperMetro domain consists of the local storage array, remote storage array, and thequorum server. Application servers can access data across data centers using a HyperMetrodomain. Before configuring a HyperMetro pair, you must configure the HyperMetro domainfirst. Each HyperMetro pair must be created in the HyperMetro domain.

NAS HyperMetro Pair

A NAS HyperMetro pair indicates a HyperMetro relationship between the local and remotefile systems. After HyperMetro is configured, a local file system on the local storage arrayand a remote file system on the remote storage array form a NAS HyperMetro pair. Byviewing the state of a HyperMetro pair, you can determine whether you need to performsynchronization and suspension operations. After performing an operation, you can view thestate of the HyperMetro pair to determine whether the operation succeeded.

Synchronization

Synchronization refers to the synchronization of differential data between a local file systemand a remote file system.



4

PausePause is a state indicating the suspension of a HyperMetro pair formed by a local file systemand a remote file system.

Force StartTo 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 SwitchoverPriority switchover indicates that the storage array at the preferred site takes precedence toprovide services for hosts. If the storage array at the preferred site needs to be repaired ormaintained, a priority switchover is performed to enable the storage array at the non-preferredsite to provide services for hosts.

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.

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.

Network OverviewFibre Channel networking is used as an example to explain HyperMetro solution networktopology. For details, see Figure 1-1.



5

Figure 1-1 HyperMetro solution network topology

Data center A Data center B

Local storage array

Quorum server

Fibre Channel switch

Ethernet switch

Remote storage array

Host-to-storage network

Host cluster

FC

HyperMetro replication networkSame-city cross-DC network

Quorum networkQuorum site

Ethernet switch

Ethernet switch




IP

Ethernet switch

Ethernet switch

Ethernet switchIP

Host cluster

To 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 GE and 10GE networks.

Networkingmode

l A fully interconnected network is usedbetween hosts and storage systems, that is,each service host is physically and logicallyconnected to two HyperMetro storagearrays.

l Dual-switch networking is required.l The HyperMetro replication network,

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



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– 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 RTT ofthe VMware vSphere applications is less than10 ms (with a distance of less than 300 km).The RTT of the SAP HANA applications isless than 1 ms (with a distance of less than100 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 onstorage devices.

Networkingmode

Each controller of the HyperMetro array has atleast two links and at most four links forredundancy.

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 dataloss or serviceinterruption.

Networktype

The network uses bare fibers.



7

Network Description

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 interconnect them.

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.

If IP networking is used for the applicationlayer, ensure that the Fiber Channel networkwith at least two pairs (four wires) of opticalcables is set up for heartbeat interconnection inthe cluster.



8

Network Description

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

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

Networktype

l Quorum links support GE and 10GEnetworks as long as routes are reachable.The Fibre Channel network is not supported.

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 onstorage devices.



9

Network Description

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.If a controller houses only one quorum port,connect controller A and controller C toswitch 1 on IP network segment 1 andconnect controller B and controller D toswitch 2 on IP network segment 2.If each controller has two quorum ports,connect the first quorum port on eachcontrollers 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 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.



10

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, without causingHyperMetro service interruption.

Static Priority Mode

The static priority mode applies to scenarios where no third-place quorum server is deployed.

In a HyperMetro vStore pair, you can set one data center as the preferred site and the other asthe non-preferred site. In the following example, data center A is used as a preferred site.Table 1-3 describes the arbitration 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.

FaultDiagram

Fault Type HyperMetro PairRunningStatus

ArbitrationResult

1 The linkbetweentwo storagearraysbreaksdown.


To besynchronized

A continuesprovidingserviceswhile Bstops.

2 The storagearray indata centerB (non-preferredsite)malfunctions.


To besynchronized

A continuesprovidingserviceswhile Bstops.

3 The storagearray indata centerA(preferredsite)malfunctions.


To besynchronized

Both A andB stop. Youmustforcibly startB to resumeprovidingservices forhosts.

Green cable: HyperMetro replication network



11

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

FaultDiagram

Fault Type HyperMetroPairRunningStatus

ArbitrationResult

1 Thequorumserverbreaksdown.

Quorum server


Normal A continuesprovidingservices whileB stops.NOTE

HyperMetroautomaticallyswitches tostatic priorityarbitration.



12

No.

FaultDiagram


ArbitrationResult

2 The linkbetween thequorumserver andone or bothstoragearraysbreaksdown.

Quorum server


Quorum server


Quorum server


1

2

3

Normal A continuesprovidingservices whileB stops.

3 The storagearray indata centerA(preferredsite)malfunctions.

Quorum server


To besynchronized

B startsprovidingservices whileA stops.



13

No.

FaultDiagram


ArbitrationResult

4 The storagearray indata centerB (non-preferredsite)malfunctions.

Quorum server


To besynchronized

A continuesprovidingservices whileB stops.

5 The linkbetweentwo storagearraysbreaksdown.

Quorum server


To besynchronized


6 One storagearray andthe quorumserver bothmalfunction.

Quorum server


Quorum server


1

2

To besynchronized

Both A and Bstop.NOTE

You mustforcibly startthe working filesystem toresumeprovidingservices forhosts.



14

No.

FaultDiagram


ArbitrationResult

7 The linkbetween thetwo storagearrays andthe linkbetween thestoragearray indata centerB and thequorumserver bothbreakdown.

Quorum server


To besynchronized


8 The linkbetween thetwo storagearrays andthe linkbetween thestoragearray indata centerA and thequorumserver bothbreakdown.

Quorum server


To besynchronized

B startsprovidingservices whileA stops.



15

No.

FaultDiagram


ArbitrationResult

9 One storagearraymalfunctions and thelinkbetween theotherstoragearray andthe quorumserver isdown.

Quorum server


Quorum server


1

2

To besynchronized


You mustforcibly startthe working filesystem toresumeprovidingservices forhosts.

10 Thequorumservermalfunctions. Thenthe linkbetweentwo storagearrays isdown.

Quorum server


To besynchronized

A continuesprovidingservices whileB stops.NOTE

HyperMetroautomaticallyswitches tostatic priorityarbitration.

11 Thequorumservermalfunctions. At thesame time,the linkbetweentwo storagearrays isdown.

Quorum server


To besynchronized


You mustmanually startA to resumeprovidingservices forhosts.



16

No.

FaultDiagram


ArbitrationResult

Green cable: HyperMetro replication networkBlue cable: quorum network

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

No.

FaultType

Fault Diagram HyperMetroPairRunningStatus

ArbitrationResult

1 Thequorumserverbreaksdown.

Quorum server (active)

Data center A Data cente B

Quorum server (standby) Normal The standbyquorum servertakes over thearbitrationservices fromthe activequorum server.




17

No.

FaultType


ArbitrationResult

2 Thelinkbetweentheactivequorumserver andoneorbothstoragearraysbreaksdown.





1

2

3

Quorum server (standby)

Quorum server (active) Quorum server (standby)


Normal l In scenarios1 and 2, theactivequorumserver runsproperly. Acontinuesprovidingserviceswhile Bstops.

l In scenario3, thestandbyquorumserver takesover thearbitrationservicesfrom theactivequorumserver. Acontinuesprovidingserviceswhile Bstops.



18

No.

FaultType


ArbitrationResult

3 Thestoragearrayindatacenter A(preferredsite)malfunctions.



Quorum server (standby) To besynchronized

The activequorum serverruns properly.B providesservices whileA stops.

4 Thestoragearrayindatacenter B(non-preferredsite)malfunctions.




The activequorum serverruns properly.A continuesprovidingservices whileB stops.

5 Thelinkbetweentwostoragearraysbreaksdown.







19

No.

FaultType


ArbitrationResult

6 Onestoragearrayandtheactivequorumserverbothmalfunction.




1

2



To besynchronized

l In scenario1, thestandbyquorumserver takesover thearbitrationservicesfrom theactivequorumserver. Bprovidesserviceswhile Astops.




20

No.

FaultType


ArbitrationResult

7 Thelinkbetweenthetwostoragearrays andthelinkbetweenthestoragearrayindatacenter Bandtheactivequorumserverbothbreakdown.







21

No.

FaultType


ArbitrationResult

8 Thelinkbetweenthetwostoragearrays andthelinkbetweenthestoragearrayindatacenter Aandtheactivequorumserverbothbreakdown.




The activequorum serverruns properly.B providesservices whileA stops.



22

No.

FaultType


ArbitrationResult

9 Onestoragearraymalfunctionsandthelinkbetweentheotherstoragearrayandtheactivequorumserver isdown.




1

2



To besynchronized

l In scenario1, thestandbyquorumserver takesover thearbitrationservicesfrom theactivequorumserver. Bprovidesserviceswhile Astops.




23

No.

FaultType


ArbitrationResult

10 Theactivequorumservermalfunctions.Thenthelinkbetweentwostoragearrays isdown.




The standbyquorum servertakes over thearbitrationservices fromthe activequorum server.A continuesprovidingservices whileB stops.



24

No.

FaultType


ArbitrationResult

11 Theactivequorumservermalfunctions.Atthesametime,thelinkbetweentwostoragearrays isdown.




The standbyquorum servertakes over thearbitrationservices fromthe activequorum server.Both A and Bstop.NOTE

You mustmanually startA to resumeprovidingservices forhosts.

Green cable: HyperMetro replication networkBlue solid cable: quorum network between the active quorum server and data centersBlue 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.

Basic ConceptsYou are advised to know the key concepts of HyperMetro before reading the I/O processingmechanism. For details, see 1.3.1 Basic Concepts.

Data HyperMetro ImplementationThe core for implementing data HyperMetro of two storage arrays lies in the tenant-basedlogical port mechanism and dual-write mechanism. Data changes can be synchronized using



25

the dual-write and DCL technologies while services are running, ensuring data consistencybetween the storage arrays in two data centers. Figure 1-2 shows the data HyperMetromechanism.

Figure 1-2 Data HyperMetro mechanism

Tenant 1 Tenant 1'

FSnFS2FS1 FSnFS2FS1

Local storage array Remote storage array

HyperMetro pair 1HyperMetro pair 2

HyperMetro pair n

Logical port Logical port

√ √Activated Not activated

Host

HyperMetro tenant pair

... ...

Local file system

Remote file system

l Create tenants on two storage arrays to enable multiple tenants to share the same storage

hardware resources. Data security and privacy of the tenants are not adversely affected.l The operations such as creating file systems in tenants, sharing resources among tenants,

and rectifying faults act on all file systems of the tenants to achieve a flexible, easy-to-manage, and cost-effective storage resource sharing mechanism.

l Create a HyperMetro tenant pair to establish a HyperMetro relationship between tenantsof the local and remote storage array. The HyperMetro arbitration is implemented in theunit of a HyperMetro tenant pair. If a fault occurs in a HyperMetro tenant pair, ensure thearbitration results of all file systems in the tenants of the HyperMetro tenant pair are thesame and the environments in which the file systems are running are consistent betweenthe tenants.

l Create a NAS HyperMetro pair to establish a HyperMetro relationship between the localand remote file systems. After creating a NAS HyperMetro pair, you can perform datasynchronization, dual-write, and suspension in the pair in real time.

l After logical ports are created for tenants, the logical ports of the local storage array areactivated but the logical ports of the remote storage array are not activated. The localstorage array provides services for hosts. If the local storage array malfunctions, thelogical ports of the remote storage array are activated and those of the local storage array



26

are deactivated. The remote storage array provides services for hosts. In addition toensuring robust reliability and service continuity, HyperMetro also improves resourceutilization of storage arrays.

Write I/O ProcessFigure 1-3 shows the write I/O process (write back as an example) when a host sends an I/Orequest and gives rise to data changes in scenarios where services are running properly.

Figure 1-3 Write I/O process

LOG

2

84

8

DCL

5

71

Local storage array Remote storage array

Host

Same-city data center network

IP/FC

Storage

Host cluster

Local cache

Disk

Remote file system

Local file system

4 5

Remote cache

Disk

LOG

HyperMetro management module

3

63 6

1. A host delivers a write I/O to the HyperMetro management module.2. A log is recorded in the local storage array.3. The HyperMetro management module writes the write I/O to both the local and remote

file systems concurrently.4. The local file system writes the write I/O to local cache and the remote file system writes

the write I/O to remote cache.5. The local cache returns the write I/O result to the local file system and the remote cache

returns the write I/O result to the remote file system.6. The local and remote file systems return the write I/O results to the HyperMetro

management module.7. The storage system determines whether dual-write is successful.

– If the write I/O request is processed successfully, the log is deleted.– If the write I/O fails to be written to the local or remote cache, the log is converted

into a DCL. The DCL records the differential data between the local and remote filesystems.



27

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 in the local file system is identical to the data in the remote file system,HyperMetro services are restored.

Read I/O Process

Data on the file systems of both storage arrays is synchronized in real time. If the storagesystem in one data center malfunctions, the storage system in the other data center continuesproviding host services alone.

Figure 1-4 shows the read I/O process.

Figure 1-4 Read I/O process

Local storage array

Local file system

Remote storage array

Remote file system

1 5

23

4.1 4.2

HyperMetro management module

Host

1. A host applies for read permission from the HyperMetro management module.

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. The logical ports of the local storage array are activated but thelogical ports of the remote storage array are not activated. The local storage arrayprovides services for hosts.

4. If the local storage array is not operating properly, the logical ports of the remote storagearray are activated and the logical ports of the local storage array are deactivated. Theremote storage array provides services for hosts and returns data to the HyperMetromanagement module.

5. The read I/O request made by the host is processed successfully.



28

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

Network RestrictionsFor details about network restrictions, see HyperMetro Solution Overview.

Device Restrictions

Table 1-6 Device configuration requirements

Device Configuration Requirement

Quorum server The arbitration software can be deployed on either a physicalmachine or a virtual machine (VM). The configuration requirementsare as follows:l CPU: X86-64 architecture; 2-core 1.6 GHz CPU (minimum

configuration)l Memory: 4 GB DDR memory (minimum configuration)l Operating system: Asianux Server 4 SP4 for x86_64, CentOS 6.5

for x86_64, NeoKylin 6.5 for x86_64, Red Hat Enterprise Linux6 for x86_64, Red Hat Enterprise Linux 6.1 for x86_64, Red HatEnterprise Linux 6.2 for x86_64, Red Hat Enterprise Linux 6.3for x86_64, Red Hat Enterprise Linux 6.5 for x86_64, Red HatEnterprise Linux 6.6 for x86_64, Red Hat Enterprise Linux 6.7for x86_64, Red Hat Enterprise Linux 7.2 for x86_64, Red HatEnterprise Linux 7.2 for x86_64, SUSE Linux Enterprise Server11 SP1 for x86_64, SUSE Linux Enterprise Server 11 SP2 forx86_64, SUSE Linux Enterprise Server 11 SP3 for x86_64,SUSE Linux Enterprise Server 11 SP4 for x86_64, SUSE LinuxEnterprise Server 12 SP2 for x86_64, Ubuntu 14.04 LTS forx86_64, CentOS 6.8 for x86_64NOTE

V300R006C00SPC100 and later versions support CentOS 6.8.

The arbitration software cannot run in operating systems that use the CPUarchitectures such as MIPS, ARM, and PPC.

l Storage capacity for installing the arbitration software: ≥ 10 GBl VMs can only use local disks of servers or file systems

independent of HyperMetro storage systems as system disks ordata disks.

l Arbitration granularity can be a HyperMetro vStore pair.

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.



29

Compatibility

When using HyperMetro, ensure that the host operating system and arbitration software arecompatible with each other. You can query the compatibility using the OceanStorInteroperability 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 Featuresl HyperMetro can work with HyperReplication to provide a three-data-center (3DC)

disaster recovery solution in cascade or parallel mode.

– Figure 1-5 shows the cascade 3DC network.



30

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

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

Figure 1-5 Cascade 3DC network with HyperMetro + HyperReplication

Optical fiber

Site CSite A Site B

HyperMetro

Asynchronous remote

replication

Storage system

File system

Storage system

File system

Storage system

File system

Network cable

– Figure 1-6 shows the parallel 3DC network.

Figure 1-6 Parallel 3DC network with HyperMetro + HyperReplication

Site C

Storage system

Site A Site B

Network cable

Asynchronous

remote

replication

File system

Storage system

File system

Storage system

File system

HyperMetro

Optical fiber

l (For V300R006C10 and later versions) HyperMetro and HyperVault are combined to

provide a 3DC disaster recovery solution in cascade or parallel mode. The 3DC disasterrecovery solution is composed of two data centers in the same city and a third data centerin a geographically dispersed location.– Figure 1-7 shows the cascaded 3DC Network.



31

Figure 1-7 Cascaded 3DC network with file system-based HyperMetro andHyperVault

Production center A

OceanStor storage system

Same-city disaster recovery center B


... Application server

Application server

...

NASNAS HyperMetro


Remote disaster recovery center C

NAS

HyperVault

HyperVault

On the cascaded 3DC network, data links must be established between theproduction center A and same-city disaster recovery center B as well as between thesame-city disaster recovery center B and remote disaster recovery center C. Same-city disaster recovery is implemented between the production center A and same-city disaster recovery center B using HyperMetro. The primary file system ofHyperVault serves as the secondary file system of HyperMetro, making remotedisaster recovery of file systems in the production center A available. Local backupof HyperVault can be implemented on the primary file system of HyperVault.

– Figure 1-8 shows the parallel 3DC network.



32

Figure 1-8 Parallel 3DC network with file system-based HyperMetro andHyperVault

Production center A


Same-city disaster recovery center B


... Application server

Application server

...

HyperVault

NASNAS HyperMetro


Remote disaster recovery center C

NAS

HyperVault

On the parallel 3DC network, HyperReplication (NAS) is configured for the storagesystems in the production center A and same-city disaster recovery center B as wellas HyperVault is configured for the storage systems in the production center A andremote disaster recovery center C. Local backup can be implemented in theproduction center A.



33

2 Planning

About This Chapter

This chapter describes the networks and data you must plan before HyperMetro configuration.

2.1 Network PlanningThis section describes connections of devices in HyperMetro data centers and third-placequorum site.

2.2 Data PlanningHyperMetro supports both Fibre Channel and IP networks. You must plan storage arrays,hosts, and IP addresses of switch ports before configuring HyperMetro.

2.1 Network PlanningThis section describes connections of devices in HyperMetro data centers and third-placequorum site.

For details about the network planning principles, see Cable Connection section.

2.2 Data PlanningHyperMetro supports both Fibre Channel and IP networks. You must plan storage arrays,hosts, and IP addresses of switch ports before configuring HyperMetro.

Principles for Planning IP Addressesl Simple: Use simple IP addresses and avoid using complex address masks.l Consecutive: Allocate consecutive IP addresses to a network.l Expandable: Ensure that IP addresses are expandable so that consecutive IP addresses

can be added as the number of devices increases.l Manageable: Ensure that an IP address change does not affect upper-layer applications

and system services.l Secure: Divide a network into different network segments (subnets) for easy

management.

OceanStor V3 SeriesHyperMetro Feature Guide for File 2 Planning


34

Other Precautionsl Configure IP addresses of ports on iSCSI host and IP addresses of service network ports

on application servers on the same network segment. If two IP addresses are on differentnetwork segments, add a route to establish a connection between them.

l The service network ports that connect hosts to the storage network and HyperMetromirrored network and management network port cannot reside on the same networksegment.

l For a dual-controller storage array, the default IP addresses of heartbeat network portsare 127.127.127.10 and 127.127.127.11. For a four-controller storage array, the defaultIP addresses of heartbeat network ports are 127.127.127.10, 127.127.127.11,127.127.127.12, and 127.127.127.13. Therefore, the configured IP addresses cannotreside on network segment 127.127.127.XXX and the gateway cannot be127.127.127.10, 127.127.127.11, 127.127.127.12, or 127.127.127.13. Otherwise, routingfails.

OceanStor V3 SeriesHyperMetro Feature Guide for File 2 Planning


35

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 the 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 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 File 3 Installation


36

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

Install storage devices into the cabinet.

Start

End

Prepare for the installation.

Power on the storage devices.

Connect cables.

Initialize the storage devices.

Install the arbitration software.

Mandatory item

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



37

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.

Table 3-2 lists the meters required in the installation process.



38

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

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



39




Document Name How to Obtain

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

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.

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.

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



40





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.

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.



41


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.

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.



42


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.

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



43


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

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



44


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.

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:



45

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


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




46

InstallationSequence

Site Procedure

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.

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



47

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


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



48

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



49




50


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.



51

Table 3-5 Cable connection principles

NetworkType

Cable Connection Principle

Networkbetween hostsand storagearrays

l Hosts and storage devices are connected through Ethernet switches.Each data center has two Ethernet switches.

l Each Ethernet switch has at least N ports to connect hosts and storagedevices. N = 1 x Number of Servers + 2 x Number of StorageDevices.

l Host-Ethernet switch connection: Each host has at least two Ethernetports to connect two Ethernet switches of the data center. It isrecommended that the two ports be separated on two HBAs.

l Storage device-Ethernet switch connection: Each controller has atleast two ports to connect two Ethernet switches of the data center. Itis recommended that the two ports be separated on two Ethernetinterface 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.



52

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.



53

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.



54

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.



55

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



56

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.



57

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.1.4.6 Uninstalling the ArbitrationSoftware.



58

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

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

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

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

Figure 4-1 shows the configuration process of HyperMetro.

OceanStor V3 SeriesHyperMetro Feature Guide for File 4 Configuration


59

Figure 4-1 Configuration process of HyperMetro

Start

Configuration Preparations.

Configuring Switch.

End

Configure Basic Storage Services.

Configure NAS HyperMetro.

Creating a File System.

Creating a vStore.

Creating a Storage Pool.

Creating a Disk Domain.

Creating a NAS HyperMetro Pair.

Creating a HyperMetro vStore Pair.

Creating a HyperMetro Domain.

Adding a Quorum Server.

Adding a Remote Device.

Checking the License File.

Creating a Qtree Tree.

Creating a Quota.

Creating a Snapshot.

Configuring Quorum Server Software.

Mandatory sub-item

Optional sub-item

Mandatory item

Optional item

Sharing a File System.

Creating a Logical Port.

Configuring Quorum Server Software.

Table 4-1 describes the configuration procedure of HyperMetro.



60

Table 4-1 Configuration procedure of HyperMetro

No. ConfigurationProcedure

Description Operation Location

1 ConfigurationPreparations.

Describes prerequisitesand documents that youmust prepare before youconfigure HyperMetro.

Local and remote storage arraysand third-place quorum server.

2 ConfiguringSwitch.

Describes theconfigurationrequirements of coreswitches and accessswitches at the networklayer and theconfiguration procedureof Fibre Channelswitches at the storagelayer.Ethernet switches serveas the core switches andaccess switches at thenetwork layer and FibreChannel switches areused at the storage layer.

Switches.

3 ConfiguringQuorum ServerSoftware.

This section describeshow to configure, andmanage the quorumserver software.

Quorum server.



61



4 The configurationsteps of basicstorage servicesinclude:1. Create a disk

domain.2. Create a

storage pool.3. Create a

vStore.4. Create a file

system.5. Creating a

Logical Port.6. Sharing a File

System.

Describes how to createdisk domains, storagepools, vStores, and filesystems.

When creating logicalports for the local andremote storage arrays,immediately activate thelogical ports of the localstorage array. Thelogical ports of theremote storage array arenot immediatelyactivated by default.NOTICE

l When creating logicalports for the local andremote storage arrays,ensure that the IPaddress types, IPv4addresses, subnetmasks, and IPv4gateways of thelogical ports are thesame.

l The name of the localfile system must bethe same as that of theremote file systemupon file systemcreation. It isrecommended that thetwo file systems alsohave the sameattributes such as theowning controller,capacity, and blocksize.

l You are advised to usethe same configurationwhen creating diskdomains and storagepools on the localstorage array andremote storage array.

Local file systems areshared with hosts. Whenthe local file systems areshared with hosts, thelocal storage arraysynchronizes theconfiguration to the

1. Create a disk domain. Thisoperation is performed on boththe local and remote storagearrays.

2. Create a storage pool. Thisoperation is performed on boththe local and remote storagearrays.

3. Create a vStore. This operationis performed on both the localand remote storage arrays.

4. Create a file system. Thisoperation is performed on boththe local and remote storagearrays.

5. Creating a Logical Port. Thisoperation is performed on boththe local and remote storagearrays.

6. Sharing a File System. Thisoperation is performed on thelocal storage array.



62



remote file systems.After the local filesystem is shared withhosts, data issynchronized from thelocal file systems to theremote file systems.NOTICE

Before creating aHyperMetro pair, ensurethat no operation isperformed on the remotefile system you want touse to create theHyperMetro pair.Otherwise, theHyperMetro pair may failto be created.



63



5 Configurationsteps include:1. Check the

license file.2. Add a remote

device.3. Add the

quorum server.4. Create a

HyperMetrodomain.

5. Create aHyperMetrotenant pair.

6. Create a NASHyperMetropair.

7. (Optional)Create a Qtree.

8. (Optional)Create a quota.

9. (Optional)Create asnapshot.

Describes how to checkthe HyperMetro license,add a remote device andquorum server, andcreate a HyperMetrodomain, HyperMetrotenant pair, and NASHyperMetro pair.

1. Check the license file. Thisoperation is performed on boththe local and remote storagearrays.

2. Add a remote device. Thisoperation is performed on thelocal storage array.

3. Add the quorum server. Thisoperation is performed on boththe local and remote storagearrays.

4. Create a HyperMetro domain.This operation is performed onthe local storage array.

5. Create a HyperMetro tenantpair. This operation isperformed on the local storagearray.

6. Create a NAS HyperMetropair. This operation isperformed on the local storagearray.

7. Create a Qtree. This operationis performed on the localstorage array.

8. Create a quota. This operationis performed on the localstorage array.

9. Create a snapshot. Thisoperation is performed on boththe local and remote storagearrays.

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.l Storage units have been deployed at a third-place quorum site.l If other features besides HyperMetro need to be configured for the storage system, see

the Impact and Restrictions section about the interaction among features.



64

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.

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

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



65

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

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

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



66

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.



67

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



68

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.



69

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




70




– 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





71


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



72

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



73











NOTE







NOTE





74

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.



75

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.




76



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



77

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



78

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











NOTE







NOTE





79

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.



80

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.5 Configuring Basic Storage ServicesThis section describes how to configure basic storage services for the HyperMetro solution.

4.5.1 Creating a Disk DomainThe types of disks in a disk domain decide which storage tiers can be created. The first stepfor creating a storage pool is to create a disk domain and specify the types and number ofmember disks.

Context

When creating a disk domain, you can select self-encrypting disks to encrypt the disk domain.Encrypted disks are not sold in mainland China.

You are advised to use different disk domains to create storage pools for the block storageservice and file storage service.

For 2000, 5000, 6000, 18000 series storage systems, a disk domain consists of the samestorage media or different storage media of disks. Disks of the same storage media form astorage tier. The system supports the following storage tiers:l The high-performance tier consists of SSDs and provides the highest performance. As

the SSD storage media have a high cost and low capacity, this tier is suitable for storingfrequently accessed data.

l The performance tier consists of SAS disks and provides modest performance. As SASstorage media have a modest cost and large capacity, this tier is suitable for storinginfrequently accessed data.

l The capacity tier consists of NL-SAS disks and provides the lowest performance. AsNL-SAS storage media have the lowest cost and largest capacity, the capacity tier issuitable for storing a large amount of seldom accessed data.

To prevent data loss or performance deterioration caused by a member disk failure, thestorage system employs hot spare space to take over data from the failed member disk. Thesupported hot spare policies are as follows:l – High

The capacity of one disk is used as hot spare space if the number of disks at astorage tier equals to or fewer than 12. The hot spare space non-linearly increases asthe number of disks increases. When the number of disks at a storage tier reaches175, the storage tier uses the capacity of one disk in every 100 disks as the hot sparespace.

– LowThe capacity of one disk is used as hot spare space if the number of disks at astorage tier equals to or fewer than 25. The hot spare space non-linearly increases as



81

the number of disks increases. When the number of disks at a storage tier reaches175, the storage tier uses the capacity of one disk in every 200 disks as the hot sparespace.

– None (not supported by 18000, 18000F series storage systems)The system does not provide hot spare space.

Table 4-8 describes how hot spare space changes with the number of disks. The hotspare space changes at a storage tier are used as an example here. The hot spare spacechanges at different types of storage tiers are the same.

Table 4-8 Changes of hot spare space

Number of Disks Number of Disks ofWhich Capacity IsUsed as Hot SpareSpace in High HotSpare Policya

Number of Disks ofWhich Capacity IsUsed as Hot SpareSpace in Low HotSpare Policya

(1, 12] 1 1

(12, 25] 2

(25, 50] 3 2

(50, 75] 4

(75, 125] 5 3

(125, 175] 6

(175, 275] 7 4

(275, 375] 8

…

a: Huawei storage systems use RAID 2.0+ virtualization technology. Hot sparecapacity is provided by member disks in each disk domain. Therefore, the hot sparecapacity is expressed in number of disks in this table.For example, if a disk domain is composed of 12 SSDs and the high hot spare policyis used, the hot spare space occupies the capacity of one SSD and the capacity isprovided by member disks in the disk domain. If a disk domain is composed of 13SSDs and the high hot spare policy is used, the hot spare space occupies the capacityof two SSDs.



82

NOTE

l For 18000 and 18000F series storage systems, the high hot spare policy is used by default.You can only run the change disk_domain general command on the CLI to modify the hotspare policy.

l When you are creating a disk domain, ensure that the disks used to provide hot spare spaceare sufficient.

l Hot spare space can be used for the current disk domain only.l Table 4-8 lists common capacity changes of the hot spare space. The number of disks

supported by a storage system and the capacity of their hot spare space are based on actualspecifications.

Procedure

Step 1 Log in to DeviceManager.

Step 2 Choose Provisioning > Disk Domain.

Step 3 Click Create.The Create Disk Domain dialog box is displayed.

Step 4 Name and describe the disk domain.1. In Name, enter a name for the disk domain.

NOTE

– The name must be unique.– The name can contain only letters, digits, periods (.), underscores (_), and hyphens (-).– The value contains 1 to 31 characters.

2. In Description, enter the function and properties of the disk domain. The descriptiveinformation helps identify the disk domain.

Step 5 In Encryption Type, select a type to determine whether the disk domain is created by usingself-encrypting disks.Encryption types include:



83

l Non-Encrypting Disk: create an unencrypted disk domain.l Self-Encrypting Disk: create an encrypted disk domain.

NOTE

l Non-Encrypting Disk: Non-encrypting disks are common disks that do not support the encryptionfunction.

l Self-Encrypting Disk: When data is written into or read from a disk, the data is encrypted ordecrypted using the hardware circuit and internal encryption key of the disk. The self-encryptingdisk is a special type of disk. Before using self-encrypting disks, install and configure keymanagement servers, and complete their interconnections with the storage system. For details, seeOceanStor V3 Series V300R006 Disk Encryption User Guide.

l Encrypted disks are not supported by 2000F, 5000F, 6000F, 18000F series storage systems.

l Self-encrypting and non-encrypting disks cannot exist in the same disk domain.

Step 6 Select the disks that comprise the disk domain. There are three ways to select the disks:l Select All available disks.

You only need to configure the hot spare policy for the storage tier.

NOTE

It is recommended that you create a disk domain by Manually select disks, ensure that all disksare from the same engine, so that disk domain on one engine reduces the disk failure probabilityand improve the read and write performance of disks.

l Select Specify disk type or Specify the number of disks.– Select Specify disk type (2000, 5000, 6000, 18000 series storage systems).

i. Select the storage tier according to the storage media of disks.ii. Configure the number of disks for each storage tier.iii. Configure the hot spare policy for each storage tier.

NOTE

For 18000 series storage systems, the high hot spare policy is used by default. You canonly run the change disk_domain general command on the CLI to modify the hotspare policy.

– Select Specify the number of disks (2000F, 5000F, 6000F, 18000F series storagesystems).The number of disks composing the storage tier will be configured.

l Select Manually select.

a. Click Select.

b. In the Select Disk dialog box, select the disks you need and click .c. Click OK to finish selecting disks.d. Configure the hot spare policy for each storage tier.



84

NOTE

If you plan to create a RAID 10 storage pool in the disk domain that you are creating, you are advised tomanually select an even number of disks owned by each engine for each storage tier in the disk domain toensure the reliability of RAID 10.

The storage system provides hot spare space by configuring hot space policies, so that the hot spare space cantake over data from failed member disks.

You are advised to configure a maximum of 100 disks for each tier in a disk domain. For example, if thenumber of disks on a tier is D (divide D by 100 and then round off the result to N and the remainder is M),you can refer to the following configurations:

l If D ≤ 100, configure all disks on this tier in one disk domain.

l If D > 100, create N+1 disk domains and evenly distribute all disks to the N+1 disk domains. That is,the number of disks in each disk domain is D/(N+1).

l For SmartTier, it is recommended that a maximum of 100 disks be configured for each tier in a diskdomain. The configuration of disks on each tier is the same as the preceding principle.

Example 1: The total number of SSDs in the storage system is 328, which is the value of D. (Divide 328 by100. Round off the result to 3, which is the value of N. The remainder is 28, which is the value of M). You areadvised to configure four disk domains, each of which contains 328/4 = 82 SSDs.

Example 2: If the total number of SSDs in the storage system is 223, which is the value of D. (Divide 223 by100. Round off the result to 2, which is the value of N. The remainder is 23, which is the value of M). You areadvised to configure three disk domains, each of which contains 223/3 = 74.3 disks. In this case, two diskdomains are configured with 74 disks respectively and the other disk domain is configured with 75 disks.

Example 3: If a disk domain consists of SSDs, SAS disks, and NL-SAS disks, for SmartTier, the number ofdisks of each type cannot exceed 100.

If the project requires a disk domain containing over 100 disks to meet capacity and service planningrequirements, contact Huawei technical engineers to evaluate.

Step 7 Click OK.A message is displayed, indicating that the operation succeeded.

Step 8 Click OK. The disk domain has been created. To view basic information about disks in thecurrent disk domain, click the Disk tab in the information display area below. To view the

engine to which a disk belongs, click .

----End

4.5.2 Creating a Storage PoolCreate storage pools for application servers to use the storage space provided by a storagesystem.

PrerequisitesA disk domain is created.

Contextl You are advised to use different disk domains to create storage pools for the block

storage service and file storage service.l For 2000, 5000, 6000, 18000 series storage systems, a storage pool is a logical

combination of one or multiple storage tiers in a disk domain. Different storage tiers mayhave different RAID policies.

l A RAID policy includes a RAID level and the number of disk blocks and parity blocksand parity blocks of this RAID level.



85

l The RAID level is classified into typical configuration and flexible configuration basedon the number of data blocks and parity blocks. The detailed configuration is shown inTable 4-9.

Table 4-9 RAID level configuration

RAID Level Typical Configuration Flexible Configuration

RAID 0 - -

RAID 1 l 2Da

l 4D

-

RAID 10 - -

RAID 3 l 2D+1Pb

l 4D+1Pl 8D+1P

2D+1P to 13D+1P

RAID 5 l 2D+1Pl 4D+1Pl 8D+1P

2D+1P to 13D+1P

RAID 50 l (2D+1P)x2l (4D+1P)x2l (8D+1P)x2

-

RAID 6 l 2D+2Pl 4D+2Pl 8D+2Pl 16D+2P

2D+2P to 26D+2P

a: D indicates the data block.b: P indicates the parity block.NOTE

For 2000, 5000, 6000, 18000 series storage systems, if the RAID level of one storage tier isconfigured with flexible configuration first, this tier is the primary control tier that controls othertiers' RAID policies. The number of RAID data disks of the primary control tier and the number ofRAID data disks of other tiers must be a multiple of 1, 2, 4, or 8. For example, if the performancetier is the primary control tier and its RAID policy is 3D+1P, the RAID policy of other tiers mustbe 3D+1P, 6D+2P, or so on, and cannot be 4D+1P. If you want to change the current primarycontrol tier, deselect this tier and select it again.

l For 2000, 5000, 6000, 18000 series storage systems, the following describes the storage

tiers in a storage pool:– The high performance tier, providing the highest performance, consists of SSDs. As

SSD storage media have a high cost and low capacity, this tier is applicable to theapplications such as database indexes that require a high random read/writeperformance.



86

– The performance tier, providing modest performance, consists of SAS disks. AsSAS storage media have a modest cost and large capacity, this tier provides highreliability, suitable for online applications.

– The capacity tier, providing the lowest performance, consists of NL-SAS disks. AsNL-SAS storage media have the lowest cost and largest capacity, the capacity tier issuitable for non-critical services such as data backup.

Procedure


Step 2 Choose Provisioning > Storage Pool.

Step 3 Click Create.The Create Storage Pool dialog box is displayed.

Step 4 Enter a name and description for the storage pool.1. In the Name text box, enter a name for the storage pool.

NOTE

– The name must be unique.

– The name can contain only letters, digits, periods (.), underscores (_), and hyphens (-).

– The value contains 1 to 31 characters.

2. In the Description text box, enter the function and properties of the storage pool. Thedescriptive information helps identify the storage pool.

Step 5 In the Usage text box, select File Storage Service.



87

NOTEUsage is unchangeable after it is configured.

l A storage pool whose Usage is Block Storage Service allows you to create LUNs only.

l A storage pool whose Usage is File Storage Service allows you to create file systems only.

Step 6 In Disk Domain, select the disk domain that the storage pool belongs to.

Step 7 In Storage Medium, select the storage tiers needed for the storage pool and set relatedparameters.1. Select storage tiers that meet service requirements.2. Set basic properties for the storage tiers. Table 4-10 describes related parameters.



88

Table 4-10 Storage tier parameters

Parameter Description Setting

RAIDPolicy

RAID level. The system supports RAID0, RAID 1, RAID 10, RAID 3, RAID 5,RAID 50, and RAID 6.NOTE

RAID 0 only supports configuration in CLImode. For details, see the CommandReference of the corresponding productmodel.

Select a RAID policybased on the plannedsolution.The default RAID policyof a storage tier varies withthe number of disksallocated to the storagetier.– If the number of disks

allocated to a storagetier is smaller than 10:n Default RAID

policy of the highperformance tier:RAID 10

n Default RAIDpolicy of theperformance tier:RAID 5 (4D+1P)

n Default RAIDpolicy of thecapacity tier: RAID6 (4D+2P)

– If the number of disksallocated to a storagetier is equal to 10:n Default RAID




– If the number of disksallocated to a storagetier is greater than 10:n Default RAID




89




NOTEIf the number of SSDs in adisk domain is two or three,you are advised to configurethe corresponding high-performance tier to RAID 1(2D).

Capacity The capacity that the storage tier providesfor the storage pool.Three capacity levels are provided: TB,GB, and PB.NOTE

Select Use all available capacity, and thenyou can allocate all available capacity in thisstorage layer to the new storage pool.

The capacity must be notlarger than the availablecapacity of the storage tier.

NOTE

You are advised to create RAID 6 groups on the capacity tier to ensure data security.

Step 8 Set properties of the storage pool according to the usage types.1. Click Advanced to set advanced properties for the storage pool.

Table 4-11 describes the related parameters.



90

Table 4-11 Storage pool advanced parameters


Used CapacityAlarmThreshold (%)

When the percentage of the used capacity ofthe storage pool to the total capacity of thestorage pool (the used capacity for short)reaches the used capacity alarm threshold, thesystem generates an alarm. The alarm isgenerated in 3 circumstances:– When the used capacity reaches the used

capacity alarm threshold, the systemgenerates an alarm informing that thecapacity of storage pool is insufficient.

– When the used capacity alarm threshold isnot greater than 88 and the used capacityreaches 90%, the system generates analarm informing that the storage pool isrunning out.

– When the used capacity alarm threshold isnot greater than 88 and the used capacityreaches (used capacity alarm threshold+2)%, the system generates an alarminforming that the storage pool is runningout.

NOTEIf the used capacity alarm threshold is set to 85and the used capacity reaches 85%, the systemgenerates an alarm informing that the capacity ofstorage pool is insufficient, and when the usedcapacity reaches 90%, the system generates analarm informing that the storage pool is runningout. If the used capacity alarm threshold is set as91, when the used capacity reaches 93%, thesystem generates an alarm informing that thestorage pool is running out.

A proper used capacity alarm threshold helpsyou monitor the capacity usage of a storagepool.

[Value range]1 to 95[Default value]80

Data MigrationGranularity

A logical storage space with a fixed sizedivided from a CKG. It is the smallest unit(granularity) for data migration and hotspotdata statistics collection. It is also thesmallest unit for space application and releasein a storage pool. The default value 4 MB isrecommended. The value cannot be changedafter being set.NOTE

You can configure this parameter only when RAIDlevels of storage tiers are typical configuration.

[Value range]512 KB to 64 MB[Default value]4 MB



91


Stripe Depth Stripe refers to that continuous data isdivided into data blocks of the same size anddata blocks are distributed on different disksof storage devices. In this way, I/O loads arebalanced among disks, improving read/writeperformance.Stripe depth refers to stripe size, indicatingthe size of data blocks on each disk. Smallerstripe size indicates smaller data blocks.These data blocks are distributed on moredisks, improving transmission performance.However, more time is required to finddifferent data blocks, decreasing disk locatingperformance. On the contrary, fewer datablocks indicate lower transmissionperformance but higher disk locatingperformance.The value of this parameter can be:– System auto select

The system selects the optimal stripedepth based on the RAID policy of thestorage tier and data migration granularity.

– 32 KB– 64 KB– 128 KB

128 KB is recommended for random read/write services (such as in databasescenarios).

– 256 KB– 512KB

512 KB is recommended for sequentialread/write services (such as media assetscenarios)

NOTEThe parameter value cannot be changed after beingdetermined.

[Default value]System auto select

2. Click OK.

Step 9 In the Create Storage Pool dialog box, Click OK.The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 10 Click Close.

----End



92

4.5.3 Creating a vStoreThis operation enables you to allocate independent private space to a vStore. The spacecontains resources such as LUNs, file systems, and ports. Each vStore can obtain completestorage services, but its resources and networks are isolated from other vStores, preventinginterference. Before allocating and managing vStore services, you need to create vStores.

PrerequisitesOnly the super administrator can create vStores.

Procedure


Step 2 Choose vStore > Create.

Step 3 In the Create vStore dialog box, configure a name and description for the vStore.

Step 4 Click OK.The Execution Result dialog box is displayed.

Step 5 Click Close. The vStore is created successfully.The system will automatically show LUNs and file systems owned by each tenant.

NOTE

Non-Internet Explorer browsers support both card and list views and the switchover of the two views toshow LUNs and file systems of tenants. However, Internet Explorer only supports the list view. Thefollowing will use the card view as an example.

l On the upper right of the card view, click to switch to the list view of tenants.

l On the upper right of the list view, click to switch to the card view of tenants.

l ClickDetails to view detailed resource information about a tenant.

----End

Follow-up ProcedureAfter the super administrator creates vStores, it needs to create vStore users to managevStores. vStore users can log in to DeviceManager and check vStore views.

NOTEFor details about the roles preset by the storage system and their permissions, see the chapter of PlanningManagement User Accounts in OceanStor V3 Series V300R006 SmartMulti-Tenant Feature Guide forBlock.

4.5.4 Creating a File SystemThis section explains how to create file systems. File systems can share storage resources inthe form of directories.



93

Prerequisites

l A storage pool is created and is used for file storage service.l Only administrators and super administrators are allowed to create file systems.l After enabling the file system function of a mirror domain, you can run the show

mirror_domain general [ mirror_domain_id=? ] command to query the mirrordomain information about a storage system. To obtain the mirror domain ID, run theshow mirror_domain general command without parameters. To enable or disable thefile system function of a mirror domain, run the change mirror_domain generalmirror_domain_id=? nas_switch=? command. For details, see Command Reference.

ContextMirror domain: the storage engine that is responsible for access to and storage structure ofdata and indexes, storage space management, cache management, lock mechanism, andtransaction mechanism at the storage layer.

PrecautionsIf a storage pool has thin file systems and the capacity of all file systems exceeds that of thestorage pool, services may be interrupted if the capacity of the storage pool is used up.

Procedure


Step 2 Go to the file system page.

The operation path varies with user types:

l System user: Click vStore, select the desired vStore, and click Details to go to thevStore view. Choose Provisioning > File System.

l vStore user: In the vStore view, choose Provisioning > File System.

Step 3 Click Create.The Create File System dialog box is displayed.

Step 4 Create a file system. Table 4-12 describes related file system parameters.



94

Table 4-12 File system parameters

Parameter Description Value

Name Name of the file system. [Value range]l The name must be unique.l The name can only contain

letters, digits, and underscores(_).

l The name can be 1 to 255characters in length.

[Example]filesystem001



95


Description Description of the file system. [Example]-

Thin Provisioning Determine whether the thinprovisioning function is enabledso that you can create thin filesystems.NOTE

After the function is enabled, thestorage system does not allocate theconfigured capacity to the filesystem at a time. Within configuredcapacity, the storage systemallocates the storage resource to thefile system on demand, based on theactual capacity used by the host.

[Example]Enable

Owning StoragePool

Storage pool to which the filesystem you are creating belongs.NOTE

l You can only choose the storagepool which is used for FileStorage Service.

l If the storage system has nostorage pool, click Create tocreate one.

[Example]storagepool002

Capacity File system capacity.l When the Thin function is

enabled, the capacity is themaximum capacity allocatedto the thin file system. That is,the total capacity dynamicallyallocated to the file systemcannot exceed the maximumcapacity.

l When the Thin function isdisabled, the capacity will beallocated to a thick file systemonce and for all.

l The system support creatingblock-level file system. Selectcapacity unit Blocks whencreating a file system. OneBlock = 512 Bytes.

[Value range]l The maximum capacity for

creating a thick file systemdoes not exceed the availablecapacity of the storage poolwhere the thick file systemresides.

l The maximum capacity forcreating a file system canexceed the available capacityof the storage pool where thethin file system resides butcannot exceed 1 GB to 16384TB.

l The system support creatingblock-level file system. Selectcapacity unit Blocks whencreating a file system. OneBlock = 512 Bytes.

[Example]3 GB



96


Use all the freecapacity of theowning storagepool

If this option is selected, all freespace of the owning storage poolis allocated to this file system.NOTE

If a thin file system exists in astorage pool, services of the thin filesystem may fail after all freecapacity of the storage pool is usedto create a thick file system.

[Example]Enable

Snapshot SpaceRatio (%)

Percentage of the file systemsnapshot space to the file systemspace.

[Value range]The value is an integer rangingfrom 0 to 50.[Example]20[Default]20



97


ApplicationScenario

Application scenarios of filesystems.l VM: File systems apply to

VMs. After this scenario isselected, the system will setthe block size of file systemsto 8 KB, and automaticallyadjust system resources toadapt to this scenario.

l Database: File systems applyto databases. You are advisedto use full-SSDs for storagepools to which file systemsbelong and enable the datacompression function.– When storage pools to

which file systems belonguse full-SSDs, the systemwill set the size of a filesystem block to 16 KB andenable the datacompression function bydefault. If you chooseAdvanced > Tuning anddisable the datacompression function, thesystem will set the size ofa file system block to 8KB. In this scenario, youare advised to enable thedata compression function.

– When storage pools towhich file systems belongdo not use full-SSDs, thesystem will set the size ofa file system block to 8KB and disable the datacompression function bydefault. If you chooseAdvanced > Tuning anddisable the datacompression function, thesystem will still set thesize of a file system blockto 8 KB. In this scenario,you are advised not toenable the datacompression function.

[Value range]The value can be VM, Database,or User-defined.[Example]User-defined



98


l User-defined: In this scenario,users need to manuallyspecify the block size of filesystems.

File System BlockSize

If Application Scenario is set toUser Defined, this parameterneeds to be specified.Data in the file system consists offixed-length disk blocks. The sizeof the blocks (also known as filesystem block size) affects diskspace usage and performance.You are advised to use the blocksize following the principlesbelow.l Select 4 KB when the size of

most files in the file system issmaller than 100 KB.

l Select 8 KB when the size ofmost files in the file system isbetween 100 KB and 1 MB.

l Select 16 KB when the size ofmost files in the file system isbetween 1 MB and 100 MB.

l Select 32 KB when the size ofmost files in the file system isbetween 100 MB and 1 GB.

l Select 64 KB when the size ofmost files in the file system islarger than 1 GB, the filesystem mainly processesbandwidth-consuming largeI/Os (in scenarios such asM&E industry, and archiveand backup of large files), orthe file size and scenarios arenot specified.

[Value range]The value can be 4KB, 8KB,16KB, 32KB, or 64KB.[Example]64KB



99


Quantity Number of file systems batchcreated. Set this parameter basedon your need.NOTE

l This option is invalid when youselect Use all the free capacityof the owning storage pool.

l A maximum of 100 file systemscan be created at one time.When multiple file systems arecreated, the system willautomatically add suffixes todistinguish between file systems.

l File systems batch created havethe same capacity.

[Value range]1 to 100[Example]5

Manually specifythe suffix

When creating multiple filesystems, the systemautomatically appends a suffixnumber to the name of each filesystem for file system distinction.You can manually set the startsuffix number after selecting thisoption.NOTE

If this option is not selected, thesuffix number starts at 0000 bydefault.

[Example]-

Start Number This parameter is valid afterManually specify the suffix isselected. From the start numberyou configured, the systemincrementally appends a suffixnumber to the name of each filesystem for file system distinction.

[Value range]0 to (10000 - the quantity of filesystems to create)NOTE

If you want to create 30 file systems,the start number is from 0 to 9970.

Step 5 Optional: Set a timing snapshot policy.1. Click Timing Snapshot Policy.

The Timing Snapshot Policy dialog box is displayed.2. Set a timing snapshot policy.

– Select Hours and Minute to execute the timing snapshot. Begin calculating at 0o'clock everyday. For example, if Every 6 Hours 10 Minute is specified, thentiming snapshot will be executed at 06:10, 12:20, and 18:30 every day.

– Select Daily and set Hours and execution start time. For example, if Hours: 01:00and 17:00 are specified, and Minute: 1 is specified, then timing snapshot will beexecuted at 01:01 and 17:01 every day.

– Select Weekly and set Week and execution start time. For example, if Week: Day3, and Time: 11:50 is specified, then timing snapshot will be executed at 11:50 onSunday and Wednesday every week.



100

– Select Monthly and set Date and execution start time. For example, if Date: 2 and30 are specified, and Time: 12:10 is specified, then timing snapshot will beexecuted at 12:10 on dates 2 and 30 every month.

3. Click OK.

Step 6 Optional: Modify advanced properties of the file system.1. Click Advanced.

The Advanced dialog box is displayed.2. Set advanced properties of the file system.

Click the Properties, Tuning and WORM tabs and set related parameters. Table 4-13,Table 4-14 and Table 4-15 describe related parameters.

Table 4-13 Property parameters


OwningController

Controller to which the file systembelongs. You are advised to allocate filesystems to different controllers for loadbalancing.NOTE

If you are not sure about the owningcontroller, select Auto Select. The storagesystem will automatically select the owningcontroller for file systems.

[Value range]Based on actual conditionsof available controllers ofthe storage device.[Example]Auto select[Default]Auto select

CapacityAlarmThreshold(%)

Alarm threshold of the file systemcapacity.

[Value range]The value is an integerranging from 50 to 95.[Example]90[Default]90



101


InitialCapacityAllocationPolicy

Policy for the storage tier to allocatecapacity to a file system.– Automatic allocation: The storage

system automatically allocatescapacity to a file system based onthe ratio of the available capacity ofthe performance tier to that of thecapacity tier. Capacity is allocatedfrom the high performance tier onlywhen the capacity of theperformance tier and capacity tier isinsufficient.

– Allocate from the high performancetier first: The storage systemallocates capacity to a file systemfrom the high performance tier first.If the capacity of the highperformance tier is insufficient, thestorage system allocates capacityfrom the other storage tiers, firstfrom the performance tier and thenfrom the capacity tier.

– Allocate from the performance tierfirst: The storage system allocatescapacity to a file system from theperformance tier first. If the capacityof the performance tier isinsufficient, the storage systemallocates capacity from the otherstorage tiers, first from the capacitytier and then from the highperformance tier.

– Allocate from the capacity tier first:The storage system allocatescapacity to a file system from thecapacity tier first. If the capacity ofthe capacity tier is insufficient, thestorage system allocates capacityfrom the other storage tiers, firstfrom the performance tier and thenfrom the high performance tier.

[Value range]The value can beAutomatic allocation,Allocate from the highperformance tier first,Allocate from theperformance tier first, orAllocate from thecapacity tier first.[Example]Automatic allocation[Default]Automatic allocation



102


SnapshotDirectoryVisibility

Specifies whether snapshot directoriesare visible.

[Value range]The value can be Visibleor Invisible.[Example]Visible[Default]Visible

Max. Numberof TimingSnapshots

Upper limit of the file system timingsnapshots. When the number of createdsnapshots reaches the upper limit, thesystem automatically deletes the earliesttiming snapshots.


DeleteObsoleteRead-OnlySnapshots

Specifies whether Delete ObsoleteRead-Only Snapshots is enabled.When used space of a file systemreaches the Capacity alarm thresholdand used space of snapshots is largerthan reserved space for snapshots, thesystem automatically deletes the earliestread-only snapshots.

[Example]Enable[Default]Disable

Checksum Specifies whether Checksum isenabled. This function is used to checkdata integrity. When it is enabled,checksum will be automaticallycalculated when data is being written,ensuring integrity of the data to beaccessed.NOTE

Enabling Checksum will impair the systemperformance.

[Example]Enable[Default]Enable

AutomaticUpdate ofAtime

Specifies whether Automatic Updateof Atime is enabled. Atime is a timewhen file systems are accessed. Afterthis function is enabled, Atime will beupdated every time data on file systemsis accessed.NOTE

Enabling Automatic Update of Atime willimpair the system performance.

[Example]Enable[Default]Disable



103


CapacityAutonegotiation Policy

A storage system supports the followingcapacity autonegotiation policies:– Not Use Capacity

Autonegotiation: The storagecapacity used by a file system isfixed and is not flexibly adjusted bythe storage system.

– Auto Expand Capacity: increasesfile system capacity and meets users'requirements in data write when theavailable space of a file system isabout to run out and the storage poolhas available space.

– Auto Reduce or Expand Capacity:The storage system automaticallyadjusts the file system capacitybased on file system space usage.When the available space of a filesystem is about to run out and thestorage pool has available space,automatic capacity expansion willbe used to increase file systemcapacity. When the file system'sstorage space is released, it can bereclaimed into a storage pool andused by other file systems in datawrite requests.

[Example]Auto Expand Capacity[Default]Not Use Autonegotiation

CapacityReclamationMode

A storage system supports the followingcapacity reclamation modes:– Preferentially Expand Capacity:

Expand the capacity to increase thefile system capacity.

– Preferentially Delete OldSnapshot: Delete old snapshots toreclaim space for increasing the filesystem capacity. IfHyperReplication and HyperMetroare configured for storage systems,the capacity autonegotiation policyof the primary storage system willbe synchronized to the secondarystorage system. If PreferentiallyDelete Old Snapshot is adopted,ensure that Delete Obsolete Read-Only Snapshots is enabled for thesecondary storage system.

[Example]Preferentially ExpandCapacity[Default]Preferentially ExpandCapacity



104


Auto AdjustCapacity

After you select Auto AdjustCapacity, automatic capacityexpansion or reduction policy for a filesystem will take effect during theservice running.

[Example]Enable[Default]Enable

Auto ExpandTriggerThreshold(%)

When the ratio of the used capacity tothe total capacity of the file system isgreater than the preset value, the storagesystem automatically triggers filesystem capacity expansion.


Auto ReduceTriggerThreshold(%)

When the ratio of the used capacity tothe total capacity of the file system issmaller than the preset value, thestorage system automatically triggersfile system space reclamation andreduces file system capacity.


Auto ExpandUpper Limit

Set the auto expand upper limit. [Value range]The value is an integerranging from file systemcapacity to 16 PB.[Example]120 GB[Default]File system capacity *120%

Auto ReduceLower Limit

Set the auto reduce lower limit. [Value range]The value is an integerranging from 1 GB toAuto Expand UpperLimit.[Example]100 GB[Default]File system capacity



105


AutoExpanded/ReducedCapacityEach Time

Set the auto expanded or reducedcapacity for each time.

[Value range]The value is an integerranging from 64 MB to100 GB.[Example]1 GB[Default]1 GB

Table 4-14 Tuning parameters

Parameter

Description Value

PriorityControl

Priority control of SmartQoS.NOTE

To apply this policy, you must purchase theSmartQoS license.

[Value range]The value can be Low,Medium, or High.[Example]Low[Default]Low

TrafficControl

Traffic control policy of SmartQoS.NOTE

To apply this policy, you must purchase theSmartQoS license.

If no traffic control policy exists, clickCreate to create one.

[Default]-

Enabledatacompression

Enable the data compression function.Storage space saved by using datacompression.NOTE

OceanStor 2200 V3 storage system does notsupport this function.

[Example]Enable data compression

Enablededuplication

Enable the deduplication function. Storagespace saved by using deduplication.NOTE

– To apply this policy, you must purchase theSmartDedupe license.

– OceanStor 2200 V3 storage system does notsupport this function.

[Example]Enable deduplication



106

Parameter

Description Value

SmartPartition

Specify SmartPartition for the file system.SmartPartition allocates cache resources ofstorage system to the file system to meetthe cache hit ratio required by differentapplications.NOTE

– To apply this policy, you must purchase theSmartPartition license.

– Select the owning controller of file systemmanually. This controller must be the sameas the owning controllers of SmartPartition,or SmartPartition is unavailable.

If no SmartPartition exists, click Create tocreate one.

[Default]-

SmartCachePartition

To specify SmartCache partition for the filesystem. In the scenario that read operationsare more than write operations and hot spotdata exists, use the SSDs as cache byemploying SSD high read performance toimprove system read performance.NOTE

– To apply this policy, you must purchase theSmartCache license.

– Please select the owning controller of thefile system manually. This controller must bethe same as the owning controllers ofSmartCache partition, or SmartCache isunavailable.

– SmartCache does not support self-encryptingSSD.

If no SmartCache partition exists, clickCreate to create one.

[Default]-

Table 4-15 WORM parameters

Parameter

Description Value

Enable If you want to create a WORM filesystem, select Enable.

[Default value]Not enabled



107

Parameter

Description Value

Mode Compliance mode of WORM protection.Modes are:– Enterprise Compliance Moden Files within the protection period

cannot be modified, renamed, ordeleted by command users, but canbe deleted by systemadministrators.

n When the protection period isoverdue, the file expires and it canbe deleted, but cannot be modifiedor renamed by common users andsystem administrators.

– Regulatory Compliance Moden Files within the protection period

cannot be modified, renamed, ordeleted by common users andsystem administrators.

n When the protection period isoverdue, the file expires and it canbe deleted, but cannot be modifiedor renamed by common users andsystem administrators.

[Default value]Regulatory Compliance

Min.Retention

The shortest file protection periodsupported by WORM file system.

[Value range]0 to 70 years or Indefinite.[Default value]3 yearsNOTE

Min. Retention must besmaller than or equal toDefault Retention and Max.Retention.

Max.Retention

The longest file protection periodsupported by WORM file system.

[Value range]1 day to 70 years orIndefinite.[Default value]70 years



108

Parameter

Description Value

DefaultRetention

If no expiration time is configured for afile, the expiration time of the file isdetermined by the default retention.

[Value range]No less than Min.Retention and no biggerthan Max. Retention orIndefinite.[Default value]Regulatory complianceMode:70 yearsEnterprise complianceMode:3 yearsNOTE

To set Default Retention asIndefinite, you must set Max.Retention to Indefinite.Otherwise, the setting fails.

AutomaticLock

If the function is enabled and a file is fileis not modified within the Lockout WaitTime (hours), files enters locked stateautomatically. Therefore, the file is underprotection, and you can only read the fileunder locked state, but cannot modify,delete or rename it.NOTE

Write operation include file data change ormetadata change.

[Default value]Enable

LockoutWait Time(hours)

Retention of a file enters the locked state.NOTE

This parameter is valid only when AutomaticLock is enabled.

[Value range]The value is an integerranging from 2 to 168.[Default value]2

AutomaticallyDelete

If this mode is enabled, the systemautomatically deletes files whoseprotection period is overdue.

[Default value]Disabled

NOTE

– If WORM is enabled, the file system created is a WORM file system. More information aboutWORM file system, see OceanStor V3 Series V300R006 WORM Feature Guide.

– Before creating a WORM file system, you must initialize WORM regulatory clock throughCLI. The CLI command is change system secure_compliance_clock date=?.

3. Click OK.The Create File System dialog box is displayed.

Step 7 Confirm that you want to create this file system.



109

1. Click OK.The Execution Result dialog box is displayed indicating that the operation succeeded.

2. Click Close.

----End

4.5.5 Creating a Logical PortThis operation enables you to create a logical port for managing and accessing file based onEthernet ports, bond ports, or VLANs.

PrecautionsThe number of logical ports created for each controller is recommended not more than 64. Ifthe number exceeds 64 and a large number of ports do not work properly, logical ports drifttowards the small number of ports available. As a result, service performance deteriorates.

Procedure


Step 2 Choose vStore.

Step 3 In the vStore view, click or to select the vStore for which a user is to be created.

Step 4 At the lower-right of the vStore view, click Details.The vStore view is displayed.

Step 5 Choose Provisioning > Port and click Create.

The Create Logical Port dialog box is displayed.

Step 6 In the Create Logical Port dialog box, configure related parameters.Table 4-16 describes related parameters.



110

Table 4-16 Logical port parameters


Name Name of the logical port.The name must meet thefollowing requirements sothat the logical port isavailable to compatibleapplications:l The name must be

unique.l The name can contain

only letters, digits,underscores (_), periods(.), and hyphens (-).

l The name contains 1 to31 characters.

[Example]lif01



111


IP Address Type IP address type of thelogical port, including IPv4or IPv6.

[Example]IPv4

IPv4 Address IPv4 address of the logicalport.

[Example]192.168.100.11

Subnet Mask IPv4 subnet mask of thelogical port.

[Example]255.255.0.0

IPv4 Gateway IPv4 gateway of the logicalport.

[Example]192.168.100.1

IPv6 Address IPv6 address of the logicalport.

[Example]fc00::1234

Prefix IPv6 prefix length of thelogical port.

[Example]64

IPv6 Gateway IPv6 gateway of the logicalport.

[Example]fc00::1

Primary Port Port to which the logicalport belongs, including theEthernet port, Bond port,and VLAN.

[Example]None

Failover Group Failover group name.NOTE

l If a failover group isspecified, services on thefailed primary port will betaken over by a port in thespecified failover group.

l If no failover group isspecified, services on thefailed primary port will betaken over by a port in thedefault failover group.

[Example]None



112


IP Address Failover After IP address failover isenabled, services are failedover to other normal portswithin the failover group ifthe primary port fails.However, the IP addressused by services remainsunchanged.NOTE

Shares of file systems do notsupport the multipathingmode. IP address failover isused to improve reliability oflinks.

[Example]Enable

Failback Mode Mode in which services failback to the primary portafter the primary port isrecovered. The mode can bemanual or automatic.NOTE

l If Failback Mode isManual, ensure that thelink to the primary port isnormal before the failback.Services will manually failback to the primary portonly when the link to theprimary port keeps normalfor over five minutes.

l If Failback Mode isAutomatic, ensure that thelink to the primary port isnormal before the failback.Services will auto fail backto the primary port onlywhen the link to theprimary port keeps normalfor over five minutes.

[Example]Automatic

Activate Now To activate the logical portimmediately.

[Example]Enable

Role Role of the logical port. [Example]Service

Dynamic DNS When the dynamic DNS isenabled, the DNS server willautomatically andperiodically update the IPaddress configured for thelogical port.

[Example]Enable



113

Step 7 Click OK.

The Success dialog box is displayed indicating that the logical port has been successfullycreated.

Step 8 Click OK.

----End

4.5.6 Sharing a File SystemThis section describes how to share a file system.

File systems can be shared using four protocols: NFS and CIFS. Local file systems are sharedwith hosts. When the local file systems are shared with hosts, the local storage arraysynchronizes the configuration to the remote file systems. After the local file systems areshared with hosts, data is synchronized from the local file systems to the remote file systems.You can access a file system only after the file system is shared. For details about how toshare a file system, see the chapter of Sharing File Systems in OceanStor V3 SeriesV300R006 SmartMulti-Tenant Feature Guide for File.

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

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 (forFS).

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

Precautions

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



114

StoragePool Name

File SystemCapacity(Capacity ofCommon FileSystems andCapacity ofFile SystemswithSmartThinConfigured)

Capacity of theStorage Pool ToWhich FileSystems Belong

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 2 Choose Settings > License Management.

Step 3 Check the active license files.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

This operation is only performed on the local storage system.



115

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.

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 device

such as a security gateway to encrypt links to prevent information leakage.l If the version of the local device is different from that of the remote device, you need to

add a remote device on the newer version device. Otherwise the operation may fail.l In HyperMetro scenarios, the two storage arrays need redundant links. Therefore, add

two Fibre Channel links or iSCSI links.

l Add an iSCSI Link

a. Set Link Type to iSCSI.b. Set parameters for the iSCSI link. Table 4-17 lists related parameters.



116

Table 4-17 iSCSI link parameters


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

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-18 lists related parameters.



117

Table 4-18 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 ProcedureIn 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.

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.

PrerequisitesTo enable quorum links to be added to storage arrays successfully, ensure the following itemsbefore creating a quorum server.



118

l The system time of the storage arrays and quorum server is correct. The validity periodof 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


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-19 lists related configuration parameters.



119

Table 4-19 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.)

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



120

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


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.



121

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 vStore PairThis operation creates a HyperMetro pair for vStores on the primary and secondary storagearrays. This ensures the consistency of the vStore environment on the primary and secondarystorage arrays for file systems.

Prerequisitesl The storage devices work normally and correctly communicate with each other.

Configurations can be properly delivered.l A HyperMetro domain has been created for the storage arrays.l vStores have been created on the storage arrays.l NAS HyperMetro licenses have been imported and activated on the primary and

secondary storage arrays.l If quorum servers are configured, the quorum servers are normal and properly

communicate with storage devices.

Contextl This operation is performed on the local storage system only.l When a NAS HyperMetro pair is created, the primary/secondary relationship of file

systems in the NAS HyperMetro pair must be consistent with that in the HyperMetrovStore pair.

l File systems in a HyperMetro pair work in active-passive (A-P) mode. If the primary filesystem is abnormal, the system automatically switches to the secondary file system in theHyperMetro pair. The NFSv3 and NFSv4 protocols support uninterrupted serviceswitching.

Procedure




122

Step 2 Choose Data Protection > HyperMetro > HyperMetro vStore Pair.

Step 3 Click Create.The Create HyperMetro vStore Pair dialog box is displayed.

Step 4 Set the properties for the HyperMetro vStore pair. Table 4-20 describes related parameters.

Table 4-20 HyperMetro vStore pair parameters

Parameter Description

HyperMetro Domain Name of a HyperMetro domain.

Local vStore Name of a local vStore.

Remote vStore Name of a remote vStore.

Step 5 Click Automatically Added to Pair List or Manually Added to Pair List.

Step 6 Set the properties for the preferred site setting mode. Table 4-21 describes related parameters.

Table 4-21 Preferred site setting mode parameters


Along with active The system will identify the activationstates of local and remote sites, and specifythe active site as the preferred site.

Local Specify the local storage system as thepreferred site.

Remote Specify the remote storage system as thepreferred site.

Step 7 Confirm the operation to create a HyperMetro vStore pair.1. Click OK.

The Warning dialog box is displayed.2. Confirm the information in the dialog box and select I have read and understood the

consequences associated with performing this operation.3. Click OK.

The Execution Result dialog box is displayed.4. Click Close. The HyperMetro vStore pair is successfully created.

----End

4.6.6 Creating a NAS 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 HyperMetro



123

relationships 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 A HyperMetro vStore pair has been created.

l The names of the primary and secondary files must be the same. The secondary filesystem must be newly created, that is, files, directories, snapshots, quota trees, andquotas are not created in the secondary file system. You are advised to set the samecapacity for the primary and secondary file systems. If the reserved space of snapshots orSmartDedupe and SmartCompression are configured for a file system, the availablespace of the file system will be affected. If the available capacity of the secondary filesystem is smaller than that of the primary file system, the HyperMetro pair will bedisconnected during data synchronization due to insufficient space of the secondary filesystem.

ContextThis operation is performed on the local storage system only.

Procedure


Step 2 Choose Data Protection > HyperMetro > HyperMetro Pair.

Step 3 Click 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 File System in Resource Type and specify HyperMetro vStore Pair in which a NASHyperMetro pair is to be created. Click Next.

Step 6 Select the local file systems for the HyperMetro pair in Available Local Resources. Thenclick Automatically Added to Pair List.

NOTE

The names of a local file system and a remote file system must be the same. Click Automatically Added toPair List. The storage system automatically selects the remote file system that shares the same name with thelocal file system in Available Remote Resources.

Step 7 Click Next.

Step 8 Set the data synchronization properties for the HyperMetro pair. Table 4-22 describes relatedparameters.



124

Table 4-22 HyperMetro parameters


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

takes a long time. Thisvalue is applicable toscenarios where theservice load is heavy.The speed ranges from 0MB/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]Low, Medium, High, andHighestNOTE

If the file systems to beconfigured in the HyperMetropair carry host services and theservice load is changingconstantly, it is advised toretain the default valueMedium to ensure properrunning of the host services.

[Default value]Medium

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

automaticallysynchronizes data.

l Manual: Datasynchronization must beperformed manually.

[Value range]Automatic and Manual[Default value]Automatic



125


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 Local and remote data isinconsistent. After thecreation is complete, datais automaticallysynchronized.

NOTEThe logical data of differentfile systems is inconsistentwhen the file systems arecreated. Therefore, you mustsynchronize data if two filesystems are newly created instorage systems that work inactive-active mode.

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

Step 9 Click Next.The Summary page is displayed.

Step 10 Confirm the HyperMetro information and click Finish.The Danger dialog box is displayed.

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

Step 12 Click Close.

----End

4.6.7 (Optional) Creating a Quota TreeQuota tree is the level-1 subdirectory of a file system. In a quota tree, you can set directoryquotas, user quotas, or user group quotas. You can manage space occupied by files in thedirectory.

Prerequisites

At least one file system is created.



126

Procedure






Step 3 Select a file system for which you want to create a quota tree. On the menu bar, choose More> Create Quota Tree.The Create Quota Tree dialog box is displayed.

NOTE

You can also right-click a file system for which you want to create a quota tree and then choose CreateQuota Tree.

Step 4 Create a quota tree. Table 4-23 describes the related parameters.

Table 4-23 Quota tree parameters


Name Name of the quota tree. [Value range]l The name must be unique.l For V3R6C00, the name

contains only letters, digits,and underscores (_).

l For V3R6C10, the namecontains only letters, digits,and special characters. Specialcharacters include !"#$%&'()*+-.;<=>?@[\]^`{_|}~ andspaces. On the CLI, somecharacters need to be enteredas escape characters. Forexample, \| indicates |, ||indicates \, \q indicates ?, and\s indicates spaces.


[Example]quotatree001

Quantity Number of quota trees created ina batch. Set this parameter basedon your need.

[Value range]1 to 500[Example]5



127


Owning FileSystem

Owning file system of the quotatree.

[Example]filesystem_001

Quota After quota is enabled, thesystem restricts the number offiles and file size of quota tree.NOTE

If you there is quota requirement onthe file system for which you wantto create a quota tree, it isrecommended to enable the quotafunction.

[Example]Enable

Step 5 Confirm that quota tree is successfully created.1. Click OK.

The security alert dialog box is displayed.

NOTE

This message will be displayed only after the quota function is enabled.

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

3. Click Close.

----End

4.6.8 (Optional) Creating a QuotaThis operation enables you to restrict the space used by files or the number of files in the rootdirectory or by user/user group.

Prerequisitesl At least one file system and quota tree have been created.l If you want to create quota for a specified user or user group, the user or user group must

have been created.

ContextFor the following types of groups and users, the quota is not limited but is tracked anddisplayed: root user group and its users, and a storage system's Administrators user groupand its users, and users in a Windows operating system's Administrators user group.

Procedure






128



Step 3 Select a file system for which you want to create a quota. On the menu bar, choose More >Create Quota.The Create Quota Wizard dialog box is displayed.

Step 4 Select a quota type and directory, user or user group.l Directory quota

a. Select a quota type of Directory quota, and click Next.b. Select the directory whose quota you want to restrict.

n Select All Quota Tree.

n Select Specific Quota Tree. Click and select a quota tree whose quota youwant to restrict.

NOTE

If no quota tree is available, create one.

c. Click Next.l User quota

a. Select a quota type of User quota, and click Next.b. Select a specified quota tree in Quota Tree.c. Select the user whose quota you want to restrict.

n Select All Users.n Select Specific Users. Select a specified user in the lower area.

NOTE

○ If no user is available, add one.

○ If you select Local authentication user, click Find, in the pop-up Add Userdialog boxes to select the user or user group you want to add. Click OK. You can

choose Provisioning > User Authentication to create localauthentication user in the Local Authentication User tab.

○ If you select Domain user, enter the corresponding name in Name, and click Add.For NIS domain and LDAP domain, the name format is Domain user name. ForAD domain, the name format is Domain name\Domain user name. Pleasecontact the domain server administrator to obtain the domain user name.

○ When CIFS users are mapped to NFS users, quota statistics will be collected forthe NFS users or owning user group.

d. Click Next.l User group quota

a. Select a quota type of User group quota, and click Next.b. Select a specified quota tree in Quota Tree.c. Select the user group whose quota you want to restrict.

n Select All Users Groups.n Select Specific User Groups. Select a specified user in the lower area.



129

NOTE

○ If no user group is available, add one.

○ If you select Local authentication user group, click Find, in the pop-up AddUser Group dialog boxes to select the user or user group you want to add. Click

OK. You can choose Provisioning > User Authentication to createlocal authentication user group in the Local Authentication User Group tab.

○ If you select Domain user group, enter the corresponding name in Name, andclick Add. The name format is Domain user group name. Please contact thedomain server administrator to obtain the domain user group name.

○ User group quota does not support AD domain.

d. Click Next.

Step 5 Set the space quota or file quantity quota, and click Next.Table 4-24 describes related parameters.

Table 4-24 Quota parameters


Hard Quota If the space quota exceeds thehard quota, the systemimmediately forbids writeoperations and prevents usersfrom using extra file space.

[Value range]Larger than 0 and no less than thecapacity of the file system.[Example]100 GB

Soft Quota If the space quota exceeds thesoft quota, the system generatesan alarm but still allows writeoperations. After exceeding thehard quota, the systemimmediately forbids writeoperations.

[Value range]l If the space hard quota is not

configured, the space softquota must be larger than 0and no less than the capacityof the file system.

l If the space hard quota isconfigured, the space softquota must be larger than 0and smaller than the hardquota.

[Example]80 GB

Hard Quota (K) If the file quantity quota exceedsthe hard quota, the systemimmediately forbids writeoperations and prevents usersfrom using extra files. The unit ofthe hard quota is set to K.

[Value range]Larger than 0 and no less than2,000,000.[Example]2



130


Soft Quota (K) If the file quantity quota exceedsthe soft quota, the systemgenerates an alarm but stillallows write operations. Afterexceeding the hard quota, thesystem immediately forbids writeoperations. The unit of the softquota is set to K.

[Value range]l If the file quantity hard quota

is not configured, the filequantity soft quota must belarger than 0 and no less than2,000,000.

l If the file quantity hard quotais configured, the file quantitysoft quota must be larger than0 and smaller than the hardquota.

[Example]1

Step 6 Confirm that the quota is successfully created.1. Confirm the quota information and click Finish.

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

NOTEIf Quota Type in step 1 is set to User quota or User group quota, Quota Tree in step 2 is set to aspecific quota tree, and the quota function has not been enabled for the quota tree, Enable quotaimmediately in the lower left corner is selected by default.

2. Click Close.The security alert dialog box is displayed.

NOTE

This message will be displayed only after Enable quota immediately is selected.

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

4. Click Close.

----End

4.6.9 (Optional) Creating a SnapshotA snapshot created for a file system is a data copy generated on the file system at a specificpoint in time. Creating a snapshot is only to create a pointer used to point to the source filesystem and thus almost does not occupy storage space.

4.6.9.1 Manually Creating a SnapshotA snapshot is a duplicate of the data generated at a certain point in time on the source filesystem. The duplicate is available immediately after being generated. Reads from theduplicate does not impact on data on the source file system.

PrerequisitesOne or more file systems are created in a storage system.



131

PrecautionsFor different file systems, you are advised to create snapshots in different hours.

Procedure


Step 2 You can use either of the following methods to manually create a snapshot:1. Method 1: Go to the file system page.


– System user: Click vStore, select the desired vStore, and click Details to go tothe vStore view. Choose Provisioning > File System.

– vStore user: In the vStore view, choose Provisioning > File System.

Select a file system for which you want to create a snapshot. On the menu bar, chooseMore > Create Snapshot. The Create Snapshot dialog box is displayed.

NOTE

You can also right-click a file system for which you want to create a snapshot and then chooseCreate Snapshot.

2. Method 2: Go to the snapshot page.


– System user: Click vStore, select the desired vStore, and click Details to go tothe vStore view. Choose Data Protection > Snapshot.

– vStore user: In the vStore view, choose Data Protection > Snapshot.

Select a file system for which you want to create a snapshot. On the menu bar, chooseCreate. The Create Snapshot dialog box is displayed.

Step 3 Create a snapshot manually. Table 4-25 describes the related parameters.

Table 4-25 Snapshot parameters


Name Name of the file system snapshot. [Value range]l The name must be unique.l The name can only contain

letters, digits, and underscores(_).


[Example]snapshot001

Step 4 Click OK.The Success dialog box is displayed, indicating that the operation succeeded.



132

Step 5 Click OK.

----End

Follow-up ProcedureAfter creating a snapshot, right-click a file in a Windows client and choose Properties. In theProperties dialog box that is displayed, click the Previous Versions tab to view a snapshotlist. In the Date modified drop-down list, select a backup restoration point and click Copy tocopy the directory (including all content under it) or the file in the backup restoration point tolocal or other servers. Content of the file and directory is consistent with the backup content.

4.6.9.2 Creating a Periodic SnapshotMultiple snapshots can be automatically generated for a file system based on a presetsnapshot policy. When data on the source file system is lost due to virus attack or maliciousdamage, the snapshot generated before the event can be used to recover the lost data.

PrerequisitesA storage pool is created for file systems in a storage system.

Precautionsl For different file systems, you are advised to create snapshots in different hours.l By default, the upper limit for the number of periodic snapshots is 16. Select the file

system for which you want to create periodic snapshots, and click Properties. In the FileSystem Properties dialog box, choose More > Advanced and modify the value in Max.Number for Timing Snapshots.

l When the number of created snapshots reaches the upper limit, the system automaticallydeletes the earliest snapshots.

Procedure






Step 3 Click Create.The Create File System dialog box is displayed.

Step 4 Click Timing Snapshot Policy.The Timing Snapshot Policy dialog box is displayed.

Step 5 Set a timing snapshot policy.1. Optional: Select Hours and Minute to execute the timing snapshot. Begin calculating at

0 o'clock everyday. For example, if Every 6 Hours 10 Minute is specified, then timingsnapshot will be executed at 06:10, 12:20, and 18:30 every day.



133

2. Optional: Select Daily and set Hours and execution start time. For example, if Hours:01:00 and 17:00 are specified, and Minute: 1 is specified, then timing snapshot will beexecuted at 01:01 and 17:01 every day.

3. Optional: Select Weekly and set Week and execution start time. For example, if Week:Day 3, and Time: 11:50 is specified, then timing snapshot will be executed at 11:50 onSunday and Wednesday every week.

4. Optional: Select Monthly and set Date and execution start time. For example, if Date:2 and 30 are specified, and Time: 12:10 is specified, then timing snapshot will beexecuted at 12:10 on dates 2 and 30 every month.

Step 6 Click OK.

----End

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



134

5 Management

About This Chapter

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

5.1 Managing HyperMetro in the System ViewThis section describes how to manage HyperMetro in the system view.

5.2 Managing HyperMetro in the Tenant ViewThis section describes how to manage HyperMetro in the tenant view.

5.1 Managing HyperMetro in the System ViewThis section describes how to manage HyperMetro in the system view.

5.1.1 Managing a HyperMetro vStore PairYou can modify parameters of a HyperMetro vStore pair or dynamically adjust theHyperMetro relationship between different vStores.

5.1.1.1 Viewing HyperMetro vStore Pair InformationThis operation enables you to view information about existing HyperMetro vStore pairs andmonitor the running status of NAS HyperMetro pairs.

PrerequisitesA HyperMetro vStore pair has been created.

Procedure



OceanStor V3 SeriesHyperMetro Feature Guide for File 5 Management


135

Step 3 View the basic information about a HyperMetro vStore pair. Table 5-1 describes the relatedparameters.



HyperMetro vStore Pair ID ID of the HyperMetro vStore pair.

Local vStore ID Local vStore ID.

Local vStore Name Name of the local vStore.

Remote vStore ID Remote vStore ID.

Remote vStore Name Name of the remote vStore.

Pair Running Status Running status of a pair of local and remoteresources in the HyperMetro vStore pair,determined by the status of the local andremote vStores in the HyperMetro vStorepair as well as the running status of all NASHyperMetro pairs for the vStores. The valuecan be Normal, To Be Synchronized,Force Start, or Invalid.l If the HyperMetro vStore pair has failed,

the value is Invalid.l If the HyperMetro vStore pair works

properly, the value is determined bymembers. If all NAS HyperMetro pairsare normal, the value is Normal.

Configuration Status Whether primary and secondary siteconfigurations are synchronized. The valuecan be Synchronizing, Normal, or To BeSynchronized.

Owning HyperMetro Domain ID ID of the owning HyperMetro domain.

HyperMetro Domain Name Name of the owning HyperMetro domain.

Link Status The value can be Link Up or Link Down.

Role Whether the site is a primary or preferredsite. The value can be Preferred or Non-preferred.

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

Step 4 View the basic information about a HyperMetro pair. Table 5-2 describes the relatedparameters.



136

Table 5-2 HyperMetro pair parameters


Local Resource Name Name of a local resource.

Local Resource ID ID of a local resource.

Remote Resource Name Name of a remote resource.

Remote Resource ID ID of a remote resource.

Pair ID ID of a pair of local and remote resources ina HyperMetro pair.

Pair Health Status Health status of a pair of local and remoteresources in a HyperMetro pair. The valuecan be Normal or Fault.

Pair Running Status Running status of a pair of local and remoteresources. The value can be Normal, To BeSynchronized, Paused, Synchronizing,Force Start, or Invalid.

Link Status Status of a link connected to a HyperMetropair.

Local Resource Role Whether the site is a primary or preferredsite. The value can be Preferred or Non-preferred.

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

Configuration Status Whether primary and secondary siteconfigurations are synchronized. The valuecan be Synchronizing, Normal, or To BeSynchronized.

Recovery Policy A recovery policy supports the followingrecovery modes:l Manual: If a HyperMetro pair is in the

To Be Synchronized state, managementand maintenance personnel mustmanually synchronize data between thelocal and remote resources.

l Automatic: If a HyperMetro pair is inthe Synchronizing state, the systemautomatically synchronizes incrementaldata from the primary resource to thesecondary resource.

Local Resource Data Status Data status of a local resource.

Remote Resource Data Status Data status of a remote resource.

Local Resource Host Access Status Data read/write status of a local resource.



137


Remote Resource Host Access Status Data read/write status of a remote resource.

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

Data Synchronization Direction Data synchronization direction. Possiblevalues are Local to Remote and Remote toLocal.

----End

5.1.1.2 Checking HyperMetro vStore Pair Information

This operation enables you to view information about existing HyperMetro vStore pairs,logical ports and file systems.

Prerequisites

A HyperMetro vStore pair has been created.

Procedure



Step 3 View the basic information about a HyperMetro vStore pair. Table 5-3 describes relatedparameters.



Local vStore Name Name of the local vStore.

Remote vStore Name Name of the remote vStore.

vStore Pair Check results of local vStore. The value can be Normal,Abnormal and Unknown.

Logical Port Check results of local vStore. The value can be Normal,Abnormal and Unknown.

File System Check results of local vStore. The value can be Normal,Abnormal, Warning and Unknown.

Step 4 Select one item from the table to view its details. Table 5-4 describes related parameters.



138

Table 5-4 HyperMetro vStore pair detailed parameters


vStore Pair Running Status: The value can be Normal,Unsynchronized, Force Start and Invalid.Configuration: The value can be Normal, To BeSynchronized and Synchronizing.

Logical Port Health Status Check Results: The value can be OK, Theprimary LIF port of the primary end fails, The primaryLIF port of the secondary end fails and Unknown.Configuration Check Results: The value can be OK, Subnetmasks of logical ports at two ends are inconsistent., IPaddresses of primary and secondary ends areinconsistent., LIF roles of primary and secondary endsare inconsistent., Types of current LIF ports at primaryand secondary ends are inconsistent., VLAN IDs ofcurrent LIF ports at primary and secondary ends areinconsistent., Gateways of logical ports at two ends areinconsistent., Failback modes of logical ports at two endsare inconsistent, Failover switches of logical ports at twoends are inconsistent. and Unknown.

File System Health Status Check Results: The value can be OK, Theprimary vStore contains faulty file systems, Thesecondary vStore contains faulty file systems andUnknown.Configuration Check Results: The value can be OK, Theprimary vStore contains file systems not configured withHyperMetro (not recommended), The secondary vStorecontains file systems not configured with HyperMetro(not recommended), File system capacities at primaryand secondary ends are inconsistent (not recommended),File system names at primary and secondary ends areinconsistent (not recommended), and Unknown.

----End

5.1.1.3 Deleting a HyperMetro vStore PairThis operation deletes an existing HyperMetro vStore pair to save resources if you need to re-establish the HyperMetro vStore pair between different vStores.

Prerequisitesl The storage devices work normally and correctly communicate with each other.

Configurations can be properly delivered.l The status of the HyperMetro vStore pair is Normal.l No NAS HyperMetro pair is configured for the vStores in the HyperMetro vStore pair.l If the HyperMetro vStore pair works in quorum server mode, the quorum servers are

normal and properly communicate with storage devices.



139

Context

After a HyperMetro vStore pair is deleted, the HyperMetro relationship between the vStoresis removed and the resources of the HyperMetro vStore pair are released.

Procedure



Step 3 Select the HyperMetro vStore pair to be deleted and click Delete.The Warning dialog box is displayed.

Step 4 Confirm that you want to delete the HyperMetro vStore pair.

1. Optional: Select Only delete the configuration information about the local device ifthe HyperMetro vStore pair fails or the remote device is disconnected.

2. Confirm the information in the dialog box and select I have read and understood theconsequences associated with performing this operation.

3. Click OK.The Execution Result dialog box is displayed.

4. Click Close.

----End

5.1.1.4 Primary/Secondary Switchover

When the primary site of a HyperMetro vStore pair suffers a disaster, the secondary site canquickly take over services to protect service continuity.

Prerequisites

You can perform primary/secondary switchover only if the following requirements are met:

l Communication between the storage arrays is normal.

l The LIF port at the secondary site is normal.

l The vStore pair for which you want to perform primary/secondary switchover hasHyperMetro pairs.

Context

l The secondary site (primary site after switching) provides service access.

l The NFSv3 and NFSv4 protocols require uninterrupted service switching.

l Primary and secondary switching is performed on the HyperMetro vStore pair and allNAS HyperMetro pairs of the vStores. After the switching, the running status of theHyperMetro pairs is normal and the configurations are consistent.

l The LIF is activated at the secondary site and deactivated at the primary site.



140

Procedure



Step 3 Select the HyperMetro vStore pair on which the switchover is to be performed and clickPrimary/Secondary Switchover.The Danger dialog box is displayed.

Step 4 Confirm the primary/secondary switchover.1. Optional: Select You are about to forcibly switch over the working site of the

HyperMetro vStore pair.

NOTE

p>If Pair Running Status of the HyperMetro vStore is Normal and Configuration Status is Normal,do not select You are about to forcibly switch over the working site of the HyperMetro vStore pair.In other conditions, select You are about to forcibly switch over the working site of the HyperMetrovStore pair. Note that some configuration data of the primary end may be lost if this option is selected.

2. Confirm the information in the dialog box and select I have read and understood theconsequences associated with performing this operation.


4. Click Close.

----End

5.1.1.5 Forcible StartIf a system fault occurs and the quorum server fails to implement arbitration, you can forciblystart the local or remote site to provide services after the fault is rectified.

Prerequisitesl The NAS HyperMetro pair is in the To Be Synchronized or Paused state.l The HyperMetro management link is disconnected at the secondary end.l Only the secondary end of the HyperMetro vStore pair can be forcibly started. After

being forcibly started, the secondary end changes to the primary end.

Procedure



Step 3 Select the HyperMetro vStore pair to be forcibly started and click Force Start.The Danger dialog box is displayed.

Step 4 Forcibly start the HyperMetro vStore pair.1. Confirm the information in the dialog box and select I have read and understood the

consequences associated with performing this operation.



141


3. Click Close.

----End

Follow-up Procedure

If you want to start the secondary storage forcibly when its quota switch is in on or initializingstate, you are advised to disable and then enable the quota switch after the file system isstarted.

5.1.1.6 Modifying the Owning Tenant of an Existing File System

If you want to create NAS active-active services for a file system that does not belong to anytenant, configure an owning tenant for this file system first.

Context

Log in to the CLI of the storage system as the super administrator and enter the developerview.

Procedure

Step 1 On the CLI, type change user_mode current_mode user_mode=developer and press Enterto enter the developer view.admin:/>change user_mode current_mode user_mode=developerdeveloper:/> \\ Login succeeds.

Step 2 Run change file_system vstore to modify the owning tenant of the file system.

For example, configure the tenant whose ID is 1 as the owning tenant of the file system whoseID is 0.

developer:/>change file_system vstore file_system_id=0 type=vstore vstore_id=1WARNING: Before changing the owning vStore of the file system, note the following:1. If the NAS share, antivirus or HyperMetro service is configured for the file system, delete the service and then change the owning vStore.Suggestion:After the owning vStore is changed:1. Check whether the NAS share, antivirus or HyperMetro service configuration of the file system still exists in the original vStore. If there is such configuration information, delete it.2. Configure the NAS share, antivirus, HyperMetro, or NDMP service for the file system if necessary.Have you read warning message carefully(y/n)yAre you sure you really want to perform the operation?(y/n)yCommand executed successfully.

NOTEYou can run the show vstore command without any parameter to obtain the ID of a tenant.admin:/>show vstore id=1ID : 1Name : vStore_TestDescription : create vstore for testRunning Status : Normal

----End



142

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

5.1.2.1 Viewing HyperMetro Domain Information

Through 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-5 explains the relatedparameters.

Table 5-5 HyperMetro domain parameters


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.1.2.2 Modifying a HyperMetro Domain

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



143

Prerequisites

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

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.1.2.3 Deleting a HyperMetro Domain

If a HyperMetro domain is no longer needed, you can delete it.

Prerequisites

The related HyperMetro Pair has being deleted.

Procedure



Step 3 Select a HyperMetro domain that you want to delete and click Delete.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

If you do not select this option, you cannot delete the HyperMetro domain when the local device isdisconnected from the remote device.

Step 5 Select I have read and understand the consequences associated with performing thisoperation. and click OK.

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



144

Step 7 Click Close.

----End

5.1.3 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.1.3.1 Viewing HyperMetro Pair Information

Through 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 4 View the basic information about a HyperMetro. Table 5-6 describes related 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



145


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

[Example]Normal

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

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.

[Example]Normal

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



146


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

Resource Data Status 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



147


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]Remote to Local

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-7 describes the related 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



148




l Manual: Thesynchronizationoperation must beperformed manually.

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



[Example]Disabled

----End



149

5.1.3.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-8 explains therelated parameters.



150

Table 5-8 Parameters of HyperMetro properties



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




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




[Value range]Possible values areAutomatic and Manual.



151



[Example]Disabled


[Example]500

----End

5.1.3.3 Synchronizing a HyperMetro Pair

Through 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



152

5.1.3.4 Suspending a HyperMetro Pair

If 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.3.5 Deleting a HyperMetro Pair

If a HyperMetro is no longer needed, you can delete it.

Prerequisites

You can delete the HyperMetro pair only when its Pair Running Status is Paused, ForceStart or To be synchronized, and its secondary LUNs are not mapped.

Procedure



Step 3 Select a HyperMetro that you want to delete and click Delete.



153

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


Step 5 Select I have read and understand the consequences associated with performing thisoperation. and click OK.


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.4 Managing Quorum ServersBy managing quorum servers, you can create and delete quorum servers, and add links forquorum servers.

5.1.4.1 Viewing Quorum Server Information

Through 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-9 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-10 describesrelated parameters.



154

Table 5-10 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

5.1.4.2 Modifying Quorum Server Information

Through 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-11explains 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



155


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.1.4.3 Adding a Link

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

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.1.4.4 Removing a Link

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

Procedure



Step 3 Select a quorum server from which you want to remove a link and click Remove in the Linkarea.



156

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.1.4.5 Removing a Quorum Server

Through this operation, you can delete quorum servers that have been created.

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

Procedure



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.1.4.6 Uninstalling the Arbitration Software

This section describes how to uninstall the arbitration software.

Prerequisites

The arbitration software has been correctly installed, and the arbitration software 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.



157

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.1. When the uninstallation progress is completed, run the ps -elf | grep quorum_serverd

command to check whether the arbitration software is uninstalled successfully.2. If the quorum_serverd process does not exist, the arbitration software is uninstalled

successfully.XXX@Linux:~/package # ps -elf | grep quorum_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.1.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.



158

Step 4 Import and activate the signed certificate.

1. Send the certificate request file to the certificate authority for signing or use theenterprise's root certificate for signing. Then click Import and Activate.The Import Certificate dialog box is displayed.

2. Configure certificate parameters. Table 5-12 describes the related parameters.

Table 5-12 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 theconsequences associated with performing this operation.. Then click OK.The Success dialog box is displayed.

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

NOTEThe CA certificate is not displayed in the certificate list.

Step 5 View the certificate information, Table 5-13 describes the related parameters.

Table 5-13 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.



159


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-14 describes the related parameters.

Table 5-14 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.

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.



160

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

Table 5-15 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

5.2 Managing HyperMetro in the Tenant ViewThis section describes how to manage HyperMetro in the tenant view.

5.2.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 2 Go to the NAS HyperMetro page.




161

l System user: Click vStore, select the desired vStore, and click Details to go to thevStore view. Choose Data Protection > HyperMetro.

l vStore user: In the vStore view, choose Data Protection > HyperMetro.


Step 4 View the basic information about a HyperMetro. Table 5-16 describes related 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

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



162


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



163


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



164



[Example]Disabled



Data SynchronizationDirection

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

[Example]Remote to Local

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-17 describes the related 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



165





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


End Time Time when datasynchronization for aHyperMetro ends.



[Example]Disabled

----End



166

5.2.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 are to be modified 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 and modify parameters as required. Table 5-18 describesrelated parameters.



167

Table 5-18 Parameters of HyperMetro properties



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




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




[Value range]Possible values areAutomatic and Manual.



168



[Example]-



----End

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

PrerequisitesThe 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 to be synchronized and choose Synchronize from the shortcutmenu.The Warning 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 understood the

consequences associated with performing this operation. Then click OK.



169

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

----End

5.2.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 the HyperMetro pair to be suspended and choose Pause from the shortcut menu.

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

Step 5 Confirm the operation to suspend the HyperMetro pair.1. Confirm the information in the dialog box and click OK.

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

NOTE

After the HyperMetro pair is suspended, data synchronization between the local and remote sites in thepair is also suspended.

----End

5.2.5 Deleting a HyperMetro PairIf a HyperMetro is no longer needed, you can delete it.

Prerequisites

Only when Pair Running Status is Paused, Force Start or To be synchronized, you candelete the HyperMetro pair.



170

Procedure






Step 3 Select the HyperMetro pair to be deleted and click Delete.The Warning 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.

NOTE


Step 5 Select I have read and understood the consequences associated with performing thisoperation and click OK.


----End



171

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 What Can I Do If the Remote Connection Fails to Be Created with the TOE InterfaceModule

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

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?

OceanStor V3 SeriesHyperMetro Feature Guide for File 6 FAQs


172

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.

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.



173

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


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



174


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.

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.



175

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

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

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



176

6.5 What Can I Do If the Remote Connection Fails to BeCreated with the TOE Interface Module

QuestionWhat can I do if the remote connection fails to be created with the TOE interface module?

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

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



177

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

2. Click the Hardware tab.

3. Select Network adapter.Record the MAC Address displayed on the right side.

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.



178

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.

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.



179

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.



180

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



181

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 File 7 Troubleshooting


182

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 File 7 Troubleshooting


183

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 File A How to Obtain Help


184

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 File A How to Obtain Help


185



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 File B Glossary


186



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 File C Acronyms and Abbreviations


187

S

SAS Serial Attached SCSI

SCSI Internet Small Computer Systems Interface

SSD Solid State Drive

OceanStor V3 SeriesHyperMetro Feature Guide for File C Acronyms and Abbreviations


188

Documents

HyperMetro Feature Guide for File - Exclusive Networks · 2019-01-25 · OceanStor V3 Series V300R006 HyperMetro Feature Guide for File Issue 05 Date 2018-01-30 HUAWEI TECHNOLOGIES