mugurs wrote:
I know what the "best practice" teaches us. Unfortunately, there are some specific critical situations when "best practice" can't help you. For a CPG where I've set only "growth warning" I've got allocated capacity bigger than the respective capacity specified by "growth warning". And that allocated capacity grew bigger and bigger due to an unstoppable tunesys and I thought in this case would have helped to set "growth limit" and not "growth limit". it appeared to me that "growth warning" had not any effect on limiting the allocated capacity.
thanks,
mugurs
I'm not quite sure I understand what you're saying, but setting a limit will surely at some point stop io from writing to the cpg, hence why hp do not recommend using it?
And best practice is normally there as a recommendation to stop you from getting into a 'critical' situation.
I agree it's not always the final word, but it's normally a good indication of what you should choose.