I'm running Backup Exec 2012 fully patched, primary backup of VM Ware virtual machines.
Last week we suddenly see this error ind the EventViewer on the backup server and backup started to fail and some jobs startet to take much longer time than normal. I have triede to find a solution, but no luck.
The error from the eventviewer
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume .
We have run chkdsk [driveletter] /f on the backup server, but no error reported.
As you can see there is no indication in the error, that shows us which drive its regarding.
Hope someone can ghelp me.
Can you please confirm the event id getting logged..
If it is 55 then refer below article.
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume B:.
A hotfix is available from Microsoft to resolve the issue.
Event ID 55 may be logged in the System log when you create many files on an NTFS partition on a Windows Server 2003-based or Windows XP-based computer
Does the event 55 generate each time when the backup fails ? (Though its a bit uncommon that the event does not specify which volume). Are there any corresponding errors under the Application events when this system event occurs ?
What is the Backup Exec error which you receive from the job log ?
Lastly, are you backing up to disk or tape ? If disk, has chkdsk been run on this storage as well ?
Yes each time, but there is no error in the job. No corresponding errors under application events.
The backup is to a deduplication store and chkdks have been run on this drive.
I have installed this hotfix http://support.microsoft.com/kb/2754784 now i'm trying to run backuop again.
I will report back with the result.
If this only affactes Windows 2012 virtual servers, as we mount the vmdk files in order to catalog the file system GRT, it's possible that this error is being generated because the operating system of the media server briefly sees the disk system that is held inside Windows 2012 as if it is a local disk.
If it only does the error for some but not all Windows 2012 VM's then try looking at differences in the configurations of the vmdk files and the windows volumes held within the vmdk files between VMs that appear to generate the error and those that don't, it's possible you may find somethingn that is not supported yet.
BTW I'd ecnorarge formal support cases to be logged for this issue just for us to confirm what is happening as my comments above are a theory / educated guess.