If the service doesn't start on one server, what makes you think it would start on the other server?
If the service wouldn't start on the original server, it is probably because either the data is whacked, or there is some external resource that isn't available (user ID locked, database server not available, etc). When the service tries to start on the failover node, it is going to see the same problems. -----Original Message----- From: Joseph L. Casale [mailto:[email protected]] Sent: Thursday, December 06, 2012 10:29 AM To: NT System Admin Issues Subject: RE: File Services Clustering in Server 2012 > Yep setting up a cluster just to protect against a service dying is overkill. I think that statement might be a bit to general. What if that service doesn't simply "restart" and 2500 people have their work impacted for 4 hours while its resolved? 2500*$30*4=$300,000.00 as an example... Does that "application" cluster investment still sound unrealistic? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
