NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 161

NetBackup status code : 161
HOWTO104082 | 2014-11-20
How To | CMS-XML

NetBackup status code 161: Evaluation software has expired. See www.symantec.com for ordering information

161
TECH58638 | 2012-01-12
Technical Solutions | CMS-XML

Windows BMR client fails with status code 1, "Failed sending the discovery".

6/5/2012 07:00:28. 161 [Error] v-121-35 BMR information discovery failed.
TECH192858 | 2014-01-16
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pciex1077,2532.1077.160 pciex1077,2532.1077. 161 pciex1077,2532.1077.162
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

User created files can cause status code 83 failures for NetBackup replication jobs due to an authorization failure.

-rw-r----- 1 root root 127 Jan 01 15:26 nbu_pd_marker -rw-r----- 1 root root 161 Jan 01 15:26 nbu_pd_server drwx------ 3 root root 96 Jan 01 15:28 srv5220
TECH201588 | 2013-09-05
Technical Solutions | CMS-XML

Restore using SAN client fails with status 5 and status 83 if the configured number of data buffers is too large

For NetBackup 6.5.5 on Linux, all concurrent pipes are limited to a total of 161 buffers. For NetBackup 6.5.6 and above on Linux, all concurrent pipes are limited to a total of 322 buffers. For NetBackup on Solaris, all concurrent pipes are limited to total of 936 buffers.
TECH155301 | 2011-03-23
Technical Solutions | CMS-XML

Backup error: exit_status = 84 : io_ioctl: MTWEOF failed during error recovery, Input/output error

22:30:53.149 [8390] 2 tape_error_rec: attempting error recovery, delay 3 minutes before next attempt, tries left = 3 22:33:53. 161 [8390] 2 io_ioctl: command (5)MTWEOF 0 from (overwrite.c.489) on drive index 9 22:33:53.184 [8390] 2 io_ioctl: MTWEOF failed during error recovery, Input/output error
TECH59178 | 2010-01-27
Technical Solutions | CMS-XML

Following 6.0mp5, running Vault as a non-root user results in error 272 (execution of a vault notify script failed)

15:54:00.128 [18742] 16 vltrun@VOpExecuteScript::doOperation()^1631 Vault Notify Script=/usr/openv/netbackup/bin/vlt_start_notify FAILED 15:54:00. 161 [18742] 16 vltrun@VOpExecuteScript::doOperation()^1631 FAILed nb_ec=1 nb_msg=the requested operation was partially successful 15:54:00.177 [18742] 16 vltrun@VOpExecuteScript::doOperation()^1631: Leaving with DMN=1 SC=1
TECH56203 | 2008-01-15
Technical Solutions | CMS-XML

Status Code Chart

160 161 162
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Status 59: access to the client was not allowed backing up a media server to its own disk storage unit.

13:45:44.750 [1936.1360] 2 bpcd peer_hostname: Connection from host media-server.enterprise.veritas.com (10.82.108. 161 ) port 2623
TECH146417 | 2013-12-26
Technical Solutions | CMS-XML

STATUS CODE 83: SAN Client backups fail reporting status 83 (media open error).

* number of data buffers should not exceed 161 for NetBackup 6.5.5 and prior, and should not exceed 322 for 6.5.6 and above. If the FT media server is Solaris, the number of FT pipes
TECH62007 | 2013-08-23
Technical Solutions | CMS-XML

Status 25 on user-directed connections to bprd due to source port issues with client_port_window and random_ports

12:20:44. 161 [20567] 2 logconnections: BPRD CONNECT FROM 10.82.89.228.45146 TO 10.82.89.228.1556 fd = 5
TECH147302 | 2012-05-14
Technical Solutions | CMS-XML

NetBackup messages

See NetBackup status code : 161 events out of sequence - image inconsistency See NetBackup status code: 229
HOWTO103773 | 2014-11-20
How To | CMS-XML

Maintenance Pack nb_60_5_m.winnt.IA64.exe provides fixes to the Veritas NetBackup (tm) Enterprise Server / Server 6.0 on Windows XP/2003 64 bit Clients and Servers

on the media server. In this case, the error status should have been 161
TECH52955 | 2012-08-18
Technical Solutions | CMS-XML

Maintenance Pack nb_60_6_m.winnt.IA64.exe provides fixes to the Veritas NetBackup (tm) Enterprise Server / Server 6.0 on Windows XP/2003 64 bit Clients and Servers

on the media server. In this case, the error status should have been 161
TECH57971 | 2012-08-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?