Subscribe

Is there a trend report/graph in DFM to show the running out of storage?

Hi,

I found there is a "volume capacity used againt total" graph in the DFM, which shows the capacity trend. However, the trend line doesn't extend enough into future so that we can't see what date the trend line hits the capacity. The user wants to get such a graph so that he can do a forcast and present to the management when he is going to run out of storage.

Thanks,

Terrence

Re: Is there a trend report/graph in DFM to show the running out of storage?

Terrence,


"Volume Growth" report provides the info customer is looking for in "Days To Full" column.

Thanks,

Raj.

Re: Is there a trend report/graph in DFM to show the running out of storage?

Hi Raj,

Thanks for your advise. I also checked this report before. However, it only shows 'more than a year' if over an year which is not enough. You know, the customer probably need to forecast for 2-3 years budget/capacity growth,  then he needs to know a more precise timeframe.

Regards,

Terrence

Re: Is there a trend report/graph in DFM to show the running out of storage?

You could file an RFE to show the exact number of days in OpsMgr reports.

Also, "Qtree Growth" report which contains similar data for Qtrees has the same issue.

This same problem exists in the custom report, if you create one using Volume/Qtree catalog.

Other alternatives for you at this moment are:

1. Get this data from database directly and run a query like below:

"SELECT objFullName, volDaysToFull FROM objectView, volumeView WHERE objId = volId"

A large value of "100000000" means per day data growth is less than a KB. You could treat that as infinite.

Refer: http://media.netapp.com/documents/tr-3690.pdf for details about DB access.

2. You could do your own calculation too. Create a custom report that will get you the two fields required to do the calculation, "Volume Available" and "Volume Daily Growth Rate". If you divide first one with second one, you get the days to full. Make sure both the columns use the same units in the custom report. For easy scripting, you could get the report output in perl or any other text based formats and have a script to do the calculation.

Re: Is there a trend report/graph in DFM to show the running out of storage?

Ravindra,

Thanks! Just want to know if there is a built in graph that can show this requirement. Will figure out how to do it manually.

Cheer!

Terrence

Re: Is there a trend report/graph in DFM to show the running out of storage?

Graphs don't have days to full, instead they have trend value.

"volume-usage" and "volume-usage-vs-total" are two graphs, that show

trend values. Probably, you can pick one.

If you run the graph CLI like below:

$ dfm graph volume-usage <volume-name-or-id>

It will give you samples in three colums, (timestamp, used space, trend

value).

You can extrapolate the trend in future by specifying "-e" option, e.g.,

to extrapolate for next two years (2365246060=63072000) you could

run it like following:

$ dfm graph -e 63072000 volume-usage <volume-name-or-id>

For the extrapolated samples, used space column will have "-" value.

Re: Is there a trend report/graph in DFM to show the running out of storage?

Ravindra,

Thanks so much. Will try it out.

Regards,

Terrence

Re: Is there a trend report/graph in DFM to show the running out of storage?

I'm not sure a DFM report is going to be accurate enough to project space usage more than a year in advance (and probably not that far either).  Many factors could change (the size of the volumes, the data change rate, and so forth) over that timeframe.  Without a human actually looking at the graphs and making a judgement call, I would not trust our projection that far in advance.

Re: Is there a trend report/graph in DFM to show the running out of storage?

Hi Pete,

Sure, this will not be accurate, and actually the user doesn't need a very accurate answer. He just need a rough time frame and a graph to present to the managment; let say, according to the trend,  20 months later, he will be running out of capacity. This is what the user needed.

Cheers,

Terrence