Turn off 'vmware tools are not up to date' warning

[JasonJoel]

In v6, is there a way to turn off the 'vmware tools are not up to date' warning when B&R backs up a VM with old VMware Tools?

Upgrading the tools is a low priority to me, and I don't want most of my backups showing 'warning' just because I chose not to upgrade the tools yet...

Jason

[Gostev]

Hi Jason - no way to turn it off, but I will ask development to suppress this warning in the next update. Having VMware Tools most up-to-date is not important indeed. Thanks!

[joshuastenhouse]

Please can you confirm if this is going to be in the next update or not and likely timescales? A large proportion of my jobs are now showing warning and it doesn't look good to the powers above! Thanks.

[Gostev]

Hi Joshua, I am confirming that. Historically, it used to take between 2 and 3 months between the major version release and the first maintenance release. Basically, we need to collect enough of other issues to justify the maintenance release. Thanks!

[jkcouch]

I will pile on this! Its Very important for us to get this warning removed. We dont have a single jobs without the warning flag. Can it just be a option in the backup server to enable warnings for the tools?

Thanks Gostev.

[tgiphil]

+1 for option to remove the vmware tools warning.

[JeffHengesbach]

I'll join in on this one also. I understand since we are working at the hypervisor level the integration points are important but if the backups are completing successfully, a warning should not be thrown.

[JasonJoel]

Any update on when this will be implemented/fixed? I was hoping it would make it to Patch 2 - but no such luck.

Jason

[Gostev]

Patches typically do not include anything but bug fixes... so most likely, this would be the next release only (in a few months). Thanks.

[JasonJoel]

With all due respect, this IS a bug. It is a degradation from v5, as well.

Jason

[Gostev]

I meant, it is not a bug per our definition (but I appreciate that you may have different opinion). We consider this as an enhancement. Besides, patches only include fixes for critical bugs anyway (we need to keep changes to absolute possible minimum to reduce time to release).

However, since there are a lot of requests for this particular issue, I will try to squeeze this into the next patch. Cannot give you 100% guarantee though! Thanks.

[JasonJoel]

Thanks. Note, they fixed the VM notes not updating if they are on a CIFS share in the patch... Certainly more minor than this issue .

But I understand! We'll keep patiently waiting. v6 is working very well for us.

Jason

[Gostev]

Yep, the CIFS one is the real bug by definition (product functionality is not working). Minor bugs are sometimes included if they have generated multiple support cases. Basically, our support organization has significant weight in deciding which bugs need to be addressed. They tell us what they would like fixed, and in what order. Yet another reason to always be opening a support case!

Thanks for understanding!

[DaxUK]

+1 on this we are seeing the same issue and are operations team are flagging issues

[lobo519]

+1

[aschepers]

+1

Honestly: who keeps all of the VMware Tools inside all their guests up to date? It's a mammoth task with 224 VM's and counting, downtime is an issue, risk of disrupting the VM (mainly network issues), etc. I would like to see the VMware Tools not necessary anymore.

[rgj]

+1 on this.

[rejected2008]

+1

[ErikSi]

+1

[Vitaliy S.]

If you want to change this behavior, please apply our latest Veeam B&R patch (#3) which can be found here. Thanks!

[ErikSi]

Thanks Veeam

[dstamen]

awesome! our support team was just asking about it this week so they knew what warnings were actually warnings.

[JasonJoel]

Just thought I would follow-up and say "thanks" for changing/fixing this in Patch 3.

For us, everything has been working really well since installing that patch.

Jason

[Gostev]

Thanks for the follow up. Always good to hear back from happy customers!

[timo.heissenbuettel]

Hi,

we've just updated from latest v7 to v8 on friday and got loads of "Backup was successful, BUT VMware Tools are out of date".

This is a helpful message, but we're monitoring VMware Tools age with another tool. Is there any way to disable this message and let backups complete successfully, even when VMware Tools are old?

Brgds,

Timo

[Vitaliy S.]

Currently there is no way to disable this behavior, but I have asked our dev team to change that in the next minor updates. Thanks!

[Vitaliy S.]

Hi Timo,

Just heard back from our QC engineer, they checked and backup job sessions appear to log informational events (not warning events) for outdated VMware Tools. Can you please give us a bit more information on your infrastructure? Also did you have this behavior in v7? Are there any other warning messages in the job log? A screenshot would also be helpful.

Thanks!

[justind]

I also have experienced this issue since upgrading to v8.0.0.817

I can confirm that this definitely was not an issue prior to the upgrade.

Support Case 00673914

[Gostev]

Since QC cannot confirm the issue with v8 code, let's have support investigate the logs.

[timo.heissenbuettel]

Is there any way to send my logs, too? Should i open a new case and somebody is linking our cases?

We haven't had this issues with latest v7 and now after updating to v8 we do have this issue.