Environment: 1x Production, 1x DR, 1x UAT and 1x Dev: All Windows Server 2016 Nodes
Is it normal for
symcscan.exe to keep creating new process handles until the CPU and RAM are at maximum capacity? Is there a known root cause for this as we're seeing the same on multiple servers with very little end user activity. Approximately 5MB has been scanned in one month but we are routinely needing to restart the services to make sure the servers are responsive. The number of end users is probably around 20-50 and the average files' scan size is small (< 1MB).
Servers tend to start grinding to a halt with a couple of million(!) handles open through the symcscan process.
Please assist.
------------------------------
Barclays
------------------------------