Considering the platform as outlined in the title, I have an instance of SQL for backup exec and a secondary instance for my database. Why does my SQL database become suspect after the server is rebooted?
The restore of the database runs successfully, the data is all there and transactions can be made. However, if the server is rebooted the database becomes suspect.
If I stop the services for backup exec and leave my other instance running - the database is no longer suspect and can be used. After checking the SQL logs it confirms that backup exec is using my associated MDF file.
Could it be the order in which the SQL instance's services are starting? Has the 3rd party who installed the system incorrectly configured backup exec? Have they forgotten to install the SQL agent for backup exec, even though they have told me they have? Has a backup exec task not been put in place?