Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Issus with Ralus Agent 5204.4

Created: 17 Aug 2011 | 12 comments

Hello,

We have updated the Backup Server 2010 R3 is installed on the Windows Server 2003 Enterprise. Now, it's 13.5204 version.

There is many computers witch work as remote agent on "Debian Linux 5"
We have few problems during the upgrade of RALUS 5204 agent version. In effect, the server connection with the Remote agent is not established.

There is the errror message on the Serveur:
Unable to connect to the NDMP server to the remote PC vic configured as Remote Media Agent

Then I am running the agent in debug mode with the following command:
 

./beremote - log-file log.txt

Here are the contents of the log.txt:

Voici le contenu du fichier log.txt:

2b52a600 Wed Aug 17 11:48:39 2011 : Starting BE Remote Agent
2b52a600 Wed Aug 17 11:48:39 2011 : Log file: log.txt
2b52a600 Wed Aug 17 11:48:39 2011 : No configuration file specified.  Using default.
2b52a600 Wed Aug 17 11:48:39 2011 : Log to console: disabled
2b52a600 Wed Aug 17 11:48:39 2011 : Successfully set the supplementary groups of the process
2b52a600 Wed Aug 17 11:48:39 2011 : Initialized locks for SSL callbacks
2b52a600 Wed Aug 17 11:48:39 2011 : Starting NDMP processor
2b52a600 Wed Aug 17 11:48:39 2011 : NDMPDMainThreadFunc spawned: grpid=1, tid=1082132832
40800960 Wed Aug 17 11:48:39 2011 : FS_InitFileSys
40800960 Wed Aug 17 11:48:39 2011 :   libbedsnt5.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedssql2.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsxchg.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsxese.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsmbox.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedspush.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsnote.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsmdoc.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedssps2.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedssps3.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsupfs.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsshadow.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   libbedsoffhost.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   loaded libbedsvx.so
40800960 Wed Aug 17 11:48:39 2011 :   libbedsdb2.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 :   loaded libbedsedir.so
40800960 Wed Aug 17 11:48:39 2011 :   libbedsvmesx.so could not be loaded: 0x       2 (2)
40800960 Wed Aug 17 11:48:39 2011 : Initializing FSs
40800960 Wed Aug 17 11:48:39 2011 : FS 1 failed to initialize: 0xE000FE46
40800960 Wed Aug 17 11:48:39 2011 : Function called: RMAN_InitFileSys
40800960 Wed Aug 17 11:48:39 2011 : Using 'UTF-8' Encoding.
40800960 Wed Aug 17 11:48:39 2011 : Using vfm path /opt/VRTSralus/VRTSvxms from config.
40800960 Wed Aug 17 11:48:39 2011 : Sucessfully set VFM_PRIVATE_ROOT env to /opt/VRTSralus/VRTSvxms.
40800960 Wed Aug 17 11:48:39 2011 : VFM_PRIVATE_ROOT was set with value /opt/VRTSralus/VRTSvxms
40800960 Wed Aug 17 11:48:39 2011 :      VXMS Initialization OK.
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <ext3> mounted at </>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <tmpfs> mounted at </lib/init/rw>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <proc> mounted at </proc>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <sysfs> mounted at </sys>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <usbfs> mounted at </proc/bus/usb>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <tmpfs> mounted at </dev>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <tmpfs> mounted at </dev/shm>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <devpts> mounted at </dev/pts>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <ext3> mounted at </data>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <ext3> mounted at </home>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <ext3> mounted at </tmp>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <ext3> mounted at </usr>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <ext3> mounted at </var>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <nfsd> mounted at </proc/fs/nfsd>
40800960 Wed Aug 17 11:48:39 2011 : Detected Mounted Filesystem: type <rpc_pipefs> mounted at </var/lib/nfs/rpc_pipefs>
40800960 Wed Aug 17 11:48:39 2011 : INFORMATIONAL: Zero value found for 'DisableRMAL' from ralus.cfg, allowing RMAL to initialize
40800960 Wed Aug 17 11:48:39 2011 : ndmpRun
40800960 Wed Aug 17 11:48:39 2011 : Successfully resolved the "ndmp" service to port: 12000 (host order)
40800960 Wed Aug 17 11:48:39 2011 : NrdsWatchThread spawned: grpid=1, tid=1090525536
40800960 Wed Aug 17 11:48:39 2011 : NrdsAdvertiserThread spawned: grpid=1, tid=1098918240
40800960 Wed Aug 17 11:48:39 2011 : NrdsAdvertiserThread spawned: grpid=1, tid=1107310944
40800960 Wed Aug 17 11:48:39 2011 : NDMP Daemon Running..
40800960 Wed Aug 17 11:48:39 2011 : BETCPListener successfully installed a signal handler for SIGTERM
40800960 Wed Aug 17 11:48:39 2011 : BETCPListener::BETCPListener: This system appears to be a Dual IP system
40800960 Wed Aug 17 11:48:39 2011 : BETCPListener::BETCPListener: Successfully set the IPV6_V6ONLY option, this listener may behave as Dual Stack listener
40800960 Wed Aug 17 11:48:39 2011 : Started NDMP Listener on port 12000
41802960 Wed Aug 17 11:48:49 2011 : NrdsAdvertiserThread: advertisement cycle started.
41802960 Wed Aug 17 11:48:49 2011 : RMAN_EnumSelfDLE: AgentConfig GetOracleDBNames returned error. If Oracle Agent is installed, please run AgentConfig.
41802960 Wed Aug 17 11:48:49 2011 : NrdsAdvertiserThread: EnumSelfDLE for file system 14 returned 0(0x0) and 0 DLEs
41802960 Wed Aug 17 11:48:49 2011 : BENetConfigEx: Successfully refreshed adapter information.
41802960 Wed Aug 17 11:48:49 2011 : NrdsAdvertiserThread: EnumSelfDLE for file system 22 returned 0(0x0) and 1 DLEs
41802960 Wed Aug 17 11:48:49 2011 : NrdsAdvertiserThread: Nrds Message Len : 151.
41802960 Wed Aug 17 11:48:49 2011 : VX_RemoveDLE: DestroyDLE()
41802960 Wed Aug 17 11:48:49 2011 : NrdsAdvertiserThread: Security is enabled!!!
41802960 Wed Aug 17 11:48:49 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
41802960 Wed Aug 17 11:48:49 2011 : BENetConfigEx: Successfully refreshed adapter information.
41802960 Wed Aug 17 11:48:49 2011 : ConnectToServerEndPoint: dest=192.168.1.251, service=6101
41802960 Wed Aug 17 11:48:49 2011 : ConnectToServerEndPoint: Failed to setup SSL context.
41802960 Wed Aug 17 11:48:49 2011 : NrdsAdvertiserThread: connect to target=192.168.1.251 port=6101 failed
41802960 Wed Aug 17 11:48:49 2011 : NrdsAdvertiserThread: Retrying in 60 seconds
42003960 Wed Aug 17 11:48:54 2011 : NrdsAdvertiserThread: negative (purge) advertisement cycle started.
42003960 Wed Aug 17 11:48:54 2011 : NrdsAdvertiserThread: no purge is pending.
42003960 Wed Aug 17 11:48:54 2011 : NrdsAdvertiserThread: negative (purge) advertisement cycle complete.  Waiting 240 minutes before advertising again.
41802960 Wed Aug 17 11:49:49 2011 : NrdsAdvertiserThread: Security is enabled!!!
41802960 Wed Aug 17 11:49:49 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
41802960 Wed Aug 17 11:49:49 2011 : BENetConfigEx: Successfully refreshed adapter information.
41802960 Wed Aug 17 11:49:49 2011 : ConnectToServerEndPoint: dest=192.168.1.251, service=6101
41802960 Wed Aug 17 11:49:49 2011 : ConnectToServerEndPoint: Failed to setup SSL context.
41802960 Wed Aug 17 11:49:49 2011 : NrdsAdvertiserThread: connect to target=192.168.1.251 port=6101 failed
41802960 Wed Aug 17 11:49:49 2011 : NrdsAdvertiserThread: Retrying in 60 seconds
41802960 Wed Aug 17 11:50:49 2011 : NrdsAdvertiserThread: Security is enabled!!!
41802960 Wed Aug 17 11:50:49 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
41802960 Wed Aug 17 11:50:49 2011 : BENetConfigEx: Successfully refreshed adapter information.
41802960 Wed Aug 17 11:50:49 2011 : ConnectToServerEndPoint: dest=192.168.1.251, service=6101
41802960 Wed Aug 17 11:50:49 2011 : ConnectToServerEndPoint: Failed to setup SSL context.
41802960 Wed Aug 17 11:50:49 2011 : NrdsAdvertiserThread: connect to target=192.168.1.251 port=6101 failed
41802960 Wed Aug 17 11:50:49 2011 : NrdsAdvertiserThread: Retrying in 60 seconds

 192.168.1.252 Is the IP of my backup server.
May Be The new version of Backup Exec  use an secure connection  Because we can be view the Following Message:
ConnectToServerEndPoint: Failed to setup SSL context ...

If so how can I fix it?

Here is the content of ralus.cfg file :

Software\Symantec\Backup Exec For Windows\Agent Browser\TcpIp\AdvertisementPort=6101
Software\Symantec\Backup Exec For Windows\Backup Exec\Debug\AgentConfig=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Debug\VXBSAlevel=
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertise All=1
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertise Now=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertisement Purge=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertising Disabled=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertising Interval Minutes=240
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Agent Directory List_1=192.168.1.251
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Auto Discovery Enabled=1
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Logging\RANT NDMP Debug Level=12
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\Encoder=
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\ShowTSAFS=
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemExclude1=/mnt/nss/pools/
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemExclude2=/mnt/nss/.pools/
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemExclude3=/_admin/*.*
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude1=devpts
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude2=proc
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude3=sysfs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude4=rpc_pipefs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude5=tmpfs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude6=ftp
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude7=ntfs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\VfmPath=/opt/VRTSralus/VRTSvxms
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RMAL\DisableRMAL=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Network\TcpIp\DnsQueryTimeOut=5000
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\CACertHash=AA5EAD35
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\CertHash=D2866B16
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\ExpirationDate=08-08-2012:10:25:01
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\IssuedBy=HERA - ROOT
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\IssuedTo=eros
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\MediaServerAddr=192.168.1.251
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\MediaServerFqdn=hera
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\MediaServerName=hera

Do you have any idea?

Thanks in advance

Best Regards

ilyass

Comments 12 CommentsJump to latest comment

Simon B.'s picture

Go into your BE Console, create a new backup. When you are in the Backup selection add the server under "user defined selection" and click on it. That should prompt you to confirm that a trust between the media server and the RALUS should be established.

If you confirm this, can you browse the resources of this machine afterwares? Rerun the backup.

/edit: Oh and:

 dest=192.168.1.251, service=6101

Is this the current IP of your media server? If yes, make sure that no firewall is blocking connections from the linux machine to the BE server on port 6101

PMCS GmbH & Co. KG - Consulting und Support für BE/NBU/EV und andere Symantec Produkte.
Please take the time and mark this post as solution if it solved your problem - thanks!

pkh's picture

BETCPListener: Successfully set the IPV6_V6ONLY 

Try disabling IPv6 on your Linux server.  Use only IPv4.

ilyass's picture

Hello

I performed the operations requested but it does not work

here is the message of BE console

Backup Exec can not establish a relationship of trust with the remote agent due to the failure of a certificate signing request to Security Branch. You can try to solve this problem by restoring the trust enter the media server and remote agent

The log file is simil:....ConnectToServerEndPoint: Failed to setup SSL context...

 dest=192.168.1.251 is the current IP of your media server and The firewall is not blocking connection on port 6101

Do you think that the connection can not be establish because is not a trust certificat ?

 If yes , is there a way around it?

Thanks in advance

Best Regards

ilyass

Simon B.'s picture

Something with the certificate exchange must have gone wrong. 

To check if the connection between your linux system and the BE server is blocked run a

telnet 192.168.1.251 6101

Is there a  connection established or does it say something about timeout or connection refused? If yes, please post the output.

Also run the following command and post the output:

ls -la /opt/VRTSralus/data/

PMCS GmbH & Co. KG - Consulting und Support für BE/NBU/EV und andere Symantec Produkte.
Please take the time and mark this post as solution if it solved your problem - thanks!

ilyass's picture

Hello,

When I do 

telnet 192.168.1.251 6101  

I have the following message : Connected to 192.168.1.251

The connection is established.

I don't have the data folder in /opt/VRTSralus

In  /opt/VRTSralus folder I have bin and VRTSvxms folder

Best Regards

ilyass

grzech's picture

I have very similar problem. Versions that I have:

RALUS 13.0.5204-0

Linux Debian 5.0.6

Media server 13.0 Rev. 2896 (64-bit) (on Windows Server 2008)

My RALUS config:

Software\Symantec\Backup Exec For Windows\Agent Browser\TcpIp\AdvertisementPort=6101
Software\Symantec\Backup Exec For Windows\Backup Exec\Debug\AgentConfig=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Debug\VXBSAlevel=
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertise All=1
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertise Now=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertisement Purge=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertising Disabled=0
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Advertising Interval Minutes=240
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Agent Directory List 1=10.0.0.1
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Auto Discovery Enabled=1
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Logging\RANT NDMP Debug Level=1
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\Encoder=
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\ShowTSAFS=
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemExclude1=/mnt/nss/pools/
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemExclude2=/mnt/nss/.pools/
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemExclude3=/_admin/*.*
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude1=devpts
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude2=proc
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude3=sysfs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude4=rpc_pipefs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude5=tmpfs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude6=cd9660
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude7=ftp
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\SystemFSTypeExclude8=ntfs
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RALUS\VfmPath=/opt/VRTSralus/VRTSvxms
Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\RMAL\DisableRMAL=0

Debug output:

b57d76c0 Thu Aug 18 19:11:48 2011 : Starting BE Remote Agent
b57d76c0 Thu Aug 18 19:11:48 2011 : Log file: /home/staff/grzech/RALUSdebug.log
b57d76c0 Thu Aug 18 19:11:48 2011 : No configuration file specified.  Using default.
b57d76c0 Thu Aug 18 19:11:48 2011 : Log to console: disabled
b57d76c0 Thu Aug 18 19:11:48 2011 : Successfully set the supplementary groups of the process
b57d76c0 Thu Aug 18 19:11:48 2011 : Initialized locks for SSL callbacks
b57d76c0 Thu Aug 18 19:11:48 2011 : Starting NDMP processor
b57d76c0 Thu Aug 18 19:11:48 2011 : NDMPDMainThreadFunc spawned: grpid=1, tid=-1250301072
b579eb70 Thu Aug 18 19:11:48 2011 : FS_InitFileSys
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsnt5.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedssql2.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsxchg.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsxese.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsmbox.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedspush.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsnote.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsmdoc.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedssps2.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedssps3.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsupfs.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsshadow.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsoffhost.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   loaded libbedsvx.so
b579eb70 Thu Aug 18 19:11:48 2011 :   loaded libbedsrman.so
b579eb70 Thu Aug 18 19:11:48 2011 :   loaded libbedssms.so
b579eb70 Thu Aug 18 19:11:48 2011 :   loaded libbedssmsp.so
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsra.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsdb2.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 :   loaded libbedsedir.so
b579eb70 Thu Aug 18 19:11:48 2011 :   libbedsvmesx.so could not be loaded: 0x       2 (2)
b579eb70 Thu Aug 18 19:11:48 2011 : Initializing FSs
b579eb70 Thu Aug 18 19:11:48 2011 : FS 1 failed to initialize: 0xE000FE46
b579eb70 Thu Aug 18 19:11:48 2011 : Function called: RMAN_InitFileSys
b579eb70 Thu Aug 18 19:11:48 2011 : Using 'UTF-8' Encoding.
b579eb70 Thu Aug 18 19:11:48 2011 : Using vfm path /opt/VRTSralus/VRTSvxms from config.
b579eb70 Thu Aug 18 19:11:48 2011 : Sucessfully set VFM_PRIVATE_ROOT env to /opt/VRTSralus/VRTSvxms.
b579eb70 Thu Aug 18 19:11:48 2011 : VFM_PRIVATE_ROOT was set with value /opt/VRTSralus/VRTSvxms
b579eb70 Thu Aug 18 19:11:48 2011 :      VXMS Initialization OK.
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <ext3> mounted at </>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <tmpfs> mounted at </lib/init/rw>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <proc> mounted at </proc>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <sysfs> mounted at </sys>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <usbfs> mounted at </proc/bus/usb>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <tmpfs> mounted at </dev>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <tmpfs> mounted at </dev/shm>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <devpts> mounted at </dev/pts>
b579eb70 Thu Aug 18 19:11:48 2011 : Detected Mounted Filesystem: type <nfsd> mounted at </proc/fs/nfsd>
b579eb70 Thu Aug 18 19:11:48 2011 : INFORMATIONAL: Zero value found for 'DisableRMAL' from ralus.cfg, allowing RMAL to initialize
b579eb70 Thu Aug 18 19:11:48 2011 : ndmpRun
b579eb70 Thu Aug 18 19:11:48 2011 : Could not resolve the "bews-ndmp" or the "ndmp" service, error code: -8, using port 10000
b579eb70 Thu Aug 18 19:11:48 2011 : NrdsWatchThread spawned: grpid=1, tid=-1262605456
b579eb70 Thu Aug 18 19:11:48 2011 : NrdsAdvertiserThread spawned: grpid=1, tid=-1270998160
b579eb70 Thu Aug 18 19:11:48 2011 : NrdsAdvertiserThread spawned: grpid=1, tid=-1279390864
b579eb70 Thu Aug 18 19:11:48 2011 : NDMP Daemon Running..
b579eb70 Thu Aug 18 19:11:48 2011 : BETCPListener successfully installed a signal handler for SIGTERM
b579eb70 Thu Aug 18 19:11:48 2011 : Could not create an IPv6 socket at this time, reason:An error occurred during a socket creation operation: Error Code: 97, System Error Message: Address family not supported by protocol
b579eb70 Thu Aug 18 19:11:48 2011 : SocketService::IsSystemDualIP: No support found for IPv6 currently
b579eb70 Thu Aug 18 19:11:48 2011 : Started NDMP Listener on port 10000
b43e1b70 Thu Aug 18 19:11:58 2011 : NrdsAdvertiserThread: advertisement cycle started.
b43e1b70 Thu Aug 18 19:11:58 2011 : RMAN_EnumSelfDLE: AgentConfig GetOracleDBNames returned error. If Oracle Agent is installed, please run AgentConfig.
b43e1b70 Thu Aug 18 19:11:58 2011 : NrdsAdvertiserThread: EnumSelfDLE for file system 14 returned 0(0x0) and 0 DLEs
b43e1b70 Thu Aug 18 19:11:58 2011 : BENetConfigEx: Successfully refreshed adapter information.

b43e1b70 Thu Aug 18 19:11:58 2011 : NrdsAdvertiserThread: EnumSelfDLE for file system 22 returned 0(0x0) and 1 DLEs
b43e1b70 Thu Aug 18 19:11:58 2011 : NrdsAdvertiserThread: Nrds Message Len : 139.
b43e1b70 Thu Aug 18 19:11:58 2011 : VX_RemoveDLE: DestroyDLE()
b43e1b70 Thu Aug 18 19:11:58 2011 : NrdsAdvertiserThread: Security is enabled!!!
b43e1b70 Thu Aug 18 19:11:58 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
b43e1b70 Thu Aug 18 19:11:58 2011 : BENetConfigEx: Successfully refreshed adapter information.
b43e1b70 Thu Aug 18 19:11:58 2011 : NrdsAdvertiserThread: connect to target=10.0.0.1 port=6101 failed
b43e1b70 Thu Aug 18 19:11:58 2011 : NrdsAdvertiserThread: Retrying in 60 seconds
b3be0b70 Thu Aug 18 19:12:03 2011 : NrdsAdvertiserThread: negative (purge) advertisement cycle started.
b3be0b70 Thu Aug 18 19:12:03 2011 : NrdsAdvertiserThread: no purge is pending.
b3be0b70 Thu Aug 18 19:12:03 2011 : NrdsAdvertiserThread: negative (purge) advertisement cycle complete.  Waiting 240 minutes before advertising again.
b43e1b70 Thu Aug 18 19:12:58 2011 : NrdsAdvertiserThread: Security is enabled!!!
b43e1b70 Thu Aug 18 19:12:58 2011 : This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
b43e1b70 Thu Aug 18 19:12:58 2011 : BENetConfigEx: Successfully refreshed adapter information.
b43e1b70 Thu Aug 18 19:12:58 2011 : NrdsAdvertiserThread: connect to target=10.0.0.1 port=6101 failed
b43e1b70 Thu Aug 18 19:12:58 2011 : NrdsAdvertiserThread: Retrying in 60 seconds

.... mute output

additionaly I run packet dump on machine with RALUS, while I start, stop, restart Agent:

tcpdump -i eth0 src 10.0.0.1 or dst 10.0.0.1

and results is null, none packets dump between machine with RALUS and Media Server 10.0.0.1.

Do You have any idea?

Thanks in advance

Best Regards

grzech

Simon B.'s picture

@thread opener: That is strange because according to your config you already have certificates in place:

Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\CACertHash=AA5EAD35
Software\Symantec\Backup Exec For Windows\Common\Backup Exec\Engine\Agents\Security\Certificates\hera\CertHash=D2866B16

However they should be in a data/ subfolder.

Might be worth a try to stop Ralus, make a backup of your ralus.cfg and remove the lines containing "Security" from your ralus.cfg. After that start ralus again and try to establish the trust as detailed in my first reply.

@grzech: Maybe a routing issue? try to ping 10.0.0.1 and also try to establish a telnet connection as detailed above

PMCS GmbH & Co. KG - Consulting und Support für BE/NBU/EV und andere Symantec Produkte.
Please take the time and mark this post as solution if it solved your problem - thanks!

grzech's picture

This is not a routing issue:

tcpdump -i eth0 src 10.0.0.1 or dst 10.0.0.1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
20:22:07.328266 IP 10.0.0.2 > 10.0.0.1: ICMP echo request, id 47229, seq 1, length 64
20:22:07.328573 IP 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 47229, seq 1, length 64
20:22:08.327875 IP 10.0.0.2 > 10.0.0.1: ICMP echo request, id 47229, seq 2, length 64
20:22:08.328084 IP 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 47229, seq 2, length 64
20:22:24.088844 IP 10.0.0.2.39169 > 10.0.0.1.6101: S 2791473770:2791473770(0) win 5840 <mss 1460,sackOK,timestamp 30696940 0,nop,wscale 6>
20:22:24.089131 IP 10.0.0.1.6101 > 10.0.0.2.39169: S 722386442:722386442(0) ack 2791473771 win 8192 <mss 1460,nop,wscale 8,sackOK,timestamp 148849945 30696940>
20:22:24.089203 IP 10.0.0.2.39169 > 10.0.0.1.6101: . ack 1 win 92 <nop,nop,timestamp 30696940 148849945>
20:22:29.447673 IP 10.0.0.2.39169 > 10.0.0.1.6101: F 1:1(0) ack 1 win 92 <nop,nop,timestamp 30698279 148849945>
20:22:29.449357 IP 10.0.0.1.6101 > 10.0.0.2.39169: . ack 2 win 260 <nop,nop,timestamp 148850481 30698279>
20:22:29.449377 IP 10.0.0.1.6101 > 10.0.0.2.39169: F 1:1(0) ack 2 win 260 <nop,nop,timestamp 148850481 30698279>
20:22:29.449444 IP 10.0.0.2.39169 > 10.0.0.1.6101: . ack 2 win 92 <nop,nop,timestamp 30698280 148850481>

ilyass's picture

Hello,

I do the required.

I deleted the rows for the certificate then I  start RALUS. When I tried to establish a relationship of trust I had the following message:

Backup Exec can not establish a relationship of trust with the remote agent due to the failure of a certificate signing request to Security Branch.....

I  have no data folder

Noted that the line about the certificate be added automatically when I run the agent in debug mode (./beremote --log-file log.txt)

This certificate problem is really weird

Best regards

ilyass

ilyass's picture

Hello,

the problem is still unresolved. Has anybody have an idea?

Best Regards

Colin Weaver's picture

Check out Page 35/36 about configuring the required trusts in Backup Exec 2010 R3 against Linux hosts

http://www.symantec.com/business/support/resources/sites/BUSINESS/content/staging/DOCUMENTATION/4000/DOC4045/en_US/2.0/beadminadndm_en.pdf

Hexadecimal's picture

i have the same problem, i do the steps for configuring the required trusts in Backup Exec 2010 R3 against Linux hosts, and i still cant see the linux server in the selection list.

my thread is : https://www-secure.symantec.com/connect/forums/i-c...

i probe make telnet to media server port 6101, and the connection is ok.