media write error (84) in VMWare Backup.
Metadata corruption!
You'll have to enable Accelerator forced rescan and perform a new full backup. I think that'll sort you out and if it does, you can then disable Accelerator forced rescan again.
(jandersen was onto this first)
There's a good recommendation in this TechNote:
The Symantec recommendation is to define at least two full schedules in the Accelerator policy. The first full schedule to define when the full backups run more frequently without the ' Accelerator forced rescan ' option enabled, and another full schedule to run less often (perhaps, once a month, every six months or once a year), with the ' Accelerator forced rescan ' option enabled. Having the forced rescan option enabled, ensures the Accelerator track log is refreshed to avoid any problems with future Accelerator backups.
Accelerator Forced Rescan option being set or used when it is not defined in the Accelerator policy full schedule
http://symantec.com/docs/TECH222420If you already have two full schedules set up, one with and one without, give the one WITH a manual run.
This is also said in the manual page:
Accelerator forced rescan option (schedule attribute)
http://symantec.com/docs/HOWTO106425
