Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

AppInsight for Exchange 2013 and Mailbox Databases on Mount Points.

In order for Auto-Reseed to function correctly Mount point need to be created for the databases. When I am look at the database view on the exchange server I see performance data for the C: drive instead of the of the disk that the database is installed. Is there any configuration fix or is this on the radar to be fixed.

I am using WMI monitoring to capture mount point disk statistics.

SAM 6.2.3

Chris Hammel

Find more posts tagged with

Accepted answers

All comments

jamesatloop1

Go into the server node itself and list resources from the management box. Ensure all your volumes are selected to be monitored and then redo the sam scan on that node.

chammel

With Exchange 2013 you can have up to 4 databases per disk. Microsoft's guidance is to have each database have its own mount point. So there are 5 mount points per Disk.

Using WMI polling the disk is only identified using one of the mount points. On this server the disk mount point is (c:)\ExchangeVolumes\ExVol1. But the databases are created under the (c:) ExchangeDatabases\DB01 mount points. My guess here is that SAM is not smart enough or WMI does not return enough information to map the Database folder to the Mount point.

jamesatloop1

Ok, does it have sql server on it at all?

aLTeReGo

I believe the following KB article should help you resolve the issue.

AppInsight for Exchange error: Cannot identify correct space for volumes in mount points - SolarWinds Worldwide, LLC. He…

chammel

I have done this. The problem is that the Identified mount point is C:\ExchangeVolumes\ExVol1 but the Database were created on C:\ExchangeDatabases\DB01\ mount point. Both mount points are the same volume but have two different paths. This is just one database as an example. The Exchange 2013 server has 44 databases and 11 disks with 4 mount points per disk for the database and 1 mount point for the Volume. Like I said with 5 mount points all pointing at the same disk but used for different things one of the technologies is not able to map the mount points to the disk ether WMI or SAM.

The reason for this configuration is because I have a 12th disk used as an AutoReseed. The AutoReseed service once a disk failure is detected will create the folders and remount the good disk in place of the bad disk for the C:\ExchangeDatabases\???? mount points. Then Reseed the Databases to the good disk.

This is Exchange 2013 not SQL.

jamesatloop1

I know its exchange but the backend is an sql database?

chammel

The backend of Exchange is a Jet database.

jamesatloop1

OK, the only thing left is the credentials that you have used to access those databases, sounds like the permissions dont have access to all the databases, can you confirm what credentials you are using and they have full access under exchange ad?

aLTeReGo

I would recommend opening a case with support. From what you describe it sounds like SAM is having a difficult time correlating the mailbox databases to their respective Mount Point locations.

amaiman

Did you ever get a resolution to this? I'm hitting the same issue (multiple mount points to same volume and it doesn't correlate them properly).

Wanted to see if they had a fix before I spend the time to open a support ticket.