[Veritas-bu] error 239 and virtual hostnames

David Magda dmagda+vertbu at ee.ryerson.ca
Thu Mar 17 11:05:21 CST 2005


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 ee.ryerson.ca>, http://www.magda.ca/
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

More information about the Veritas-bu mailing list