In typical Backup Exec form, everything was working fine until this error starting popping on one of my backup jobs. The backup job is backing up a domain controller where the Backup Exec server itself resides.
Completed status: FailedFinal error: 0xe000943f - Database s failed to freeze for backup. This can be caused if the database is in a state that does not support backup; such as offline, standby, or recovering. Final error category: Other Errors
The database in question is the actual Backup Exec SQL database. All articles on the net and in the community are mostly pointing to a credentials issue, but the credentials for the database test successfully. Again, this was working previously. Further digging on the net pointed towards the SQL VSS Writer or service being missing--lo and behold--they are both missing.
1. How do I get the service and writer back? I ran a repair on BE21.2 hoping it would fix the issue, but it didn;'t since this is a SQL issue.
2. Should I run a repair on the database using the BEUtility?
3. I unchecked the BE SQL database from the backup to see if it fixes the problem, but that seems like a workaround rather than a real solution.
4. Should I just upgrade to BE22? A new upgraded database will be installed if I'm correct (SQL2017). Will this fix the problem?
I unchecked the Backup Exec SQL database from the backup job and the job is now working without failing. Is there a difference between backup up the SQL database and just backing up the database files themselves?
I will see what Microsoft says about this and report back what I find...........
You could certainly try a repair of the database as per this TN:
https://www.veritas.com/support/en_US/article.100020074 - How to run an extensive database repair and cleanup of the Backup Exec database when it is found to be inconsistent
just ensure you take a backup (or dump) of it first. It may help bearing in mind this used to work but then started failing.
I'm guessing you've rebooted the machine since this problem as that often fixes VSS issues if that is the cause. Might also be worth checking the event logs for any error messages around the time of the backup failure.