NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 151

NetBackup status code : 151
HOWTO90569 | 2013-10-02
How To | CMS-XML

NetBackup status code: 151

NetBackup status code : 151
HOWTO50917 | 2012-11-19
How To | CMS-XML

NetBackup status code: 151

NetBackup status code : 151
HOWTO35027 | 2010-10-29
How To | CMS-XML

How to troubleshoot NDMP Backups failures when status code 99 (or other NDMP backup failure) is reported. Includes logging instructions.

install path \NetBackup\bin\vxlogcfg -a -p 51216 -o 134 -s DebugLevel=6 -s DiagnosticLevel=6 install path \NetBackup\bin\vxlogcfg -a -p 51216 -o 151 -s DebugLevel=6 -s DiagnosticLevel=6 For Unix media server:
TECH56492 | 2014-07-11
Technical Solutions | CMS-XML

Large NDMP restores to NetApp filers fail with status 5 on account of a defect in bytes_processed value returned by the filer.

On account of a defect in calculating bytes_processed by NDMP server on NetApp filer, it was found that the value returned by filer at a given time may be less than the value returned earlier. Here is a sample from NDMP session, (this pattern can be found by running grep bytes_processed for vxlogview for the originator id 151 .
TECH67759 | 2013-10-24
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)

PID:14221422 File ID: 151
TECH157680 | 2013-10-25
Technical Solutions | CMS-XML

BUG REPORT: Large NDMP backups to filers fail with status code 23 (socket read failed) reported.

To see if this change has taken effect, check the ndmp logs (OID 151 ) for the following message: ndmp_net_connect: Timeout Value: 480000
TECH66020 | 2013-10-24
Technical Solutions | CMS-XML

Duplications to ndmp device fail with status 90

01/14/13 12:07:49.831 [Debug] NB 51216 ndmp 151 PID:1628 TID:9088 File ID: 151 [No context] 1 [ndmp_logger_vxul] 00000000010b0930 - (1104) 246690 [0] 12:07:49 ndmp_tape_write (0x304) ndmp_no_err (0x0)
TECH206010 | 2013-10-01
Technical Solutions | CMS-XML

NDMP backups fail with status 13 or status 42

Status 13 Status 42 ndmpagent (OID=134) ndmp (OID= 151 ) reports:
TECH199943 | 2013-06-20
Technical Solutions | CMS-XML

Netbackup catalog restore fails with status 47 or 25

14:02:55.607 [6084.4504] 2 vnet_async_connect: vnet_vnetd.c.4172: connect: async CONNECT FROM 10.16.248. 151 .2068 TO ip_media_server
TECH70578 | 2012-08-18
Technical Solutions | CMS-XML

Backups of UNIX client will fail with status 13 (File Read Failed) if the /etc/group file on the client does not have a group name defined.

13:17:38. 151 [7861] 2 bpdbm: request complete: exit status 13 file read failed BPBRM (Media server) 13:17:38.131 [7852] 2 db_end_sts: no DONE from db_getreply(): file read failed
TECH34703 | 2012-07-19
Technical Solutions | CMS-XML

GENERAL ERROR: VMWare Type 2 Backups are failing with "Error bpbrm (pid=21401) db_flistsend failed: file read failed (13)"

From the bpdbm log: 08:00:42. 151 [28982] 2 add_files: creating /usr/openv/netbackup/db/images/vmmachine1.veritas.com/1217000000/tmp/vmware-weekend_1217343601_full.f
TECH62391 | 2012-02-07
Technical Solutions | CMS-XML

MPX DB extension backups fail intermittently with status 54.

...snip... 06:47:02.144 [18032] 2 bpbrm spawn_brm_child: spawning child 06:47:02. 151 [18047] 2 bpbrm send_bpsched_connecting_msg: sending bpsched msg: CONNECTING TO CLIENT FOR client-2_1279273619
TECH138071 | 2011-02-22
Technical Solutions | CMS-XML

nbpemreq -subsystems command will return error message: "cannot connect to nbpem"

12/02/10 12:57:03. 151 [Debug] NB 51216 nbpem 116 PID:687 TID:12 File ID:116 [No
TECH148534 | 2011-01-19
Technical Solutions | CMS-XML

GENERAL ERROR: FlashBackup fails with error; Unable to read metadata for index: <index>, VFM error = 5

10:56:16. 151 [7148.3740] 16 bpbrm handle_backup: from client cdcsrvr1: ERR - Unable to read metadata for index: 850737, VFM error = 5.
TECH58050 | 2010-01-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?