NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 161

NetBackup status code : 161
HOWTO90579 | 2013-10-02
How To | CMS-XML

NetBackup status code: 161

NetBackup status code : 161
HOWTO50927 | 2012-11-19
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

NetBackup status code: 161

NetBackup status code : 161
HOWTO35037 | 2010-10-29
How To | 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

ALL jobs fail with error 237 before any action or resource allocation.

00:00:02.003 [25494] 2 process_files: log_1195268400 is too new 04:17:07. 161 [6865] 16 class_db: Data for policy testwebex is stale: incoming generation: 13, existing generation: 15 04:17:07.162 [6865] 2 bpdbm: request complete: exit status 238 the database contains conflicting or erroneous entries
TECH137984 | 2010-08-21
Technical Solutions | CMS-XML

restore failure: exit status 5

-- 9/26/2008 12:41:47. 161 [ClientAttrCache::isFatClient] number of FT clients for master pnbus001 = 0
TECH63733 | 2010-01-24
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

catalog backup problems status 130 after upgrade nbu 6.5-- bpbkar core dumping

system error occurred 11:29:36. 161 [2460] 4 bpbkar Exit: INF - setenv FINISHED=0 SOLUTION/WORKAROUND: Engineering binary provided for etrack 1429771 Formal resolution will be in 6.5.4
TECH64242 | 2009-01-21
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

The status code 58 Can’t connect to client | Symantec Connect

The status code 58 Can’t connect to client 01:55:02.219 [24252] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpdbm 01:55:02.322 [24252] <2> logconnections: BPDBM CONNECT FROM 135. 161 .151.97.38022 TO 135. 161 .150.167.13724 01:58:47.304 [24252] <2> vnet_async_connect: vnet_vnetd.c.4237: getsockopt so_error returned: 145 0x00000091
Connect Forums | HTML

Netbackup flashbackup-windows Failed with Error 13 and Error 11 | Symantec Connect

Netbackup flashbackup-windows Failed with Error 13 and Error 11 AM: [1284.8148] <4> dos_backup::v_verifyfilelist: INF - UBS Local Type for '\\.\D:\' --> 00000000 1:16:30. 161 AM: [1284.8148]
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?