<div>
The SQL install wizard didn't seem to think this was available. This LUN was orginally used as the Quorum disk and then moved it to a different LUN. I ended up removing the volumes and setup the cluster again. When I moved the Quorum this time I took it offline and then moved it. When that completed I had all my available LUNS back. Strange. Needless to the say the actual SQL 2008 R2 clustering piece was a piece of cake. I had just struggled with some quirky issue in setting up the Windows cluster. All is happy now. Thanks. 
</div>


<div>
<div class="content wysiwyg-content">
I have started to prepare a Windows 2008R2 cluster for use with SQL 2008 R2 clustering. I have 5 shared LUNS. I created the cluster and added all the LUNS to storage. I then installed MSDTC on one of the LUN and moved the quorum disk to another LUN. One thing I have noticed now is that 2 of my LUNS are in the available storage group while one of the LUNS is in a goup called 'Cluster Group'. I want to be able to use the &nbsp;3 remaining LUNS for the SQL install. 2 are for the user databases (logs and db's) and the other one is for the system databases. I am new to shared clustering. Why is this LUN in the cluster group and why aren't the others there? 
</div>
</div>


I have started to prepare a Windows 2008R2 cluster for use with SQL 2008 R2 clustering. I have 5 shared LUNS. I created the cluster and added all the LUNS to storage. I then installed MSDTC on one of the LUN and moved the quorum disk to another LUN. One thing I have noticed now is that 2 of my LUNS are in the available storage group while one of the LUNS is in a goup called 'Cluster Group'. I want to be able to use the  3 remaining LUNS for the SQL install. 2 are for the user databases (logs and db's) and the other one is for the system databases. I am new to shared clustering. Why is this LUN in the cluster group and why aren't the others there? 

The SQL install wizard didn&#39;t seem to think this was available. This LUN was orginally used as the Quorum disk and then moved it to a different LUN. I ended up removing the volumes and setup the cluster again. When I moved the Quorum this time I took it offline and then moved it. When that completed I had all my available LUNS back. Strange. Needless to the say the actual SQL 2008 R2 clustering piece was a piece of cake. I had just struggled with some quirky issue in setting up the Windows cluster. All is happy now. Thanks. 

Cluster WIndows 2008 R2 for SQL 2008R2

I have started to prepare a Windows 2008R2 cluster for use with SQL 2008 R2 clustering. I have 5 shared LUNS. I created the cluster and added all the LUNS to storage. I then installed MSDTC on one of the LUN and moved the quorum disk to another LUN. One thing I have noticed now is that 2 of my LUNS are in the available storage group while one of the LUNS is in a goup called &#39;Cluster Group&#39;. I want to be able to use the  3 remaining LUNS for the SQL install. 2 are for the user databases (logs and db&#39;s) and the other one is for the system databases. I am new to shared clustering. Why is this LUN in the cluster group and why aren&#39;t the others there? 

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.