Filecopy: lsass.exe CPU / RAM very high

[cobra]

Hello,

I use Veeam 8.0.0.2021 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.

Someone knows this problem?

Greetings

[Shestakov]

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.

[cobra]

Hello,

the path to the lsass.exe is right.

The CPU goes up, after the file copy is started.

Greetings

[Shestakov]

That`s strange.

Could you specify how many files and their size are you copying? What`s the source and destination?

Have you tried to reboot the server? It looks like a random Windows bug. Thanks.

[cobra]

Hello,

I boot the server two times. I run the job 2 times, and 2 times, the error appiers.

The source is a shared folder on a physical Server. The destination is a NAS. The NAS is connected over iSCSI on the physical server, on which Veeam is installed.

I copy 400GB of data. Some data is very small (dokuments,...), the rest are setup files, ISO Images of DVDs,...

Greetings

[veremin]

If you try to copy those files manually without VB&R presence, do you the issue re-occurs?

[Vitaliy S.]

Also can you please try to use anther destination target to see if this issue reproduces or not?

[cobra]

When I copy the data manual (Windows Explorer), all is working fine.

I test today, what happens, if I select another destination.

[adrianIDC]

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 .

[Shestakov]

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!

[adrianIDC]

Yes, I analyzed that when there were few files or a large file (.iso for example) if that copied much faster .

As I said at the time, nor is it so important this section because I care more related to the backup B & R; )

[Shestakov]

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!

[stoon41]

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 8.0.0.2084

regards Steve

[Shestakov]

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!