Looking for approximate hotfix timing

[mikeely]

Hi all,

We're bit by:

#7: Suspicious incremental backup size alarm randomly triggers, resolves itself and triggers again in a short time

The suggested workaround is to disable the alarm, but then I fear we'll forget to enable the alarm when the hotfix is released. Maybe somebody from Veeam can speak to where this bug is on their priority list so I can make a better decision about whether to just endure the spam for a couple more weeks or whether we should disable the darn thing.

Also maybe the hotfix can offer an install-time option to re-enable the alarm so we don't forget?

[Shestakov]

Hi Mike,
The fix is under investigation and may be done and tested in a couple of weeks, but we don't guarantee any terms.

[Shestakov]

Hi Mike,
The hotfix is already available via the support team.

[mikeely]

Hi Mike,
The hotfix is already available via the support team.

Please tell the support team this. I opened ticket 04113374 and here is the reply I received:

Hello Mike,

Thank you for contacting Veeam. My name is Justin from EM support I will be the engineer assisting you.

In regards to this specific alarm, it is in the release notes below. At this time we unfortunately don't have a patch or fix for this alarm. The only way to get around it at this time is to suppress the alarm. We are aware of the issue but do not currently have a hotfix or patch for it.

https://www.veeam.com/veeam_one_10_0_re ... tes_rn.pdf

[Shestakov]

Strange. Support management told me today that the fix is available. I'll double-check. Sorry for the confusion.

[Vitaliy S.]

For all future readers > the hotfix is ready and our QA team is verifying it now, so next week it will be available for download.

[WifiToaster]

Hey,

I am future reader, lol.

What is the version number that contains this hotfix? I am still getting this error with Version 10.0.0.750

[foggy]

Hi, the hotfix is available through our technical support team, please contact them directly to get it. Thanks!

[mikeely]

Except it didn't work when I installed it. Support ticket 04113374 is in Research/Testing status.

[Martin Damgaard]

I first got a patch from Veeam support, that did not help.
Then we installed VBR v10 Patch 2, but that also did not help.

Getting loads of alerts every day for Suspicious incremental backup size, only to get a reset resolved only a couple of minutes later.
Veeam support is now escalating it...

Also noticed, that when opening job history for Suspicious... in Veeam ONE, it does not show all triggered alarms.
Some of them is not in the history, like it didn't happen - only my mailbox says otherwise.

Does any of you use "Transform previous backup chains into rollbacks" by any chance?

[wishr]

Hi Martin,

Please keep working with our support engineers until the issue is fully resolved and share your case ID so we could keep an eye on the progress and assist where necessary.

Thanks

[skazzzi]

I also get this after update to 10. Is there any fix from support already?

[wishr]

Hi Skazzzi,

What VONE version you are at and what backup method you use?

Thanks

[pirx]

Did this fix go into any regular update yet, or do I still have to contact support to get a hotfix? We are on 10a.

[wishr]

Hi Pirx,

10a was our latest publicly released update. Most of the fixes shared with customers through the support team channel after this release will be included in v11.

Since it's not clear what issue you are experiencing and what are the environmental details, I would recommend contacting our support team directly. Once the issue is clarified and understood, I'll be able to say what version contains/will contain the related fix.

Thanks

[pirx]

I'm experiencing the "#7: Suspicious incremental backup size alarm randomly triggers, resolves itself and triggers again in a short time" from #1 post. It might not be the same as alarms are flip-flopping on a daily base. But it could also be the expected behavior for these VM's, I'll ignore it from now.

[wishr]

Thanks for commenting. We can take a precise look at it if needed. It may be both an environment-related issue as well as a bug in the alarm logic.

In fact, in v11 we've significantly improved the alarm, so you may want to give it a try after upgrading. As always, we'll be happy to hear any feedback on these changes.