/var/tmp getting filled up by VeeamAgent?

[it_rc]

::edit (with fix!)::

The solution was, for me, anyways, to remove my NAS as a managed server from VBR. I initially had it as both a backup repository and managed server, but was using for neither, so when I removed it as a managed server, those files stopped being produced.

::end edit::

My Freenas box is used for a number of things, one of which is as a target of a single physical machine using the VeeamAgent. However, yesterday I noticed that the /var/tmp directory was full (5gb) of files named "VeeamAgent2a24e31a-01d2-4842-9793-7b518821bfcf" where everything after "VeeamAgent" was different and each file was exactly 21281560 bytes (~21 MB). I tried to view it with cat but it looks to be encrypted. Plus, the timestamps are at precisely every 4 hours but none line up with the times my backups run.

Has anyone seen this before?

 

[Mlovelace]

To answer your question, no I've never seen anything like that before, and I've been using several freeNAS servers as storage repos for Veeam B&R as well as Veeam Agent for 6+ years now. What version of Veeam Agent are you using and what protocol are you using to present the storage to the physical box?

 

[it_rc]

Veeam Agent is current: 2.2.0.589 (free version)
Freenas is presented via SMB/CIFS

 

[Mlovelace]

Veeam Agent is current: 2.2.0.589 (free version)
Freenas is presented via SMB/CIFS

Well the current Veeam Agent for Windows is 3.0.1.1039

I would say clear out the tmp folder, upgrade to the latest version and run a backup and see if it happens again. I suspect freeNAS is writing some sort of session information/errors to the tmp folder, but I would also consider opening a bug report.

 

[it_rc]

Well the current Veeam Agent for Windows is 3.0.1.1039.

Well I'll be.... I was going off of the "about" section of my install and it said it was up to date and didn't even think to consider the fact that it maybe wouldn't do major version upgrades. I'll give this a shot. Thanks!

 

[Mlovelace]

Well I'll be.... I was going off of the "about" section of my install and it said it was up to date and didn't even think to consider the fact that it maybe wouldn't do major version upgrades. I'll give this a shot. Thanks!

Yeah, the internal update function goes off the current version. Same thing happened when they went from 1.x to 2.x. You can track updates and versions on their community forum. It's worth checking periodically.

 

[it_rc]

So the upgrade did not help but I was able to somewhat replicate it by power cycling the server running the agent. It writes the file quite fast so it's thus far difficult to catch what is creating it. Off to the Veeam forums I go.