Linux guest processing leaves VeeamApp file in /tmp

[signal]

During backup using Guest processing of a Linux server there is an upload of a file (new each run) to /tmp named VeeamApp<random <8>-<4>-<4>-<4>-<12> [0-9af] chars>. This is an executeable that will not be run as /tmp is mounted noexec. I see no attempts at running the file. After the backup completes this file is left behind, and no attempt at deleting it is performed.

I have test-run the file from another path and it looks like it's an Oracle agent, even though the system has no Oracle installed.
Disabling database processing does not help. The file is still uploaded.

Is there some part in the backup process where this would be removed automatically?

The Linux system is locked down tightly, security wise.

[Dima P.]

Hello signal.

Indeed this is a small file that seeks for the Oracle components, but it must be deleted automatically. Thus, please submit a support case and share the case ID. Thank you.

[signal]

Thank you for the feedback. Further testing revealed a solution.

It looks like there was no attempt at running the file, or it failed. That must have stopped the rest of the process from running and the file was never deleted.
Adding the LinAgentFolder setting in registry (found another post on this here) and creating a folder owned by the service account/group with chmod 770 let this run and the files are removed as they should.