I would appreciate any help / practical advice on the issue
Great handle BTW. The fact that a sector based backup utility (BESR) and a file/folder based backup program (BE 11.d) are both causing the system crashes part way through, suggests a software conflict somewhere. Possibly a Volume Shadow Copy service provider conflict. These tend to pop up within the first 5 percent of the imaging process, but can cause problems later in Backup Exec jobs I ran into a similar VSS conflict between the SymantecSnapService in BESR and BE 12.5. I have to stop that service, the "Backup Exec System Recovery Server" Service and several others in order for the Backup Exec 12.5 jobs to complete. I do this in a pre backup script and start the services in a post backup script.
When I used to use BE 11.d, I would stop the associated BE 11.d services with another script before imaging with BESR, and restart them after the snap was done. This includes the MSSQL instance that Backup Exec uses to store job information. Also, if you are running a defrag utility like Diskeeper, it might be helpful to stop that when backps are running on either BE or BESR. I have had my backups lock up because of this.
It might also be advisable to run chkdsk on the C:volume. I would try the
chkdsk /r command (which implies /f as well) to do the most thorough check. It will take a long time to complete, but at least you can rule out hard disk trouble afterward.
If you are in a pinch and need to get something for a distaster recovery image. the System Recovery Disk for version 8.5 does have the ability to cold image the system. The cold images will also be Restore Anyware compatible.
Best of Luck