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

Linux Client Backup failure - With Error Code 25

Created: 24 Dec 2011 | 2 comments
Rajan Iyer's picture

Hi

I am facing the problem for one of the linux client in which the backup fails no. of times. In the same ref. with same Master Server other  linux clients backup are running fine.

While checking I found that in linux client in which the backup fails the kernel parameter setting is

 net.ipv4.ip_local_port_range = 32768       61000-------------------------------------Backup Failure

While in all other servers the range is

net.ipv4.ip_local_port_range = 1024        65000---------------------------------------Backup Sucessfull.

While checking bpcd is using 13782 to connect with the client which shows in "LISTEN" state.

netstat -an | grep 13782

tcp        0      0 0.0.0.0:13782               0.0.0.0:*                   LISTEN

In the bpcd client side log there is no error indicates.

Also from client side no error indicates in /var/log/messages during backup failure.

Please suggest what need to check from client end with other linux clients.

Thanks

Rajan

Comments 2 CommentsJump to latest comment

Yasuhisa Ishikawa's picture

> In the bpcd client side log there is no error indicates.

This indicate that there are no connections accepted on the client. Ephemeral port range defined as net.ipv4.ip_local_port_range is no matter.

For first plese tell us version of your OS and NetBackup.
I guess iptables or network-based firewall blocks connection requests for bpcd(13782), vnetd(13784), pbx(1556)  from media server.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Yogesh9881's picture

Post output of below commands.

Run on Master /usr/openv/netbackup/bin/admincmd/ ./bptestbpcd -client SAPCJDV -debug -verbose

Run on Client /usr/openv/netbackup/bin/ ./bpclntcmd -self

i will also suggest you to update host file on Master / Media & Clients as shown below

192.168.2.100      SERVER01    SERVER01.mydomain.com

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)