NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 619

Message: internal error 619 Explanation:
HOWTO104316 | 2014-11-20
How To | CMS-XML

NetBackup status code: 23 - How to troubleshoot backups that fail with status 23 "socket read failed".

12:44:38. 619 [4804.5184] 2 logconnections: BPCD ACCEPT FROM 10.1.2.3.47204 TO 10.1.2.37.13724
TECH56079 | 2013-04-24
Technical Solutions | CMS-XML

Backup failure with status code 99 for NDMP.

2014年09月09日 16:11:58. 619 [NdmpAgentLmLogger::Log] Creating server for 10.0.0.1 in Server Port Window 1025 to 5000
TECH224593 | 2015-02-19
Technical Solutions | CMS-XML

SAP Agent Backup Failing with error code c0000135.

10:26:00.604 [5172.5016] 4 bphdb: INF - BACKUP START 5172 10:26:00. 619 [5172.5016] 4 bphdb: INF - CONTINUE BACKUP message received 10:26:00.619 [5172.5016] 4 bphdb: INF - Processing E:\oracle\netbackup_scripts\sap_offline_backup.cmd
TECH213039 | 2014-02-25
Technical Solutions | CMS-XML

Client Direct backups to MSDP fail with status 83

15:24:52.443 [5887] 2 59249:bpbrm:5887:master1:probe: libsts openp() 13/10/30 15:24:52: opening module /usr/openv/lib/libstspibasicdisk.so 15:24:52. 619 [5887] 2 59249:bpbrm:5887:master1:probe: libsts openp() 13/10/30 15:24:52: opening module /usr/openv/lib/libstspinbostpxy.so
TECH212376 | 2013-11-11
Technical Solutions | CMS-XML

Multiple ungraceful reboots fails to start EMM on Master Server with Errors "Database [NBDB] is not available" nbdb log also shows Errors "ping_database: ErrMsg [Sybase][ODBC Driver][SQL Anywhere]Connection error: Unable to initialize requested communication links, ErrCode -1, Sqlstate 08001" and " NBDBsystem: System call failed with status: 2304"

/usr/openv/netbackup/logs/nbdb log shows the following errors: 20:08:11. 619 [14387] 4 nbdb_admin: Entering. 20:08:11.621 [14387] 4 nbdb_admin: SQLANY = /usr/openv/db/
TECH167618 | 2013-09-03
Technical Solutions | CMS-XML

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

12:08:48.376 [22497] 4 write_backup: successfully wrote backup id myclient_1249905798, copy 1, 1058 Kbytes 12:08:48. 619 [22497] 2 write_backup: waiting 10 seconds for start of another backup 12:09:23.537 [22497] 4 write_backup: successfully wrote backup id myclient_1249905344, copy 1, 866 Kbytes
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML

Status Code Chart

618 619 620
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

STATUS CODE 3: When attempting to start backups on a media server, a status code 3 is reported.

... 16:54:44. 619 [800.4856] 2 bpbrm Exit: client backup EXIT STATUS 3: valid archive image produced, but no files deleted due to non-fatal problems Resolution:
TECH58643 | 2010-01-14
Technical Solutions | CMS-XML

NetBackup messages

See NetBackup status code: 618 internal error 619 See NetBackup status code: 619
HOWTO103773 | 2014-11-20
How To | CMS-XML

BUG REPORT: After upgrading to NetBackup version 7.6.0.1, bpdbm processes appear to be using excessive RAM/CPU resources.

00:00:09. 619 [8900.8420] 32 DbmImage::create_dir_structure: cannot create image subdirectory: No such file or directory (2)
TECH223862 | 2014-09-18
Technical Solutions | CMS-XML

BUG REPORT: nbdb_move reports Move of database files failed

13:30:12.583 [7914] 4 nbdb_move: /usr/openv/db/bin//nbdb_move.bin -data /usr/openv/db/data -index /usr/openv/db/data -tlog /usr/openv/db/data 13:30:12. 619 [7914] 2 vnet_pcache_init_table: ../../libvlibs/vnet_private.c.232: 0: starting cache size: 200 0x000000c8
TECH217020 | 2014-05-16
Technical Solutions | CMS-XML

BUG REPORT: The NetBackup jobs database is recording an invalid job try in the jobs report.

KB written - 3047. 619 KB/sec,12/20/10 19:31:51 - 577 KB written - 8066.666 KB/sec,12/20/10 19:32:03 - end writing; write time: 000:00:37,1089,2165,265283,8066,,,,,,,,,,,1, ,,1,0,0,client_name_1292891484,,,,0, ,
TECH158625 | 2011-12-20
Technical Solutions | CMS-XML

Warning bptm cannot locate on drive index , No more data is on the tape. | Symantec Connect

Line 619 : 16:53:28.292 [10424.13532] <2> io_read_block: read error on media id xo0354, drive index 4 reading header block, len = 0; No more data is on the tape.
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?