Hi Martin,

There is a storage efficiency doc from NetApp's that addresses this very thing.

"Storage Efficiency Every Day: How to achieve and manage best-in-class storage use"

October 2010 | RA-007

Basically they say that after thin provisioning all vols on an aggr (along with dedupe, autogrow & snap delete) you set your thresholds on the aggr lower and tie decision making to those thresholds. Ex. 50% is "almost full", 60% - start looking in volume growth patterns and see if things can be removed, deduped or some process is awry, 70% - time to decide to add disks or move data elsewhere.

These are examples. The doc is much better at explaining.

---- Scott Eno s.eno@me.com

On Aug 1, 2013, at 11:18 AM, Martin martin@leggatt.me.uk wrote:

Does anyone know of Netapp best practise docs or other references on configuring monitoring on aggregates that have thin provisioned volumes:

Specifically:

Aggregate Overcommitted Threshold (%) Aggregate Nearly Overcommitted Threshold (%) Aggregate Nearly Full Threshold (%)

I realise this depends on the rate of change of the data i.e allowing enough time to provision more storage or reduce usage. I am not clear on some of the detail though.

Any pointers would be appreciated.

Martin

-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/Oncommand-Core-DFM-thr... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters