OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003 Remote Replication Feature Guide For Block 03

OceanStor 5300 V3&5500 V3&5600 V3&5800
V3&6800 V3 Storage System

V300R003
Remote Replication Feature Guide

for Block
Issue 02
Date 2015-12-10
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
Issue 02 (2015-12-10) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block About This Document
About This Document
This document describes the implementation principles and application scenarios of the
remote replication feature. Also, it explains how to configure and manage remote replications.
Intended Audience
This document is intended for:
l Technical support engineers
l Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

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

avoided, could result in death or serious injury.
WARNING

avoided, may result in minor or moderate injury.

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

tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Issue 02 (2015-12-10) Huawei Proprietary and Confidential ii

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block About This Document
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 03 (2016-04-30)
This issue is the third official release, which incorporates the following changes:
Optimized descriptions about section Availability.
Optimized descriptions about section Restrictions.
Optimized the description of configuration operations in Configuration Example.
Added FAQs for remote replication licenses.
Issue 02 (2015-12-10)
This issue is the second official release. The updates are as follows:
Description about principles is optimized.
1.2 Availability is revised.
Issue 01 (2015-08-30)
This issue is the first official release.
Issue 02 (2015-12-10) Huawei Proprietary and Confidential iii

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block Contents
Contents
About This Document.....................................................................................................................ii

1 Feature Description....................................................................................................................... 1
1.1 Overview........................................................................................................................................................................ 2
1.2 Availability..................................................................................................................................................................... 3
1.3 Working Principle........................................................................................................................................................... 4
1.3.1 Related Concepts......................................................................................................................................................... 4
1.3.2 Data Replication.......................................................................................................................................................... 8
1.3.3 Service Switchover.................................................................................................................................................... 12
1.3.4 Data Recovery........................................................................................................................................................... 14
1.3.5 Functions of a Consistency Group.............................................................................................................................15
1.4 Restrictions................................................................................................................................................................... 18
1.5 Application Scenarios...................................................................................................................................................23
2 Configuration Example.............................................................................................................. 32
2.1 Central Backup and Disaster Recovery........................................................................................................................ 33
2.1.1 Requirement Analysis................................................................................................................................................33
2.1.2 Configuration Planning..............................................................................................................................................36
2.1.3 Configuration Operations.......................................................................................................................................... 43
2.1.4 Configuration Verification......................................................................................................................................... 53
3 Disaster Recovery........................................................................................................................ 55
4 Configuration and Management.............................................................................................. 57
4.1 Viewing System Information........................................................................................................................................58
4.2 Setting Device Information.......................................................................................................................................... 60
4.3 Configuring Remote Replication..................................................................................................................................60
4.3.1 Configuration Process................................................................................................................................................61
4.3.2 Preparing for the Configuration.................................................................................................................................61
4.3.3 Checking the License File......................................................................................................................................... 62
4.3.4 Managing a Route......................................................................................................................................................62
4.3.5 Adding a Remote Device...........................................................................................................................................64
4.3.6 Creating a Remote Replication..................................................................................................................................71
4.3.6.1 Creating a Synchronous Remote Replication......................................................................................................... 71
4.3.6.2 Creating an Asynchronous Remote Replication.....................................................................................................73
4.3.7 Creating a Consistency Group................................................................................................................................... 80
Issue 02 (2015-12-10) Huawei Proprietary and Confidential iv

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.4 Managing Remote Replications....................................................................................................................................86

4.4.1 Viewing Information of Remote Replication Pair..................................................................................................... 87
4.4.2 Modifying the Properties of a Remote Replication Pair..........................................................................................100
4.4.3 Synchronizing a Remote Replication Pair...............................................................................................................107
4.4.4 Splitting a Remote Replication Pair........................................................................................................................ 108
4.4.5 Performing a Primary/Secondary Switchover for a Remote Replication................................................................ 110
4.4.6 Enabling Protection For Secondary Resource Of Remote Replication Pair............................................................111
4.4.7 Disabling Protection For Secondary Resource Of Remote Replication Pair...........................................................112
4.4.8 Synchronizing Remote Status..................................................................................................................................113
4.4.9 Deleting a Remote Replication Pair.........................................................................................................................114
4.5 Managing Consistency Groups...................................................................................................................................115
4.5.1 Viewing Consistency Group Information................................................................................................................ 116
4.5.2 Changing the Properties of a Consistency Group....................................................................................................130
4.5.3 Synchronizing a Consistency Group....................................................................................................................... 136
4.5.4 Splitting a Consistency Group................................................................................................................................. 137
4.5.5 Performing Primary/Secondary Switchover of a Consistency Group..................................................................... 138
4.5.6 Enabling Protection For Secondary Resource Of Consistency Groups.................................................................. 140
4.5.7 Disabling Protection For Secondary Resource Of Consistency Groups................................................................. 141
4.5.8 Adding a Remote Replication Pair.......................................................................................................................... 142
4.5.9 Removing a Remote Replication Pair..................................................................................................................... 143
4.5.10 Deleting a Consistency Group............................................................................................................................... 143
5 FAQs.............................................................................................................................................146
5.1 What are the differences between synchronous remote replication and asynchronous remote replication............... 147
5.2 How do I use the secondary LUN in a remote replication......................................................................................... 147
5.3 Why information about the primary device and the secondary device in a remote replication cannot be updated in
real time............................................................................................................................................................................ 148
5.4 What is the relationship among a remote replication, clone, and consistency group.................................................148
5.5 What is the principle of setting bandwidth for remote replication and LUN copy among storage arrays................. 149
5.6 Precautions for Creating a Remote Link.................................................................................................................... 149
5.7 Functions of Reserved Space During Asynchronous Remote Replication................................................................ 150
5.8 Impact of Modifying Consistency Group Properties..................................................................................................151
5.9 When performing a remote replication task, is an initial synchronization required to synchronize data from the
primary storage system to the secondary storage system................................................................................................. 151
5.10 Do I need to stop the services on the primary storage system before performing the initial synchronization.........151
5.11 Impact of the Secondary Storage System Failure on Remote Replication............................................................... 152
5.12 Do File Remote Replication and Block Remote Replication Use the Same License...............................................152
A Using the External Storage System to Perform Initial Synchronization for a Remote
Replication .................................................................................................................................... 153
A.1 Introduction................................................................................................................................................................154
A.2 Configuration Operation (Using the LUN Copy Feature of the External Storage System)...................................... 155
A.3 Configuration Operation (Using the LUN Copy Feature of the Production and DR Centers)..................................156
B How to Obtain Help................................................................................................................. 159
Issue 02 (2015-12-10) Huawei Proprietary and Confidential v

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
B.1 Preparations for Contacting Huawei.......................................................................................................................... 160

B.1.1 Collecting Troubleshooting Information.................................................................................................................160
B.1.2 Making Debugging Preparations............................................................................................................................ 160
B.2 How to Use the Document......................................................................................................................................... 160
B.3 How to Obtain Help from Website............................................................................................................................ 160
B.4 Ways to Contact Huawei............................................................................................................................................161
C Glossary...................................................................................................................................... 162
D Acronyms and Abbreviations................................................................................................ 174
Issue 02 (2015-12-10) Huawei Proprietary and Confidential vi

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block 1 Feature Description
1 Feature Description
About This Chapter
The remote replication feature provides flexible and powerful data replication functions
including remote data backup and recovery, continuous support for service data, and disaster
recovery.
1.1 Overview
This section describes the background, definition, purposes, and benefits of the remote
replication feature.
1.2 Availability
This section describes the availability of the remote replication feature in terms of license
requirement and applicable versions.
1.3 Working Principle
This section describes how the remote replication feature replicates data, switches services,
and recovers data, and introduces the function of a consistency group.
1.4 Restrictions
This section describes the impact of the remote replication feature on system performance,
interaction between the remote replication feature and other features, and restrictions on the
remote replication feature.
1.5 Application Scenarios
The remote replication feature is used for data backup and DR. The typical application
scenarios include central backup and DR, and 3DC.
Issue 02 (2015-12-10) Huawei Proprietary and Confidential 1

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
1.1 Overview
This section describes the background, definition, purposes, and benefits of the remote
Background
As the digitalization drive advances in various industries, data has become critical to the
operation of enterprises, and customers impose increasingly demanding requirements on the
stability of storage systems. Although some storage devices offer extremely high stability,
they fail to prevent natural disasters from irrecoverable damage to production systems caused
by natural disasters. To ensure the consistency, recoverability, and high reliability of data
access, remote disaster recovery solutions emerge. The remote replication technology is one
of the key technologies used by remote disaster recovery solutions. HyperReplication is a
remote replication feature developed by Huawei.
Definition
As a core technology for disaster recovery and backup, the remote replication technology can
implement remote data synchronization and disaster recovery.
The remote replication feature supports two replication modes:

l Synchronous remote replication
In this mode, data is synchronized in real time to achieve full protection for data
consistency and minimized data loss in the event of a disaster.
l Asynchronous Remote Replication
Data is synchronized periodically to minimize service performance deterioration caused
by the long latency of long-distance data transmission.
Benefit
Table 1-1 lists the purposes and benefits of the remote replication feature.
Table 1-1 Purposes and benefits of the remote replication feature
Function of Remote Purpose Benefit

Replication
Remote backup and To recover service data using This feature prevents damage
recovery backup data in the remote caused by data loss in the case
storage system after the that data at the primary site
service data becomes becomes unusable.
unusable.
Continuous support for To quickly switch service data This feature prevents damage
services from the primary site to the caused by a service interruption
secondary site, protecting upon a failure at the primary
service continuity. site.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Function of Remote Purpose Benefit

Replication
Disaster recovery To recover data at the primary This feature prevents the
site using backup data at the damage caused by service data
secondary site in the case of a loss or long recovery duration.
disaster.
Note 1: The primary site is a data center that includes the primary storage system,
application servers, and links.
Note 2: The secondary site is a backup center that includes the secondary storage system,
application servers, and links.
Note 3: Unless otherwise specified, hosts mentioned in this document refer to application
servers.
1.2 Availability
This section describes the availability of the remote replication feature in terms of license
requirement and applicable versions.
License Requirement
Remote replication is a value-added feature that requires a software license in both the
primary storage system and the secondary storage system.
Applicable Product Versions

This section describes applicable versions of the primary storage system and secondary
storage system, as shown in Table 1-2 and Table 1-3.
Table 1-2 Applicable versions of primary storage system
Product Version
OceanStor 5300 V3/5500 V3/5600 V3/5800 V3/6800 V300R003

V3
Table 1-3 Applicable versions of secondary storage system
Product Version
OceanStor 18500/18800/18800F V100R001C00SPC200 and later versions
OceanStor 5300 V3/5500 V3/5600 V300R001 and later versions

V3/5800 V3/6800 V3/6900 V3a
OceanStor S2600T/S5500T/S5600T/ V200R002C00SPC200 and later versions

S5800T/S6800T

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Product Version
a: 6900 V3 is no longer supported in V300R002 and later versions.
Applicable Software Versions

Product Version
OceanStor BCManagera V100R005C00 and later versions
a: To obtain the BCManager software installation package, log in to http://

support.huawei.com/enterprise/, choose Downloads > IT > Storage > Massive Storage
> Data Protection > OceanStor BCManager.
1.3 Working Principle

This section describes how the remote replication feature replicates data, switches services,
and recovers data, and introduces the function of a consistency group.
1.3.1 Related Concepts

This section describes concepts related to the remote replication feature, including pair,
consistency group, synchronization, splitting, primary/secondary switchover, data status and
writable secondary LUN.
Remote replication replicates data based on storage systems and is independent of upper-layer
host services. Full implementation of remote replication consists of five phases: creating a
remote replication pair, replicating data, switching services, restoring data, and restoring the
pair, as shown in Figure 1-1.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-1 Implementation of remote replication

Primary Secondary
storage system storage system
Remote 1. Creating remote replication sessions
replication links
Primary Secondary
LUN LUN The remote replication session
corresponds to a pair.
Multiple associated pairs can form a
consistency group.
Pair
Remote
2. Replicating data
replication links
Primary Secondary Data is replicated during
LUN LUN
synchronization.
Phases in a full remote replication process
Users can stop synchronization by

performing a splitting operation.
Pair
Remote
replication links 3. Switching services
Secondary Primary The data status and secondary
LUN LUN LUNs accessible property show
whether a primary/secondary
switchover can be performed.
Pair A new pair is generated after a
primary/secondary switchover.
Remote
replication links 4. Recovering data
Secondary Primary
LUN LUN Data recovery is implemented
using synchronization.
Pair
Remote
replication links 5. Restoring pairs
Primary Secondary
LUN LUN The original pair is restored after
another primary/secondary
switchover.
Pair
Pair
A pair refers to the relationship between a primary logical unit number (LUN) and a
secondary LUN of a remote replication session. In a pair, data can be replicated only from the
primary LUN to the secondary LUN. People can speak over two phones only after a
connection is set up between the phones by dialup. Similarly, data can be replicated from the
primary LUN to the secondary LUN only after a pair is set up between the LUNs. The
primary and secondary LUNs of a pair must come from different storage systems.
A pair may be in different running status at different phases of a remote replication session.
By viewing the running status of a pair, you can determine whether you need to perform an
operation for that pair, and what operation should be performed if you need. After you
perform an operation, you can view the pair running status to determine whether the operation
succeeded. Table 1-4 describes the pair running status involved in a remote replication
session.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 1-4 Pair running status of a remote replication session

Running Status Description
Normal Data synchronization between the primary LUN and the secondary
LUN is complete.
Split Data replication between the primary LUN and the secondary LUN
is suspended. The pair running status changes to Split after the
primary and secondary LUNs are split from each other manually by
the administrator.
Interrupted The pair running status changes to Interrupted after the pair
between the primary and secondary LUNs is interrupted because the
links used by the remote replication are interrupted or any of the two
LUNs fails.
To be recovery If a remote replication session needs to be restored using a Manual

policy after the fault that caused a pair interruption is removed, the
pair running status changes to To be recover. This status reminds
users of manual synchronization between the original primary LUN
and the secondary LUN to restore the pair.
Invalid If the original basic pair properties of the primary or secondary LUN
are changed (for example, the secondary LUN configured at the
secondary site is deleted) after the pair is interrupted, configuration
becomes inconsistent between the primary and secondary sites and
the pair running status changes to Invalid.
Synchronizing Data is being copied from the primary LUN to the secondary LUN.
When a pair is in this state, data on the secondary LUN is unusable.
Consistency Group
A consistency group is a collection of pairs that have a service relationship with each other.
For example, the primary storage system has three primary LUNs, which respectively store
service data, log, and change tracking information of a database. If data on any of the three
LUNs becomes invalid, all data on the three LUNs becomes unusable. For these LUNs, you
can create a consistency group, and add the remote replication sessions of the LUNs to the
consistency group.
Synchronization
Synchronization refers to a process during which data is copied from the primary LUN to the
secondary LUN of a pair. Synchronization can be performed for a single remote replication
session or multiple remote replication sessions in a consistency group at one time.
Splitting
Splitting refers to the action of stopping data replication from the primary LUN to the
secondary LUN. This operation can be performed only by the administrator. Splitting can be
performed for a single remote replication session or multiple remote replication sessions in a
consistency group at one time. After the splitting, the pair relationship between the primary

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
LUN and the secondary LUN still exists and the access permission of hosts for the primary
and secondary LUNs remains unchanged.
At some time, for example when the bandwidth is not enough to support critical services, you
probably do not want to copy data from the primary LUN to the secondary LUN. In such
cases, you can split the secondary LUN from the primary LUN to suspend data
synchronization.
Users can effectively control a remote replication process by performing synchronization and
splitting.
Primary/Secondary Switchover
A primary/secondary switchover is a process during which the primary and secondary LUNs
in a pair exchange their roles. A primary/secondary switchover changes the original
relationship between the LUNs in a remote replication session (a new pair is formed). You can
perform a primary/secondary switchover for a single remote replication session or multiple
remote replication sessions in a consistency group at one time. Usually, a primary/secondary
switchover needs to be performed in the following scenarios:
l The remote replication links are reestablished and data is synchronized between the
primary and secondary sites after the primary site recovers from the disaster. In such a
case, the administrator needs to perform a primary/secondary switchover for the remote
replication session at the primary or secondary site.
l When a device in the primary storage system needs to be replaced, the administrator
performs primary/secondary switchover for the remote replication session at the primary
or secondary site.
After a primary/secondary switchover, services are running on the secondary storage system.
Therefore, it is required that data on the secondary LUN is available before a primary/
secondary switchover is initiated. You can determine whether data on the secondary LUN is
available by viewing the data status of the secondary LUN.
Data Status
The remote replication feature identifies the data status of a pair based on the data difference
between the primary LUN and the secondary LUN. When a disaster occurs, the remote
replication feature determines whether to allow a primary/secondary switchover for a pair
based on the data status of the pair. There are two pair data states: Consistent and
Inconsistent.
Writable Secondary LUN

A writable secondary LUN can receive data from hosts. After a remote replication is
configured, its secondary LUN state is read-only. If a fault occurs on the primary LUN the
administrator needs to set the secondary LUN state to writable through the action of Disable
Protection for Secondary Resource so that the secondary storage system can take over host
services to ensure service continuity. The two usual scenarios for setting a writable secondary
LUN are as follows:
l When a fault occurs on the primary LUN, and the remote replication is linked down, the
administrator needs to set the secondary LUN state to writable on the secondary storage
system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
l When a fault occurs on the primary LUN, and the remote replication is linked up, the
administrator needs to split pair before setting the secondary LUN state to writable on
the primary or secondary storage system.
Link Compression
Link compression is an online compression technology. In asynchronous remote replication,
data is compressed first on the primary device before being transferred. Then the compressed
data is decompressed on the secondary device, reducing bandwidth required for data transfer.
Link compression used by the OceanStor 5300 V3/5500 V3/5600 V3/5800 V3/6800 V3
storage system has the following highlights:
l Online data compression
Data to be transferred is compressed in real time.
l Intelligent compression
The system identifies whether data can be compressed in advance, minimizing
unnecessary compression and improving transfer efficiency.
l High reliability and security
Lossless compression technology is used to ensure data security. Multiple check methods
are used to ensure data reliability. After receiving data, the secondary device verifies data
correctness and checks data consistency after the data is decompressed.
l User unawareness
Link compression does not affect services running on the host and is transparent to users.
l Compatibility with full backup and incremental backup
Link compression compresses all data that is transferred over the network regardless of
upper-layer services.
1.3.2 Data Replication

Data replication refers to the process of writing service data generated by hosts to the
secondary LUN in the secondary storage system for backup and disaster recovery. The writing
process varies depending on the remote replication mode. This section describes how a
synchronous remote replication session and an asynchronous remote session process host
writes.
Writing Process in Synchronous Remote Replication

A synchronous remote replication session replicates data in real time from the primary storage
system to the secondary storage system. The characteristics of synchronous remote replication
are as follows:
l After receiving a write I/O request from a host, the primary storage system sends the
request to the primary and secondary LUNs.
l The data write result is returned to the host only after the data is written to both primary
and secondary LUNs. The data write result is determined by whether the data is
successfully written to the primary LUN and is irrelevant to the secondary LUN. If data
fails to be written to the primary LUN or secondary LUN, the primary LUN or secondary
LUN returns a write I/O failure to the remote replication management module. Then, the
remote replication management module changes the mode from dual-write to single-
write, and the remote replication works incorrectly.
After a synchronous remote replication pair relationship is set up between the primary LUN
and the secondary LUN, a manually triggered synchronization needs to be performed so that

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
the two LUNs have consistent data. Every time a host writes data to the storage system after
the synchronization, the data is copied from the primary LUN to the secondary LUN in real
time. Figure 1-2 shows how a synchronous replication processes a write (the data block being
written is N).
Figure 1-2 Writing process in synchronous remote replication mode
Host
LOG DCL
1 5 2 6
6
RM
3
3 4
4
Primary Secondary
Cache Cache
Remote replication links
Primary Secondary
LUN LUN
Primary Secondary
LOG
Primary Primary Secondary Secondary

RM
cache LUN cache LUN
1 Data block N
2 Records the difference in the LOG
3 Data block N
3 Data block N
4 Write I/O result

4
5 Write I/O result
Determination
6
Saves the log to the DCL upon any write failure
Deletes the log if all writes are successful
RM: Remote replication management module.
LOG: Records data write logs.
DCL: Data change log.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
1. The host sends a write I/O request to the RM.

2. The RM records the write I/O request in the LOG.
3. The RM concurrently writes the write I/O request to both the primary cache and
secondary cache.
4. The primary cache and secondary cache return the write I/O result to the RM.
5. A storage array returns the write I/O result to the host after receiving the response from
the primary cache and secondary cache. If data fails to be written to the primary cache or
secondary cache, the primary cache or secondary cache returns a write I/O failure to the
RM. Then, the RM changes the mode from dual-write to single-write, and the remote
replication works incorrectly.
6. The storage array determines whether dual-write succeeds.
The LOG is deleted if data has been successfully written to both the primary cache
and secondary cache.
If data fails to be written to the primary cache or secondary cache, the LOG is
stored in the DCL.
Writing Process in Asynchronous Remote Replication

An asynchronous remote replication session periodically replicates data from the primary
storage system to the secondary storage system. The characteristics of asynchronous remote
replication are as follows:
l Asynchronous remote replication relies on the snapshot technology. A snapshot is a
point-in-time copy of source data.
l When a host writes data to a primary LUN, the primary storage system returns a
response indicating a successful write to the host, as soon as the primary LUN returns a
response indicating a successful write.
l Data synchronization is triggered by a user manually or by the system periodically to
keep data consistent between the primary LUN and the secondary LUN.
After an asynchronous remote replication relationship is set up between a primary LUN and a
secondary LUN, initial synchronization is performed to copy all of the data from the primary
LUN to the secondary LUN so that the two LUNs have consistent data.
When receiving a host write, the primary storage system sends the data to the primary LUN.
As soon as the primary LUN returns a response indicating a successful write, the primary
storage system returns a response indicating a successful write to the host. At the scheduled
synchronization time, new data on the primary LUN is copied to the secondary LUN. Figure
1-3 shows how an asynchronous replication processes a write in a synchronization period (the
data block being written is N).

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-3 Writing process in asynchronous remote replication mode
Host
1 2
DCL
3 6
RM
1 2
Primary 5 Secondary
Cache Cache
5
Primary Secondary
LUN LUN
4 4
Remote replication links
Snapshot Snapshot
7 7
Snapshot Snapshot
Primary Secondary
DCL
Primary Secondary
Pri Primary Primary Secondary Secondary Secondary
LUN
Primary LUN
Primary Secondary
mar RM
1 Primary
Cache LUN LUN Cache LUN
LUN LUN
snapshot
y snapshot snapshot
1 Data block N 1 Data block N
2 Write I/O 2 Write I/O

result result
Data block N
4 The primary LUN 4 The secondary LUN
snapshot is created snapshot is created
3 Records the difference in the DCL
5 Data is replicated from the primary cache and LUN to the secondary cache.
5 Incremental data is synchronized

to the secondary cache
6 Eliminates the
difference Data block N
in the DCL.
7 The primary LUN 7
The secondary LUN
snapshot is stopped. snapshot is stopped.
RM: Remote replication management module.
DCL: Data change log.
NOTE
Snapshots for the primary and secondary LUNs are generated and activated when synchronization starts
for the first time. The functions of the snapshots are as follows:
l The snapshot generated for the primary LUN ensures that data read from the primary LUN during
data synchronization is always consistent and allows concurrent implementation of data
synchronization and data write to the primary LUN.
l The snapshot for the secondary LUN stores backup data for the data on the secondary LUN before
synchronization so that data on the secondary LUN can still be usable even when an exception
occurs during synchronization.
The reason for stopping the snapshots: The snapshot function is used only during a data synchronization.
After the data synchronization is complete, the snapshot function is stopped to reduce the system
overhead and improve performance.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
1. The host sends a write I/O request to the RM, and the RM directly writes data to the
primary cache.
2. The primary cache returns the write I/O result to the RM, and the RM further returns the
result to the host.
3. After data in the primary cache is written to the LUN, the RM records data differences
between the primary LUN and the secondary LUN in the DCL.
4. When a replication period starts, the snapshots of the primary and secondary LUNs are
activated.
5. Data is replicated from the primary cache and LUN to the secondary cache.
Asynchronous remote replication employs multi-time-point caching technology to
replicate data from cache to the DR site. The working principle is as follows:
a. When a replication period starts, new time segments (T2 and P2) are respectively
generated in the caches of primary and secondary LUNs.
b. New data from the host is written into time segment T2 in the cache of the primary
LUN.
c. The primary LUN returns a message indicating that the write I/O operation is
complete.
d. Data in time segment T1 is replicated to time segment P2.
e. Data in the caches of the primary and secondary LUNs is written to LUNs.
6. The RM delete differences recorded in the DCL after replicating data.
7. After the remote replication, the snapshot for the primary and secondary LUNs is
stopped.
1.3.3 Service Switchover

When the primary site of a remote replication session encounters a disaster, the secondary site
can quickly take over services of the primary site to protect service continuity.
The remote replication feature not only implements remote data backup but also recovers
services as soon as possible in the case of a disaster to keep service continuity. The following
two indicators need to be considered before a service switchover:
l RPO
Recovery Point Objective (RPO) refers to the maximum acceptable time period prior to a
failure or disaster during which changes to data may be lost as a consequence of
recovery. Data changes preceding the failure or disaster by at least this time period are
preserved by recovery. The RPO indicates the tolerable amount of lost data. Synchronous
remote replication copies data from a primary LUN to a secondary LUN in real time,
ensuring that the RPO is 0. Zero is a valid value and is equivalent to a "zero data loss"
requirement. A remote disaster recovery system built based on synchronous remote
replication implements data-level disaster recovery with a high disaster recovery level
(tier 6 zero data loss). In asynchronous remote replication scenarios RPO is equal to
the time that you set in the Interval.
l RTO
Recovery Time Objective (RTO) refers to the maximum acceptable time period required
to bring one or more applications and associated data back from an outage to a correct
operational state. It takes the recovery time point as the objective and ensures that the
(standby host) can take over services as quickly as possible. The RTO indicates the
tolerable service interruption time. The RTO depends on host services and faults in
remote replication scenarios.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
The remote replication mode should be chosen based on users' requirements for the RPO and
RTO.
Service Switchover Implemented Using the Remote Replication Feature

Services can run on the secondary storage system only when the following conditions are met:
l Historical service data exists in the secondary storage system.
l The service on the production host has also been configured on the standby host.
l The secondary storage system allows a host to access a LUN in a LUN group mapped to
the host.
When the primary site fails due to a disaster, the remote replication links between the primary
LUN and the secondary LUN are down. In this case, administrator needs to set the access
permission of secondary LUNs manually to accessible, and a service switchover can be
performed. Figure 1-4 shows how a service switchover is implemented using the remote
Figure 1-4 Service switchover implemented using the remote replication feature
Primary site Secondary site
Production host Standby host

1. The primary site is working properly.
The primary LUN is accessible to hosts but

The production the secondary LUN is not.
Read only The primary site copies data to the secondary
host runs services.
Remote replication site.
Primary links Secondary
LUN LUN
Primary storage system Secondary storage system
Production host Standby host

Phases in a service switchover
2. The primary site encounters a disaster.
The remote replication links are interrupted.

The pair between the primary and
Read only secondary LUNs is broken.
Remote replication
links interrupted
Secondary
Primary
LUN
LUN
Production host Standby host 3. The secondary site takes over services.
Administrator sets the access permission of

The standby secondary LUNs manually to accessible.
Read host takes over
The secondary site takes over services from
/Write services.
Links interrupted the primary site to ensure service continuity.
Primary
Secondary
LUN
LUN

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
NOTE
After a primary/secondary switchover is implemented, the primary and secondary sites will record
changed data respectively to avoid the full synchronization next time when the secondary site turns back
to the primary one.
1.3.4 Data Recovery

After the primary site of a remote replication session fails, the secondary temporarily takes
over services of the primary site. When the primary recovers, services are switched back to
the primary site. This section describes how the storage system recovers from a site failure.
This section will help you with remote replication configuration, site recovery, and fault
analysis in disaster recovery scenarios.
When the primary site recovers from a disaster, it is required to rebuild a remote replication
between primary and secondary storage systems. And you can use the data on the secondary
site to recover the primary site. Figure 1-5 shows how the storage system recovers data at the
primary site after a disaster.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-5 Process of recovering data at the primary site after a disaster
Primary site Secondary site
Production 1. The primary site recovers from the

Standby host
host disaster.
The primary storage system recovers

from the disaster. And the links
between storage systems are
restored.
The standby After the links are restored, it is
Links restored host runs need to perform a primary/secondary
services. switchover manually on the primary
site, to make the secondary LUN on
Secondary the secondary storage system
Primary
LUN
LUN become the primary one.
Primary storage Secondary storage

system system
Phases in a data recovery process
2. The secondary site recovers data at the

Production primary site.
Standby host
host
Synchronous: Perform synchronization
once to copy data on the primary LUN
to the secondary LUN.
Recovers data Asynchronous: Perform
synchronization for multiple times
New remote replication during idle hours to copy data on the
links Primary primary LUN to the secondary LUN.
Secondary
LUN LUN
Production 3. The primary site recovers services.

Standby host
host
Synchronous: Perform a
primary/secondary switchover to
restore the pre-disaster pair.
Asynchronous: Start synchronization
again to eliminate the difference
The caused by host writes during the
production previous synchronization. Then split
host runs Remote replication Pair to set the secondary LUN to be
services. writable and perform a
Primary Secondary primary/secondary switchover to
LUN LUN restore the pre-disaster pair.
After recovered the pair, enable
protection for secondary resource in
Primary storage system Secondary storage system the primary storage system.
NOTE
In an asynchronous remote replication scenario, the storage system performs data synchronization
multiple times until the data difference between the primary and secondary LUN is comparatively small.
Then, the storage system stops services and performs the last synchronization. This prevents data loss
and minimizes the downtime.
1.3.5 Functions of a Consistency Group

In medium- and large-sized database applications, data, logs, and modification information
are stored on different LUNs that are associated with each other. If data on one of the LUNs
becomes unavailable, data on the other LUNs is also unusable. On this condition, you can add
the pair that created by the LUNs to a consistency group. This section compares a storage

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
system running a consistency group with a system without running a consistency group in
terms of data unavailability to describe the functions of a consistency group.
Users can perform synchronization, splitting, and primary/secondary switchovers for a single
remote replication session or perform these operations for multiple remote replication sessions
by creating a consistency group. The following are notes for creating a consistency group:
l Remote replication sessions can be added to a consistency group only on the primary
storage system. In addition, secondary LUNs of all member remote replication sessions
must be in the same remote storage system.
l LUNs of different member remote replication sessions in a consistency group can belong
to different working controllers.
l Remote replication sessions in one consistency group must work in the same remote
replication mode.
l When a remote replication is added to a consistency group, the configuration properties
of it (such as synchronization rate and recovery policy) must be the same with that of the
consistency group.
The following compares remote replication sessions in a consistency group with sessions
without using a consistency group in terms of synchronization result to prove that a
consistency group is effective in preventing data unavailability.
Remote Replication Without Using a Consistency Group

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

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-6 Remote replication without using a consistency group

system system
Before data
replication 1. No consistency group is created.
Remote replication
Primary session 01 Secondary
LUN01 Data, log, and change tracking
LUN01
information of a database are
respectively stored on primary
Remote replication LUN01, primary LUN02, and
Primary session 02 Secondary primary LUN03.
LUN02 LUN02 No consistency group is
created on the primary storage
Remote replication system.
LUN03 LUN03
Phases in a process of data becoming invalid
Data replication 2. A task failure causes data

inconsistency.
Remote replication
LUN01 LUN01 During synchronization,
remote replication session 02
fails due to a fault.
Remote replication
Remote replication sessions
Primary session 02 Secondary 01 and 03 succeed. As a
LUN02 LUN02 result, data in the primary
storage system becomes
Remote replication inconsistent with that in the
Primary session 03 Secondary secondary storage system.
LUN03 LUN03
Data recovery
3. Data becomes invalid.
Remote replication
LUN01 LUN01 After the remote replication
session failure, the secondary
storage system recovers data
Remote replication in the primary storage system,
Primary session 02 Secondary but data in the primary
LUN02 LUN02 storage system is still
unusable because the three
Remote replication primary LUNs store data at
Primary session 03 Secondary different points in time.
LUN03 LUN03
Remote replication using a consistency group

If associated LUNs are added to a consistency group, the consistency group effectively
prevents data loss, as shown in Figure 1-7.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-7 Remote replication using a consistency group

system system
1. Create a consistency group
Consistency group 01
Remote replication session
Primary 01 Secondary Data, log, and change tracking
LUN01 LUN01 information of a database are
respectively stored on primary LUN01,
Remote replication session primary LUN02, and primary LUN03.
Primary 02 Secondary Create consistency group 01 in the
LUN02 LUN02 primary storage system and add the
Phases in a process in which a consistency group protects data availability
three remote replication sessions to the

Remote replication session consistency group.
Primary 03 Secondary
LUN03 LUN03
Consistency group 01 2. The consistency group stops all remote

Remote replication session replication sessions.
01
Primary Secondary
LUN01 LUN01
During synchronization, remote
Remote replication session replication session 02 fails due to a fault.
02 The consistency group stops remote
Primary Secondary
LUN02 replication sessions 01 and 03
LUN02
immediately.
Remote replication session After the fault is rectified, the consistency
03 group resumes synchronization.
Primary Secondary
LUN03 LUN03
Consistency group 01 3. The consistency group protects data

Remote replication session availability
LUN01 LUN01 In the event of a disaster, the secondary
storage system recovers data on the
Remote replication session primary storage system. Data in the
Primary 02 Secondary primary storage system is available
LUN02 LUN02 immediately after the recovery.
Remote replication session

LUN03
LUN03
1.4 Restrictions
This section describes the impact of the remote replication feature on system performance,
interaction between the remote replication feature and other features, and restrictions on the
remote replication feature.
Impact on Host Performance

l Synchronous remote replication: The secondary site synchronizes data with the primary
site in real time. In this case, host performance is affected by the comparatively long data
transmission latency. Specifically, the primary site can return a response indicating that
the I/O processing is completed to the host only after the secondary site completes the
I/O processing.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
l Asynchronous remote replication: The secondary site synchronizes data with the primary
site periodically. In this case, host performance is not affected. However, in the event of
a disaster, the amount of lost data is mainly subject to the synchronization period. (A
longer synchronization period leads to more lost data. A shorter synchronization period
leads to less lost data.) I/O requests delivered by a host are processed only at the primary
site. When the user-defined synchronization period reaches, a data synchronization is
automatically initiated between the primary site and the secondary site. Therefore, after
completing the I/O processing, the primary site immediately returns a response
indicating that the I/O processing is completed to the host.
Interaction with Other Features (Where Remote Replication Is Configured

Earlier than Other Features)
Table 1-5 describes the interaction relationship between the remote replication feature and
other features, where the remote replication feature (containing primary and secondary LUNs)
are configured earlier than other features on the storage system.
Table 1-5 Interaction relationship between the remote replication feature and other features
(where the former is configured earlier than the latter)
NOTE
l HyperMetro and asynchronous remote replication are not mutually exclusive. HyperMetro and
synchronous remote replication are mutually exclusive.
l The following table indicates whether the primary or secondary LUN in a remote replication can be
configured as a LUN in the first column.
l In the following table, indicates that the primary or secondary LUN in a remote replication can be
configured as the corresponding LUN in first column, - indicates that the primary or secondary LUN in
a remote replication is unlikely to be configured as the corresponding LUN in the first column, and
indicates that the primary or secondary LUN in a remote replication cannot be configured as the
corresponding LUN in the first column.
LUN Used in Another Primary LUN in a Secondary LUN in a

Feature Remote Replication Remote Replication
Local LUN in
HyperMetro
Remote LUN in
HyperMetro
Source LUN in the

snapshot feature
Snapshot LUNa - -
Primary LUN in the clone

feature
Secondary LUN in the

clone feature
Primary LUN in a remote

replication
Secondary LUN in a
remote replication

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

Source LUN in a LUN

copy
Target LUN in a LUN

copy
Source LUN in
SmartMigration
Target LUN in
SmartMigration
Mirror LUN in
HyperMirror
Mirror copy in - -
HyperMirrorb
LUN configured with

SmartDedupe&SmartCo
mpression
eDevLUN hosted by - -
SmartVirtualizationc
LUN configured with

SmartThin
LUN configured with

SmartQoS
LUN configured with

SmartPartition
LUN configured with

SmartTier
LUN configured with

SmartCache
LUN configured with - -

SmartMulti-Tenantd

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

a: A snapshot LUN is a data copy automatically generated by the storage system after a
snapshot is created. Therefore, the scenario where the primary or secondary LUN in a
remote replication is configured as a snapshot LUN does not exist.
b: A mirror copy is a data copy automatically generated by the storage system when a
HyperMirror task is created. Therefore, the scenario where the primary or secondary LUN
in a remote replication is configured as a mirror copy in a HyperMirror task does not exist.
c: SmartVirtualization only hosts external LUNs from a third-party storage system as an
eDevLUN. Therefore, the scenario where the primary or secondary LUN in a remote
replication is hosted as an eDevLUN does not exist.
d: In the SmartMulti-Tenant feature, a vStore is configured and then LUNs are added the
vStore. Therefore, the scenario where another feature is configured earlier than
SmartMulti-Tenant for a LUN does not exist.
Interaction with Other Features (Where Remote Replication Is Configured Later

than Other Features)
Table 1-6 describes the interaction relationship between the remote replication feature and
other features, where the remote replication feature is configured later than other features on
the storage system.
Table 1-6 Interaction relationship between the remote replication feature and other features
(where the former is configured later than the latter)
NOTE
l HyperMetro and asynchronous remote replication are not mutually exclusive. HyperMetro and
synchronous remote replication are mutually exclusive.
l The following table indicates whether a LUN in the first column can be configured as the primary or
secondary LUN in a remote replication.
l In the following table, indicates that the corresponding LUN in first column can be configured as the
primary or secondary LUN in a remote replication, and indicates that the corresponding LUN in the
first column cannot be configured as the primary or secondary LUN in a remote replication.

Local LUN in HyperMetro
Remote LUN in
HyperMetro
Source LUN in the

snapshot feature
Snapshot LUN
Primary LUN in the clone

feature

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

Secondary LUN in the

clone feature
Primary LUN in a remote

replication
Secondary LUN in a
remote replication
Source LUN in a LUN

copy
Target LUN in a LUN

copy
Source LUN in
SmartMigration
Target LUN in
SmartMigration
Mirror LUN in
HyperMirror
Mirror copy in
HyperMirror
LUN configured with

SmartDedupe&SmartCom
pression
eDevLUN hosted by
SmartVirtualization
LUN configured with

SmartThin
LUN configured with

SmartQoS
LUN configured with

SmartPartition
LUN configured with

SmartTier
LUN configured with

SmartCache
LUN configured with

SmartMulti-Tenant

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
NOTICE
If you select an existing LUN to be the secondary LUN or target LUN of a value-added
feature, data on the existing LUN may be overwritten. Therefore, perform this operation with
caution.
Application Restriction
l The remote replication feature is not available if network address translation (NAT)
devices exist on the local area network (LAN) where the storage system resides.
l The remote replication feature of this series does not support direct data replication with
a storage device from another vendor.
l Because of the LUN identification mechanism used by hosts' operating systems and
volume managers, do not map the primary and secondary LUNs of a remote replication
pair both to a host. For example, in Oracle ASM, hosts distinguish between LUNs by
ASM disk headers and may wrongly identify the primary and secondary LUNs as the
same LUN, causing data corruption on the two LUNs.
l During the creation of a remote replication, a LUN mapped to a host cannot be added as
the secondary LUN.
l Table 1-7 lists the maximum distance between the primary site and secondary site
supported by the remote replication feature.
Table 1-7 Maximum distance supported by the remote replication feature

Networking Mode Synchronous remote Asynchronous Remote
replication Replication
Direct connection using 100 m to 150 m 100 m to 150 m

iSCSI host ports
Direct connection using Fiber 500 m 500 m

Channel host ports (multi-
mode optical fibers)
Connection through remote 200 km No restriction

transfer devices (switches or
routers)
l The creation of a remote replication requires links to meet the following requirements:
Synchronous remote replication: Link bandwidth x Bandwidth utilization rate >=
Peak service write bandwidth x Bandwidth utilization rate >= 64 Mbit/s
Asynchronous remote replication: Link bandwidth x Bandwidth utilization rate >=
Average service write bandwidth x Bandwidth utilization rate >= 1 Mbit/s
1.5 Application Scenarios

The remote replication feature is used for data backup and DR. The typical application
scenarios include central backup and DR, and 3DC.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Different remote replication modes apply to different application scenarios.

l Synchronous remote replication applies to backup and DR scenarios where the primary
site is very near to the secondary site, for example, in the same city (same data center or
campus).
l Asynchronous remote replication applies to backup and DR scenarios where the primary
site is far from the secondary site (for example, cross countries or regions) or the
network bandwidth is limited.
NOTE
As for the asynchronous remote replication on an iSCSI network, you are advised to use a device such
as a security gateway to encrypt links when adding the iSCSI links to ensure data transfer security
among storage systems and prevent information leakage.
In a specific application scenario, determine the replication mode based on the distance and
bandwidth between sites. Table 1-8 describes the typical application scenarios of the remote
Table 1-8 Typical application scenarios of remote replication

Analysis Items Central Backup and DR 3DC
Scenario characteristics l Backup data is managed l Three data centers (DCs)

centrally so that data are deployed at two
analysis and data mining places. Real-time backup
can be performed without and remote backup are
affecting services. available concurrently.
l When any of the service l Service data is backed up
sites encounters a disaster, to the intra-city DR
the central backup site can center in real time
quickly take over services through a high-speed
of the site and recover link.
data, achieving unified l After data in the
service data management. production center is
l A remote replication mode invalid, services are
can be selected for a quickly switched to the
service site flexibly based intra-city DR center.
on the distance between l If a large-scale disaster
the service site and the damages the production
central backup site. center and DR center in
the same city, the remote
DR center can take over
services and implement
DR.
Remote replication mode Synchronous remote l Intra-city: synchronous

replication or asynchronous or asynchronous remote
remote replication replication
l Remote: asynchronous
remote replication

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Analysis Items Central Backup and DR 3DC
Maximum distance Synchronous remote Synchronous remote

replication: within 200 km replication: within 200 km
Asynchronous remote Asynchronous remote
replication: no restriction replication: no restriction
Central Backup and DR

In a central backup and DR scenario, service data distributed in different places is backed up
to the same site for centralized management. Service data at multiple service sites is centrally
backed up to and managed at the central backup site. When a disaster occurs at any service
site, the central backup site can take over services from the service site and recover data.
Figure 1-8 shows a central backup and DR scenario.
Figure 1-8 Central backup and DR
Remote replication
session 01
Primary
LUN 01 Secondary
LUN 01
Synchronous
Service site 01
Remote replication Host
Primary session 02
Snapshot Secondary
LUN 02
02 LUN 02
Asynchronous
...
Service site 02
...
Remote replication
...
session n
Primary Snapshot Secondary
LUN n n LUN n
Asynchronous
Central backup site
Service site n
In the example shown in the previous figure, the remote replication feature can do the
following things:
l Collects data from n (a number) service sites to the central backup site, takes a snapshot
of a secondary LUN, and maps the secondary LUN to a host. The snapshot can be used
for data analysis and data mining.
l Lets the central backup site to take over services when any service site (01 to n)
encounters a disaster and switch services back to the service site when the site recovers.
l Implements real-time backup (using the synchronous remote replication mode) from
service site 01 to the central backup site, which is 500 m away from service site 01.
Performs replication tasks (using the asynchronous remote replication mode) from
service site 02 to the central backup site, which is 500 km away from service site 02.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
3DC
3DC indicates that three DCs are deployed at two places in the DR solution. Three DCs
consist of the production center, intra-city DR center, and remote DR center. The three DCs
can be cascaded and interconnected in parallel mode based on different networks formed by
storage systems in the three DCs.
l Cascaded 3DC
The production center (A), intra-city DR center (B), and remote DR center (C) are
cascaded in A-B-C mode.
l Parallel-connected 3DC
The intra-city DR center (B) and remote DR center (C) concurrently serve as the DR
centers for the production center (A). The three DCs are interconnected in A-B and A-C
mode.
Figure 1-9 shows the cascaded 3DC in synchronous + asynchronous mode.
Figure 1-9 Cascaded 3DC in synchronous + asynchronous mode
Site A
LUN
Storage System
Production
center
Synchronous
Remote
Replication
Site B Site C
Asynchronous
Remote
LUN Replication LUN
Storage System Storage System
Intra-city DR Remote DR
center center
Optical fiber cable
Network cable
The cascaded 3DC in synchronous + asynchronous mode meets the following service
requirements:
l Real-time backup and remote backup of data achieve robust reliability of critical service
data and ensure that critical service data has two copies.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
l The cascaded 3DC has minor impact on the performance of the storage system in the
production center and does not affect host services.
l When the production center (A) encounters a disaster, the intra-city DR center (B) takes
over services immediately and recovers data. If the secondary disaster damages the intra-
city DR center (B), data in the remote DR center (C) is available.
Figure 1-10 shows the cascaded 3DC in asynchronous + asynchronous mode.
Figure 1-10 Cascaded 3DC in asynchronous + asynchronous mode
Site A
LUN
Storage System
Production
center
Asynchronous
Remote
Replication
Site B Site C
Asynchronous
Remote
LUN Replication LUN
center center
Optical fiber cable
Network cable
The cascaded 3DC in synchronous + asynchronous mode meets the following service
requirements:
l The cascaded 3DC has minor impact on the performance of the storage system in the
production center and does not affect host services.
over services and recovers data. If the secondary disaster damages the intra-city DR
center (B), data in the remote DR center (C) is available.
Figure 1-11 shows the parallel-connected 3DC in synchronous + asynchronous mode.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-11 Parallel-connected 3DC in synchronous + asynchronous mode
Site A
LUN
Storage System
Production
center Asynchronous
Remote
Synchronous
Replication
Remote
Replication
Site B Site C
LUN LUN
center center
Optical fiber cable
Network cable
The parallel-connected 3DC in synchronous + asynchronous mode meets the following

service requirements:
l Data backup of the remote DR center (C) does not depend on the intra-city DR center
(B). If the intra-city DR center (B) or remote DR center (C) fails, the production center
(A) still has a backup site.
over services immediately and recovers data. If the secondary disaster damages the intra-
city DR center (B), data in the remote DR center (C) is available.
Figure 1-12 shows the parallel-connected 3DC in asynchronous + asynchronous mode.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-12 Parallel-connected 3DC in asynchronous + asynchronous mode
Site A
LUN
Storage System
A
sy Re lica
Production
nc m ti
hr ote on
center
R
ep
on
ou
Asynchronous
s
Remote
Replication
Site B Site C
LUN LUN
center center
Optical fiber cable
Network cable
The parallel-connected 3DC in asynchronous + asynchronous mode meets the following

service requirements:
l Data backup of the remote DR center (C) does not depend on the intra-city DR center
(B). If the intra-city DR center (B) or remote DR center (C) fails, the production center
(A) still has a backup site.
over services and recovers data. If the secondary disaster damages the intra-city DR
center (B), data in the remote DR center (C) is available.
NOTE
The difference between 3DC in synchronous + asynchronous and asynchronous + asynchronous modes
lies in the different data synchronization modes of the production center (A) and intra-city DR center
(B). For the data synchronization mode used by the 3DC in synchronous + asynchronous mode, when
data is concurrently written to the production center (A) and intra-city DR center (B), a message is
displayed indicating that the synchronization succeeds. For the data synchronization mode used by the
3DC in asynchronous + asynchronous mode, when data is concurrently written to the production center
(A), a message is displayed indicating that the synchronization succeeds.
For details, see OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003
3DC Configuration.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
works with BCManager to implement DR

BCManager is a piece of DR management software specifically designed for Huawei typical
DR solutions. With application data consistency, snapshot, and remote replication, it provides
a GUI-based and process-based platform for simple and rapid operation and monitoring.
Figure 1-13 illustrates how to use BCManager to deploy remote replication. Deploy the
BCManager host in the DR center and installBCManager Server on the host. Install
BCManager Agent on service hosts and DR hosts in the production center.
Figure 1-13 Using BCManager to deploy remote replication
Production center DR center
BCManager
Agent
BCManager BCManager
Server Agent
Production
host BCManager DR host
host
Remote
replication
Storage system Storage system
Figure 1-14 and Figure 1-15 illustrate how to use BCManager to deploy 3DC. Deploy the
BCManager host in DR centers 1 and 2 and install BCManager Server on the hosts. Install
BCManager Agent on service hosts and DR hosts in the production center.
Figure 1-14 Using BCManager to deploy cascaded 3DC

Production center DR center 1 DR center 2
BCManager
Agent BCManager BCManager
BCManager BCManager
Server Agent Server Agent
Production
host
BCManager DR host BCManager DR host
host host
Synchronous/
Asynchronous Asynchronous
remote remote
replication replication
Storage system Storage system Storage system

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 1-15 Using BCManager to deploy parallel-connected 3DC
DR center 1
BCManager BCManager
Server Agent
Production center
BCManager DR host
host
BCManager
Agent
us/ Storage system

Production
hr ono us
c o
host Syn nchron
s y o te
A rem
tion
lica
rep
DR center 2
A
rem sync BCManager BCManager
Storage system ote hro
rep nou Server Agent
lica s
tio
n
BCManager DR host
host
Storage system
NOTE
For details about how to install, deploy, and configure BCManager, see the OceanStor BCManager
V100R005C00 Product Documentation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block 2 Configuration Example
2 Configuration Example
About This Chapter
The remote replication feature is usually used for remote disaster recovery. The feature can be
configured flexibly based on customer requirements. This chapter provides an example to
explain how to configure the remote replication feature in a typical remote disaster recovery
scenario. The content is divided into requirement analysis, configuration planning,
configuration procedure, and configuration verification.
2.1 Central Backup and Disaster Recovery
This example explains how to configure the remote replication feature to implement central
backup and disaster recovery.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
2.1 Central Backup and Disaster Recovery

This example explains how to configure the remote replication feature to implement central
backup and disaster recovery.
2.1.1 Requirement Analysis

This section analyzes the requirements of a carrier that implements central backup and
disaster recovery using the remote replication feature and comes to a conclusion.
Requirement Source
The carrier has a service site at place A (the service site is called site A later in this
document). At site A, there is an application server of which the most important application is
a user data management application. Data generated by the application server is stored in an
OceanStor storage system. The data and bandwidth status of site A is as follows:
l The daily data change amount is between 100 MB to 200 MB.
l The total data amount does not exceed 500 GB.
l The current network bandwidth between the application server and the storage system is
2 Mbit/s.
Since the network is complete and the application is running properly, the carrier prefers to
keep the existing network. Figure 2-1 shows a diagram of the existing network.
Figure 2-1 Diagram of the existing network

Site A Application server 1
Switch
Host port P0 on Host port P0 on

controller A controller B
Management
network port
Maintenance Storage system

terminal
Table 2-1 and Table 2-2 describe the LUN mapping and IP address allocation on existing
devices at site A.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 2-1 LUN mapping at site A

LUN Name LUN Size Host Mapping
LUN001 500 GB Mapped to application server 1
Table 2-2 IP address allocation at site A

Port IP Address Subnet Mask Gateway
Management network 192.168.15.60 255.255.0.0 192.168.0.1

port
Host port P0 on 172.16.19.30 255.255.0.0 172.16.0.1

controller A
Host port P0 on 172.16.19.31 255.255.0.0 172.16.0.1

controller B
Place A suffers natural disasters from time to time. The carrier wants to protect service data at
site A against natural disasters and to quickly recover the service data when a disaster
happens. The specific requirements are as follows:
l Data backup and disaster recovery
Data at site A is automatically backed up to a backup site without interrupting services to
minimize data loss upon a disaster. The backup data can be used to quickly recover
services at site A after the disaster.
l Quick service recovery
Once a disaster happens, site B takes over services with an RTO no longer than 15
minutes.
l Central data management
After a new service site (site C) or even more service sites are set up, data from all
service sites are backed up to the backup site for central management and reduced
deployment and maintenance costs.
l Data analysis and mining
Service data can be exported for analysis and mining to support policy-making.
Requirement Analysis and Conclusions

The previous requirements indicate that the carrier needs a disaster recovery solution. Table
2-3 lists the considerations for implementing a remote disaster recovery solution.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 2-3 Considerations for implementing a remote disaster recovery solution
Consideration Description
Data transfer amount Inter-city data transfer is subject to the bandwidth. The amount
of lost data decreases as the amount of data transferred within a
specified period of time increases.
Host performance Data backup affects services on the host. Services on the host
can run properly if the impact of backup on the services is
slight.
Data availability Availability of data at the disaster recovery site is significant

for data recovery. Therefore, data at the disaster recovery site
must be available any time.
Service continuity The disaster recovery site must be able to quickly take over
services at the service site through a service switchover to
protect service continuity.
Others Other factors need to be taken into consideration include cost

as well as central data management and analysis.
The detailed analysis is as follows:

l Data transfer amount
At site A, the daily data change amount is between 100 MB to 200 MB, while the
available bandwidth is only 2 Mbit/s, which is not adequate for the data change amount.
Therefore, the data replication period must be shortened to reduce the amount transferred
each time.
l Host performance
The carrier requires minimized impact of backup on host performance to ensure host
services run correctly. There probably will be multiple service sites that are in different
places and comparatively far from the backup site. Therefore, asynchronous remote
replication is suitable for this case. Table 2-4 describes advantages of asynchronous
remote replication.
Table 2-4 Advantages of an asynchronous remote replication solution
Advantage Description
Incremental data Incremental data replication is implemented between the

replication primary and secondary storage systems. Specifically, After
the initial synchronization (full replication), only data
changes is replicated from the service site to the backup site
during each synchronization process. Since the amount of
data replicated each time is small, synchronization
completes fast.
No host performance Data replication is between storage systems, occupying no

deterioration host resources, so it does not affect current services. The
quality of service (QoS) does not decrease.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Advantage Description
Quick service takeover When a disaster happens, breaking remote replication pairs
between the service site and the backup site, the backup site
quickly takes over services of the service site.
l Data availability
The carrier needs to analyze the backup data and requires that data at site A be quickly
recovered after a disaster. Therefore, data at the backup site must be available anytime.
l Service continuity
The backup site must be able to quickly take over services when a disaster causes a
failure of site A to minimize the loss, through setting the Interval is 10 minute to satisfy
the RPO requirement.
l Others
Besides backup and disaster recovery, the carrier hopes backup data be managed
centrally and latest data at service sites be available anytime so that services can be
analyzed conveniently. Therefore, data at service sites needs to be centrally backed up to
one site. In this way, copies of all data can be quickly obtained when necessary.
Based on the former analysis, details of the solution are as follows:
l To choose the central backup and disaster solution and build a central backup site at
place B (equipment at the backup site includes an OceanStor storage system, an
application server, a maintenance terminal, and an iSCSI switch)
l To use asynchronous remote replication for backup and disaster recovery
l To set up an iSCSI connection between site A and B
2.1.2 Configuration Planning

This section describes how to plan the remote replication feature for central backup and
disaster recovery. This section is organized into two parts: network planning and service
planning.
Network Planning
Figure 2-2 shows a diagram of the planned network. As shown in the diagram, central backup
and disaster recovery is implemented without changing the carrier's existing network.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 2-2 Diagram of central backup and disaster recovery
Site A Application Standby Site B

server 1 server
Switch Switch
Controller A Controller B Controller A Controller B

host port P0 host port P0 host port P0 host port P0
Management Management
network port network port
Maintenance Primary Secondary Maintenance

terminal storage system storage system terminal
Site C
To achieve data backup to the central backup site, an iSCSI connection between site A and
site B must be set up first, and then a logical connection needs to be established by adding a
routes and a target. Before setting up the connections, a detailed networking plan must be
drawn.
Table 2-5 describes the IP address plan for site B.
Table 2-5 IP address plan for site B

Port IP Address Subnet Mask Gateway
Management network 192.168.19.10 255.255.0.0 192.168.0.1

port
Host port P0 on 172.17.20.31 255.255.0.0 172.17.0.1

controller A
Host port P0 on 172.17.20.32 255.255.0.0 172.17.0.1

controller B
Service Planning
According to the requirement analysis conclusion, a central backup and disaster recovery
solution can meet the carrier's requirements. Figure 2-3 shows the configuration roadmap of
the solution.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Figure 2-3 Configuration roadmap
Start
Make sure that the license files of

Enable the remote storage systems at sites A and B
Check the license files. grant the permission for
asynchronous remote replication.
Create a disk domain.
Create a secondary LUN In the storage system at site B, create

Create a storage pool.
in the storage system at a secondary LUN of the same size as
site B. the primary LUN at site A.
Create a secondary LUN.
Configure host port IP

addresses. If you want to connect the two storage
systems at the two sites through iSCSI
Set up a logical host ports and the host ports of the two
connection between sites storage systems are in different network
Add routes.
A and B. segments, add a route for each storage
system.
Add a remote device.
Create an asynchronous After a logical connection is set up

remote replication Create an asynchronous between the two storage systems, create
session in the primary remote replication session. an asynchronous remote replication
storage system at site A. session in the storage system at site A.
End
Table 2-6 lists the configuration operations and planning items involved in the configuration
example.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 2-6 Configuration operations and planning items

Configuration Major Planning Parameter Planned Value
Roadmap Operation Item
and Purpose
Enable the Check the None None None

remote license file.
replication Check the
feature license file to
ensure that it
grants the
permission to
use the
remote
replication
feature.
Create a Create a disk Disk domain's l Name l DiskDomain_

secondary LUN domain. name and disk l Disk Type BK
in the storage Before type l Performance
system at site B. creating a Tier (SAS)
storage pool, -
a disk domain
needs to be
created.
Because all
the disks used
to create a
storage pool
are in the disk
domain.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

and Purpose
Create a Storage pool l Name l StoragePool_

storage pool. parameters and l Disk Domain BK
This step is available disk l DiskDomain_
domains for the l RAID policy
fundamental BK
for storage system l Capacity
at site B l RAID 6;4D
subsequent +2P
storage space
configuration. l 1TB
A storage
pool is a
container, in
which
multiple
LUNs can be
created.
NOTE
When
configuring
asynchronous
remote
replication,
reserve
certain space
in the storage
pool of the
secondary
storage array
to ensure that
sufficient
space is
provided for
COW for
host I/Os or
data
synchronizati
on I/Os of the
secondary
storage array
during remote
replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

and Purpose
Create a Information l Name l LUN_BK

secondary about the l Capacity l 500GB
LUN. secondary LUN
in the storage l Quantity l 1
Storage pools
cannot be system at site B l Owning l StoragePool_
identified by Storage Pool BK
hosts. The
host can use
the storage
space only
when the
storage space
of the storage
pool is
divided into
LUNs.
Set up a logical Configure IP addresses of l IPv4 l Site A

connection host port IP host port at site Address 172.16.19.
between sites A addresses. A and that at l Subnet Mask 30
and B. This step is site B
255.255.0.
fundamental 0
for setting up
a logical l Site B
connection 172.17.20.
between the 31
two storage 255.255.0.
systems. 0

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

and Purpose
Add a route. Information on l Type l Site A

Perform this the route list of l Destination Network
step when the site A and that address segment
host port on of site B route
l Destination
the primary mask 172.17.0.0
storage
system and l Gateway 255.255.0.
that on the 0
secondary 172.16.0.1
storage l Site B
system use IP
addresses in Network
different segment
network route
segments. If 172.16.0.0
the host ports 255.255.0.
use IP 0
addresses in
172.17.0.1
the same
network
segment, skip
this step.
Add a remote Remote device l Link type l iSCSI

device. information of l Controller l CTE0.A
Add a remote the storage
system at site A l Port l CTE0.R5.IO
device for M0.P0
data or site B l IP address
transmission. l Username l 172.17.20.31
NOTE l Password l The right user
You only namea
need to
perform this
l The right
step on either passworda
storage
system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

and Purpose
Create an Create an Basic l Select l Asynchronou

asynchronous asynchronous information Replication s
remote remote and the primary Model l LUN001
replication replication LUN of the l Select
session in the session. remote l LUN_BK
Primary
primary storage The created replication LUN l Medium
system at site A. asynchronous session in the l Automatic
primary storage l Secondary
remote LUN l Timed wait
replication system at site A
l Rate when
session is synchronizati
used to l Recovery on begins
implement policy
remote data l 10 (minutes)
l Synchronizat
replication. ion type
l Interval
a:The user used for communication authentication between remote devices.

l If remote devices are OceanStor 18000 series V1R1C20, T series V2R2C20, or
OceanStor V3 series V3R1C10 or later, you need to use the machine-machine user. The
default username and password of the machine-machine user are mm_user and
mm_user@storage respectively.
NOTE
You are advised to change your login password periodically in the future by executing the change
mm_user password command. This reduces the password leakage risks. For details about how to
use the command, see OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System
V300R003 Command Reference.
l If remote devices are OceanStor 18000 series V1R1C10, T series V2R2C10, or
OceanStor V3 series V3R1C00 or earlier, you need to use the password of the super
administrator or administrator account on the older version remote device. The
username and password of the super administrator or administrator account are
consistent with the password on the remote device.
NOTE
l Keep the default values of the parameters that are not mentioned in this table.
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.
2.1.3 Configuration Operations

After completing the network and service plans, configure the remote replication feature on
the DeviceManager according to the plans.
Prerequisites
l The connection between the storage system and application server at each site is normal.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
l The iSCSI connection between the primary storage system at site A and the secondary
storage system at site B is normal.
Procedure
Step 1 Check the license file.
Remote replication is a value-added feature. Before configuring this feature, you must make
sure that the license file of the storage system grants the permission for the remote replication
feature.
On the navigation bar of the DeviceManager of each storage system, click Settings.
Click License Magement. On the Active License tab page, check information about the
license file for remote replication. If the license file does not grant the permission for remote
replication, search for License in Help. Then follow the displayed instructions to import and
activate the license file.
Step 2 Create a secondary LUN in the secondary storage system at site B.
1. Create a disk domain in the secondary storage system at site B.
On the navigation bar of the DeviceManager, click Provisioning. And on the

Storage Configuration and Optimization area, click Disk Domain to create
DiskDomain_BK.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
2. Create a storage pool in the secondary storage system at site B.

This step is fundamental for subsequent storage space configuration. A storage pool is a
container, in which multiple LUNs can be created.

Storage Configuration and Optimization area, click Storage Pool to create
StoragePool_BK.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
3. Create the secondary LUN in the storage pool.

Storage pool cannot be identified by hosts. The host can use the storage space only when
the storage space of the storage pool is divided into LUNs.

Block Storage Service area, click LUN to create a secondary LUN. The secondary LUN
must have the same capacity as the primary LUN (500 GB). Otherwise the system
cannot detect the created secondary LUN when you adding a secondary LUN.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Step 3 Set up a logical connection between sites A and B.

1. Configure host port IP addresses.
This step is fundamental for setting up a logical connection between the two storage
systems. The following uses port CTE0.R5.IOM0.P0 on the primary storage system at
site A as an example to describe how to configure a port IP address. The procedure for
any other host port on either site is the same.
In the navigation tree, click Data Protection. Click Port, and click the host port
whose IP address you want to change. In the dialog box that is displayed, click
Properties. On the Properties of the Port dialog box, configure the IP address of the port.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
2. Add routes for iSCSI host ports of both the primary and secondary storage systems.
Perform this step when the host port on the primary storage system and that on the
secondary storage system use IP addresses in different network segments. If the host
ports use IP addresses in the same network segment, skip this step. The following uses
the primary storage system at site A as an example to describe how to add a route for a
host port. The procedure at site B is the same.
After modifying host port IP address, select the host port need to add routes under the
device view. Then click Route Management, and choose Add in the displayed diagnose
box to add route information.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
3. Add a remote device in either the primary storage system at site A or the secondary
storage system at site B.
Add a remote device at one side to establish an usable link between two storage systems.
The following uses the primary storage system at site A as an example to describe how
to add a remote device. The procedure for the secondary storage system at site B is the
same.
On the navigation bar of the DeviceManager, click Data Protection, and click
Remote Device. Choose Add Remote Device to add a remote device following the Add
Remote Device Wizard dialog box.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
NOTE
If remote devices are OceanStor 18000 series V1R1C20, T series V2R2C20, or OceanStor
V3 series V3R1C10 or later, you need to use the machine-machine user. The default
username and password of the machine-machine user are mm_user and mm_user@storage
respectively.
NOTE
You are advised to change your login password periodically in the future by executing
the change mm_user password command. This reduces the password leakage risks.
For details about how to use the command, see OceanStor 5300 V3&5500 V3&5600
V3&5800 V3&6800 V3 Storage System V300R003 Command Reference.
If remote devices are OceanStor 18000 series V1R1C10, T series V2R2C10, or OceanStor
V3 series V3R1C00 or earlier, you need to use the password of the super administrator or
administrator account on the older version remote device. The username and password of the
super administrator or administrator account are consistent with the password on the remote
device.
4. Add an iSCSI link.
Only one link is selected between the storage systems during remote device adding. To
ensure link redundancy, you must manually add links after the remote device is added.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Select the added remote device and click Add Link. Set Link Type to iSCSI and then
add desired links.
Step 4 Create an asynchronous remote replication.

The created asynchronous remote replication session is used to implement remote data
replication.
On the navigation bar of the DeviceManager, click Data Protection, and click Remote
Replication. Choose Create to create RP_001 following the Create Remote Replication
Wizard dialog box.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
The following shows the properties of the asynchronous remote replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
----End
2.1.4 Configuration Verification

After configuring the remote replication feature, view the data status of the secondary LUN of
the remote replication session to check whether data replication from the primary LUN to the
secondary LUN succeeded.
Prerequisites
l The connection between the storage system and application server at site A and that at
site B are normal. The primary and secondary LUNs have been mapped to hosts.
l Initial synchronization of the asynchronous remote replication session is complete.
Procedure
Step 1 Map the primary and secondary LUNs to the hosts.
1. Log in to DeviceManager, and choose Provisioning > LUN > LUN Group. Click
Create to create LUN groups. Then add primary and secondary LUNs to corresponding
LUN group.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
2. Choose Provisioning > Mapping View, and choose the mapping view that the host
group which holds the application servers belongs to.Then add the newly created LUN
group to this mapping view.
Step 2 Check whether data replication succeeded.
1. Log in to application server 1 at site A and write data block X to the primary LUN.
2. Wait 10 to 20 minutes. Then log in to the standby server at the secondary site to check
whether data block X is on the secondary LUN.
If yes, data replication succeeded.
If no, log in to the DeviceManager at site A, click Data Protection on the

navigation bar, and click Remote Replication. Click the remote replication, and
choose More > Synchronize to synchronize data manually.
Step 3 Check whether site B can take over services.
1. Log in to the DeviceManager at site B, click Data Protection on the navigation bar,
and click Remote Replication. Click the remote replication, and choose More > Switch
Over Primary/Secondary to switch the secondary LUN to the primary LUN.
2. Log in to the standby server at site B, copy data block X to another disk and write data
block Y to the new primary LUN (previous secondary LUN) to check whether the LUN
is accessible.
If yes, the secondary site can take over services.
If no, the secondary site cannot take over services.
Step 4 Check whether data can be recovered.
1. Log in to the DeviceManager at site B, click Data Protection on the navigation bar,
and click Remote Replication. Click the remote replication, and choose More >
Synchronize to synchronize data manually.
2. After the synchronization is complete, log in to application server 1 at site A to check
whether data block Y is on the secondary LUN (after the primary/secondary switchover).
If yes, data can be recovered.
If no, data cannot be recovered.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block 3 Disaster Recovery
3 Disaster Recovery
If the production center malfunctions, use the DR center to take over services from the
production center. After the production center is recovered, switch the services back to the
production center.
If a disaster occurs in the production center, perform the following operations for the DR
center to take over services:
1. Disable secondary resource protection on the DR storage system.
2. Map the secondary LUN to the standby host.
3. Run services on the secondary host in the DR center.
After the production center is recovered, perform the following operations to switch the
services back to the production center:
1. Perform a primary/secondary switchover for the remote replication on the production
storage system and start data synchronization on the DR storage system.
2. After data synchronization is complete, stop host services in the DR center and delete the
mapping between the secondary host and the storage system.
storage system.
4. After the switchover, set the secondary LUN on the storage system in the DR center
read-only on the production storage system.
5. Run services on the production host.
Perform the following operations to reconstruct the production center and switch back
services:
storage system and start data synchronization on the DR storage system.
2. After data synchronization is complete, stop host services in the DR center and delete the
mapping between the secondary host and the storage system.
3. Manually start incremental synchronization to copy data from the DR storage system to
the production storage system and ensure data consistency between the storage systems.
4. After data replication is complete, perform a primary/secondary switchover on the
production storage system.
5. After the switchover, set the secondary LUN on the storage system in the DR center
read-only on the production storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block 3 Disaster Recovery
6. Run services on the production host.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block 4 Configuration and Management
4 Configuration and Management
About This Chapter
This chapter introduces how to configure and manage a remote replication.

To better grasp interface-related operations, you are advised to use DeviceManager Demo for
practices when reading this document. DeviceManager Demo is a simulated program of
storage system management software and can be used to simulate various configuration and
management operations. To download DeviceManager Demo, log in to http://e.huawei.com/
storagehelp, search for Demo, and download the latest Demo software package and user
guide.
4.1 Viewing System Information
Users can learn about the overall conditions of a storage system from the system information
view.
4.2 Setting Device Information
To identify devices, before configuring remote replication, set device information, including
the device name and device location.
4.3 Configuring Remote Replication
Synchronous remote replication ensures data consistency between the primary resource and
secondary resourceof each remote replication pair. Asynchronous remote replication quickly
responds to hosts' service requests and enables long-distance disaster recovery. Before
configuring remote replication, you must understand the configuration process and check for
the related license file. Then, configure link connectivity and parameters related to remote
replication.
4.4 Managing Remote Replications
This function allows you to set up a replication relationship between local and remote storage
devices to copy data from the primary resource to the secondary resource. When data on one
storage device is lost due to a disaster, data on the other storage device is available. This
ensures data integrity and availability.
4.5 Managing Consistency Groups
This function allows you to create a consistency group, add remote replications to it, and
centrally manage the remote replications in the consistency group. For example, you can
synchronize or split the remote replications in a consistency group at the same time.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.1 Viewing System Information

Users can learn about the overall conditions of a storage system from the system information
view.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Click Home.
Step 3 In the Basic Information area, check the system's basic information. Table 4-1 describes
related parameters.
Table 4-1 Basic information

Parameter Description Value
Device status Status of the storage device. [Example]

Normal
Device model Model of the storage device. [Example]

-
Total Capacity Total capacity of the storage [Example]

device(The capacity is calculated 72.000 TB
based on the sector size of 512
bytes. If the sector size employed
by a disk is not 512 bytes, the value
may be different from the actual
capacity).
Device location Geographical location of the storage [Example]

device. Chengdu
Version Version of the storage device. [Example]

-
SN Serial No. of the storage device. [Example]

210235G6GSZ0B500XXXX
WWN World Wide Name of the storage [Example]

device. 210030d17eb4XXXX
Step 4 In the Alarms area, check the system's alarm information. Table 4-2 describes related
parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 4-2 Alarm information
Level Severity of the impact caused by an [Example]

alarm on a system. Critical
Description Description of an alarm. [Example]

-
Occurred on Time when an alarm occurred. [Example]

2015-08-15 11:02:43 UTC
+08:00
Step 5 In the Disk Information area, view the used disk quantity and total disk quantity.
Step 6 In the System Capacity Trend area, view the system capacity trend of the storage system.
Table 4-3 describes related parameters.
Table 4-3 System capacity trend information
Total Capacity All hard disk capacity of the storage [Example]

system. It contains the total used 100.000 TB
capacity, available capacity and
system loss capacity.
Used Capacity Total used capacity of all storage [Example]

pools in the storage system. 10.000 TB
Available The remaining capacity which is [Example]

Capacity available in the storage system. It 80.000 TB
contains the total capacity of the
free hard disks which do not join
the disk domains, available capacity
of the disk domains and storage
pools.
Mapped LUN Total capacity of all LUNs mapped [Example]

Capacity to hosts in the storage system. 100.000 GB
Unmapped Total capacity of all LUNs not [Example]

LUN Capacity mapped to hosts in the storage 100.000 GB
system.
Total Thin LUN Total capacity of all thin LUNs in [Example]

Capacity the storage system. 100.000 GB
Assigned Thin Total assigned capacity of all thin [Example]

LUN Capacity LUNs in the storage system. 100.000 GB

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Step 7 In the Performance area, view the bandwidth and total IOPS of the storage system.
Table 4-4 describes related parameters.
Table 4-4 Performance information

Block The average amount of I/O data per [Example]

Bandwidth second in the storage system. 10.000 MB/s
File Bandwidth The average amount of I/O data per [Example]

second in the file system. 10.000 MB/s
Total IOPS The number of I/O requests per [Example]

second in the storage system. 10.000 IO/s
----End
4.2 Setting Device Information

To identify devices, before configuring remote replication, set device information, including
the device name and device location.
Procedure
Step 2 Choose Settings > Basic Information > Device Information.

Step 3 Set Device Name and Device Location.
l Device name must contain 1 to 127 characters and only letters, digits, periods (.),
underscores (_), and hyphens (-). It cannot be blank.
l Device location must contain 1 to 511 characters and cannot be blank.
Step 4 Confirm the configuration of basic information about storage devices.
1. Click Save.
The Execution Result dialog box is displayed, indicating that the operation succeeded.
2. Click Close.
----End
4.3 Configuring Remote Replication

Synchronous remote replication ensures data consistency between the primary resource and
secondary resourceof each remote replication pair. Asynchronous remote replication quickly
responds to hosts' service requests and enables long-distance disaster recovery. Before
configuring remote replication, you must understand the configuration process and check for
the related license file. Then, configure link connectivity and parameters related to remote
replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.3.1 Configuration Process

This section describes how to configure remote replication. You can set up a pair relationship
between the primary resource and secondary resource to implement data synchronization.
Figure 4-1 shows the process of configuring remote replication.
Figure 4-1 Process for configuring remote replication
4.3.2 Preparing for the Configuration

To successfully configure the remote replication feature, you must make preparations in
advance, for example, obtaining the remote replication license and selecting host ports for
data transmission.
Activating the License

Before configuring file system remote replication, import and activate its license file to enable
the remote replication function to take effect.
l If you do not have its license, contact technical support to purchase the license.
l If you have purchased its license, follow instructions in Managing License File of the
Online Help to import the license file to the primary storage system and secondary
storage system respectively and activate them.
Selecting Host Ports

Remote replication supports data transmission based onFChost ports or iSCSI host ports.
l Fibre Channel port
Fibre Channel ports feature high transmission rate and low transmission latency.
However, Fibre Channel ports use multi-mode optical fibers as transmission media.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Multi-mode optical fibers support only a short transmission distance. Therefore, remote
replication that uses Fibre Channel ports is suitable for short-distance backup and DR.
l iSCSI host port
Typically, iSCSI host ports are inferior to Fibre Channel ports in terms of transmission
rate and latency. However, iSCSI host ports carry data by using the IP protocol.
Therefore, data can be backed up to the secondary storage system through the Internet or
dedicated cables, achieving remote backup and DR across cities, provinces, and even
countries.
Understanding the advantages and disadvantages of data transmission based on Fibre Channel
ports and those of data transmission based on iSCSI host ports helps you select host ports that
best meet service needs. After you select a host port type, the corresponding link type is also
selected by default. In an actual networking scenario, you must also consider factors such as
the bandwidth, latency, network quality, and security to ensure link efficiency and stability.
4.3.3 Checking the License File

Each value-added feature requires a license file for activation. Before configuring a value-
added feature, ensure that its license file is valid for the feature.
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 file.
----End
Follow-up Procedure
If no license is available, buy and import a license file.
4.3.4 Managing a Route

This topic guides you through the process of configuring routes to enable data transmission
across network segments.
Context
The ethernet port has been assigned an IP address.
NOTE
In redundant links, you must configure IP addresses and route for multiple Ethernet ports.
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Step 2 Choose Provisioning > Port > Ethernet Ports.

Step 3 Select the Ethernet port for which you want to add a route and click Route Management.
The Route Management dialog box is displayed.
Step 4 Configure the route information for the Ethernet port.
1. In IP Address, select the IP address of the Ethernet port.
2. Click Add.
The Add Route dialog box is displayed.
NOTICE
The default IP addresses of the internal heartbeat on a dual-controller storage system are
127.127.127.10 and 127.127.127.11, and the default IP addresses of the internal
heartbeat on a four-controller storage system are 127.127.127.10, 127.127.127.11,
127.127.127.12, and 127.127.127.13. Therefore, the IP address of the router cannot fall
within the 127.127.127.XXX segment. Besides, the IP address of the gateway cannot be
127.127.127.10, 127.127.127.11, 127.127.127.12, or 127.127.127.13. Otherwise, routing
will fail. (Internal heartbeat links are established between controllers for these controllers
to detect each other's working status. You do not need to separately connect cables. In
addition, internal heartbeat IP addresses have been assigned before delivery, and you
cannot change these IP addresses).
3. In Type, select the type of the route to be added.

There are three route options:
Default route
Data is forwarded through this route by default if no preferred route is available.
The destination address field and the target mask field (IPv4) or prefix (IPv6) of the
default route are automatically set to 0. To use this option, you only need to add a
gateway.
Host route
The host route is the route connecting to an individual host. The destination mask
(IPv4: 255.255.255.255) or prefix (IPv6: 128) of the host route are automatically
set. To use this option, you only need to add the target address and a gateway.
Network segment route
The network segment route is the route connecting to a network segment. You need
to add the target address, target mask (IPv4) or prefix (IPv6), and gateway. Such as
the target address is 172.17.0.0, target mask is 255.255.0.0, and gateway is
172.16.0.1.
4. Set Destination Address.
If IP Address is an IPv4 address, set Destination Address to the IPv4 address or
network segment of the application server's service network port or that of the other
storage system's Ethernet port.
If IP Address is an IPv6 address, set Destination Address to the IPv6 address or
network segment of the application server's service network port or that of the other
storage system's Ethernet port.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
5. Set Destination Mask (IPv4) or Prefix (IPv6).

If a Destination Mask is set for an IPv4 address, this parameter specifies the subnet
mask of the IP address for the service network port on the application server or
storage device.
If a Prefix is set for an IPv6 address, this parameter specifies the prefix of the IPv6
address for the application server's service network port or that of the other storage
system's Ethernet port.
6. In Gateway, enter the gateway of the local storage system's Ethernet port IP address.
Step 5 Click OK. The route information is added to the route list.
The security alert dialog box is displayed.
Step 6 Confirm the information of the dialog box and select I have read and understood the
consequences associated with performing this operation..
Step 7 Click OK.

The Success dialog box is displayed indicating that the operation succeeded.
NOTE
To remove a route, select it and click Remove.
Step 8 Click Close.
----End
4.3.5 Adding a Remote Device

This operation enables you to establish a logical connection between a local storage device
and a remote storage device for data transfer between the two devices.
Prerequisites
A local storage device is normally connected to the remote storage device.
Context
The link between a local storage device and a remote storage device can be a Fibre Channel
link or an iSCSI link.
The following describes two types of the remote device.

l Replication: the remote device used for creating remote replication, LUN copy,
HyperMetro, and HyperVault
l Heterogeneity: the remote device used for managing the storage resources provided by
heterogeneous storage systems
NOTE
l In scenarios where a firewall is deployed, ports 36061 and 3260 must be enabled for adding a
remote device.
l On a Fibre Channel network, clear zone configurations of ports connecting to the storage system
from the switch before adding the remote device. You are advised to allocate two ports in one zone
to prevent excessive remote links because too many ports exist in one zone.
l A maximum of eight links are available between a controller and the remote device, and a
maximum of two links can be used for adding a remote device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Procedure
Step 2 Choose Data Protection > Remote Device.
Step 3 Click Add Remote Device.

The Wizard for Adding Remote Device dialog box is displayed.
Step 4 Select the remote device type, and set up the connection to the remote device.
NOTICE
l If Running Status of an added link is Invalid, delete and add the link again.
l To ensure data transfer security among storage systems, you are advised to use a device
such as a security gateway to encrypt links to prevent information leakage.
l If the version of the local device is different from that of the remote device, you need to
add a remote device on the newer version device. Otherwise the operation may fail.
l Replication
Adding an iSCSI link
i. Set Link Type to iSCSI.
ii. Set parameters for the iSCSI link. Table 4-5 lists related parameters.
Table 4-5 iSCSI link parameters

Parameter Description Setting
Controller Name of the local [Example]

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

Ethernet port CTE0.A.IMO1.P0
connected to the
remote storage device.
IP Address IP address of the [Example]

Ethernet port on the 192.168.26.12

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Username The user used for [Value]

communication The default
authentication between username of the
remote devices. machine-machine
If remote devices user is mm_user.
are OceanStor Obtain the super
18000 series administrator or
V100R001C20, T administrator
series account on the
V200R002C20, or remote device.
OceanStor V3
series
V300R001C10 or
later, you need to
use the machine-
machine user.
If remote devices
are OceanStor
18000 series
V100R001C10, T
series
V200R002C10, or
OceanStor V3
series
V300R001C00 or
earlier, you need to
use the super
administrator or
administrator
account on the older
version remote
device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Password Password of the user [Value]

used for The default
communication password of the
authentication between machine-machine
remote devices. user is
If remote devices mm_user@storage
are OceanStor .
18000 series NOTE
V100R001C20, T You are advised to
series change your login
V200R002C20, or password
periodically in the
OceanStor V3
future by executing
series the change
V300R001C10 or mm_user password
later, you need to command. This
use the password of reduces the password
the machine- leakage risks. For
details about how to
machine user.
use the command,
If remote devices see OceanStor 5300
are OceanStor V3&5500 V3&5600
18000 series V3&5800 V3&6800
V3 Storage System
V100R001C10, T
V300R003
series Command
V200R002C10, or Reference.
OceanStor V3
The password of the
series
super administrator
V300R001C00 or
or administrator
account is
use the password of
consistent with the
the super
password on the
administrator or
remote device.
administrator
version remote
device.
TCP/IP Port Ethernet port number [Example]

on the remote storage 3260
device.
Adding a Fibre Channel link

i. Set Link Type to FC.
ii. In the Fibre Channel link list, select a Fibre Channel link.
iii. Set parameters for the Fibre Channel link. Table 4-6 lists related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 4-6 Fibre Channel link parameters

Username The user used for [Value]

communication The default
authentication between username of the
remote devices. machine-machine
If remote devices user is mm_user.
are OceanStor Obtain the super
18000 series administrator or
V100R001C20, T administrator
series account on the
V200R002C20, or remote device.
OceanStor V3
series
V300R001C10 or
later, you need to
use the machine-
machine user.
If remote devices
are OceanStor
18000 series
V100R001C10, T
series
V200R002C10, or
OceanStor V3
series
V300R001C00 or
use the super
administrator or
administrator
version remote
device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Password Password of the user [Value]

used for The default
communication password of the
authentication between machine-machine
remote devices. user is
If remote devices mm_user@storage
are OceanStor .
18000 series NOTE
V100R001C20, T You are advised to
series change your login
V200R002C20, or password
periodically in the
OceanStor V3
future by executing
series the change
V300R001C10 or mm_user password
later, you need to command. This
use the password of reduces the password
the machine- leakage risks. For
details about how to
machine user.
use the command,
If remote devices see OceanStor 5300
are OceanStor V3&5500 V3&5600
18000 series V3&5800 V3&6800
V3 Storage System
V100R001C10, T
V300R003
series Command
V200R002C10, or Reference.
OceanStor V3
The password of the
series
super administrator
V300R001C00 or
or administrator
account is
use the password of
consistent with the
the super
password on the
administrator or
remote device.
administrator
version remote
device.
l Heterogeneity
a. Set parameters for the iSCSI link. Table 4-7 lists related parameters.
Table 4-7 iSCSI link parameters
Controller Name of the local [Example]

storage device's CTE0.A
controller connected to
the remote storage
device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Local Port Local storage device's [Example]

Ethernet port connected CTE0.A.IMO1.P0
to the remote storage
device.
IP Address IP address of the [Example]

Ethernet port on the 192.168.26.12
TCP/IP Port Ethernet port number on [Example]

the remote storage 3260
device.
b. Optional: Select Enable CHAP authentication, and enter CHAP Name,

Password and Confirm Password.
Step 5 Click Next. The information summary is displayed.
Step 6 Click Finish. The operation result is displayed. Perform the following operations based on the
number of links you want to add:
l To add only one link, click Close.
l To add another link for link redundancy, select Continue adding links and click Close.
The Add Link dialog box is displayed. Perform Step 7 as prompted.
NOTE
After the links are added, you can select the remote device from the remote device list. On the
navigation bar, click Add Link or right-click the device and choose Add Link to add other links.
Step 7 Optional: Perform the following operations based on Link Type:

l Add an iSCSI link.
a. In the Link Type drop-down list, select iSCSI.
b. In the Local Device area, set Controller and Local Port.
c. In the Remote Device area, set IP Address.
d. Click OK.
The Execution Result dialog box is displayed indicating that the operation
succeeded.
e. Click Close.
l Add a Fibre Channel link.
a. In the Link Type drop-down list, select FC.
b. Select the newly added Fibre Channel link and click OK.
The Execution Result dialog box is displayed indicating that the operation
succeeded.
c. Click Close.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.3.6 Creating a Remote Replication

Remote replication copies data from a local storage device to a remote storage device for
remote disaster recovery. remote replication include synchronous remote replication and
asynchronous remote replication.
4.3.6.1 Creating a Synchronous Remote Replication

Creating a synchronous remote replication includes the following operations: configuring
basic information about the remote replication, selecting a primary resource and a secondary
resource, and setting remote replication properties. You can proceed as prompted.
Prerequisites
l The remote replication license is valid.
l The local and remote storage devices must support remote replication.
l The remote storage device is added already, and secondary resource is created on the
remote device.
l The storage room size of primary and secondary resource is the same.
l The status of primary and secondary resource is healthy.
Precautions
Do not create remote replications on any of the following LUNs:
l The snapshot LUN of a snapshot

l The target LUN of a LUN copy
l A LUN on which snapshot rollback is being performed
l The secondary LUN of a clone
l A LUN mapping to a host can not be a secondary LUN of remote replication
l The source or target LUN in a SmartMigration task
Procedure
Step 2 Choose Data Protection > Remote Replication.
Step 3 Click Create.

The Create Remote Replication Wizard dialog box is displayed.
Step 4 Select the replication mode of the remote replication to Synchronous, and click Next.
Step 5 Select a primary resource and a secondary resource.

1. Select a primary resource type from the drop-down list.
Possible values of the primary resource type are LUN, Microsoft Exchange, VMware,
Hyper-V, Oracle and SQL Server.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
2. Optional: When Microsoft Exchange, VMware, Hyper-V, Oracle or SQL Server is

selected as the primary resource type, click Select, select an application instance, and
click OK.
3. In the primary resource area, select the desired primary resource.
4. From the Remote device drop-down list, select the remote device where the secondary
resource resides.
NOTE
If no remote device exists, click Add to add one.

5. In the secondary resource area, select the desired secondary resource.
6. Click Add to Pairs.
Add the pair of the primary and secondary resources to Pairs.
7. Click Next.
Step 6 Set properties of the synchronous remote replication.
1. From the Speed drop-down list, select the desired speed for synchronizing data from the
primary resource to the secondary resource.
Low: When the speed is set to low, remote replication will take a long time. This
value is applicable to scenarios where the service load is heavy. The speed is
normally from 0 to 5 MB/s.
Medium: When the speed is set to medium, remote replication will take relatively
short period. This value is applicable to scenarios where the service load is heavy.
The speed is normally from 10 to 20 MB/s. (default value)
High: When the speed is set to high, remote replication will take a short period.
This value is applicable to scenarios where the service load is relatively light. The
speed is normally from 50 to 70 MB/s.
Highest: When the speed is set to highest, remote replication will be complete in
the shortest period. This value is applicable to scenarios where the service load is
light. The speed is normally above 100 MB/s.
2. In Recovery policy drop-down list, select after the remote replication internal I/O error
is rectified or the replication link is up, whether the remote replication pair automatically
synchronizes data or not.
Manual: The pair enters the To be recovered state. You need to manually
synchronize the data from the primary resource to the secondary resource in the
pair.
Automatic: The pair enters the Synchronizing state. The system will automatically
synchronize the data from the primary resource to the secondary resource in the
pair. (default value)
3. Select the initial synchronization method of the remote replication.
Data is inconsistent between the primary and secondary resources. After a
remote replication task is created, the system automatically performs data
synchronization.: After the remote replication task is created, the data on the
secondary resource is overwritten immediately. Ensure that the data on the
secondary resource is no longer necessary or has been backed up. (default value)
Data is inconsistent between the primary and secondary resources. After a
remote replication task is created, manually perform data synchronization.:
After the remote replication task is created, manually synchronize data on the
primary and secondary resources as soon as possible to ensure data consistency.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
The data on primary and secondary resources is consistent and data

synchronization is not required.: Ensure that the data on the primary and
secondary resources is consistent. If the data is inconsistent, the secondary resource
cannot be used to recover data or take over services from the primary resource
when the primary resource fails. As a result, data loss and service interruption may
occur.
4. Click Next.
Step 7 Optional: Add the remote replication pair to a newly created consistency group.
1. Select Create a consistency group and add pairs to it.
2. Set Name and Description of the consistency group.
3. Click Next.
Step 8 Confirm the creation of the remote replication pair.

1. Click Next and view the configuration summary of the remote replication pair.
2. Click Finish to create the remote replication pair.
3. Click Close to complete remote replication pair creation.
----End
4.3.6.2 Creating an Asynchronous Remote Replication

Creating an asynchronous remote replication includes the following operations: configuring
basic information about the remote replication, selecting a primary resource and a secondary
resource, and setting remote replication properties. You can proceed as prompted.
Prerequisites
l The remote replication license is valid.
l The local and remote storage devices must support remote replication.
l The remote storage device is added already, and secondary LUN is created on the remote
device.
l The storage room size of primary and secondary LUN is the same.
l The status of primary and secondary LUN is healthy.
Precautions
Do not create remote replications on any of the following LUNs:
l The snapshot LUN of a snapshot

l The target LUN of a LUN copy
l A LUN on which snapshot rollback is being performed
l The secondary LUN of a clone
l A LUN mapping to a host can not be a secondary LUN of remote replication
l The source or target LUN in a SmartMigration task

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Procedure

The Create Remote Replication Pair Wizard dialog box is displayed.
Step 4 On the Select Replication Mode page, select Asynchronous. Click Next.
NOTE
File system remote replication supports the asynchronous mode only.
Step 5 Select the primary resource and secondary resource to form a remote replication pair.
1. In Select Primary Resource Type, select the desired resource type.
2. In the Primary Resource area, select the primary resource.
3. In the Secondary Resource area, select a remote device to which the primary resource is
copied from the Remote Device drop-down list.
4. In the Secondary Resource area, select the secondary resource.
5. Click Add to Pairs. After the pair is added successfully, the specified pair will be
displayed in Pairs.
NOTE
When you set Select Primary Resource Type to File system, if the capacities of the primary and
secondary resources are inconsistent, the following risks may arise:
1. When the capacity of the primary resource is larger than that of the secondary resource, remote
replication I/Os may become abnormal, remote replication pairs may be interrupted unexpectedly,
and data at the primary and secondary ends may become inconsistent.
2. When the capacity of the primary resource is smaller than that of the secondary resource, the
capacity at the secondary end is wasted. To optimize capacity utilization, ensure that the capacities
of primary and secondary resources are the same.
The Remote Device Compression Status in the pairs list indicates that the compression algorithm or
protocol of both local and remote storage devices matches or not. If it matches, the status displays as
Valid, indicating data compression transmission is available. Otherwise, the status displays as Invalid,
indicating data compression transmission is not available.
6. Click Next.
The Set Properties page is displayed.
Step 6 Set properties of the remote replication pair.
1. On the Set Properties page, set the remote replication parameters based on your service
requirements.
Table 4-8 describes parameters of remote replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 4-8 Parameters of remote replication

Speed Speed of data [Default value]

synchronization. The values Medium
include:
Low: When the speed is
set to low, remote
replication will take a long
time. This value is
applicable to scenarios
where the service load is
heavy. The speed is
normally from 0 to 5
MB/s.
Medium: When the speed
is set to medium, remote
replication will take
relatively short period.
This value is applicable to
scenarios where the
service load is heavy. The
speed is normally from 10
to 20 MB/s.
High: When the speed is
set to high, remote
replication will take a
short period. This value is
relatively light. The speed
is normally from 50 to 70
MB/s.
Highest: When the speed
is set to highest, remote
replication will be
complete in the shortest
period. This value is
light. The speed is
normally above 100 MB/s.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Recovery Policy After the remote replication [Default value]

internal I/O error is rectified Automatic
or the replication link is up,
the remote replication pair
automatically synchronizes
data or not. The values
include:
Manual: The pair enters
the To be recovered state.
You need to manually
synchronize the data from
the primary resource to the
secondary resource in the
pair.
Automatic: The pair
enters the Synchronizing
state. The system will
automatically synchronize
the data from the primary
resource to the secondary
resource in the pair.
Data During primary and [Default value]

Transmission secondary resource No compression
synchronization, data is
compressed or not. If you
select data compression
transmission, replication links
are with lower bandwidth
pressure, while improving the
replication performance. The
values include:
Compression
No compression
NOTE
When Remote Device
Compression Status is Invalid,
do not configure Data
Transmission as Compression,
or creating a remote replication
pair would fail.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Synchronization Mode of data synchronization [Default value]

Method between the primary resource Manual
and secondary resource. The
values include:
Manual: Data must be
manually synchronized
between the primary
resource and secondary
resource.
Timed wait when
synchronization begins:
The system starts timing
as soon as the latest
synchronization begins.
When the time specified in
Interval has elapsed, the
system automatically starts
to synchronize data
between the primary
resource again.
NOTE
If the latest synchronization
is still being executed after
the time specified in
data synchronization will
start after the latest
synchronization finishes.
Timed wait when
synchronization ends:
synchronization ends.
When the time specified in
system automatically starts
to synchronize data
between the primary
resource again.
Specify the time policy:
The system automatically
synchronizes data between
the primary file system
and secondary file system
based on a specified time
policy.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

NOTE
Specify the time policy is
only applied to file system.
Interval Time spent waiting of the two [Value range]

synchronization methods, If the resource type is LUN,
Timed wait when the unit of the interval can be
synchronization begins and minutes or seconds:
Timed wait when
synchronization ends. n When minutes is used as
the unit, the value is an
NOTE
integer ranging from 1 to
This parameter is available when
Replication Mode is set to 1440 (inclusive).
Asynchronous and n When seconds is used as
Synchronization Method is set the unit, the value is an
to Timed wait when
synchronization begins or
Timed wait when 59 (inclusive).
synchronization ends. If the resource type is file
system, the interval is an
1440 (inclusive), when
minutes is used as the unit.
File system does not support
interval in seconds level.
NOTE
When the primary-end model is
2200 V3, the resource type is LUN,
the unit can only be minutes and
the interval is an integer ranging
from 15 to 1440 (inclusive).
[Default value]
If the unit is minutes, the default
value is 60 minutes.
If the unit is seconds, the default
value is 30 seconds.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Initial Mode of initial data [Default value]

Synchronization synchronization between the Data is inconsistent between the
primary resource and primary and secondary
secondary resource. The resources. After a remote
values include: replication task is created, the
Data is inconsistent system automatically performs
between the primary and data synchronization.
secondary resources.
After a remote
replication task is
created, the system
automatically performs
data synchronization.:
After the remote
replication task is created,
the data on the secondary
resource is overwritten
immediately. Ensure that
the data on the secondary
resource is no longer
necessary or has been
backed up.
Data is inconsistent
between the primary and
After a remote
replication task is
created, manually
perform data
synchronization.: After
the remote replication task
is created, manually
synchronize data on the
primary and secondary
resources as soon as
possible to ensure data
consistency.
The data on primary and
secondary resources is
consistent and data
synchronization is not
required.: Ensure that the
data on the primary and
secondary resources is
consistent. If the data is
inconsistent, the secondary
resource cannot be used to
recover data or take over
services from the primary

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
resource when the primary

resource fails. As a result,
data loss and service
interruption may occur.
This option is not
displayed when the
resource type is file
system.
2. Click Next.
The Add Pairs to Remote Replication Consistency Group page is displayed.
Step 7 Optional: Add the remote replication pair to a newly created consistency group (only applied
to resource type is LUN).
1. Select Create a consistency group and add pairs to it.
2. Set the Name and Description of consistency group.
3. Click Next.
The Summary page is displayed.
Step 8 Confirm the creation of the remote replication pair.

1. Check the remote replication pair information. If correct, click Finish.
2. Read the content in the dialog box carefully, and select I have read and understood the
consequences associated with performing this operation..
3. Click OK.
The Execution Result page is displayed.
4. On Execution Result page, check whether remote replication pair is created
successfully.
5. Click Close.
The remote replication pair displays detailed information in the remote replication pair
list if successfully created.
----End
4.3.7 Creating a Consistency Group

Remote replication can implement data backup and disaster recovery in the scenario where a
host writes data to a single or multiple independent primary LUNs. However, remote
replication cannot implement data backup and disaster recovery in the scenario where a host
writes data to multiple dependent primary LUNs. A consistency group ensures data
consistency of secondary LUNs of all remote replication pairs in the group at the same point
in time (for example, the data of all secondary LUNs are the data copy of its primary LUN at
3:00 PM today), therefore ensures the data availability of primary LUNs after disaster
recovery.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Prerequisites
l The Role of the remote replication pair to be added into the consistency group must be
Primary.
l The remote replication pair to be added into the consistency group must be from the
same storage device.
l The Replication Mode of the remote replication pair to be added into the consistency
group must be the same as the Replication Mode of the consistency group.
Precautions
l If the remote replication pair is not in split status, the system will split the remote
replication pair first and then add it into the consistency group.
l The consistency group does not support the remote replication pair whose resource type
is file system.
l After the remote replication pair has been added into the consistency group, the remote
replication pair will function according to the replication properties of the consistency
group (the properties are Recovery Policy, Speed, Data Transmission,
Synchronization Method, and Interval), and is not relevant to the properties of the
remote replication pair.
Procedure
Step 2 Choose Data Protection > Remote Replication > Consistency Group.

The Create Remote Replication Consistency Group Wizard dialog box is displayed.
Step 4 Configure basic information about the consistency group. The Table 4-9 describes related
parameters.
Table 4-9 Consistency Group Parameters
Name The name of the consistency [Value range]

group. l The name must be
unique.
l The name can contain
letters, digits, periods (.),
underscores (_), and
hyphens (-).
l The name contains 1 to
31 characters.
[Example]
ConsistentGroup001

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Description The description of the None

consistency group.
Replication Mode Data replication mode of a [Default value]

consistency group. The Asynchronous
value includes:
l Synchronous: When
data is written on a
primary resource, the
write request is also sent
to the secondary
resource. Only after the
data is written on both
the primary and
secondary resources
successfully, does the
host receive a successful
data write message.
Synchronous mode
ensures that the data on
the primary resource and
secondary resource
synchronize in real-time.
If the primary resource is
written successfully, a
write success
acknowledgement is
returned to the host.
l Asynchronous: When
primary resource
successfully, the host
receive a successful data
write message. In the
meanwhile, the primary
site records the data
difference between the
written data and the
secondary resource. In
the data synchronization
later, only the different
data the primary site
records are synchronized
to the secondary site,
reducing the write
latency of application
server to the minimum.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Recovery Policy After the remote replication [Default value]

the consistency group
include:
l Manual: The
consistency group enters
the To be recovered
state. You need to
manually synchronize
resource.
l Automatic: The
the Synchronizing state.
The system will
automatically
synchronize the data
from the primary
resource.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Speed Rate of data synchronization [Default value]

of the consistency group. Medium
The values include:
l Low: When the speed is
set to low, remote
long time. This value is
heavy. The speed is
MB/s.
l Medium: When the
speed is set to medium,
remote replication will
take relatively short
heavy. The speed is
MB/s.
l High: When the speed is
set to high, remote
short period. This value
is applicable to scenarios
relatively light. The
speed is normally from
50 to 70 MB/s.
l Highest: When the speed
replication will be
light. The speed is
normally above 100
MB/s.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Data Transmission During data synchronization [Default value]

for the consistency group, No compression
data is compressed or not. If
NOTE
you select data compression This parameter is available
transmission, replication only when Replication Mode
links are with lower is set to Asynchronous.
bandwidth pressure, while
improving the replication
performance. The values
include:
l Compression
l No compression
Synchronization Method Mode of data [Default value]

synchronization of the Manual
consistency group. The
NOTE
values includes: This parameter is available
l Manual: only when Replication Mode
Synchronization is is set to Asynchronous.
performed manually.
l Timed wait when
When the time specified
in Interval has elapsed,
the system automatically
starts to synchronize data
between the primary
resource again.
NOTE
If the latest
synchronization is still
being executed after the
time specified in Interval
has elapsed, the data
synchronization will start
after the latest
l Timed wait when
as soon as a
the system starts to
synchronize data again.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Interval Waiting time for the two [Value range]

synchronization methods, l An integer ranging from
Timed wait when 1 to 1440 (inclusive),
synchronization begins and when minutes is used as
Timed wait when the unit.
l An integer ranging from
3 to 59 (inclusive), when
seconds is used as the
unit.
[Default value]
60, when minutes is used as
the unit.
30, when seconds is used as
the unit.
NOTE
This parameter is available
only when Synchronization
Method is set to Timed wait
when synchronization begins
or Timed wait when
Step 5 Select the remote replication pair that you want to add to the consistency group.
1. Click Next, and in Owning Remote Device of Secondary Resource of Pair, select the
remote device.
NOTE
The remote device is the storage device which the secondary resource of the remote replication pair to
be added into the consistency group belongs to.
2. From the Available Remote Replications Pairs list, select one or multiple remote
replication pairs and click to add.

Step 6 Confirm the consistency group creation.
1. Click Next and view the configuration summary of the consistency group to be created.
2. Click Finish to create the consistency group.
The Execution Result dialog box is displayed.
3. Click Finish to complete creating the consistency group.
----End
4.4 Managing Remote Replications

This function allows you to set up a replication relationship between local and remote storage
devices to copy data from the primary resource to the secondary resource. When data on one
storage device is lost due to a disaster, data on the other storage device is available. This
ensures data integrity and availability.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.4.1 Viewing Information of Remote Replication Pair

This operation enables you to view information about existing remote replication pairs, so that
you can effectively monitor the status of remote replication.
Context
l On the remote replication management page, you can click Refresh to refresh remote
replication pair information.
l On the remote replication management page, you can click Keyword and enter
keywords to search for the desired remote replication pair information.
l On the remote replication management page, you can click and select the pair
information items you want to view.
Procedure
Step 3 View the information of remote replication pairs. Table 4-10 describes related parameters.
Table 4-10 Remote replication 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
Remote Device Name Name of a remote device. None
Remote Device SN SN of a remote device. None
Pair ID ID of a remote replication None

pair.
Role The local resource of the [Example]

remote replication pair is the Primary
primary resource or not. If
the local resource is the
primary resource, it displays
as Primary. Otherwise, it
displays as Secondary.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Pair Health Status Indicates whether the [Example]

remote replication pair is Normal
functioning normally. The
values include:
l Normal: The pair is
functioning normally.
You can perform the
synchronization
operation.
l Fault: The primary
resource or secondary
resource of the pair
malfunctions or the
replication link is down,
you cannot perform the
synchronization
operation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Pair Running Status Indicates whether the [Example]

running properly. The values
include:
l Normal: Pair has
completed
synchronization
successfully.
l Synchronizing: Pair is
synchronizing data.
l Split: Pair is in the split
status, and the
synchronization is
suspended.
l Interrupted: The remote
replication internal I/O
error or the replication
link is down, and you
cannot perform the
synchronization
operation temporarily.
l To be recovered: After
the remote replication
internal I/O error is
rectified or the
replication link is up, and
if Recovery Policy is
Manual, the pair enters
this status. You need to
manually start
synchronization for the
pair to synchronize data.
l Invalid: The pair is
useless and cannot be
restored in this status,
except deleting it. You
must delete the pair on
both primary and
secondary storage
devices. Otherwise, the
pair creation may fail.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

NOTE
When the running status of a
remote replication repair is
Synchronizing, the progress
bar is displayed on the GUI to
indicate the current
synchronization progress. The
progress may suddenly
change, which is a normal
phenomenon.
Remote Replication Name of the owning [Example]

Consistency Group consistency group of the ConsistentGroup001

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Replication Mode Mode of the data [Example]

replication. The values Synchronous
include:
l Synchronous: When
to the secondary
the primary and
secondary resources
data write message.
Synchronous mode
secondary resource
primary resource
reducing the write
NOTE
File system is only supported
by asynchronous remote
replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Recovery Policy After the remote replication [Example]

the remote replication pair
include:
l Manual: The pair enters
the To be recovered
state. You need to
resource in the pair.
l Automatic: The pair
enters the
Synchronizing state.
The system will
automatically
synchronize data from
the primary resource to
the secondary resource in
the pair.
Primary Resource Data Status of data on the [Example]

Status primary resources. Consistent

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Secondary Resource Data Status of the secondary [Example]

Status resource. The data status Synchronized
between the primary
resource includes:
l Synchronized: Data in
the secondary resource is
the same as that in the
primary resource. Data
availability is the
highest.
l Consistent: Data in the
secondary resource is a
duplicate of the data in
the primary resource (at
the time the latest
successful
synchronization starts).
In this state, data in the
secondary resource is
available but not
necessarily the same as
the current data in the
primary resource.
l Inconsistent: Data in the
secondary resource is not
a duplicate of the data in
the current point in time
or at the time the
previous synchronization
is ended). In this state,
data in the secondary
resource is unavailable.
You can synchronize the
data to ensure data
consistency between the
primary resource and
secondary resource.
NOTE
Synchronized is only applied
for synchronous remote
replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Secondary Resource Protection status of the [Example]

Protection secondary resource. Once Enable
protection for secondary
resource of remote
replication pair is enabled,
the application server cannot
modify the data of
secondary resource,
ensuring the security of the
data of the secondary
resource.
Data Transmission During primary and [Example]

secondary resource Compression
synchronization, data is
compressed or not. If it is
data compression
transmission, replication
links are with lower
include:
l Compression
l No compression
Compression Status If the status displays as [Example]

Valid, indicating data Valid
compression transmission is
available for the remote
replication. If the status
displays as Invalid,
indicating data compression
transmission is not available
or data compression
transmission is not selected
for the remote replication.
Step 4 Click a remote replication pair, under the pair list, the information of the remote replication
pair is displayed in graphic style. Table 4-11 lists the parameters.
Table 4-11 Parameters of a remote replication pair

Local Device Name of a local device. None
Primary Resource Name of the primary None

resource.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Secondary Resource Name of the secondary None

resource.
Remote Device Name of a remote device. None

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Synchronization Method Method to synchronize data [Example]

from the primary resource to Manual
the secondary resource. The
NOTE
values include: This parameter is available
l Manual: The only when Replication Mode
synchronization is set to Asynchronous
operation must be carried
out manually.
l Timed wait when
between the primary
resource again.
NOTE
If the latest
after the latest
l Timed wait when
l Specify the time policy:
The system
automatically
synchronizes data
between the primary file
system and secondary
file system based on a
specified time policy.
NOTE

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Interval Time spent waiting of the [Value range]

two synchronization l If the resource type is
methods, Timed wait when LUN, the interval is an
synchronization begins and integer ranging from 1 to
Timed wait when 1440 (inclusive), when
synchronization ends. minutes is used as the
unit.
l If the resource type is
file system, the interval
is an integer ranging
from 5 to 1440
(inclusive), when
minutes is used as the
unit.
l The interval is an integer
ranging from 3 to 59
(inclusive), when
unit.
NOTE
l This parameter is available
when Replication Mode is
set to Asynchronous and
Synchronization Method
is set to Timed wait when
Timed wait when
l File system does not
support interval in seconds
level.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Time Policy The system automatically NOTE

synchronizes data between This parameter is valid only
when the Replication Mode is
the primary file system and
Asynchronous, the resource
secondary file system based type is file system, and
on a specified time policy. Synchronization Method is
l Hourly: Specifies when Specify the time policy.
data synchronization
begins in every hour. Its
value is an integer
ranging from 0 to 59.
l Daily: Specifies when
begins in every day. Its
value ranges from 00:00
to 23:59.
l Weekly: Specifies when
begins in every week. Its
value ranges from
Monday to Sunday and
00:00 to 23:59.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Speed Speed of data [Example]

synchronization. The values High
include:
set to low, remote
heavy. The speed is
MB/s.
l Medium: When the
heavy. The speed is
MB/s.
set to high, remote
50 to 70 MB/s.
replication will be
light. The speed is
normally above 100
MB/s.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Synchronization Progress Progress of synchronizing [Example]

data between the primary 25%
resource.
NOTE
The synchronization progress
is indicated by an arrow
between the primary resource
and secondary resource.
Start Time Time when a remote [Format]

replication task is started. YYYY-MM-DD hh:mm:ss
UTC+hh:mm
[Example]
2015-08-15 16:51:32 UTC
+08:00
End Time Time when a remote [Format]

replication task is complete. YYYY-MM-DD hh:mm:ss
UTC+hh:mm
[Example]
2015-08-15 20:51:32 UTC
+08:00
----End
4.4.2 Modifying the Properties of a Remote Replication Pair

This operation enables you to change the synchronization type, speed, and recovery policy of
a remote replication pair.
Precautions
The properties of the remote replication pair that has been added into the consistency group
cannot be modified.
NOTE
After the remote replication pair has been added into the consistency group, the remote replication pair will
function according to the replication properties of the consistency group (the properties are Recovery Policy,
Data Transmission, Speed, Synchronization Method, and Interval), and is not relevant to the properties of
the pair.
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Step 3 Select the remote replication pair you want to modify and click Properties.
The Properties of Pair dialog box is displayed.
Step 4 Modify properties of the remote replication pair. Table 4-12 describes related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 4-12 Remote replication parameters

Synchronization Method Way of synchronizing data [Example]

between the primary and Manual
NOTE
l Manual: A user needs to This parameter is available
manually synchronize only when Replication Mode
data from the primary is set to Asynchronous.
resource.
l Timed wait when
between the primary
resource again.
NOTE
If the latest
after the latest
l Timed wait when
between the primary
resource again.
l Specify the time policy:
The system
automatically
synchronizes data
between the primary file
system and secondary
file system based on a
specified time policy.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

NOTE
Interval Time spent waiting of the [Value range]

two synchronization l If the resource type is
methods, Timed wait when LUN, the interval is an
synchronization begins and integer ranging from 1 to
Timed wait when 1440 (inclusive), when
synchronization ends. minutes is used as the
unit.
l If the resource type is
file system, the interval
is an integer ranging
from 5 to 1440
(inclusive), when
minutes is used as the
unit.
l The interval is an integer
ranging from 3 to 59
(inclusive), when
unit.
NOTE
l This parameter is available
set to Asynchronous and
Synchronization Method
is set to Timed wait when
Timed wait when
l File system does not
support interval in seconds
level.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Time Policy The system automatically [Value range]

synchronizes data between l Hourly: Specifies when
the primary file system and data synchronization
secondary file system based begins in every hour. Its
on a specified time policy. value is an integer
ranging from 0 to 59.
l Daily: Specifies when
begins in every day. Its
value ranges from 00:00
to 23:59.
l Weekly: Specifies when
begins in every week. Its
value ranges from
Monday to Sunday and
00:00 to 23:59.
NOTE
This parameter is valid only
when the Replication Mode is
Asynchronous, the resource
type is file system, and
Synchronization Method is
Specify the time policy.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Speed Speed of data [Example]

synchronization. The values High
include:
set to low, remote
heavy. The speed is
MB/s.
l Medium: When the
heavy. The speed is
MB/s.
set to high, remote
50 to 70 MB/s.
replication will be
light. The speed is
normally above 100
MB/s.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Recovery Policy Policy applied by a remote [Example]

replication to recover after Automatic
the storage system recovers
from a failure. The value
can be Manual or
Automatic.
l Manual: The
maintenance personnel
must manually
the secondary resource.
l Automatic: The system
will automatically
the secondary resource.
Data Transmission Data compression [Example]

transmission or not during No compression
resource synchronization. If
you select data compression
include:
l Compression
l No compression
NOTE
l When Compression
Status of the remote
device is Invalid, do not
configure Data
Transmission as
Compression, or
modifying the properties
of the pair would fail.
l Select Data
Protection >
Remote Device, and click
Modify to view the
Compression Status of
the remote device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Enable the I/O timeout If data is written into the [Default value]
threshold for the secondary primary LUN but fails to be Disabled
LUN written into the secondary
NOTE
LUN when the timeout This parameter is available
period you set has elapsed, only when Replication Mode
the remote replication pair is set to Synchronous.
enters the Interrupted
status.
Timeout Threshold (second) The timeout for data written [Value range]
into the secondary LUN. 10 to 30
[Default value]
30
NOTE
only when Enable the I/O
timeout threshold for the
secondary LUN is selected.
Step 5 Confirm the remote replication pair modification.

1. Click OK.
2. Click Close.
----End
4.4.3 Synchronizing a Remote Replication Pair

In the scenario where a remote replication pair has completed the initial synchronization and
then a host writes the primary resource or splits the remote replication pair, there will be data
inconsistency between the primary resource and the secondary resource. In this case, you can
synchronize the remote replication pair to ensure data consistency.
Prerequisites
l The remote replication pair for which you want to perform data synchronization is not
added to a consistency group.
l Secondary resource protection has been enabled.
l The Pair Running Status of the remote replication pair determines whether data
synchronization can be performed for the remote replication pair, as shown in Table
4-13.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 4-13 Status requirements for synchronizing a remote replication
Pair Running Status Synchronizing a Synchronizing an

Synchronous Remote Asynchronous Remote
Replication Pair Replication Pair
Normal
Split
Interrupted
To be recovery
Synchronizing N/A
Invalid
: Able to operate.
: Unable to operate.
Procedure
Step 3 Right-click the remote replication you want to synchronize and choose Synchronize.
Step 4 Confirm the remote replication synchronization.

1. Confirm the information in the dialog box. Select I have read and understood the
consequences associated with performing this operation. and click OK.
The Success dialog box is displayed, indicating that the operation succeeded.
2. Click OK.
----End
4.4.4 Splitting a Remote Replication Pair

If you want a secondary resource to save data on a primary resource at a specific point in
time, maintain a remote replication link, or expand network bandwidth, you must split the
remote replication pair. After a remote replication pair is split, the data written into the
primary resource by the application server will not by synchronized to the secondary resource.
This may cause data inconsistency between the primary resource and secondary resource.
Prerequisites
l The remote replication pair that you want to split is not added to a consistency group.
l Based on Pair Running Status of the remote replication pair, determine whether the
remote replication pair can be split, as shown in Table 4-14.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 4-14 Status requirements for splitting a remote replication

Pair Running Status Splitting a Splitting an
Synchronous Remote Asynchronous Remote
Replication Pair Replication Pair
Normal
Split
Interrupted
To be recovery
Synchronizing
Invalid
: Able to operate.
Precautions
If the remote replication pair does not complete the initial synchronization, splitting the
remote replication pair will cause data on the secondary resource unavailable. Perform this
operation with caution.
Procedure
Step 3 Right-click the remote replication you want to split and choose Split.
Step 4 Confirm the remote replication splitting.
2. Click OK.
NOTE
Once the pair is split, the data of secondary resource will roll back to the data when the latest pair
synchronization completes.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.4.5 Performing a Primary/Secondary Switchover for a Remote

Replication
This operation enables you to switch the roles of the primary and secondary resources of a
remote replication pair. The data synchronization direction changes as the primary/secondary
relationship changes.
Prerequisites
l The remote replication pair for which you want to initiate a primary/secondary
switchover is not added to a consistency group.
l Based on Pair Running Status and Secondary Resource Data Status of the remote
replication pair, determine whether a primary/secondary switchover can be performed for
the remote replication pair, as shown in Table 4-15.
Table 4-15 Status requirements for initiating a primary/secondary switchover

Pair Running Secondary Initiating a Initiating a
Status Resource Data Primary/ Primary/
Status Secondary Secondary
Switchover for a Switchover for
Synchronous an
Remote Asynchronous
Replication Pair Remote
Replication Pair
Normal Synchronized N/A
Normal Consistent N/A
Normal Inconsistent N/A
Split Consistent
Split Inconsistent
Interrupted Consistent
Interrupted Inconsistent
To be recovery Consistent
To be recovery Inconsistent
Synchronizing Inconsistent
Synchronizing Consistent
Invalid Any status
: Able to operate.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Procedure
Step 3 Perform a primary/secondary switchover for a remote replication pair. Right-click the remote
replication pair you want to perform the switchover and choose Primary/Secondary
Switchover.
Step 4 Confirm the primary/secondary switchover.

2. Click OK to complete the primary/secondary switchover.
----End
4.4.6 Enabling Protection For Secondary Resource Of Remote

Replication Pair
Once protection for secondary resource of remote replication pair is enabled, the application
server cannot modify the data of secondary resource, ensuring the security of the data of the
secondary resource.
Prerequisites
Based on Pair Running Status and Secondary Resource Data Status of the remote
replication pair, determine whether enable protection for secondary resource can be performed
for the remote replication, as shown in Table 4-16.
Table 4-16 Status requirements for enabling protection for secondary Resource
Pair Running Status Secondary Resource Enable protection for

Data Status secondary resource
Normal Any status
Split Consistent
Interrupted (link is down) Consistent (Operate on remote

device)
Interrupted (link is up) Any status
To be recovery Any status
Synchronizing Any status
Invalid Any status

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

: Able to operate.
Context
l If resource type is LUN, you cannot write any data into secondary resource after
protection for secondary resource is enabled.
l If resource type is file system, you cannot read or write any data into secondary resource
after protection for secondary resource is enabled.
Procedure
Step 3 Enable protection for secondary resource.

1. Select the remote replication pair you want to enable protection for secondary resource.
2. Click More > Enable Protection for Secondary Resource.
The Success dialog box is displayed.
3. Click OK.
----End
4.4.7 Disabling Protection For Secondary Resource Of Remote

Replication Pair
Once the secondary resource protection of remote replication pair is disabled, the application
server can read and write the data to secondary resource. This operation is mainly applied
when the secondary site takes over the service in the disaster recovery scenario.
Prerequisites
Based on Pair Running Status and Secondary Resource Data Status of the remote
replication pair, determine whether disable protection for secondary resource can be
performed for the remote replication, as shown in Table 4-17.
Table 4-17 Status requirements for disabling protection for secondary resource
Pair Running Status Secondary Resource Disable protection for
Normal Any status
Split Consistent

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Pair Running Status Secondary Resource Disable protection for

Interrupted (link is down) Consistent (Only operate on the

secondary site)
Invalid Any status
: Able to operate.
Procedure

Step 3 Disable protection for secondary resource.
1. Select the remote replication pair you want to disable protection for secondary resource.
2. Click More > Disable Protection for Secondary Resource.
3. Click OK.
----End
4.4.8 Synchronizing Remote Status

You can synchronize data from a remote storage system to a local storage system. The data
includes status and name of the secondary resource, name of the remote storage system, and
so on.
Prerequisites
l The connection between the local storage system and remote storage system is normal.
l Remote replication pair is created.
Procedure

Step 3 Choose More > Synchronize Remote Status.
The Success dialog box is displayed indicating that the operation succeeded.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Step 4 Click OK.
----End
4.4.9 Deleting a Remote Replication Pair

Once a remote replication pair is deleted, the replication relationship between the primary
resource and the secondary resource is deleted, and data on the primary resource will no
longer be copied to the secondary resource.
Prerequisites
l The remote replication pair to be deleted is not added to a consistency group.
l Based on Pair Running Status of the remote replication pair, determine whether the
remote replication can be delete, as shown in Table 4-18.
Table 4-18 Status requirements for deleting a remote replication

Pair Running Status Deleting a Remote Replication Pair
Normal
Split
Interrupted
To be recovery
Synchronizing
Invalid
: Able to operate.
Context
l The essence of deleting a remote replication pair is to delete the remote replication
configuration information of the primary and secondary resources, thereby, to cancel the
replication relationship between them. The configuration information is stored on both
local and remote storage device. In this way, the remote replication pair can be deleted.
l Remote replication configuration is automatically generated in the primary and
secondary resources when the remote replication pair is created.
Procedure
Step 3 In the remote replication list, select a remote replication pair that can be deleted.
Step 4 Delete the selected pair.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
1. Click Delete.
2. In the security alert dialog box, select Only delete the configuration information
about the local device if the local device is disconnected from the remote device and
Forcibly ensure data consistency for the secondary resource based on your needs.
Table 4-19 describes the parameters.
Table 4-19 Parameters for deleting remote replication

Parameter Description
Only delete the configuration information This option is applicable to scenarios

about the local device if the local device where the physical link between the local
is disconnected from the remote device storage system and remote storage system
is disconnected. In such scenarios, this
option is mandatory. Otherwise, the pair
cannot be deleted.
If you want to delete the configuration
information of remote replication from
the remote storage system, you must
perform this operation in the remote
storage system.
NOTE
If the physical link is normal, do not select
this option.
Forcibly ensure data consistency for the If the secondary resource data is
secondary resource inconsistent and the initial
synchronization completes, the secondary
resource will execute snapshot rollback to
ensure data consistency. If the initial
synchronization does not complete, the
secondary resource data may not be
consistent. You are advised to manually
clear the resource to use.
Step 5 Confirm the remote replication deletion.

The Execution Result dialog box is displayed.
2. Click Close to complete deleting the remote replication.
----End
4.5 Managing Consistency Groups

This function allows you to create a consistency group, add remote replications to it, and
centrally manage the remote replications in the consistency group. For example, you can
synchronize or split the remote replications in a consistency group at the same time.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.5.1 Viewing Consistency Group Information

This operation enables you to view information about existing consistency groups, including
basic information and remote replication pair information, so that you can effectively monitor
the status of consistency groups.
Context
l On the consistency group management page, you can click Refresh to refresh
consistency group information.
l On the consistency group management page, you can click Keyword and enter
keywords to search for the desired consistency group information.
l On the consistency group management page, you can click and select the information
items you want to view.
Procedure
Step 3 View basic information about existing consistency groups. Table 4-20 describes the related
parameters.
Table 4-20 Parameters of Consistency Group

Name Name of a consistency [Example]

group. ConsistentGroup001
ID ID of a consistency group. [Example]

00E0F0000050000

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Health Status Indicates whether the [Example]

consistency group is Normal
values include:
l Normal: The
consistency group is
You can perform the
synchronization
operation.
l Fault: The consistency
group malfunctions or
the replication link is
down, you cannot
perform the
synchronization
operation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Running Status Indicates the consistency [Example]

group is running properly. Normal
The values include:
l Normal: Consistency
group has completed
synchronization
successfully.
synchronizing data.
l Split: Consistency group
is in the split status, and
the synchronization is
suspended.
cannot perform the
synchronization
rectified or the
Manual, the consistency
group enters this status.
You need to manually
start synchronization for
the consistency group to
synchronize data.
l Invalid: Consistency
group is useless and
cannot be restored in this
status, except deleting it.
You must delete the
consistency group on
both primary and
secondary storage
consistency group
creation may fail.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Replication Mode Data replication mode of the [Example]

consistency group. The Synchronous
values include:
l Synchronous: When
to the secondary
the primary and
secondary resources
data write message.
Synchronous mode
secondary resource
primary resource
reducing the write
Role The local resource of the [Example]

remote replication pair in Primary
the consistency group is the
primary resource or not. If
the local resource is the
primary resource, it displays
as Primary. Otherwise, it
displays as Secondary.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

include:
l Manual: The
the To be recovered
state. You need to
resource.
l Automatic: The
The system will
automatically
from the primary
resource.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Speed Rate of data synchronization [Example]

The values include:
set to low, remote
heavy. The speed is
MB/s.
l Medium: When the
heavy. The speed is
MB/s.
set to high, remote
50 to 70 MB/s.
replication will be
light. The speed is
normally above 100
MB/s.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Synchronization Method Mode of data [Example]

synchronization for Manual
consistency group. This
parameter is displayed only
set to Asynchronous. The
values include:
l Manual: Data
synchronization needs to
be performed manually.
l Timed wait when
between the primary
resource again.
NOTE
If the latest
after the latest
l Timed wait when
as soon as a
synchronization
operation is completed.
When the time indicated
by Interval has elapsed,
the system starts
synchronizing data
again.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Interval Waiting time for the two [Example]

synchronization methods, 30 minutes
Timed wait when
NOTE
synchronization begins and
Timed wait when
NOTE
This parameter is displayed
only when Replication Mode
is set to Asynchronous and
Synchronization Method is
set to Timed wait when
Timed wait when
Data Transmission During data synchronization [Example]

for the consistency group, Compression
it is data compression
include:
l Compression
l No compression

or data compression
Step 4 Click the desired consistency group and view its remote replication information. The
following Table 4-21describes the related parameters.
Table 4-21 Parameters of Remote Replication Pair

Local Resource Name Name of a local resource. NA
Local Resource ID ID of a local resource. NA

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Resource Name Name of a remote resource. NA
Remote Resource ID ID of a remote resource. NA
Remote Device Name Name of the remote device. NA
Remote Device SN Serial No. of the remote NA

device.
Pair ID ID of the remote replication NA

pair.
Pair Health Status Indicates whether the [Example]

values include:
l Normal: The pair is
You can perform the
synchronization
operation.
l Fault: The pair
malfunctions or the
replication link is down,
you cannot perform the
synchronization
operation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Pair Running Status Indicates whether the [Example]

running properly. The values
include:
l Normal: Pair has
completed
synchronization
successfully.
synchronizing data.
l Split: Pair is in the split
status, and the
synchronization is
suspended.
cannot perform the
synchronization
rectified or the
Manual, the pair enters
this status. You need to
manually start
synchronization for the
pair to synchronize data.
l Invalid: The pair is
useless and cannot be
restored in this status,
except deleting it. You
must delete the pair on
both primary and
secondary storage
pair creation may fail.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

NOTE
When the running status of a
remote replication repair is
Synchronizing, the progress
bar is displayed on the GUI to
indicate the current
synchronization progress. The
progress may suddenly
change, which is a normal
phenomenon.
Remote Replication Name of the owning [Example]

Consistency Group consistency group of the ConsistentGroup001
remote replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Replication Mode Mode of the data [Example]

replication. The values Synchronous
include:
l Synchronous: When
to the secondary
the primary and
secondary resources
data write message.
Synchronous mode
secondary resource
primary resource
reducing the write
NOTE
File system is only supported
by asynchronous remote
replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Recovery Policy A recovery policy supports [Example]

the following recovery Automatic
modes:
l Manual: The remote
replication pair enters the
To be recovered state.
Remote replication must
resources to the
l Automatic: The remote
replication pair enters the
Synchronizing state.
The system will
automatically
synchronize the
incremental data from
the primary resources to
the secondary resources
in the remote replication.
Primary Resource Data Status of data on the [Example]

Status primary resources. Consistent

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Secondary Resource Data Status of the secondary [Example]

Status resource. The data status Consistent
between the primary
resource includes:
l Synchronized: Data in
the secondary resource is
the same as that in the
primary resource. Data
availability is the
highest.
l Consistent: Data in the
secondary resource is a
duplicate of the data in
the time the latest
successful
synchronization starts).
In this state, data in the
secondary resource is
available but not
necessarily the same as
the current data in the
primary resource.
l Inconsistent: Data in the
secondary resource is not
a duplicate of the data in
the current point in time
or at the time the
previous synchronization
is ended). In this state,
data in the secondary
resource is unavailable.
You can synchronize the
data to ensure data
consistency between the
primary resource and
secondary resource.
NOTE
Synchronized is only applied
for synchronous remote
replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Secondary Resource Protection status of the [Example]

Protection secondary resource. Once Enable
protection for secondary
resource of remote
replication pair is enabled,
the application server cannot
modify the data of
secondary resource,
ensuring the security of the
data of the secondary
resource.
Data Transmission Data compression [Example]

transmission or not during Compression
resource synchronization. If
it is data compression
performance.

or data compression
----End
4.5.2 Changing the Properties of a Consistency Group

This operation enables you to change the name, description, recovery policy and rate of a
consistency group.
Caution
The properties of pairs in a consistency group will not be changed after the properties of
consistency group are modified, but the working properties change to the properties of
existing consistency group.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Procedure
Step 3 Select the consistency group whose properties you want to modify and click Properties.
The Properties of Consistency Group dialog box is displayed.
Step 4 Modify properties of the consistency group. Table 4-22 describes the related parameters.
Table 4-22 Parameters of Consistency Group

Name Name of a consistency [Example]

group. ConsistentGroup001
Description Description of a consistency [Example]

group. None

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Synchronization Method Mode of data [Example]

synchronization of the Manual
consistency group. The
NOTE
values includes: This parameter is available
l Manual: only when Replication Mode
Synchronization is is set to Asynchronous.
performed manually.
l Timed wait when
between the primary
resource again.
NOTE
If the latest
after the latest
l Timed wait when
as soon as a

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Interval Waiting time for the two [Value range]

synchronization methods, l Integer from 1 to 1440
Timed wait when (minutes)
synchronization begins and
Timed wait when l Integer from 10 to 59
synchronization ends. (seconds)
[Example]
50 minutes
NOTE
only when Synchronization
Method is set to Timed wait
when synchronization begins
or Timed wait when

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Speed Rate of data synchronization [Example]

The values include:
set to low, remote
heavy. The speed is
MB/s.
l Medium: When the
heavy. The speed is
MB/s.
set to high, remote
50 to 70 MB/s.
replication will be
light. The speed is
normally above 100
MB/s.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System

include:
l Manual: The
the To be recovered
state. You need to
resource.
l Automatic: The
The system will
automatically
from the primary
resource.
Data Transmission During data synchronization [Example]

for the consistency group, No compression
NOTE
you select data compression This parameter is available
transmission, replication only when Replication Mode
links are with lower is set to Asynchronous.
include:
l Compression
l No compression
Enable the I/O timeout If data is written into the [Example]

threshold for the secondary primary LUN but fails to be Enabled
LUN written into the secondary
NOTE
LUN when the timeout This parameter is available
period you set has elapsed, only when Replication Mode
the remote replication pair is set to Synchronous.
enters the Interrupted
status.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Timeout Threshold (second) The timeout for data written [Example]

into the secondary LUN. 30
NOTE
only when Replication Mode
is set to Synchronous.
Step 5 Confirm the operation of modifying properties of the consistency group.

1. Click OK.
The Execution Result dialog box is displayed indicating that the operation is successful.
2. Click Close to complete modifying the properties of the consistency group.
----End
4.5.3 Synchronizing a Consistency Group

This operations enables all remote replication pairs contained in a consistency group to
initiate data synchronization simultaneously so that data is synchronized from all primary
LUNs to all secondary LUNs at the same point in time, ensuring data validity.
Prerequisites
l This operation can be performed only on the primary device of a consistency group.
l Secondary resource protection has been enabled.
l Based on Running Status of a consistency group, determine whether data
synchronization can be performed for the consistency group, as shown in Table 4-23.
Table 4-23 Status requirements for synchronizing a consistency group

Running Status of a Synchronizing Synchronizing
Consistency Group Synchronous Remote Asynchronous Remote
Replications in a Replications in a
Consistency Group Consistency Group
Normal
Split
Interrupted(Linked down)
Interrupted(Linked up)
To be recovery
Invalid
Synchronizing
: Able to operate.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Precautions
During the synchronous consistency groups are synchronizing, if the storage system happens
to controller restoration, which may cause some remote replications result in synchronization
failure, at this time, the consistency groups can not guarantee the data consistency.
Procedure
Step 3 Right-click the desired consistency group and choose Synchronize.

Step 4 Confirm the synchronization operation.
1. Carefully read the contents of the dialog box. Then click the check box next to the
statement I have read the warning message carefully. and click OK to confirm the
information.
2. Click OK.
The Success dialog box is displayed indicating that the operation is successful.
3. Click OK to complete synchronizing data from the primary LUNs to the secondary
LUNs in the consistency group.
----End
4.5.4 Splitting a Consistency Group

This operation enables you to split all remote replication pairs in a consistency group
simultaneously so that a full data copy is generated for each secondary LUN in each pair,
facilitating report generation, test, data mining, decision making, and data recovery.
Precautions
l Based on Running Status of a consistency group, determine whether remote
replications in the consistency group can be split, as shown in Table 4-24.
Table 4-24 Status requirements for splitting remote replications in a consistency group
Running Status of a Consistency Splitting Remote Replications in a
Group Consistency Group
Normal
Split
Interrupted
To be recovery
Invalid

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Running Status of a Consistency Splitting Remote Replications in a

Group Consistency Group
Synchronizing
: Able to operate.
l During the synchronous consistency groups are splitting, if the storage system happens
to controller restoration, which may cause some remote replications result in split failure,
at this time, the consistency groups can not guarantee the data consistency.
Procedure
Step 3 Right-click the desired consistency group and choose Split.

Step 4 Confirm the operation of splitting remote replications in the consistency group.
statement I have read and understood the consequences associated with performing
this operation. and click OK to confirm the information.
2. Click OK.
3. Click OK to complete splitting remote replications in the consistency group.
----End
4.5.5 Performing Primary/Secondary Switchover of a Consistency

Group
This operation enables you to switch between the primary LUNs and the secondary LUNs in a
consistency group. When the primary LUNs in a consistency group fail, you can initiate a
primary/secondary switchover to enable the secondary LUNs to become the new primary
LUNs, taking over services from the original primary LUNs to ensure service continuity.
Prerequisites
Based on Running Status of a consistency group and Secondary Resource Data Status of
the remote replications added to the consistency group, determine whether a primary/
secondary switchover can be performed for the consistency group, as shown in Table 4-25.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Table 4-25 Status requirements for initiating a primary/secondary switchover for a

consistency group
Running Status of Secondary Initiating a Initiating a
a Consistency Resource Data Primary/ Primary/
Group Status of Remote Secondary Secondary
Replications Switchover for a Switchover for a
synchronous asynchronous
Consistency Consistency
Group Group
Normal Synchronized N/A
Normal Consistent N/A
Normal Inconsistent N/A
Split Consistent
Split Inconsistent
Interrupted Consistent
Interrupted Inconsistent
To be recovery Consistent
To be recovery Inconsistent
Invalid Any status
: Able to operate.
Procedure
Step 3 Right-click the desired consistency group and choose Primary/Secondary Switchover.
Step 4 Confirm the primary/secondary switchover operation.
1. Carefully read the contents of the dialog box, and click OK for confirmation.
2. Click OK to complete the primary/secondary switchover.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.5.6 Enabling Protection For Secondary Resource Of Consistency

Groups
This operations enables protection for secondary resource of all remote replication pairs in
consistency group, and the data of secondary resource can not be written to ensure the
security of the data from the secondary resource.
Prerequisites
the remote replications added to the consistency group, determine whether enable protection
for secondary resource can be performed for the consistency group, as shown in Table 4-26.
Table 4-26 Status requirements for enabling protection for secondary resource

Normal Any status
Split Consistent

device)
Invalid Any status
: Able to operate.
Procedure
Step 3 Enable protection for secondary resource.

1. Select the consistency group you want to enable protection for secondary resource.
2. Click More > Enable Protection for Secondary Resource.
3. Click OK.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.5.7 Disabling Protection For Secondary Resource Of

Consistency Groups
This operations disables protection for secondary resource of all remote replication in
consistency group, and the data of secondary resource can be written again.
Prerequisites
the remote replications added to the consistency group, determine whether disable protection
for secondary resource can be performed for the consistency group, as shown in Table 4-27.
Table 4-27 Status requirements for disabling protection for secondary resource

Normal Any status
Split Consistent

device)
Invalid Any status
: Able to operate.
Procedure
Step 3 Disable protection for secondary resource.

1. Select the consistency group you want to disable protection for secondary resource.
2. Click More > Disable Protection for Secondary Resource.
3. Click OK.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
4.5.8 Adding a Remote Replication Pair

This operation enables you to add a remote replication pair to a consistency group. This
ensures that the data of secondary resource of added pair is consistent with that of other pairs
in the group at the same point in time.
Prerequisites
l The Replication Mode of the remote replication pair to be added into the consistency
group must be the same as the Replication Mode of the consistency group.
l A remote replication pair can be added only when the Role of the consistency group is
Primary.
l The Role of the remote replication pair to be added into the consistency group must be
Primary.
l The number of the remote replication pair in consistency group does not reach the
maximum number of specifications.
Precautions
l If the consistency group is in split status, when a remote replication pair is added, the
system will split the remote replication pair first and then add it into the consistency
group.
l If the consistency group is not in split status, when a remote replication pair is added, the
system will split the consistency group first, split the remote replication pair and add it
into the group, and then synchronize the consistency group.
l After the remote replication pair has been added into the consistency group, the remote
replication pair will function according to the replication properties of the consistency
group (the properties are Recovery Policy, Speed, Data Transmission,
Synchronization Method, and Interval), and is not relevant to the properties of the
Procedure
Step 3 Right-click a consistency group to which you want to add a remote replication pair and
choose Add Remote Replication Pair
The Add Remote Replication Pairs dialog box is displayed.
Step 4 In Owning Remote Device of Secondary Resource of Pair, select the remote device.
NOTE
The remote device is the storage device which the secondary resource of the remote replication pair to be
added into the consistency group belongs to.
Step 5 From the Available Remote Replications Pairs list, select one or multiple remote replication
pairs and click .
Step 6 Confirm the operation of adding remote replication pair.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
1. Click OK.
The Execution Result message box is displayed, indicating that the operation
succeeded.
2. Click Close to complete adding remote replication pair.
----End
4.5.9 Removing a Remote Replication Pair

This operation enables you to remove a remote replication pair from a consistency group.
Data of secondary resource of a removed remote replication will not be consistent with data of
secondary resources of other remote replication pairs in the consistency group in terms of
synchronization point in time.
Prerequisites
l The consistency group is split.
l A remote replication pair can be removed only when the Role of the consistency group is
Primary.
Precautions
l When a remote replication pair cannot be removed due to a link failure, delete the
consistency group to which the remote replication belongs.
l Once a remote replication pair is removed from the consistency group, the remote
replication pair will work according to its own replication properties.
Procedure
Step 3 Right-click a consistency group from which you want to remove a remote replication pair and
choose Remove Remote Replication Pair
The Remove Remote Replication Pairs dialog box is displayed.
Step 4 From the Available Remote Replications Pairs list, select one or multiple remote replication
pairs and click to remove.

Step 5 Confirm the operation of removing remote replication pair.
1. Click OK.
The Execution Result message box is displayed, indicating that the operation
succeeded.
2. Click Close to complete removing remote replication pair.
----End
4.5.10 Deleting a Consistency Group

This operation enables you to delete an unwanted consistency group.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Prerequisites
Based on Running Status of the consistency group, determine whether the group can be
delete, as shown in Table 4-28.
Table 4-28 Status requirements for deleting a consistency group

Running Status Deleting a Consistency Group
Normal
Split
Interrupted
To be recovery
Synchronizing
Invalid
: Able to operate.
Precautions
l The essence of deleting a consistency group is to delete the consistency group
configuration information stored on both local and remote storage device. In this way,
the consistency group can be deleted.
l If the link has failed, you must forcibly delete consistency groups from the local and
remote devices.
l The deletion of a consistency group causes you cannot centrally manage the remote
replication pairs within the group.
Procedure
Step 3 Right-click the desired consistency group and choose Delete.

Step 4 Confirm the operation of deleting the consistency group.
1. Optional: Select Only delete the configuration information about the local device if
the local device is disconnected from the remote device based on the situation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
NOTE
This option is applicable to scenarios where the physical link between the local storage system and
remote storage system is disconnected. In such scenarios, this option is mandatory. Otherwise, the
pair cannot be deleted.
If you want to delete the configuration information of consistency group from the remote storage
device, you must perform this operation in the remote storage system.
If the physical link is normal, do not select this option.
statement I have read and understood the consequences associated with performing
this operation. and click OK to confirm the information.
3. Click OK to complete deleting the consistency group.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block 5 FAQs
5 FAQs
About This Chapter
This section provides answers to frequently asked questions (FAQs). If you encounter
problems during remote replication configuration or maintenance, you can refer to this
section.
5.1 What are the differences between synchronous remote replication and asynchronous
remote replication
5.2 How do I use the secondary LUN in a remote replication
5.3 Why information about the primary device and the secondary device in a remote
replication cannot be updated in real time
5.4 What is the relationship among a remote replication, clone, and consistency group
5.5 What is the principle of setting bandwidth for remote replication and LUN copy among
storage arrays
5.6 Precautions for Creating a Remote Link
5.7 Functions of Reserved Space During Asynchronous Remote Replication
5.8 Impact of Modifying Consistency Group Properties
5.9 When performing a remote replication task, is an initial synchronization required to
synchronize data from the primary storage system to the secondary storage system
5.10 Do I need to stop the services on the primary storage system before performing the initial
synchronization
5.11 Impact of the Secondary Storage System Failure on Remote Replication
5.12 Do File Remote Replication and Block Remote Replication Use the Same License

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
5.1 What are the differences between synchronous remote

replication and asynchronous remote replication
Question
What are the differences between synchronous remote replication and asynchronous remote
replication?
Answer
Both synchronous remote replication and asynchronous remote replication can be used to
back up data remotely, implementing disaster recovery for a storage system. However,
synchronous remote replication and asynchronous remote replication are implemented in
different modes and applicable to different service scenarios.
l Implementation mode
Synchronous remote replication: When data is being written to the primary LUN, a
write request is also sent to the secondary LUN. After both primary LUN and
secondary LUN return a write success response, the storage system returns a write
success response to the host. This ensures real-time data synchronization between
the primary LUN and the secondary LUN.
Asynchronous remote replication: When writing data to the primary LUN, the
primary site records the changed data. After the primary LUN returns a write
success response, the primary site returns a write success response to the host.
Then, data synchronization is performed manually or automatically based on user-
defined trigger conditions to ensure data consistency between the primary LUN and
the secondary LUN.
l Application scenario
Synchronous remote replication requires high bandwidth and low latency.
Therefore, synchronous remote replication typically applies to disaster recovery
scenarios where the primary device and the secondary device are adjacent to each
other, for example, data backup and disaster recovery within the same city.
Asynchronous remote replication does not require high bandwidth and low latency.
Therefore, asynchronous remote replication applies to disaster recovery scenarios
where the primary device and the secondary device are far from each other or
network bandwidth is limited.
5.2 How do I use the secondary LUN in a remote

replication
Question
How do I use the secondary LUN in a remote replication?

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Answer
The primary LUN and the secondary LUN in a remote replication form a pair, and the
secondary LUN stores a data duplicate for the primary LUN.
l In normal cases, the secondary LUN cannot be accessed by a host. To enable a host to
access data on the secondary LUN, you can create a snapshot for the secondary LUN and
map the snapshot to the host.
l When the primary LUN fails and causes service interruption, you must perform a
primary/secondary switchover to change the secondary LUN into the primary LUN, and
then map the new primary LUN to the host.
5.3 Why information about the primary device and the

secondary device in a remote replication cannot be
updated in real time
Question
Why information about the primary device and the secondary device in a remote replication
cannot be updated in real time?
Answer
The symptoms and reasons are as follows:
l Symptom 1: After data synchronization between the primary LUN and the secondary
LUN is initiated, the secondary device does not display the synchronization progress in
real time.
To display the synchronization progress in real time during data synchronization, the
secondary device must send a query task to the primary device. This affects system
performance and the number of tasks.
l Symptom 2: After the name of the primary device is changed, the name in the remote
replication is not updated in real time.
The name of the primary device in a remote replication is obtained by invoking the
interface of the system management module rather than using the remote replication
module. Therefore, after the device name is changed, the remote replication cannot
detect the change. In this case, you can refresh the information manually or log in to the
DeviceManager again. Then, the name of the primary device will be updated.
To obtain the latest information about the primary device and the secondary device in a timely
manner, you can log in to the DeviceManager and click Refresh on the remote replication
management page.
5.4 What is the relationship among a remote replication,

clone, and consistency group
Question
What is the relationship among a remote replication, clone, and consistency group?

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Answer
The relationship among a remote replication, clone, and consistency group are describes as
follows:
l Remote replication and consistency group can be implemented only between separate
storage arrays while clone can be implemented only in a single storage array.
l A remote replication involves two types of objects: pairs and remote replication
consistency groups. A clone involves only one type of object, namely, pairs.
l A consistency group manages remote replications in it in a unified manner. When a
consistency group implements a synchronization, split, or primary/secondary switchover,
the operation applies to all of the remote replications in the consistency group at the
same time, ensuring data consistency among multiple LUNs.
5.5 What is the principle of setting bandwidth for remote

replication and LUN copy among storage arrays
Question
What should the bandwidth for remote replication and LUN copy among storage arrays be to
achieve the optimal system performance?
Answer
The bandwidth refers to the amount of data that is transferred on a channel in a certain period
of time. Its common unit is bit per second (bps). The bandwidth of a computer network refers
to the maximum data rate in the network, that is, the number of bits transferred per second.
When setting the bandwidth, note the follows:
l The bandwidth should be set to meet the requirements of actual services. You can
customize a proper bandwidth as required.
l The bandwidth should be set no larger than the current bandwidth of customers' network.
If the workload in the system is heavy, the bandwidth for remote replication and LUN copy
among storage arrays can be correspondingly reduced to guarantee the normal running of
ongoing services.
5.6 Precautions for Creating a Remote Link

Question
What precautions need to be observed during the creation of a remote link?
Answer
l If a Fibre Channel network is used for creating a remote link, set Link Type to FC. If an
IP network is used, set Link Type to iSCSI.
l If two storage systems of different versions are used for creating a remote link, initiate
link creation from the storage system of the later version. Otherwise, link creation fails.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
5.7 Functions of Reserved Space During Asynchronous

Remote Replication
Question
How do I plan storage pool reserved space during asynchronous remote replication? What are
the functions of reserved space?
Answer
Reserved space stores snapshots generated during asynchronous remote replication. Storage
space is reserved because:
l Copy-on-write (COW) for I/Os newly written to the host during remote replication
occupies the storage pool space of the primary storage array. In addition, COW for data
synchronization I/Os of the secondary storage array occupies the storage pool space of
the secondary storage array.
l If the storage pool cannot provide sufficient space, COW for host I/Os or data
synchronization I/Os of the secondary storage array fails due to insufficient space. As a
result, the remote replication session enters the split state. You are advised to reserve
30% of LUN space in an asynchronous remote replication for copy-on-write.
When configuring asynchronous remote replication, reserve certain space in the storage pool
of the secondary storage array to ensure that sufficient space is provided for COW for host
I/Os or data synchronization I/Os of the secondary storage array during remote replication.
The following example shows how to plan reserved space:
The scheduled synchronization period of asynchronous remote replication is 1 hour, the

synchronization rate is medium (15 MB/s on average), and the host bandwidth is 5 MB/s.
l Amount of data written into the host during 1 hour = 1 x 60 x 60 x 5 = 18000 MB
l Time required for replicating data from the primary LUN to the secondary LUN =
18000/15 = 1200s
l Amount of data written into the primary LUN when data is replicated from the primary
LUN to the secondary LUN = 1200 x 5 = 6000 MB
Therefore, at least 6000 MB space must be reserved in the storage pool of the primary storage
array and at least 18000 MB space must be reserved in the storage pool of the secondary
storage array. If a primary/secondary switchover is required, at least 18000 MB space must be
reserved in the storage pools of both the primary and secondary storage arrays.
NOTE
l The size of each data block written by the host must be considered during reserved space planning.
If the COW granularity for host I/Os is 64 KB and the size of each data block written by the host is
smaller than 64 KB, the reserved space for COW must be larger than the amount of data written by
the host during the copy period.
l If an incremental synchronization is implemented after the remote replication session is interrupted
due to manual splitting or external faults and, the space required for COW on the secondary storage
array equals the amount of service data delivered by the primary storage array during the
synchronization or the LUN capacity at most.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
5.8 Impact of Modifying Consistency Group Properties

Question
What impact does modifying consistency group properties have on pairs in the consistency
group?
Answer
After the properties of a consistency group are modified, the properties of pairs in the
consistency group keep unchanged. However, the working properties are the properties of the
consistency group. After a member whose rate is Medium is added to a consistency group
and the rate of the consistency group is changed to High, the displayed rate of the remote
replication remains Medium but the working rate is High. After the member exits the
consistency group, its working rate is Medium.
5.9 When performing a remote replication task, is an

initial synchronization required to synchronize data from
the primary storage system to the secondary storage
system
Question
When performing a remote replication task, is an initial synchronization required to
synchronize data from the primary storage system to the secondary storage system?
Answer
Initial synchronization is recommended to make the data on the primary system consistent
with that on the secondary system. However, if you are absolutely sure that the two sets of
data are exactly the same, you can skip this operation.
5.10 Do I need to stop the services on the primary storage

system before performing the initial synchronization
Question
If the primary storage system is processing services and has data stored on it, and I want to
connect a secondary storage system to it and create a remote replication relationship in
between, do I need to stop the services on the primary storage system before performing the
initial synchronization?
Answer
No, you do not need to stop the services, because initial synchronization can be performed
when the primary storage system is processing services.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
5.11 Impact of the Secondary Storage System Failure on

Remote Replication
Question
What is the impact of the secondary storage system failure on remote replication?
Answer
If the secondary storage system is powered off or faulty, services running on the primary
storage system are not affected but the remote replication relationship is interrupted. The
primary storage system records changes after the remote replication relationship is interrupted
in the Data Change Log (DCL) bitmap. After the secondary storage system is recovered, the
remote replication relationship can be restored by one synchronization operation.
5.12 Do File Remote Replication and Block Remote

Replication Use the Same License
Question
Do file remote replication and block remote replication use the same license?
Answer
File remote replication and block remote replication use the same license. After purchasing
and importing a remote replication license file, you can create both file and block remote
replications.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System A Using the External Storage System to Perform Initial
Remote Replication Feature Guide for Block Synchronization for a Remote Replication
A Using the External Storage System to

Perform Initial Synchronization for a Remote
Replication
You can perform initial synchronization for a remote replication using the external storage
system.
NOTICE
This section is intended for Huawei technical engineers. Use this method only under the
guidance of Huawei technical engineers. If you want to use this method to perform initial
synchronization, contact Huawei technical support engineers for help.
A.1 Introduction
After a remote replication is established between the production center and the DR center,
initial synchronization is automatically started to replicate data from the production center to
the DR center.
A.2 Configuration Operation (Using the LUN Copy Feature of the External Storage System)
You can create a LUN copy on the external storage system to implement initial
synchronization for a remote replication.
A.3 Configuration Operation (Using the LUN Copy Feature of the Production and DR
Centers)
You can create a LUN copy on the storage system of the production center and DR center to
implement initial synchronization for a remote replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
A.1 Introduction
After a remote replication is established between the production center and the DR center,
initial synchronization is automatically started to replicate data from the production center to
the DR center.
In actual application scenarios, the amount of data in the production center is large (up to a
terabyte level), but the data transmission bandwidth is limited between the DR center and the
production center. As a result, it takes a long time for initial synchronization to complete.
Performing initial synchronization using the external storage system can greatly reduce the
initial synchronization time.
Figure A-1 shows the process of using the external storage system to perform initial
Figure A-1 The process of using the external storage system to perform initial
synchronization
LUN 2
LUN
Physical transportation
replicaiton
replication
Data
1 3
Data
Remote
LUN replication LUN
4
Storage Storage
system system
Production center DR center

Fibre Channel
Network cable
The process in Figure A-1 is as follows:

1. Replicate data from the production center to the external storage system.
2. Move the external storage system to the DR center.
3. Replicate data from the external storage system to the storage system of the DR center.
4. Start the remote replication form the production center to the DR center.
Methods for performing initial synchronization for a remote replication using the external
storage system vary with provider of the LUN copy feature:
l Method 1: Use the snapshot feature of the production center and the LUN copy feature
of the production and DR centers and create LUN copies in the production center and the
DR center respectively.
l Method 2: Use the snapshot feature of the production center and the LUN copy feature
of the external storage system and create LUN copies on the external storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
A.2 Configuration Operation (Using the LUN Copy

Feature of the External Storage System)
You can create a LUN copy on the external storage system to implement initial
Prerequisites
l The production center and the DR center have network established, remote storage
systems configured, and the primary and secondary LUNs created.
l A LUN has been created on the external storage system. This LUN has the same capacity
as the primary and secondary LUN of the remote replication.
l The external storage system is in the production center and connected to the storage
system of the production center. The remote storage system has been configured in the
production center.
l The external storage system is a Huawei product and supports the LUN copy feature.
l The production center supports the snapshot feature.
Procedure
Step 1 Configure the remote replication form the production center to the DR center.
1. Log in to the storage system of the production center and create a remote replication. The
primary LUN of the remote replication is the LUN of the production center and the
secondary LUN is the LUN of the DR center.
The remote replication is created from the production center to the DR center and its
Pair Health Status is Normal.
NOTE
When creating remote replication, select The primary and secondary LUNs have consistent
data and data synchronization is not required.
2. Split the remote replication form the production center to the DR center.
The remote replication is split from the production center to the DR center and its Pair
Running Status is Split.
Step 2 Replicate data from the production center to the external storage system.
1. Create and activate a snapshot for the primary LUN of the production center.
The snapshot is created and activated.
2. Log in to the external storage system and create a full LUN copy. The source LUN of the
LUN copy is the snapshot for the storage system of the production center and the target
LUN is the LUN of the external storage system.
The full LUN copy is created and its Health Status is Normal.
3. Start the full LUN copy.
The full LUN copy is started and its Running Status is Copying. After the full LUN
copy is complete, its Running Status becomes Completed.
4. Delete the full LUN copy.
The full LUN copy is deleted.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
5. Log in to the storage system of the production center and deactivate and delete the
snapshot.
The snapshot is deactivated and deleted.
Step 3 Move the external storage system to the DR center.
Step 4 Recover data from the external storage system to the storage system of the DR center.
1. Cancel the write protection for the secondary LUN of the remote replication from the
production center to the DR center.
2. Set the property of the secondary LUN (LUN of the DR center) to write through.
NOTE
In developer mode, run the change lun lun_id=## write_policy=write_through command.

LUN copy is the LUN of the external storage system and the target LUN is the
secondary LUN of the remote replication. Then start the LUN copy.
The full LUN copy is created and started. After the full LUN copy is complete, its
Running Status becomes Completed.
NOTE
In developer mode, run the create lun_copy remote name=test local_role=source lun_id=##
remote_device_id=## remote_lun_id=## is_target_lun_check=no command.
Step 5 Start to reclaim differences in the data control list (DCL) for the secondary LUN of the DR
center.
NOTE
In developer mode, run the change remote_replication clear_difference operation=recycle command.
Step 6 Wait 5 minutes and then cancel the reclamation. If you fail to cancel the reclamation, retry 5
minutes later.
NOTE
In developer mode, run the change remote_replication clear_difference operation=unrecycle

command.
Step 7 Configure the write protection for the secondary LUN of the remote replication from the
production center to the DR center.
Step 8 Set the property of the secondary LUN (LUN of the DR center) to write back.
NOTE
In developer mode, run the change lun lun_id=## write_policy=write_back command.
Step 9 Start the remote replication form the production center to the DR center.
----End
A.3 Configuration Operation (Using the LUN Copy

Feature of the Production and DR Centers)
You can create a LUN copy on the storage system of the production center and DR center to
implement initial synchronization for a remote replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
l The production center and the DR center have network established, remote storage
systems configured, and the primary and secondary LUNs created.
l A LUN has been created on the external storage system. This LUN has the same capacity
as the primary and secondary LUN of the remote replication.
l The external storage system is in the production center and connected to the storage
system of the production center. The remote storage system has been configured in the
production center.
l The external storage system is a Huawei product.
l The production center supports the snapshot feature and both the production center and
the DR center support the LUN copy feature.
Procedure
Step 1 Configure the remote replication form the production center to the DR center.
1. Log in to the storage system of the production center and create a remote replication. The
primary LUN of the remote replication is the LUN of the production center and the
secondary LUN is the LUN of the DR center.
The remote replication is created from the production center to the DR center and its
Pair Health Status is Normal.
NOTE
When creating remote replication, select The primary and secondary LUNs have consistent
data and data synchronization is not required.
2. Split the remote replication form the production center to the DR center.
The remote replication is split from the production center to the DR center and its Pair
Running Status is Split.
Step 2 Replicate data from the production center to the external storage system.
1. Create and activate a snapshot for the primary LUN of the production center.
The snapshot is created and activated.
LUN copy is the snapshot for the storage system of the production center and the target
LUN is the LUN of the external storage system.
The full LUN copy is created and its Health Status is Normal.
3. Start the full LUN copy.
The full LUN copy is started and its Running Status is Copying. After the full LUN
copy is complete, its Running Status becomes Completed.
The full LUN copy is deleted.
5. Log in to the storage system of the production center and deactivate and delete the
snapshot.
The snapshot is deactivated and deleted.
Step 3 Move the external storage system to the DR center.
Step 4 Recover data from the external storage system to the storage system of the DR center.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
1. Log in to the storage system of the DR center and create a full LUN copy. The source
LUN of the LUN copy is the LUN of the external storage system and the target LUN is
the secondary LUN of the remote replication. Then start the LUN copy.
The full LUN copy is created and started. After the full LUN copy is complete, its
Running Status becomes Completed.
NOTE
Create this LUN copy in developer mode and use command parameter is_target_lun_check=no.
Ensure that the remote replication secondary LUN is in the Read-only state during LUN copy and
LUN copy configuration.
Step 5 Start the remote replication form the production center to the DR center.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block B How to Obtain Help
B How to Obtain Help
If a tough or critical problem persists in routine maintenance or troubleshooting, contact

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

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

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
B.1 Preparations for Contacting Huawei

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

You need to collect troubleshooting information before troubleshooting.
You need to collect the following information:
l Name and address of the customer
l Contact person and telephone number
l Time when the fault occurred
l Description of the fault phenomena
l Device type and software version
l Measures taken after the fault occurs and the related results
l Troubleshooting level and required solution deadline
B.1.2 Making Debugging Preparations

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

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

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

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
B.4 Ways to Contact Huawei

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

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block C Glossary
C Glossary
A
AC power The module that transfers the external AC power supply into the
module power supply for internal use.
Application A service processing node (a computer device) in the network.
server Application programs of data services are run on the application
server.
Asynchronous A kind of remote replication. When the data on the primary site is
remote updated, the data does not need to be updated on the mirroring site
replication synchronously to finish the update. In this way, performance is not
reduced due to data mirroring.
B
Backup A periodic operation performed on the data stored in the database for
the purposes of database recovery in case that the database is faulty.
The backup also refers to data synchronization between active and
standby boards.
Bandwidth A range of transmission frequencies that a transmission line or
channel can carry in a network. In fact, it is the difference between
the highest and lowest frequencies the transmission line or channel.
The greater the bandwidth, the faster the data transfer rate.
Baud rate The number of times per second the signal can change on a
transmission line. Commonly, the transmission line uses only two
signal states, making the baud rate equal to the number of bits per
second that can be transferred. The underlying transmission technique
may use some of the bandwidth, so it may not be the case that user
data transfers at the line's specified bit rate.
Bit error A computer that is connected to the serial port or management
network port of the storage system for maintenance.
Bit error rate The percentage of bits that have errors relative to the total number of
bits received in a transmission.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Bonding Bonding can bind multiple independent physical network ports into a
logical port, which ensures the high availability of server network
connections and improving network performance.
Boundary scan A test methodology that uses shift registers in the output connections
of integrated circuits. One IC often is connected to the next. A data
pattern is passed through the chain and the observed returned data
stream affected by the circuit conditions gives an indication of any
faults present. The system is defined under IEEE standard 1149.1 and
is also often known as JTAG (Joint Test Action Group).
Browser/Server An architecture that defines the roles of browser and server, where the
browser is the service request party and the server is the service
provider.
C
Cache hit ratio The ratio of directly accessed I/O from Cache to all the I/O operation
during the read operation.
Cache prefetch According to the operation in which data has been read or is being
strategy read, the required data is read from a disk into the cache in advance.
Captive Screw After the screw is loosened, screw caps and bolts are not disconnected
from the main body.
Cascading Connect the storage system to more disk enclosures through
connection cables, thus expanding the capacity of the storage system.
CHAP A method to periodically verify the identity of the peer using a 3-way
handshake. During the establishment of a link, the authenticator sends
a "challenge" message to the peer. The peer responds with a value
calculated using a "one-way hash" function. The authenticator checks
the response against its own calculation of the expected hash value. If
the values match, the authentication is acknowledged. CHAP
provides protection against playback attack.
Clone A snapshot technology. The source data is completely copied to
generate a data duplicate; therefore the duplicate needs the storage
space as the same size as the source data. It is also called clone. In the
VIS system, it is also called third-mirror break-off snapshot.
Cluster A mechanism adopted to improve the system performance. Several
devices of the same type form a cluster. The exterior of a cluster is
some like a kind of equipment. In the interior of a cluster, the nodes
share the load.
Coffer A technology for ensuring data security and integrity in a storage
system. It is used to store the mission-critical data of the system.
Coffer disk Disks that build up the coffer.
Command device A special LUN through which the host can send inband commands to
storage devices.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Constant prefetch A cache prefetch strategy. The size of the data to be prefetched is the
size as set. This strategy applies to the applications that require
reading data of a fixed size in a certain order. An example is the
streaming media demanded by multiple subscribers who use the same
bit rate.
Controller The core module that processes services in a storage system. It
contains physical components such as system-level CPUs and
memory.
Controller An enclosure that accommodates controllers and provides storage
enclosure services. It is the core component of a storage system, and generally
consists of components such as controllers, power supplies, and fans.
Copyback The process of copying the data from the hot spare disk back to the
previous disk when the faulty member disk is restored or replaced by
a new one.
Copying A state of pair. The state indicates that the source LUN data is being
synchronized to the target LUN.
D
Data compress A data reduction method. Data compression involves encoding
information using fewer bits than the original representation.
Data A specialized data compression technique for eliminating coarse-
deduplication grained redundant data, typically to improve storage utilization. In the
deduplication process, duplicate data is deleted, leaving only one
copy of the data to be stored, along with references to the unique copy
of data. Deduplication is able to reduce the required storage capacity
since only the unique data is stored.
Data flow A process that involves processing the data extracted from the source
system, such as filtering, integration, calculation, and summary,
finding and solving data inconsistency, and deleting invalid data so
that the processed data meets the requirements of the destination
system for the input data.
Data migration It is the process to cleanse and transform history data, and then load
them to the new system.
Data source A system, database, or file that can make BOs persistent. A data
source can be a database instance or a database user.
Data switch A data switch used for interconnections between controllers.
Dirty data The data that is stored temporarily on cache and has not been written
onto disks.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Disaster recovery A system deployment solution aiming at reducing loss in disasters. A

set of disaster recovery system that is the same as the production
system is deployed as a backup to store the production data when a
fault occurs in the production system. The applications are switched
over to the disaster recovery system before the production system
recovers. After the production system recovers, the applications are
switched back to the production system.
Disk array A set of disks from one or more commonly accessible disk
subsystem. These disks are combined and controlled by the control
software. The control software provides the storage capacity of these
disks for hosts as one or more virtual disks.
Disk Domain A combination of disks. A disk domain consists of the same type or
different types of disks. Disk domains are isolated from each other.
Therefore, services carried by different disk domains do not affect
each other in terms of performance and faults (if any).
Disk location Locate a hard disk, that is, determine the enclosure number and slot
number of the hard disk in the storage system.
Disk enclosure It consists of the following parts in redundancy: expansion module,
hard disk, power module, and fan module. System capacity can be
expanded by cascading multiple disk enclosures.
Disk utilization The percentage of used capacity in the total available capacity.
E
eDevLUN Logic space created by third-party storage systems.
(external device
LUN)
Engine Two controllers in one enclosure are called Engine.
Expansion Connecting a storage system to more disk enclosures through
connection cables, thus expanding the capacity of the storage system.
Expander module A component used for expanding.
F
Failover The automatic substitution of a functionally equivalent system
component for a failed one. The term failover is most often applied to
intelligent controllers connected to the same storage devices and host
computers. If one of the controllers fails, failover occurs, and the
survivor takes over its I/O load.
Field replaceable A unit that can function as a circuit board, part, or component of an
unit electronic device. It can be quickly and easily removed from a
personal computer or other electronic devices. If an FRU becomes
faulty, users can replace it with a new one instead of sending the
entire product or system for maintenance.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Firmware The programmable software part in a hardware component. A

firmware is a part of hardware, but is scalable as software.
Front-end host The port that connects the controller enclosure to the service side and
port transfers service data. There are three types of front-end host ports:
SAS, FC, and iSCSI.
G
Gateway The entrance node on another network.
Global system for The second-generation mobile networking standard defined by
mobile European Telecommunications Standards Institute (ETSI). It is aimed
communications at designing a standard for global mobile phone networks. The
standard allows a subscriber to use a phone globally. GSM consists of
three main parts: mobile switching subsystem (MSS), base station
subsystem (BSS), and mobile station (MS).
H
Hard disk A non-volatile storage device that stores digitally encoded data on
rapidly rotating platters with magnetic surfaces. Hard disks generally
offer more storage and quicker access to data than floppy disks do.
Hard disk tray The tray that bears the hard disk.
Hard quota The value to limit the space used in quota configuration. If the space
used arrives hard quota, file operation is not allowed to continue.
Heartbeat Heartbeats are the packets, requiring no acknowledgement,
transmitted between two devices. The device can judge the validity
status of the peer device. Heartbeat supports node communication,
fault diagnosis, and event triggering.
Hit ratio The ratio of directly accessed I/Os from cache to all I/Os.
Hot swap In a running system, inserting or removing a blade does not affect
normal running of the system.
I
I/O Data movement process between memory and peripheral devices in
the computer system. I/O is a collective name, indicating the
operations reading data into the memory and writing data to other
places from computer memory.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Inband Inband management means that the management control information

management of the network and the carrier service information of the user network
are transferred through the same logical channel. Inband management
enables users to manage storage arrays through commands.
Management commands are sent through service channels, that is, I/O
write and read channels. The advantages of inband management
include high speed, stable transfer, and no additional management
network ports required.
Initiator A system component that can initiate an I/O operation on an I/O bus
or on a network.
Intelligent A cache prefetch strategy. The system software calculates a proper
prefetch size of prefetched data. This strategy applies to a read application
involving a single bit stream or to the situations where you do not
know whether the data is read in a certain order. An example is
reading or writing a file.
Interface module interface module connects various types of front-end host port, such
as the front-end host ports of SAS, FC and iSCSI.
The interface module can be configured with one type of the
following host ports or expansion ports: 10Gb iSCSI, 8Gb FC, and
iSCSI host ports, or 4Gb FC and 6Gb SAS expansion ports.
L
Load balance A method of adjusting the system, application components and data to
averagely distribute the applied I/O or computing requests for
physical resources of the system.
Logical unit The entity is located inside the SCSI object, and can execute I/O
commands. After a SCSI I/O command is sent to an object, the logic
unit inside the object executes this command. Usually, each SCSI
physical disk has one logic unit. A tape drive and array controller may
have multiple logic units, which process different I/O commands.
Each logic unit inside an array controller corresponds to a virtual
disk.
Logical unit The SCSI identifier of the internal logical unit of a target.
number
LUN format The process of writing 0 bits in the data area on the logical drive and
generating related parity bits so that the logical drive can be in the
ready state.
LUN mapping The storage system maps LUNs to ASs so that the ASs can access the
storage reorganization.
LUN migration A method for the data in the LUN to migrate between different
physical storage space while ensuring data integrity and uninterrupted
operation host services.
LUN copy The function of copying the original LUN data to one or multiple
target LUNs.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
M
Maintenance The computer that is connected through a serial port or management
terminal network port and maintains the storage system.
Management An entity that provides a means to transmit and process the
network information related to network management.
Management The network port on the controller enclosure that is connected to the
network port maintenance terminal. It is provided for the remote maintenance
terminal.
N
Node A managed device in the network. For a device with a single frame,
one node stands for one device. For a device with multiple frames,
one node stands for one frame of the device.
O
Out-of-band A management mode used during out-of-band networking. In the out-
management of-band management mode, the management and control information
of the network and the bearer service information of the user network
are transmitted through different logical channels.
Original LUN The LUN where the original data of the copied LUNs is located.
Owning For a LUN, the user configures the owing controller, that is, specified
controller the created LUN to a certain controller. When the owning controller
of the LUN is invalid, another controller manages the LUN
automatically. When the owning controller of the LUN is restored, the
original controller manages the LUN again.
P
Power failure When the external power failure occurs, the AC PEM depends on the
protection battery for power supply, which ensures the integrity of the dirty data
in cache.
Pre-copy When the system monitors that a member disk in a RAID group is to
fail, the system copies the data on the disk to a hot spare disk in
advance. This technology is called pre-copy.
Primary storage The controller that plays a leading role in controlling the management
controller is the primary storage controller. It can perform relevant management
operations on the controller enclosure.
Primary/ A procedure during which the two controllers of the storage system
Secondary change their master/slave states.
switchover

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Prior controller For the application server LUN, prior controller means that the
working controller is the owner controller of the corresponding array
LUN.
Q
Quota tree A first-level directory of file system that can be managed with quota.
R
RAID level The application of different redundant types to a logical drive. A
RAID level improves the fault tolerance or performance of the logical
drive but reduces the available capacity of the logical drive. You must
specify a RAID level for each logical drive.
Reconstruction A function of the storage system. It refers to the process of restoring
the data saved in the faulty member disk in a storage pool.
Redundancy The scheme to add more than one channels, elements or parts that
have the same functions with the counterparts in the system or device
at a critical place. When a fault occurs, the system or device can work
well, and the reliability is then improved.
Remote A core technology for disaster recovery and a foundation that
replication implements remote data synchronization and disaster recovery. This
technology remotely maintains a set of data mirror through the remote
data connection function of the storage devices that are separated in
different places. Even when a disaster occurs, the data backup on the
remote storage device is not affected. Remote replication can be
divided into synchronous remote replication and asynchronous remote
replication by whether the host that requires mirrors needs the
confirmation information of the remote replication site.
Reverse The process of restoring data from the redundancy machine (RM)
synchronizing when the services of the production machine (PM) are recovering.
Route The path that network traffic takes from its source to its destination.
In a TCP/IP network, each IP packet is routed independently. Routes
can change dynamically.
S
Script A collection of data statements used to perform an operation.
Secondary (1) A controller that backs up service and management data of the
controller primary controller in a clustered system. When the primary controller
fails, the secondary controller is upgraded to the primary controller
and takes over the management and services of the controller
enclosure. (2) A controller that backs up the management data of the
primary controller in a block-level array. When the primary controller
fails, the secondary controller is upgraded to the primary controller
and takes over the management of the system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Serial port An input/output location (channel) that sends and receives data to and
from a computer's CPU or a communications device one bit at a time.
Serial ports are used for serial data communication and as interfaces
with some peripheral devices, such as mice and printers.
Service data Data which is saved in data disk. Service data is the data source for
computing check data in parity disk.
Service network The network port that is used to store services.
port
SFP optical A component that can make data conversion between optical signals
transceiver and electrical signals and that can receive and transfer data.
Simple network A network management protocol of TCP/IP. It enables remote users to
management view and modify the management information of a network element.
protocol This protocol ensures the transmission of management information
between any two points. The polling mechanism is adopted to provide
basic function sets. According to SNMP, agents, which can be
hardware as well as software, can monitor the activities of various
devices on the network and report these activities to the network
console workstation. Control information about each device is
maintained by a management information block.
Single point A type of failure. Data transmission over a network is stopped and
failure cannot be recovered automatically if a single point failure occurs. The
point can be an interface, a board, a device, or a link.
Small computer A set of standards for physically connecting and transferring data
system interface between computers and peripheral devices. SCSI is most commonly
used for hard disks and tape drives, but it can connect a wide range of
other devices, including scanners, and optical drive.
SmartTenancy A feature of Huawei storage system. With SmartTenancy, multiple
virtual storage systems can be created in one physical storage system,
which allows tenants to share the same storage system hardware
resource without affecting data security and privacy of each other.
This feature achieves more flexible, easy-to-manage and low-cost
shared storage in a multi-protocol unified storage architecture.
Snapshot A data backup technology through which a fully usable copy of a data
object can be quickly generated. The duplicate contains the image of
the data object at a point in time.
Snapshot copy A copy of the snapshot LUN, which is also a snapshot LUN.
Soft quota The value to alarm space usage in quota configuration. After used
space arrives this value, an alarm triggered; if space used from above
this value becomes lower than, the previous alarm eliminated.
Storage system An integrated system. It consists of the following parts: controller,
storage array, host bus adapter, physical connection between storage
units, and all control software.
Storage unit An abstract definition of backup storage media for storing backup
data. The storage unit is connected with actual storage media, used to
back up data.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Streaming media A transmission mode in which data is consumed (read, listened to, or
watched) while it is being sent.
Stripe The set of strips at corresponding locations of each member extent of
a disk array which uses striped data mapping. The strips in a stripe are
associated with each other in a way (e.g., relative extent block
addresses) that allows membership in the stripe to be quickly and
uniquely determined by a computational algorithm. Parity RAID uses
stripes to map virtual disk block addresses to member extent block
addresses.
Subnet A type of smaller networks that form a larger network according to a
rule, for example, according to different districts. This facilitates the
management of the large network.
Subnet mask The technique used by the IP protocol to determine which network
segment packets are destined for. The subnet mask is a binary pattern
that is stored in the device and is matched with the IP address.
Synchronous A kind of remote replication. When the data on the primary site is
remote updated, the data must be synchronously updated on the mirroring site
replication before the update is complete. In this way, the data that is stored on
both the primary and mirroring sites can be synchronized.
T
Target A system component that can receive SCSI I/O operation commands.
Target LUN The target for LUN copy.
Tenant A property of SmartTenancy, which represents a virtual storage
system in a physical one. The private and independent logical
resource of a tenant mainly includes disk domain space, LUN, file
system and ports. Tenants get complete storage services, but also
remain resource and network isolation with other tenants, which
avoids interference.
Thin provisioning A mechanism that offers on-demand allocation of storage space.
Thin LUN The thin LUN is a logic disk that can be accessed by hosts. The thin
LUN dynamically allocates storage resources from the thin pool
according to the actual capacity requirements of users.
Timing Snapshot To create snapshots periodically to continuously protect data.
Topology The logical layout where computer systems and network components
are interconnected with one another. The topological structure gives
the interconnection relationship among the components from the
viewpoint of communication, but the topological structure does not
specify the exact locations of components and the interconnection
mode.
Trap A type of SNMP message that indicates the occurrence of an event.
This type of message is transmitted to the received through UDP. The
transmission process is not completely reliable.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
U
User datagram A TCP/IP standard protocol that allows an application program on
protocol one device to send a datagram to an application program on another.
User Datagram Protocol (UDP) uses IP to deliver datagram. UDP
provides application programs with the unreliable connectionless
packet delivery service. There is a possibility that UDP messages will
be lost, duplicated, delayed, or delivered out of order. The destination
device does not confirm whether a data packet is received.
User interface The space in which users interact with a machine.
V
Variable prefetch A cache prefetch strategy. The size of the data to be prefetched is the
multiple for prefetching multiplied by the length of a read command.
This strategy applies to the applications that require reading data of
variable size in a certain order or to the situations where multiple
subscribers read data concurrently but no fixed prefetch size can be
set, because the amount of pre-read data cannot be judged. An
example is the streaming media demanded by multiple subscribers
who use different bit rates.
vStore A property of SmartTenancy. In Huawei SmartTenancy, a tenant is
called a vStore, which represents a virtual storage system.
W
Working The controller used by the array LUN to read and write a disk.
controller
Write back A caching technology in which the completion of a write request is
signaled as soon as the data is in cache, and actual writing to non-
volatile media occurs at a later time. Write back includes an inherent
risk that an application will take some action predicated on the write
completion signal, and a system failure before the data is written to
non-volatile media will cause media contents to be inconsistent with
that subsequent action. For this reason, good write back
implementations include mechanisms to preserve cache contents
across system failures (including power failures) and to flush the
cache at system restart time.
Write through A caching technology in which the completion of a write request is
not signaled until data is safely stored on non-volatile media. Write
performance with the write through technology is approximately that
of a non-cached system, but if the data written is also held in cache,
subsequent read performance may be dramatically improved.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Zone In the fiber channel, a collection of the N_Port or the NL_Port which
can communicate with each other in the optical network. Only the
N_Port or the NL_Port in the same partition can communicate with
each other through the optical network.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block D Acronyms and Abbreviations
D Acronyms and Abbreviations
C
CHAP Challenge Handshake Authentication Protocol
CLI Command Line Interface
F
FC Fiber Channel
G
GUI Graphical User Interface
H
HBA Host Bus Adapter
I
IP Internet Protocol
iSCSI Internet Small Computer Systems Interface
L
LUN Logical Unit Number
R
RAID Redundant Array of Independent Disks

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3 Storage System
Remote Replication Feature Guide for Block D Acronyms and Abbreviations
S
SAS Serial Attached SCSI
SSD Solid State Drive
U
UI User Interface
UTC Universal Time Coordinated


OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003 Remote Replication Feature Guide For Block 03

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003 Remote Replication Feature Guide For Block 03

Uploaded by

Copyright:

Available Formats

OceanStor 5300 V3&5500 V3&5600 V3&5800

V3&6800 V3 Storage System

Remote Replication Feature Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2015-12-10) Huawei Proprietary and Confidential i

About This Document

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

NOTE Calls attention to important information, best practices and

Issue 02 (2015-12-10) Huawei Proprietary and Confidential ii

Issue 02 (2015-12-10) Huawei Proprietary and Confidential iii

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

Issue 02 (2015-12-10) Huawei Proprietary and Confidential iv

4.4 Managing Remote Replications....................................................................................................................................86

B How to Obtain Help................................................................................................................. 159

Issue 02 (2015-12-10) Huawei Proprietary and Confidential v

B.1 Preparations for Contacting Huawei.......................................................................................................................... 160

Issue 02 (2015-12-10) Huawei Proprietary and Confidential vi

About This Chapter

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 1

The remote replication feature supports two replication modes:

Table 1-1 Purposes and benefits of the remote replication feature

Function of Remote Purpose Benefit

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 2

Function of Remote Purpose Benefit

Applicable Product Versions

Table 1-2 Applicable versions of primary storage system

OceanStor 5300 V3/5500 V3/5600 V3/5800 V3/6800 V300R003

Table 1-3 Applicable versions of secondary storage system

OceanStor 18500/18800/18800F V100R001C00SPC200 and later versions

OceanStor 5300 V3/5500 V3/5600 V300R001 and later versions

OceanStor S2600T/S5500T/S5600T/ V200R002C00SPC200 and later versions

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 3

a: 6900 V3 is no longer supported in V300R002 and later versions.

Applicable Software Versions

OceanStor BCManagera V100R005C00 and later versions

a: To obtain the BCManager software installation package, log in to http://

1.3 Working Principle

1.3.1 Related Concepts

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 4

Figure 1-1 Implementation of remote replication

Users can stop synchronization by

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 5

Table 1-4 Pair running status of a remote replication session

To be recovery If a remote replication session needs to be restored using a Manual

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 6

Writable Secondary LUN

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 7

1.3.2 Data Replication

Writing Process in Synchronous Remote Replication

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 8

Figure 1-2 Writing process in synchronous remote replication mode

Remote replication links

Primary Primary Secondary Secondary

4 Write I/O result

RM: Remote replication management module.

LOG: Records data write logs.

DCL: Data change log.

Issue 02 (2015-12-10) Huawei Proprietary and Confidential 9