Can concatenated Meta be of different hyper sizes ?

its symmetrix VMAX model, Enginuity 5874.

You can choose whatever number of members.

EMC suggests an even number of members. Better if it's something like 2^n. But you CAN use odd number of members, if you need.

With an odd number of members (or a number that don't fall into the 2^n suggestion) it's difficult spreading the workload evenly in the backend. But usually this isn't a real issue.

If you are using RAID in the backend, don't spend too much time in choosing the number of members.

If you are using mirroring, try to use 2^n rule but don't waste too much space (and time) in choosing the number of members :-)

Not sure... Pls wait replies from other contributors...

You talk about concat meta. AFAIK concat isn't available in recent codes. What code version are you running in your storage? What storage are you using?

Thanks, can i mix different types of  hyper sizes as members with in same meta ?

We definetly need an answer from someone with vmax skills... :-)

Can't answer on vmax, yet. :-)

yes.. you can..

Meta Device Members (3)  :
        {
        ----------------------------------------------------------------------
                               BCV  DATA                    RDF  DATA
                      ----------------------------  --------------------------
        Sym    Cap    Std Inv BCV Inv Pair          R1 Inv R2 Inv Pair
        Dev    (MB)   Tracks  Tracks  State         Tracks Tracks State
        ----------------------------------------------------------------------
    --> 0xxx  34856        -       -  N/A                -      - N/A
        0xxx  34856        -       -  N/A                -      - N/A
        0xxx   1688        -       -  N/A                -      - N/A
        ----------------------------------------------------------------------
              71400        -       -                     -      -
        }

You need to make sure, all devices are unbind from pool....

Can you please guide me which one is the best practice for creating 350 gig LUN for windows host. with the device standards mentioned above.

1. 21*16.8gb gives 354gb
   
2. 2*134gb+1*67gb+1*16gb gives 354gb
   

Do you see any other possibilties, or any standard method for dealing this situations as you have somany combinations of summing up devices to 350gig.

You mention in your original post that virtual provisioning is in place. With VP, the front end meta devices are assigned to a device pool rather than a tied directly to back-end hyper volumes. so with VP in place, the practice of having uniform meta sizes can be relaxed somewhat.

Rather than pre-creating the TDEVS at standard size, if it is going to work better for you perhaps you could create your TDEVS as part of the storage allocation process with custom meta member sizes.

Here are some considerations with the meta member size:

- SRDF/S can have one outstanding write per device per path, so a single large device will potentially have limited write rate compared to a meta device.

- Symmetrix devices numbers are finite resources, there are limits on the number that can be presented to an FA port, and an overall limit. So you need to be able to address all your back-end storage while keeping within the limits of your available Symmetrix resources.

here I have 67.4GB as standard in my environment, 5 devices cannot makeup 350 that way, All I am trying to know that i can mix up different device sizes in a meta, that got answered in this post. I can understand if you have 70 gig dev that could make up simply 70*5 350gig there.