how to not store any temp. files in %UserProfile%

[pirx]

This happend now the second time in a few weeks. I need to create a log bundle, I do this from a windows terminal server where I start the console. Logs on VBR server are located on D drive for a good reason. But Veeam created ~80 GB of temp data in the service user appdata path (C:\Users\service-user\AppData\Local\Temp\VeeamLogs_f96ab8b41abb42a4a574851388bc6e89) which then filled up C drive. I probably could move all the profiles to D but there should be a different way to define where temp data is created. We had similar issues with the C:\windows\temp location and IIRC it can also not be changed.

[david.domask]

Hi pirx,

Just to confirm, you followed https://www.veeam.com/kb1832 and set the registry value to set the default log directory, correct?

Can you maybe share a screenshot of the path that's being made in %temp% (with the full path visible)? If I remember right it's just using the %temp% variable, but a quick test checking %temp% for changes during a log export and nothing was written to %temp%, but this was from the VBR server directly. Do you see the same behavior if you export from the VBR server itself?

[pirx]

LogDirectory is set to d:\Veeam\Logs. That's working for years now. But there are other things in Veeam that create temp. files in other locations on VBR server. In current case its the creation of a log bundle on a different host that triggers the creation in AppData\Local\Temp of the Veeam service user on VBR host. We had other functions (Veeam One VID) that create files in other locations.

[Ivan239]

Hi, You can set the registry key LogExportPath (string \ path) on VBR server.

[pirx]

That's great and works! Interesting that I had a case weeks ago where support also was puzzled why temp data was created in users %appdata% but had no solution for creating it elsewhere. I think its also not mentioned in one of the KB articles (helpcenter: We could not find any results matching "LogExportPath").