Veeam Satellite Process is not cleaned up

[Talom]

Hey Guys,

yesterday i noticed, when i'm cancelling my powershell script with CTRl+C the corresponding Veeam.Backup.Satellite process won't be killed.
My reporting scripts are sometimes cancelled automatically because of timeout or something else and after a few weeks i have a lot of satellite processes that are stuck in the task manager.
After a while my scripts just fail because of too many existing processes

Is this a bug in Veeam or can i write a cleanup script which cleans up unused satellite processes?

[veremin]

Actually, the said process should have a pre-defined timeout (around 5 minutes, if I'm not mistaken) after which it should be killed. If you see a lot of stuck (not killed) Satellite Process, kindly, reach our support team for further investigation.

Within a ticket you can point out that the problem is not directly related to PowerShell, as support team do not take over tickets regarding non-working scripts, etc.

Thanks.

[yurixd]

Hello friend, I'm having this same problem in version 9.5. When running multiple jobs the Veeam.Backup.Satellite.exe process appears in excess, causing backups to fail.

when I finish these processes in the task manager the backups do again.

Have you come up with any solutions to this problem?

[yurixd]

Case # 02197424

Hello friends, the above case was initially referring to a warning message in the SQL and Oracle transaction log.

After a period began to occur in the job of backups where the engineer when analyzing my server found that there is memory leak in veeam, which is causing failures in backup jobs.
I also noticed that in some cases the veeam console is inaccessible on the server, it is necessary to restart the veeam service backup or to restart the server itself.
When I look at the task manager, I see excessive numbers in the Veeam.Backup.Sattelite process. By killing all processes leaving only 1 the backup job returns to normal operation.

Anyone have any suggestions on the problem? I have to daily run the backups by hand due to failure.

**it seems to me that the Veeam.Backup.Satellite process is finished in 5 minutes. something that is not happening.

[veremin]

Hi, Yuri,

Please, let's wait and see what support team says about the issue, once the debug logs are investigated.

Thanks.

[JRJenZen]

Any News On This, i'm an SP and we have hundreds of these causing customers backup to fail.

[veremin]

We've identified the root cause of this problem. The hotfix is currently being tested.

Since you're an SP, kindly, apply to Veeam Cloud Provider group, using Usergroup settings in the User Control Panel. This's needed to get access to dedicated cloud providers' forum. That is likely to be the first place where we will share news regarding hotfix availability.

Thanks.

[rntguy]

we are getting the same issue. one customer's backups now failing. they don't copy up to the cloud though. where can I get the hotfix?

[FCa]

Hello,
We are also getting the same Issue.

Killing all " Veeam.Backup.Satellite" processes & rescan the Veeam Backup Server temporarly solve the issue...
Could we get a Script that kill all processes except one, so we can schedule it hourly the time for Veeam Dev to fix this bug ?

[Vitaliy S.]

Fabien, to receive the hotfix for this problem, please contact our technical support team directly using cp.veeam.com

[sleti]

You can proceed in the following way:
Modify PS script: add Connect-VBRServer and Disconnect-VBRServer You must use this commands to close PowerShell session and finish satellite process
Restart Veeam server.
Monitor server and satellite processes.
If you still see multiple satellites – collect fresh logs and PS script for further investigation by the technical team.

[veremin]

The easiest way to get this issue fixed is to open a support ticket; which I recommend to everyone experiencing the similar problem. Thanks.

[seamusobr]

I am also seeing this and having to clear down 50 of these processes daily does anyone know if there is a hotfix for this?
We are a bit reluctant to scale beyond the single client we have at the moment until we get a fix

[Vitaliy S.]

Seamus, please contact our technical team for assistance with this/fix.

[mma]

Case # 02620437

Does this fix also help on not powershell triggered jobs?

[Vitaliy S.]

AFAIK this was related to PowerShell only, but you'd better to double-check with your support engineer.

[DMIT]

I am Veeam Service Provider and noticed the issue when backup agents were unable to connect to our cloud repository - error "Backup Repository is inaccessible". Creating a scheduled task with the the following " Taskkill /im veeam.backup.satellite.exe /f" works perfectly.

[Vitaliy S.]

Thanks for the post, Jeff! This temp workaround indeed should solve the problem until the hotfix for this issue is provided.

[Vitaliy S.]

Quick update: hotfix for this problem is available for download from our support team.

[StoneFritz]

Hello, I have the same problem even with the hotfix installed.

[Vitaliy S.]

Please let our support team know about this to verify the reason for this issue.

[StoneFritz]

The support is currently looking at the case with me.

[KeyInfo]

We have multiple (63) Veeam.Backup.Satellite processes on our veeam B&R server. Is that normal? If its not, should i periodically stop the processes?

[Vitaliy S.]

There should be a hotfix available to resolve that. Please contact our technical support team.

[tpayne]

I too have applied the hotfix provided by support and am still having satellite processes not being cleaned up. I have gone back to running the scheduled task that kills them every 6 hours... Just to compare with others applying the hotfix, is it labled "Fix_123620_83ea8ab698"?

[StoneFritz]

I have gone back to running the scheduled task that kills them, too.

[KeyInfo]

We disabled it and now were getting multiple errors that are listed below. Veeam support dont know what the issue is either.
Waiting for backup infrastructure resources availability
Some VMs were not processed during the copy interval

[Vitaliy S.]

Tim, StoneFritz what are your latest support case IDs?

[tpayne]

02957644

[Vitaliy S.]

Thanks, I will ask our QA team to take a look at your particular situation. It appears that there are different scenarios when this behavior can be observed and our support team would like to review them all.