System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup client failed after trying to backup /dev directory

 
SOLVED
Go to solution
irt_1
Frequent Advisor

Netbackup client failed after trying to backup /dev directory

Hi All,

I am configuring the Netbackup on HP UX as follow: "NetBackup-HP-UX11.23 6.5.4"

It was always failed with this message
...
17:37:59.671 [7756] <4> bpbkar: INF - Excluded /dev/devkrs by exclude_list entry /dev/d*
17:37:59.673 [4344] <16> bpbkar: ERR - bpbkar killed by SIGPIPE
17:37:59.673 [4344] <16> bpbkar: ERR - bpbkar FATAL exit status = 40: network connection broken
17:37:59.673 [4344] <4> bpbkar: INF - EXIT STATUS 40: network connection broken
17:37:59.673 [4344] <4> bpbkar: INF - setenv FINISHED=0

The message "network connection broken" I think is misleading, because if I put /dev on the exclude_list the backup was running fine.
So I suspect there is certain files when being backup causing the failure.

I have reboot the server, but the problem still there when it backup the /dev directory.

Anyone know the answer why?

Thank you,

Iwan Tamimi
13 REPLIES
Michael Steele_2
Honored Contributor

Re: Netbackup client failed after trying to backup /dev directory

Hi

bpbkar: ERR - bpbkar killed by SIGPIPE

You've got an issue with your NIC's speed and duplex. Verify speed and duplex on all hops between master and clients including switches and routers.
Support Fatherhood - Stop Family Law

Re: Netbackup client failed after trying to backup /dev directory

>if I put /dev on the exclude_list the backup was running fine.

Does netbackup claim to backup device files?
Perhaps it is best to exclude /dev and back that up with ignite.

Tingli
Esteemed Contributor

Re: Netbackup client failed after trying to backup /dev directory

If Netbackup goes all the way down to /dev/devkrs, then the next one can be /dev/dsk, which goes to all the devices by itself. And I guess here is where the trouble comes from. Better to put /dev on the exclude_list.
VK2COT
Honored Contributor

Re: Netbackup client failed after trying to backup /dev directory

Hello,

a) The typical culprit is network setup,
but it seems you already checked it and
eliminated it.

Other reasons for bpbkar error 40:

b) Chech your hostname resolution (DNS,
and others). Use the bpclntcmd
utility.

c) If you have too many files in /dev, you
may want to increase the client read
timeouts and the client connect timeouts.
That might be the reason for your failures.
It tries to back up /dev but somehow it
takes too long to do it...

Cheers,

VK2COT
VK2COT - Dusan Baljevic
Larry Klasmier
Honored Contributor

Re: Netbackup client failed after trying to backup /dev directory

Is this happening on all you 11.23 netbackup clients or only one in particular? We backup a bunch of 11.23 servers and have no issues /dev. We exclude nothing in /dev and only get one warning in the bpbkar log regarding a socket file that skipped.

Have you tried increasing the logging level on the bpbkar log to see if you get any more information?
Albert Smith_1
Regular Advisor
Solution

Re: Netbackup client failed after trying to backup /dev directory

I wouldn't recommend backing up /dev as a policy as the files are very dynamic and would be rebuilt as the system boots and is recovered and overwritting files in that directory is STRONGLY discouraged.

irt_1
Frequent Advisor

Re: Netbackup client failed after trying to backup /dev directory

Hi All,

Thank you for the answers. Sorry for the late reply.

Actually I wanted to backup all the vg00 file systems (/, /stand, /var etc) using the netbackup but it always seemed to stop in /dev, if I put it in the exclude_list it would be fine. So I strongly think it is not a network issue.

I also had a bunch of 11.23 and 11.31 servers with Netbackup and have no problems, this one is the first time.

Yes I also ignite the to the tape once a month and this netbackup to cover daily backup.

I think I just let it backup excluding the /dev for the time being as many of you suggest.

Thanks again.

Iwan Tamimi
Michael Steele_2
Honored Contributor

Re: Netbackup client failed after trying to backup /dev directory

Johnson Punniyalingam
Honored Contributor

Re: Netbackup client failed after trying to backup /dev directory

>>>Actually I wanted to backup all the vg00 file systems (/, /stand, /var etc) using the netbackup but it always seemed to stop in /dev, if I put it in the exclude_list it would be fine. So I strongly think it is not a network issue.<<<<<

It would better always to Use make_tape_recovery if you wanted to backup all the vg00 file system
its most recommended backup tool which comes from "HPUX"

Its just suggestion

my 2 cents
Problems are common to all, but attitude makes the difference
Michael Steele_2
Honored Contributor

Re: Netbackup client failed after trying to backup /dev directory

Boy is that terrible advice. I have never seen any state from anyone in this world saying make_tape_recovery is better.

Make_net_recovery has been the ignite standard for a decade at least.

Support Fatherhood - Stop Family Law
Johnson Punniyalingam
Honored Contributor

Re: Netbackup client failed after trying to backup /dev directory

Oops, I got it wrong :( apologies,

if it can be either make_tape_recovery -> using tape

make_net_recovery -> via Lan

Problems are common to all, but attitude makes the difference
Gary Beckett
Occasional Advisor

Re: Netbackup client failed after trying to backup /dev directory

I have this exact problem. Same error 40 code.
I've also eliminated the NICs, cables and negotiation. All the file systems on my system are backed up except for root, which /dev is part of. Manually backing up the different directories under /dev revieled that is is certain files within /dev.
I came to the same conclusion, just add /dev/ to the exclude_list file. Which I have done. But, the backup still tries to backup /dev and hangs. Is there a process that needs to be bounced on the client. My understanding is that there isn't.
Any ideas?
Gary Beckett
Occasional Advisor

Re: Netbackup client failed after trying to backup /dev directory

Please ignore that last request. There's obvious a difference between and manual user initiated backup and a system scheduled backup. Last nights system schedule backup succeeded after adding the /dev in the exclude_list file.