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.


FusionStorage V100R006C30 Block Storage Service Disaster Recovery Feature Guide 03

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).
Installing DR Nodes

Installing DR Nodes


DR nodes are used for data replication between sites, and therefore they are required for both local and remote sites. DR nodes can be deployed on either physical servers or VMs.



Requirements listed in System Requirements are met.
  • When the DR component is installed, the system automatically creates the replication account and the dr user group that are used to start and manage service processes. Do not manually create the replication account and the dr user group on the DR node. Otherwise, the DR cluster will fail to deploy, related replication processes cannot be started, and services related to HyperMetro and remote replication becomes unavailable.
  • If the DR nodes are deployed on VMs, the virtual network adapters need to be set to the physical network adapter passthrough or SR-IOV mode to guarantee the network performance and reliability of the DR nodes.


  • In physical deployment mode, the baseboard management controller (BMC) IP addresses of DR nodes have been obtained.
  • In virtual deployment mode, empty VMs that meet requirements listed in System Requirements have been created.


You have obtained the OS image file. For the OSs supported by the DR nodes, see System Requirements.


    Install the OS for the node.

    1. You can mount the OS image file on the server BMC page and install the required OS based on the environment. For details about the OS installation method, see the installation guide provided by the OS vendor.

      After the OS is installed, ensure that the available spaces of the following directories meet the requirements for running FusionStorage Block.

      Directory Minimum Available Space Description
      /opt 1 GB This directory provides sufficient space to ensure the proper running of FusionStorage Block.
      /tmp 1 GB The available space must be greater than 1 GB before the software is installed. After the software is installed, you can clear the directory.
      /var/log 2 GB You are advised to create an independent partition for storing logs, preventing a large number of logs from adversely affecting the proper running of the OS.

      Table 2-7 lists the space requirements for system partitions. If your system disk space is sufficient, you are advised to properly expand the size of each partition based on the actual condition.

      Table 2-7  Server OS partition
      Mount Point


      Minimum Partition Size (GB) Recommended Partition Size (GB)
      / System root directory 20 20
      swap Swap partition 20 20
      /usr System program directory 5 20
      /opt Third-party software directory 5 40
      /tmp Directory for saving temporary files generated by users or during program running 5 40
      /var Directory for saving changed data during system running 5 5
      /var/log Log partition

      Do not save other files in this partition. Otherwise, log space will be occupied, resulting in failure to save new logs and affecting fault location.

      5 60

    Install OS dependency packages.

    You can install the FusionStorage Agent (FSA) node only after installing the required OS dependency packages on the server.

    1. After the OS is installed, configure firewall rules for the OS by performing operations provided in FusionStorage Communication Matrix.

      If you do not have any special requirements for the firewall rules, disable the system firewall.

      Commands for disabling firewalls are as follows:

      SUSE Linux OSs:

      Stopping the firewall program:

      /etc/init.d/SuSEfirewall2_setup stop

      /etc/init.d/SuSEfirewall2_init stop

      Disabling automatic firewall startup upon OS startup:

      chkconfig SuSEfirewall2_setup off

      chkconfig SuSEfirewall2_init off

      For detailed operation guidelines, visit the official website of the OS provider.

    2. Decompress the FusionStorage Block software package.

      Obtain the installation script for the OS dependency packages from the install_lib folder:

      SUSE Linux OSs:

    3. (Optional) Modify the installation script of OS dependency packages to adapt with the installation.

      Perform this step if you have already configured the software repository onsite and do not need to obtain the dependency package software by mounting the OS image file.

      Modify the installation script as follows:

      SUSE Linux OSs: Edit the file as follows:

      • Change the REPO_NAME value to the name of the in-use software repository. You can query the software repository name by running the zypper lr command in the OS.
      • Change the ZYPPER_REPO_IS_EXIST value to 1.

    4. Upload the obtained installation script to a directory, for example, /tmp, on each server.
    5. On the remote control page, mount the OS image file.

      If the software repository has been configured onsite, do not obtain the software dependency packages by mounting the OS image file.

    6. Use PuTTY to log in to the first server.

      Ensure that the management IP address and username root are used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

    7. Switch to the directory containing the installation script and run the following command to install the dependency packages:


      In this command, specifies the installation script name.

      For example, run the sh command.

      The installation process takes about 20 minutes. You can install the dependency packages for multiple servers at the same time.

      • If the server does not support the dependency package installation by mounting the image file, perform the following operations to install the dependency packages:
        1. Copy the OS image file to the system.
        2. Run the sh Name of the image file command to install the dependency packages.

          In the preceding command, specifies the name of the installation script.

          Example command: sh /tmp/CentOS-7-x86_64-DVD-1611.iso

      • After the dependency packages are installed, the server is automatically restarted.

    8. Install the dependency packages for all servers. For details, see 7 to 8.
Updated: 2019-01-17

Document ID: EDOC1100044928

Views: 17660

Downloads: 34

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