We suffered an outage due to Storage behaviour suddenly being maxed out. We were polling capacity every 6 hours and between those two 2 polls was all it took.
I raised a question here about how to alert on change of behaviour and subsequently a feature request if you'd be so kind.
One request we had from the business was to increase the polling to monitor Capacity every 30mins for example instead of 6hourly. Concious this might mean a growth in DB until the weekly/monthly averaging up takes effect but any other issues?
According to the SW document here I need to get the vendor guidance on each SAN model but any issues SW side?
Has anyone dropped the 6 hourly values right down? That first line 'changing the frequency the data is polled by SRM does not alter the frequency the data is collected' is confusing me. SW poll SAN more often but SAN might only poll itself at a fixed speed so more than that is pointless?
I found also this article which leads me to believe that the max frequency the data is provided is limited by the SMI-S in this case, or perhaps the SAN, we monitor about 37 SANs and all but 2 are direct due to issues seen with SMI-S reliability for SW SRM pass-through.
Also someone did mention /Orion/Admin/AdvancedConfiguration/Global.aspx and this setting, stating Capacity runout time is only calculated weekly, but I am hoping that may just be the Capacity Runout date, not the Capacity data changing.
Hoping someone has tried similar and has some advice/guidance
Thank you
