Veeam Product Request

[cvanreenen]

We need an option to disable alerting on sealed extents while keeping alerts for actual repository health issues. This feature could be a part of the VBR GUI or a change that can be made to the configuration file.

We cannot remove the extent since it contains large amounts of data that would have to be evacuated. We also cannot unseal it, as doing so would allow new data to be written. The extent is sealed intentionally, and should not be triggering warnings.

Currently, there is no built-in way to disable warnings specifically for sealed extents while keeping other repository health alerts. This causes unnecessary alerting noise.

[Gostev]

This makes sense. Could you detail what sort of alerts are you still getting for sealed extents? Thanks

[cvanreenen]

Thank you for your response. To clarify, we’re currently receiving the following alerts for sealed extents in our Scale-Out Backup Repository:

Extent Health Warnings:
Alerts indicating that the extent is sealed and cannot receive new data, which is expected behavior. These warnings are redundant because the extent was intentionally sealed and should not be triggering notifications.

Capacity Warnings:
Despite no new data being written, we continue receiving capacity-related warnings, which indicate that the sealed extent is nearing its storage limit. This alert is unnecessary since no data is being added to the extent.

Backup Job Alerts:
Occasionally, backup jobs are flagged as failing or delayed due to attempts to write data to the sealed extent. Since writing to the sealed extent is not part of the plan, these alerts do not reflect an actual problem.

It would be nice to have the ability to granularly turn off individual warnings. Even if it is just editing the proxy file to ignore an alert.