Error 239

Netbackup is case sensitive. "SERVERNAME" and "servername" is two different servers in Netbackup view

In general all server names should be lowercase - including server names in policy configuration.

When running the bpbackup command, ensure the -p  {policy} and -s {schedule} option is specified. If neither the -p or -s is specified Netbackup try to do a qualified  guess and may select the wrong policy, resulting in a status 239

Tech note backup bpbackup :

http://www.veritas.com/docs/000093112

Have you checked your "hosts" files on... the client, the media server, and the master server?

hello,

Thanks for your reply, yes all is ok on the Policy and on the schedule.

we i launch the backup by command line with lowercase on client name it's fail, when i change to uppercase, it's pass, or when i launch it with IP adress o FQDN it's pass, without touching to the policy or schedule name.

NetBackup Client, NetBackup Media Server, NetBackup Master - any of these three may still be holding on to a stale "name+address" in their local cache of client names... so, one thing we usually do when we have odd naming issues is always to issue this command on all three of:  client and media and master

bpclntcmd -clear_host_cache

hello,

i did "bpclntcmd -clear_host_cache" on Master and Media servers.

i'll do it on clients, and update you.

thanks a lot for your help

I will be surprised if NBU 7.7.1 caused this.

My experience with NBU is that it has always been case sensitive.

Can you please show us what you see?
I would like to see:
-  your bpbackup command (are you using -C <client-name>?)
-  how client sees own hostname: bpclntcmd -self
-  the hostname used in Clients tab in the policy
-  and how the master resolves the client IP to hostname: bpclntcmd -ip <client-IP>

No need for real hostnames - replace names with client1/CLIENT1/client.fqdn, , etc.

The issue that you experience is with initial comms between client and master.
To troubleshoot the error, you need to check bprd log on the master to see the master's interpretation of the backup request.

If bprd log folder does not exist on the master server, create it and restart NBU to enable the log.

Please clarify if the bpbackup command is called with the -p -s parameter specified.

Its does do a difference .....

hello,

i launched the command with these parameters : bpbackup -i -p 3_Win -h server-A -s FULL_Hebdo -w 0  --> This command give error 239.

when i launched the command : bpbackup -i -p 3_Win -h SERVER-A -s FULL_Hebdo -w 0  -> the backup pass

Please show us the following:

-  how client sees own hostname:(run command on client) bpclntcmd -self
-  the hostname used in Clients tab in the policy
-  and how the master resolves the client IP to hostname: (run command on master) bpclntcmd -ip <client-IP>

What happens if you completely omit '-h <client-name>'?
IMHO, client-name sent to the master will default to 'bpclntcmd -self' output.

*** EDIT *** 

There is a section in chapter 6 of  NetBackup Administrator's Guide, Volume II  that explains:  How NetBackup uses host names

1) A wild guess... did you copy the client name from a Word doc?  If so, sometimes the 'hyphens' are not hyphens and are actually a different character...

...so, try replacing any and all of (what appear visually to be) hyphens on the command line by backspace or delete and then re-typing with a real hyphen from the keyboard.  Sounds wierd I know... but I have seen it happen more than once.

2) Also perhaps try encapsulating the client name in quotes?  Maybe try this:

bpbackup -i -p 3_Win -h "server-A" -s FULL_Hebdo -w 0