LSASS High CPU and Memory Utilization
Hi all,
We have a very curious issue with a Windows 2008 R2 SP1 box (NOT a DC).
In essence lsass seems to be leaking handles and memory.
It goes through periods of high cpu (25% on a 4 core box, so 1 complete CPU).
I have managed to isolate the timing of these periods of high CPU usage down to one event, SQL Server backups.
In investigating this I stumbled across http://www.sqlservercentral.com/Forums/Topic1341522-391-1.aspx and sure enough we did not have the hotfix applied referenced in that (http://support.microsoft.com/kb/2545833). So that was applied last night and I put in performance monitoring on the lsass process.
Come this morning we still get CPU spikes every time SQL backups are running (transaction log backups every 15 minutes) and lsass is currently using 325,000 handles and 191,692K. From my performance stats I could see the gradual increase overnight.
SQL Server itself is suffering with it's transaction logs backups going from taking seconds to complete to now taking over 15 minutes.
Any insights or advice would be appreciated.
Cheers
Terry
We have a very curious issue with a Windows 2008 R2 SP1 box (NOT a DC).
In essence lsass seems to be leaking handles and memory.
It goes through periods of high cpu (25% on a 4 core box, so 1 complete CPU).
I have managed to isolate the timing of these periods of high CPU usage down to one event, SQL Server backups.
In investigating this I stumbled across http://www.sqlservercentral.com/Forums/Topic1341522-391-1.aspx and sure enough we did not have the hotfix applied referenced in that (http://support.microsoft.com/kb/2545833). So that was applied last night and I put in performance monitoring on the lsass process.
Come this morning we still get CPU spikes every time SQL backups are running (transaction log backups every 15 minutes) and lsass is currently using 325,000 handles and 191,692K. From my performance stats I could see the gradual increase overnight.
SQL Server itself is suffering with it's transaction logs backups going from taking seconds to complete to now taking over 15 minutes.
Any insights or advice would be appreciated.
Cheers
Terry
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
ASKER
The backup drive for SQL backups had recently been replaced. When they replaced it they copied the files, but not the permissions. SQL did not have access to delete old transaction logs.
This has now been rectified and am waiting to see if this is a resolution to our problem.