cancel
Showing results for 
Search instead for 
Did you mean: 

RALUS Probleme: Stoppt immer wieder

rbol
Level 3

Mein Ralus auf einem Suse Linux-Server startet zwar (Eingabe von /etc/init.d/VRTSralus.init start ergibt: OK), aber bricht dann immer mal wieder weg.

Ab und zu funktioniert das Backup, oft aber bekomme ich die Meldung, dass das Backup fehlgeschlagen sei und wenn ich dann den Ralus überprüfe, läuft er nicht.

Ich habe schon einen Cron-Job erstellt, der den Ralus täglich kurz vor dem Backup einmal startet, aber auch dieser scheint nicht dauerhaft zu funktionieren.

 

Nun habe ich irgendwo mal den Debug-Parameter des beremote gefunden und ausgeführt.

Leider bin ich kein Linux-Spezi und weiss nicht genau, was da das Problem ist. Vielleicht kann mir jemand aus dieser Runde helfen? Die Ausgabe von ./beremote --log-console ergibt folgende Probleme:

Einmal finde ich:

 b5a7cba0 Fri Jan 21 08:36:11 2011 : Initializing FSs
b5a7cba0 Fri Jan 21 08:36:11 2011 : FS 1 failed to initialize: 0xE000FE46

Und dann etwas später:

 b4969ba0 Fri Jan 21 08:36:21 2011 : This instance of BETCPListener was not requested to install a signal handler
 and hence will not install one!
b4969ba0 Fri Jan 21 08:36:21 2011 : ConnectToServerEndPoint: dest=10.107.226.231, service=6101
b4969ba0 Fri Jan 21 08:36:21 2011 : BETCPConnection::LoopThroughListAndConnect: Could not connect to remote addr
ess "10.107.226.231" Error:111.
b4969ba0 Fri Jan 21 08:36:21 2011 : BETCPConnection::CreateConnectionFromHostAndPort: Remote Host: "10.107.226.2
31": There were no addresses returned, belonging to family: IPv6
b4969ba0 Fri Jan 21 08:36:21 2011 : BETCPConnection::CreateConnectionFromHostAndPort: Could not create a connect
ion to "10.107.226.231" because attempts with both IPv4 and IPv6 protocols failed
b4969ba0 Fri Jan 21 08:36:21 2011 : Could not create a BETCPConnection object from address: 10.107.226.231 error
=An error occurred during a socket connect operation: Error Code: 111, System Error Message: Connection refused
b4969ba0 Fri Jan 21 08:36:21 2011 : NrdsAdvertiserThread: connect to target=10.107.226.231 port=6101 failed
b4969ba0 Fri Jan 21 08:36:21 2011 : This instance of BETCPListener was not requested to install a signal handler
 and hence will not install one!
b4969ba0 Fri Jan 21 08:36:21 2011 : ConnectToServerEndPoint: dest=10.107.226.232, service=6101
b4969ba0 Fri Jan 21 08:36:21 2011 : BETCPConnection::LoopThroughListAndConnect: Could not connect to remote addr
ess "10.107.226.232" Error:111.
b4969ba0 Fri Jan 21 08:36:21 2011 : BETCPConnection::CreateConnectionFromHostAndPort: Remote Host: "10.107.226.2
32": There were no addresses returned, belonging to family: IPv6
b4969ba0 Fri Jan 21 08:36:21 2011 : BETCPConnection::CreateConnectionFromHostAndPort: Could not create a connect
ion to "10.107.226.232" because attempts with both IPv4 and IPv6 protocols failed
b4969ba0 Fri Jan 21 08:36:21 2011 : Could not create a BETCPConnection object from address: 10.107.226.232 error
=An error occurred during a socket connect operation: Error Code: 111, System Error Message: Connection refused
b4969ba0 Fri Jan 21 08:36:21 2011 : NrdsAdvertiserThread: connect to target=10.107.226.232 port=6101 failed
b4969ba0 Fri Jan 21 08:36:21 2011 : NrdsAdvertiserThread: Retrying in 60 seconds
b4169ba0 Fri Jan 21 08:36:26 2011 : NrdsAdvertiserThread: negative (purge) advertisement cycle started.
b4169ba0 Fri Jan 21 08:36:26 2011 : NrdsAdvertiserThread: no purge is pending.
b4169ba0 Fri Jan 21 08:36:26 2011 : NrdsAdvertiserThread: negative (purge) advertisement cycle complete.  Waitin
g 240 minutes before advertising again.

 

Offensichtlich bekommt der beremote die zu sichernden Server irgendwie nicht connectet.

 

Seltsamerweise funktioniert die Sicherung ab und zu.

 

Gibt's hier 'nen Experten, der einem Linux-Laien, der sonst eher in der Windows-Welt unterwegs ist, eine Lösung anbieten kann?

13 REPLIES 13

itsmeaffinity
Level 6

Hi

 

Please let me know which version of Linux is this with updates like RHEL 5.4 or SUSE 10.2

 

Also let me know backupexec version with updates like BE 2010 r2 sp1

 

Also let me know what is the file system used for example ext3 or ext4

 

Thank You

pkh
Moderator
Moderator
   VIP    Certified

First of all, check the SCL for your version of BE to see whether the version of SUSE Linux that you are using is supported.

rbol
Level 3

Filesystem: ext3

BackupExec 12.5 Rev. 2213 SP 3

Linux: suse 10.2

 

itsmeaffinity
Level 6

Hi

 

Thanks for the updates & yes it supported configuration so should not be an issue if this is intermittent connection you can updates your backupexec to sp4 & few updates or if you are vaild for free upgrade you can go upto BE 2010 r2 sp1 & then check if that help to give you stable backup

You can even install BE 2010 r2 in trialware with sp1 & on different server & may be test & see if that works with trialware you will get 60 days of time to use it so will be good option to check it out & once you install  BE 2010 r2 with sp1 please upgrade your linux agent to BE 2010 r2 sp1 by uninstalling previous version which is 12.5

This is link to download BE 2010 r2 please download 3 gb iso file

https://www4.symantec.com/Vrt/offer?a_id=93355

link for BE 2010 r2 sp1

http://www.symantec.com/docs/TECH143670

 

If this information help you please mark this post as solved

 

Thank You

rbol
Level 3

Ich wollte eigentlich kein extr-Update machen, da alles andere sauber funktioniert.

 

Dachte eher, hier kann mir jemand sagen, was die gepostete Fehlermeldung bedeutet und dafür eventuell eine Lösung nennen?

itsmeaffinity
Level 6

Hi

 

Ok that is fine I will check the log again & check out if I can give you some points

About upgrading I was not suggesting to upgrade tyou can install BE 2010 r2 sp1 if possible on different server & then for time being use linux agent for 2010 r2 to see if that helps

 

Anyways  no issue update you soon

 

Thank You

itsmeaffinity
Level 6

Hi

 

Back again can you please check this & see if that helps as the error mention by you in that beremote & the one mention by me are pretty similar so let me no give it a shot

 

https://www-secure.symantec.com/connect/forums/ralus-listener-will-no-longer-be-able-listen-its-ipv4-address

I think this might be happening due to port scanning application due to which the port will be blocked randomly which terminates connection to RALUS and job fails

Thank You

rbol
Level 3

Klappt nicht. Die beschriebene Lösung ist für Solaris.

 

Noch eine andere idee?

itsmeaffinity
Level 6

Hi

Thanks for the update again few question I will like to ask please let me know updates on that

 

1 Is Ipv6 enabled on linux box

2 How many nic card does this box have

3 Is this linux box on virtual machine

4 Linux is in an LDAP environment. Are you using LDAP ? if yes then please follow the document below

http://www.symantec.com/docs/TECH87344

 

Waiting for updates

 

Thank You

itsmeaffinity
Level 6

Hi

 

Any updates here please mark the post solved if this has resolved the issue

 

I appreciate your response on same

 

Thank You

rbol
Level 3

> 1 Is Ipv6 enabled on linux box

nein

> 2 How many nic card does this box have

1

> 3 Is this linux box on virtual machine

nein

> 4 Linux is in an LDAP environment. Are you using LDAP ? if yes then please follow the document below

Der in dem Dokument beschriebene Fehler tritt bereits beim Start von RALUS auf. Bei mir startet RALUS aber einwandfrei (zumindest wird kein "Failed" angezeigt), beendet sich halt nur irgendwann wieder.

 

In den letzten 2 Tagen ist die Sicherung auch einwandfrei gelaufen und derzeit ist RALUS auch noch an. Bin gespannt, wann der wieder wegbricht.

itsmeaffinity
Level 6

Hi

 

Thanks for your update on same I have seen in past lot of issue with SUSE  & LDAP & which has been fixed by that document

 

Anyways keeps me posted in case if wanted any further help

 

ThanK You

bigbenaugust
Level 3

I believe I am having a similar issue. (Thank you Google Translate!)

Server: Windows Server 2003 SP2 with Backup Exec 2010 R2 SP1

Clients: RHEL4.8 (32-bit) and RHEL5.5 (32- and 64-bit) all with RALUS 4164.111.146017 (it happens to all of them)

Network: Non-routed 192.168. network.

No LDAP and IPv6 is not enabled.

It seems that the Linux clients all run just fine for a week or two after updating or restarting. But then at the start of a backup job, the connection mysteriously and instantly disappears and the job is marked failed with the "could not connect to the remote computer" error. It happens to 1-2 machines a night until they've all been restarted, then the cycle repeats again.

This issue did not occur at all when I was on 11d.7170.

I have enabled debugging information in the ralus.cfg file to see if I can get some useful information.