These mount on folder names below C:\Cluster Storage and are co-owned by all servers in the cluster.
Right now, the mount points do not even show up as a monitored disk, let alone dealing with the same view on all cluster hosts.
This is a must for all of us who use hypre-v
Having been using this product in a Hyper-V environment for 6 months now, i surely feel your pain and frustration. Once you start getting to Windows 2012 Hyper-V deployed in your environment things start to get better because the filesystem type is CSVFS - and the mount points will start showing up as "mount points" / data stores with a explicit name.
I countered this problem in our environment by creating a label called isClusteredSharedVolume and then scoping filters/searches/queries etc only to include these items of concern for alerting/trends/reports/etc. I did this because i didn't like the fact i was getting space, iops, etc from disks that I had no concern in the world for in my environment. If you look closely Solarwinds is finding the disks for Windows 2008 - It's just not as you expect to see them beneath a C:\Cluster Storage mount point.
It picks up the name defined in your Failover Cluster Manager beneath Cluster Shared Volumes
If you're not seeing these disks, you've likely got some configuration issue. Don't worry I've had many in the system because nothing wants to work as i expect it too. If you're not seeing the disks might i suggest taking 1 cluster and breaking it out into its own discovery job. I've found that separating all my clusters into their own discovery jobs has been helpful for accuracy of data and spreading the load on the VMAN appliance over time. Not spreading the load seemed to end in missing data because of jobs would overlap and not complete, etc. In each discovery job specify the management IP for each node, and also include the Cluster IP.
It stinks managing separate discovery jobs at times when you change the environment around some. Like in my case, i'm currently removing nodes from 2008 clusters and shifting them to 2012.
Hi uidzer0,
This request is for Storage Manager. I believe your statements apply to Virtualization Manager, which is a different product.
