I recently encountered a customer environment in which they had failover cluster where one of the virtual nodes had more than one 'Client Access Name' (i.e. more than one IP address and DNS name for the single virtual node).

Long story short we had to modify our software to deal with this situation, but we want to recreate the situation in house to test it before releasing.

I have been unable to locate any information about how or why you would end up with a virtual node that has more than one access name.

Does anyone know how I can set up a Windows failover cluster where a virtual node has more than one access name/IP?

  • You may want to clarify the term "virtual node", that's not really a standard failover clustering term. Normally CAPs are associated with a service or are for general cluster administration, are these CAPs associated with SQL or with some other service or do you mean multiple CAPs for the cluster itself? One reason to have multiple CAPs for say a clustered file server is if one is performing some sort of migration, combining previously multiple servers into one. – phoebus Oct 26 '13 at 23:33

As noted in my comment on the question, it depends somewhat on what you mean by "virtual node" and whether the CAPs are for administration of the cluster itself or for some clustered service such as file sharing or SQL Server.

One reason to have multiple CAPs for a service is if it is being used to consolidate what were previously multiple servers, e.g. combining multiple file servers into a new single clustered file server. Instructions on setting up multiple CAPs for a clustered file server are available on the Windows Server Core Team blog.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.