I haven't had to do this in years, but you might think about putting the "POS" into its own group so a failure of that resource won't affect the resources. I think this is a best practice, or used to be.
On Wed, Jul 28, 2010 at 2:42 PM, Ziots, Edward <[email protected]> wrote: > Got another one of those screw ball requests, DBA put a non-cluster > aware service on one node of the SQL Server Cluster, and didn't tell us > about it, now he wants it to be a cluster aware service with its own > Group, drive, ect etc. > > I haven't had to do a Generic Service before and with everything going > on, my google-fu is failing me, and M$ doesn't have jack$hit that I can > find on a step by step procedure to install this POS as a generic > service. > > I was thinking from what I remember, I can either use the MSDTC group or > Quorum or SQL group on the cluster for the generic service, and I think > I need the drive letter the service is installed on, as a dependency > accordingly. OR do you need to install the application to the same > drive on both nodes and then make it a clustered service? > > Z > > Edward E. Ziots > CISSP, Network +, Security + > Network Engineer > Lifespan Organization > Email:[email protected] <email%[email protected]> > Cell:401-639-3505 > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
