STATUS CODE 160: A Hot Catalog Backup fails with status code 160 (authentication failed) reported.

Article: 100019100
Last Published: 2015-02-17
Ratings: 0 0
Product(s): NetBackup & Alta Data Protection

Problem

STATUS CODE 160: A Hot Catalog Backup fails with status code 160 (authentication failed) reported.

Error Message

authentication failed (160)

Solution

Issue:
Hot Catalog Backup failing with status code 160 (authentication failed) reported.

Environment:
This was an existing hot catalog backup configuration, backing up to tape, which had been running fine.
In a review of the job details for the associated job IDs, it was discovered that while all three child jobs completed successfully (status code 0), the parent job failed reporting status 160 at the very end.

Log Files:
On the master server, the bpbrm and admin logs were used to verify the issue.

From the Job Details of the parent job:
11/28/2007 1:33:57 AM - requesting resource usa-entbu-001.NBU_CATALOG.MAXJOBS
11/28/2007 1:33:58 AM - granted resource usa-entbu-001.NBU_CATALOG.MAXJOBS
11/28/2007 1:33:58 AM - estimated 0 kbytes needed
11/28/2007 1:33:58 AM - begin Parent Job
11/28/2007 1:33:58 AM - begin Catalog Backup , Start Notify Script Status 26
11/28/2007 1:33:58 AM - end Catalog Backup , Start Notify Script; elapsed time: 00:00:00
11/28/2007 1:33:58 AM - begin Catalog Backup , DBM Query Status 160
11/28/2007 2:04:34 AM - end Catalog Backup , DBM Query; elapsed time: 00:30:36
11/28/2007 2:04:34 AM - begin Catalog Backup , Stop On Error Status 0
11/28/2007 2:04:34 AM - end Catalog Backup , Stop On Error; elapsed time: 00:00:00
11/28/2007 2:04:34 AM - begin Catalog Backup , End Notify Script Status 26
11/28/2007 2:04:34 AM - end Catalog Backup , End Notify Script; elapsed time: 00:00:00 Status 160
11/28/2007 2:04:34 AM - end Parent Job; elapsed time: 00:30:36 authentication failed(160)

Resolution:
The error occurred while attempting to create the DR file.  It was discovered that changes in the network now limited the user to the UNC path, meaning it was no longer authorized to use the path specified in the policy.

The Catalog policy was updated with a new username and password which did have access to the DR path.
 
The domain prefix was also added to the beginning of the login name.

After these changes were made, the backup ran successfully.

 
 

 

Was this content helpful?