10-06-2016 08:04 AM
Hello All,
In our environment we have many Linux master servers. The VMbackups are getting failed with EC 84 for few vm clients daily ( not the same list daily but different list). It happens only when the VM is getting migrated from one ESX to another ESX by DRS ( Distrubuted Resource Scheduler. Also the failed backups are getting successful when it is migrated from one ESX to another ESX again.
Any thought on this?
Master servers : NetBackup-RedHat2.6.18 7.7.2
VMbackup hosts : NetBackup-RedHat2.6.18 7.7.2
From Activity monitor please refer the below error
10/02/2016 23:14:29 - Critical bptm (pid=xxxxx) A portion of data to be included from a previous backup (backupid = XXXXXXXXXXX_123456789, offset = xxxxxxx, length = xxxxx) has incorrect checksum (calculated checksum from backup image xxxxxxxxxxxxxxxxxxxxxxx, expected checksum xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
10/02/2016 23:14:29 - Critical bptm (pid=xxxxx) image write failed: error -1: plugin error
10/02/2016 23:14:38 - Error bptm (pid=xxxxx) cannot write image to disk, Invalid argument
10/02/2016 23:14:38 - Info bptm (pid=xxxxx) EXITING with status 84 <----------
10/02/2016 23:14:38 - Error bpbrm (pid=xxxxx) from client xxxxxxxxxxxxxxx: ERR - bpbkar exiting because backup is aborting
10/02/2016 23:14:38 - Critical bpbrm (pid=xxxxx) from client xxxxxxxxxx: FTL - cleanup() failed, status 40
10/02/2016 23:14:40 - Critical bpbrm (pid=xxxxx) unexpected termination of client xxxxxxxxxxx
Thanks
10-06-2016 10:31 AM
Hi,
Can you check is there any accumulated files of older dates under this path "usr/openv/netbackup/onlineutil/fi_cntl" in your backup off host server.
If you see older dates then move them to different location and try running the backups.
Please post us with the job details, i suppose it is failing after wirting some data or while updating the catalog in bpdbm.
10-06-2016 02:33 PM
Does this policy enabled with accelerated backups?
what is the transport method being used for backups..
https://www.veritas.com/support/en_US/article.TECH222588
check this tech note... the currnet version that you are in is not listed in this tech note however it is worth checking..