Well I think I figured out the socket
errors.
We have a backup LAN defined and on the
master we have two NICs on that LAN. For some reason it appears a lot of the
traffic that formerly went out the first NIC (which is what we have in local
hosts files on the clients defined for the master’s name) are going out
the second NIC so it isn’t being recognized as the correct name.
I was able to make the backups work by
changing IP in local hosts on client to that of second NIC from master. I was
also able to make the backups work by reverting local hosts to the IP of the
first NIC from master and downing the second NIC so it couldn’t use that.
Does anyone know what effect it would have
if I put both NICs in local hosts on clients so that either IP looked up would
result in the same master host name? Alternatively does anyone know a way I
can insure the master uses the first NIC when talking to specific clients?
Our intent is to setup auto port
aggregation on the master eventually to try to increase throughput to the Data
Domain. (The master is HP-UX, APA is network bonding somewhat like bonding in
Linux.) We’re not quite there yet.
Also – I found an nbproxy process
with nothing but CLOSE_WAITS to the various hosts that had had the socket
errors. I had to kill -9 that to make it go away. Does anyone know where I
can find info on this nbproxy. It was a child of other nbproxy processes and
seeing it only had CLOSE_WAITS on it made me think it safe to kill.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jeff Lightner
Sent: Friday, December 19, 2008
2:18 PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NCVU
download for NBU 6.5.1?
I’m seeing status 23, 24 & 25 (socket errors) on
various backups for the past couple of weeks but don’t know why.
Network seems to be OK.
On looking at troubleshooting it suggests running Netbackup
Configuration Validation Utility (NCVU).
On going looking for this I don’t have it on my
master. The download I did find seems to be for 4.5 and 5.1.
Is it still valid for 6.5.1? If not is there an alternate utility to use?
Of course if anyone has an idea why I’m seeing the
socket errors on some backups (different clients and different client types)
but not on all backups I’d appreciate hearing that.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
information and is for the sole use of the intended recipient(s). If you are
not the intended recipient, any disclosure, copying, distribution, or use of
the contents of this information is prohibited and may be unlawful. If you have
received this electronic transmission in error, please reply immediately to the
sender that you have received the message in error, and delete it. Thank you.
----------------------------------
