Background disk merge interruption

[max0664]

Hey,
I have often a "Background disk merge interruption" Warning in Veeam One on different servers.
When I check the Eventlog I see this Events at
03:46:07 - 19070 - "VM01" background disk merge has been started.
03:36:34 - 19090 - "VM01" background disk merge has been interrupted
03:46:34 - 19070 -"VM01" background disk merge has been started.
03:46:46 - 19080 - "VM01" background disk merge has been finished successfully
So I think I can ignore this Warning because the Disk merge is done.
The only problem is that I get every day around 5 Warnings after the backup. So is there an opportunity to make a rule to close this Warnings automatically if the merge finished successfully?
Thx for help.

[Shestakov]

Hi Max,
The alarm is triggered by event 19090 "Microsoft-Windows-Hyper-V-VMMS".
You can edit the "Background disk merge interruption" alarm adding a rule to resovle it in a case of Event ID 19080.
This feature is going to be available in the next versions. Currently the event is not collected by Veeam ONE.
Thanks!

[auclairy]

I know this thread is quite old but I am wondering if Veeam One finally collect the event id 19080. It was mentioned the feature would be available in the next version (in 2016). Is it now available in VeeamOne 12? I found no reference about this.
Thanks.

[RomanK]

Hello Yannick,

I've checked with our QA that event ID 19080 is not collected. No changes should be expected in the 12th version.

Thanks

[TimInKent]

This rule adjustment seemed to work to resolve the issue (see image). It would be nice if it was finally added to the default rule: (I tried using the insert image flags but they didn't work for me, so adjusted the post to include a link to the image) https://i.postimg.cc/g2LBT4zQ/Resolve.png

[RomanK]

Hi all,

It is hard to say why the case above is working and if it works correctly in every case.
The event 19080 is in the database exclusion list. However, we've researched a bit more and in theory, it is possible to work around.

NOTE: This is not an official solution. Apply everything below at your own risk and do backups in advance.

1. add 19080 event ID to the monitoring

Code: Select all

insert into monitor.EventInclude
select 4, 3, 19080, NULL

2. remove it from the exclude filter

Code: Select all

delete from monitor.EventExclude
where id = 54

3. restart VeeamDCS service

4. add alarm rule


This works in a lab but could be broken by any product upgrade.

Thanks