NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 830

NetBackup status code : 830
HOWTO104827 | 2014-11-20
How To | CMS-XML

Error nbjm(pid=4484) NBU status: 830, EMM status: All compatible drive paths are down, but media is available drive(s) unavailable or down(830)

Error nbjm(pid=4484) NBU status : 830 , EMM status : All compatible drive paths are down, but media is available drive(s) unavailable or down( 830 )
TECH125106 | 2014-06-05
Technical Solutions | CMS-XML

Restores fail with message of 'NBJM returned an extended error status: drive(s) unavailable or down (830)'

12/28/2010 12:57:59 - Error bptm (pid=xxxx) NBJM returned an extended error status: drive(s) unavailable or down (830) 12/28/2010 12:57:55 - requesting resource mediaID 12/28/2010 12:57:55 - Error nbjm (pid=xxxxx) NBU status : 830 , EMM status : No drives are available
TECH147079 | 2011-01-30
Technical Solutions | CMS-XML

STATUS CODE 830: "All compatible drive paths are down, but media is available".

830
TECH71590 | 2010-01-17
Technical Solutions | CMS-XML

NBU status: 830, EMM status: No drives are available | Symantec Connect

NBU status : 830 , EMM status : No drives are available
Connect Forums | HTML

NetBackup backups are failing with Status 24 due to network issue in the environment

12:11:52. 830 PM: [6552.6976] 2 TransporterRemote::write[2](): DBG - | An Exception of type [SocketWriteException] has occured at: | Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.54.126.1
TECH217961 | 2014-05-30
Technical Solutions | CMS-XML

Restore failing with Restore error(2850)

Restore failing with Restore error(2850) NBJM returned an extended error status: No drives are available (2001) NBU status : 830 , EMM status : No drives are available
TECH215318 | 2014-03-25
Technical Solutions | CMS-XML

DB2/Informix/Oracle/SAP/sql-server/Sybase backup fails with status 25 if media ready occurs during client call-back

: INF - Data socket = mymm.4146 12:20:48. 830 [11520] 2 bpbrm spawn_brm_child: bpbrm child pid = 12147 12:20:48.850 [12147] 2 bpbrm write_msg_to_progress_file: INF - Name socket = mymm.1833
TECH135901 | 2012-03-27
Technical Solutions | CMS-XML

SAP restore fails with status 12 on mediaserver/client.

...snip... 08:52:45. 830 [10039] 2 mpx_read_data: begin reading data from media id l2z103, file num 1 08:52:45.830 [10039] 2 mpx_read_data: Total Kbytes transferred 0
TECH72223 | 2010-01-08
Technical Solutions | CMS-XML

Restore error(2850) | Symantec Connect

Restore error(2850) 13/11/2014 12:28:34 PM - requesting resource nocc07 13/11/2014 12:28:34 PM - Error nbjm(pid=7072) NBU status : 830 , EMM status : No drives are available 13/11/2014 12:28:34 PM - Error nbjm(pid=7072) NBU status: 830, EMM status: No drives are available
Connect Forums | HTML

MSSQL backup jobs fails intermittent with status 6 the last 4-5 weeks | Symantec Connect

MSSQL backup jobs fails intermittent with status 6 the last 4-5 weeks 17:39:13. 830 [10360.11880] <2> logconnections: BPRD CONNECT FROM XXX.XX.XXX.XX.63476 TO YYY.YY.YYY.YY.1556 fd = 872
Connect Forums | HTML

Status Code Chart

823 830 831
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Status 96 and Status 98 during media related operations.

8/19/2014 11:38:00 AM - requesting resource NetBackup: media_id 8/19/2014 11:38:00 AM - Error nbjm(pid=4552) NBU status : 830 , EMM status : No drives are available 8/19/2014 11:38:07 AM - end Erase; elapsed time: 0:00:08
TECH223913 | 2014-08-19
Technical Solutions | CMS-XML

STATUS CODE 69: Exchange 2000 backups fail with a NetBackup Status Code 69 (invalid filelist specification) when snapshot backups are enabled.

05:47:22. 830 PM: [560.5292] 2 WinMain: DAT - lpCmdLine = -r 1209600 -ru root -dt 0 -to 0 -clnt kynudcms004 -class kynudcms004_daily_exchange_db -sched daily_full -st FULL -bpstart_to 300 -bpend_to 300 -read_to 300 -stream_count 4 -stream_number 1 -jobgrpid 331 -use_otm -use_ofb -b kynudcms004_1181666831 -fso -fi - S kynudcms028 -fim NONE
TECH52640 | 2012-02-20
Technical Solutions | CMS-XML

NBDB upgrade from 6.5.6 to 7.1 fails with "All threads are blocked".

14:14:26. 830 [22890] 16 NBDBsystem: System call failed with status : 256
TECH186968 | 2013-01-10
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?