remote media write error (84) writing to MSDP storage pool

[TimWillingham]

I have a remote media server writing to a MSDP pool at my office.  All drives backup successfully except the C: drive.  Here are the job details and bpbkar log:

02/21/2014 17:00:55 - Info bpbrm (pid=2304) altrcfs02 is the host to backup data from
02/21/2014 17:00:55 - Info bpbrm (pid=2304) reading file list from client
02/21/2014 17:00:55 - Info bpbrm (pid=2304) accelerator enabled
02/22/2014 21:10:04 - Info nbjm (pid=2809) starting backup job (jobid=1294378) for client altrcfs02, policy ar_trc_win1_nt, schedule cal-w
02/22/2014 21:10:04 - Info nbjm (pid=2809) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1294378, request id:{FD8E5D08-9C37-11E3-83E0-A11AB60767CD})
02/22/2014 21:10:04 - requesting resource altrcfs02_MSDP
02/22/2014 21:10:04 - requesting resource alxaptb07xs.NBU_CLIENT.MAXJOBS.altrcfs02
02/22/2014 21:10:04 - requesting resource alxaptb07xs.NBU_POLICY.MAXJOBS.ar_trc_win1_nt
02/22/2014 21:10:04 - granted resource  alxaptb07xs.NBU_CLIENT.MAXJOBS.altrcfs02
02/22/2014 21:10:04 - granted resource  alxaptb07xs.NBU_POLICY.MAXJOBS.ar_trc_win1_nt
02/22/2014 21:10:04 - granted resource  MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb...
02/22/2014 21:10:04 - granted resource  altrcfs02_MSDP
02/22/2014 21:10:04 - estimated 52505464 kbytes needed
02/22/2014 21:10:04 - Info nbjm (pid=2809) resumed backup (backupid=altrcfs02_1393023654) job for client altrcfs02, policy ar_trc_win1_nt, schedule cal-w on storage unit altrcfs02_MSDP
02/22/2014 21:10:05 - started process bpbrm (pid=6444)
02/22/2014 21:10:14 - connecting
02/22/2014 21:10:15 - Info bpbrm (pid=6444) starting bpbkar32 on client
02/22/2014 21:10:15 - Info bpbkar32 (pid=5972) Backup started
02/22/2014 21:10:15 - connected; connect time: 0:00:00
02/22/2014 21:10:16 - Info bptm (pid=8380) start
02/22/2014 21:10:16 - Info bptm (pid=8380) using 1048576 data buffer size
02/22/2014 21:10:16 - Info bptm (pid=8380) setting receive network buffer to 262144 bytes
02/22/2014 21:10:16 - Info bptm (pid=8380) using 24 data buffers
02/22/2014 21:10:17 - Info bptm (pid=8380) start backup
02/22/2014 21:10:19 - begin writing
02/22/2014 21:10:29 - Info bpbkar32 (pid=5972) change journal NOT enabled for <C:\>
02/22/2014 21:10:38 - Critical bptm (pid=8380) A portion of data to be included from a previous backup (backupid = altrcfs02_1392774401, offset = 3036672, length = 18432) has incorrect checksum (calculated checksum from backup image f16c47c3090880c80f02ed100db36cdcd5319607, expected checksum faa2cbed0de7ca747812bfdbdf58eb113b392ab9)
02/22/2014 21:10:38 - Critical bptm (pid=8380) image write failed: error -1: plugin error
02/22/2014 21:10:49 - Error bptm (pid=8380) cannot write image to disk, Invalid argument
02/22/2014 21:10:49 - Info bptm (pid=8380) EXITING with status 84 <----------
02/22/2014 21:10:49 - Info bpbkar32 (pid=5972) accelerator sent 24896512 bytes out of 3059850240 bytes to server, optimization 99.2%
02/22/2014 21:10:49 - Info bpbkar32 (pid=5972) bpbkar waited 1 times for empty buffer, delayed 25 times.
02/22/2014 21:10:52 - Info altrcfs02 (pid=8380) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 400383 KB, CR sent: 390 KB, CR sent over FC: 0 KB, dedup: 99.9%
02/22/2014 21:10:52 - Info bpbkar32 (pid=5972) done. status: 84: media write error
02/22/2014 21:10:52 - end writing; write time: 0:00:33
02/24/2014 09:05:15 - job 1294378 was restarted as job 1296592
media write error  (84)
 

[TimWillingham]

Here is another bpbkar log for same timeframe.

[SymTerry]

Hello What version of NetBackup is this? We have patched issues like this with newer versions of NetBackup. If your on the most current, please let me know and we can get a case set up as this will need to be looked at.

EDIT:

I did find a workaround that you might be able to try from a internal source. 

Workaround:

turn off accelerator on policy

run policy

turn on accelerator on policy

run policy

[TimWillingham]

Running 7.5.0.6

Turned off Accelerator, but still got an 84.

Killed some rogue bpbrm processes, but still fails at exactly the same point each time.

[TimWillingham · Accepted solution]

Created a new test policy and it is running.  I kept trying to rerun the failed jobs and it just wasn't working.

[Scott_Austin]

I would recommend a case be logged and a CRcheck be done against that mspd.

[Marianne]

There is obviously an issue with this image:

Critical bptm (pid=8380) A portion of data to be included from a previous backup (backupid = altrcfs02_1392774401, offset = 3036672, length = 18432) has incorrect checksum (calculated checksum from backup image f16c47c3090880c80f02ed100db36cdcd5319607, expected checksum faa2cbed0de7ca747812bfdbdf58eb113b392ab9)

I would say expiration of this image-id followed by new full backup would also fix the issue.

Or log a call with Symantec to investigate the checksum issue.