NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 180

NetBackup status code : 180
HOWTO104100 | 2014-11-20
How To | CMS-XML

BUG REPORT: Duplication jobs fail with status code 50 (Client process aborted) reported

07:01:49.682 [6092.6824] 2 bptm: Calling tpunmount for media 0148l3 07:01:49.682 [6092.6824] 2 send_mds_msg: media_done 0 299454 0 0148l3 4000089 180 {acb7070f-151c-4c45-aefb-cf622e9e1f4d} 07:01:49.682 [6092.6824] 2 JobInst::sendIrmMsg: starting
TECH56753 | 2010-09-07
Technical Solutions | CMS-XML

BUG REPORT: Duplication job using SharedDisk receives a status code 800 error due to emmstatus=914 but activity monitor shows status code 0.

[15036] 2 drivename_unlock: unlocked 17:20:55.850 [15036] 2 drivename_close: Called for file acs004-0.3.1.4 17:20:55.850 [15036] 2 send_mds_msg: media_done 0 3899779 0 m10102 4007072 180 {6c74bafe-1dd2-11b2-b5bd-0003ba830c31}
TECH70228 | 2014-11-06
Technical Solutions | CMS-XML

Backup with Accelerator and Deduplication to appliance failed with status 14

Create: ..netbackup/db/config/cd_update_interval with a value of 180 Create: ..netbackup/db/config/ost_cd_busy_retry_limit
TECH213488 | 2014-03-18
Technical Solutions | CMS-XML

Incremental backup using client direct fail with status 14

$install_path\netbackup\db\config\cd_whole_image_copy $install_path\netbackup\db\config\cd_update_interval with a value of 180 $install_path\netbackup\db\config\ost_cd_busy_retry_limit with a value of 1500
TECH185860 | 2013-11-12
Technical Solutions | CMS-XML

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

log of the media server, messages similar to the following are found: 19:01:10. 180 [4792.5372] 2 NdmpSession: [514] Sending 15 (get_kbytes) 19:06:07.258 [4792.5372] 2 NdmpSession: [514] Reply 15 433281744 , error = 0
TECH66020 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: The available_media script incorrectly lists a volume's status as DBBACKUP, and script execution time is slow when many tapes exist in the mediaDB.

3. Go to the line where bpmedialist is being piped to a while loop (typically this entry is around line 180 or so) 4. Comment out the bpmedialist
TECH6059 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: A restore using an alternate media server fails with Status Code 5 and the error ' client hostname could not be found '

shows the restore still wants to use the original Media server: 02:25:57.060 [6541] 2 start_mpx_group: /usr/openv/netbackup/bin/bpbrm bpbrm -restore -mpx_restore -S MASTER -mt 2 -to 0 -mud 180 -mediasvr oldmediasrv -masterversion 650000 02:25:57.060 [6541] 2 local_bpcr_connect: Can t connect to client source_client_name
TECH63986 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: Large SAP backups exit with status 50

....... 13:49:36.318 [10153] 2 send_mds_msg: media_done 0 -1198484877 0 d00000 4000129 180 13:49:36.323 [10153] 2 JobInst::sendIrmMsg: starting
TECH84193 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: Certain reports in Veritas NetBackup (tm) Advanced Reporter cause out of memory errors

at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java: 180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
TECH27726 | 2013-10-23
Technical Solutions | CMS-XML

A potential for skipped duplications has been discovered in NetBackup 6.5.4 when using Vault, or in NetBackup versions 6.5.1 - 6.5.3 if a specific vltrun binary has been applied. Vault may end with status code 0, 306 or 308 if duplication rules are configured. If a Status 0 occurs due to this issue, duplications are skipped without indication.

For example, the offending rule satisfies (i) above: 10:20:46. 180 [1588] 4 vltrun@LogDuplicationBatches^1434: DupRule for MS=ms1 #Batches=4 10:20:46.182 [1588] 4 vltrun@LogDuplicationBatches^1434: DupRule for MS=ms2 #Batches=4
TECH72483 | 2013-10-24
Technical Solutions | CMS-XML

NDMP restore failing with nbrb status: RB deallocated orphaned resources

set the /usr/openv/var/global/nbrb.conf file with the following settings: seconds_for_eval_loop_release = 180 respect_request_priority = 0
TECH181938 | 2012-07-28
Technical Solutions | CMS-XML

GENERAL ERROR: Even though backup resources are available, backups are taking hours to go active and complete. However, if they are canceled and re-submitted, they take off and complete right away.

Example format for parameters in nbrb.conf seconds_for_eval_loop_release = 180 respect_request_priority = 0
TECH57277 | 2012-02-08
Technical Solutions | CMS-XML

SharePoint Granular Restore Technology (GRT) Restore Fails with Status Code: 5

SharePoint Document Level Restore fails with a status code 5, or 180 .
TECH171172 | 2012-01-10
Technical Solutions | CMS-XML

BUG REPORT: At all versions of NetBackup 6.5 and 6.0 MP5, 6.0mp6, 6.0mp7, 7.0, 7.0.1, 7.1, 7.1.0.1 and 7.1.0.2, bpdm may core dump during duplication of Oracle SAP type backups when a media position error occurs on the read process.

06:36:06. 180 [20450] 2 media_dispatch_signal: calling catch_signal for 1 (bpdm.c:2797) delay 0 seconds
TECH164148 | 2011-12-20
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?