I have several Windows Services that use a large amount of Windows memory, and must be up 24x7. I was hoping to use clustering in some way to ensure availability and possibly pool memory resources.
These Windows services stores info in RAM. I was researching the possibility of using clustering to ensure the availability of these actual Windows services, but have not been able to find anythign substantial indicating this is even possible.
This service is part of the back-end to a web based application, cannot run on the IIS server itself, but must have high availability as it can be a single point of failure for the application. The front-end IIS servers are using NLB, but I am trying to come up with a solution that will allow for a certain level of redundancy for this Service as well.
Is 2003 cluster services a viable option here? If so, what kind of config should I look into? If not, does anyone have any other suggestions?
These Windows services stores info in RAM. I was researching the possibility of using clustering to ensure the availability of these actual Windows services, but have not been able to find anythign substantial indicating this is even possible.
This service is part of the back-end to a web based application, cannot run on the IIS server itself, but must have high availability as it can be a single point of failure for the application. The front-end IIS servers are using NLB, but I am trying to come up with a solution that will allow for a certain level of redundancy for this Service as well.
Is 2003 cluster services a viable option here? If so, what kind of config should I look into? If not, does anyone have any other suggestions?