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).
Installing the eReplication Server Using a Software Package (Linux)

Installing the eReplication Server Using a Software Package (Linux)

This section describes how to install the eReplication Server using the software package. In Linux, you can install the eReplication Server using the GUI or the CLI.

Prerequisites

  • A qualified VM or physical server is ready and the required operating system has been installed on it. For details about the requirements, see Deployment Environment Requirements.
  • The software packages, reference documentation, and tools required by the eReplication Server have been obtained. For details, see Obtaining Installation Packages and Documentation.
  • The signature file and digital signature public key have been obtained and the software integrity has been verified.
    1. On the page for downloading the eReplication software package, you can download the .asc digital signature file whose name is the same as that of the software package.
    2. You have used the digital signature public key and verification tool provided by the website to verify the digital signature of the software package. You can obtain the digital signature public key, verification tool, and their usage methods from:
  • Password of the user root of physical servers or VMs on which the eReplication Server is to be installed has been obtained.
  • The operating system of the server where the eReplication Server is installed has been hardened. For details about how to harden operating systems, see OceanStor BCManager6.5.0eReplication Security Hardening Guide.
  • The system time stability of the server is important for the eReplication Server. Do not change the system time during the operation of the eReplication Server. If system time-hopping occurs, you need to restart the eReplication Server. For details about how to restart the eReplication Server, see Starting the eReplication Server.
  • You can deploy management node HA only in Linux operating systems. If HA needs to be configured, plan the following network environment in advance:
    • Names of active and standby HA nodes.
    • Floating IP address of HA. After HA is configured, the floating IP address is used to provide DR services. This IP address will be set automatically after the HA software is started, so you can skip setting the floating IP address.
    • Heartbeat links and file synchronization links between HA nodes. You are advised to plan two or more heartbeat links and file synchronization links, and ensure the links using different communication networks, for example, using different network planes.
    • Gateway IP addresses. The gateway plays an important role in HA arbitration switching process.

Context

  • To ensure normal operation of the remote DR function, ensure that the same eReplication Server is installed at the production and DR centers.
  • If the protected object is FusionSphere OpenStack, ensure that the server time of the installed eReplication Server and that of the OpenStack server are the same.
  • Google Chrome set restrictions on some ports. If such ports are used on the web-based eReplication Server and Google Chrome is used to access the eReplication services, error message ERR_UNSATE_PORT will be displayed on the page. This error is not caused by eReplication. Therefore, eReplication web service ports need to be modified.
  • The system time stability of the server is important for the eReplication Server. Do not change the system time during the operation of the eReplication Server. If system time-hopping occurs, you need to restart the eReplication Server. For details about how to restart the eReplication Server, see Starting the eReplication Server.
In Linux, a password can be changed on the CLI.
NOTE:
Run the startx command. If the following information is not displayed, the system supports the X Window System.
Command not found

CLI

This section describes how to install the eReplication Server on the CLI.

  • If the eReplication Server is deployed in HA mode, the restrictions are as follows:
    • If the system is to be deployed in HA mode, you need to deploy one eReplication Server on each DC, and configure cross-site HA between the two eReplication Servers.
    • The management node HA can only be deployed in Linux operating system and the HA active/standby mode is supported. In this mode, when deploying the local server as active (standby) server, you need to deploy the peer server as the standby (active) server.
    • If the system is to be deployed in HA mode, the two servers equipped with the eReplication Server must be on the same subnet. And the two servers must be installed using the same installation package.
    • When HA is being configured, the floating IP address cannot be the management IP address of the host. Otherwise, you cannot access the server after the HA switchover.
  • If the eReplication Server is deployed in active/standby mode, the restrictions are as follows:
    • If the system is to be deployed in active/standby mode, you need to deploy one eReplication Server on each DC.
    • The active/standby mode can be deployed only in the Linux operating system and the active/standby mode that one active server and one standby server are deployed is supported. In this mode, when deploying the local server as active (standby) server, you need to deploy the peer server as the standby (active) server.
    • If the eReplication Server is deployed in active/standby mode, the data replication link between the two servers where the eReplication Server is installed must be connected. In addition, the two servers must be installed using the same installation package.
NOTE:
  • This section uses the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package as an example. The version number in the preceding software package varies with site conditions.
  • If you need to reconfigure mode after installing the eReplication Server, refer to Configuring a Deployment Mode.
Single-Node Mode

The eReplication Server is deployed in single-node mode in the system.

  1. Check whether the firewall is enabled.

    • If the firewall is disabled, check whether the firewall needs to be enabled. If you need to enable the firewall, perform related operations to enable the firewall. If you do not need to enable the firewall, go to 2.
    • If the firewall is enabled, enable the firewall port of the server on which the eReplication Server is installed by performing OceanStor BCManager 6.5.0 eReplication Communication Matrix. For details about how to enable the firewall ports, see Configuring the Firewall.

  2. Use PuTTY to log in as user root to the server where the eReplication Server is to be installed.

    NOTE:

    This section uses an operating system whose kernel version is Linux 3.0.76-0.11-default to explain how to install the eReplication Server in the kernel version Linux. In Linux, the commands vary with versions.

  3. Run the following command to prevent PuTTY from exiting due to session timeout:

    TMOUT=0

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Copy the eReplication Server package to the server where the eReplication Server is to be installed.

    The name of the directory where the eReplication Server installation package resides can contain only letters, digits, underscores (_), hyphens (-), periods (.), and single spaces.

  5. Go to the directory where the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package resides.
  6. Run the following command to decompress the package. Place the decompressed folders and files in the directory where the package resides.

    tar -zxvf OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz

  7. Install the eReplication Server.
    1. Run the following command to execute the installation script:

      sh cliInstall.sh

      The following command output is displayed:

      The operation system is : Linux 3.0.76-0.11-default
      Step 1:
      The install path is: /opt/BCManager. Are you sure? (y/n): [y]
      
      NOTE:

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

    2. Type y and press Enter, or directly press Enter.

      The following command output is displayed:

      Step 2:
      The data files path: [/opt/gs/app/data]
      
      Enter the database port [6432]:
      

    3. Set the database port number and press Enter. You can directly press Enter, and the port number is 6432 by default.

      NOTE:

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Please input the database admin password :

    4. Set the database administrator password. The database administrator has the highest database permission, including all system and object permissions. The administrator account has been created by the system by default. The user name is GaussDB and the default password is Gaussdb_123. During installation, you need to change the password to a user-defined one and record it for future maintenance. Press Enter.

      NOTE:
      The new password must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits
      • Cannot be the same as the default database password Gaussdb_123.

      The following command output is displayed:

      Please confirm the database admin password :

    5. Type the database administrator password again and press Enter.

      The following command output is displayed:

      Enter the BCManager DBA user [RDDBUser]:
      

    6. BCManager DBA is the database account created during the installation. It is used for BCManager to access the database. The user name and password can be customized. The user name consists of 4 to 8 letters, for example, RDDBuser. To change the password, see Changing the Password of a Database Account, and update the new password in eReplication by referring to Update the Password of the Account Used by the eReplication to Access Databases.

      The following command output is displayed:

      Please input the password for BCManager DBA user:
      NOTE:

      The user name of the BCManager DBA contains four to eight letters.

      The password of the BCManager DBA user must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits

    7. Set the password for the account used to access the database and press Enter.

      The following command output is displayed:

      Please confirm the password for BCManager DBA user:

    8. Enter the password for accessing the database and press Enter.

      The following command output is displayed:

      Step 3:
      
           NAME                                   DESCRIPTION                                                          VERSION        SIZE      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      1.   Application DR Management Component    Provided DR protection for applications, such as Oracle.              7.0.3          80MB      
      2.   VMware vSphere DR Management Component Provided DR protection for VMware vSphere.                            7.0.3          80MB      
      3.   FusionSphere DR Management Component   Provided DR protection for FusionSphere.                              7.0.3          80MB      
      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      Enter the serial numbers of modules to be installed, and separate the serial numbers with blank spaces.
      All modules will be installed by default.

    9. Select the components that you want to install. Table 2-10 describes the components to be installed.

      Table 2-10  Description of the components to be installed

      Component

      Description

      Application DR Management Component

      This type of component provides DR for Oracle, IBM DB2, Microsoft SQL Server, Microsoft Exchange Server, LUNs, local file systems, NAS file systems, and the InterSystems Caché application.

      VMware vSphere DR Management Component

      This type of component provides DR for VMware vSphere.

      FusionSphere DR Management Component

      This type of component provides DR for FusionSphere.

      • Enter component serial numbers and separate them with spaces. Then press Enter to install them.
      • If you press Enter without entering any component serial number, all components are installed.

      The following command output is displayed:

      Required space:  1264(M)
      Free space:  28.89(G)
      Step 4:
      Select this IP address as the listening IP address of the DR system.
      ==============================================================================
       [1] eth0  MAC=00:50:56:B1:04:9A  IP=192.168.28.58  NetMask=255.255.0.0
       [2] eth1  MAC=00:50:56:B1:08:EF  IP=192.168.28.59  NetMask=255.255.0.0
      ==============================================================================

    10. Select an IP address and press Enter.

      The following command output is displayed:

      Please input the listening port [9443]:

    11. Enter the listening port number and press Enter. Alternatively, directly press Enter to use default listening port 9443.

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Current IP configuration:
      ----------------------------------------------------------------------------------------
      
      [1] MAC=00:50:56:B1:73:A1  Service Management IP=192.168.28.58
      
      ----------------------------------------------------------------------------------------

    12. Select a deployment mode for the eReplication Server.

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

    13. Enter 1 and press Enter.

      The following command output is displayed:

      
      
      Start install software. Please wait...
      Installation is completed.
      
      *************Install Succeed!*************
      
      
      access_privilege success.
      
      Are you sure to start up the software immediately? (y/n):

  8. Enter y and press Enter to start the eReplication Server.

    Startup succeeds if the following command output is displayed:

    System is starting. Please wait...
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    NOTE:

    If you do not want to start the eReplication Server immediately, enter n. If you want to start the OceanStor BCManager Server in the follow-up procedures, you can go to the /opt/BCManager/Runtime/bin directory and run the sh startSystem.sh command to start it.

    Some ports are occupied when the eReplication Server is being started. If those ports are occupied by other applications or the format of port numbers is incorrect, the eReplication Server cannot be started. Under such conditions, you need to reconfigure ports and start the eReplication Server again. For details, see Changing Ports of the eReplication Server.

HA Mode (Configuring eReplication as the Active Server)

The eReplication Server is deployed in HA mode in the system. This section describes how to set the current eReplication as the active server.

  1. Check whether the firewall is enabled.

    • If the firewall is disabled, check whether the firewall needs to be enabled. If you need to enable the firewall, perform related operations to enable the firewall. If you do not need to enable the firewall, go to 2.
    • If the firewall is enabled, enable the firewall port of the server on which the eReplication Server is installed by performing OceanStor BCManager 6.5.0 eReplication Communication Matrix. For details about how to enable the firewall ports, see Configuring the Firewall.

  2. Use PuTTY to log in as user root to the server where the eReplication Server is to be installed.

    NOTE:

    This section uses an operating system whose kernel version is Linux 3.0.76-0.11-default to explain how to install the eReplication Server in the kernel version Linux. In Linux, the commands vary with versions.

  3. Run the following command to prevent PuTTY from exiting due to session timeout:

    TMOUT=0

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Copy the eReplication Server package to the server where the eReplication Server is to be installed.

    The name of the directory where the eReplication Server installation package resides can contain only letters, digits, underscores (_), hyphens (-), periods (.), and single spaces.

  5. Go to the directory where the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package resides.
  6. Run the following command to decompress the package. Place the decompressed folders and files in the directory where the package resides.

    tar -zxvf OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz

  7. Install the eReplication Server.
    1. Run the following command to execute the installation script:

      sh cliInstall.sh

      The following command output is displayed:

      The operation system is : Linux 3.0.76-0.11-default
      Step 1:
      The install path is: /opt/BCManager. Are you sure? (y/n): [y]
      
      NOTE:

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

    2. Type y and press Enter, or directly press Enter.

      The following command output is displayed:

      Step 2:
      The data files path: [/opt/gs/app/data]
      
      Enter the database port [6432]:
      

    3. Set the database port number and press Enter. You can directly press Enter, and the port number is 6432 by default.

      NOTE:

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Please input the database admin password :

    4. Set the database administrator password. The database administrator has the highest database permission, including all system and object permissions. The administrator account has been created by the system by default. The user name is GaussDB and the default password is Gaussdb_123. During installation, you need to change the password to a user-defined one and record it for future maintenance. Press Enter.

      NOTE:
      The new password must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits
      • Cannot be the same as the default database password Gaussdb_123.

      The following command output is displayed:

      Please confirm the database admin password :

    5. Type the database administrator password again and press Enter.

      The following command output is displayed:

      Enter the BCManager DBA user [RDDBUser]:
      

    6. Set the user name used to eReplication access the database and press Enter. Alternatively, directly press Enter, and the user name is RDDBUser by default.

      The following command output is displayed:

      Please input the password for BCManager DBA user:

      User names and passwords of the BCManager DBA on the active and standby servers must be consistent.

      NOTE:

      The user name of the BCManager DBA contains four to eight letters.

      The password of the BCManager DBA user must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits

    7. Set the password for the account used to access the database and press Enter.

      The following command output is displayed:

      Please confirm the password for BCManager DBA user:

    8. Enter the password for accessing the database and press Enter.

      The following command output is displayed:

      Step 3:
      
           NAME                                   DESCRIPTION                                                          VERSION        SIZE      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      1.   Application DR Management Component    Provided DR protection for applications, such as Oracle.              7.0.3          80MB      
      2.   VMware vSphere DR Management Component Provided DR protection for VMware vSphere.                            7.0.3          80MB      
      3.   FusionSphere DR Management Component   Provided DR protection for FusionSphere.                              7.0.3          80MB      
      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      Enter the serial numbers of modules to be installed, and separate the serial numbers with blank spaces.
      All modules will be installed by default.

    9. Select the components that you want to install. Table 2-11 describes the components to be installed.

      Table 2-11  Description of the components to be installed

      Component

      Description

      Application DR Management Component

      This type of component provides DR for Oracle, IBM DB2, Microsoft SQL Server, Microsoft Exchange Server, LUNs, local file systems, NAS file systems, and the InterSystems Caché application.

      VMware vSphere DR Management Component

      This type of component provides DR for VMware vSphere.

      FusionSphere DR Management Component

      This type of component provides DR for FusionSphere.

      • Enter component serial numbers and separate them with spaces. Then press Enter to install them.
      • If you press Enter without entering any component serial number, all components are installed.

      The following command output is displayed:

      Required space:  1264(M)
      Free space:  28.89(G)
      Step 4:
      Select this IP address as the listening IP address of the DR system.
      ==============================================================================
       [1] eth0  MAC=00:50:56:B1:04:9A  IP=192.168.28.58  NetMask=255.255.0.0
       [2] eth1  MAC=00:50:56:B1:08:EF  IP=192.168.28.59  NetMask=255.255.0.0
      ==============================================================================

    10. Select an IP address and press Enter.

      The following command output is displayed:

      Please input the listening port [9443]:

    11. Enter the listening port number and press Enter. Alternatively, directly press Enter to use default listening port 9443.

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Current IP configuration:
      ----------------------------------------------------------------------------------------
      
      [1] MAC=00:50:56:B1:73:A1  Service Management IP=192.168.28.58
      
      ----------------------------------------------------------------------------------------

    12. Select a deployment mode for the eReplication Server.

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

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

    14. Enter 1 and press Enter.

      The following command output is displayed:

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

    15. 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:

    16. 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 peer node name set at the local end must be the same as the local node name set at the peer end.

      The following command output is displayed:

      Please enter the service management floating IP address. This IP address will replace the service management IP address for service management.

    17. Enter the floating IP address and press Enter.

      This IP address is used to manage services.

      • This IP address must be different from the local IP address of the host and must be configured on both the active and standby hosts.
      • This IP address must be different from the IP addresses of heartbeat links, file synchronization links, and the gateways.

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

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

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

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

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

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

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

    24. 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:

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

    26. 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:

      Configure the HA gateway IP successfully!
       
      
      Start install software. Please wait...
      Installation is completed.
      
      *************Install Succeed!*************
      
      
      access_privilege success.
      
      Are you sure to start up the software immediately? (y/n):

  8. Enter y and press Enter to start the eReplication Server.

    Startup succeeds if the following command output is displayed:

    System is starting. Please wait...
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    NOTE:

    If you do not want to start the eReplication Server immediately, enter n. If you want to start the OceanStor BCManager Server in the follow-up procedures, you can go to the /opt/BCManager/Runtime/bin directory and run the sh startSystem.sh command to start it.

    Some ports are occupied when the eReplication Server is being started. If those ports are occupied by other applications or the format of port numbers is incorrect, the eReplication Server cannot be started. Under such conditions, you need to reconfigure ports and start the eReplication Server again. For details, see Changing Ports of the eReplication Server.

HA Mode (Configuring eReplication as the Standby Server)

The eReplication Server is deployed in HA mode in the system. This section describes how to set the current eReplication as the standby server.

  1. Check whether the firewall is enabled.

    • If the firewall is disabled, check whether the firewall needs to be enabled. If you need to enable the firewall, perform related operations to enable the firewall. If you do not need to enable the firewall, go to 2.
    • If the firewall is enabled, enable the firewall port of the server on which the eReplication Server is installed by performing OceanStor BCManager 6.5.0 eReplication Communication Matrix. For details about how to enable the firewall ports, see Configuring the Firewall.

  2. Use PuTTY to log in as user root to the server where the eReplication Server is to be installed.

    NOTE:

    This section uses an operating system whose kernel version is Linux 3.0.76-0.11-default to explain how to install the eReplication Server in the kernel version Linux. In Linux, the commands vary with versions.

  3. Run the following command to prevent PuTTY from exiting due to session timeout:

    TMOUT=0

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Copy the eReplication Server package to the server where the eReplication Server is to be installed.

    The name of the directory where the eReplication Server installation package resides can contain only letters, digits, underscores (_), hyphens (-), periods (.), and single spaces.

  5. Go to the directory where the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package resides.
  6. Run the following command to decompress the package. Place the decompressed folders and files in the directory where the package resides.

    tar -zxvf OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz

  7. Install the eReplication Server.
    1. Run the following command to execute the installation script:

      sh cliInstall.sh

      The following command output is displayed:

      The operation system is : Linux 3.0.76-0.11-default
      Step 1:
      The install path is: /opt/BCManager. Are you sure? (y/n): [y]
      
      NOTE:

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

    2. Type y and press Enter, or directly press Enter.

      The following command output is displayed:

      Step 2:
      The data files path: [/opt/gs/app/data]
      
      Enter the database port [6432]:
      

    3. Set the database port number and press Enter. You can directly press Enter, and the port number is 6432 by default.

      NOTE:

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Please input the database admin password :

    4. Set the database administrator password. The database administrator has the highest database permission, including all system and object permissions. The administrator account has been created by the system by default. The user name is GaussDB and the default password is Gaussdb_123. During installation, you need to change the password to a user-defined one and record it for future maintenance. Press Enter.

      NOTE:
      The new password must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits
      • Cannot be the same as the default database password Gaussdb_123.

      The following command output is displayed:

      Please confirm the database admin password :

    5. Type the database administrator password again and press Enter.

      The following command output is displayed:

      Enter the BCManager DBA user [RDDBUser]:
      

    6. Set the user name used to eReplication access the database and press Enter. Alternatively, directly press Enter, and the user name is RDDBUser by default.

      The following command output is displayed:

      Please input the password for BCManager DBA user:

      User names and passwords of the BCManager DBA on the active and standby servers must be consistent.

      NOTE:

      The user name of the BCManager DBA contains four to eight letters.

      The password of the BCManager DBA user must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits

    7. Set the password for the account used to access the database and press Enter.

      The following command output is displayed:

      Please confirm the password for BCManager DBA user:

    8. Enter the password for accessing the database and press Enter.

      The following command output is displayed:

      Step 3:
      
           NAME                                   DESCRIPTION                                                          VERSION        SIZE      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      1.   Application DR Management Component    Provided DR protection for applications, such as Oracle.              7.0.3          80MB      
      2.   VMware vSphere DR Management Component Provided DR protection for VMware vSphere.                            7.0.3          80MB      
      3.   FusionSphere DR Management Component   Provided DR protection for FusionSphere.                              7.0.3          80MB      
      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      Enter the serial numbers of modules to be installed, and separate the serial numbers with blank spaces.
      All modules will be installed by default.

    9. Select the components that you want to install. Table 2-12 describes the components to be installed.

      Table 2-12  Description of the components to be installed

      Component

      Description

      Application DR Management Component

      This type of component provides DR for Oracle, IBM DB2, Microsoft SQL Server, Microsoft Exchange Server, LUNs, local file systems, NAS file systems, and the InterSystems Caché application.

      VMware vSphere DR Management Component

      This type of component provides DR for VMware vSphere.

      FusionSphere DR Management Component

      This type of component provides DR for FusionSphere.

      • Enter component serial numbers and separate them with spaces. Then press Enter to install them.
      • If you press Enter without entering any component serial number, all components are installed.

      The following command output is displayed:

      Required space:  1264(M)
      Free space:  28.89(G)
      Step 4:
      Select this IP address as the listening IP address of the DR system.
      ==============================================================================
       [1] eth0  MAC=00:50:56:B1:04:9A  IP=192.168.28.58  NetMask=255.255.0.0
       [2] eth1  MAC=00:50:56:B1:08:EF  IP=192.168.28.59  NetMask=255.255.0.0
      ==============================================================================

    10. Select an IP address and press Enter.

      The following command output is displayed:

      Please input the listening port [9443]:

    11. Enter the listening port number and press Enter. Alternatively, directly press Enter to use default listening port 9443.

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Current IP configuration:
      ----------------------------------------------------------------------------------------
      
      [1] MAC=00:50:56:B1:73:A1  Service Management IP=192.168.28.58
      
      ----------------------------------------------------------------------------------------

    12. Select a deployment mode for the eReplication Server.

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

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

    14. Enter 2 and press Enter.

      The following command output is displayed:

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

    15. 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:

    16. 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 peer node name set at the local end must be the same as the local node name set at the peer end.

      The following command output is displayed:

      Please enter the service management floating IP address. This IP address will replace the service management IP address for service management.

    17. Enter the floating IP address and press Enter.

      This IP address is used to manage services.

      • This IP address must be different from the local IP address of the host and must be configured on both the active and standby hosts.
      • This IP address must be different from the IP addresses of heartbeat links, file synchronization links, and the gateways.

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

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

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

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

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

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

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

    24. 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:

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

    26. 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:

      Configure the HA gateway IP successfully!
       
      
      Start install software. Please wait...
      Installation is completed.
      
      *************Install Succeed!*************
      
      
      access_privilege success.
      
      Are you sure to start up the software immediately? (y/n):

  8. Enter y and press Enter to start the eReplication Server.

    Startup succeeds if the following command output is displayed:

    System is starting. Please wait...
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    NOTE:

    If you do not want to start the eReplication Server immediately, enter n. If you want to start the OceanStor BCManager Server in the follow-up procedures, you can go to the /opt/BCManager/Runtime/bin directory and run the sh startSystem.sh command to start it.

    Some ports are occupied when the eReplication Server is being started. If those ports are occupied by other applications or the format of port numbers is incorrect, the eReplication Server cannot be started. Under such conditions, you need to reconfigure ports and start the eReplication Server again. For details, see Changing Ports of the eReplication Server.

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

The eReplication Server is deployed in active/standby mode in the system. This section describes how to set the current eReplication as the active server.

  1. Check whether the firewall is enabled.

    • If the firewall is disabled, check whether the firewall needs to be enabled. If you need to enable the firewall, perform related operations to enable the firewall. If you do not need to enable the firewall, go to 2.
    • If the firewall is enabled, enable the firewall port of the server on which the eReplication Server is installed by performing OceanStor BCManager 6.5.0 eReplication Communication Matrix. For details about how to enable the firewall ports, see Configuring the Firewall.

  2. Use PuTTY to log in as user root to the server where the eReplication Server is to be installed.

    NOTE:

    This section uses an operating system whose kernel version is Linux 3.0.76-0.11-default to explain how to install the eReplication Server in the kernel version Linux. In Linux, the commands vary with versions.

  3. Run the following command to prevent PuTTY from exiting due to session timeout:

    TMOUT=0

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Copy the eReplication Server package to the server where the eReplication Server is to be installed.

    The name of the directory where the eReplication Server installation package resides can contain only letters, digits, underscores (_), hyphens (-), periods (.), and single spaces.

  5. Go to the directory where the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package resides.
  6. Run the following command to decompress the package. Place the decompressed folders and files in the directory where the package resides.

    tar -zxvf OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz

  7. Install the eReplication Server.
    1. Run the following command to execute the installation script:

      sh cliInstall.sh

      The following command output is displayed:

      The operation system is : Linux 3.0.76-0.11-default
      Step 1:
      The install path is: /opt/BCManager. Are you sure? (y/n): [y]
      
      NOTE:

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

    2. Type y and press Enter, or directly press Enter.

      The following command output is displayed:

      Step 2:
      The data files path: [/opt/gs/app/data]
      
      Enter the database port [6432]:
      

    3. Set the database port number and press Enter. You can directly press Enter, and the port number is 6432 by default.

      NOTE:

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Please input the database admin password :

    4. Set the database administrator password. The database administrator has the highest database permission, including all system and object permissions. The administrator account has been created by the system by default. The user name is GaussDB and the default password is Gaussdb_123. During installation, you need to change the password to a user-defined one and record it for future maintenance. Press Enter.

      NOTE:
      The new password must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits
      • Cannot be the same as the default database password Gaussdb_123.

      The following command output is displayed:

      Please confirm the database admin password :

    5. Type the database administrator password again and press Enter.

      The following command output is displayed:

      Enter the BCManager DBA user [RDDBUser]:
      

    6. Set the user name used to eReplication access the database and press Enter. Alternatively, directly press Enter, and the user name is RDDBUser by default.

      The following command output is displayed:

      Please input the password for BCManager DBA user:

      User names and passwords of the BCManager DBA on the active and standby servers must be consistent.

      NOTE:

      The user name of the BCManager DBA contains four to eight letters.

      The password of the BCManager DBA user must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits

    7. Set the password for the account used to access the database and press Enter.

      The following command output is displayed:

      Please confirm the password for BCManager DBA user:

    8. Enter the password for accessing the database and press Enter.

      The following command output is displayed:

      Step 3:
      
           NAME                                   DESCRIPTION                                                          VERSION        SIZE      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      1.   Application DR Management Component    Provided DR protection for applications, such as Oracle.              7.0.3          80MB      
      2.   VMware vSphere DR Management Component Provided DR protection for VMware vSphere.                            7.0.3          80MB      
      3.   FusionSphere DR Management Component   Provided DR protection for FusionSphere.                              7.0.3          80MB      
      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      Enter the serial numbers of modules to be installed, and separate the serial numbers with blank spaces.
      All modules will be installed by default.

    9. Select the components that you want to install. Table 2-13 describes the components to be installed.

      Table 2-13  Description of the components to be installed

      Component

      Description

      Application DR Management Component

      This type of component provides DR for Oracle, IBM DB2, Microsoft SQL Server, Microsoft Exchange Server, LUNs, local file systems, NAS file systems, and the InterSystems Caché application.

      VMware vSphere DR Management Component

      This type of component provides DR for VMware vSphere.

      FusionSphere DR Management Component

      This type of component provides DR for FusionSphere.

      • Enter component serial numbers and separate them with spaces. Then press Enter to install them.
      • If you press Enter without entering any component serial number, all components are installed.

      The following command output is displayed:

      Required space:  1264(M)
      Free space:  28.89(G)
      Step 4:
      Select this IP address as the listening IP address of the DR system.
      ==============================================================================
       [1] eth0  MAC=00:50:56:B1:04:9A  IP=192.168.28.58  NetMask=255.255.0.0
       [2] eth1  MAC=00:50:56:B1:08:EF  IP=192.168.28.59  NetMask=255.255.0.0
      ==============================================================================

    10. Select an IP address and press Enter.

      The following command output is displayed:

      Please input the listening port [9443]:

    11. Enter the listening port number and press Enter. Alternatively, directly press Enter to use default listening port 9443.

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Current IP configuration:
      ----------------------------------------------------------------------------------------
      
      [1] MAC=00:50:56:B1:73:A1  Service Management IP=192.168.28.58
      
      ----------------------------------------------------------------------------------------

    12. Select a deployment mode for the eReplication Server.

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

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

    14. Input 1 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.

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

    16. Ensure that the data replication link information is 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:

      Start install software. Please wait...
      Installation is completed.
      
      *************Install Succeed!*************
      
      
      access_privilege success.
      
      Are you sure to start up the software immediately? (y/n):

  8. Enter y and press Enter to start the eReplication Server.

    Startup succeeds if the following command output is displayed:

    System is starting. Please wait...
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    NOTE:

    If you do not want to start the eReplication Server immediately, enter n. If you want to start the OceanStor BCManager Server in the follow-up procedures, you can go to the /opt/BCManager/Runtime/bin directory and run the sh startSystem.sh command to start it.

    Some ports are occupied when the eReplication Server is being started. If those ports are occupied by other applications or the format of port numbers is incorrect, the eReplication Server cannot be started. Under such conditions, you need to reconfigure ports and start the eReplication Server again. For details, see Changing Ports of the eReplication Server.

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

The eReplication Server is deployed in active/standby mode in the system. This section describes how to set the current eReplication as the standby server.

  1. Check whether the firewall is enabled.

    • If the firewall is disabled, check whether the firewall needs to be enabled. If you need to enable the firewall, perform related operations to enable the firewall. If you do not need to enable the firewall, go to 2.
    • If the firewall is enabled, enable the firewall port of the server on which the eReplication Server is installed by performing OceanStor BCManager 6.5.0 eReplication Communication Matrix. For details about how to enable the firewall ports, see Configuring the Firewall.

  2. Use PuTTY to log in as user root to the server where the eReplication Server is to be installed.

    NOTE:

    This section uses an operating system whose kernel version is Linux 3.0.76-0.11-default to explain how to install the eReplication Server in the kernel version Linux. In Linux, the commands vary with versions.

  3. Run the following command to prevent PuTTY from exiting due to session timeout:

    TMOUT=0

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Copy the eReplication Server package to the server where the eReplication Server is to be installed.

    The name of the directory where the eReplication Server installation package resides can contain only letters, digits, underscores (_), hyphens (-), periods (.), and single spaces.

  5. Go to the directory where the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package resides.
  6. Run the following command to decompress the package. Place the decompressed folders and files in the directory where the package resides.

    tar -zxvf OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz

  7. Install the eReplication Server.
    1. Run the following command to execute the installation script:

      sh cliInstall.sh

      The following command output is displayed:

      The operation system is : Linux 3.0.76-0.11-default
      Step 1:
      The install path is: /opt/BCManager. Are you sure? (y/n): [y]
      
      NOTE:

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

    2. Type y and press Enter, or directly press Enter.

      The following command output is displayed:

      Step 2:
      The data files path: [/opt/gs/app/data]
      
      Enter the database port [6432]:
      

    3. Set the database port number and press Enter. You can directly press Enter, and the port number is 6432 by default.

      NOTE:

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Please input the database admin password :

    4. Set the database administrator password. The database administrator has the highest database permission, including all system and object permissions. The administrator account has been created by the system by default. The user name is GaussDB and the default password is Gaussdb_123. During installation, you need to change the password to a user-defined one and record it for future maintenance. Press Enter.

      NOTE:
      The new password must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits
      • Cannot be the same as the default database password Gaussdb_123.

      The following command output is displayed:

      Please confirm the database admin password :

    5. Type the database administrator password again and press Enter.

      The following command output is displayed:

      Enter the BCManager DBA user [RDDBUser]:
      

    6. Set the user name used to eReplication access the database and press Enter. Alternatively, directly press Enter, and the user name is RDDBUser by default.

      The following command output is displayed:

      Please input the password for BCManager DBA user:

      User names and passwords of the BCManager DBA on the active and standby servers must be consistent.

      NOTE:

      The user name of the BCManager DBA contains four to eight letters.

      The password of the BCManager DBA user must meet the following complexity requirements:
      • Contains 8 to 15 characters.
      • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
      • Contains at least two of the following types of characters:
        • Uppercase letters
        • Lowercase letters
        • Digits

    7. Set the password for the account used to access the database and press Enter.

      The following command output is displayed:

      Please confirm the password for BCManager DBA user:

    8. Enter the password for accessing the database and press Enter.

      The following command output is displayed:

      Step 3:
      
           NAME                                   DESCRIPTION                                                          VERSION        SIZE      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      1.   Application DR Management Component    Provided DR protection for applications, such as Oracle.              7.0.3          80MB      
      2.   VMware vSphere DR Management Component Provided DR protection for VMware vSphere.                            7.0.3          80MB      
      3.   FusionSphere DR Management Component   Provided DR protection for FusionSphere.                              7.0.3          80MB      
      
      ------------------------------------------------------------------------------------------------------------------------------------
      
      Enter the serial numbers of modules to be installed, and separate the serial numbers with blank spaces.
      All modules will be installed by default.

    9. Select the components that you want to install. Table 2-14 describes the components to be installed.

      Table 2-14  Description of the components to be installed

      Component

      Description

      Application DR Management Component

      This type of component provides DR for Oracle, IBM DB2, Microsoft SQL Server, Microsoft Exchange Server, LUNs, local file systems, NAS file systems, and the InterSystems Caché application.

      VMware vSphere DR Management Component

      This type of component provides DR for VMware vSphere.

      FusionSphere DR Management Component

      This type of component provides DR for FusionSphere.

      • Enter component serial numbers and separate them with spaces. Then press Enter to install them.
      • If you press Enter without entering any component serial number, all components are installed.

      The following command output is displayed:

      Required space:  1264(M)
      Free space:  28.89(G)
      Step 4:
      Select this IP address as the listening IP address of the DR system.
      ==============================================================================
       [1] eth0  MAC=00:50:56:B1:04:9A  IP=192.168.28.58  NetMask=255.255.0.0
       [2] eth1  MAC=00:50:56:B1:08:EF  IP=192.168.28.59  NetMask=255.255.0.0
      ==============================================================================

    10. Select an IP address and press Enter.

      The following command output is displayed:

      Please input the listening port [9443]:

    11. Enter the listening port number and press Enter. Alternatively, directly press Enter to use default listening port 9443.

      The port ID ranges from 1024 to 65535.

      The following command output is displayed:

      Current IP configuration:
      ----------------------------------------------------------------------------------------
      
      [1] MAC=00:50:56:B1:73:A1  Service Management IP=192.168.28.58
      
      ----------------------------------------------------------------------------------------

    12. Select a deployment mode for the eReplication Server.

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

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

    14. Input 2 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.

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

    16. Ensure that the data replication link information is 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:

      Start install software. Please wait...
      Installation is completed.
      
      *************Install Succeed!*************
      
      
      access_privilege success.
      
      Are you sure to start up the software immediately? (y/n):

  8. Enter y and press Enter to start the eReplication Server.

    Startup succeeds if the following command output is displayed:

    System is starting. Please wait...
    10% complete...
    20% complete...
    30% complete...
    40% complete...
    50% complete...
    60% complete...
    70% complete...
    80% complete...
    90% complete...
    100% complete...
    
    System started completely.
    NOTE:

    If you do not want to start the eReplication Server immediately, enter n. If you want to start the OceanStor BCManager Server in the follow-up procedures, you can go to the /opt/BCManager/Runtime/bin directory and run the sh startSystem.sh command to start it.

    Some ports are occupied when the eReplication Server is being started. If those ports are occupied by other applications or the format of port numbers is incorrect, the eReplication Server cannot be started. Under such conditions, you need to reconfigure ports and start the eReplication Server again. For details, see Changing Ports of the eReplication Server.

Follow-up Procedure
  1. After the installation is complete, wait 5 to 10 minutes. After the eReplication Server is started, perform operations described in Log In To eReplication. If you can log in to eReplication, the installation is successful.
  2. To ensure system security, you are advised to periodically change the passwords of DRManager, ICUser, RDDBUser, and GaussDB after the eReplication Server is installed using software package. For details about how to change passwords, see eReplication Account Management.
  3. For security purposes, users may want to use an SSL certificate issued by a third-party certification authority. The eReplication Server allows users to replace users' Tomcat certificates as long as they provide authentication certificates and private-public key pairs. For details about how to replace certificates, see Replacing Tomcat Certificates on the eReplication Server.

GUI

This section describes how to install the eReplication Server using the GUI.

Context

  • If the eReplication Server is deployed in HA mode, the restrictions are as follows:
    • If the system is to be deployed in HA mode, you need to deploy one eReplication Server on each DC, and configure cross-site HA between the two eReplication Servers.
    • The management node HA can only be deployed in Linux operating system and the HA active/standby mode is supported. In this mode, when deploying the local server as active (standby) server, you need to deploy the peer server as the standby (active) server.
    • If the system is to be deployed in HA mode, the two servers equipped with the eReplication Server must be on the same subnet. And the two servers must be installed using the same installation package.
    • When HA is being configured, the floating IP address cannot be the management IP address of the host. Otherwise, you cannot access the server after the HA switchover.
  • If the eReplication Server is deployed in active/standby mode, the restrictions are as follows:
    • If the system is to be deployed in active/standby mode, you need to deploy one eReplication Server on each DC.
    • The active/standby mode can be deployed only in the Linux operating system and the active/standby mode that one active server and one standby server are deployed is supported. In this mode, when deploying the local server as active (standby) server, you need to deploy the peer server as the standby (active) server.
    • If the eReplication Server is deployed in active/standby mode, the data replication link between the two servers where the eReplication Server is installed must be connected. In addition, the two servers must be installed using the same installation package.
NOTE:
  • This section uses the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package as an example. The version number in the preceding software package varies with site conditions.
  • If you need to reconfigure mode after installing the eReplication Server, refer to Configuring a Deployment Mode.

Procedure

  1. Check whether the firewall is enabled.

    • If the firewall is disabled, check whether the firewall needs to be enabled. If you need to enable the firewall, perform related operations to enable the firewall. If you do not need to enable the firewall, go to 2.
    • If the firewall is enabled, enable the firewall port of the server on which the eReplication Server is installed by performing OceanStor BCManager 6.5.0 eReplication Communication Matrix. For details about how to enable the firewall ports, see Configuring the Firewall.

  2. Use PuTTY to log in as user root to the server where the eReplication Server is to be installed.

    NOTE:

    This section uses Linux 2.6.32-358.el6.x86_64 as an example to explain how to install the OceanStor BCManager Server using the GUI. In Linux, the commands vary with Linux versions.

  3. Run the following command to prevent PuTTY from exiting due to session timeout:

    TMOUT=0

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Copy the eReplication Server package to the server where the eReplication Server is to be installed.

    The name of the directory where the eReplication Server installation package resides can contain only letters, digits, underscores (_), hyphens (-), periods (.), and single spaces.

  5. Go to the directory where the OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz package resides.
  6. Run the following command to decompress the package. Place the decompressed folders and files in the directory where the package resides.

    tar -zxvf OceanStor_BCManager_6.5.0_eReplication_for_SLES.tar.gz

  7. Run the following command to execute the installation script:

    sh installSystem.sh

  8. Select I have read the copyright statement and agree to the terms and click Next.



  9. Select the components that you want to install and click Next . Table 2-15 describes the components to be installed.



    Table 2-15  Description of the components to be installed

    Component

    Description

    Base management components

    This type of components offer functions such as system settings, alarm monitoring, DR protection, configuration restoration, and DR report and provide an integration environment for running DR service components.

    FusionSphere DR management component

    This type of component provides DR for FusionSphere.

    Application DR management component

    This type of component provides DR for Oracle, IBM DB2, Microsoft SQL Server, Microsoft Exchange Server, LUNs, local file systems, NAS file systems, and the InterSystems Caché application.

    VMware vSphere DR management component

    This type of component provides DR protection for VMware vSphere.

    NOTE:

    Base management components are mandatory and other three types of components are optional. You can install necessary components based on service requirements.

  10. View the basic system information, configure HTTPS port and click Recheck to ensure the port is available. Then click Next.



  11. Set the database file directory and database parameters, and click Next.Table 2-16lists the database parameter configurations.



    Table 2-16  Database parameter configurations

    Parameter

    Description

    Setting

    Target folder

    The directory where database files reside

    [Value range]

    The folder name contains only letters, digits, hyphens (-), underscores (_), and periods (.).

    [Default value]

    /opt/gs/app/data

    Port

    Database port number

    [Value range]

    1024 to 65535

    [Default value]

    6432

    Admin Password

    The database administrator has the highest database permission, including all system and object permissions. The administrator account has been created by the system by default. The user name is GaussDB and the default password is Gaussdb_123. During installation, you need to change the password to a user-defined one and record it for future maintenance. If you need to change the password in the future, see Changing the Password of a Database Account.

    [Value range]

    • Contains 8 to 15 characters.
    • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
    • Contains at least two of the following types of characters:
      • Uppercase letters
      • Lowercase letters
      • Digits
    • Cannot be the same as the default database password Gaussdb_123.

    BCManager DBA

    eReplication database access user name
    NOTICE:

    When HA is started, usernames of BCManager DBA on active and standby servers must be consistent.

    [Value range]

    The user name contains four to eight letters.

    [Default value]

    RDDBUser

    DBA Password

    eReplication database access password
    NOTICE:

    When starting HA, passwords of BCManager DBA on active and standby servers must be consistent.

    [Value range]

    • Contains 8 to 15 characters.
    • Contains at least one special character from ~!@#$%*-_=+\[{}];:,./?
    • Contains at least two of the following types of characters:
      • Uppercase letters
      • Lowercase letters
      • Digits

  12. Set system parameters and click Next. Table 2-17 describes the setting of system parameters.



    Table 2-17  Description about the setting of system parameters

    Parameter

    Description

    Setting

    Target folder

    Directory for storing BCManager software.

    [Value range]

    The folder name contains only letters, digits, hyphens (-), underscores (_), and periods (.).

    [Default value]

    /opt/BCManager/Runtime

    IP address

    Service management IP address. Used to log in to eReplication to connect to service systems, such as hosts, storage devices, FusionSphere OpenStack, and vCenter servers. The service management IP address must be in the same network segment as the devices managed by eReplication.

    [Value range]

    The service management IP address must be a fixed IP address.

    HTTPS port

    Port number used by the service management service.

    [Value range]

    1024~65535

    [Default value]

    9443

    NOTE:

    The database file directory name of the eReplication Server can contain only letters, digits, hyphens (-), underscores (_), and periods (.). You are advised not to install the OceanStor BCManager Server on a system disk.

  13. Configure an installation mode and related parameters. and press Next.



    • If Enable the system service DR is not selected, the system will be deployed in single-node mode.
    • If you select Enable the system service DR and set DR Mode to HA, the system will be deployed in HA mode. Table 2-18 describes the configuration of parameters.
      Table 2-18  Parameter description of HA configuration

      Parameter

      Description

      Setting

      The role

      Sets eReplication as active server or standby server.

      [Example]

      active

      The local node name

      Specifies the local node name.

      [Value range]

      The name contains 1 to 39 characters. The characters can only include letters, digits, underscores (_), and hyphens (-).

      [Example]

      local

      The peer node name

      Specifies the peer node name. The peer node name cannot be the same as the local node name.

      [Value range]

      The name contains 1 to 39 characters. The characters can only include letters, digits, underscores (_), and hyphens (-).

      [Example]

      peer

      Floating IP Address

      Specifies the IP address used to provide DR services. If the floating IP address is not set, enter the floating IP address planned in advance.
      NOTICE:

      The service management floating IP address cannot be the management IP address of the host. Otherwise, you cannot access the server after the HA switchover.

      [Value range]

      • This IP address and the system management IP address must be in the set network segment.
      • This IP address must be different from the heartbeat link IP address, file synchronization links and the gateway IP address.

      [Example]

      192.168.10.10

      Heartbeat link

      Connects the active server to the standby server (usually in HA scenarios). Heartbeat signals will be sent between active and standby servers through heartbeat links to notify the peer end of local end's running status.

      [Value range]

      • The number of heartbeat links ranges from 1 to 4. This IP address must be the local IP address, and the local IP address must be different from the peer IP address.
      • The port ID ranges from 1024 to 65535.
      • The local and peer IP addresses cannot be the same as the floating IP address.
      • The local and peer IP addresses in different links cannot be the same.

      File synchronization link

      Links used by the active and standby servers for file synchronization.

      [Value range]

      • The number of file synchronization links ranges from 1 to 4. This IP address must be the local IP address, and the local IP address must be different from the peer IP address.
      • The port ID ranges from 1024 to 65535.
      • The local and peer IP addresses cannot be the same as the floating IP address.
      • The local and peer IP addresses in different links cannot be the same.

      Gateway IP address

      Plays a key role in HA arbitration switching process.

      [Value range]

      • The number of the gateway IP addresses ranges from 1 to 4.
      • The gateway IP address cannot be the same the floating IP address.
    • If you select Enable the system service DR and set DR Mode to Active/Standby, the system will be deployed in HA mode. Table 2-18 describes the configuration of parameters.
      Table 2-19  Parameters in active/standby mode

      Parameter

      Description

      Setting

      Role

      Set current eReplication to active (active) or standby (standby) server.

      [Example]

      active

      File synchronization link

      Link used by the active and standby servers for data synchronization. You need to set both Local IP address and Peer IP address.

      [Value range]

      The port number ranges from 1024 to 65535.

  14. Confirm the information and click Next.

  15. The system starts to install BCManager. This process takes 5 to 10 minutes.After the installation and initialization are complete, click OK in the dialog box that is displayed. The start process takes approximately three minutes.

    NOTE:

    If Start up the BCManager software immediately is deselected, you can go to the /opt/BCManager/Runtime/bin directory and run the sh startSystem.sh command to start it.

  16. After the service is started, click OK in the dialog box that is displayed.

    Some ports are occupied when the eReplication Server is being started. If those ports are occupied by other applications or the format of port numbers is incorrect, the eReplication Server cannot be started. Under such conditions, you need to reconfigure ports and start the eReplication Server again. For details about how to change ports of the eReplication Server, see Changing Ports of the eReplication Server.

    NOTE:
    • Username is admin and Password is Admin@123, by default.
    • For security purposes, log in to the eReplication and change the initial password as soon as possible. For details, see Log In To eReplication.

Follow-up Procedure

  1. After the installation is complete, wait 5 to 10 minutes. After the eReplication Server is started, perform operations described in Log In To eReplication. If you can log in to eReplication, the installation is successful.
  2. To ensure system security, you are advised to periodically change the passwords of DRManager, ICUser, RDDBUser, and GaussDB after the eReplication Server is installed using software package. For details about how to change passwords, see eReplication Account Management.
  3. For security purposes, users may want to use an SSL certificate issued by a third-party certification authority. The eReplication Server allows users to replace users' Tomcat certificates as long as they provide authentication certificates and private-public key pairs. For details about how to replace certificates, see Replacing Tomcat Certificates on the eReplication Server.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10797

Downloads: 55

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