Backup Exec 12.5 - problem with backup of System State

Nobody any clue?

Please check if these files are present in the specified locations. Most likely, registry has a reference to these files, which are missing from the disk, and hence not found in the snapshot. Make sure, the files are there, if present in alternate location, we might have to copy them there or look for their referencing entries in registry and delete them. But, there are some .sys files showing here, which could be kernel drivers, hence registry fix would not be recommended. You will need to identify these files and repair the softwares associated with these files.

Please mark it a solution, if this is useful.
Thanks

Hi there,

After you downloaded and installed the updates from LiveUpdate, did you push the RAWS agent out to that server in question again? These updates also have updates for RAWS, so it's in your best interest to do that if you haven't already.

Laters!

I checked for those 5 files which were marked in the exceptions of the job log and found out there just not there.

for example
VSS Snapshot warning. File c:\program files (x86)\microsoft sql server\mssql.1\mssql\binn\sqlservr.exe
I found this one at c:\program files (x86)\microsoft sql server\mssql.2\mssql\binn\sqlservr.exe

The other 4 files are just not present

What is the way to go to solve this problem in a decent matter ?
I can try to copy them from another Windows2008 Server installation, and I can copy the sqlservr.exe file to a correct location, but will that be enough for the snapshot of the system state and does that count as a decent solution?

Thanks for any further help.

Yes, just having the files there would be enough. It is basically an incomplete installation of some applications, which has the left over entries in the registry and hence causing the issue. Placing those dummy files there should make your backups successful, and as long as you cannot identify these files as some critical files, it should not be a problem. Else, if you can identify those applications, repairing them could be another option for you. If you are looking at a decent solution, i would suggest you consulting Microsoft or the corresponding vendors who own these files to find out exactly what made this incomplete install of these applications. As far as Backup Exec is concerned, it is VSS who is looking for these files, so not much can be changed within Backup Exec to get it working. So, this solution should be good for you to place the files there in that location.

Please mark it a solution, if this is useful.
Thanks

So I placed the missing files which were marked in the 'exceptions' in the correct folders, and run our backup job again including the system state.
No more exception warnings now...woohoow... but still not a succesfull backup :-(

He's down to still the same Error Code about the consistency check of the AD.

Job Completion Status
Error code : E000035A
Completed status: Failed
Final error: 0xe000035a - The consistency check of the snapshot for the Microsoft Active Directory, ADAM or AD LDS database has failed.
You should check for possible data corruption in the Active Directory, ADAM or AD LDS Server that is online.

As stated above :
- We already did a command line consistency check of our AD using tools like dsbutil etc... no failures, no problems. (It's a brand new AD installation after all)
- If we exclude the system state from the backup job, the backup job is succesfull. But ofcourse we want to backup the system state too.

Who can provide any more help ?
Many thanks in advance.

Did you push the RAWS agent out to that server again? Alternatively uninstall it, and then reinstall it...may be some sort of corruption there.

By RAWS you mean the Remote Agent Utility ?
Not sure what it does on the system, but is installed and is running 'idle'.

The publish check box is marked with our server added.

Also not sure if that is related with our problem of the consistency check of the AD ?
Can you provide more info please ?

Hi lavh,

You need RAWS (Remote Agent for Windows Servers) installed on any server that needs to be backed up.
It shouldn't be "idle"...it should be in a Running state. If it's idle, stopped or disabled, BE wouldn't be able to connect to the agent to perform the backups.
When you update your media server, it's always best to push your agent out again as it normally containts some critical updates.

Laters!

Hi Craig,

Thanks for your input.

But, I'm afraid I just want to backup one local server with backup-exec 12.5., so not on different servers and not remotely.
So, if we talk about just one local server, does RAWS installation matter then and is that related to the consistency check error ?

Yep, RAWS needs to be on any server being backed up, including the media server. It will also run on the Local System account, and no other.