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 BCManager 6.5.0 eReplication User Guide 02

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


This section introduces restrictions on deploying High Availability (HA) on eReplication and using HA.

Before deploying or using HA on eReplication, read content in Table 1-19 carefully.
Table 1-19  Restrictions on using HA



Deployment restrictions

  • HA can only be deployed on Linux operating systems in x86 architecture.
  • Multi-node HA is not supported. HA can only be deployed in active-standby mode and the only one standby node is supported.
  • Switchover cannot be performed on monitoring resources independently. The HA roles of the resources on the two nodes are switched as a whole and the floating IP address can access the resources on the active management node.
  • HA queries resource status by scheduled inspection. Therefore, the queried resource status is in real time.
  • Restrictions on file synchronization:
    • The system environments of the active and standby servers must be the same. Otherwise, the lib library version inconsistency may occur.
    • Only file synchronization of common directories, files and soft links is supported.
    • Incremental synchronization is not supported, that is, changed content cannot be independently synchronized. After a file is modified, content of the whole file will be synchronized.
    • To improve system performance and efficiency, the size and last modification time of files are used to check the file consistency between the active and standby servers are the same is the time and last modification time of a file, instead of the content. Therefore, the size and last modification time of files on the active and standby servers must be different when a file is generated.
  • The active and standby management nodes communicate with each other through heartbeat links. If a heartbeat link is disconnected, there may exist two active management nodes, resulting in data inconsistency. After arbitration, data of the active management node will be synchronized to the standby management node. However, data on the standby management node that is different from that on the active management node will be lost. To prevent faults of two active nodes, HA supports the configuration of floating IP addresses to avoid switchover after heartbeat link disconnection.

Configuration restrictions

If HA is deployed in active-standby mode, note the following:
  • The deployment environments of the two management nodes must be the same, including the operating system version and eReplication version.
  • The time of the active management node must be the same as that of the standby management node. You can change the management node time or configure the Network Time Protocol (NTP) service to ensure the time consistency. For details about how to configure the NTP service, see Configuring the Time Zone and the NTP Service (SUSE Linux).
  • A node name contains 1 to 39 characters. The characters can only include letters, digits, underscores (_), and hyphens (-). The local node name must be different from the peer node name.
  • The ports used by the local and peer heartbeat links and file synchronization links cannot be the same.
  • One to four groups of gateway IP addresses, heartbeat links, and file synchronization links can be configured.
  • Plan the network before configuring HA. When you configure the floating IP address of the active management node, the IP address you entered cannot be the local IP address. The floating IP address and port of the standby management node must be the same as that of the active management node but cannot be the local IP address. The floating IP addresses must be different from the gateway IP addresses.
  • Before configuring gateway IP addresses, ensure that the gateway server is accessible.
  • In private cloud scenarios, cloud platform quorum servers must be configured to replace quorum gateways.
  • In other scenarios, floating IP addresses and quorum gateways need to be configured to avoid faults of two HA active nodes.
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 14018

Downloads: 68

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