Backups are failing with error code 84 after writing 16gb of data in desktop

Question

Hi All ,Backup for one of the Lab PC is getting faled with 84 after writing some data .Please help me on this .&nbsp;Dec&nbsp;15,&nbsp;2019&nbsp;12:31:16&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=90913)&nbsp;starting&nbsp;backup&nbsp;job&nbsp;(jobid=5862919)&nbsp;for&nbsp;client&nbsp;07r-malvern02,&nbsp;policy&nbsp;GOLD-FS-07R-LABPC-GRP1,&nbsp;schedule&nbsp;WeeklyDec&nbsp;15,&nbsp;2019&nbsp;12:31:16&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=90913)&nbsp;requesting&nbsp;STANDARD_RESOURCE&nbsp;resources&nbsp;from&nbsp;RB&nbsp;for&nbsp;backup&nbsp;job&nbsp;(jobid=5862919,&nbsp;request&nbsp;id:{B27CAD80-1F60-11EA-9361-F55878484892})Dec&nbsp;15,&nbsp;2019&nbsp;12:31:16&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;MGW_FS_STGDec&nbsp;15,&nbsp;2019&nbsp;12:31:16&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;u0bpnbuma02.NBU_CLIENT.MAXJOBS.07r-malvern02Dec&nbsp;15,&nbsp;2019&nbsp;12:31:16&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;u0bpnbuma02.NBU_CLIENT.MAXJOBS.07r-malvern02Dec&nbsp;15,&nbsp;2019&nbsp;12:31:16&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;MediaID=@aaaas;DiskVolume=fs_lsu;DiskPool=mgw_fs_pool;Path=fs_lsu;StorageServer=s07dd002;MediaServer=w07pnbume02.myl.comDec&nbsp;15,&nbsp;2019&nbsp;12:31:16&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;w07pnbume07_MGW_FS_STUDec&nbsp;15,&nbsp;2019&nbsp;12:31:17&nbsp;PM&nbsp;-&nbsp;estimated&nbsp;33184826&nbsp;kbytes&nbsp;neededDec&nbsp;15,&nbsp;2019&nbsp;12:31:17&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=90913)&nbsp;started&nbsp;backup&nbsp;(backupid=07r-malvern02_1576431077)&nbsp;job&nbsp;for&nbsp;client&nbsp;07r-malvern02,&nbsp;policy&nbsp;GOLD-FS-07R-LABPC-GRP1,&nbsp;schedule&nbsp;Weekly&nbsp;on&nbsp;storage&nbsp;unit&nbsp;w07pnbume07_MGW_FS_STUDec&nbsp;15,&nbsp;2019&nbsp;12:31:18&nbsp;PM&nbsp;-&nbsp;started&nbsp;process&nbsp;bpbrm&nbsp;(pid=3368)Dec&nbsp;15,&nbsp;2019&nbsp;12:31:53&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;07r-malvern02&nbsp;is&nbsp;the&nbsp;host&nbsp;to&nbsp;backup&nbsp;data&nbsp;fromDec&nbsp;15,&nbsp;2019&nbsp;12:31:53&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;reading&nbsp;file&nbsp;list&nbsp;for&nbsp;clientDec&nbsp;15,&nbsp;2019&nbsp;12:32:01&nbsp;PM&nbsp;-&nbsp;connectingDec&nbsp;15,&nbsp;2019&nbsp;12:32:23&nbsp;PM&nbsp;-&nbsp;connected;&nbsp;connect&nbsp;time:&nbsp;0:00:00Dec&nbsp;15,&nbsp;2019&nbsp;12:32:25&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;starting&nbsp;bpbkar32&nbsp;on&nbsp;clientDec&nbsp;15,&nbsp;2019&nbsp;12:32:57&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbkar32&nbsp;(pid=6820)&nbsp;Backup&nbsp;startedDec&nbsp;15,&nbsp;2019&nbsp;12:32:57&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbkar32&nbsp;(pid=6820)&nbsp;change&nbsp;time&nbsp;comparison:&lt;disabled&gt;Dec&nbsp;15,&nbsp;2019&nbsp;12:32:57&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbkar32&nbsp;(pid=6820)&nbsp;archive&nbsp;bit&nbsp;processing:&lt;enabled&gt;Dec&nbsp;15,&nbsp;2019&nbsp;12:32:57&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=3108)&nbsp;startDec&nbsp;15,&nbsp;2019&nbsp;12:32:58&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=3108)&nbsp;using&nbsp;262144&nbsp;data&nbsp;buffer&nbsp;sizeDec&nbsp;15,&nbsp;2019&nbsp;12:32:58&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=3108)&nbsp;setting&nbsp;receive&nbsp;network&nbsp;buffer&nbsp;to&nbsp;1049600&nbsp;bytesDec&nbsp;15,&nbsp;2019&nbsp;12:32:58&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=3108)&nbsp;using&nbsp;30&nbsp;data&nbsp;buffersDec&nbsp;15,&nbsp;2019&nbsp;12:33:00&nbsp;PM&nbsp;-&nbsp;begin&nbsp;writingDec&nbsp;15,&nbsp;2019&nbsp;12:33:01&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=3108)&nbsp;start&nbsp;backupDec&nbsp;15,&nbsp;2019&nbsp;12:33:02&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=3108)&nbsp;backup&nbsp;child&nbsp;process&nbsp;is&nbsp;pid&nbsp;8364.8424Dec&nbsp;15,&nbsp;2019&nbsp;12:33:02&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=8364)&nbsp;startDec&nbsp;15,&nbsp;2019&nbsp;12:36:14&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbkar32&nbsp;(pid=6820)&nbsp;not&nbsp;using&nbsp;change&nbsp;journal&nbsp;data&nbsp;for&nbsp;&lt;C:\&gt;:&nbsp;not&nbsp;enabledDec&nbsp;15,&nbsp;2019&nbsp;10:10:19&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\Program&nbsp;Files&nbsp;(x86)\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Bin\service.dat&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:19:05&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\BASH\ShdSettg.dat&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:19:06&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\BASH\ShdSettg.dat.log&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:19:08&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\BASH\SPSettg.dat&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:19:10&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\BASH\SPSettg.dat.log&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:22:05&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\CmnClnt\ccGEvt\Global\LM2.dat&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:22:07&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\CmnClnt\ccGLog\ccGenericLog.dat&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:22:09&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\CmnClnt\ccJobMgr\JobMgr.dat&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:22:10&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\CmnClnt\ccJobMgr\JobMgr.dat.log&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:22:12&nbsp;PM&nbsp;-&nbsp;Warning&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;WRN&nbsp;-&nbsp;can't&nbsp;open&nbsp;file:&nbsp;C:\ProgramData\Symantec\Symantec&nbsp;Endpoint&nbsp;Protection\12.1.5337.5000.105\Data\CmnClnt\ccSetMgr\44bb4a26-6c2a-48a8-a256-8ae3ee56f112.dat&nbsp;(WIN32&nbsp;32:&nbsp;The&nbsp;process&nbsp;cannot&nbsp;access&nbsp;the&nbsp;file&nbsp;because&nbsp;it&nbsp;is&nbsp;being&nbsp;used&nbsp;by&nbsp;another&nbsp;process.&nbsp;)Dec&nbsp;15,&nbsp;2019&nbsp;10:22:12&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=3368)&nbsp;from&nbsp;client&nbsp;07r-malvern02:&nbsp;TRV&nbsp;-&nbsp;last&nbsp;message&nbsp;being&nbsp;suppressed&nbsp;after&nbsp;10&nbsp;occurrencesDec&nbsp;16,&nbsp;2019&nbsp;10:59:26&nbsp;AM&nbsp;-&nbsp;Critical&nbsp;bptm&nbsp;(pid=3108)&nbsp;image&nbsp;write&nbsp;failed:&nbsp;error&nbsp;2060046:&nbsp;plugin&nbsp;errorDec&nbsp;16,&nbsp;2019&nbsp;10:59:26&nbsp;AM&nbsp;-&nbsp;Critical&nbsp;bptm&nbsp;(pid=3108)&nbsp;sts_get_image_prop&nbsp;failed:&nbsp;error&nbsp;2060046:&nbsp;plugin&nbsp;errorDec&nbsp;16,&nbsp;2019&nbsp;10:59:32&nbsp;AM&nbsp;-&nbsp;Error&nbsp;bptm&nbsp;(pid=3108)&nbsp;cannot&nbsp;write&nbsp;image&nbsp;to&nbsp;disk,&nbsp;Invalid&nbsp;argumentDec&nbsp;16,&nbsp;2019&nbsp;10:59:33&nbsp;AM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=3108)&nbsp;EXITING&nbsp;with&nbsp;status&nbsp;84&nbsp;&lt;----------Dec&nbsp;16,&nbsp;2019&nbsp;11:00:03&nbsp;AM&nbsp;-&nbsp;end&nbsp;writing;&nbsp;write&nbsp;time:&nbsp;22:27:03Dec&nbsp;16,&nbsp;2019&nbsp;11:00:05&nbsp;AM&nbsp;-&nbsp;Info&nbsp;bpbkar32&nbsp;(pid=6820)&nbsp;done.&nbsp;status:&nbsp;84:&nbsp;media&nbsp;write&nbsp;errormedia&nbsp;write&nbsp;error&nbsp; (84)

sdo · Answer

Unfortunately status 84 is a fairly generic error status code. So we need a bit more detail please:

1) Can I ask what is the storage unit type for : w07pnbume07_MGW_FS_STU e.g. is it Adv.Disk or MSDP or Data Domain or something else?

2) What else can you tell us about this storage unit?

3) Is the backup policy using NetBackup Accelerator?

4) Is the backup client using Client Side Dedupe?

5) Are there any other regular backups to the same target storage unit, and do they always complete ok?

6) Have you tried pointing this failing backup client towards an alternate different target storage unit, and does that then regularly complete ok?

7) Is the failing backup client a WAN based client across a wide area network?

Thank you.

Forum Discussion

Backups are failing with error code 84 after writing 16gb of data in desktop

Related Content

file write failed(14)

Re: Netbackups failing with error code 24 on linux clients

The backup failed to back up the requested files

file write failed

File Write Failed (14)

Recent Discussions

NetBackup Virtual Appliance

Control number of VM backups running concurrently

restoring file from linux source to windows target; is possible?

MSDP 2 MSDP duplication

DR file package to NAS Share