NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 833

NetBackup status code : 833
HOWTO105068 | 2014-11-20
How To | CMS-XML

NDMP backups are failing with status 174 (media manager - system error occurred) reported. Status code 14 (file write failed) can also be seen in logs.

log on the media server: 03:44:36. 833 [21701] 2 set_job_details: LOG 1206758676 16 bptm 21701 media manager exiting because bpbrm is no longer active 03:44:37.340 [21701] 2 check_error_history: just tpunmount: called from bptm line 17644, exit_status = 174
TECH59140 | 2014-01-17
Technical Solutions | CMS-XML

nbpem stops after startup. Status 158 in NBPEM log

06/13/09 20:55:46. 833 [JobScheduler::run] calling getDbInfo()(JobScheduler.cpp:496)
TECH71502 | 2013-04-26
Technical Solutions | CMS-XML

backup hyper-v failed,error information:snapshot creation failed, status 156 and WRN - all_local_drives is not frozen

15:46:21. 833 [6188.9588] 2 onlfi_vfms_logf: INF - snapshot services: vss:Thu Aug 18 2011 15:46:21.832000 Thread id - 9588 VssNode::prepareCsvsForBackup: CSV TimeOut expired, Not all required CSV available in required state
TECH167764 | 2012-07-28
Technical Solutions | CMS-XML

NetBackup 7.0.1. A restore using tape media fails with EXIT STATUS 210.

09:14:44.583 [2152.3752] 2 process_request: command c_bprestore_7_0 (138) received Truncated for clarity. 09:14:45. 833 [2152.3752] 2 start_mpx_main_bprd: /usr/openv/netbackup/bin/bprd bprd -dontfork -mpxmain
TECH160846 | 2011-05-25
Technical Solutions | CMS-XML

Backups intermittently fail with status 24 or 42 within a few seconds of the start of data transfer.

833 12:56:37.17026 3.3.3.3 - 2.2.2.2 TCP D=662 S=13782 Ack=3625715306 Seq=3009467682 Len=1460 Win=49640
TECH143964 | 2010-11-11
Technical Solutions | CMS-XML

GENERAL ERROR: Administration Console is unresponsive and all jobs fail with Status 25 after NetBackup was upgraded to version 6.5

01:20:30.817 [4400.5772] 2 logparams: D:\VERITAS\NETBAC~2\bin\VNETD.EXE 01:20:30. 833 [4400.5772] 2 ProcessRequests: .\vnetd.c.281: msg: VNETD ACCEPT FROM FROM IPADDRESS TO TO IP ADDRESS fd = 460 log snipped
TECH55786 | 2009-01-31
Technical Solutions | CMS-XML

HP UX File System Backup Failed with Error 49 | Symantec Connect

12:57:21.816 [28318] <2> bpcd valid_server: comparing MasterServer.fully.qualified.domain.name and MediaServer.Short.Name 12:57:21. 833 [28318] <2> bpcd valid_server: comparing MediaServer.Short.Name and MediaServer.Short.Name 12:57:21.833 [28318] <4> bpcd valid_server: hostname comparison succeeded
Connect Forums | HTML

NetBackUp 7.0 on Server 2003 156 error | Symantec Connect

22:00:41. 833 [7056.460] <2> ol_cleanup: removing C:\Program Files\Veritas\NetBackup\temp\int-win-gemini-flash+7056+1.std_filelist
Connect Forums | HTML

getting status code 23: socket read failed.. | Symantec Connect

getting status code 23: socket read failed.. 15:00:50.756 [24993] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2057: service: bpcd 15:00:50. 833 [24993] <2> vnet_async_connect: vnet_vnetd.c.4205: in progress connect: 0 0x00000000 15:00:50.833 [24993] <2> vnet_async_connect: vnet_vnetd.c.4208: connect: async CONNECT FROM 100.1.1.61.4999 TO 192.168.255.2.13724 fd = 7
Connect Forums | HTML

Backup failing with Error code 23 on Solaris client NBU version 6.5.6 | Symantec Connect

01:13:33.811 [11654] <2> bpcd main: output socket port number = 1 01:13:33. 833 [11654] <2> bpcd main: Duplicated vnetd socket on stderr 01:13:33.833 [11654] <2> bpcd main: <---- NetBackup 6.5 0 ------------initiated
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

18:35:30. 833 [5472.4344] <2> db_end: Need to collect reply
Connect Forums | HTML

Status Code Chart

832 833 900
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Status Code 85 on 1st Phase of import | Symantec Connect

Status Code 85 on 1st Phase of import 11:44:31.830 [13518] <2> get_pref_netconnection: ../../libvlibs/vnet_addrinfo.c.4893: 0: using interface : ANY 11:44:31.830 [13518] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1200: 0: connect in progress: 1 0x00000001 11:44:31. 833 [13518] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML

NetBackup messages

error parsing discovered XML data See NetBackup status code : 833 error receiving information on message queue
HOWTO103773 | 2014-11-20
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?