Array Performance and Data Protection
Showing results for 
Search instead for 
Did you mean: 

Initiator group cleanup - Best practice

Go to solution
Occasional Contributor

Initiator group cleanup - Best practice

Hello everyone,

We have multiple initiator groups - some old custom, some new, and out of the box names.  I would like to clean this up to just a few.  For example, VMFS01-09 can only be access by Non-SQL hosts and SQLVMFS01-09 can only be access by SQL hosts, etc.  Right now, we have several volumes in a ESXHost0001 init group that both Non-SQL host and SQL hosts can access. 

What is the best way to do this without impacting our VMs?  What do I need to take account before the cleanup?



Valued Contributor

Re: Initiator group cleanup - Best practice

Hi Alex,

You can absolutely accomplish this without affecting any of your VMs. If I understood you correctly, you need to move some volumes's ACLs from ESX0001 (vcenter created igroup) to VMFS01-09 igroup and another set from ESX0001 igroup to SQLVMFS01-09 igroup. The easiest way to accomplish this is to go to each of the volumes in the array GUI, click "Edit" and navigate to the "Security" tab on the right. This will have a listing of all the ACLs for that volume. You can add the new and correct ACLs and remove the ESX0001 ACL from the list. This will ensure that going forward only the right hosts will be able to detect those volumes. Word of caution, though. Before you make these changes, make sure the hosts that aren't supposed to see the volumes have them disconnected. Otherwise you'll have hosts looking for volumes they can no longer access.

Hope this helps!