UNSOLVED

scrookston

updated

13 years ago

0

955

March 21st, 2013 16:00

FAST on VNX 5100

To anyone out there that has experience with a VNX 5100, what capabilities can I expect from FAST. I've received conflicting information however it appears I was able to create a FAST pool with placement, but no ability to auto-tier thereafter or even manually move and relocate data.

  • GearoidG

    251 Posts

    519

    0

    Posted March 21st, 2013 16:00

    When you say FAST do you mean FASTVP or FASTCache?

    Considering its a 5100 where FASTVP is not supported I am curious about your questions

    See http://support.emc.com/docu45748_FAST-VP-for-VNX-OE-for-Block-Release-Notes-Version-05.32.000.5.201.pdf P3 for the VNX's that are compatible

    Also see emc267855

    Which discusses the mutual exclusivity of enablers on VNX5100's

    Hope that helps

    Gearoid

  • 519

    0

    Posted March 21st, 2013 17:00

    Sorry to not clarify, FAST VP. I'm hearing now from others it is not supported but have an array that is in a state where all the tiers of storage were setup in a single pool. It appears some of them went to the slowest disk possible and was wondering if there is any easy way to correct this.

  • GearoidG

    251 Posts

    519

    0

    Posted March 22nd, 2013 03:00

    Hmm as I said its  not possible for data to tier on 5100 with FASTVP so I dont know how it could have got there with out seeing specifics

    The only way that I can suggest is that you could correct it with a lun migration to luns that in specific tiers

    Hope this helps

    Gearoid

  • Rainer_EMC

    6 Operator

    8645 Posts

    519

    0

    Posted March 22nd, 2013 04:00

    FAST VP is the relocation of slices between tiers in a pool based on their I/O temperature

    That isn’t supported on the 5100

    Of course the 5100 does support pools composed of different tiers – so there is an initial distribution – i.e. what slice get put onto which disk.

    I think that is done based on capacity – i.e. we try to fill up the tiers equally.

    Without FAST VP a block will stay on the disk that it was allocated initially.

    With FAST VP in the latest releases you also get the new policy “Start High then Auto-tier” which means that new incoming blocks would be allocated on the fastest tier initially.

    That only makes sense if you also use FAST VP to later move some of these that aren’t accessed frequently to a lower tier.

    My advice – don’t create pools with different tiers on a 5100 if you cannot tolerate the performance of the slowest tier

  • kelleg

    6 Operator

    4537 Posts

    519

    0

    Posted March 29th, 2013 15:00

    Was your question answered correctly? If so, please remember to mark your question Answered when you get the correct answer and award points to the person providing the answer. This helps others searching for a similar issue.

    glen