Can someone help a newb? Disclaimer: I'm actually a storage adminstrator but please don't let that fool you. I think I'm an OK guy :)
We're planning a new failover SQL cluster which will host multiple SQL 2008R2 installations. I thought I might come here for an opinion on part of my storage design. Specifically, I need some help with deciding how to present the LUNs to the clustered
OS.
Here's what I've come up with thus far:
C:\ {{OS}} (local disk)
D:\ <--10GB FC-attached LUN
---\SQL-Installation-00
---\DB00
---\LOGS00
---\TEMPDB00
---\Volume-Mount-Points
---\Sharepoint
---\DB00 <--500GB FC-attached LUN
---\Logs00 <--125GB FC-attached LUN
---\TempDB00 <--125GB FC-attached LUN
---\Lync
---\DB00 <--500GB FC-attached LUN
---\Logs00 <--125GB FC-attached LUN
---\TempDB00 <--125GB FC-attached LUN
E:\ <--10GB FC-attached LUN
---\SQL-Installation-01
---\DB00
---\LOGS00
---\TEMPDB00
---\Volume-Mount-Points
---\SCCM
---\DB00 <--500GB FC-attached LUN
---\Logs00 <--125GB FC-attached LUN
---\TempDB00 <--125GB FC-attached LUN
F:\ <--10GB FC-attached LUN
---\SQL-Installation-02
---\DB00
---\LOGS00
---\TEMPDB00
--\Volume-Mount-Points
---\Solarwinds
---\DB00 <--500GB FC-attached LUN
---\Logs00 <--125GB FC-attached LUN
---\TempDB00 <--125GB FC-attached LUN
In this situation, SQL-INSTALLATION-00 would run our Sharepoint and Lync databases; SQL-INSTALLATION-01 is for SCCM; and SQL-INSTALLATION-02 is for Solarwinds. SCCM definitely requires a unique SQL installation; likewise, we keep Solarwinds segregated for peformance reasons.
My questions, if you have the time --
1> If you've found any faults in this design, could you please explain?
2> Do I need a unique MSDTC per SQL installation?
3> Do I need a unique quorum disk per SQL installation?
4> Under what circumstances might I relocate the OS paging file, and to where?
Thank you so much --