NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Single file restore from VMware backup image fails with EXIT STATUS 185

02/06/2015 18:14:08 - restored from image client_name _1422986321; restore time: 0:01:01 02/06/2015 18:14:08 - Error bpbrm (pid=3812) client restore EXIT STATUS 185 : tar did not find all the files to be restored 02/06/2015 18:14:09 - end Restore; elapsed time 0:01:03
TECH228208 | 2015-02-09
Technical Solutions | CMS-XML

NetBackup status code: 185

NetBackup status code : 185
HOWTO104105 | 2014-11-20
How To | CMS-XML

Media Manager status code 185

Media Manager status code 185
HOWTO104536 | 2014-11-20
How To | CMS-XML

NetBackup for Microsoft Exchange database restore fails with status 185, "MountDatabase failed with error(0x0)"

NetBackup for Microsoft Exchange database restore fails with status 185 , "MountDatabase failed with error (0x0)"
TECH175849 | 2014-07-23
Technical Solutions | CMS-XML

STATUS CODE 185: A "tar did not find all the files to be restored" occurs on restore.

Overview A status 185 tar did not find all the files to be restored occurs on restore. Troubleshooting
TECH36506 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: Status 185 when restoring Encrypted File System data protected by Flashbackup

GENERAL ERROR : Status 185 when restoring Encrypted File System data protected by Flashbackup
TECH66460 | 2012-11-18
Technical Solutions | CMS-XML

Restore from a fullbackup vmware fails with status 185

Restore from a fullbackup vmware fails with status 185
TECH168667 | 2011-11-24
Technical Solutions | CMS-XML

NetBackup status codes related to hyper-v

156, snapshot error encountered See Snapshot error encountered (status code 156) 185 , tar did not find all the files to be restored
HOWTO70816 | 2014-12-13
How To | CMS-XML

EXIT STATUS 185: tar did not find all the files to be restored | Symantec Connect

EXIT STATUS 185 : tar did not find all the files to be restored
Connect Forums | HTML

Restore of a large VMware virtual machine may fail with status 5/2817/2820 due to VM creation timing out after 2 hours

02:42:46.843 [5900.1860] 2 logconnections: BPCD CONNECT FROM 10. 185 .10.145.2898 TO 10.185.10.146.1556 fd = 1344
TECH171837 | 2014-10-07
Technical Solutions | CMS-XML

Individual files restore from VMware backup fails with status 2820

Individual files restore from VMware backup fails with status 2820. Status 185
TECH197978 | 2014-01-10
Technical Solutions | CMS-XML

After jobs hanging and failing with error 252, all new jobs remain queued

job hung at send_mds_msg : 06:27:53. 185 [11264146] 2 send_mds_msg: MEDIADB 1 177977 a00309 4000462 *NULL* 20 1376086272 1376086272 1384121472 0 0 0 0 5 14 0 0 1024 0 65627 0 06:57:53.235 [11264146] 2 insert_if_not_dup: ../../libvlibs/vnet_addrinfo.c.5827: 0: ignoring ipv6 loopback: 0 0x00000000
TECH211569 | 2014-01-09
Technical Solutions | CMS-XML

Vmware virtual machine restore failed with error "FTL - Virtual machine restore: file write failed"

06/28/2012 16:58:44 - end reading; read time: 1:35:32 06/28/2012 16:58:50 - Error bpbrm (pid=6332) client restore EXIT STATUS 185 : tar did not find all the files to be restored
TECH192738 | 2013-11-27
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

0x000000e8 08:20:38.892 [5871] 2 vnet_pop_byte: vnet.c. 185 : Function failed: 43 0x0000002b 08:20:38.893 [5871] 2 vnet_pop_string: vnet.c.266: Function failed: 43 0x0000002b
TECH58196 | 2013-10-24
Technical Solutions | CMS-XML

Restore from vmware machine cumulative backup fail with status code 2820 reported.

185
TECH210512 | 2013-09-12
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?