Video Screencast Help

Adding a Linux server

Created: 18 Jan 2013 • Updated: 21 Jan 2013 | 7 comments
This issue has been solved. See solution.

Before upgrading to version 2012 I was backing up a Linux box successfully.  Once I upgraded the media server to BE 2012 I began seeing that job complete with exception because it was running an older version of the backup utility.  It ran like that for several days as I had other more important features to fix.  The last two backups of its kind started failing:  "The job failed with the following error: The Backup Exec server could not connect to the remote computer. Ensure that a Backup Exec agent is installed and running on the remote computer. If a Backup Exec agent is installed, ensure that it is the correct version."

I thought, "Okay, time to update it."  So I used WinSCP to xfer the .gz file from my Win 7 machine to a folder I created on the Linux box at /BE_RAWS and then followed the following article to a 'T' and at the end it stated that the agent installed successfully.

http://www.symantec.com/business/support/index?pag...

Now, back on the media server I try to add the Linux server but it now cannot connect to it, I receive this error:  Failure to browse "FQDN of media server" A communication failure occurred when attempting to connect to this server.  Some common causes for this error are:  the coputer name is typed incorrectly, the computer is not powered on, a Backup Exec agent is not installed, or the network is imporperly configured.

1.  computer name is typed correctly: tried adding by server name, FQDN, and by IP and all failed

2.  server is certainly powered on

3.  I just installed the agent and it reported success, so can't be that

4.  nothing on the network changed, ping and nslookup return favorable results

5.  for the logon account I am using the root account, the same account i used to install the agent

 

 

Comments 7 CommentsJump to latest comment

Backup_Exec's picture

Hi

Please check the link below

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

 

Hope that helps

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

pkh's picture

What is the variant of Linux that you are using?  Check that it is supported.  See the SCL below

BE 2012 SCL

If IPv6 is running on the Linux box, turn it off.

rsmccall's picture

@Backup_Exec - Thanks for the idea but I have already been in that config file and verified it was pointing to the proper media server.

@pkh - I checked the list and Ubuntu 8.04 is on the list.  During the install of RAWS on this server it stated that it was supported too. 

When I configure the logon account it should just be "root" or should it be "root@servername"?

 

Backup_Exec's picture

Hi

 

It should be only root when adding the account and authenticating to the server

 

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

pkh's picture

Have you tried turning off IPv6 on the Linux server?

VJware's picture

See if this applies ~ http://www.symantec.com/business/support/index?pag...

Additionally, if the above KB does not apply, are you able to browse if selinux is temporarily disabled... Lastly, would you please provide debug output per this KB ~ http://www.symantec.com/business/support/index?pag...

rsmccall's picture

@Backup_Exec - I left the logon account as just root.

@pkh - I haven't touched anything with IPv6.  I instead jumped to the debugging mode as VJware suggested.

@VJware - Your first post does not apply to this scenario and didn't know where to start with selinux...(I haven't really dabbled too much with linux of any fashion).  So I turned to the debugging mode per the article you posted.  As I was looking through the info I found that the server was attempting to communicate via NDMP port 10000.  

The other day I had changed NDMP on the media server to port 9000 so that communication to my NetAPP FAS2040 filer would be possible.  All other Windows servers are running just fine since that change and it didn't dawn on me that it would affect this guy.  

So anyhow, I found this helpful article (http://www.symantec.com/business/support/index?pag...) and had to create the NDMP entry at the end of the file.  I then started the VRTSralus service and voila.  Now I can add the server and browse ROOT from the media server.

 

SOLUTION