Installing the eReplication Server (Linux) Using a Software Package

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:
     • Enterprise

       Software Digital Signature (OpenPGP) Verification Tool

     • Carrier

       Digital Signature Verification Method

• 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 BCManager 8.5.1 eReplication Security Configuration Hardening Guide. For details about how to obtain the document, see Obtaining Installation Packages and Documentation.
• 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.

Context

• To ensure normal operation of the remote DR function, ensure that the same eReplication Server is installed at the production and DR centers.
• 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.

The Linux operating system provides the CLI execution mode. The active/standby mode is recommended. Based on network conditions and HA requirements, select the active/standby mode that can be automatically restored or manually restored.