I know EMC recommends that once a Lun is created, we must not manually change its ownership. If we want that Lun on other SP's ownership, then we must migrate it from old lun to a new lun which has desired ownership. Does any one know why does EMC not recommend changing its ownership manually?
We have a pool on a VNX 8000 in which we have some 35 luns, which currently are all assigned to SPA inspite some of them have default owner as SPB. Considering its active - active, do I need to tresspass the luns to its default owner?
can you validate that default owner is the same as allocation owner ( you can look at LUN properties or look at naviseccli commands). If default owner = allocation owner that i would trespass them back
For every Pool LUN regardless of whether the LUN is thick or thinly provisioned there are 3 owner types assigned to each LUN:
♦ Allocation Owner
♦ Default Owner
♦ Current Owner
There has been cases where inconsistencies in Current, Default & Allocation LUN ownership results in poor performance. Please review the EMC KB88169 written by Dave Reed for more detail.
Jon Klaus goes into good detail on the topic in his post ‘VNX Storage Pool LUN Ownership’
All three owner types need to align with the same ‘VNX Storage Processor’ (A/B) for best performance. If all 3 owners are aligned correctly then there is no need for the system to redirect I/O across the CMI to a peer Storage Processor. This is an example of a best practice LUN ownership configuration as viewable from the LUN properties in Unisphere:
dynamox
11 Legend
•
20419 Posts
•
87439 Points
3115
1
Posted February 17th, 2015 12:00
metadata about that LUN resides on the "original" SP, simply trespassing the LUN to another SP and changing the owner does not move that metadata.