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).
How Is Load Balancing Implemented for Remote Replication?

How Is Load Balancing Implemented for Remote Replication?

Question

How is load balancing implemented for remote replication?

Answer

  • Load balancing within a controller is enabled by default. Users cannot modify it manually.

    If there are multiple usable links on a controller, the LEAST_QUEUE algorithm is used for path selection.

  • Load balancing between controllers is enabled by default. Users can modify it manually by performing the following operations.
    1. Run change user_mode current_mode user_mode=developer to switch the user view to the developer view.
    2. Run change private_device proportion enable=? to enable or disable load balancing between controllers.
      • change private_device proportion enable=yes enables load balancing between controllers.
      • change private_device proportion enable=no disables load balancing between controllers.
NOTE:
  • For details about the commands, see product-specific Advanced O&M Command Reference.
  • Load balancing between controllers is applicable only to asynchronous remote replication.

The following explains load balancing within a controller and load balancing between controllers.

  • Load balancing within a controller: On the sending end, all the replication links that belong to the same controller have almost the same transmission bandwidth.

    Example: Assume that a remote replication relationship is set up to copy data from array A (local) to array B (remote) and the total transmission bandwidth is 200 MB/s. Controller A on array A has two replication links, link 0 and link 1.

    • If load balancing within a controller is enabled, the bandwidth of both link 0 and link 1 is 100 MB/s.
    • If load balancing within a controller is disabled, the bandwidth of link 0 is 200 MB/s and the bandwidth of link 1 is 0 MB/s.
  • Load balancing between controllers: If the bandwidth usage of the source controller on the sending end exceeds 50% of the total bandwidth, services are switched over to other controllers for load balancing.

    Example: Assume that a remote replication relationship is set up to copy data from array A (local) to array B (remote) and the total transmission bandwidth is 200 MB/s. Controller A on array A has one replication link, link 0, and controller B has one replication link, link 256.

    • If load balancing between controllers is enabled, the bandwidth of both link 0 and link 256 is 100 MB/s.
    • If load balancing between controllers is disabled, the link under the working controller for remote replication occupies the entire bandwidth 200 MB/s. If both controllers are working controllers, services of each controller are carried by its own link.
Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181492

Views: 50982

Downloads: 375

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