NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 614

NetBackup status code : 614
HOWTO104311 | 2014-11-20
How To | CMS-XML

How to configure email notification and the different methods to email backup exit statuses from a UNIX master in NetBackup

00:02:28. 614 [25398] 2 OpenMailPipe: /usr/ucb/mail -s Backup on client - 54 started user@domain.com /dev/null 2 /dev/null
TECH32539 | 2014-07-08
Technical Solutions | CMS-XML

Restore to a Windows 2003 client from a Windows 2008 R2 media server failing with status code 23

The corresponding errors reported in the bptm log on the media server: 15:33:18. 614 [6436.1676] 2 ConnectionCache::connectAndCache: Acquiring new connection for host NBMASTER1, query type 1 15:33:18.630 [6436.1676] 2 vnet_pbxconnect: pbxConnectEx Succeeded
TECH180624 | 2012-07-06
Technical Solutions | CMS-XML

Some of the SAP application backup jobs fail with status 90 without backing up any files.

05:43:03.574 [8107] 4 bpbkar PrintFile: /oracle/SID/920/dbs/initSID.utl 05:43:07. 614 [8107] 4 bpbkar PrintFile: /oracle/SID/sapreorg/spaceSID.log 05:43:11.664 [8107] 4 bpbkar PrintFile: /oracle/SID/sapbackup/bealldaf.anf
TECH70742 | 2012-02-09
Technical Solutions | CMS-XML

BUG REPORT: nas_snapshot restores are failing with Status 71 due to incorrect REMAP String

11:28:11. 614 [5852.3508] 4 pfi_send_path_to_bkar: bpbkar remap string=BACKUP \\netapp01\TEST3\bbbbbbb mp6 backups\ USING \\netapp01\test3\~snapshot\NAS+NBU+PFI+nbutest01+test_nas_nackup_3+sr+vol3+2008.05.22.00h04m01s\\cccccc mp6 backups\ OPTIONS:
TECH60842 | 2012-01-25
Technical Solutions | CMS-XML

Many small jobs in a large MPX group may result in slow performance and status 13 or status 6

11:59:58.884 [22497] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.33289 TO 1.1.1.1.13724 11:59:59. 614 [22497] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.33291 TO 1.1.1.1.13724
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML

Catalog Backup is failing with status code 25/40

18:50:49.408 [5186] 2 bpbrm kill_child_process: start 18:50:49. 614 [5186] 4 db_error_add_to_file: could not write EXIT STATUS to stderr 18:50:49.633 [5186] 2 bpbrm Exit: client backup EXIT STATUS 25: cannot connect on socket
TECH148416 | 2011-01-18
Technical Solutions | CMS-XML

SLP duplications fail with status 191 when read server cannot connect to write server

00:53:47 . 614 [4589] 2 write_backup: write_data() returned, exit_status = 0, CINDEX = 0, twin_index = 0, backup_status = -7 00:53:47.614 [4589] 2 write_backup: tp.tv_sec = 1290581627, stp.tv_sec = 1290581183, tp.tv_usec = 614587, stp.tv_usec = 396998, et = 444217, mpx_total_kbytes[twin_index = 0] = 0
TECH145146 | 2010-11-29
Technical Solutions | CMS-XML

Backup to disk storage unit runs for several hours and then fails with status 84.

17:01:39.969 [438274] 2 write_data: received first buffer (262144 bytes), begin writing data 23:11:45.607 [438274] 2 write_data: fragmenting backup id myclient_1228258864, 524288000 Kbytes written 23:11:45. 614 [438274] 2 write_backup: write_data() returned, exit_status = 0, CINDEX = 0, backup_status = -6
TECH66095 | 2009-01-15
Technical Solutions | CMS-XML

BUG REPORT: Duplication may leave a bptm process hung on a Unix media server after posting a successful status 0 completion code.

10:08:49.602 [20491] 2 bpduplicate: Received keep alive 10:09:49. 614 [20491] 2 bpduplicate: Received keep alive 10:10:49.625 [20491] 2 bpduplicate: Received keep alive
TECH72346 | 2009-01-06
Technical Solutions | CMS-XML

GENERAL ERROR: Automatic or manual relocation of data from Disk Staging to Tape storage units fail immediately with Error 25.

10/24/2007 19:45:24.670 [Debug] NB 51216 137 PID:1704 TID:4992 File ID:153 [No context] 1 [bpcompatd_bpcd_end_connect_req] bpcompatdreq.cpp. 614 : vnet_receive_network_socket() failed: 9(bpcompatdreq.cpp:1493)
TECH55161 | 2008-01-02
Technical Solutions | CMS-XML

bptestbpcd: EXIT status = 25 cannot connect on socket | Symantec Connect

bptestbpcd: EXIT status = 25 cannot connect on socket 16:35:39. 614 [3660.3528] <2> logconnections: BPCD ACCEPT FROM 192.168.100.226.61837 TO 192.168.100.226.13782 fd = 380
Connect Forums | HTML

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

01:13:32.592 [11650] <2> bpcd main: output socket port number = 1 01:13:32. 614 [11650] <2> bpcd main: Duplicated vnetd socket on stderr 01:13:32.614 [11650] <2> bpcd main: <---- NetBackup 6.5 0 ------------initiated
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:21:13. 614 [4665] <2> db_end: Need to collect reply 14:21:20.245 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:21:20.249 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

18:36:05. 614 [5472.4344] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?