Veeam Commands in bash_history

[ZdenekT]

Hello,
I have backup repository mounted on Linux server. Suddenly this started appearing in bash_history of the server:

For example, during backups, rescan of repository etc.

/tmp/VeeamAgent551c6ef8-4c77-4641-9ebd-f508d3c36a81 -l flush,/var/log/VeeamBackup/TestJob/Agent.TestJob.Target__cli.log,/tmp/VeeamBackup/TestJob/Agent.TestJob.Target__cli.log -i 8df783ff-bc7b-43cf-9376-e067bdedc891 -g 2500-5000 --setFileLimit 4096 --mgmtConnKey AQAAAAAAA
/tmp/VeeamAgent6e59afb2-d2ca-4893-b508-ec45e089b962 -l flush,/var/log/VeeamBackup/Utils__DatabaseResynchronizer/Agent.VbkManager__cli.log,/tmp/VeeamBackup/Utils__DatabaseResynchronizer/Agent.VbkManager__cli.log -i 23fc7144-dd1a-463f-81b6-2ed3b7a000b0 -g 2500-5000 --setFi
(cd /tmp && perl veeam_soapc70a59e7-1ccb-4733-855e-ad8e1d01a8e6.pl -d -c -l libc70a59e7-1ccb-4733-855e-ad8e1d01a8e6 -e /tmp/veeam_errorc70a59e7-1ccb-4733-855e-ad8e1d01a8e6 2>> /tmp/veeam_errorc70a59e7-1ccb-4733-855e-ad8e1d01a8e6) || cat /tmp/veeam_errorc70a59e7-1ccb-4733

Any experience with this, please?

[HannesK]

Hello,
and welcome to the forum.

that looks normal for me. What is your question?

Best regards,
Hannes

[mikeely]

For us it interferes with normal use of the "history" command, because the normal and expected output of that command is blown out with all the spam as listed above. $HISTFILESIZE is typically only 1000 or 2000 lines, and with a single backup job dumping several hundred lines of utter garbage into .bash_history the ability to use that command is greatly impeded.

I'm well aware that this can be remediated by setting environment variables in authorized_keys but doing so should be in the default setup docs.

[Gostev]

v11 should practically eliminate these as a side effect of the architecture change, since our components are now persistent and SSH is only required for deploying and upgrading them.

[mikeely]

I'm glad to hear that, but how is this architecture change going to work in terms of new firewall rules to add?

[Gostev]

It should not be significantly different from before, as the components are still the same... except they were runtime before, and with v11 they will become persistent. May be one extra command port, if we did not have one before due to SSH usage? It will all be documented, of course.

[mikeely]

Alright. Just keep in mind, any firewall changes at all can be a massive workload amplification for what would otherwise be a routine update. I'm one of those people working in an environment where I have to deal with three different departments depending on who owns the firewall in question and do not love having to add rules.