Monitoring disk usage
Posted: Mon Aug 04, 2014 11:00 am
This isn't really a StarWind question but I'm guessing some of you will be able to point me in the right direction.
Our current v6 production build has both what we call primary and secondary storage. Primary storage is on faster 15k SAS drives but due to 600GB limit, is more precious. Secondary storage is on 7k SATA drives that is supposed to be for less frequently used storage.
However, I happened to look at throughout on the two targets on StarWind over a 24 hour period and 23GB had been read from secondary storage compared to 15GB from primary storage. That at first glance looks the wrong way around! Sure, not a very scientific check so we raised a job to investigate further.
Starwind itself doesn't appear to give much information/reporting here aside from last hour or last 24 hours. Can't check back over a week - that's one for the wishlist. Maybe it's already in v8. More granular reporting would be good as well around iSCSI connections - that would allow us to determine which Hyper-V hosts were generating the load.
But I suspect we actually need to monitor VMDX usage on the Hyper-V cluster. So hence this post - any ideas how to go about this? Third party tool? We do actually have SCOM licenses but we're only just rolling out that system.
Cheers, Rob.
Our current v6 production build has both what we call primary and secondary storage. Primary storage is on faster 15k SAS drives but due to 600GB limit, is more precious. Secondary storage is on 7k SATA drives that is supposed to be for less frequently used storage.
However, I happened to look at throughout on the two targets on StarWind over a 24 hour period and 23GB had been read from secondary storage compared to 15GB from primary storage. That at first glance looks the wrong way around! Sure, not a very scientific check so we raised a job to investigate further.
Starwind itself doesn't appear to give much information/reporting here aside from last hour or last 24 hours. Can't check back over a week - that's one for the wishlist. Maybe it's already in v8. More granular reporting would be good as well around iSCSI connections - that would allow us to determine which Hyper-V hosts were generating the load.
But I suspect we actually need to monitor VMDX usage on the Hyper-V cluster. So hence this post - any ideas how to go about this? Third party tool? We do actually have SCOM licenses but we're only just rolling out that system.
Cheers, Rob.