if you are going to boot from SAN and you only have one set of HBAs then you would do example 1. Where each server has its own storage group where first LUN is the boot LUN for that specific host and the rest of the LUNs are shared between other hosts.
If you are booting from local disk/storage then Example 2 is the easiest one to manage, you simply create one storage group, add all clusters members to it and then add shared LUNs.
In order to take advantage of the clustering features in vCenter like vMotion or Storage vMotion, you must have shared storage visible to all ESXi hosts. So as you have given the example, option 2 is your best choice.
Also - you must ensure that all switch zoning is correct so that there are redundant paths to each ESXi host.
dynamox
9 Legend
•
20.4K Posts
0
July 15th, 2015 17:00
if you are going to boot from SAN and you only have one set of HBAs then you would do example 1. Where each server has its own storage group where first LUN is the boot LUN for that specific host and the rest of the LUNs are shared between other hosts.
If you are booting from local disk/storage then Example 2 is the easiest one to manage, you simply create one storage group, add all clusters members to it and then add shared LUNs.
bonetsm
8 Posts
1
July 16th, 2015 00:00
Since you are booting from local mirrored SD cards, example 2 is the recommended configuration.
RoadKing2413
4 Posts
1
July 16th, 2015 04:00
In order to take advantage of the clustering features in vCenter like vMotion or Storage vMotion, you must have shared storage visible to all ESXi hosts. So as you have given the example, option 2 is your best choice.
Also - you must ensure that all switch zoning is correct so that there are redundant paths to each ESXi host.
Gary_P1
6 Posts
0
July 16th, 2015 07:00
Thanks everybody for the responses they were very helpful.