NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 86

Media Manager status code 86
HOWTO104465 | 2014-11-20
How To | CMS-XML

Device configuration status code 86

Device configuration status code 86
HOWTO104621 | 2014-11-20
How To | CMS-XML

NetBackup status code: 86

NetBackup status code : 86
HOWTO104014 | 2014-11-20
How To | CMS-XML

STATUS CODE: 86, Backup fails with exit status 86 Media Position Error. Problem log shows: ioctl (MTBSF) failed on media id <mediaID>, drive index <drive index number>, Inappropriate ioctl for device (bptm.c.<process id>)

86
TECH9258 | 2013-10-23
Technical Solutions | CMS-XML

Jobs fail with any of the following status codes: 84 - Media Write, 85 - Media Read, 86 - Media Position. There could be potential hardware issues that can cause these errors. There are several tools available from the hardware vendors that can be used to help diagnose these hardware issues.

86
TECH36257 | 2013-10-23
Technical Solutions | CMS-XML

3rd PARTY: Jobs fail with Status 86 (media position error) on a Sun server with rebranded Emulex HBAs. The bptm log reports "cannot locate on drive index 2, locate scsi command failed".

3rd PARTY: Jobs fail with Status 86 (media position error ) on a Sun server with rebranded Emulex HBAs. The bptm log reports "cannot locate on drive index 2, locate scsi command failed".
TECH48129 | 2011-08-15
Technical Solutions | CMS-XML

STATUS CODE 86: Backup jobs fail with a NetBackup Status Code 86 (media position error) and the system's device driver returns an I/O error while NetBackup was positioning media (tape or optical disk).

86
TECH56460 | 2009-01-24
Technical Solutions | CMS-XML

STATUS CODE: 86, 84, Backups are failing when using ait-4 drives with Veritas NetBackup (tm) 6.0

Backups to various supported ait-4 drives have been known to fail with a Status 86 (media position error ) or Status 84 (media write error ) when running NetBackup 6.0. This is known to be caused due to a problem with detecting the Small Computer System Interface (SCSI) protocol supported by the drive. If NetBackup detects that a drive will support the scsi-3 protocol, it will execute additional commands using a 16-byte Command Descriptor Block (CDB).
TECH45854 | 2009-01-28
Technical Solutions | CMS-XML

STATUS CODE: 86 and STATUS CODE 5; Restores fail with status code 5, but the BPTM log shows status 86 errors.

STATUS CODE : 86 and STATUS CODE 5; Restores fail with status code 5, but the BPTM log shows status 86 errors .
TECH37269 | 2006-01-07
Technical Solutions | CMS-XML

Media position errors 86 | Symantec Connect

Media position errors 86
Connect Forums | HTML

Multiple Media Errors 86,84 causing backups to fail | Symantec Connect

Multiple Media Errors 86 ,84 causing backups to fail
Connect Forums | HTML

VSphere 5.0 backup of Windows 2003 client fails with STATUS 130 and "ERROR :1735:scan operation failed:" using NetBackup 52xx appliance as VMware backup host

15:07:42.628 [12898] 2 set_job_details: Tfile (419123): LOG 1363702062 16 bpbrm 12898 from client sjira01: ERROR :1735:scan operation failed: 15:07:42.628 [12898] 2 send_job_file: job ID 419123, ftype = 3 msg len = 86 , msg = LOG 1363702062 16 bpbrm 12898 from client sjira01: ERROR :1735:scan operation failed: VxMS logs, with the non-error messages removed:
TECH205606 | 2013-09-12
Technical Solutions | CMS-XML

All VMware backups fail with snapshot creation failed, status 156

bpfis logs: 09:12:47.970 [4644.6624] 2 onlfi_vfms_logf: INF - vmwareLogger: BuildVirtualMachinesAndTemplatesView: entered , 86 09:12:48.001 [4644.6624] 2 onlfi_vfms_logf: INF - vmwareLogger: RetrieveDcMorAndObjMorFromPath: sym_vmc_error: failed_to_get_mob
TECH164857 | 2013-01-10
Technical Solutions | CMS-XML

NDMP backups fail with Status 99

Solaris 10 (x 86 ) with Netbackup 7.1.0.2 Clients and Master in different subnet
TECH171488 | 2012-07-28
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:05.939 [20439] 2 log_media_error: successfully wrote to error file - 06/16/11 06:36:05 a00001 26 position_error STK.t10kb.000 06:36:05.939 [20439] 2 check_error_history: just tpunmount: called from bptm line 24203, exit_status = 86 The bpdm
TECH164148 | 2011-12-20
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?