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 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).
Configuring a Deployment Mode

Configuring a Deployment Mode

After installing the eReplication Server, you can change the current deployment mode as needed.

Prerequisites
  • A cross-platform remote access tool, such as PuTTY, has been obtained.
  • You have obtained the passwords of users root and DRManager of the Linux operating system on the eReplication Server whose deployment mode is to be configured.
  • Observe the following restrictions when changing the current deployment mode to HA:
    • If you deploy the local server as the active (standby) server, you need to deploy the remote server as the standby (active) server.
    • When HA is being configured, the selected system management IP address and the floating IP address must be in the same network segment. The floating IP address cannot be the management IP address of the host. Otherwise, you cannot access the server after the HA switchover.
    • To modify HA information in HA dual-server mode, you must stop the eReplication Server on both the active and standby ends in off-peak hours.
    • To modify HA information in HA dual-server mode, you must modify the active server prior to the standby server. After configuration, you need to start the active server first and then the standby server. Otherwise, some information may fail to be modified.
    • Configure the same subnet and IP addresses in the same network for the active and standby nodes to enhance the communication reliability between and performance of the active and standby nodes.
    • Configure two or more heartbeat and file synchronization links or configure the links to bound ports. Multiple redundant links can improve the communication reliability between the active and standby nodes, avoid heartbeat interruption and problems of two active nodes, and improve file synchronization performance.
    • Configure the IP addresses of the heartbeat links to be the same as those of the synchronization links so that heartbeat link status and synchronization link status are consistent.
    • Configure the floating IP addresses and heartbeat IP addresses on the same network port to prevent accessible floating IP addresses which may cause the peer end unable to take over services.
    • After NICs are replaced, you need to re-configure HA.
    • If the eReplication Server has been deployed in active/standby mode, neither of the two eReplication servers can be deployed in HA mode.
  • Observe the following restrictions when changing the current deployment mode to HA:
    • If you deploy the local server as the active (standby) server, you need to deploy the remote server as the standby (active) server.
    • When the deployment mode of the eReplication Server is switched from HA mode to active/standby mode, switch the mode of the active and standby servers from HA mode to single-node mode, and then switch the single-node mode to the active/standby mode.

Single-Node Mode

The system will change the current deployment mode to single-node mode.

  1. Use PuTTY to log in to the eReplication Server management server.

    • In template-based installation mode: Log in as user DRManager, and run the su root command to switch to user root.
    • In software package-based installation mode: Log in as user root.
    NOTE:
    The default password of user DRManager is Huawei@CLOUD8. In template-based installation mode, the default password of user root is Huawei@CLOUD8!.

  2. Run the following command to prevent PuTTY from logging out because of timeout.

    TMOUT=0

    NOTE:
    After the preceding command is executed, the system keeps running even when no operations are performed, resulting in security risks. To ensure system security, run the exit command to exit the system after performing your operations.

  3. Run the following command to go to the save directory of the script.

    cd /opt/BCManager/Runtime/bin

    NOTE:

    In Linux, the installation path of the eReplication Server is /opt/BCManager. The path is fixed.

  4. Run the following command to configure the deployment mode to single-node mode:

    sh configSystem.sh

    The following command output is displayed:

    You are about to change the eReplication running mode.
    This operation will suspend the DR system, which may cause the DR protection services configured during the modification of the HA running mode to be invalid. In addition, this operation will affect the reliability of the DR system.
    
    Suggestion: Ensure that this operation is performed when no protection task is being executed.
    
    Are you sure you want to change the eReplication running mode? (y/n):
    

  5. Enter y and press Enter.

    This section uses changing the active/standby mode to single-node mode as an example.The following command output is displayed:

    The DR system is stopping.
    The DR system is shut down successfully.
    
    Start configuring eReplication:
    Select the mode to which eReplication needs to be configured.
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    
    1. Single-node mode (eReplication is running on only one local node, and data of eReplication is not backed up. If a fault occurs, the DR service cannot be provided.)
    2. Active/standby mode (eReplication runs on two nodes. Users can use the IP address of the active host to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, users need to manually switch the DR service to the standby end.)
    
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    

  6. Input 1 and press Enter.

    The following command output is displayed:

    Select this IP address as the listening IP address of the DR system.
    
       1  192.168.28.81
       2  192.168.28.82

  7. Select an IP address and press Enter.

    The following command output is displayed:

    Config eReplication successfully.
    
    Are you sure to start the DR system immediately? (y/n):

  8. Enter y to start the BCManager service immediately and press Enter.

    BCManager services are started successfully if the following command output is displayed:

    System is starting. Please wait...
    
    Total memory:  7.69(G)
    Required memory:  4(G)
    
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    Start the DR system successfully.

HA Mode (Configuring eReplication as the Active Server)

The system will change the current deployment mode to HA mode and configure the current eReplication as the active server.

  1. Use PuTTY to log in to the eReplication Server management server.

    • In template-based installation mode: Log in as user DRManager, and run the su root command to switch to user root.
    • In software package-based installation mode: Log in as user root.
    NOTE:
    The default password of user DRManager is Huawei@CLOUD8. In template-based installation mode, the default password of user root is Huawei@CLOUD8!.

  2. Run the following command to prevent PuTTY from logging out because of timeout.

    TMOUT=0

    NOTE:
    After the preceding command is executed, the system keeps running even when no operations are performed, resulting in security risks. To ensure system security, run the exit command to exit the system after performing your operations.

  3. Run the following command to go to the save directory of the script.

    cd /opt/BCManager/Runtime/bin

    NOTE:

    In Linux, the installation path of the eReplication Server is /opt/BCManager. The path is fixed.

  4. Run the following command to change the current deployment mode to HA mode and configure the current eReplication as the active server.

    sh configSystem.sh

    The following command output is displayed:

    You are about to change the eReplication running mode.
    This operation will suspend the DR system, which may cause the DR protection services configured during the modification of the eReplication running mode to be invalid. In addition, this operation will affect the reliability of the DR system.
    
    Suggestion: Ensure that this operation is performed when no protection task is being executed.
    
    Are you sure you want to change the eReplication running mode? (y/n):
    

  5. Input y and press Enter.

    The following command output is displayed:

    The DR system is stopping.
    The DR system is shut down successfully.
    
    Start configuring eReplication:
    Select the mode to which eReplication needs to be configured.
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    
    1. Single-node mode (eReplication is running on only one local node, and data of eReplication is not backed up. If a fault occurs, the DR service cannot be provided.)
    2. HA mode (eReplication runs on two nodes. Users can use a floating IP address to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, the system automatically switches the DR service to the standby end.)
    3. Active/standby mode (eReplication runs on two nodes. Users can use the IP address of the active host to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, users need to manually switch the DR service to the standby end.)
    
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    

  6. Enter 2 and press Enter.

    The following command output is displayed:

    Please select the role which you will to configure in the server.
    
        1.active
        2.standby
    

    1. Enter 1 and press Enter.

      The following command output is displayed:

      You select the active mode.
      
      Enter the local HA name:

    2. Enter the local node name and press Enter.

      NOTE:
      • The name contains 1 to 39 characters chosen from letters, digits, underscores (_), and hyphens (-).

      • The local node name set at the local end must be the same as the peer node name set at the peer node.

      The following command output is displayed:

      Enter the peer HA name:

    3. Enter the peer node name which is different from the local node name and press Enter.

      NOTE:
      • The name contains 1 to 39 characters chosen from letters, digits, underscores (_), and hyphens (-).

      • The local node name set at the local end must be the same as the peer node name set at the peer node.

      The following command output is displayed:

      Enter the floating IP address. (This IP address cannot be the same as the local IP address and will be used as the listening IP address of the dual-server DR system.)
      

    4. Enter the floating IP address and press Enter.

      • This IP address must be different from the local IP address.
      • This IP address must be different from the heartbeat link IP address, file synchronization links and the gateway IP address.

      The following command output is displayed:

      Configure the heartbeat IP addresses and ports (1 to 4 pairs can be configured).  
      Please enter the number(1 to 4):
      

    5. Set the number (ranging from 1 to 4) of heartbeat links on the local node and press Enter.

      The following command output is displayed:

      Please enter the IP address and port of the heartbeat link's local end and peer end respectively(format: IP address:port number):  
      Note that the IP addresses of both ends cannot be floating ones.
      The default port is 25221.

      NOTE:
      The default number of ports and the entered number of heartbeat links on the local node must be the same.

    6. Enter the heartbeat link IP address and port number of the local and peer node in sequence in the format of IP address:port number. Then press Enter.

      • The IP addresses of the local and peer heartbeat links can be those of nodes corresponding to communication links in the HA cluster.
      • The port ID ranges from 1024 to 65535.
      • The local and peer IP addresses cannot be the same as the floating IP address.
      • Port numbers used by different links cannot be the same.

      After the IP addresses and port numbers of all heartbeat links are set, the following command out put is displays:

      Is the input heartbeat link correct?(Enter y for yes and any other letters to reconfigure the heartbeat link.)(y/n):

    7. Enter y and press Enter to confirm that the heartbeat link is correct.

      If the heartbeat link information needs to be changed, press any key to reset the information.

      The following command output is displayed:

      Configuring heartbeat IP addresses and ports succeeded! 
      
      
      Configure file synchronization IP addresses and ports (1 to 4 pairs can be configured)! 
      Please enter the number(1 to 4):

    8. Set the file synchronization link number (the number ranges from 1 to 4) and press Enter.

      The following command output is displayed:

      Please enter the IP addresses and ports of the file synchronization link's local and peer ends respectively (format: IP address:port number): 
      Note that both IP addresses cannot be floating ones or be the same as the local IP address of the heartbeat link.
      The default port is 25321.

    9. Enter the file synchronization link IP address and port number of the local and peer node in sequence in the format of IP address:port number. Then press Enter.

      • The IP addresses of the local and peer file synchronization links can be those of nodes corresponding to communication links in the HA cluster.
      • The port ID ranges from 1024 to 65535.
      • The local and peer IP addresses cannot be the same as the floating IP address.
      • Port numbers used by different links cannot be the same.

      After the IP addresses and port numbers of all file synchronization links are set, the following command out put is displays:

      Is the input file synchronization link correct? (Enter y for yes and any other letters to reconfigure the file synchronization link.)(y/n):

    10. Enter y and press Enter to confirm that the file synchronization link is correct.

      If the file synchronization link information needs to be changed, press any key to reset the information.

      The following command output is displayed:

      Configuring file synchronization IP addresses and ports  succeeded! 
      
      
      Begin set the gateway IP.
      1 to 4 IP addresses can be configured and they must be different from the heartbeat IP addresses and floating IP addresses.
      Please enter the number(1 to 4):

    11. Set the numbers of the gateway (the number ranges from 1 to 4) and press Enter.

      The following command output is displayed:

      Please enter the gateway IP address:

    12. Enter the gateway information and press Enter.

      The gateway IP address cannot be the same as the floating IP address.

      After all gateway IP addresses are set, the following command output is displayed:

      Is the input gateway IP correct?(Enter y for yes and any other letters to reconfigure the gateway IP.)(y/n):

    13. Enter y and press Enter to confirm that the gateway IP address is correct.

      If you need to change the gateway IP address, press any key to reset the gateway IP address.

      The following command output is displayed:

      Configuring gateway IP addresses succeeded!
      
      Config HA successfully.
      
      Are you sure to start the DR system immediately? (y/n):

  7. Enter y to start the BCManager service immediately and press Enter.

    BCManager services are started successfully if the following command output is displayed:

    System is starting. Please wait...
    
    Total memory:  7.69(G)
    Required memory:  4(G)
    
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    Start the DR system successfully.

HA Mode (Configuring eReplication as the Standby Server)

The system will change the current deployment mode to HA mode and configure the current eReplication as the standby server.

  1. Use PuTTY to log in to the eReplication Server management server.

    • In template-based installation mode: Log in as user DRManager, and run the su root command to switch to user root.
    • In software package-based installation mode: Log in as user root.
    NOTE:
    The default password of user DRManager is Huawei@CLOUD8. In template-based installation mode, the default password of user root is Huawei@CLOUD8!.

  2. Run the following command to prevent PuTTY from logging out because of timeout.

    TMOUT=0

    NOTE:
    After the preceding command is executed, the system keeps running even when no operations are performed, resulting in security risks. To ensure system security, run the exit command to exit the system after performing your operations.

  3. Run the following command to go to the save directory of the script.

    cd /opt/BCManager/Runtime/bin

    NOTE:

    In Linux, the installation path of the eReplication Server is /opt/BCManager. The path is fixed.

  4. Run the following command to change the current deployment mode to HA mode and configure the current eReplication as the standby server.

    sh configSystem.sh

    The following command output is displayed:

    You are about to change the eReplication running mode.
    This operation will suspend the DR system, which may cause the DR protection services configured during the modification of the eReplication running mode to be invalid. In addition, this operation will affect the reliability of the DR system.
    
    Suggestion: Ensure that this operation is performed when no protection task is being executed.
    
    Are you sure you want to change the eReplication running mode? (y/n):
    

  5. Input y and press Enter.

    The following command output is displayed:

    The DR system is stopping.
    The DR system is shut down successfully.
    
    Start configuring eReplication:
    Select the mode to which eReplication needs to be configured.
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    
    1. Single-node mode (eReplication is running on only one local node, and data of eReplication is not backed up. If a fault occurs, the DR service cannot be provided.)
    2. HA mode (eReplication runs on two nodes. Users can use a floating IP address to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, the system automatically switches the DR service to the standby end.)
    3. Active/standby mode (eReplication runs on two nodes. Users can use the IP address of the active host to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, users need to manually switch the DR service to the standby end.)
    
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    

  6. Enter 2 and press Enter.

    The following command output is displayed:

    Please select the role which you will to configure in the server.
    
        1.active
        2.standby
    

    1. Enter 2 and press Enter.

      The following command output is displayed:

      You select the standby mode.
      
      Enter the local HA name:

    2. Enter the local node name and press Enter.

      NOTE:
      • The name contains 1 to 39 characters chosen from letters, digits, underscores (_), and hyphens (-).

      • The local node name set at the local end must be the same as the peer node name set at the peer node.

      The following command output is displayed:

      Enter the peer HA name:

    3. Enter the peer node name which is different from the local node name and press Enter.

      NOTE:
      • The name contains 1 to 39 characters chosen from letters, digits, underscores (_), and hyphens (-).

      • The local node name set at the local end must be the same as the peer node name set at the peer node.

      The following command output is displayed:

      Enter the floating IP address. (This IP address cannot be the same as the local IP address and will be used as the listening IP address of the dual-server DR system.)
      

    4. Enter the floating IP address and press Enter.

      • This IP address must be different from the local IP address.
      • This IP address must be different from the heartbeat link IP address, file synchronization links and the gateway IP address.

      The following command output is displayed:

      Configure the heartbeat IP addresses and ports (1 to 4 pairs can be configured).  
      Please enter the number(1 to 4):
      

    5. Set the number of gateways (the number ranges from 1 to 4) and press Enter.

      The following command output is displayed:

      Please enter the IP address and port of the heartbeat link's local end and peer end respectively(format: IP address:port number):  
      Note that the IP addresses of both ends cannot be floating ones. 
      The default port is 25221.

    6. Enter the heartbeat link IP address and port number of the local and peer node in sequence in the format of IP address:port number. Then press Enter.

      • The IP addresses of the local and peer heartbeat links can be those of nodes corresponding to communication links in the HA cluster.
      • The port ID ranges from 1024 to 65535.
      • The local and peer IP addresses cannot be the same as the floating IP address.
      • Port numbers used by different links cannot be the same.

      After the IP addresses and port numbers of all heartbeat links are set, the following command out put is displays:

      Is the input heartbeat link correct?(Enter y for yes and any other letters to reconfigure the heartbeat link.)(y/n):

    7. Enter y and press Enter to confirm that the heartbeat link is correct.

      If the heartbeat link information needs to be changed, press any key to reset the information.

      The following command output is displayed:

      Configuring heartbeat IP addresses and ports succeeded! 
      
      
      Configure file synchronization IP addresses and ports (1 to 4 pairs can be configured)! 
      Please enter the number(1 to 4):

    8. Set the file synchronization link number (the number ranges from 1 to 4) and press Enter.

      The following command output is displayed:

      Please enter the IP addresses and ports of the file synchronization link's local and peer ends respectively (format: IP address:port number): 
      Note that both IP addresses cannot be floating ones or be the same as the local IP address of the heartbeat link.
      The default port is 25321.

    9. Enter the file synchronization link IP address and port number of the local and peer node in sequence in the format of IP address:port number. Then press Enter.

      • The IP addresses of the local and peer file synchronization links can be those of nodes corresponding to communication links in the HA cluster.
      • The port ID ranges from 1024 to 65535.
      • The local and peer IP addresses cannot be the same as the floating IP address.
      • Port numbers used by different links cannot be the same.

      After the IP addresses and port numbers of all file synchronization links are set, the following command out put is displays:

      Is the input file synchronization link correct? (Enter y for yes and any other letters to reconfigure the file synchronization link.)(y/n):

    10. Enter y and press Enter to confirm that the file synchronization link is correct.

      If the file synchronization link information needs to be changed, press any key to reset the information.

      The following command output is displayed:

      Configuring file synchronization IP addresses and ports  succeeded! 
      
      
      Begin set the gateway IP.
      1 to 4 IP addresses can be configured and they must be different from the heartbeat IP addresses and floating IP addresses.
      Please enter the number(1 to 4):

    11. Set the numbers of the gateway (the number ranges from 1 to 4) and press Enter.

      The following command output is displayed:

      Please enter the gateway IP address:

    12. Enter the gateway information and press Enter.

      The gateway IP address cannot be the same as the floating IP address.

      After all gateway IP addresses are set, the following command output is displayed:

      Is the input gateway IP correct?(Enter y for yes and any other letters to reconfigure the gateway IP.)(y/n):

    13. Enter y and press Enter to confirm that the gateway IP address is correct.

      If you need to change the gateway IP address, press any key to reset the gateway IP address.

      The following command output is displayed:

      Configuring gateway IP addresses succeeded!
      
      Config HA successfully.
      
      Are you sure to start the DR system immediately? (y/n):

  7. Enter y to start the BCManager service immediately and press Enter.

    BCManager services are started successfully if the following command output is displayed:

    System is starting. Please wait...
    
    Total memory:  7.69(G)
    Required memory:  4(G)
    
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    Start the DR system successfully.

Active/Standby Mode (Configuring eReplication as the Active Server)

The system will change the current deployment mode to active/standby mode and configure the current eReplication as the active server.

  1. Optional: If you need to switch the deployment mode from the HA mode to the active/standby mode, switch the HA mode to the single-node mode first. For details, see Single-Node Mode.
  2. Use PuTTY to log in to the eReplication Server management server.

    • In template-based installation mode: Log in as user DRManager, and run the su root command to switch to user root.
    • In software package-based installation mode: Log in as user root.
    NOTE:
    The default password of user DRManager is Huawei@CLOUD8. In template-based installation mode, the default password of user root is Huawei@CLOUD8!.

  3. Run the following command to prevent PuTTY from logging out because of timeout.

    TMOUT=0

    NOTE:
    After the preceding command is executed, the system keeps running even when no operations are performed, resulting in security risks. To ensure system security, run the exit command to exit the system after performing your operations.

  4. Run the following command to go to the save directory of the script.

    cd /opt/BCManager/Runtime/bin

    NOTE:

    In Linux, the installation path of the eReplication Server is /opt/BCManager. The path is fixed.

  5. Run the following command to change the current deployment mode to active/standby mode and configure the current eReplication as the active server.

    sh configSystem.sh

    The following command output is displayed:

    You are about to change the eReplication running mode.
    This operation will suspend the DR system, which may cause the DR protection services configured during the modification of the eReplication running mode to be invalid. In addition, this operation will affect the reliability of the DR system.
    
    Suggestion: Ensure that this operation is performed when no protection task is being executed.
    
    Are you sure you want to change the eReplication running mode? (y/n):
    

  6. Input y and press Enter.

    The following command output is displayed:

    The DR system is stopping.
    The DR system is shut down successfully.
    
    Start configuring eReplication:
    Select the mode to which eReplication needs to be configured.
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    
    1. Single-node mode (eReplication is running on only one local node, and data of eReplication is not backed up. If a fault occurs, the DR service cannot be provided.)
    2. HA mode (eReplication runs on two nodes. Users can use a floating IP address to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, the system automatically switches the DR service to the standby end.)
    3. Active/standby mode (eReplication runs on two nodes. Users can use the IP address of the active host to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, users need to manually switch the DR service to the standby end.)
    
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    

  7. Input 3 and press Enter.

    The following command output is displayed:

    Please select the role which you will to configure in the server.
    
        1.active
        2.standby
    

    1. Input 1 and press Enter.

      The following command output is displayed:

      You select the standby mode.
      
      Select this IP address as the listening IP address of the DR system.
      
         1  100.136.27.171
      

    2. Enter the serial number of the desired IP address and press Enter.

      The following command output is displayed:

      Enter the data synchronization link in active/standby mode of eReplication (format: IP address:port number):
      The default port is 25321.
      

    3. Enter the data replication link IP address and port number of the local and peer nodes in sequence in the format of IP address:port number. Then press Enter.

      • The data replication link IP addresses of the local and peer nodes can be the local management IP addresses of the local and peer nodes.
      • The port number ranges from 1024 to 65535.

    4. Ensure that the data replication link IP addresses are correct. Input y and press Enter.

      If the data replication link information needs to be changed, press any key to reset the information.

      The following command output is displayed:

      Configuring data synchronization IP addresses and ports succeeded!
      
      
      Config Active-Standby successfully.
      
      Are you sure to start the DR system immediately? (y/n):
      

  8. Enter y to start the BCManager service immediately and press Enter.

    BCManager services are started successfully if the following command output is displayed:

    System is starting. Please wait...
    
    Total memory:  7.69(G)
    Required memory:  4(G)
    
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    Start the DR system successfully.

  9. Optional: If both the active and standby servers have been configured, run the sh showSystemStatus.sh command to check whether the active/standby mode is configured successfully. For details, see Querying the Deployment Mode Status and Service Information.

Active/Standby Mode (Configuring eReplication as the Standby Server)

The system will change the current deployment mode to active/standby mode and configure the current eReplication as the standby server.

  1. Optional: If you need to switch the deployment mode from the HA mode to the active/standby mode, switch the HA mode to the single-node mode first. For details, see Single-Node Mode.
  2. Use PuTTY to log in to the eReplication Server management server.

    • In template-based installation mode: Log in as user DRManager, and run the su root command to switch to user root.
    • In software package-based installation mode: Log in as user root.
    NOTE:
    The default password of user DRManager is Huawei@CLOUD8. In template-based installation mode, the default password of user root is Huawei@CLOUD8!.

  3. Run the following command to prevent PuTTY from logging out because of timeout.

    TMOUT=0

    NOTE:
    After the preceding command is executed, the system keeps running even when no operations are performed, resulting in security risks. To ensure system security, run the exit command to exit the system after performing your operations.

  4. Run the following command to go to the save directory of the script.

    cd /opt/BCManager/Runtime/bin

    NOTE:

    In Linux, the installation path of the eReplication Server is /opt/BCManager. The path is fixed.

  5. Run the following command to change the current deployment mode to active/standby mode and configure the current eReplication as the standby server.

    sh configSystem.sh

    The following command output is displayed:

    You are about to change the eReplication running mode.
    This operation will suspend the DR system, which may cause the DR protection services configured during the modification of the eReplication running mode to be invalid. In addition, this operation will affect the reliability of the DR system.
    
    Suggestion: Ensure that this operation is performed when no protection task is being executed.
    
    Are you sure you want to change the eReplication running mode? (y/n):
    

  6. Input y and press Enter.

    The following command output is displayed:

    The DR system is stopping.
    The DR system is shut down successfully.
    
    Start configuring eReplication:
    Select the mode to which eReplication needs to be configured.
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    
    1. Single-node mode (eReplication is running on only one local node, and data of eReplication is not backed up. If a fault occurs, the DR service cannot be provided.)
    2. HA mode (eReplication runs on two nodes. Users can use a floating IP address to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, the system automatically switches the DR service to the standby end.)
    3. Active/standby mode (eReplication runs on two nodes. Users can use the IP address of the active host to access the DR page. Data is automatically backed up to the standby end. When a fault occurs, users need to manually switch the DR service to the standby end.)
    
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    

  7. Input 3 and press Enter.

    The following command output is displayed:

    Please select the role which you will to configure in the server.
    
        1.active
        2.standby
    

    1. Input 2 and press Enter.

      The following command output is displayed:

      You select the standby mode.
      
      Select this IP address as the listening IP address of the DR system.
      
         1  100.136.27.170
      

    2. Enter the serial number of the desired IP address and press Enter.

      The following command output is displayed:

      Enter the data synchronization link in active/standby mode of eReplication (format: IP address:port number):
      The default port is 25321.
      

    3. Enter the data replication link IP address and port number of the local and peer nodes in sequence in the format of IP address:port number. Then press Enter.

      • The data replication link IP addresses of the local and peer nodes can be the local management IP addresses of the local and peer nodes.
      • The port number ranges from 1024 to 65535.

    4. Ensure that the data replication link IP addresses are correct. Input y and press Enter.

      If the data replication link information needs to be changed, press any key to reset the information.

      The following command output is displayed:

      Configuring data synchronization IP addresses and ports succeeded!
      
      
      Config Active-Standby successfully.
      
      Are you sure to start the DR system immediately? (y/n):
      

  8. Enter y to start the BCManager service immediately and press Enter.

    BCManager services are started successfully if the following command output is displayed:

    System is starting. Please wait...
    
    Total memory:  7.69(G)
    Required memory:  4(G)
    
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    Start the DR system successfully.

  9. Optional: If both the active and standby servers have been configured, run the sh showSystemStatus.sh command to check whether the active/standby mode is configured successfully. For details, see Querying the Deployment Mode Status and Service Information.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 18355

Downloads: 76

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