HPE Storage Users Group

Hi!

AFAIK you can set a growth warning on a CPG and on VV, but is it some where you can set a warning on lets say when your total storage capacity is at 80%?

If you are overprovisioning your storage with 2 or more CPGS on the same physical disks, your storage could already be full before the CPG warnings starts showing up i believe?

You can set warnings on system capacity as well.

Also, the sp can alert both you and hp when the capacity gets low via email

The array has some pre-defined warnings I believe at 85% and 95% and I believe also at 50 and/or 75% of RAW.

You can also use the setsys command.

http://h20564.www2.hp.com/hpsc/doc/public/display?docId=mmr_kc-0105741

Does anyone use CPG growth warnings? More specifically, does anyone have a strong reason/opinion on why they use CPG growth warnings?

I personally don't since I'm far more concerned with the overall system-wide usage as opposed to a single cpg.

That said, the only technical reason I can think of for implementing them is for AO. Since AO won't move regions into a CPG that has reached a warning on growth, you can use them to limit the amount of data AO will place in a CPG.

I was advised by HP to never assign a growth limit to a CPG, as if the CPG hits it's growth limit, the applications residing within will halt. I also feel strongly that warnings should be literally technical warnings. I don't want to see a red light because a tenant added some data. I only want the red light when things are getting tight and I need to buy hard drives.

Richard Siemers wrote:Does anyone use CPG growth warnings? More specifically, does anyone have a strong reason/opinion on why they use CPG growth warnings?

I only used them in the past for AO. AO uses them to determine how much data to move into atier. When we have multiple AO polices that overlapped same physical tiers fo disks the only way to make sure they were no stepping on each other was to use growth warning as AO honors the growth warning as the max it will put in a CPG tier. It is a hookey way to do things and we have voiced our concerns because then it causes the array tho issue alerts when you hit a growth warning.

Another use case might be in a service provider environment typically using virtual domains. When a tenant is closing in on their leased capacity (maybe due to snaps etc) it would trigger a warning and you can follow up with an ivoice for additional capacity allocation without the need for a hard stop (limit).

Also for AO take a look at the new volume filter.