No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


OceanStor 18500, 18800, and 18800F Storage System V100R001C30 Remote Replication Feature Guide 09

This document describes the remote replication feature, in terms of the implementation principle, application scenario, configuration process, and reference information.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuration Planning

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.
Figure 2-2  Diagram of central backup and disaster recovery

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


IP Address

Subnet Mask


Management network port

Host port P0 on controller 0

Host port P0 on controller 1

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.
Figure 2-3  Configuration roadmap

Table 2-6 lists the configuration operations and planning items involved in the configuration example.
Table 2-6  Configuration operations and planning items

Configuration Roadmap

Major Operation and Purpose

Planning Item


Planned Value

Enable the remote replication feature

  • Check the license file.
  • Check the license file to ensure that it grants the permission to use the remote replication feature.




Create a secondary LUN in the storage system at site B.

  • Create a disk domain.
  • Before creating a storage pool, a disk domain needs to be created. Because all the disks used to create a storage pool are in the disk domain.

Disk domain's name and disk type

  • Name
  • Disk Type
  • DiskDomain_BK
  • Performance Tier (SAS)
  • Create a storage pool.
  • This step is fundamental for subsequent storage space configuration. A storage pool is a container, in which multiple LUNs can be created.

Storage pool parameters and available disk domains for the storage system at site B

  • Name
  • Disk Domain
  • RAID policy
  • Capacity
  • StoragePool_BK
  • DiskDomain_BK
  • RAID 6;4D+2P
  • 1TB
  • Create a secondary LUN.
  • Storage pools 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.

Information about the secondary LUN in the storage system at site B

  • Name
  • Capacity
  • Quantity
  • Owning Storage Pool
  • LUN_BK
  • 500GB
  • 1
  • StoragePool_BK

Set up a logical connection between sites A and B.

  • Configure host port IP addresses.
  • This step is fundamental for setting up a logical connection between the two storage systems.

IP addresses of host port at site A and that at site B

  • IPv4 Address
  • Subnet Mask
  • Site A
  • Site B
  • Add a route.
  • 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.

Information on the route list of site A and that of site B

  • Type
  • Destination address
  • Destination mask
  • Gateway
  • Site A
    • Network segment route
  • Site B
    • Network segment route
  • Add a remote device.
  • Add a remote device for data transmission.

You only need to perform this step on either storage system.

Remote device information of the storage system at site A or site B

  • Link type
  • Controller
  • Port
  • IP address
  • Username
  • Password
  • iSCSI
  • A
  • A1.P0
  • The right user namea
  • The right passworda

Create an asynchronous remote replication session in the primary storage system at site A.

  • Create an asynchronous remote replication session.
  • The created asynchronous remote replication session is used to implement remote data replication.

Basic information and the primary LUN of the remote replication session in the primary storage system at site A

  • Select Replication Model
  • Select Primary LUN
  • Secondary LUN
  • Rate
  • Recovery policy
  • Synchronization type
  • Interval
  • Asynchronous
  • LUN001
  • LUN_BK
  • Medium
  • Automatic
  • Timed wait when synchronization begins
  • 10 (minutes)
a:The user used for communication authentication between remote devices.
  • 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 username is mm_user, and the default password is mm_user@storage.
  • 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.
  • Keep the default values of the parameters that are not mentioned in this table.
  • 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.
Updated: 2019-01-28

Document ID: EDOC1000077758

Views: 9899

Downloads: 65

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next