Are there any known issues with vaai xcopy and the new Inyo code on the VNX?
When we do a clone from one array to another, no issue.
When we do a clone with a pool with acceleratedmove enabled:
It takes about half an hour to clone a vm.
When we repeat the same step with acceleratedmove disabled:
done in two minutes, my two destination luns in my fastvp pool which has EFD,SAS and NL-SAS, FAST Cache enabled are showing following iops:
Period between the two peaks is the VAAI enabled copy, the two peaks are non VAAI enabled clone's.
Other hosts in our demo cluster are showing the same behaviour.
Our setup is running vsphere 5.0.0 623860 over a FC network connected to VNX running latesty inyo code.
No case created, it's our demo equipment, not sure this is still under support.
Going to do some more debugging next week. It looks like if we're migrating within a pool with the same tiering policy we're having some issues.
I was wondering if you could reach out to me with your contact info along with your location?
We would like to make sure our local teams can reach out as well as gather some information?
My email is email@example.com
I have a few queries too on INYO:
1. Whether the Flare is now INYO? Or is it somethingn being used by Developers for the new code?
2. Whether the INYO is above and from 5.32?
3. Did somebody upgraded to this version and faced any bug/issue say ... LUN tresspass storm or LUN going offline
4. Does INYO supports recover point as i read somewhere that it doesn't.
I need urgent inputs on this if some one can help please.Thanks in advance
1) Inyo is / was the code name for the 5.32 release of FLARE + the 7.1 release of DART.
2) Inyo specifically refers to 5.32.x and DART 7.1.x only. Not future versions.
3) These scenarios can happen if you aren’t following best practices.
4) RecoverPoint is supported on 5.32.
Matt Cowger | EMC Sr. vSpecialist – VCDX #52
(t) @mcowger || (m) 540.999.8239 || (b) blog.cowger.us
Inyo is EMC internal code name for Rel 32 (5.32)
There is an issue with Virtual Provisioning that can cause trespassing issues
It is fixed in Rel 32 P15 (see https://support.emc.com/docu44571_Virtual-Provisioning-for-VNX-OE-for-Block-Release-Notes-Version-05... )P5
There was issues with early rel 32 with Recoverpoint but I do believe that Recoverpoint is support with Rel 32
(I would advise opening a new thread too not to be confusing issues )
Thanks for the response. As you suggested I opened a new thread (this is my first thread so not sure how to invite you)
I have clearly mentioned by concern and queries. If you can have a look and suggest something it will be of great help.
Thanks in advance.