by cobra » Fri May 15, 2015 12:36 pm people like this post
I use Veeam 184.108.40.2061 on a Windows Server 2008R2.
Backup of VMs works perfect.
When veeam starts a filecopy job, the lsass.exe process goes high on CPU / RAM. CPU is 100% and all goes very slow. The job take files of an Server an copy it to an NAS, which is over iSCSI connected to the server, on which the veeam runs.
by Shestakov » Fri May 15, 2015 1:01 pm people like this post
Hello, In general the lsass.exe (Local Security Authority Subsystem Service) is there to handle enforcing the security policy, verifying User logins, creating access tokens, etc. It should not take lots of CPU resources. Sometimes, however, viruses also use the name. The real lsass.exe should be in C:\Windows\System32. Please check the path. Thanks.
by adrianIDC » Tue May 26, 2015 2:39 pm people like this post
cobra wrote:When I copy the data manual (Windows Explorer), all is working fine.
I test today, what happens, if I select another destination.
I had the same symptoms and eventually gave up . Copying the same files using Windows Explorer took much less. If many files are located in sub / sub / sub folders takes even more since B & R need to do a little analysis for each .
by Shestakov » Wed May 27, 2015 2:56 pm people like this post
Adrian, do you also observe lsass.exe service consuming lots of CPU resources? In general, you are correct copying huge number of small files for filecopy and file-to-tape jobs is a struggle for now. Try to archive the files and see if the job will work faster copying a single archive file. Thanks!
by Shestakov » Thu May 28, 2015 11:53 am people like this post
Adrian, could you open a support case and share your logs with us? It can help us investigating the issue with file copy job. Once you do, please post your support case number. Thank you for the feedback!
by stoon41 » Tue Jan 26, 2016 9:41 am people like this post
Was this issue every resolved? I'm getting exactly the same. Lsass.exe consumes CPU and RAM while running and after a file copy job. This job is only 44GB but over 70,000 files. Veeam version 220.127.116.114
by Shestakov » Tue Jan 26, 2016 10:20 am people like this post
Hello Steve and welcome to the community! Unfortunately we don`t know results of the issue investigation since OP has not posted the case number. You may try to write him a private message. But the "issue" looks generic. Upgrading to v9 may help a bit here. Thanks!