Avoid use of /tmp folder

[ssandoz]

Hi,

I backup Linux servers with VAL.
Internal policies do not allow the use of /tmp folder.

I already moved Index information to another location by changing settings in /etc/veeam/veeam.ini

However, I noted that during the backup process, a temporary folder like {XXXX} is also created and deleted at the end of the backup process.
Is there a way to completely avoid the use of /tmp folder by Veeam?

Thanks in advance for your feedback.

[HannesK]

Hello,
as of today, we use /tmp for some temporary data. We work fine with noexec on /tmp.

What is the background of not using /tmp? I mean, the purpose of /tmp is storing temporary data.

Best regards,
Hannes

[ssandoz]

Hi,
The root partition has a limited free space available and when a backup is processing, the temporary {XXXX} folder triggers an alert that no more space is available.
That disturbs other processes which run over the night and use /tmp.

I saw that it can be possible to completely prevent the use of /tmp by adding a LinAgentFolder registry key. The key should be placed in HKLM\Software\Veeam\Veeam Backup and Replication registry branch.
Can you give me more information about this possibility?
Thx in advance.

[HannesK]

Hello,
yes, there is LinAgentFolder and LinAgentExecutableFolder (REG_SZ)

LinAgentExecutableFolder is for agents managed by VBR (which I expect you use). I tested it yesterday before posting and there is still a small amount data in /tmp (no idea how this can fill up the disk)

That both keys are about deployment and we changed it to /opt/veeam some versions ago. If you use the keys, keep in mind to not put a trailing slash in the path.

Best regards,
Hannes

[PTide]

In fact, we were asked to introduce the reg.keys exactly because Veeam did not work fine with noexec flag set on /tmp, and I really doubt that our binaries can override the flag (otherwise that would be a fat bug in linux).

[ssandoz]

Thanks a lot for your feedback.
So if I understood correctly these reg.keys are used to avoid use of exe (installation and rescan) in /tmp.
But even with these reg.keys, veeam create this temporary {XXXX} folder in /tmp.

[HannesK]

correct.

[ssandoz]

Hi,

I backup a physical Linux server using VAL.
Users reported activities in the /tmp folder by VEEAM.

- I know VEEAM is using /tmp to store indexing data.
- During the backup process, VEEAM also creates a temporary folder like {XXXXX}.

2 questions:
1/ What VEEAM exactly does with this {XXXX} folder? Can this folder use a significant amount of space during the backup process?
2/ Does VEEAM use /tmp for any other purpose?

Thanks in advance for your feedback.

[HannesK]

Hello,
I merged your question to the existing thread.

We store temporary data in /tmp (that's the purpose of /tmp).

If you observed significant amounts of data (not sure what "significant" means), can you please post the case support case number with debug logfiles and more details?

Thanks,
Hannes

[PTide]

Is your VAL managed by VBR or it's a standalone installation?

Thanks!

[c.schulzejn]

As VAL needs free space somewhere for that data - what about a pre- und a post-script mounting a directory below /tmp for backups?

[PTide]

It's not just for data that is generated during a job run. It's also for data that is generated during agent deployment (if deployed from VBR), so it might be generated even if no jobs (hence no pre/post-scripts too) are present.

Thanks!