NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 319

NetBackup status code : 319
HOWTO90728 | 2013-10-02
How To | CMS-XML

NetBackup status code: 319

NetBackup status code : 319
HOWTO51076 | 2012-11-19
How To | CMS-XML

NetBackup status code: 319

NetBackup status code : 319
HOWTO35187 | 2010-10-29
How To | CMS-XML

Backups of the same client using some media servers fail with status 21: socket open failed

on the client host confirms that the media server host can connect to the client host and start the bpcd service. 14:20:34. 319 [9621694] 2 ProcessRequests: vnetd.c.288: msg: VNETD ACCEPT FROM 2.2.2.2.59499 TO 2.2.2.2.13724 fd = 4 14:20:34.344 [9621694] 2 ProcessRequests: vnetd.c.349: msg: Request vn_request_service_socket(6)
TECH129303 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup STATUS 23, NDMP backups fail after the data has been transferred to the tape storage

13:45:01. 319 [29687] 4 report_throughput: VBRT 1 29687 7 1 IBM.ultrium-td2.001 MEDIA1 0 1 0 692 692 (bptm.c.27873)
TECH202406 | 2013-10-16
Technical Solutions | CMS-XML

Oracle RMAN application backup job hangs and the automatic job fails with status 6 at 15 minutes after the data transfer completes.

07:00:49.059 [11175] 2 sbtinfo2: INF - leaving 07:00:49. 319 [11175] 2 int_signal_hdlr: INF - ** SIGCLD received **
TECH73130 | 2013-03-27
Technical Solutions | CMS-XML

SAP backups that run many days may fail intermittently with status 6 after lock file removal

Output = EXIT STATUS 6: 20:10:46. 319 [5845] 16 bsa_initiatebackup: ERR - backup failed: 6 the backup failed to back up the requested files 20:21:00.128 [5850] 2 dbc_get_string: Output = EXIT STATUS 6:
TECH170245 | 2011-09-23
Technical Solutions | CMS-XML

MPX DB extension backups fail intermittently with status 54.

07:17:18.312 [18037] 2 send_brm_msg: DATASOCKET client-1_1279273728 3080 07:17:18. 319 [23645] 2 fill_buffer: child.c.1027: Calling: bpcr_get_socket_rqst4 The parent is also able to respond to the bpbrm request for a forwarding socket for the fourth job, then start a child to wait for the dbclient to attach to the end of the socket.
TECH138071 | 2011-02-22
Technical Solutions | CMS-XML

File Read error on netbackup client 7.0 | Symantec Connect

07:58:37.299 [20840588] <4> is_excluded: Excluded /oracle/E8P/sapdata5 by exclud e_list entry /oracle*/*/sapdata*/ 07:58:37. 319 [20840588] <4> is_excluded: Excluded /oracle/E8P/sapdata6 by exclud e_list entry /oracle*/*/sapdata*/
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:25:33.973 [4665] <2> db_end: Need to collect reply 14:25:38.317 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:25:38. 319 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML

Snapshot error(not in cluster) | Symantec Connect

Snapshot error(not in cluster) 9:10:14. 319 PM: [23272.46184] <4> dos_backup::tfs_include: INF - folder (ctmxs235) has been created recently (since 6/15/2012 12:46:07 AM). It will be backed up in full.
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

18:30:01.132 [4452.1652] <4> read_data: successfully read (duplicate) backup id hqeclt01_1345158490, copy 1, fragment 1, 2080 Kbytes at 44255. 319 Kbytes/sec
Connect Forums | HTML

Status Code Chart

318 319 320
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

STATUS CODE 5 and 227: After successful backups, Microsoft SQL Server restores fail with a NetBackup Status Code 5 (the restore failed to recover the requested files) and NetBackup Status Code 227 (no entity was found).

12:39:42. 319 [19005] 2 fileslist: begin db communication 12:39:42.319 [19005] 2 fileslist: criteria sent to db mgr 12:39:42.368 [19005] 2 fileslist: unexpected return value from db_flistreceive: no entity was found 227
TECH51393 | 2010-01-07
Technical Solutions | CMS-XML

Status 58: All NetBackup client backups to a Solaris NetBackup media server fail

The NetBackup bpcd log on the NetBackup media server shows that bpcd connections to media server fail when attempting to connect back to itself on vnetd (port 13724): 00:00:02. 319 [4345] 2 bpcd main: offset to GMT 18000
TECH66737 | 2010-01-09
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?