A few months ago the memory used by lsass.exe started to grow from 50MB (with BE services disabled) to over 1.5GB in a a matter of weeks, until the server becomes unresponsive and must be restarted.
The issue seems to be caused by Symantec Backup Exec 11D and even if we upgraded from Rev. 6235 to Rev. 7170 and applied the SP5 and HotFix 70, the problem was not solved.
In the Event Logs the only errors associated with the backups are:
----------------------------------------------------------------------------
Source: VSS
Event ID 6013
Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80004005. SQLSTATE: 08001, Native Error: 18
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.
Source: Backup Exec
Event ID 57860
An error occurred while attempting to log in to the following server: "server".
SQL error number: "0012".
SQL error message: "[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.
".
----------------------------------------------
Stopping or restarting the Backup Exec 11D services will not release the lsass.exe memory and the server must be rebooted to avoid a lockout and subsequent AD/Exchange services unavailability.
Every time a backup job is performed (note that all backups are successfully completed) the increase in the memory used by lsass.exe is in the 100MB to 200MB range.
The Windows 2003 SBS Standard R2 server is 5.2.3790 Service Pack 2 Build 3790, has 4GB RAM and recommended updates and hotfixes installed.
Any solution to solve this issue is appreciated.
