June 26, 2008 at 1:28 pm
I would like to install a new SQL Server 2005 named instance on a server active/passive cluster, where an SQL Server 2005 default instance exists.
Would anyone like to provide detail information on how to do it, or what special attention I should pay to?
Any input will be greatly appreciated.
June 26, 2008 at 1:45 pm
Is the second instance going to fail over at the same time as the default instance?
or are you looking to set them up "opposite" each other in a pseudo "active/active" scenario (so node1 is serving up instance1 and node 2 is serving instance 2)?
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
June 26, 2008 at 4:21 pm
To install a new clustered instance, set up a new Cluster Group, with a volume(s) allocated (and properly formatted for SQL, of course), dont add anything else to the Cluster Group - the SQL install does everything else for you. Then, run the SQL install (this isfrom a doc I prepared for another DBA, so, if it's too much detail, sorry) :
(a)Installing Prerequisites: SQL Prerequisites are installed – NOTE these components are only installed on the current node at this time; they are installed on the other node(s) later in the process. The process to install the prerequisites on the other nodes is transparent to the installer.
In case of error installing the prerequisites, try rebooting all nodes in the cluster and restarting the install. If the error(s) persists, troubleshoot the error(s) to successfully complete this phase.
(b)System Configuration Check: The install performs a System Configuration Check. All items should have green checks. Any yellow warning icons should be investigated and resolved if possible, these can sometimes be ignored. Any red error icons must be resolved before proceeding.
(c)Enter registration info.
(d)Components To Install: Select the SQL components to install The ‘Create SQL Failover Cluster’ option is required.
(e)Instance Name: Select a Named instance and define the Instance Name – this is the second part of ‘ServerName\InstanceName’.
(f)Virtual Server Name: Define the Virtual Server Name – this is the first part of ‘ServerName\InstanceName’. This *should* be the same as the Cluster Group name (but doesn't have to be).
(g)Virtual Server Configuration: Define the IP address for the Virtual Server. This should be the same as the IP address for the Cluster Group. The IP address must belong to the same subnet as the IP addresses used by all of the nodes. Don’t forget to click ‘ADD’ …
(h)Cluster Group Selection: Select the predefined Cluster Group to install SQL to.
(i)Cluster Node Configuration: Add all available Nodes to the Selected Nodes box. The current Node is in the Required Node field, and cannot be removed.
(j)Remote Account Information: Enter an AD account that has admin rights on all the Cluster Nodes participating in the Virtual Server.
(k)Service Account: Enter the details for the Service Account to be used to run the SQL Components Services.
(l)Domain Groups For Clustered Services: Select pre-existing global domain groups that are used to contain the startup account for each clustered service. You can choose to add all three services to the same global domain group, or to create separate global domain groups, one for each service.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply