Alarm Suppressions get messed due to wintertime

[mbietz]

Hello,

we had the change to the wintertime in germany.
Now the suppression times for the most but not all alarms are wrong (they are now one hour to early)

I see those entries in the database

<suppress version="900">
<period day="7" from="11/30/1999 5:00:00 AM" to="11/30/1999 6:15:00 AM" comment="" enabled="1" />
<period day="7" from="11/30/1999 5:00:00 PM" to="11/30/1999 6:15:00 PM" comment="" enabled="1" />
</suppress>

How can I resolve this issue.

Thank You

[Vitaliy S.]

Hello,

Have you tried to reset them? Specify new time, save it and then change the suppression time back to the desired value. Also did you change time on the Veeam ONE server to adjust to wintertime?

Thank you!

[mbietz]

Well,

all Servers (Veeam-One, SQL-DB, vCenter,...) are in same timezone and the change was successful.
I had the same problem prior, this year when going from wintertime to summertime.
What is strange, is that not all suppression times had this problem.

I now put in the day and the time in the comment value, I bet it will be messed up again when going to summertime.
This Bug should be fixed soon.

Also I have suppressions where I put a distinct day (for instance Monday) in, and after saving, this day is incremented automatically.
So it is Tuesday, after another save it is Wednesday, and so on.

Well those suppressions are very unreliable and in this state totally nonsense.

I have a case for that Case # 01956634

I hope that this will be fixed very soon.

[Vitaliy S.]

Thanks for the case ID. I see from the internal notes, that this behavior confirms with version 9 only. 9.5 shouldn't have this issue, but we will double-check once again.