Database Management
SQL Sentry - Troubleshooting and Implementing Mount Point Support to Maximize Database Efficiency
The purpose of this how to article is to understand what Mount Support is and how to troubleshoot it's implementation in SQL Sentry. Mount point support is a crucial feature in SQL Sentry that enhances the management and accessibility of storage resources. It allows SQL Server databases to utilize additional storage without being restricted by traditional drive letter limitations. Here's a detailed overview of the key aspects and recent insights related to mount point support in SQL Sentry. Imagine your computer's storage as a bookshelf with limited shelves. Each shelf can only hold a certain number of books. Mount point support is like adding doors on these shelves that open into additional rooms with more shelves. This way, you can store many more books (data) without cluttering your main bookshelf (drive). Essentially, it expands your storage capacity seamlessly and efficiently.
First published date
5/20/2024 1:36 PM
Last published date
5/20/2025 6:06 PM
Overview
Mount point support allows a system to access and manage storage devices using mount points, which are directories on a file system that serve as access points for other file systems or volumes. In the context of SQL Server, it enables databases to utilize additional storage without being limited by the drive letter restrictions of traditional storage configurations. Several key insights on this topic below:
Troubleshooting DCOM Permission Errors
Setting DCOM Permissions for Mount Point Support to resolve DCOM permission errors related to Mount Point Support in SQL Sentry, it is recommended to update to the latest version of the software. If upgrading is not possible, you can manually set the necessary permissions. This involves editing the registry to grant full control to administrators and configuring DCOM settings to give the SQL Sentry Monitoring service account full permissions. Specific steps include locating GUIDs in the registry, adjusting security settings, and modifying DCOM properties to ensure proper activation and access permissions for the Virtual Disk Service. **Disclaimer: Do not edit the registry unless it is absolutely necessary! Modifying the registry may require you to reinstall your OS. Before editing or changing anything, you may consider backing up the Registry.
Troubleshooting Port Issues
Port Requirements for Mount Point Support Mount was introduced in SQL Sentry version 5.5. For Windows versions prior to Windows 2008 R2 and Windows 7, the default communication ports required are generally covered by those needed for RPC. For newer versions, the default port is 5895, as WinRM 2.0 is used for remote communication. This is primarily because VDS uses WinRM (Windows Remote Management) 2.0 to communicate remotely in the newer versions of Windows. See the following TechNet article for information on this change: Details on secure port configuration for WS-Management in Windows 7 and Windows Server 2008 R2
To open this port on servers with built-in software firewalls, you can run a command to enable the necessary firewall rules. After executing this command, it's essential to scan for configuration changes in SQL Sentry to ensure the settings take effect. This script below would be run from Command Prompt and it should open necessary ports to allow SQL Sentry to collect Mount Point Information:
Additional Solutions with PowerShell
You might find success by enabling Mount Point Support by opening the Remote Volume Management firewall rules using PowerShell Commands:
These commands potentially enables the necessary firewall rules, allowing SQL files on mount points to appear. After running the command, use the "Scan for Configuration Changes" option in SQL Sentry to finalize the setup as a Best Practice.
Troubleshooting DCOM Permission Errors
Setting DCOM Permissions for Mount Point Support to resolve DCOM permission errors related to Mount Point Support in SQL Sentry, it is recommended to update to the latest version of the software. If upgrading is not possible, you can manually set the necessary permissions. This involves editing the registry to grant full control to administrators and configuring DCOM settings to give the SQL Sentry Monitoring service account full permissions. Specific steps include locating GUIDs in the registry, adjusting security settings, and modifying DCOM properties to ensure proper activation and access permissions for the Virtual Disk Service. **Disclaimer: Do not edit the registry unless it is absolutely necessary! Modifying the registry may require you to reinstall your OS. Before editing or changing anything, you may consider backing up the Registry.
Troubleshooting Port Issues
Port Requirements for Mount Point Support Mount was introduced in SQL Sentry version 5.5. For Windows versions prior to Windows 2008 R2 and Windows 7, the default communication ports required are generally covered by those needed for RPC. For newer versions, the default port is 5895, as WinRM 2.0 is used for remote communication. This is primarily because VDS uses WinRM (Windows Remote Management) 2.0 to communicate remotely in the newer versions of Windows. See the following TechNet article for information on this change: Details on secure port configuration for WS-Management in Windows 7 and Windows Server 2008 R2
To open this port on servers with built-in software firewalls, you can run a command to enable the necessary firewall rules. After executing this command, it's essential to scan for configuration changes in SQL Sentry to ensure the settings take effect. This script below would be run from Command Prompt and it should open necessary ports to allow SQL Sentry to collect Mount Point Information:
-- Scripts are not supported under any SolarWinds support program or service. -- Scripts are provided AS IS without warranty of any kind. SolarWinds further -- disclaims all warranties including, without limitation, any implied warranties -- of merchantability or of fitness for a particular purpose. The risk arising -- out of the use or performance of the scripts and documentation stays with you. -- In no event shall SolarWinds or anyone else involved in the creation, -- production, or delivery of the scripts be liable for any damages whatsoever -- (including, without limitation, damages for loss of business profits, business -- interruption, loss of business information, or other pecuniary loss) arising -- out of the use of or inability to use the scripts or documentation. netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes
Additional Solutions with PowerShell
You might find success by enabling Mount Point Support by opening the Remote Volume Management firewall rules using PowerShell Commands:
-- Scripts are not supported under any SolarWinds support program or service. -- Scripts are provided AS IS without warranty of any kind. SolarWinds further -- disclaims all warranties including, without limitation, any implied warranties -- of merchantability or of fitness for a particular purpose. The risk arising -- out of the use or performance of the scripts and documentation stays with you. -- In no event shall SolarWinds or anyone else involved in the creation, -- production, or delivery of the scripts be liable for any damages whatsoever -- (including, without limitation, damages for loss of business profits, business -- interruption, loss of business information, or other pecuniary loss) arising -- out of the use of or inability to use the scripts or documentation. #PowerShell to check if enabled (execute on the target) Get-NetFirewallRule | Where DisplayName -match "Remote Volume Management" #Powershell to Enable (execute on the target) Get-NetFirewallRule | Where DisplayName -match "Remote Volume Management" | Set-NetFirewallRule -Enabled True
These commands potentially enables the necessary firewall rules, allowing SQL files on mount points to appear. After running the command, use the "Scan for Configuration Changes" option in SQL Sentry to finalize the setup as a Best Practice.
Product section
SQL Sentry (SQLS)
Resolution
If mounted drives are not showing up under Disk Activity or Disk Space, it is likely related to the required ports or DCOM permissions. Mount point support in SQL Sentry is a valuable feature that enhances storage management for SQL Server databases. By ensuring proper DCOM permissions and opening necessary firewall ports, users can effectively utilize additional storage resources, thereby improving database performance and scalability. These insights and steps provide a comprehensive understanding of how to implement and troubleshoot mount point support in SQL Sentry.