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

Reminder

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

upgrade

HyperReplication Feature Guide for Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5110F V5, 5300 V5, 5300F V5, 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, 5800F V5, 6800 V5, 6800F V5, 18500 V5, 18500F V5, 18800 V5, and 18800F V5. It describes the working principle and application scenarios of the HyperReplication feature (for block). Also, it explains how to configure and manage the feature.
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).
Central Backup and DR

Central Backup and DR

This example explains how to configure the remote replication feature to implement central backup and DR.

Requirement Analysis

This section analyzes the requirements of a carrier that implements central backup and DR using the remote replication feature and provides conclusions.

Requirement Source

A carrier has a service site at site A. At site A, there is an application server that serves user data management. Data generated by the application server is stored in an OceanStor storage system. The data and bandwidth of site A are as follows:

  • The amount of daily data changes is between 100 MB to 200 MB.
  • The total amount of data does not exceed 500 GB.
  • The current network bandwidth between the application server and the storage system is 2 Mbit/s.

Since the network is complete and the applications are running properly, the carrier prefers to keep the existing network. Figure 3-4 shows the existing network.

Figure 3-4 Diagram of the existing network

Table 3-11 and Table 3-12 describe the LUN mapping and IP address allocation on existing devices at site A.

Table 3-11 LUN mapping at site A

LUN Name

LUN Size

Mapping

LUN001

500 GB

Mapped to application server 1

Table 3-12 IP address allocation at site A

Port

IP Address

Subnet Mask

Gateway

Management network port

192.168.15.60

255.255.0.0

192.168.0.1

Front-end port P0 on controller A

172.16.19.30

255.255.0.0

172.16.0.1

Front-end port P0 on controller B

172.16.19.31

255.255.0.0

172.16.0.1

The carrier wants to protect service data at site A against natural disasters and quickly recover the service data when a disaster occurs. The specific requirements are as follows:

  • Data backup and DR

    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.

  • Quick service recovery

    Once a disaster happens, site B takes over services with an RTO not longer than 15 minutes.

  • Central data management

    After a new service site (site C) or more service sites are set up, data from all service sites is backed up to the backup site for central management, reducing deployment and maintenance costs.

  • 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 DR solution. Table 3-13 lists the criteria for implementing a remote DR solution.

Table 3-13 Criteria for implementing a remote DR solution

Factor to Be Considered

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

Data availability

Availability of data at the DR site is significant for data recovery. Therefore, data at the DR site must be available any time.

Service continuity

The DR site must be able to quickly take over services at the service site through a service switchover to protect service continuity.

Others

Other factors to be considered include cost as well as central data management and analysis.

The analysis is as follows:

  • 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 that is not adequate for the data change amount. Therefore, the data replication period must be shortened to reduce the amount of data transferred each time.

  • Host performance

    The carrier requires minimized impact of backup on host performance to ensure that host services run properly. Multiple service sites may locate in different places and are comparatively far from the backup site. Therefore, asynchronous remote replication is suitable for this case. Table 3-14 describes advantages of asynchronous remote replication.

Table 3-14 Advantages of asynchronous remote replication

Advantage

Description

Incremental data replication

Incremental data replication is implemented between the primary and secondary storage systems. Specifically, after the initial synchronization (full replication), only data changes are replicated from the service site to the backup site during each synchronization process. Since the amount of data replicated each time is small, synchronization is fast.

No host performance deterioration

Data replication is between storage systems, occupying no host resources, so it does not affect current services. The quality of service (QoS) does not decrease.

Quick service takeover

When a disaster occurs, remote replication pairs are interrupted between the service site and the backup site. The backup site quickly takes over services from the service site.

  • Data availability

    The carrier needs to analyze the backup data and requires that data at site A must be quickly recovered after a disaster. Therefore, data at the backup site must be available anytime.

  • 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, by setting Interval to 10 minutes to satisfy the RPO requirement.

  • Others

    Besides backup and DR, the carrier hopes backup data can be managed centrally and latest data at service sites must 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 analysis, the conclusions are as follows:

  • Choose the central backup and DR solution. Add an OceanStor storage system, an application server, a maintenance terminal, and an iSCSI switch to site B.
  • Use asynchronous remote replication for backup and DR.
  • Set up iSCSI connections between sites A and B.

Configuration Planning

This section describes how to plan the remote replication feature for central backup and DR. This section is organized into two parts: network planning and service planning.

Network Planning

Figure 3-5 shows a diagram of the planned network. As shown in the diagram, central backup and DR are implemented without changing the carrier's existing network.

Figure 3-5 Diagram of central backup and DR

To achieve data backup to the central backup site, iSCSI connections between site A and site B must be set up first, and then logical connections need to be established by adding a route and a target. Before setting up the connections, a detailed networking plan must be drawn.

Table 3-15 describes the IP address planning for site B.

Table 3-15 IP address planning for site B

Port

IP Address

Subnet Mask

Gateway

Management network port

192.168.19.10

255.255.0.0

192.168.0.1

Front-end port P0 on controller A

172.17.20.31

255.255.0.0

172.17.0.1

Front-end port P0 on controller B

172.17.20.32

255.255.0.0

172.17.0.1

Service Planning

Based on the conclusions of the requirement analysis, a central backup and DR solution can meet the requirements of the carrier. Figure 3-6 shows the configuration roadmap of the solution.

Figure 3-6 Configuration roadmap

Table 3-16 lists the configuration operations and planning items involved in the configuration example.

Table 3-16 Configuration operations and planning items

Configuration Roadmap

Major Operation and Purpose

Planning Item

Parameter

Planned Value

Enable the remote replication feature.

Check the license files at the primary and secondary sites.

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

None

None

None

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

NOTE:

When configuring an asynchronous remote replication pair, reserve certain space in the storage pool of the secondary storage system to ensure that sufficient space is provided for COW for host I/Os or data synchronization I/Os of the secondary storage system during remote replication.

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 5; 4 D+1P
  • 1 TB

Create a secondary LUN.

Storage pools cannot be identified by hosts. A 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
  • 500 GB
  • 1
  • StoragePool_BK

Set up a logical connection between sites A and B.

Configure front-end port IP addresses.

This step is fundamental for setting up a logical connection between the two storage systems.

IP addresses of front-end ports at site A and those at site B

  • IPv4 Address
  • Subnet Mask
  • Site A
    • 172.16.19.30
    • 255.255.0.0
  • Site B
    • 172.17.20.31
    • 255.255.0.0

Add a route.

Perform this step when the front-end port on the primary storage system and that on the secondary storage system use IP addresses in different network segments. If the front-end ports use IP addresses in the same network segment, skip this step.

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

  • Type
  • Destination address
  • Destination mask
  • Gateway
  • Site A
    • Network segment route
    • 172.17.0.0
    • 255.255.0.0
    • 172.16.0.1
  • Site B
    • Network segment route
    • 172.16.0.0
    • 255.255.0.0
    • 172.17.0.1

Add a remote device.

Set up a logical connection between the primary and secondary storage systems for remote data transmission.

NOTE:

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
  • CTE0.A
  • CTE0.R5.IOM0.P0
  • 172.17.20.31
  • Right usernamea
  • Right passworda

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

Create an asynchronous remote replication pair.

The created asynchronous remote replication pair is used to implement remote data replication.

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

  • Select Replication Model
  • Select Primary LUN
  • Secondary LUN
  • Rate
  • Recovery policy
  • Link Compression
  • Synchronization type
  • Interval
  • Asynchronous
  • LUN001
  • LUN_BK
  • Medium
  • Automatic
  • No compression
  • Timed wait after synchronization begins
  • 10 (minutes)

a: Account used for authentication of communication between remote devices.

  • If remote devices are OceanStor 18000 series V100R001C20, T series V200R002C20, or OceanStor V3 series V300R001C10 or later, you need to use a machine-machine account. The default username and password of the machine-machine account 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 the Command Reference of the corresponding product model.

  • 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 an earlier version of a remote device for authentication. Obtain the username and password of the super administrator or administrator account on the remote device.
NOTE:
  • 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 a device of the latest version. Otherwise the operation may fail.

Configuration Operations

After completing the network and service planning, configure the remote replication feature on the DeviceManager according to the planned items.

Prerequisites
  • The connection between the storage system and application server at each site is working properly.
  • The iSCSI connection between the primary storage system at site A and the secondary storage system at site B is working properly.
Precautions

The OceanStor 5000 V5 series is used as an example. For other product models, the operations are similar but the GUIs may be different. The actual GUI depends on the specific product model.

Procedure
  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 each storage system grants the permission for the remote replication feature.

    On the navigation bar of DeviceManager of each storage system, click Settings. Click License Management.

  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 DeviceManager, click Provisioning. In the Storage Configuration and Optimization area, click Disk Domain to create DiskDomain_BK.

    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.

      On the navigation bar of DeviceManager, click Provisioning. In the Storage Configuration and Optimization area, click Storage Pool to create StoragePool_BK.

    3. Create a secondary LUN in the storage pool.

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

      On the navigation bar of DeviceManager, click Provisioning. In the 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 are adding a secondary LUN.

  3. Set up a logical connection between sites A and B.

    1. Configure front-end port IP addresses.

      This step is fundamental for setting up a logical connection between the two storage systems. The following uses port CTE0.B.P2 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 front-end port at either site is the same.

      In the navigation tree, click Provisioning. Click Port, and click the front-end port whose IP address you want to change. Click Properties. In the Properties of Port dialog box, configure the IP address of the port.

    2. Add routes for iSCSI front-end ports of both the primary and secondary storage systems.

      Perform this step when the front-end port on the primary storage system and that on the secondary storage system use IP addresses in different network segments. If the front-end 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 front-end port. The procedure at site B is the same.

      After modifying front-end port IP addresses, in Ethernet Ports, select the front-end port for which you need to add routes. Click Route Management, and choose Add in the displayed dialog box to add route information.

    3. Add a remote device in the primary storage system at site A or the secondary storage system at site B.

      Add a remote device at one side to establish a 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 DeviceManager, click Data Protection and then Remote Device. Choose Add Remote Device to add a remote device following the Add Remote Device Wizard dialog box.

    4. Add an iSCSI link.

      Only one link is selected between the storage systems when a remote device is added. To ensure link redundancy, you must manually add links after the remote device is added.

      Select the added remote device and click Add Link. Set Link Type to iSCSI and then add desired links.

  4. Create an asynchronous remote replication pair.

    On the navigation bar of DeviceManager, click Data Protection and then Remote Replication. Choose Create to create RP_001 following the Create Remote Replication Wizard dialog box.

    The following shows the properties of the asynchronous remote replication pair.

Configuration Verification

After creating a remote replication pair, view the data status of the secondary LUN of the remote replication pair to check whether data replication from the primary LUN to the secondary LUN succeeded.

Prerequisites
  • The connection between the storage system and application server at site A and that at site B are normal.
  • Initial synchronization of asynchronous remote replication is complete.
Procedure
  1. Map the primary and secondary LUNs to 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 groups.
    2. Choose Provisioning > Mapping View. Select the mapping view of the host group to which the host belongs. Then add the newly created LUN group to this mapping view.
    NOTE:

    To check on a standby server whether data replication succeeds, you need to mount the secondary LUN to the standby server. Before mounting the secondary LUN, split the remote replication pair in which the secondary LUN resides and set Status of Secondary Resource Protection to Read/Write.

  2. Check whether data replication succeeded.

    1. Log in to the application server at the primary site and create file X.txt in the primary LUN. When Pair Running Status is Normal, go to the next step.
    2. Wait about 10 to 20 minutes. Log in to the standby server at the secondary site to check whether data file X.txt exists in the secondary LUN.
      • If yes, data replication succeeded.
      • If no, log in to the DeviceManager at the primary site, choose Data Protection > Remote Replication > Remote Replication Pair. Select the remote replication pair, and choose More > Synchronize to synchronize data manually.

  3. Check whether a primary/secondary switchover can be performed at the secondary site.

    1. Log in to DeviceManager at the secondary site. Choose Data Protection > Remote Replication > Remote Replication Pair and perform the following operations.
      1. Select the remote replication pair to be split and choose More > Split.
      2. Click Properties. Change Status of secondary resource protection to Read/Write to set the secondary LUN to readable and writable.
      3. Choose More > Primary/Secondary Switchover to switch the secondary LUN to the primary LUN.
    2. Log in to the standby server at the secondary site and create file Y.txt in the new primary LUN. Check whether the primary LUN is readable and writable.
      • If yes, a primary/secondary switchover can be performed at the secondary site.
      • If no, a primary/secondary switchover cannot be performed at the secondary site. Check whether an alarm about remote replication exists in DeviceManager at the primary and secondary sites.
        • If yes, solve the fault based on the alarm information and repeat the previous operations.
        • If no, contact Huawei technical support.

  4. Check whether data can be recovered.

    1. Log in to DeviceManager at the secondary site, choose Data Protection > Remote Replication > Remote Replication Pair, and perform the following operations.
      1. Select the remote replication pair for which you want to enable secondary resource protection and click Properties. Change Status of secondary resource protection to Read-only to set the secondary LUN to read-only.
      2. Select the remote replication pair to be synchronized. Choose More > Synchronize to perform the synchronization manually.
    2. After the synchronization is complete, log in to the application server at the primary site to check whether file Y.txt exists in the secondary LUN (after the primary/secondary switchover).
      • If yes, data can be recovered.
      • If no, data cannot be recovered. Check whether an alarm about remote replication exists in DeviceManager at the primary and secondary sites.
        • If yes, solve the fault based on the alarm information and repeat the previous operations.
        • If no, contact Huawei technical support.
    3. Switch services back to the primary site after the verification. Log in to DeviceManager at the primary site, choose Data Protection > Remote Replication > Remote Replication Pair, and perform the following operations.
      1. Select the remote replication pair to be split and choose More > Split.
      2. Select the remote replication pair for which you want to cancel secondary resource protection and click Properties. Change Status of secondary resource protection to Read/Write to set the secondary LUN to readable and writable.
      3. Select the remote replication pair for which you want to perform the switchover and choose More > Primary/Secondary Switchover.
      4. Select the remote replication pair for which you want to enable secondary resource protection and click Properties. Change Status of secondary resource protection to Read-only to set the secondary LUN to read-only.
      5. Select the remote replication pair to be synchronized. Choose More > Synchronize to perform the synchronization manually.

Download
Updated: 2019-07-11

Document ID: EDOC1000181492

Views: 51596

Downloads: 376

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