Unsolved
This post is more than 5 years old
2 Posts
0
378
February 17th, 2014 12:00
Masking View Maintenance
I have a customer who is using consistent LUN with ESX and Recover Point. We need to separate the masking view into two separate views so we can isolate the RPA initiators. Currently all the ESX and RPA's are in one cluster IG. This is causing issues because the next available LUN address is beyond decimal 256 which is preventing the ESX cluster from seeing any new LUNs.
THe plan is to remove the RPA initiators from the current MV. Then we will create a new MV with the RPA IG and the same SG and PG as the host MV has today. This will be a brief interruption to the RPA's visibility.
Does anyone know what the effect to the Consistency Group will be?
Anyone have a different recommendation on how to correct this issue?
jb_varrow
2 Posts
0
February 18th, 2014 02:00
Thanks.
This was the first option I proposed but was hoping there was a less intrusive way. I appreciate the feedback.
John
Sent from my iPhone
rawstorage
4 Apprentice
•
423 Posts
0
February 18th, 2014 02:00
Have a look at this thread. I've answered a similar question on there
https://community.emc.com/message/781487#781487
rawstorage
4 Apprentice
•
423 Posts
0
February 18th, 2014 02:00
Does anyone know what the effect to the Consistency Group will be?
As long as you are moving host initiators from the initiator group on the shared masking view only the consistency group will be unaffected.
Removing RPA initiators from the masking view will require a full sweep as you will need to disable the consistency group prior to making the changes. See the thread I mentioned earlier, as you are using ESX you will probably have vmotion and a bit more flexibility moving the host initiators.