NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 249

Robotic status code 249
HOWTO104749 | 2014-11-20
How To | CMS-XML

NetBackup status code: 249

NetBackup status code : 249
HOWTO104163 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: NDMP Backups with NetBackup 6.5.x fails with Status 249 and 229

GENERAL ERROR : NDMP Backups with NetBackup 6.5.x fails with Status 249 and 229
TECH61273 | 2013-10-29
Technical Solutions | CMS-XML

Intermittent status 13/99/249 during NDMP backups with AIX master or media servers BPBRM- db_flistsend failed: file read failed (13)

Intermittent status 13/99/ 249 during NDMP backups with AIX master or media servers BPBRM- db_flistsend failed: file read failed (13)
TECH157680 | 2013-10-25
Technical Solutions | CMS-XML

When performing a backup of a client with NetBackup, the backup job completes with status 249

When performing a backup of a client with NetBackup, the backup job completes with status 249
TECH167161 | 2011-08-16
Technical Solutions | CMS-XML

STATUS CODE 249: When performing a backup of a client with NetBackup, the backup job completes with Status 249.

STATUS CODE 249 : When performing a backup of a client with NetBackup, the backup job completes with Status 249 .
TECH49166 | 2010-01-17
Technical Solutions | CMS-XML

GENERAL ERROR: TIR backup failing with status 249

GENERAL ERROR : TIR backup failing with status 249
TECH66218 | 2009-01-05
Technical Solutions | CMS-XML

BUG REPORT: NDMP Backups from an AIX NDMP Agent Media Server can fail with Status 13

REFERENCE: Intermittent status 13/99/ 249 on AIX masters during NDMP backups: BPBRM- db_flistsend failed: file read failed http://www.symantec.com/docs/tech157680
TECH128789 | 2013-10-25
Technical Solutions | CMS-XML

update_clients install fails with status 25 for clients configured for Resilient Network

1 1 1 10.81.40.61:45496 - 10.82.104. 249 :13724 10.81.40.61:45498 - 10.82.104.249:13724
TECH204402 | 2013-04-12
Technical Solutions | CMS-XML

user-directed backup, restore, and image list operations fail with status 133 if the client database exits.

15:01:16.327 [2350] 2 connected_peer: Connection from host beetle-v2 , 10.82.104. 249 , on non-reserved port 40776 ...snip...
TECH67669 | 2013-03-21
Technical Solutions | CMS-XML

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

12:00:02.480 [22497] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.33299 TO 1.1.1.1.13724 12:00:03. 249 [22497] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.33301 TO 1.1.1.1.13724
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML

BUG REPORT: VMWare Consolidated Backups (VCB) repeat "Error bptm(pid=1784) read of TIR file failed: the file list is incomplete" after receiving "failure reading raw device"

18:55:24.075 [1784.5804] 2 logconnections: BPDBM CONNECT FROM From IP.3376 TO To IP.13724 19:15:24.279 [1784.5804] 2 setup_tir_read: string received from bpdbm is ( 249 -1) 19:15:24.279 [1784.5804] 2 set_job_details: Sending Tfile jobid (1005767)
TECH70378 | 2010-01-22
Technical Solutions | CMS-XML

Client backups failing with error 42

16:28:01. 249 [6708.6336] db_error_add_to_file: dberrorq.c:midnite = 1210892400
TECH60570 | 2010-01-10
Technical Solutions | CMS-XML

BUG REPORT: Vault internal error 286

06:36:35.113 [3006544] 32 vltrun@DupBatch::merge^673: pre-condition violated: Vital stats of batches don t match in dup_batch.cpp near 249
TECH68282 | 2010-01-08
Technical Solutions | CMS-XML

The bplist command fails with EXIT STATUS 23: socket read failed

myclient.com myclient.com 10.82.105. 249 37005
TECH71215 | 2009-01-11
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?