cancel
Showing results for 
Search instead for 
Did you mean: 

Accelerator enabled backup failing with 84 (Media write error)

admin2025
Level 2

Accelerator enabled backups failing with 84 ( Media write error ) on a Particular client - Rest of the clients on the same STU are completing successful.

Backup successful when configured this policy in a regular test MS-WINODWS Policy - it is running fine.

 

Master : Linux(2.6.18-371.3.1.el5) UNIX Master Server 7.5.0.6

Media server : Linux(2.6.18-274.el5) UNIX Media Server 7.5.0.6

Client :   Windows2003(5) Windows Client 7.5.0.6



Error :

 

02/17/2014 23:57:08 - begin writing
02/17/2014 23:57:42 - Info bpbkar (pid=5480) change journal NOT enabled for <C:\>
02/18/2014 00:02:11 - Critical bptm (pid=21116) include image failed
02/18/2014 00:02:11 - Critical bptm (pid=21116) image write failed: error 2060046: plugin error
02/18/2014 00:02:11 - Critical bptm (pid=21116) sts_get_image_prop failed: error 2060046: plugin error
02/18/2014 00:02:34 - Error bptm (pid=21116) cannot write image to disk, Invalid argument
02/18/2014 00:02:34 - Info bptm (pid=21116) EXITING with status 84 <----------
02/18/2014 00:02:34 - Info bpbkar (pid=5480) done. status: 84: media write error
02/18/2014 00:02:34 - end writing; write time: 0:05:26
 
 
Please suggest !!!
4 REPLIES 4

Mark_Solutions
Level 6
Partner Accredited Certified

Can that client resolve the host name of your de-dupe server?

Generally it will be caused by the client not being able to get to the de-dupe pool to write to it

Take a look under \netbackup\bin\ost-plugins - there will be the server name in there and under that some config files - check those for server names etc.

admin2025
Level 2

Mark 

 

Client is able to resolve the storage server name fine.

I see the below files in ost-plugins directory -  

Directory of C:\Program Files\VERITAS\NetBackup\bin\ost-plugins

 
libstspipd.dll
libstspisoapwrapper.dll
pd.conf
      
No other info is there in it.

Mark_Solutions
Level 6
Partner Accredited Certified

Maybe a bit late now but this just came out http://www.symantec.com/docs/TECH216391

phan-
Not applicable

This happen to me. the same but my problem is im using mountpoint Estructure and im using Cross Mount Point in the policy to do the backup.  

Whe the job is passing to the Root Disk in my case D:\ fail the job

 

4/26/2014 3:19:35 PM - Info bpbkar32(pid=3480) not using change journal data for <D:\Appl\>: unable to locate change journal data
4/26/2014 3:19:35 PM - Info bpbkar32(pid=3480) not using change journal data for <D:\Appl\>: forcing rescan, each file will be read in order to validate checksums
4/26/2014 3:30:08 PM - Critical bptm(pid=6892) include image failed          
4/26/2014 3:30:08 PM - Critical bptm(pid=6892) image write failed: error 2060046: plugin error      
4/26/2014 3:30:08 PM - Critical bptm(pid=6892) sts_get_image_prop failed: error 2060046: plugin error       
4/26/2014 3:30:15 PM - Error bptm(pid=6892) cannot write image to disk, Invalid argument      
4/26/2014 3:30:15 PM - Info bptm(pid=6892) EXITING with status 84 <----------        
4/26/2014 3:30:26 PM - Info bpbkar32(pid=3480) done. status: 84: media write error       
4/26/2014 3:30:26 PM - end writing; write time: 00:11:15
media write error(84)