Long winded, so hopefully I included everything in this post since I already accidentally closed my window once!! :(
We have been going back and forth with CommVault support with no fix yet and seems we have a tech that can not get his responses straight. We have been having lock ups on our file shares from our file server. It is caused by recalls of CommVault and when I turn the services off, it resolves it till it gets to a certain point again then it starts all over.
They want to go by what this https://ma.commvault.com/KB/Details/11411 document says to do. Which is this below:
"You mentioned that stopping the CommVault services on the client alleviated the resource issue. Due to that and the fact that the client is running Windows 2012, we recommend that you disable SMB 2.0 on the client, fs1, by using the following registry entry. This will force any clients doing recalls to use Windows 2012's native SMB 3.0.
1. Click Start, type regedit in the Start Search box, and then press ENTER.
2. Locate and then click the following registry subkey:
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type SMB2, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type 0 (zero), and then click OK.
7. Exit Registry Editor.
8. Restart the computer."
Basically they want us to turn off SMB 2.0 on our File Server which runs Windows 2012 R2. By doing this, which he was wrong above, this turns off SMB 2.0 and 3.0 and will force clients to use 1.0. This will cause us to lose a lot of new features, and have some of the bugs that were associated to 1.0 come back.
After discussing this with management, we do not agree with this and even MICROSOFT says in this WARNING, only turn off SMB 2.0 for testing purposes. https://support.microsoft.com/en-us/kb/2696547
This issue they have they continue to blame Microsoft for and it's a CommVault related issue which is proven in the following threads.
http://forum.commvault.com/forums/thread/26791.aspx and https://forum.avast.com/index.php?topic=62136.0
When Commvault is having issues with other applications are having this issue with CommVault what is the common dominator? CommVault is. We use Microsoft End Point Protection, and we can not turn this off as we are a Financial Institution and must protect our file servers from harm.
So at last, they said we need to push this KB fix to our workstations if we don't want to do the server. But when I question him on this line in that KB, he continues on the same lines as we need to push this to the clients.
"Note You need to apply the hotfix package on the computer which shares files."
That tells me right there it needs to be applied to the FILE SERVER that is hosting the shares and not the clients.
What do you guys think? We need a resolution or we are just turning off Archiving and finding another product.