Acronis error message:

Your Raid Setup should have a Diagnostic software. CHKDSK is not a good thing to run on most RAIDS.
If you know what RAID setup you have look for the proper software. Intel has there own as most do others do.

Thanks the disk check out ok, which leaves the Acronis issue unsolved any help would be appreciated.

I found this thread that may help you fix your problem with Acronis. Take a look. I hope it works for you.
http://www.wilderssecurity.com/archive/index.php/t-128080.html

  I too am having the same problem but I get the error when backing up SBS 2008 to external usb hard drives. I have 6 external hard drives (I swap them out) and each one is giving me the exact same error. Sector 63.

   I am running the absolute latest build. Hmm ... 6 hard drives all hace a problem with sector 63 and yours too? Acronis obviously has a problem. Their tech support, however, is like a screen door on a submarine. Not very effective wold e putting it mildly. Let me open up a case with Aconis and I'll keep you posted ...

  That was one of the less painful incidents with Acronis ...

http://download.acronis.com/sl/ncmsfadfpsjltepmpdbi/support/ticket/380380/SnapAPISetup.msi

It is an updated snap manager. The problem disappeared ...

I am also getting the same error on a customers server. just installed it a week ago.
But what i have noticed is that this happens even when you create a backup job and get it to dump the image onto the local hard drive. I will post any fixes i find usefull.

  It has been a while but there seems to be a fix. Acronis Tech Support is worthless and for the record stay away from ABR 10. It is a total piece of junk. Acronis has this nasty habit of putting out a new release and letting the public debug it. Total waste of time.

   In my case I am backing up to external USB hard drives and the read error is on the external usb hard drive. Even though that is the destination and it shouldn't be trying to back it up. I found a little utility called USBDLM. I mounted the external usb drive as a folder on drive C: and then backed up to that folder. The error went away. Don't know what you are backing up to but if it is external usb hard drives it will fix the error.