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

Configuration Operations

This section describes how to configure InfoReplicator in a one-to-one scenario according to your planning.

Prerequisites

  • Basic service configuration such as system initialization has been completed at the primary and secondary sites.
  • IP addresses have been planned at the primary and secondary sites.
  • The replication channel authentication passwords have been obtained at the primary and secondary sites.
  • The account and password for logging in to the nodes operating systems have been obtained at the primary and secondary sites. The default account is omuser.

Context

The process of configuring InfoReplicator includes checking the environment, creating directories and users, and creating remote replication. Figure 6-21 shows the flowchart.

If the source and destination directories (primary and secondary directories) and authentication users of a remote replication session already exist, there is no need for you to create extra directories and users. In this example, the customer deploys the OceanStor 9000 for the first time and therefore needs to create directories. The customer uses local authentication, so you need to ensure that the local authentication user IDs are the same in the source and destination; otherwise, the roles of the source and destination directories cannot be switched.

Figure 6-21  Configuration process

Procedure

  1. Check the license file.

    InfoReplicator is a value-added feature. Before configuring this feature, you must ensure that the license file of the source and destination storage systems grant the permission to use InfoReplicator.

    Log in to DeviceManager of each storage system. Choose Settings > License Management > Active License. Check whether the activated license file grants the permission to use InfoReplicator. If the license file does not grant the permission, follow the displayed instructions to import and activate the license file.

    Figure 6-22  Checking the license file

  2. Check the remote replication network.

    Data can be replicated only when the network communication is normal between the two data centers. If firewalls or VPN devices are deployed between the two data centers, ensure that the configuration of the firewalls or VPN devices does not hinder the data center communication.

    When no firewalls or VPN devices are configured, use PuTTY and the management IP address of the OceanStor 9000 in a data center in to an OceanStor 9000 node as user omuser. Then run the ping command to ping any node of the OceanStor 9000 in the other data center. Check whether the node can be pinged. If the node cannot be pinged, contact the administrator to configure a network route between the data centers.

  3. Create local authentication users.

    In this example, the customer uses the local authentication. The local authentication users accessing the source and destination directories in both data centers must have the same IDs; otherwise, the roles of the source and destination directories cannot be switched. Ensure that the IDs of local authentication users are the same.

    In the CLI of a node, run the create local user command to create local authentication users. For details, see Allocating an ID to a Local Authentication User or User Group Being Created.

  4. Create primary and secondary directories (source and destination directories).

    NOTE:
    • The directory for which you want to create a quota must be empty.
    • The information about directory quotas and statistics cannot be remotely replicated from the source directory to the destination directory. To reduce the failover time, you are advised to configure InfoAllocator properties for the destination directory before creating pairs. Ensure that the properties are the same as those configured for the destination directory.
    • You cannot modify the quota for the destination directory in write protection state. The quota can be modified after you disable write protection for the directory.
    • The quota of the source directory can be modified because this directory is not in write protection state.

    In this example, the customer deploys the OceanStor 9000 for the first time and therefore needs to create the source and destination directories for replication.

    Log in to DeviceManager in data center D. Choose Provisioning > Create Directory. Create directories /Bill, /Media, and /AppLog as source directories. Ensure that local authentication users created in 3 have the read and write permission for these directories.

    Use the same method to create destination directories /Bill, /Media, and /AppLog on the OceanStor 9000 in data center Y. Ensure that the same strips and InfoAllocator attributes are configured for the source and destination directories.

  5. Configure the default replication zone.

    The default replication zone does not contain any system nodes. If all nodes participate in remote replication, add the static front-end IP addresses of all nodes to the replication zone.

    Log in to DeviceManager in data center D and data center Y. Choose Data Protection > Remote Replication > Replication Zone. Select the default replication zone and click Properties. In the dialog box that is displayed, add the static front-end IP addresses of all nodes.

    On the General tab page, selecting a subnet is to determine the node range that participates in remote replication. To specify the actual nodes that participate in remote replication, you should configure parameters on the Include IP Address Segment and Excluded IP Address tab pages. Otherwise, the following actions may not be performed successfully.

    Figure 6-23  Configuring the replication zone-1

    Figure 6-24  Configuring the replication zone-2

  6. Create the replication channel.

    Create a replication channel for the nodes in the default replication zone to establish a logical data transmission link.

    Log in to DeviceManager in data center D. Choose Data Protection > Remote Replication > Replication Channel. Create replication channel Channel_01.

    Figure 6-25  Creating a replication channel

  7. Create replication pairs.

    Create three replication pairs for the three types of services in data center D and synchronize the pair information to data center Y.

    Log in to DeviceManager in data center. Choose Data Protection > Remote Replication > Remote Replication Pair. Click Create. In the Create Remote Replication Pair Wizard page that is displayed, follow the wizard instruction to create replication pairs.

    For details about how to configure parameters, see Configuration Planning.

Translation
Download
Updated: 2019-06-27

Document ID: EDOC1000122519

Views: 69975

Downloads: 145

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