RobertPBham
15 years agoLevel 3
Windows Internal Database backup (SQL)
Hi folks,
I'm currently testing our disaster recovery and everything is working well. However, I've just restored a server that hosts among other things WSUS and our antivirus software. Both of these use the Windows Internal Database (SQL mdf files). When I restored the server the Windows Internal Database services wouldn't start and I found this to be because the mdf files were missing. After a quick check, I found that these are excluded due to the Active File Exclusions mechanism that is implemented in Backup Exec.
Now, I know that Backup Exec do a SQL Server agent, but this seems like a rather costly solution as many applications use the Windows Internal Database for storing data and as the Backup Exec SQL agent is licensed per machine, it is by no way cheap to implement. I also believe that Backup Exec uses SQL databases, so I can only assume that my backup of our backup server is technically not a complete backup as well? I can understand the SQL agent being used with SQL Server Enterprise applications, but I don't understand why Backup Exec cannot backup the Windows Internal Database's.
So I guess my question is, does everyone use the Backup Exec SQL agent to do this or is there another way? I do know that I could script a backup via the SQL Agent, but this is quite admin intensive and defeats the object of using Backup Exec to backup servers if it 'misses' bits.
Thanks for all your help
Rob
- Hi Robert,
I think they put that alert in the admin guide.
Hope you come right, and if you do, you can close this off as being solved.
Cheers!