EV 8 - Index on iSCSi LUN?

[citizen]

I am building EV8 on a Windows 2008 x64 cluster of 2 physical boxes.
I was told that the index storage locations should not be on iSCSi LUNs is this true?
Am I OK using iSCSi LUNs or do I have another option?

Currently I configured the storage as NFS but according to Microsoft, MS clustering requires I use either fiber channel (too expensive) or iSCSi and it won't let even see the NFS storage to configure for clustering. I will keep researching but I don't know another option.

In the mean time we are quickly running out of storage......Help Help!!

Thank you!! Thank you!!

[John_Chisari]

 I don't see any reason why having iSCSI Luns as Index storage locations should not be used.

[Liam_Finn1 · Accepted solution]

Agreed as long as you have a high quality Ethernet switch there should be no issue

I would however recommend that you put the iSCSI on it's own VLAN to ensure that nothing can affect the traffice between the LUN and the server

[AndrewB]

Been doing it this way for years. Works like a charm.

[citizen]

Thanks everyone!

[Liam_Finn1]

 If you found your solution please vote on it and also mark it as solved 

[Ryujin]

Check out the EV compatibility list for authoritative details on this.

I have spoken with Symantec back end engineers about this subject as well. Symantec recommends block based storage for the indexes over file based. This can be either iSCSI SAN or FC SAN. Because of the nature of the index you really want to have it as responsive as possible. I have placed production EV indexes on CIFS. We eventually switched FC to follow our IT infrastructure standard. In both the iSCSI and CIFS scenarios the storage was NetApp, with the DFM (Data Fabric Managment) agent to give performance statistics. If you use iSCSI just make sure you have high performance switches and a dedicated VLAN.

^_^