NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

STATUS CODE 153: The error message "Windows could not start the NetBackup Database Manager on local computer" and the service specific error 153 are returned when starting the NetBackup Database Manager Service.

STATUS CODE 153 : The error message "Windows could not start the NetBackup Database Manager on local computer" and the service specific error 153 are returned when starting the NetBackup Database Manager Service.
TECH18031 | 2013-10-23
Technical Solutions | CMS-XML

Media Manager status code 153

Media Manager status code 153
HOWTO91014 | 2013-10-02
How To | CMS-XML

NetBackup status code: 153

NetBackup status code : 153
HOWTO90571 | 2013-10-02
How To | CMS-XML

Media Manager status code 153

Media Manager status code 153
HOWTO51363 | 2012-11-19
How To | CMS-XML

NetBackup status code: 153

NetBackup status code : 153
HOWTO50919 | 2012-11-19
How To | CMS-XML

Unable to start NetBackup services. Status 153

Unable to start NetBackup services. Status 153
TECH164708 | 2011-08-23
Technical Solutions | CMS-XML

NetBackup status code: 153

NetBackup status code : 153
HOWTO35029 | 2010-10-29
How To | CMS-XML

Media Manager status code: 153

Media Manager status code : 153
HOWTO35473 | 2010-10-29
How To | CMS-XML

GENERAL ERROR: Disk Pool Creation fails when trying to configure Media Server Deduplication

log on the master server reports the following information: 11:33:59. 153 [16322] 2 ParseConfigExA: Option (client_name) redefined on line 11, discarding definition on line 10. 11:33:59.153 [16322] 2 ParseConfigExA: Option (client_name) redefined on line 12, discarding definition on line 11.
TECH130130 | 2014-01-05
Technical Solutions | CMS-XML

GENERAL ERROR: Large SAP backups exit with status 50

13:49:36.323 [10153] 2 JobInst::sendIrmMsg: starting 13:59:37. 153 [10153] 2 jmcomm_processexception: retrying call after CORBA::comm_failure 14:09:39.949 [10153] 2 jmcomm_processexception: retrying call after CORBA::comm_failure
TECH84193 | 2013-10-24
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pciex1077,2432.1077.152 pciex1077,2432.1077. 153 pciex1077,2432.1077.154
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

GENERAL ERROR: Automated Cartridge System (ACS) drives are in an AVR status.

RPC TCP client connection failed, RPC: Remote system errorErrno = 146(Connection refused)Remote Internet address:10.57.4.1, Port: 30031; 04-03-08 17:32:27 SSI[0]:[csi_freeqmem.c:152] ONC RPC: csi_freeqmem(): status :status_queue_failure; Dropping from Queue: Remote Internet address: 0.0.0.0,Port: 0 , ssi_identifier: 153 , Protocol: 838860800, Connect type: 0; Resolution
TECH59332 | 2013-09-15
Technical Solutions | CMS-XML

Optimized duplications jobs fail with status 13 after 1 or 2 hours

14:08:49 . 153 [13737] 4 ... number of bytes replicated, returned from SPAD 25: (39460845925) ...snip....
TECH163912 | 2013-02-15
Technical Solutions | CMS-XML

bpbrm cannot create data on socket with error code 25.

1:13:01.559 [5960.6840] 2 hosts_equal: Comparing hosts friendlymaster and friendlymaster 11:13:01.559 [5960.6840] 2 hosts_equal: names are the same 11:13:01.559 [5960.6840] 2 hosts_equal: Comparing hosts 153 .30.24.33 and friendlymaster
TECH74242 | 2011-03-09
Technical Solutions | CMS-XML

Duplication jobs exiting with status 96 / status 50 also result in a nbrb problem of processing "RB deallocated orphaned resources".

01/14/10 09:39:43. 153 PID:17423 TID:6 [MyMonitor::evaluate] allocation ID {baa2485a-1dd1-11b2-ac29-00144f43083c} is being classified as orphan; will be de-allocated in roughly 600 seconds
TECH130451 | 2010-01-12
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?