RES: [Veritas-bu] error 239 and virtual hostnames

Carlos Alberto Lima dos Santos carlos_listas at
Thu Mar 17 11:36:33 CST 2005

	You must use in the policy, the CLIENT_NAME configured in the
bp.conf file (Unix) or register (Windows).


Carlos Alberto Lima dos Santos 
Eng. de Computação
Campinas-SP - Brasil
* carlos_listas at
icq 123987362

-----Mensagem original-----
De: veritas-bu-admin at
[mailto:veritas-bu-admin at] Em nome de David Magda
Enviada em: quinta-feira, 17 de março de 2005 14:05
Para: veritas-bu at
Assunto: [Veritas-bu] error 239 and virtual hostnames


I'm having a little trouble with jobs returning error 239 which
bperror(1M) reports as:

> the specified client does not exist in the specified policy
> The specified client is not a member of the specified policy.

This is with NetBackup 4.5 on Solaris 8, and all the jobs involve
going to a 'virtual host' (not the system's real hostname but one of
its aliases). All the jobs are Oracle BLIBs but I think that's
because we're only using the virtual host with those types of jobs.

We would have a policy called 'somedb_blib' under schedules
'oracle_full' and 'oracle_inc' (incremental) going to a virtual
hostname of 'somedb'. The real hostname would be 'hostdb1'.

The 'somedb_blib' policy is running fine to the virtaul hostname. The
error 239 comes in for jobs in in policy 'somedb_blib' in schedule
'ALL' going to 'hostdb1'. So basically the policy is trying to go to
the real hostname and do the job there.

We have multiple jobs that use the virtual hostname: they all run
fine to the virtual hostname, but then try to run to the real
hostname and return the 239 error code.

Any ideas?

David Magda <dmagda at>,
Because the innovator has for enemies all those who have done well under
the old conditions, and lukewarm defenders in those who may do well 
under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI
Veritas-bu maillist  -  Veritas-bu at

More information about the Veritas-bu mailing list