NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 125

NetBackup status code : 125
HOWTO90546 | 2013-10-02
How To | CMS-XML

NetBackup status code: 125

NetBackup status code : 125
HOWTO50894 | 2012-11-19
How To | CMS-XML

NetBackup status code: 125

NetBackup status code : 125
HOWTO35004 | 2010-10-29
How To | CMS-XML

Backup fails with status 24 after the network stops delivering data to the media server.

Friday October 9 05:14:38 GMT 2009 10.43.2.62.13724 198.235. 125 .52.42317 1 0 49344 0 ESTABLISHED
TECH76201 | 2013-06-20
Technical Solutions | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

The direct updates to bpjobd and bpdbm, in this example, are all successful; the last of which is shown here. 03:49:44. 125 [43776] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.44491 TO 1.1.1.1.1556 fd = 6 03:49:44.145 [43776] 2 db_end: Need to collect reply
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

Backup completes with status 1 - BMR not collecting disk configuration

24/05/2011 11:15:54. 125 [Application] NB 51216 bmrsavecfg 121 PID:976 TID:5096 File ID:121 [No context] [Error] v-121-35 BMR information discovery failed
TECH162813 | 2014-01-24
Technical Solutions | CMS-XML

GENERAL ERROR: Lotus Notes database restores fail with a socket error if there is a faulty NIC on the Veritas NetBackup (tm) master server.

11:57:38. 125 [2636.2012] 16 write_to_out: cannot write data to socket, 10054
TECH39360 | 2013-10-23
Technical Solutions | CMS-XML

BUG REPORT: Vault jobs failing with Status 332 (error getting information from EMM database)

9/15/2007 13:28:43. 125 [Debug] NB 51216 137 PID:2376 TID:5588 File ID:111 [No context] 4 [TAO] TAO (2376|5588) - giop_message_base::dump_msg, send GIOP v1.2 msg, 4464020 data bytes, my endian, Type Reply[13]
TECH54494 | 2013-10-24
Technical Solutions | CMS-XML

A rare potential for data loss has been discovered in NetBackup if a socket error occurs at the exact instant that a Media Server is writing True Image Restore (TIR) data to media during a multiplexed (MPX) backup. This may result in a "found wrong backup id" message during restore, verify, or duplication.

15:32:33. 125 [8511.7133] 16 write_data_tir: socket operation failed - 10054 (at bptm.c.28938)
TECH64161 | 2013-10-24
Technical Solutions | CMS-XML

BUG REPORT: SAP backups on Linux exit with status 130.

SAP backups on Linux exit with status 130 after a signal 11 is logged in bpbkar The Oracle database has a large number of database files ( 125 database files produced the problem). SAP brbackup util_file online or offline. From the bpbkar log:
TECH53930 | 2013-10-24
Technical Solutions | CMS-XML

Media Manager status code 58

unable to obtain bound socket, Address already in use ( 125 )
HOWTO90936 | 2013-10-02
How To | CMS-XML

Media Manager status code 58

unable to obtain bound socket, Address already in use ( 125 )
HOWTO51285 | 2012-11-19
How To | CMS-XML

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

11:05:23. 125 [22492] 2 bpbrm read_media_msg: read from media manager: WROTE client4_1249894526 0 0 5386.076 0
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML

SLP duplications using shared memory are failing with status code 12/35

11:41:12. 125 [15483] 2 logconnections: BPDBM CONNECT FROM 144.42.24.1.35918 TO 144.42.73.15.13724
TECH155827 | 2011-03-17
Technical Solutions | CMS-XML

BUG REPORT: The Oracle backup process may fault if certain other errors occur during the data transfer

VxBSASendData()+ 125 call bsa_put() 003fc50c0 ? 000040000 ?
TECH77618 | 2010-12-01
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?