Disabling Data Collection For Decommissioned Veeam Instances

[chadduxbury]

When decommissioning a Veeam Backup & Replication server instance, the log collection in Backup Enterprise Manager continues to run for those Veeam servers. Due to this, the collection logs always show as failed because the server is no longer in existence. Since I need to retain the backup logs for audit purposes, I cannot remove these Veeam instances from the BEM console since that also removes all audit logs for that Veeam instance. I’d like to request a feature to disable log collection for Veeam instances that no longer are functioning but still need to be retained in the console for audit purposes. This way I know if the log collection is successful on existing servers that still need it.

[david.domask]

Hi chadduxbury, welcome to the forums.

Just to confirm, you're talking about the Data Collection described here, correct?

The request is interesting -- may I ask though, do your regulations require that you have _live_ access to the data? Or just a copy? That is, would backing up the Enteprise Manager server to protect the configuration database be sufficient and just restore the database if needed?

[chadduxbury]

Yes that is all correct. I just need access to the backup logs. The live data is not in question at this point. This proves we had backup log tracking done by our department and action upon backup failures that correspond with support tickets opened on our end.

[chadduxbury]

I should clarify my last statement a little further. I need BEM to retain all of the backup job logs for all Veeam instances that it collects from to be retained in BEM with the capability to stop collection of those logs from the servers that are no longer in existence. Meaning just disable collection process from those servers but keep BEM Veeam job logs completely in tact. That's without having to restore any database or make any other manipulation to BEM. Just the capability to disable the collection process from BEM to those non-existent servers would fix this problem. That would allow me to have visibility on the job logs for all audits and then also know that the collection process is succeeding each time. Right now the collection process shows as failing every time because three of my five Veeam servers in BEM are decommissioned and BEM is trying to collect each time from them. So I have to review the collection logs themselves to verify the two Veeam servers I still have in production are actually collecting properly which is very cumbersome.