Anyone see this brbackup error? Status = 160 : authentication failed

[Geoff Wild]

Our QA system failed last weekend with:

ERROR: executing command /usr/openv/netbackup/bin/bpbackup -w -t 17 -h svr006 -S svr006 -c QA_sap_offline -s Default-P
olicy -L /oracle/QA/sapscript/backint_dir/.backint.log.3.1114364038.20482 -k ".bdpuopli.lst" -f /oracle/QA/sapscript/b
ackint_dir/.backint.files.1114364038.20482.3 >> /oracle/QA/sapscript/backint_dir/.backint.log.3.1114364038.20482.output
2>&1
Status = 160 : authentication failed

Anyone ever see that before?

It's stumped the Oracle and SAP guys here as well as me...

Rgds...Geoff

[Alex Lavrov. · Accepted solution]

Some stuff I found, may be it helps:

============================================
Description:
VOPIE Enhanced Authentication may not work when host names are longer than
32 characters.
You may see Authentication Failed (error code 160) messages when connecting
to systems with host names or client names greater than 32 characters.
============================================
Description:
VOPIE authentication failures may occur when the case of host
names differ between NetBackup machines. For example, if
a NetBackup server thinks that the host name of a client is
"abc" and the client thinks its host name is "ABC", authentication
errors (error code 160) are likely to occur between the client and
server if VOPIE authentication is set up between the two machines.

Workaround:
Make sure the case of host names is consistent on all machines.
===========================================
Description:
When trying to use set UID to root binaries with VOPIE authentication,
it is likely that the message "authentication failed (160)" will appear
when trying to use one of those binaries as a non-root user. Set UID
to root binaries are typically created by the nonroot_admin script.

Additional Notes:
This fix does not apply to RS6000 (AIX), Sequent, and Auspex
platforms. Unable to use set UID to root binaries
with VOPIE authentication on those platforms.
============================================

And this link, there are several steps to follow to check this issue:
http://www.mwalters.com/CLIC/Configs/Veritas_Status_Codes.htm



Taken from:
http://seer.support.veritas.com/docs/246368.htm
http://www.mwalters.com/CLIC/Configs/Veritas_Status_Codes.htm
http://support.veritas.com/docs/267451

[Dave Hutton]

I'm not sure what version of NB you're using but a 160 in NB5.0 is under the troubleshooter helper:

Problem:
A problem was encountered when two systems were attempting to authenticate one another.

It's solution:
Try the following:
See the NetBackup System Administrator's Guide for more information on the files and commands mentioned here.
1. Ensure that the authentication libraries exist:
Windows:
install_path\NetBackup\lib\libvopie.dll
install_path\NetBackup\lib\libvnoauth.dll
UNIX (except HP-UX):
/usr/openv/lib/libvopie.so
/usr/openv/lib/libvnoauth.so
UNIX (HP-UX only):
/usr/openv/lib/libvopie.sl
/usr/openv/lib/libvnoauth.sl
Macintosh:
:System Folder:Extensions:libvopie.dll
:System Folder:Extensions:libvnoauth.dll
2. Check the methods_allow.txt files on the systems that are having problems to ensure that authentication is enabled. The files are in the following locations:
Windows:
install_path\NetBackup\var\auth
UNIX:
/usr/openv/var/auth
Macintosh:
:System Folder:Preferences:NetBackup:var:auth
If one system reports authentication failed (status code 160) and the other system reports network connection timed out (status code 41), you may have enabled authentication in the first system's methods_allow.txt file but not in the second system's methods_allow.txt file.
3. On the systems that are having the authentication problem, remove the remote host that is not being authenticated from the methods_allow.txt file.
For example, if host A and host B are having the problem, remove host A from the file on host B and vice versa.
Retry the operation.
* If the problem still exists, it indicates connection problems not related to authentication.
* If connections are now successful, proceed to the next step.
4. Execute bpauthsync -vopie on the master server to resynchronize the key files on the systems.
On Windows:
install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers -clients
On UNIX:
/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers -clients
5. Add back the names removed in step 3 and retry the operation.
6. Create debug log directories for the processes involved in authentication between NetBackup systems. These include:
* On the server, create debug log directories for bprd, bpdbm, bpcd.
* On the client, create debug log directories for bpbackup, bprestore, bpbkar (Windows only).
Retry the operation and check the logs.

[Geoff Wild]

Not too sure is this fixed it or not:

bpauthsync -vopie

But the backup was successful yesterday...

Rgds...Geoff