8/2/2019 Benefits of Using Mount Points With SQL Server Clusters

http://slidepdf.com/reader/full/benefits-of-using-mount-points-with-sql-server-clusters 1/6

 

Top SQL Server Tools

SQL safe backup

SQL Monitor

SQL diagnostic manager

SQL compliance manager

SQL Sentry Performance Advisor forSQL Server

Benefits of Using Mount Points with SQL Server Clusters

By: Dan Quinones | Read Comments (4) | Print

Dan is an Architect/Systems Engineer with over 11 yearsof experience specializing in Microsoft Server and

Database technologies.

Related Tips: More

Problem

The traditional configuration of a letter assigned for each volume on a Windows Server imposes limitations on our SQLServer cluster design. The primary constraint is the twenty-six letters in the alphabet limiting us to that number of 

drives that our server can use. This limits the number of instances we can fit onto a cluster as well as limits the abilityto distribute the workload across disks for a particular instance or database. What alternative configuration can we

utilize to overcome the restrictions placed on our design by the limited number of letters left over for our SQL install?What additional benefits can we achieve with another configuration?

Solution

The use of Mount Points allows us to overcome the challenges discussed above. In addition to overcoming the availableletter limitation, utilizing mount points also allows for greater flexibility, reduced administrative overhead, higher

utilization of hardware investments and even cost-savings. You may be asking, what is a mount point? A mount point

is a mounted volume within another folder or volume. Essentially a mount point is a disk, usually a SAN LUN, that ismapped and ends up being a folder within a folder. In Author Edwin Samiento's tip Configuring Volume Mountpoints ona SQL Server 2008 Failover Cluster running on Windows Server 2008 he outlines the steps to creating and configuring

mount points. In this tip we will further explore the advantages of using mount points and how it may benefit you. Inthis tip we will discuss the reasons and benefits for using mount points.

Overcoming Drive Letter Limitations

Let's look at how mount points can help overcome the l imitations on the number of available letters remaining. Mostorganizations have standard conventions defining items such as disk layout on their windows server builds. Typically a

Windows server has a system drive (C:), a DVD/CD drive (we'll call this F:) and in some cases dedicated local drives forlog and/or application files. It would not be too far-fetched to assume that an organization that is willing to spend the

money and time in deploying a high availability solution such as a SQL cluster would employ such standardconventions. This leaves us with twenty-two available letters for a configuration such as the one described. Thenconsider how often you use A: or B: as volumes on your Windows servers. Most of us think of 3.5" disks when seeingA:. Although we rarely see A: or B: used in the real world, it is generally a best practice to not use them and keep

them reserved. This brings our pool of available letters down to twenty.

Once we setup our Cluster and then the SQL server cluster prerequisite shared Distributed Transaction Coordinator, wehave two more letters used up, quickly taking our pool of available letters down to eighteen.

EnterE-mailAddress  

Identify and resolve SQL Server problems BEFORE they happen with SQL diagnostic manager

fits of Using Mount Points with SQL Server Clusters http://www.mssqltips.com/sqlservertip/2631/benefits-of-using-mou

18-Apr-2012

8/2/2019 Benefits of Using Mount Points With SQL Server Clusters

http://slidepdf.com/reader/full/benefits-of-using-mount-points-with-sql-server-clusters 2/6

Eighteen drive letters may sound like a lot but anyone with experience using dedicated LUNs for the various SQLdatabase and log files will realize that number can quickly be exceeded with even one or two instances. In this examplewe see how quickly we can consume letters with only a single instance:

With only a single instance installed we have used up roughly half of the available drive letters. We are already

becoming constrained if we want to add additional luns for filegroups or install a second or third instance on the cluster.Utilizing a mount point the same SQL configuration above could be configured utilizing a single let ter - the mount pointhost volume.

The contents of the mount point are the same physical disk LUNs as above without using the additional drive letters.

Per MSDN's Maximum Capacity Specifications for SQL Server SQL Server supports 25 instances on a failover cluster.

Let your hardware constraints limit the maximum number of instances you can install onto your SQL clusters, not the

fits of Using Mount Points with SQL Server Clusters http://www.mssqltips.com/sqlservertip/2631/benefits-of-using-mou

18-Apr-2012

8/2/2019 Benefits of Using Mount Points With SQL Server Clusters

http://slidepdf.com/reader/full/benefits-of-using-mount-points-with-sql-server-clusters 3/6

limited number of letters left to you from the alphabet.

Flexibility

When using mounted volumes you have increased options available for your use. If you want to add additional volumes

to spread filegroups across you can easily do this. All you would have to do is add a new volume under the existingmount letter. Another scenario would be if you want to try a different RAID configuration on some of the volumes aspart of performance tuning. You can easily have different RAID implementations configured under the same mount.

Storage tiering also can be utilized easily, in the above example we see a Backup_01 and 02, the 01 volume may becomprised of smaller, higher speed disks that could be used to complete a backup within a limited backup window. The02 volume could then be a slower, larger volume that would archive the backup from 01 for long(er) term archiving.

You can even have storage presented from different storage platforms (as long as they are on the same storagenetwork that the cluster is attached to). These are a few examples of how utilizing a mount point can offer additional

flexibility in your SQL solution design.

Reduced Administrative Overhead

In conjunction with the increased flexibility discussed above reduced administrative workload can be achieved as a

result of the additional flexibility. Additionally the complexity surrounding managing multiple san volumes between 2 ormore cluster nodes is reduced with the use of a single root mount volume dedicated to each SQL instance. In ourexample we know that all our volumes associated to the SQL01 instance are located under the P:\ drive. Gone are the

days of keeping track of which drive letters are in use on which cluster nodes. I have personally seen issues where a

drive letter was available on one node but when a cluster group using that letter was failed over the letter was in useand that volume would fail to come online, causing a outage situation. There may be a small increase in complexity

during the initial setup but the simplicity that follows helps reduce your administration workload in many ways.

Increased Hardware Utilization

As discussed during the drive letter limitation section the number of instances that can be installed on a single cluster

can be increased significantly. Theoretically, without the limitation on the number of letters available to use, we can

install up to the product maximum twenty-five instances on a cluster. This can be scaled even higher to fifty instanceson a stand-alone server, where mount points can also be used. Theoretically, without the limitation on the number of letters available to use, we can install up to the hardware resource limitations or the maximum number of instances,whichever comes first.

We also can achieve greater utilization through the use of "Active-Active" clustering. Active-Active works in a

configuration where instead of allowing the second, traditionally passive, node in a cluster to remain idle, a SQLinstance or instances can be run on both nodes concurrently. This allow us to take advantage of the otherwise idle

resources on that second node. This is also easier to manage with mount points as described in the reduced

administrative overhead section above.

Cost Savings

Along with the increased hardware utilization come the inherent cost-savings of having to deploy less hardware to

support more instances. The extent of the cost-savings does not end with having to buy less hardware. A significantcost of any SQL Server solution comes from the SQL Server li censing. As we know SQL Server is licensed based onphysical hardware, so the licensing cost would be the same for a server regardless if you have 1 instance or 10

instances on it. The savings that can be realized from both hardware and license savings can be significant. Similar tothe way virtualization has taken numerous less utilized servers and consolidated them onto common hardware as

virtual machines, We are effectively consolidating our SQL physical server footprint and reducing costs as a result.

Simple cost-savings analysis

The following is just an example of how savings can be achieved through utilizing a greater number of instances on a

single cluster. The example uses an estimated cost of $25,000 for a SQL license, and assumes we are only purchasingone license per physical cluster we need.

Traditional Cluster Deployments:

# of 

Instances

# of 

Servers

Total # of 

Servers

# of SQL

Licenses:

Total # of 

licenses

Total Licensing

Costs

Instance 1 2 - Cluster 1 2 1 License 1 $25,000

Instance 2 2 - Cluster 1 2 1 License 1 $25,000

Instance 3 2 - Cluster 2 4 2 Licenses 2 $50,000

Instance 4 2 - Cluster 2 4 2 Licenses 2 $50,000

Instance 5 2 - Cluster 3 6 3 Licenses 3 $75,000

Consolidated Cluster Deployments using multiple instances with mount points:

# of 

Instances

# of 

Servers

Total # of 

Servers

# of SQL

Licenses:

Total # of 

licenses

Total Licensing

Costs

Instance 1 2 - Cluster 1 1 1 License 1 $25,000

Instance 2 2 - Cluster 1 1 1 License 1 $25,000

Instance 3 2 - Cluster 1 1 1 License 1 $25,000

Instance 4 2 - Cluster 1 1 1 License 1 $25,000

Instance 5 2 - Cluster 1 1 1 License 1 $25,000

In the above example we were saved on 4 physical servers (the 2 additional clusters needed to support instances 3-5)as well as $50,000 in SQL li censing. Again this i s an example only, use this as a starting point for your own

cost-analysis.

Caveats/Known Issues

With all of the benefits listed above, I am obligated to point out some of the caveats that should be considered. One

thing to take into careful consideration is the amount of instances on a single cluster. The old adage "don't put all your

eggs in one basket" applies here. With the relative simplicity that instances can be stacked onto a cluster make sure toproperly plan for adequate resources in the event that one of the cluster nodes were to fail. Highly consolidated

clusters running many instances would be best suited for development and test environments where hardware failurewould not have as significant an impact as it would in the event numerous instances were to go down in production.

fits of Using Mount Points with SQL Server Clusters http://www.mssqltips.com/sqlservertip/2631/benefits-of-using-mou

18-Apr-2012

8/2/2019 Benefits of Using Mount Points With SQL Server Clusters

http://slidepdf.com/reader/full/benefits-of-using-mount-points-with-sql-server-clusters 4/6

An issue that I have seen comes in the form of installation errors when attempting to specify the mount point folderitself as a data or log directory during SQL install. KB Article 2216461 states that "SQL Server does not supportinstalling to the root of the Volume Mount point because the permissions are not propagated to the Mount Point since

Windows does not let you replace permissions on the root of a volume. To prevent problems during new installationsand applications of updates to SQL Server, create a folder on the root of the mount point and install to that folder. Atthis point, permissions are set correctly.

This would cause installation to fail:

This would be the correct configuration, creating a folder under each mounted volume to specify as your data or logdirectory during install.

Next Steps

Review the tip Configuring Volume Mountpoints on a SQL Server 2008 Failover Cluster running on WindowsServer 2008.

Analyze your environment and determine if any of the benefits noted in this tip could help your organization.Review Microsoft KB Article SQL Server 2008 setup fails to install on a Windows Server 2008-based clustermount point.

Review Maximum Capacity Specifications for SQL Server to familiarize yourself with SQL Server 2008 capacityfigures.

For further information on SQL Server licensing look at A Guide to Assessing SQL Server Licensing - Microsoft.

Related Tips: More | Become a paid author

Last Update: 3/19/2012

Share: Share  Tweet

Free SQL Server Learning

How to Use SQL Server’sExtended Events andNotifications to ProactivelyResolve PerformanceIssues

fits of Using Mount Points with SQL Server Clusters http://www.mssqltips.com/sqlservertip/2631/benefits-of-using-mou

18-Apr-2012

8/2/2019 Benefits of Using Mount Points With SQL Server Clusters

http://slidepdf.com/reader/full/benefits-of-using-mount-points-with-sql-server-clusters 5/6

Comments and Feedback:

Monday, March 19, 2012 - 4:31:02 AM - Wilfred van Dijk Read The Tip

There's also another Caveat with mountpoints and that's the free diskspace issue. A lot of scripts/programs monitoryour free diskspace, based on the driveletter (even microsoft's SCOM is using this technique). Since the real driveletter can be very limited in size this results in a lot of false out-of-free-diskspace warnings.

So don't rely on XP_FIXEDDRIVES when using mountpoints

Monday, March 19, 2012 - 10:00:40 AM - Greg Robidoux Read The Tip

Here a related tip to the previous post:

http://www.mssqltips.com/sqlservertip/2444/script-to-get-available-and-free-disk-space-for-sql-server/

this shows how to get free space per mount point instead of using xp_fixeddrives

Monday, March 19, 2012 - 10:48:52 AM - Wilfred van Dijk Read The Tip

@Greg: Thanks! This saves me some time in developing a script like this.

Monday, March 19, 2012 - 11:06:43 AM - Dan Quinones Read The Tip

Thanks for the comments Wilfred & Greg!

Post a Comment or Question

Keep it clean and stay on the subject or we may delete your comment.

Your email address is not published. Required fields are marked with an asterisk (*)

*Name *Email Notify for updates

Comments

*** NOTE *** - If you want to include code from SQL Server Management Studio (SSMS) in your post, please copy the code from SSMS and paste thecode into a text editor like NotePad before copying the code below to remove the SSMS formatting.

*Enter Code

Sponsor Information

Try the free performance monitoring tool from Idera!

Write, edit, and explore SQL effortlessly with SQL Prompt.

SQL Server Training – How you like it.

Free Trial: Get Proactive Insight with Spotlight® for SQL Server Enterprise.

Solving SQL Server problems for millions of DBAs and Devs since 2006. Join now.

Valuable SQL Server web casts on Performance Tuning, Development, Administration, SSIS and more...

Copyright (c) 2006-2012 Edgewood Solutions, LLC All rights reservedprivacy | disclaimer | copyright | advertise | about

authors | contribute | feedback | giveaways | user groupsSome names and products listed are the registered trademarks of their respective owners.

Paragraph

fits of Using Mount Points with SQL Server Clusters http://www.mssqltips.com/sqlservertip/2631/benefits-of-using-mou

18-Apr-2012

8/2/2019 Benefits of Using Mount Points With SQL Server Clusters

http://slidepdf.com/reader/full/benefits-of-using-mount-points-with-sql-server-clusters 6/6

Edgewood Solutions LLC | MSSharePointTips.com | MSSQLTips.com

fits of Using Mount Points with SQL Server Clusters http://www.mssqltips.com/sqlservertip/2631/benefits-of-using-mou