I also ran into this problem as well. It's been a while, but I believe
that you have to have the fully qualified domain name of your NB master
first in the hosts file. By first I mean, ip address of master, fqdn,
and then short name. Short name before fqdn will not work. 

-djb

Dwayne J. Brzozowski 
Sr. Solaris Systems Administrator
mail: dwayne.brzozowski AT va DOT gov 

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
carrd AT ijet DOT com
Sent: Tuesday, October 07, 2008 12:28 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Netbackup 6.5 New upgrade woes

I have issues with the nbpushdata -add command. We recently updated to
6.5 from 5.1

eng01adm# nbpushdata -add
Validating configured host names.
Contacting oldhost to get host information.
Failed to get host information from host: oldhost
Failed to validate configured host names.
Add hosts that are down or inaccessible by using "nbemmcmd -addhost".
After adding the hosts, you must run nbpushdata again.
Error: invalid host name (136)

eng01adm# nbpushdata -remove oldhost
Records for oldhost do not exist in EMM.
Error: invalid host name (136)

nbpushdata -show_flags returns nothing

How do I clear what is in the EMM DB? How can I remove a host that EMM
claims does not exist?

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu