- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Re: SQL 2005 VM on VMFS what cache policy?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2016 05:38 AM
тАО09-14-2016 05:38 AM
I have a Windows 2008 R2 VM, running SQL 2005. I have the drives split up on VMware....
C\D on its own VMFS volume with ESX caching policy
L (Logs) on its own VMFS volume with SQL Logs caching policy, or no caching.
M (SQL Data) on its own VMFS volume with ESX or SQL Data???
Thanks for any help!
-Chris
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2016 08:57 AM
тАО09-20-2016 08:57 AM
SolutionHi Chris,
Excellent question. The performance policies you've selected for your SQL logs and SQL data are designed for volumes directly connected to a Windows host. There is one attribute on both of these policies that makes them less ideal for VMFS Datastores. This attribute, called "Quota Exceeded Behavior", is set to "Set Offline" in both of these policies. This setting will cause a thin provisioned volume to go offline in an out of space condition. ESX will respond to this behavior by going into APD (all paths down) and potentially PDL (permanent device loss). The performance policy named "VMware ESX 5" has the correct setting, which is "Set to Non-Writeable". ESX will respond to this behavior by "stunning" (pausing) the VM. ESX is able to automatically recover from this situation once the low space condition is resolved.
To address this, you might create a new performance policy for both MS SQL and MS SQL Log on VMFS. You can use the existing policies as models. The only change would be to the "Quota Exceeded Behavior" attribute, which should be set to "Set to Non-Writeable". Because the block size and the application category will remain the same, you should be able to change the performance of the volume.
I hope this helps,
-Eric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2016 11:36 AM
тАО09-20-2016 11:36 AM
Re: SQL 2005 VM on VMFS what cache policy?
Thanks!