MSSQL2K Install in Cluster

  • cblay

    Valued Member

    Points: 63

    During setup Virtual Server is selected by default. The statement above the radio buttons says "Or, enter the name of a new or existing Virtual SQL Server to manage."

    I do not want to create a new virtual server for SQL Server, I want to install it to use an existing Virtual Server name. According to the statement above, this can be done but it won't let me. I get an error stating "Another Virtual Server of the same name exists on the network." when I enter the name of an existing Virtual Server.

    I got it to work using an existing Virtual Server name by installing under a new Virtual Server name, then juggling the resources in Cluster Admin. and hacking the registries on both nodes in my cluster. I'm sure this is not the preferred method. I would like to set it up correctly from the beginning. Any help is appreciated.

    Thanks,

    Chuck Blaylock

  • Brian Knight

    One Orange Chip

    Points: 27249

    By the following statement, are you referring to your existing NT virtual name or have you already installed SQL Server once before on this cluster?

    quote:


    I do not want to create a new virtual server for SQL Server, I want to install it to use an existing Virtual Server name.


    Brian Knight

    bknight@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/bknight

  • cblay

    Valued Member

    Points: 63

    I have never installed SQL Server on this cluster. It is a 2 node cluster and I have 1 Virtual Server for each physical node. 1 node owns my file resources and the other should own the database resources. I want to access my file server by Vname1 and SQL Server by Vname2 (both of which are already present). How can I tell MSCS to install the SQL Server resources on Vname2?

  • Brian Knight

    One Orange Chip

    Points: 27249

    You may want to check out this article:

    http://www.sqlservercentral.com/columnists/bknight/stepbystepclustering.asp

    to see a step by step guide. Let me know if you have any questions here after that.

    Brian Knight

    bknight@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/bknight

  • cblay

    Valued Member

    Points: 63

    Brian,

    I have read the article and understand it completely. Let me explain again what I'm trying to achieve.

    I want to access my file share server by VNAME1, and my SQL Server by VNAME2. I already have these Virtual Servers created. When I install SQL Server, I don't want to create VNAME3. I want it (SQL Server) to use VNAME2.

    I guess another valid question would be...If I set up my first node (VNAME1) then install SQL Server (VNAME2) then when I add my 2nd node, do I have to manually install the SQL Client utilities on the physical node (VNAME3)?

    Sorry for all the confusion, but I'm trying to layout an install procedure for our product that all of my department's installation engineers can use to ensure standardization.

    Thanks for your patience,

    Chuck Blaylock

  • Brian Knight

    One Orange Chip

    Points: 27249

    No problems! SQL Server has to be a unique virtual name so if you have VNAME4, your SQL Server instance will be VNAME5. ALso, once you install SQL Server on the cluster, it will copy the binaries (including the utilities) to both nodes. If this is A/A, then your next install will also have to be a unique VNAME.

    Hopefully this is what you're asking for?

    Brian Knight

    bknight@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/bknight

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply