Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 812
  • Last Modified:

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
0
qz8dsw
Asked:
qz8dsw
  • 2
1 Solution
 
qz8dswAuthor Commented:
OK, found out some more info.
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.
0
 
qz8dswAuthor Commented:
Confirmed this is a resolution for our issue.
The handles lsass.exe was holding onto were user tokens going back to an ad account SQL server 2008 uses (Found by using handles.exe from sysinternals/microsoft).

I spose my question has now changed slightly since I have found resolution to the initial issue.

Why would lsass hold onto these resources and continue to build them up for what is in essence an access denied on deleting a file. (SQL Server trying to purge old transaction logs)

Any insight would be appriciated.

Cheers
Terry
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now