[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 568
  • Last Modified:

Adding instance to sql cluster

We have a 2 node sql cluster and need to install another instance.  This instance will be installed on Node1 (both  nodes are 'active').  I have never done this before and was hoping someone could provide explicit instructions on how to install a new instance (named of course) and also how to go about applying the patch.
0
sqlnewbie08
Asked:
sqlnewbie08
5 Solutions
 
lcohanDatabase AnalystCommented:
0
 
sqlnewbie08Author Commented:
Yes... I am aware of this.  We are having all the necessary infrastructure in place before the install begins (separate virtual server, ip address, luns ...).  What i've never done is install a new instance on an exisiting clustered environment and then patch the new instance.  That is what I  need to know how to do.
0
 
lcohanDatabase AnalystCommented:
Ok, so if you have dedicated disks, IP, etc. please see articles below and do all these in a TEST environment first not directly to PRODUCTION environment. Also no matter what you do, because SQL is clueter aware and you have already a cluster built and running, perform ALL actions on ACTIVE node during downtime and from Cluster Manager exclusively including service packs/patches.

We did similar thing in dev/testing and did not worked verry well so we will be building brand new environment for SQL 2008 soon then migrate our prod DB's db's to that environment.

SQL Server 2005 Failover Clustering White Paper
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en


You cannot find SQL Server cluster resources in Failover Cluster Manager after you install a SQL Server 2005 failover cluster on a computer that is running Windows Server 2008
http://support.microsoft.com/kb/932897

Lessons Learned
http://technet.microsoft.com/en-ca/library/cc917532.aspx
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
lcohanDatabase AnalystCommented:
Oh yeah...I remember we had quite some fun with admin domain accounts running the patches that were "named" differently on active directory vs no active directory domain.
0
 
Eugene ZCommented:
if you have set 1st node and have set shared drives and got ip for new sql server:
check:

How to: Add or Remove Nodes in a SQL Server 2005 Failover Cluster (Setup)
http://msdn.microsoft.com/en-us/library/ms191545%28v=SQL.90%29.aspx


How to Cluster SQL Server 2005
http://www.sql-server-performance.com/articles/clustering/cluster_sql_server_2005_p1.aspx

0
 
sqlnewbie08Author Commented:
I've reviewed all these docs ...  none of the specifically let you know how to add an instance to an existing cluster.  
0
 
publicvoidCommented:
Make sure your new disk group is on Node1 and run the SQL installer from there (you will need to choose the appropriate path for your data files during the installation).

Here is a good article, complete with screen shots:

http://www.sql-server-performance.com/articles/clustering/cluster_sql_server_2005_p1.aspx

Note that for SQL Server 2005, the installer will install the binaries on all of the nodes in the cluster (unless you explicitly remove them, not recommended). Also be aware that even though you are installing a NEW SQL instance, your existing instances MAY be restarted during the installation. If you are running this on a production cluster, you may want to perform the installation when this is acceptable.

As for patching your clustered SQL instances, simply run the appropriate EXE on a cluster node (make sure you have the correct CPU architecture...x86 or x64). The installer will find all of your SQL instances and let you patch them all together (and will patch all of the nodes in the cluster). Of course, expect SQL service restarts while the patch is running and possible server reboots once patching is complete.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now