配置备份服务器-九游平台

前提条件

• 安装前准备请提前规划备份服务器的相关网络平面参数。
• 已准备跨平台远程访问工具如“putty”。
• 已获取ebackup服务器“root”账号的登录密码。

配置ebackup备份服务器

1. 以“root”账号登录待配置的ebackup服务器。

   “root”账号初始密码为“cloud12#$”。

   使用跨平台访问工具登录，或在vmware vsphere client工具中的控制台登录。

2. 执行cd 备份软件安装包所在目录命令进入初始配置脚本目录。

   备份软件安装包所在目录为/opt/ebackup_8.0.0-lhc01/action。

3. 执行sh ebackup_utilities.sh config命令，开始进行初始化配置。

   回显如下信息。

   please select network type for this machine:
    1.ipv4
    2.ipv6

4. 输入“1”，按“enter”。

   1
   please select a role for this machine:
    1.backup server 
    2.backup proxy 
    3.backup manager 
    4.backup workflow server 

5. 输入“1”，按“enter”。

   1
   ===================================================================================================
   note:
   in the following steps you will be required to configure four network planes for ebackup.
   the definition of each network plane is as follows:
   backup management plane: the communication plane for ebackup to provide external services.
   internal communication plane: the communication plane between backup server and backup proxy.
   production management plane: the communication plane between ebackup and the management plane of the production end.
   storage plane: the communication plane between ebackup and the storage plane of the production end and communication plane between ebackup and backup storage.
   ====================================================================================================
   set network adapter for 'backup management' network plane:
   [1] bond1 mac=28:6e:d4:88:c6:f2 ip=192.168.1.10 mask=255.255.254.0 
   [2] bond2 mac=28:6e:d4:88:c6:f3 ip=10.10.1.10 mask=255.255.254.0 
   which network adapter from the above list would you like to bind to the 'backup management' network plane?

6. 配置备份服务器网络平面。
   

   此处需要为备份服务器的五个网络平面绑定相应的网卡，具体绑定哪张网卡请根据中的网络规划进行选择。

   本节以备份服务器配置两张网卡，备份管理平面、生产管理平面、内部通信平面、生产存储平面绑定在同一张网卡，备份存储平面绑定在一张网卡为例说明。

   1. 选择备份管理平面需要绑定的网卡，按“enter”。
      

      如果选择bond1作为备份管理平面需要绑定的网卡，请输入“1”。

      1
      set network adapter for 'internal communication' network plane:
      [1] bond1 mac=28:6e:d4:88:c6:f2 ip=192.168.1.10 mask=255.255.254.0 
      [2] bond2 mac=28:6e:d4:88:c6:f3 ip=10.10.1.10 mask=255.255.254.0 
      which network adapter from the above list would you like to bind to the 'internal communication' network plane?

   2. 选择内部通信平面需要绑定的网卡，按“enter”。

      1
      set network adapter for 'production management' network plane:
      [1] bond1 mac=28:6e:d4:88:c6:f2 ip=192.168.1.10 mask=255.255.254.0 
      [2] bond2 mac=28:6e:d4:88:c6:f3 ip=10.10.1.10 mask=255.255.254.0 
      which network adapter from the above list would you like to bind to the 'production management' network plane?

   3. 选择生产管理平面需要绑定的网卡，按“enter”。

      1
      set network adapter for 'production storage' network plane:
      [1] bond1 mac=28:6e:d4:88:c6:f2 ip=192.168.1.10 mask=255.255.254.0 
      [2] bond2 mac=28:6e:d4:88:c6:f3 ip=10.10.1.10 mask=255.255.254.0 
      which network adapter from the above list would you like to bind to the 'production storage' network plane?    

   4. 选择生产存储平面需要绑定的网卡，按“enter”。

      1
      set network adapter for 'backup storage' network plane:
      [1] bond1 mac=28:6e:d4:88:c6:f2 ip=192.168.1.10 mask=255.255.254.0 
      [2] bond2 mac=28:6e:d4:88:c6:f3 ip=10.10.1.10 mask=255.255.254.0 
      which network adapter from the above list would you like to bind to the 'backup storage' network plane?

   5. 选择备份存储平面需要绑定的网卡，按“enter”。

      2
      enter a floating ip address that is in the same network segment as the internal communication plane.

   6. 设置浮动ip地址。

      浮动ip地址为内部通信平面浮动ip地址。请确保浮动ip地址跟内部通信平面ip地址在同一网段中，且未被使用。

      回显如下信息，表示配置成功。

      192.168.1.12
      configuration succeeded.
      grep: this version of pcre is compiled without utf support
      the ebk_accelerator agent of oceanstor bcmanager ebackup was started successfully.
      start:ebk_accelerator service succeeded.
      start reload gaussdb
      grep: this version of pcre is compiled without utf support
      the ebk_backup agent of oceanstor bcmanager ebackup was started successfully.
      start:ebk_backup service succeeded.
      grep: this version of pcre is compiled without utf support
      the ebk_copy agent of oceanstor bcmanager ebackup was started successfully.
      start:ebk_copy service succeeded.
      grep: this version of pcre is compiled without utf support
      the ebk_delete agent of oceanstor bcmanager ebackup was started successfully.
      start:ebk_delete service succeeded.
      grep: this version of pcre is compiled without utf support
      the ebk_mgr agent of oceanstor bcmanager ebackup was started successfully.
      start:ebk_mgr service succeeded.
      grep: this version of pcre is compiled without utf support
      the ebk_restore agent of oceanstor bcmanager ebackup was started successfully.
      start:ebk_restore service succeeded.
      grep: this version of pcre is compiled without utf support
      the ebk_vmware agent of oceanstor bcmanager ebackup was started successfully.
      start:ebk_vmware service succeeded.
      service hcp start:completed
      you can access the ebackup ui using the following link.
       https://192.168.1.10:8088 or 192.168.1.10
      alternatively, you can access the ebackup cli through ssh session.

7. 依次执行以下命令进行安全加固。

   加固后禁止使用“root”账号直接登录，请使用“hcp”账号登录，“hcp”账号的初始密码为“pxu9@ctunov17!”。

   cd /opt/huawei-data-protection/ebackup/bin/standardhardening

   echo -e "yes\nyes\n"|./standardsusehardening.sh

   

   • 执行该命令会重启ebackup服务器，如需登录ebackup服务器请您稍后重试。
   • 执行安全加固后，执行date命令查看当前时间，需要确保当前时间与选择目标上云region的时间保持一致，如果偏差 10min以上可能会导致备份失败。
8. （可选）如果备份上云的带宽小于100mbits，可能会因网络质量导致备份失败，为了降低失败概率，可以执行如下命令，优化部分参数：

   vim /opt/huawei-data-protection/ebackup/microservice/ebk_vmware/conf/hcpconf.ini

   查找并修改如下三个参数

   productstoragememorypoolblocknum 从64修改为8

   backupstoragememorypoolblocknum 从64修改为8

   commontaskusingmaxthread4backup 从8修改为2

   执行上述参数修改后，执行如下命令重启进程生效：

   cd /opt/huawei-data-protection/ebackup/microservice/ebk_vmware/script

   sh ebackup_stop.sh

   sh ebackup_start.sh

   

   备份带宽的规划应该与备份数据量正相关，如果备份数据量较大而带宽较小，可能会出现备份时间过长的情况。