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

OceanStor 9000 V300R006C00 File System Feature Guide 12

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).
Configuring Remote Replication

Configuring Remote Replication

This section describes how to use InfoReplicator to configure remote replication.

Configuration Process

This section describes how to configure InfoReplicator.

Figure 6-26 shows the configuration process for InfoReplicator.
Figure 6-26  Configuration process for InfoReplicator
Table 6-11 describes the configuration steps.
Table 6-11  Configuration steps for InfoReplicator
No. Step Description
1 Check the license file. InfoReplicator is a value-added feature of the OceanStor 9000. You must purchase and import the feature license into both the primary and secondary OceanStor 9000 storage systems.
2 Check the remote replication network. Check the network communication between the primary and secondary storage systems.
3 Create local authentication users. (Optional) Create local authentication users with the same UID on the primary and secondary OceanStor 9000 storage systems. This step is required when a Windows client uses a local authentication user to access a directory.
Create domain users. (Optional) Create domain users on the domain server. This step is required when a domain user is used to access a directory. Ensure that the primary and secondary OceanStor 9000 storage systems are in the same domain.
4 Create directories. (Optional) Create primary and secondary directories for data replication. Skip this step when primary and secondary directories already exist.
5 Configure the replication zone. Configure the node range in the default replication zone.
6 Create the replication channel. Create a replication channel to establish replication links between the primary and secondary ends.
7 Create replication pairs. Follow wizard instructions to create replication pairs to establish replication relationship.
8 Start the initial synchronization. Manually start the initial synchronization for a newly created pair.

Checking the License File

InfoReplicator is a value-added feature of the OceanStor 9000. InfoReplicator is available only after its license is imported and activated.

Prerequisites

You have obtained the password of account admin for logging in to DeviceManager of each OceanStor 9000 storage system.

Procedure

  1. Log in to DeviceManager.
  2. Choose Settings > License Management > Active License.
  3. Check whether the license file of InfoReplicator exists.

    • If yes, go to 5.
    • If no, go to 4.

  4. Import and activate the license file of InfoReplicator.

    For details, see (Optional) Applying for and Importing a License in the OceanStor 9000 Software Installation Guide.

  5. Perform 1 to 3 on each storage system to check the license file of InfoReplicator. Ensure that the license file is imported and activated on all storage systems.

Checking the Replication Network

Data can be replicated between the source and destination storage systems only when the network communication is normal between the two systems. When configuring remote replication, first configure the replication network to ensure that the source and destination can communicate correctly with each other.

Prerequisites

  • The source and destination OceanStor 9000 storage systems are working correctly.
  • You have obtained the management IP address (IP1) of either OceanStor 9000 storage system and the front-end service IP address (IP2) of any node of the other storage system.

Context

InfoReplicator resolves the remote data backup problem between two OceanStor 9000 storage systems. However, data transmitted between the two storage systems are not encrypted, posing security risks. You are advised to deploy virtual private network (VPN) devices when enabling InfoReplicator to ensure data transmission security. Also, you are advised to deploy physical firewalls to defend against distributed denial of service (DDoS) attacks that interrupt communication by occupying system resources in a short time.

Two OceanStor 9000 storage systems replicate data between each other over a front-end service network. The two storage systems can communicate with each other correctly only when the VPN or firewall devices deployed between them are correctly configured. For details about how to configure the VPN and firewall devices, see related device documentation. This section describes how to check the replication network when VPN or firewall devices are not configured.

Procedure

  1. Use IP1 to log in to the storage system as user omuser through PuTTY.
  2. Run the ping IP2 command to the communication between the two storage systems.

    For example, run the ping 192.168.0.10 command.

    Check whether the two storage systems can ping each other.
    • If yes, the replication network is normal. No further action is required.
    • If no, contact the network administrator to reset the communication network between the two storage systems.

Configuring a Replication Zone

For the replication zone of a cluster, you can select a subnet, and configure the IP addresses of replication nodes within the subnet to control the number of nodes involved in the replication, so that you can decrease the impact of the replication task on other services.

Context

  • The cluster only has one replication zone by default. You can only modify it, neither create it nor delete it.
  • Both local cluster and remote cluster must configure the replication zone to implement remote replication.
  • It is recommended that the number of nodes in both replication zones of local cluster and remote cluster are the same. If the number of nodes differs a lot, it may cause replication performance degraded.

Procedure

  1. Log in to DeviceManager.
  2. Choose Data Protection > Remote Replication > Replication Zone.
  3. Select the replication zone that you want to modify and click Properties.

    The Properties of Replication Zone dialog box is displayed.

  4. Optional: In Name, modify the name of replication zone.

    NOTE:
    • The length range is 1 to 31 characters.
    • Contains only letters, digits, underscore (_), hyphens (-), and periods (.).

  5. Configure the nodes that participate in remote replication.
    1. On the General tab page, click Browse. In the wizard that is displayed, select a subnet.

      NOTE:
      • Selecting a subnet is to determine the node range that participate in remote replication. The actual nodes that participate in remote replication is determined by 5.b and 5.c.
      • The system default subnet default contains all nodes.
      • If you want to create a new subnet, see Configuring and Managing InfoEqualizer chapter.
      • If the selected subnet is deleted or the nodes within the subnet are changed, please re-select the subnet or re-configure the nodes that participate in remote replication.

    2. On the Include IP Address Segment tab page, click Add to configure the IP address segment of nodes within the subnet that need to participate in the remote replication.

    3. Optional: On the Excluded IP Address tab page, click Add to configure the IP addresses of node within the subnet that do not need to participate in the remote replication.

      NOTE:
      • Ensure the IP addresses configured in 5.b and 5.c are within the subnet selected and the IP address must be the static service IP address of the node in the local cluster. Otherwise, these IP addresses are invalid.

      • If you do not configure any IP address in 5.b, it will cause replication service unavailable between clusters.

  6. Click OK.

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

  7. Click Close.

    NOTE:
    Select the replication zone and in the bottom of the UI, check whether the IP address of the node matches the one you configure. If it is a match, you have successfully modified the replication zone.

  8. Log in to the remote cluster, and repeat the steps above to configure the replication zone for remote cluster.

Creating a Replication Channel

You can establish replication links between the local and remote clusters by creating a replication channel.

Prerequisites

  • The name of the replication zone of the remote cluster has been obtained.
  • The static service IP address of any node in the remote cluster has been obtained.
  • Both local and remote replication zones have configured the nodes that participate in remote replication.

Procedure

  1. Log in to DeviceManager.
  2. Choose Data Protection > Remote Replication > Replication Channel.
  3. Click Create.

    The Create Replication Channel dialog box is displayed.

  4. Configure the replication channel. Table 6-12 explains the related parameters.

    Table 6-12  Replication channel parameters

    Parameter

    Description

    Example Value

    Name

    Indicates the name of a replication channel.

    [Value range]
    • The name contains 1 to 31 characters.
    • The name contains letters, digits, underscores (_), periods (.), and hyphens (-).

    [Example]

    replication_channel

    Remote Replication Zone

    Indicates the name of the replication zone of the remote cluster.

    [Value range]
    • The name contains 1 to 31 characters.
    • The name contains letters, digits, underscores (_), periods (.), and hyphens (-).

    [Example]

    zone1

    Channel Authentication IP Address

    Indicates the static service IP address of any node in the remote cluster. This IP address is used to establish connections between replication zones. The IP address can be an IPv4 or IPv6 address.
    NOTE:
    • The node can be one that is not in the replication zone of the remote cluster.
    • You can view the static service IP address of the node by logging into the remote cluster and selecting Settings > Cluster Settings > InfoEqualizer > Node Management.

    [Example]

    192.168.1.100

    Channel Authentication Password

    Indicates the password of the machine-machine account for replication link authentication.
    NOTE:

    You can use the CLI to change this password. When any replication link is interrupted after the password is changed, you need to manually enter the new password and ensure that the same password is entered at the cluster-sender and cluster receiver ends of the replication channel.

    For details about the default passwords of machine-machine account (account name is _machine_user), see the account list in the Security Maintenance document.

    Bandwidth

    You can click Set bandwidth to control the maximum amount of data replicated per second by each node in the replication zone to the remote cluster.
    NOTE:
    • This parameter applies only to nodes in the replication zone of the local cluster.
    • The value of the bandwidth multiplied with the number of nodes in the replication zone must be smaller than the actual network bandwidth, so that the other services of the system will not be impacted.

    [Value range]

    The bandwidth must be no less than 2 Mbit/s.

    [Default value]

    1 Gbit/s

  5. Click OK.

Creating a Remote Replication Pair

A remote replication pair between the local and remote directories enables data in the local directory to be backed up in the remote cluster. If a disaster occurs, you can use the backup data to recover the data on the local cluster or start services on the remote cluster. Remote replication ensures less data loss and shorter service interruption.

Prerequisites

  • A replication channel has been created for the local and remote clusters and communicate normally.
  • The local and remote clusters support the remote replication function.
  • The remote directory must be empty.
  • If the WORM feature is configured for the local and remote directories, the WORM properties must be the same.
  • Snapshot directory or directory that has manually created snapshots cannot be configured as the primary or secondary directory in a remote replication pair.
Precaution
  • One primary directory can replicate data to 3 different secondary directories at most.
  • After the remote replication pair created successfully, ensure the primary directory, secondary directory and their parent directories are not deleted, renamed or moved, or it may cause the remote replication abnormal.

Procedure

  1. Log in to DeviceManager.
  2. Choose Data Protection > Remote Replication.
  3. Click Create in the Remote Replication Pair tab.

    The Create Remote Replication Pair Wizard dialog box is displayed.

  4. Configure the remote replication pair name and select a local directory as the primary directory, and click Next.

    Table 6-13 describes the related parameters.

    Table 6-13  Parameters for primary directory

    Parameter

    Description

    Value

    Name

    Name of the remote replication pair.

    [Value range]
    • The name contains 1 to 39 characters.
    • The name contains letters, digits, underscores (_), periods (.), and hyphens (-).

    [Example]

    Remote_replication_001

    Local Directory

    A directory in the local cluster. This directory as the primary directory becomes the data source in the remote replication pair.

    NOTE:
    • The local directory does not support nesting remote replication pair. That is, if remote replication pair is configured for the directory, remote replication pair cannot be configured for its parent directory or subdirectory.
    • One directory supports only three remote replications.

    [Value range]

    The absolute path of the directory contains a maximum of 511 characters.

    [Example]

    /local01

  5. Select a remote replication zone channel to specify the remote cluster and configure a directory in this cluster as the secondary directory. Click Next.

    Table 6-14 describes the related parameters.

    Table 6-14  Parameters for secondary directory

    Parameter

    Description

    Value

    Remote Replication Zone Channel

    Specify the remoter cluster by selecting a remote replication zone channel.

    [Example]

    replication_channel

    Remote Directory

    A directory in the remote cluster to save data from primary directory. This directory as the secondary directory becomes the data receiver in the remote replication pair.

    NOTE:
    • Clear information in the remote directory before the configuration. Otherwise, the configuration fails.
    • The remote directory does not support nesting remote replication pair. That is, if remote replication pair is configured for the directory, remote replication pair cannot be configured for its parent directory or subdirectory.
    • One directory supports only one remote replication.

    [Value range]

    The absolute path of the directory contains a maximum of 511 characters.

    [Example]

    /remote01

  6. Configure a synchronization policy. Click Next.

    Table 6-15 describes the related parameters.

    Table 6-15  Parameters for synchronization policy

    Parameter

    Description

    Value

    Speed

    Remote replication rate.
    • Low: This rate applies to scenarios where the service load is heavy.
    • Medium: This rate applies to scenarios where the service load is relatively heavy.
    • High: This rate applies to scenarios where the service load is relatively light.
    • Highest: This rate applies to scenarios where the service load is light.

    [Default value]

    Medium

    Recovery Policy

    Whether the system automatically synchronizes data after a remote replication fault is rectified.

    • Automatic: The system automatically synchronizes data after the pair recovers.
    • Manual: The data synchronization operation must be performed manually after the pair recovers.

    [Default value]

    Automatic

    Synchronization Method

    Synchronization method of the primary and secondary directories.

    • Manual: You need to manually synchronize data from the primary directory to the secondary directory.
    • Timed wait when synchronization begins: When a data synchronization operation starts, the system waits for the duration specified in Interval. When the duration is reached, the system automatically synchronizes data from the primary directory to the secondary directory again.
      NOTE:

      If the latest synchronization is still being executed after the time specified in Interval has elapsed, the data synchronization is not triggered.

    • Timed wait when synchronization ends: When a data synchronization operation is complete, the system waits for the duration specified in Interval. When the duration is reached, the system automatically synchronizes data from the primary directory to the secondary directory again.

    [Default value]

    Manual

    Interval (minutes)

    Time spent waiting of the two synchronization methods, Timed wait when synchronization begins or Timed wait when synchronization ends.

    [Value range]

    An integer ranging from 15 to 1440 (inclusive).

    [Default value]

    15

    Enable Secondary Directory Snapshot Retention Period

    After this function is enabled, the cluster where secondary directory resides automatically retains the consistency snapshots in a specific period of time. The snapshots can be used as data copies at different time points. The snapshots that are beyond the specified retention period are automatically deleted.

    Once this function is enabled, you must specify the snapshot retention period.

    [Default value]

    Disabled

    Snapshot Retention Period

    The retention period to retain the secondary directory snapshot.

    [Value range]

    No smaller than 1 day and no greater than 360 days, or 51 weeks, or 12 months.

    [Default value]

    1 Day

    NOTE:

    One month equals to 30 days.

  7. Confirm the remote replication creation.
    1. Confirm information about the remote replication creation and click Finish.

      The Warning dialog box is displayed.

    2. Carefully read the contents of the dialog box, select I have read and understand the consequences associated with performing this operation. and click OK.
    3. On the Execution Result page, verify that the remote replication pair is created successfully.
    4. Click Close.

Follow-up Procedure

After the remote replication pair is created, you must start initial synchronization manually.

Synchronizing/Splitting a Remote Replication Pair

You can synchronize the remote replication pair to replicate data to secondary directory. And you can pause the replication by splitting the remote replication pair.

Prerequisites

  • The remote replication Pair Health Status is Normal.
  • You can synchronize a remote replication pair only when the value of remote replication pair Secondary Directory Write Protection is Read-only.
  • Determine whether a remote replication can be synchronized or split based on remote replication Pair Running Status. Table 6-16 lists status requirements for synchronizing or splitting a remote replication.
    Table 6-16  Status requirements for synchronizing/splitting a remote replication

    Pair Running Status

    Synchronization

    Split

    Normal

    Synchronizing

    ×

    Split

    ×

    Interrupted

    ×

    To be recovered

    Invalid

    ×

    ×

    √: Able to operate.

    ×: Unable to operate.

Context

  • After creating a remote replication pair, you must manually start synchronization between the directories in the replication pair. This is called initial synchronization which is also known as full synchronization that replicates all data from the primary directory to the secondary directory.
  • Full synchronization replicates all data from primary directory to secondary directory. Full synchronization is bandwidth- and time-consuming, degrading system performance. You are advised to start initial synchronization when the service is not busy.
  • Every synchronization after the initial synchronization completes is incremental synchronization. Incremental synchronization only replicate added, modified and deleted data, therefore it requires a small amount of data to be synchronized each time, so less bandwidth and time are consumed, posing a modest impact on system performance.
  • If you split a replication pair when the pair is in initial synchronization, the data replication will be suspended and the data in the secondary directory is incomplete. When you resume the synchronization for the replication pair, data continues to be replicated. This process is called resumable data transfer.
  • A maximum of five replication pairs can synchronize data at the same time, and other pairs cannot start synchronization. Wait until at least one of five synchronizing pairs completes, other remote replication pairs will start synchronization.

Procedure

  • Synchronize a remote replication pair.
    1. Log in to DeviceManager.
    2. Choose Data Protection > Remote Replication.
    3. In the remote replication pair list, select the remote replication pair that you want to synchronize.
    4. Click Synchronize to synchronize the primary directory data to secondary directory.

      The remote replication Pair Running Status changes to Synchronizing.

  • Split a remote replication pair.
    1. Log in to DeviceManager.
    2. Choose Data Protection > Remote Replication.
    3. In the remote replication pair list, select the remote replication pair that you want to split.
    4. Click More > Split to pause the primary directory data synchronization to secondary directory.

      The Danger dialog box is displayed.

    5. Confirm the information in the dialog box and select I have read and understand the consequences associated with performing this operation..
    6. Click OK.

      The Success dialog box is displayed indicating that the operation succeeded. The remote replication Pair Running Status changes to Split.

    7. Click OK. The remote replication management page is displayed.

Follow-up Procedure

Once the synchronization completes successfully, the secondary directory creates a consistency snapshot for data consistency verification. You can determine whether the synchronization is successful by checking the time when the snapshot is created or whether the pair Data Status is Consistent.

Translation
Download
Updated: 2019-06-27

Document ID: EDOC1000122519

Views: 79927

Downloads: 147

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