Hi, I managed to work it out. Thanks though.

So, looks like login as batch file seems top have fixed it.

If you go into the cluster management console. It's the bottom tab.

If you are using a SAN I doubt it will honour what you set in windows either way. Even most array controllers will ignore this Windows setting as you have...

For one or two drives to cause the significant of a performance hit I'd suggest your SAN needs some sort of firmware upgrade. One or two disk failures should go...

You only want/need to do one backup you just need too do two restores. So backup DB logs to network share and have the two other servers both restore from...

You might be best to destroy your second cluster and setup a geo-cluster now called multi site clusters in Microsoft speak. Assuming your storage vendor has the required plugins and...

So you've setup two completely independent clusters not a geocluster?

Wow, in a modern SAN that is a significant performance hit from 1 failed disk.

Pretty much every SAN now in the mid-high end range use disk pooling technology and fancy virtual raids to stripe data as wide as possible. Most will want to stripe...

What backup tool are you using? I'm pretty sure if it's VSS compatible it should work.

My understanding of lockpagesinmemory is that it means SQL will not yield the memory back to the OS if it needs/requests it. Setting max server memory just caps the amount...

Sometimes hardware just doesn't fix the issue though. We have a vendor app that is under performing we can't do anything to the DB or code as we upgraded from...

Should help. I think the Tempdb fixes were in SP2 CU1 or 2.

http://www.brentozar.com/archive/2014/04/memory-ssd-tempdb-temp-table-sql-2014/

Are you running SQL 2012 SP3? there are significant performance improvements to tempdb in CU since SP2 was released.

This is a free solution that is worth testing to see if...