经验总结：Veritas BE备份Redhat ES4排错一例

2019-11-04 01:32:21

字体：大中小

来源：转载

供稿：网友

Backup Exec RALUS备份 Redhat ES4出现的问题： 在Server端（192.168.66.100）和ES4（192.168.66.13）上分别安装好软件，安装完成后在ES4S的RALUS能够正常启动起来，通过server端的BEWS治理界面也能看到这个linux机器，但就是不能浏览，经验总结：Veritas BE备份Redhat ES4排错一例（图一）

本人也重新安装过两边软件，问题依然存在，在两台机器之间是没有防火墙的

  ralus.cfg内容如下：
  SOFTWARE/VERITAS/Backup Exec/Agent Browser/Tcpip/AdvertisementPort=6101
  Software/VERITAS/Backup Exec/Engine/Agents/Advertising Interval Minutes=60
  SOFTWARE/VERITAS/Backup Exec/Engine/Agents/Agent Directory List 1=192.168.66.100
  Software/VERITAS/Backup Exec/Engine/Logging/RANT NDMP Debug Level=0
  Software/VERITAS/Backup Exec/Engine/RALUS/Encoder=LATIN-1
  Software/VERITAS/Backup Exec/Engine/RALUS/SystemExclude1=/dev/*.*
  Software/VERITAS/Backup Exec/Engine/RALUS/SystemExclude2=/PRoc/*.*
  Software/VERITAS/Backup Exec/Engine/RALUS/SystemExclude3=/mnt/nss/pools/
  Software/VERITAS/Backup Exec/Engine/RALUS/SystemExclude4=/mnt/nss/.pools/

  ralusdebug内容如下：
  53c6c0 Fri Sep 8 16:45:16 2006: Starting BE Remote Agent
  53c6c0 Fri Sep 8 16:45:16 2006: Log file: ralusdebug
  53c6c0 Fri Sep 8 16:45:16 2006: No configuration file specified. Using default.
  53c6c0 Fri Sep 8 16:45:16 2006: Log to console: disabled
  53c6c0 Fri Sep 8 16:45:16 2006: Starting NDMP processor
  5af6bb0 Fri Sep 8 16:45:17 2006: FS_InitFileSys
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedsnt5.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedssql2.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedsxchg.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedsxese.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedsmbox.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedspush.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedsnote.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:17 2006: libbedsmdoc.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedssps2.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedsupfs.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedsshadow.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedsoffhost.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: loaded libbedsvx.so
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedsorcl.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedsagnt.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedssms.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: loaded libbedssmsp.so
  5af6bb0 Fri Sep 8 16:45:11 2006: libbedsra.so could not be loaded: 0x 2 (2)
  5af6bb0 Fri Sep 8 16:45:11 2006: Initializing FSs
  5af6bb0 Fri Sep 8 16:45:11 2006: Using 'LATIN-1' Encoding.
  5af6bb0 Fri Sep 8 16:45:11 2006: VXMS Initialization OK.
  5af6bb0 Fri Sep 8 16:45:11 2006: Listening on port 12000
  3f1ebb0 Fri Sep 8 16:45:11 2006: TCPSendAdvertisement: target=192.168.66.100
  3f1ebb0 Fri Sep 8 16:45:12 2006: TCPSendAdvertisement: inet_addr(192.168.66.100) returned s_addr=192.168.66.100
  3f1ebb0 Fri Sep 8 16:45:12 2006: TCPSendAdvertisement(linux) 192.168.66.13 [12000]
  3f1ebb0 Fri Sep 8 16:45:12 2006: Agent browser advertisement cycle complete. Advertisement interval is 60 minutes.

报错如下： 经验总结：Veritas BE备份Redhat ES4排错一例（图二）

经过多次调试排错，发现出现这个问题的原因并不在于软件和系统问题。最后发现是LINUX这边IPTABLE阻挡了连接请求。由此可见，我们往往把简单的问题想复杂了，从而犯下低级错误。此类技术工作还是需要一步一步扎实来做呀：）具体如下： http://seer.entsupport.symantec.com/docs/260695.htm 另外提示：还有就是以后在安装时候，假如出现问题,最好安装英文软件，这样报的错误也好在support站点上来搜索帮助。

上一篇：精华探讨关于双机、集群软件选择的基本方法

下一篇：经验：通过BackupExec重定向Oracle 8I数据库