02-20-2008 02:46 AM
06-26-2008 10:27 PM
06-27-2008 01:52 AM
Unfortunately not
Are you using the Backup Exec default database or SQL ?
I concluded it might be because I was using SQL, and resorted to using NT Backup to backup the system state from the live system as a separate occassional backup.
Not ideal but decided we needed to do it anyway as Backup Exec couldn't restore to anything except identical hardware, and since one likely failure was the hardware that wasn't adequate.
William
06-27-2008 01:57 AM
Hey William
After the failed attempt at getting the services to start up, I restarted into normal mode to have a play around, make a duplicate of my backup set, etc.
Then logged back into Active Directory restore mode and VOILA, all the services were running. I did change them to Local Service during the previous attempt, and this time they worked well.
I only restored the system state, but not the actual C: data, however it didn't like it very much and caused a gazillion errors in event viewer. I have a feeling the C: on the set is corrupt (due to it backing up corrupt data to start with), so restoring from a few days prior. Will see how it goes and report back.
01-09-2009 07:54 AM
@higherorbit
Spot on - I don't quite see why a reboot is necessary after changing the BE service and SQL service logon accounts, but it worked here too (without rebooting into Normal Mode).
Well spotted and thanks very much!