We have an installation of a BI application which requires a database to be up an running.
The critical BI service requires the database to be up and running to validate logins.
The database is ‘taken down’ every night for a ‘cold’ backup and is then made available the next morning.
The critical service will fail to start if the database is not available, which then requires a manual restart of the service.
Even if the service is setup to restart automatically after a number of failures, it needs to be started manually if the database isn’t available after the first restart.
Is there any way that we can keep the service try to startup until it does connect to the database?
Our current solution is to have a NT schedule restart the service one hour after the agreed time of the database being up and running again.
Any other suggestions gratefully accepted.
Regards
Zinger
-
Testing for running service
- This topic has 7 replies, 3 voices, and was last updated 18 years, 4 months ago.
AuthorViewing 1 reply threadAuthorViewing 1 reply thread