VeeamONE Reporter Web Console>Configuration>Servers

[jtupeck]

Good morning all -

I am decommissioning a server from my environment and moving to a more simplified, single B&R host architecture for my Production>DR replication. The server in question has always reported to the BEM server for licensing, etc. Before I delete the VM I am decommissioning, I want to be sure it is removed from all Veeam/VeeamONE environments and not causing any errors. I removed the entry from the BEM web console and it is working properly for its data collection scans, but I am not seeing any way to remove it from the VeeamONE Reporter web console's Configuration>Servers page. When the 'object properties collection task' runs every 8 hours, I am now getting Warnings/Failures due to the decommissioned server being turned off. Can someone point me in the right direction for removing this machine so the errors will stop? Because the server was removed from the BEM, it has subsequently disappeared from the Data Protection View in VeeamONE Monitor and I cannot remove it there, so I am at a complete loss for where else I should be looking for this connection.

If I need to open a case, I will, but I was hoping someone had a suggestion to look somewhere that I am simply unaware of, or forgetting about.

Thank you!

[jtupeck]

Shortly after posting, I had an idea. I added the server back into VeeamONE Monitor Data Protection View area as a standalone B&R box, using the same FQDN that was displaying in the Reporter config page and then let it sync. After the sync, I removed the server from VeeamONE Monitor and it has now been removed from the data collection process and no longer displays in the Configuration>Servers page. Maybe this will help someone in the future, if you run into the same issue.

[Shestakov]

Hello Jason,
there server should has been removed from reporter automatically. What product version are you at?
Thanks!

[jtupeck]

9.5 Update 3 for B&R, and 9.5.0.3801 for VeeamONE. I thought it should have removed automatically as well, but it did not.

[Shestakov]

Thanks we will double-check the behavior.
Glad you have found the workaround.