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).
Deployment Environment Requirements

Deployment Environment Requirements

This section describes hardware and software environments required for deploying the maintenance terminal, eReplication Server, and eReplication Agent to ensure that eReplication can work correctly.

  • The eReplication Server can be deployed on physical servers and mainstream virtualization platforms, such as VMware and Hyper-V.
  • To ensure the stability of DR and backup, you are advised to deploy the eReplication Server on an independent server. Note that the eReplication Server and the service host cannot be deployed on the same server.
  • The time zones of the servers where the eReplication Server is deployed at the production and DR sites must be the same. In addition, the same time source has been configured, and the time has been synchronized.
  • To prevent time deviation caused by different time zones, ensure that the time zone of the maintenance accessing eReplication is the same as that of the server where the eReplication Server is deployed.
  • To deploy the eReplication Server on a VM, ensure that the eReplication Server exclusively occupies the VM resources.

Maintenance Terminal Requirements

Table 2-3 describes maintenance terminal requirements.
Table 2-3  Maintenance terminal requirements

Item

Requirement

Operating system

English operating systems

Browser

  • Internet Explorer 9.0 to 11.0
  • Firefox 26.0 to 57.0
  • Chrome 28.0 to 62.0

Flash plug-in

Adobe Flash Player 10.2 or later

After you log in to eReplication, the system automatically checks whether the Flash plug-in is installed on the current browser. If the Flash plug-in is not installed or an earlier version of Flash plug-in is installed, functions such as alarm sound notification and DR topology may be affected. Then you need to go to https://get.adobe.com/flashplayer/?loc=en to download the qualified Flash plug-in and install it.

Network

Ensure that the maintenance terminal can access the physical server or VM where the eReplication Agent is to be installed. Besides, the IP address of the maintenance terminal must be a free IP address.

eReplication Deployment Environment Requirements

eReplication is composed of the eReplication Server and eReplication Agent. Table 2-4 describes their deployment environment requirements.

Table 2-4  eReplication Server environment specifications

Specifications

Requirement

Operating system

  • SUSE Linux Enterprise Server 11 SP1/SP2/SP3 x86_64
  • SUSE Linux Enterprise Server 12 SP2 x86_64
  • RedHat Linux 6.4 x86_64
  • RedHat Linux 7.2/7.3 x84_64
  • Microsoft Windows Server 2008 R2 Standard/Enterprise/Datacenter x86_64
  • Microsoft Windows Server 2012/2012 R2 Standard x86_64
  • Microsoft Windows Server 2016 x86_64
NOTICE:
For RedHat Linux 7.2/7.3 x84_64, when a user installs the operating system, Base Environment in SOFTWARE SELECTION does not support the default Minimal Install option. You are advised to select Server with GUI.

CPU

  • Minimum configuration: 2-core 1.6 GHz CPU
  • Standard configuration: 4-core 1.6 GHz CPU or higher

Memory

  • Minimum configuration: 4 GB DDR
  • Standard configuration: 8 GB DDR or higher
NOTE:

If the physical memory capacity is 4 GB, the available physical memory capacity must be 2 GB at least. If the physical memory capacity is 8 GB, the available physical memory capacity must be 4 GB at least.

If the installation environment is a VM, the VM cannot use dynamic memory allocation.

If the installation environment is a Linux operating system, the requirements on swap are as follows:
  • If the memory capacity ranges from 4 GB to 16 GB, the swap value must be the same as the memory capacity.
  • If the memory capacity is greater than 16 GB, the swap value must be 16 GB.

Free disk space

10 GB or higher

The minimum free disk space required by a service host

For a FusionSphere OpenStack private cloud DR scenario, check whether partitions of the eReplication Server operating system meet requirements in Table 2-5 and Table 2-6. If any requirement is not met, perform modification as required.
NOTE:

LVM partitions must be used. If you use raw partitions, software may fail to be installed due to insufficient logical partition space.

Bandwidth of the management network

2 Mbit/s or higher

In the Disaster Recovery Data Center Solutions (Active-Passive Mode) and (Geo-Redundant Mode), if two eReplication Servers are deployed. The bandwidth of the management network between the eReplication Servers is 2 Mbit/s or higher.

Deployment mode

  • Centralized deployment:

    Only one eReplication management server can be deployed, and the server must be interconnected to the management network of data centers.

  • Distributed deployment:

    In the Disaster Recovery Data Center Solutions (Active-Passive Mode) and (Geo-Redundant Mode), at most two eReplication management servers can be deployed and management networks between the servers must be interconnected.

Table 2-5  Requirements for primary partitions

Partition

Free Capacity

Installation Point

/

≥ 25 GB

/

swap

16 GB

swap

Table 2-6  Requirements for logical partitions

Partition

Free Capacity

Installation Point

/tmp

≥ 5 GB

/tmp

/home

≥ 1 GB

/home

/var

≥ 30 GB

/var

/var/log

≥ 10 GB

/var/log

/var/log/audit

≥ 10 GB

/var/log/audit

/opt

≥ 60 GB

/opt

Table 2-7  eReplication Agent environment specifications

Specifications

Requirement

Operating system

  • Windows
    • Microsoft Windows Server 2003 for x86_64
    • Microsoft Windows Server 2008 SP2 for x86_64
    • Microsoft Windows Server 2008 R2 SP1 for x86_64
    • Microsoft Windows Server 2012 for x86_64
    • Microsoft Windows Server 2012 R2 for x86_64
  • Linux
    • SUSE Linux Enterprise Server 10 SP1/SP2 for x86_64
    • SUSE Linux Enterprise Server 11 SP1/SP2/SP3 for x86_64
    • RedHat Linux 6.4/6.5/6.6/6.7/6.8/7.0/7.1/7.2/7.3 for x86_64
    • Meditation Rocky 6.0.3/6.0.4 for x86_64
    • Oracle Enterprise Linux 6.4/6.5/6.9/7.5 for x86_64
    • iSoft Server OS v3.0 x86_64
  • AIX

    AIX 7.1 for 64-bit

  • HP-UX

    HP-UX 11i V3

  • Solaris
    • Solaris 10 SPARC (64bit)
    • Solaris 11.2 SPARC (64bit)

Physical memory

Minimum configuration: 128 MB

The minimum physical memory required by a service host

Free disk space

Minimum configuration: 500 MB

The minimum free disk space required by a service host

Deployment mode

Deployed on an application server

eReplication must be deployed on application servers at both the production site and DR site.

Requirements for Configuring Permission on Installation Packages and Directories

To decompress an installation package, note the following:
  • The name of the directory where the installation package resides can contain only letters, digits, underscores (_), hyphens (-), and one space.
  • The package cannot be decompressed to the installation directory of eReplication. In Linux, the installation path of the eReplication Server is fixed to /opt/BCManager.

Before installing the eReplication Server in Linux, ensure that permission of directories at each level (755 by default) listed in Table 2-8 and that of the / root directory are properly assigned. Otherwise, users ICUser, Tomcat, and GaussDB have no operation permission on installation directories of the eReplication Server, interrupting services. In this manner, you are advised to set permission of these directories to 755.

Table 2-8  Description of directory permission

Directory

Description

Impact

/usr/local

GaussDB database installation directory

If the permission is improper, the database cannot be normally started.

/usr/lib

Directory for saving file lib of the GaussDB database

If the permission is improper, the database may fail to be normally started.

/usr/lib64

Directory for saving file lib of the GaussDB database

If the permission is improper, the database may fail to be normally started.

/opt

Directory under which the eReplication Server is installed and data of the GaussDB data is saved

If the permission is improper, eReplication may unable to run properly.

/usr/sbin

Save directory of logs collected by running the DataCollect command.

If the permission is improper, eReplication may fail to collect logs.

NOTE:
  • Run the ls -ld directory name command to check the permission information about a directory.
  • Run the ll command to check owners and permission information about the files.
Set users' operation permission on installation directories of eReplication. The following details the process using directory /opt as an example:
  1. Log in as user root to the server where eReplication is to be installed.
  2. Run the cd /opt command to go to directory /opt.
  3. Run the chmod 755 /opt command to set permission on the directory to 755.

Requirements for Configuring the Host File

Before eReplication Server installation, the permission on the host file must meet the following configuration requirements:

Ensure host file hosts contains information about the mapping between the management IP address of the eReplication Server and the host name.
  • If the mapping is not configured, the eReplication service cannot be started after eReplication installation.
  • If the mapping is improperly configured, the eReplication Server cannot be logged in after it has been installed and started.

To configure the mapping between the management IP address of the eReplication Server and the host name, perform the following steps:

Windows:
  1. Log in to the eReplication Server as an administrator.
  2. Go to directory C:\Windows\System32\drivers\etc.
  3. Open file hosts.
  4. Add the mapping between the management IP address of the eReplication Server and the host name to file hosts.
    Add the following content (management IP address 192.168.10.10 and host name host01 are used as examples) into file hosts:
    192.168.10.10 host01
    NOTE:

    Open the CLI, and run the hostname command to check the host name.

  5. Save the changes and close the file.

Linux:

  1. Log in to the eReplication Server server as user root.
  2. Run the cd /etc command to go to the directory where file hosts resides.
  3. Run the vi hosts command to open file hosts.
  4. Press i to enter the editing mode and edit file hosts.
    Add the following content (management IP address 192.168.10.10 and host name host01 are used as examples) into file hosts:
    192.168.10.10 host01
    NOTE:

    Run the hostname command to check the host name.

  5. Press Esc, and run the :wq! command to save the change and exit.

Requirements for Configuring the Encryption Algorithm

For Linux, to enhance operating system security, you are advised to set sha256 as the password encryption algorithm for operating systems of physical servers and VMs on which the eReplication Server and eReplication Agent are to be installed. Otherwise, passwords of the ICUser, DRManager, and rdadmin created during the software installation may be encrypted using MD5 by default. MD5 is a less secure encryption algorithm that may be cracked. To change the encryption algorithm for operating systems, perform the following steps:

SUSE Linux (SUSE Linux 11 for example):

  1. Log in as user root to the server where the eReplication Server or eReplication Agent is to be installed.
  2. Run the vi /etc/default/passwd command and press Insert to edit the passwd file, and check the current encryption algorithm of the operating system (the value of CRYPT).
    • If the current encryption algorithm is sha256 or sha512, go to 4.
    • If the current encryption algorithm is not sha256 or sha512, go to 3.
  3. Change the value of CRYPT to sha256.
  4. Add the explanatory note # in the CRYPT_FILES=blowfish field and make the parameter is invalid.
  5. Press Esc, and run the :wq! command to save the change and exit.
Red Hat Linux:
  1. Log in as user root to the server where the eReplication Server or eReplication Agent is to be installed.
  2. Run the authconfig --test | grep hashing command, and check the current encryption algorithm of the operating system.
    • If the current encryption algorithm is sha256 or sha512, end the operation.
    • If the current encryption algorithm is not sha256 or sha512, go to 3.
  3. Run the authconfig --passalgo=sha256 --update command to change the encryption algorithm to sha256.
NOTE:

If the current encryption algorithm of the operating system is not modified before installing the eReplication software, you need to modify the password of the ICUser, DRManager and rdadmin user and make the parameter is invalid. For details, refer to eReplication Account Management.

Requirements on User IDs

Along with the installation of the eReplication Server, three operating system accounts are created and will occupy three UIDs (namely 20000, 20001, and 20002) and GID 20000, by default. If the three UIDs and the GID is being occupied before the installation, the eReplication Server will fail to be installed.

You can run the following two commands to check whether the current system environment meets the requirements. If both the two commands have no output, the environment meets the requirements.
cat /etc/passwd | awk -F: '{print $1, $3}' | grep -wE "20000|20001|20002" | sed 's/ //g' | grep -vE "ICUser20000|Tomcat20001|GaussDB20002"
cat /etc/group | awk -F: '{print $1, $3}' | grep -w 20000 | grep -v LEGO
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10768

Downloads: 55

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