Mounting a Volume as a Folder on a Cluster
I have recently had an opportunity to learn some new stuff from a customer so I thought I would share. The scenario is implementing an eight instance SQL Server 2008\Windows 2008 cluster with seven drives per instance. If you are sharp, I bet you are saying, “Wait a minute, there are only 20-something drive letters.”. This is true but did you use your toes to count on?
You have to use mount points. See below.
So let’s continue with one instance of our example. The seven drives would be provisioned something like this:
- d:\ – 3GB – Program files
- d:\system – 10GB – System databases and system object filegroup files for every user DB
- d:\data – 500GB – all user database filegroups files
- d:\indexes – 300GB – all user index filegroups files
- d:\bindata – 2TB – all user blob filegroups files
- d:\TempDBData – 100GB TempDB data files
- d:\backups – 3TB
Here are the basic steps you go through:
- Present the LUNs to the OS
- Create sector aligned partitions
- Create the root letter formatted with x64 NT allocation units
- Format the mount points with x64 NT allocation units
- Create empty folders named accordingly in the root drive. d: in this case
- Create the mount points just as you would assign a drive letter. See the image above
- Install your clustered instance to the root drive with system databases going to d:\system in our case.
- After the installation, make the SQL Service cluster resource dependant on the mount points.(The mounted folders will automatically be added to the cluster group if you install to the root.)
Now before I end, setting it up like this is really dictated by what is important. Unless you just have uddles of disks, this design put aversion to data loss(assuming there are separate disk groups.) ahead of performance. However, that is another conversation.
This content is published under the Attribution-Share Alike 3.0 Unported license.
Comments
-
Helge Rutz
-
Jason Massie
