February 28, 2007 at 8:21 am
Does anyone have reference of detail procedures of installing SQL cluster?
Many thanks in advance.
February 28, 2007 at 9:59 am
http://www.sqlservercentral.com/columnists/bknight/stepbystepclustering.asp
If you search SSC for articles on Clustering, you'll find more.
March 1, 2007 at 3:38 am
This works for us. The process starts with building a virtual domain and installing SQL on virtual servers. If you already have a Windows cluster, start at item 4). We do not include Reporting Services in our standard SQL Server 2005 build.
These notes should be considered as general guidance only, and not as a set of instructions for a clustered install.
It is recommended that the reasons for creating a cluster are fully understood and documented, as a SQL Server cluster may not be the most appropriate method of achieving the SLA objectives. It is also recommended to plan cluster naming standards and IP address use, as the process below will create a number of cluster resources and clusters. The names for all of these should be unique within the enterprise, and it may help troubleshooting if a contiguous range of IP addresses are reserved for all the software clusters on a given physical cluster.
All processes should be performed on the primary (active) node in the cluster unless specified otherwise.
1) Review requirements for installing SQL Server 2005 in a clustered environment.
See: http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
2) (site-specific - removed for this post)
3) Create the Windows 2003 Cluster.
See: http://www.microsoft.com/technet/prodtechnol/virtualserver/deploy/cvs2005.mspx.
Notes:
a) The above link include details on how to set up a cluster in a virtual environment. If physical servers are being used, the details relating to virtual servers can be ignored.
b) If any firewall exists between the SQL Server machine and the Domain Controller, ports will need to be opened to allow authentication and other communication to take place.
4) Setup the MSDTC Cluster resources.
See: http://www.microsoft.com/technet/prodtechnol/biztalk/2006/library/bts06clustering/b361f721-60db-485e-9ce3-48a6871ebd79.mspx?mfr=true.
Note: Where the resource names given in this link refer to BizTalk, use MSDTC instead.
5) Create the MSDTC Cluster.
See: http://www.microsoft.com/technet/prodtechnol/biztalk/2006/library/bts06clustering/55b0c81f-44a5-4069-b065-57df1cce19ac.mspx?mfr=true.
Note: Where the resource names given in this link refer to BizTalk, use MSDTC instead.
6) Create the SQL Server 2005 Cluster.
See: http://msdn2.microsoft.com/en-us/library/ms179530.aspx.
Notes:
a) This process will install clustered SQL Server 2005 resources on all nodes in the cluster, but will only install non-clustered resources on the primary node in the cluster.
b) The INSTALL account used for this stage must have domain Account Operator rights, otherwise the SQL Server 2005 install will be blocked.
7) Install non-clustered components on the passive node.
The list of components to be installed should specify only Notification Services, Integration Services, and Workstation components, as these were not installed when the SQL Server 2005 cluster was created.
8) Complete remaining SQL Server 2005 installation processes.
Complete any site-specific customisation of SQL Server 2005. (For us this includes SP1 and HF 2153) This must be done for both the primary and passive cluster nodes.
9) Create the Integration Services Cluster.
See: http://msdn2.microsoft.com/en-gb/library/ms345193.aspx.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply