VeeamVixProxy log

[averylarry]

On at least 1 of my servers (which is not a Veeam server or proxy server), since 9/3/2013, the VeeamVixProxy_date.log file is anywhere from 13 to 65 Mb (each day's log file). Prior to that, they were less than 256 Kb. I've got 5.5 Gb of log files now, and I just wondered if there's a setting or something related before I bother with a tech support case . . .

[Gostev]

There is definitely a support KB that lists all the registry keys related to debug log control. I will try to find it when I make it to proper PC.

[Vitaliy S.]

Here you go - http://www.veeam.com/kb1825

[foggy]

And here's a huge existing topic on log files management.

[b.vanhaastrecht]

Hi, I''m also having problems that guests logs are filling with the "VeeamVixProxy" logs. The settings in the knowlegdebase doenst seem to apply to these VIX logs.

We are using VIX alot because we are using vCloud without network access from proxy to VM's.

[foggy]

Bastiaan, guest log is indeed not affected by the mentioned log management settings and currently there seems to be no way to limit its size via Veeam B&R. We're planning to address this in the next versions.

[b.vanhaastrecht]

Bastiaan, guest log is indeed not affected by the mentioned log management settings and currently there seems to be no way to limit its size via Veeam B&R. We're planning to address this in the next versions.

Hi Foggy, ok thanks for the info. As we are a service provider which uses Veeam to backup the VM's of our customers, we would like zero interferance & influence within their VM's. So an automated cleanup of the logs to us is very welcome.

[veremin]

So an automated cleanup of the logs to us is very welcome.

You can, probably, set a cleanup script as the post job activity. This way, the given directory will be cleaned, right after the job is finished. Thanks.

[b.vanhaastrecht]

You can, probably, set a cleanup script as the post job activity. This way, the given directory will be cleaned, right after the job is finished. Thanks.

Does Veeam execute this script thru VIX? As we do not have network access to the customers vCloud VM's.

[veremin]

Hmmm, then, you might want to schedule the "cleaning" script via Windows Scheduler to run inside given VM at whatever basis you want to. Thanks.

[b.vanhaastrecht]

Hmmm, then, you might want to schedule the "cleaning" script via Windows Scheduler to run inside given VM at whatever basis you want to. Thanks.

Thank for helping. But, as we are talking about customers VM's we dont actively manage them. Asking the customer to add a scripts, is not desired ... We would prefer a buildin feature into the Veeam agent.

[veremin]

As far as I'm concerned, there should be a way to call VIX function from PS. So, it seems that you can create a local PS script and specify this script as a post job activity. Within the script you will call VIX function called VixVM_RunScriptInGuest and pass "cleaning" command to it.

I haven't tested this scenario myself, so, it's nothing but my speculations.

Thanks.

[averylarry]

To echo b.vanhaastrecht -- my issue is on guest computers, not the Veeam backup server or Veeam proxy servers. Frankly I don't understand why there are any logs generated on non-Veeam machines at all. And then to hard code it to the programdata folder seems shortsighted at best.

[b.vanhaastrecht]

To echo b.vanhaastrecht -- my issue is on guest computers, not the Veeam backup server or Veeam proxy servers. Frankly I don't understand why there are any logs generated on non-Veeam machines at all. And then to hard code it to the programdata folder seems shortsighted at best.

VIX is the VMware API which Veeam uses to execute a small piece of Veeam software to do some VSS things and index the guest. It's only used when application and/or guest indexing is enabled on the backup job. Veeam isn't agentless, which they state ... (but you dont need to update it).

To my opinion scripting on the guest side is not the anwser to elimitate these logs. It should be addressed within Veeam itself. As Veeam is also capable to do vCloud backups they should know the guest OS is not always within the Veeam proxy's reach. Foggy states Veeam might add options to configure the logging. To me, it should be addressed asap.

[foggy]

VIX is the VMware API which Veeam uses to execute a small piece of Veeam software to do some VSS things and index the guest. It's only used when application and/or guest indexing is enabled on the backup job. Veeam isn't agentless, which they state ... (but you dont need to update it).

Neither update, nor install/remove/monitor/troubleshoot/manage in any way, since this is not a persistent agent but rather a runtime coordination process automatically deployed when backup starts and removed immediately after backup finishes.

[b.vanhaastrecht]

This issue is realy getting a serious problem for us. We have vCloud customers complaining about the log file growth in their VM's protected by Veeam. In some situations its getting over 3GB. Again, scripting is no option as we do not actively manage these vCloud customers, and Veeam should manage their logfiles. Is this issue addressed in the next release/patch?

[veremin]

This has been tracked as the bug. According to the plan, it should be fixed in the next product release. Thanks.

[b.vanhaastrecht]

This has been tracked as the bug. According to the plan, it should be fixed in the next product release. Thanks.

Great, nice job, thanks for the feedback!

[b.vanhaastrecht]

This has been tracked as the bug. According to the plan, it should be fixed in the next product release. Thanks.

Is it fixed in v7 Patch #4 or coming with Veeam 8?

[Vitaliy S.]

Hi Bastiaan, the plan is to make it part of the product release, not patch. Thanks!

[Gostev]

Just to add to that, we list every single change in the patch notes, so if you don't see it listed there, it's not there

[b.vanhaastrecht]

Ok thank you both, good to know.

Sorry for being an eager beaver for this feature, it's most welcome in our situation

[Jois]

Hi,
Any news regarding this issue? Will VM registry values be introduced in v8 to manage these logs?

[Gostev]

Hi, we will know closer to the v8 release if this one is going to make it. Thanks!

[cpalmer]

Hi There,

Apologies if this has been asked before but I looked around and have been unable to find the answer i've been looking for

I have come across this kb - http://www.veeam.com/kb1825 but this doesn't relate to the same logs and the regkeys mentioned don't appear on this particular VM

Basically one of the VM's we backup has accumulated a large number of log files located in C:\ProgramData\Veeam\Backup named VeeamVixProxy_date.log ie VeeamVixProxy_01042012.log

These go back a long time and vary in size -Other than for troubleshooting is there any requirement for them to be kept and will deleting old ones cause any issues?

Many thanks

[veremin]

Hi Chris,

Your post has been merged into existing discussion regarding similar matter. Kindly, check answers provided above; should clarify situation for you.

Thanks.

[b.vanhaastrecht]

We're getting pretty close to the release of v8. Any news on v8 having a fix for this issue?

[foggy]

Yes, v8 will improve VIX logs handling.

[b.vanhaastrecht]

thank you !!

[Ysoba]

Hi,

I have the same issue on a client host, is Vcenter has accumulated a lot of VeeamVixProxy_***.log files. Veeam is still in version 7 and we can't upgrade it.
So i was wondering if deleting this log files will have an impact on Veeam or the Vcenter ?

Thanks