Unsolved
This post is more than 5 years old
4 Posts
0
450
September 17th, 2009 12:00
AutoStart Services on Windows Server
Hi,
I've taken on administration of a number of AutoStart clusters and would like to know do the "AutoStart Community" consider is best practice to set the recovery of the AutoStart windows services to "restart the service" on the first, second and subsequent failures and are there any known "pros and cons"?
I've a number of servers on which the services stop occasionaly - not a major thing as it only happens once every few weeks, maybe even months but if the Backbone and/or Agent service stops running on a node in the domain, AutoStart marks it as unavailable and we loose HA - which could be a major thing.
Many thanks.
I've taken on administration of a number of AutoStart clusters and would like to know do the "AutoStart Community" consider is best practice to set the recovery of the AutoStart windows services to "restart the service" on the first, second and subsequent failures and are there any known "pros and cons"?
I've a number of servers on which the services stop occasionaly - not a major thing as it only happens once every few weeks, maybe even months but if the Backbone and/or Agent service stops running on a node in the domain, AutoStart marks it as unavailable and we loose HA - which could be a major thing.
Many thanks.
No Events found!
yito1
262 Posts
1
September 17th, 2009 19:00
The Agent service and the BackBone service fail never.
If service fails in your environment, it might have the issue of environmental dependence.
We sell it in Japan, but do not hear such a report! !
It is default in the recovery tab of service.
They are all Take No Action.