Port Groups / SG Different FAST Policy

Question

Is there a reason I need to create multiple masking views for storage groups that are associated with different FAST policies? The reason I'm asking is I inherited an environment that's done exactly that and I trying to understand why? Would like to simplify if possible:

I'm also trying to understand why we would of created multiple storage groups for the same ESX cluster. I should be able to use nested storage groups shouldn't I?

I'm working with a VMAX 10K, single engine, 2 directors, mainly VMware and Recoverpoint. Also questioning our port group strategy and if there are any best practices on how the FA ports should be divided up? I'm going to be going through and redoing the mappings since we don't have the ports spread across each director very well.

cincystorage · Accepted Answer

A single masking view can only contain a single group group, however you can use cascaded storage groups (parent/child). You might end up with something like:

vmware_clu_milg8_MV

-> IG

-> PG

-> vmware_clu_milg8_parent_sg (no devices)

-> vmware_clu_milg8_fast_a_sg (devices associated with FAST policy A)

-> vmware_clu_milg8_fast_b_sg (devices associated with FAST policy B)

duhaas1 · Answer

great feedback Mark, thanks much.  is it common to see storage groups with individual devices in them?  i'm trying to use the performance piece of unisphere for vmax for some things, but its difficult when you have storage groups that contain multiple devices when you trying to say get the change rate for a particular device.

cincystorage · Answer

The idea of nested/cascaded storage groups is something "new" to a lot of people... So you will often fine environments where people use separate storage groups for data access and FAST policies.

I prefer the cascaded approach, it just seems more well organized to me.

duhaas1 · Answer

thanks for the feedback mark

VMAX

Port Groups / SG Different FAST Policy

Was this post helpful?