some weeks ago, I received a call from a collegue with the information that his local disk was full - which surprised me. TreeSize immediately mentioned the culprit - the veeam agent. Looks like that the job.log has generated an insane amount of data (>70 GB!!) which has filled the disk. Now of course, I don't have the file anymore (cause I had to delete it immediately to free up the disk) but it looks like that there's something wrong with the code here - or at least the check "am I too big" is missing.
That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be deleted by moderators.
Rovshan.
Rovshan Pashayev
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
Yes Rovshan, thanks, this is a technical issue. But is it possible to have an investigation if the file isn't persist anymore? I mean you can't really investigate the crime if the crime scene is gone...
I suggest that if the issue occurs again, you should zip the log file and move it to a different location instead of removing it. This way, you can submit the zipped log file along with the case for further analysis.
Rovshan
Rovshan Pashayev
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
