(84) media write error

[traghav86]

Hi Guys

Please assist with below error getting while VMDK backups running to Netbackup appliance using san transport.

06/15/2016 01:35:52 - Critical bptm (pid=240507) A portion of data to be included from a previous backup (backupid = NRCASUS101_1465428251, offset = 52670823424, length = 131072) has incorrect checksum (calculated checksum from backup image 17d03252b1217391333fb6ebd380aee777cb01ac, expected checksum 74e0103d34d34b6050a31b49992519d83130ac08)
06/15/2016 01:35:52 - Critical bptm (pid=240507) image write failed: error -1: plugin error
06/15/2016 01:35:56 - Error bptm (pid=240507) cannot write image to disk, Invalid argument
06/15/2016 01:35:56 - Info bptm (pid=240507) EXITING with status 84 <----------
06/15/2016 01:35:56 - Error bpbrm (pid=240487) from client NRCASUS101: ERR - bpbkar exiting because backup is aborting
06/15/2016 01:35:56 - Critical bpbrm (pid=240487) from client NRCASUS101: FTL - cleanup() failed, status 40

[Marianne]

Problem with dedupe storage on the media server: " A portion of data to be included from a previous backup (backupid = NRCASUS101_1465428251, offset = 52670823424, length = 131072) has incorrect checksum (calculated checksum from backup image ...) " Try to verify this backup image. NRCASUS101_1465428251 Ensure bptm and bpdm log folders exist. If verify fails, you need to log a Support call with storage vendor. If this is NBU Appliance or MSDP, you will need level 5 logs when logging the call.

[traghav86]

Hi Marianne

verify completed. do you think next backup will run without issues ?

i thought this was due to IO error on media server.

[Marianne]

I cannot say... that checksum error does not look good...

[hrhrhrhrhr]

We had the same error and ended up with a fresh MSDP-Pool. But we had failing backups not only on VMware.

It could be this: https://www.veritas.com/support/en_US/article.000025261

[Marc_LHeureux]

Certain versions of VMWare actually report bad CBT information to VADP causing backups to appear successful when they are in fact not usable for restore.  When I read your message and the link provided by hrhrhrhrhrhr, it sounds like you could be impacted - without knowing your VMWare versions I can't say for sure.

See this: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21368...

I recommend making sure your VMWare environment is up to date with the latest updates and patches; clearing out a CBT logs on the VMs; and running fresh full backups on all clients without Accelerator.