- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Initiator group cleanup - Best practice
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-28-2015 04:53 PM
07-28-2015 04:53 PM
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?
Thanks,
AB
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-05-2015 08:54 AM
10-05-2015 08:54 AM
SolutionHi 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!
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP