As noted above (and posted in other threads) I cannot create a working ISO using IDR as I have intergrated Win SBS 2k3 SP1 disks.
I'm attempting a manual restore:
I built a barebones Windows Server install. I then installed BE to a different location. I inventoried and cataloged my backup media.
I then try to do a restore of the C, D & E drives and the System State / Shadow Copy Components.
Regardless of whether this is attempted in 'normal' Windows, Safe Mode, DSRM and whether or not I restore to the original location or to an alternative location e.g. 2nd hard disk bengine.exe crashes when the job gets to 99% and is logged in the application log.
If I don't do anything after 15-20 minutes the job fails with a timeout error.
If I restart the bengine service the job just sits there. If I restart any other BE services the job fails anyway.
I've tried setting the recovery options to automatically restart the service and that hasn't worked.
I've tried recovering the information using NT backup and that can't restore the system state from my BE backups (but can restore NT backup's).
The job result is either Cancelled (by User Recovery), Failed or Recovered (in grey - but recovery fails)
To date all I've managed to do successfully is restore the system to a working state using NT Backup's ASR. But I am unable to recover anything in regards to system state, AD, security etc from the BE backups. Only file level restores work with BE.
Given that I can't recover the system using IDR or BE but I am able to get get a working system using Windows ASR, how do I go about getting my system recovered using the latest BE backups taken.
How can I verify that Backup Exec is in fact taking successful backups of the system state? I don't get any errors in the job log when backing up. Should NT Backup be able to access the system state information contained in a BE backup?
These are just a few of the Veritas KB articles I've refrenced: 283367, 236240, 243037