EV 9.0.1 Sql Server Dell SAN

[SammyC3]

Hopefully an easy one... for someone

In the Sql best practices guide they siggest to turn off offload/TOE/TSO is this only for the windows NIC's or is this for the iscsi NIC's going to the SAN for our DB and Index volumes.

We have had data corruption issues that has force me to rebuild our enviroment. The server was setup before I got here and we had a major melt down...

Thanks

Sam

[AndrewB]

is this a generic sql question or did you find an EV specific reference?

what version of windows and sql?

[JesusWept3 · Accepted solution]

Typically the TCP Offload Engine (Chimney or whatever) should be disabled on the SQL Server and whatever is accessing it, so like EV Servers and DA Servers.

I seem to remember it causing an issue with applying legal holds correctly , and its like the Opportunistic Locking where you have to disable it on source and target (where possible)

[JesusWept3]

But simply put, turn it off everywhere that you can turn it off

[SammyC3]

I apologize I havent even turned back to this since I started but will continue as I wasnt to make sure its noted for someone else down the road.

@Andrew

EV Server 2003 R2

EV SQL 2008 sp2

SQL 2005 32 bit sp2

This is an EV specific question. In the EV 10.0 SQL best practices guide under Network considerations

We recommend that the Enterprise Vault SQL servers and Enterprise Vault servers are connected via gigabit network technology. The SQL servers may require multiple network interface cards to support the anticipated loads.

It is also recommended to disable the TCP Chimney Offload, TCP/IP Offload Engine (TOE) or TCP Segmentation Offload (TSO) to prevent network issues. For guidance in disabling these, see Symantec technical article

TECH55653.

I guess my question is does this matter for the ISCSI storage to the SAN? Or is this only regards to the network on the LAN side?

I did what JesusWept3 suggested before I came back to this article. So far so good but I'd like confirmation.