[Veritas-bu] Dedicated NIC for network backups

I apologize if I am stating something you have already done.

Use the  "REQUIRED_INTERFACE = <netbackup-host-name>" in your
/usr/openv/netbackup/bp.conf file...

I personally recommend using /etc/hosts file for name resolution and edit my
nsswitch.conf file for "hosts   file    dns".

And yes you will need "SERVER = <netbackup-host-name>" settings or
"MEDIA_SERVER = <netbackup-host-name>" settings in your bp.conf of the
master/media servers.

DNS and NetBackup do not get an A+ for playing together. On a good day I
can't figure out where NetBackup gets its IP addresses from.

If you continue to have problems, enable verbose logging and create the
directory /usr/openv/netbackup/logs/bpcd on the master/media/client servers.
The log.ddmmyy file will usually tell you what your IP / name resolution
problem is.

Brian

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
Malachi_McCabe AT newport-news DOT com
Sent: January 5, 2005 16:25 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Dedicated NIC for network backups



Hello all,

I have a Solaris server (We'll call it Bob) with two NICs, one for
production/user data, and another one that is solely dedicated to providing
a pipe for data backups and restores.  The server is running the NB4.5_FP6
client, while the Master is running NB5.0_MP3.  I have the client properties
identified on the Master so that it is still named Bob, but is pointing to
the IP address of the second NIC.  Backups and restores run fine, and
without complaint, as expected, because NB obediently uses the IP address I
gave it.

That being said, here is the issue:  When I check my problem log, I find
that it is filled with reverse lookup (gethostbyaddr) errors.  It seems
that, for some reason, NB performs a forward DNS lookup on Bob, establishes
the IP address according to DNS, and is then trying to re-verify with these
reverse lookups - And it does it twice every ten minutes.  This verification
process seems to be completely independent of any backup/restore jobs, so it
isn't causing any issues other than filling up my log.

So, is there any way I can keep the client name of Bob in my policy, or am I
going to have to create another DNS entry with a different name for this
second NIC, and then clone the Bob policy with the new name to make NB
happy?  Or, is there a way to disable this constant communication check?


Thanks in advance,

      Malachi



##########################################################################
# This email and all files transmitted with it are confidential and      #
# intended solely for the use of the individual or entity to whom they   #
# are addressed.                                                         #
#                                                                        #
# This e-mail message has been scanned for Viruses and Content and       #
# cleared by NetIQ MailMarshal.                                          #
#                                                                        #
#                                                                        #
# System Administrator                                                   #
# postmaster AT spiegel DOT com                                                 
#
#                                                                        #
##########################################################################
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu