NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 160

NetBackup status code : 160
HOWTO104081 | 2014-11-20
How To | CMS-XML

Media Manager status code 160

Media Manager status code 160
HOWTO104519 | 2014-11-20
How To | CMS-XML

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

authentication failed ( 160 )
TECH63122 | 2014-10-28
Technical Solutions | CMS-XML

NetBackup status code: 160

NetBackup status code : 160
HOWTO95177 | 2014-02-13
How To | CMS-XML

The parent hot catalog backup job is failing with a status 160 when attempting to write the DR file to a share.

) failed ( 160 :64) 14:04:14.728 [3356.2520] 4 db_error_add_to_file: Cannot write to \\share\D\PATH\NAME
TECH197828 | 2012-10-03
Technical Solutions | CMS-XML

Informix backup results in an error 160 : authentication failed

Informix backup results in an error 160 : authentication failed
TECH24130 | 2012-08-03
Technical Solutions | CMS-XML

Catalog backup finishes with Status 160 on Windows 2008 R2

For Windows 2008 R2 systems, user receives status 160 while performing a Hot Catalog Backup. Checking the Job Details tab of the parent job shows that all the children jobs for the individual portions of the catalog backup were completed successfully with status 0. However, the parent job completed with status 160.
TECH137173 | 2010-08-04
Technical Solutions | CMS-XML

NetBackup reports intermittent status code 160, 59, and 41 for a particular Windows or UNIX client.

NetBackup Error 160
TECH53112 | 2010-01-09
Technical Solutions | CMS-XML

STATUS CODE: 160, encountered after enabling Vopie authentication for the NetBackup server and clients.

A Status code 160 is encountered after enabling Vopie (Veritas one-time Passwords In Everything) authentication for the Veritas NetBackup (tm) server and clients. This error is seen when starting the Windows Remote Administration Console and attempting to connect to the master server. The connection will report a Status 160 and state that the bprd
TECH47600 | 2008-01-25
Technical Solutions | CMS-XML

STATUS CODE: 160, occurs when backing up a client due to an authentication error.

16 bpbrm start_bpcd: bpcd on exited with status 160 : authentication failed
TECH53234 | 2008-01-20
Technical Solutions | CMS-XML

STATUS CODE 25, 41, 58, and 160: Oracle RMAN backups fail intermittently

160
TECH45551 | 2007-01-11
Technical Solutions | CMS-XML

Catalog Backup to Disk: Status Code 160: Authentication failed..... | Symantec Connect

Catalog Backup to Disk: Status Code 160 : Authentication failed.....
Connect Forums | HTML

Status code 160 - authentication failed | Symantec Connect

Status code 160 - authentication failed Tweet I'm having trouble determining why one of the catalog backup jobs fails with code 160 .
Connect Forums | HTML

VMware restore failing with "VMware policy restore error(2820)" due to timeout in bptm child pid "wait for child pid #### timeout"

11:16:23.300 [11144.11352] 2 write_blocks: [3616] writing 6272 data blocks of 512 *** 300 seconds later *** 11:21:21. 160 [11144.11352] 2 write_blocks: [3616] writing 64 data blocks of 512
TECH227068 | 2014-12-12
Technical Solutions | CMS-XML

NetBackup status code: 41

Make sure that enhanced authentication is configured correctly. For example, the following may result in status code 41: Host A is configured to use enhanced authentication with host B, but host B is not configured to use enhanced authentication with host A. In this case, connections from host B to host A are likely to fail with status code 41. Connections from host A to B are likely to fail with authentication errors ( status code 160 ).
HOWTO103971 | 2014-11-20
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?