cancel
Showing results for 
Search instead for 
Did you mean: 

Error 239

MagMan
Level 3

hi,

some backups failed with error code 239.

these client are correct on the NBU Policy, and, the DNS resolution is OK.

the resolution with bpclntcmd -hn and with -ip are correct. the communication is OK too.

when i lanch the backup from command line with a lowercase of the client name that give the error : EXIT STATUS 239: the specified client does not exist in the specified policy.

 

when i changed the client name to the uppercase, and lanched again, it's pass.

when launching from GUI, it's OK.

when launching with all fqdn name it's pass, same if launching from command line with IP adress.

 

the issue appear just when launching with lowercase...

the backups are launched from a scheduler (that run the command bpbackup...).

the Issue appear aleatory, after we upgraded the Master; media servers from 7.5.0.6 to 7.7.1 (Netbackup Enterprise).

master is windows 2008 R2 Standard Edition.

 

please help

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

So, on master server you have something like this in hosts file (according to bpclntcmd output):
10.11.18.53 server-A.dm.ok.domain     server-A
Is this right?
I don't see any alias for all uppercase in bpclntcmd output?
If you have added another alias in the meantime, do you clear NBU host cache each time you change hosts file?

Client name in Policy is SERVER-A, right?

Client know itself as server-A SERVER-A.dm.ok.domain  

Can you see that the master does not resolve IP address 10.11.18.53 to SERVER-A? or to SERVER-A.dm.ok.domain?

We see on client and master 4 different alias for client name:
server-A   server-A.dm.ok.domain   SERVER-A   SERVER-A.dm.ok.domain
Is this right?
All 4 these names are different in NBU....

Have you enabled bprd log on the master?
Have you had a look at the log after starting bpbackup command on the client?
You will see connection request from client IP address, followed by reverse lookup of IP to hostname, and then policy lookup.

My advice:
Choose one naming convension and stick to it.

PLEASE do not change between different hostnames and IP address - you may end up having difficulty with restores....

View solution in original post

17 REPLIES 17

Nicolai
Moderator
Moderator
Partner    VIP   

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

sdo
Moderator
Moderator
Partner    VIP    Certified

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

MagMan
Level 3

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.

sdo
Moderator
Moderator
Partner    VIP    Certified

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

MagMan
Level 3

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

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

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.

Nicolai
Moderator
Moderator
Partner    VIP   

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

Its does do a difference .....

MagMan
Level 3

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

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

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

 

sdo
Moderator
Moderator
Partner    VIP    Certified

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

MagMan
Level 3

C:\>bpclntcmd -hn server-A
host server-A: server-A.dm.ok.domain at 10.11.18.53
aliases:     server-A.dm.ok.domain     server-A     10.11.18.53

C:\>

C:\>bpclntcmd -ip 10.11.18.53
host 10.11.18.53: server-A.dm.ok.domain at 10.11.18.53
aliases:     server-A.dm.ok.domain     10.11.18.53

C:\>


from client side :

 

server-A.dm.ok.domain
SERVER-A.dm.ok.domain


c:\>bpclntcmd -self
gethostname() returned: server-A
host server-A: SERVER-A.dm.ok.domain at 10.11.18.53

aliases: SERVER-A.dm.ok.domain server-A
10.11.18.53
getfqdn(server-A) returned: SERVER-A.dm.ok.domain

 

here is the retur message when i ran the command without -h "client name"

bpbackup -i -p 3_Win -s FULL_Hebdo -w 0
EXIT STATUS 37: operation requested by an invalid server

 

sdo
Moderator
Moderator
Partner    VIP    Certified

You never showed us your hosts file on client, media or master.

You have an upper-case name in a hosts file, and/or an upper-case name in DNS, or both upper and lower in hosts file, or both upper and lower in DNS.  You need to remove the upper-case names and/or replace them with lower-case names in either or both of hosts files and/or DNS.

You seem to have doctored some text above.  It is very difficult (impossible) to work out what you are doing or where the output is coming from if you snip pieces of text away.

.

The killer test is this, do at least two nslookups on all three of client, media, master.  Do every combination of bpclntcmd at least twice on each of client, media, master... so that you can detect "round robin" multiple names in DNS.    This is the only way to spot bad multiple names.

sdo
Moderator
Moderator
Partner    VIP    Certified

What is particularly telling is this...

c:\>bpclntcmd -self
gethostname() returned: server-A
host server-A: SERVER-A.dm.ok.domain at 10.11.18.53

...is that the NetBackup Client thinks it's own name is uppercase.

sdo
Moderator
Moderator
Partner    VIP    Certified

On the client show us this:

> dir C:\Windows\System32\drivers\etc

...please?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
And we still don't know how client name is specified in Clients tab in the policy.

MagMan
Level 3

Marianne, it's with UPPERCASE, same on client propreties client name.

 

and we have hosts file in drivers\etc\.... the resolution of name is with DNS server. i already add the IP adress client name (upper and lower case), and FQDN name.. when launched the bpbackup command return Error 239.

the backup can be initiate successfuly when i launched it with the command line with the IP adress.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

So, on master server you have something like this in hosts file (according to bpclntcmd output):
10.11.18.53 server-A.dm.ok.domain     server-A
Is this right?
I don't see any alias for all uppercase in bpclntcmd output?
If you have added another alias in the meantime, do you clear NBU host cache each time you change hosts file?

Client name in Policy is SERVER-A, right?

Client know itself as server-A SERVER-A.dm.ok.domain  

Can you see that the master does not resolve IP address 10.11.18.53 to SERVER-A? or to SERVER-A.dm.ok.domain?

We see on client and master 4 different alias for client name:
server-A   server-A.dm.ok.domain   SERVER-A   SERVER-A.dm.ok.domain
Is this right?
All 4 these names are different in NBU....

Have you enabled bprd log on the master?
Have you had a look at the log after starting bpbackup command on the client?
You will see connection request from client IP address, followed by reverse lookup of IP to hostname, and then policy lookup.

My advice:
Choose one naming convension and stick to it.

PLEASE do not change between different hostnames and IP address - you may end up having difficulty with restores....