Agent for Linux, large index data on root disk

[sandsturm]

We use veeam agent for linux in managed mode via VBR console with the most current version of VAL. We often see the issue on different machines, that veeam agent creates a lot of index data within /tmp/veeam with 5GB or more. These files fill up the root disk and we often get alerts and have then to increase the diskspace. We try to not have such services writing to root disk excessively, if possible. What are the option we have in this case for the veeam agent?
- is it possible to save these index file into another path/another disk?
- is it possible to disable this index creation and what would be the effect of that?

thx
sandsturm

[PTide]

Hi,

Not sure that I fully understand what kind of files you are seeing. What are the names of those files?

Thanks!

[sandsturm]

Hi

These are the mentioned files:

[user@servername veeam]$ pwd
/tmp/veeam
[user@servername veeam]$ ls -la *
total 13436
drwxrws--- 2 root veeam 6 Feb 17 21:51 _
drwxrwxrwx 8 root root 286 Mar 28 21:51 .
drwxrwxr-x 3 root veeam 19 Mar 28 21:51 ..
drwxrws--- 2 root veeam 6 Feb 17 21:52 _boot
-rw-rw-rw- 1 root root 1887478 Mar 28 21:51 GuestIndexData.tar.gz
drwxrws--- 2 root veeam 6 Feb 17 21:52 _home
-rw-r----- 1 root slocate 5984 Mar 28 21:47 mlocate._boot.db
-rw-r----- 1 root slocate 7295136 Mar 28 21:51 mlocate._.db
-rw-r----- 1 root slocate 4053219 Mar 28 21:47 mlocate._home.db
-rw-r----- 1 root slocate 433295 Mar 28 21:47 mlocate._opt_hds.db
-rw-r----- 1 root slocate 26934 Mar 28 21:47 mlocate._var_log.db
-rw-r----- 1 root slocate 40384 Mar 28 21:47 mlocate._var_tmp.db
drwxrws--- 2 root veeam 6 Feb 17 21:52 _opt_hds
-rw-rw-rw- 1 root root 203 Mar 28 21:51 summary.txt
drwxrws--- 2 root veeam 6 Feb 17 21:52 _var_log
drwxrws--- 2 root veeam 6 Mar 24 21:58 _var_tmp

thx,
sandsturm

[PTide]

Those files contain information that allows for incremental indexing.

- is it possible to save these index file into another path/another disk?

Not possible to change that location for index data only. You can change location for all auxiliary files from /tmp to some other location:

1. Open /etc/veeam/veeam.ini

2. Go in [core] section

3. Add/change the "tempFolder" parameter

Example:

Code: Select all

[core]
tempFolder = /opt/tmp = /opt/tmp

- is it possible to disable this index creation and what would be the effect of that?

Yes, it is is possible.
Without indexing enabled you will not be able to search and pick for a file to restore without mounting a backup first. With indexing enabled, you can use EM to search for files across many backups without having to mount them.

Thanks!