NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 184

NetBackup status code : 184
HOWTO104104 | 2014-11-20
How To | CMS-XML

Backups of Encrypted Clients fail with Status 184.

Backups of Encrypted Clients fail with Status 184 .
TECH126181 | 2013-10-24
Technical Solutions | CMS-XML

Backup with encryption configured on client fails with STATUS 184, "tar had an unexpected error"

Backup with encryption configured on client fails with STATUS 184 , "tar had an unexpected error "
TECH66078 | 2012-07-28
Technical Solutions | CMS-XML

NetBackup status code 184: tar had an unexpected error

184
TECH58656 | 2009-01-12
Technical Solutions | CMS-XML

PureDisk / MSDP (Media Server Deduplication Pool) backups fail with STATUS 87 or STATUS 14 after the Storage Server has been upgraded to NetBackup 7.6

10:02:27.925 [8304.12100] 2 i_sts_copy_extent: offset from:8704 to:0 length=52428791296 written=253440 stserr=2060005 cpy_flag=2 10:02:29.517 [8304.12100] 2 ost_proxy_copy_whole_image: extent loop 1 r=2060005 (52428791296 253440 253440) 0 500 10:02:32. 184 [8356.8116] 2 set_job_details: Tfile (662838): LOG 1389603752 32 bptm 8356 sts_close_server failed: error 2060005 object is busy, cannot be closed
TECH214856 | 2014-08-29
Technical Solutions | CMS-XML

Restores of client encrypted backups fail with status 5 after upgrading the client to NetBackup 7.0.1 or later.

7:03:58.075 PM: [1320.7844] 2 tar_base::backup_finish: TAR - restore: image data: 2560 bytes 7:03:58.075 PM: [1320.7844] 2 tar_base::backup_finish: TAR - restore: elapsed time: 103 secs 24 bps 7:03:58.075 PM: [1320.7844] 2 tar_base::v_vtarmsgw: INF - TAR EXITING WITH STATUS = 184
TECH169376 | 2013-10-28
Technical Solutions | CMS-XML

GENERAL ERROR: Network errors during Oracle RMAN backups when using xinetd resulting in status 6, status 23, status 25, status 41, or status 58

08:20:38.891 [5871] 2 vnet_connect_to_vnetd_extra: vnet_vnetd.c.179: msg: VNETD CONNECT FROM 1.2.3.4.54106 TO 2.3.4.5.13724 fd = 10 08:20:38.892 [5871] 2 vnet_pop_byte: vnet.c. 184 : errno: 232 0x000000e8
TECH58196 | 2013-10-24
Technical Solutions | CMS-XML

Cannot write image media i/o device error - Status 84

06:25:22.394 [6368.5552] 2 write_data: received first buffer (64512 bytes), begin writing data 06:29:14. 184 [6368.5552] 2 write_data: write of 64512 bytes indicated only 0 bytes were written , err = 1117
TECH74634 | 2013-06-06
Technical Solutions | CMS-XML

Backup and restore operation fail with status 25 when multi-homed Windows 2008 clients have stronghost enabled

.13724 fd = 556 13:22:30.188 [9928.5332] 2 vnet_pop_byte: ..\libvlibs\vnet.c. 184 : errno: 10054 0x00002746 13:22:30.188 [9928.5332] 2 vnet_pop_byte: ..\libvlibs\vnet.c.186: Function failed: 43 0x0000002b
TECH63457 | 2013-04-16
Technical Solutions | CMS-XML

NDMP alternate client restore to a remote Quantum dxi8500 is selecting a non-ndmp drive, causing the restore to fail with status 5.

05/31/2012 12:37:15. 184 PID:7716 File ID:134 [Error] ndmp_data_connect_v3 failed, status = 23 (ndmp_connect_err)
TECH202154 | 2013-01-28
Technical Solutions | CMS-XML

Incremental Catalog backup fails with Status 41 (network connection timeout)

/usr/openv/netbackup/db/images/master1/1243000000/tmp/nb-catalog_1243231645_incr.f 10:48:29. 184 [19001] 2 add_files: 5000 files added to /usr/openv/netbackup/db/images/master1/1243000000/tmp/nb-catalog_1243231645_incr.f
TECH71176 | 2010-01-05
Technical Solutions | CMS-XML

Backup error: exit_status = 84 : io_ioctl: MTWEOF failed during error recovery, Input/output error

22:33:53.184 [8390] 2 io_ioctl: MTWEOF failed during error recovery, Input/output error 22:33:53. 184 [8390] 2 tape_error_rec: attempting error recovery, delay 3 minutes before next attempt, tries left = 2 22:36:53.196 [8390] 2 io_ioctl: command (5)MTWEOF 0 from (overwrite.c.489) on drive index 9
TECH59178 | 2010-01-27
Technical Solutions | CMS-XML

BUG REPORT: (Cold) offline catalog backup reports 'failed to perform database backup' even though the job completed successfully with status 0.

01/21/08 09:41:33. 184 117 PID:5107 [jobinst_i::requestResources] request resources, jobid=284640
TECH56239 | 2008-01-26
Technical Solutions | CMS-XML

GENERAL ERROR: Automatic or manual relocation of data from Disk Staging to Tape storage units fail immediately with Error 25.

10/24/2007 19:45:24.607 [Debug] NB 51216 137 PID:1704 TID:4992 File ID:153 [No context] 6 [BPCRConnector::handle_input] +++ ENTERING +++ : obj = 00c72010 (BPCRConnector.cpp: 184 )
TECH55161 | 2008-01-02
Technical Solutions | CMS-XML

GENERAL ERROR: Windows cannot initialize the device driver for this hardware. (Code 37)

PNP Device IDROOT\SCSIADAPTER\0000 Driverc:\winnt\system32\drivers\emcpbase.sys (4.4.0.0070, 262.88 KB (269, 184 bytes), 11/24/2004 3:49 PM) EMC has documented a conflict with VERITAS Tape Device Drivers and EMC PowerPath 4.4.0 in the Release Notes for EMC PowerPath for Windows, P/N 300-002-313, Rev a07, August 17, 2005.
TECH46214 | 2007-01-10
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?