directory /root/tmp/VeeamBackupTemp/

[pirx]

I had some issues with linux fs filling up when I deployed our new linux repos/proxies a few months ago. Today I installed a hotfix an had to remove existing Veeam service and directory. Later I received an alarm that / was filled up 100% (20 GB). I checked it but at that time / had 80% free space again. Now I see that /root/tmp/VeeamBackupTemp/ is growing constantly from 20% in a couple of minutes to 35%. VeeamIndex resync seems to occupy most of the space.

Code: Select all

[root@sdeu4000 veeam]# du -sh  /root/tmp/VeeamBackupTemp/*
2.6M    /root/tmp/VeeamBackupTemp/98260fe1-46a2-cbc0-1888-90e3351cc07d.34552a.7f79d7fff700
925M    /root/tmp/VeeamBackupTemp/VeeamIndexResync_{3d3de43b-a078-4e63-910a-1678c1ad4bed}.32963e.7f362a7fc700
2.5G    /root/tmp/VeeamBackupTemp/VeeamIndexResync_{5e08cbdb-2476-4338-8ef5-50ec4d8b8848}.340cb0.7f9c6a7fc700

I use regkey LinAgentFolder with /opt/veeam as value and /opt/veeam is indeed used for transport agent etc...

Is there any other setting in Linux that might have been removed when I reinstalled new Veeam hotfix? Any other setting I can make to point VeeamBackupTemp to a different location/filesystem?

[Mildur]

Is there any other setting in Linux that might have been removed when I reinstalled new Veeam hotfix? Any other setting I can make to point VeeamBackupTemp to a different location/filesystem?

Best to ask your support case technician, which gave you the hotfix. He can look through the documentation.
It‘s difficult to say which hotfix you have installed without any information about the situation.