Gatekeepers: Thin and bound

Question

Hi Guys,

I have seen numerous discussions on gatekeepers and browsed through EMC KB 74113, however I am still not clear if

it is OK to have GKs thin provisioned and Binded to the thin pool in the SG with another TDEVs when FAST policy is applied to this SG?

In this case GKs been thin and bound will be moved around by FAST policy

This setup has been in existence in the present environment and I want to verify no issues will be encountered down the road.

Otherwise, I will created a separate MV for GKs with no policy applied, or pin GKs?

This is VMAX40K with Enginuity 5876.

Let me know what you think. Thanks!

dynamox · Answer

don't bind thin gatekeepers.

aldikan1 · Answer

Thanks Dynamox,

Any details you can share on "why"?

I want to have a better understanding on any problems with that setup: Are there any EMC docs that specifically saying "not to do that" and listing reasons? Thanks!

dynamox · Answer

i think it's documented in the KB you provided above. GK is used to pass symcli commands, no need to bound it because you will never add any user data to it.

VMAX

Gatekeepers: Thin and bound

Was this post helpful?