Reporting Issue in SIM 5.1 sp1

[jlbetsch]

I have rolled out a disk space thresh hold for all servers in my domain. There is one server that is proving to be an enigma.

It is a ProLiant BL20p G2. It connected to our SAN with 4 logical drives that are spanned. Why is it spanned? I have no idea, this configuration predates everyone on my team.

Well when I do a data collection report in insightm - the total disk space for the SAN is correct, and the available space is correct. But the Percentage Used is off by a LOT. It shows that only 12 percent of the disk space is used when actually, it is about 40%.

Windows reflects the correct amounts, even in the "system management homepage" is reporting everything properly.

The issue is that we got down to 8% free space on the SAN last week and the disk threshold never prompted us. Why - because SIM - data collection report still showed about 30% available and yes, the disk space thresh hold is installed on this server.

This is the only server that is spanned. All other servers that are connected to the SAN are just fine in Insightm.

Is there a known issue for this? How does the data collection report calculate the info when genereating the report? Has anyone else seen this issue?

[Rob Buxton]

I'm confused.
You use the term "free space on the SAN" but you're also talking about space on a particular disk presented to a server which would be a LUN.
Space on the SAN itself is only monitored if you have the appropriate software set up and that depends on what kind of SAN you have. Growth on a SAN would be caused by snapshots, logfiles or whatever, again depending on what kind of SAN you have.

As regards the data presented to the reports, the Report tables, by default, are updated every two weeks. There's a task that does this: Bi Weekly Data Collection.
You can increase the frequency of this.

You can also create a Daily Historical Data collection task and then write your own reports to pull data directly from the database tables. The data tables (CIM_Logical_Disk from memory but check) will contain more up to date data.

Lastly there is an issue with agents prior to 7.80 where the usage figures for larger storage arrays are not correctly reported.