"Components Update" Windows after B&R 9 Update 1

[jmeisel]

Hello,

we applied Veeam Backup & Replication 9 Update 1 yesterday. Everything ran smoothly and without any error messages. The build number is 9.0.0.1491.
But now, each time the Veeam Console is started, we get an "Components Update" Window that is completely empty. No managed Servers to update. Nothing.

Anybody else facing this issue?
I am able to open a case too, if that is necessary.

[nielsengelen]

Best to open a case to see why this is happening. Might be an invalid reference in the database or something.

[veremin]

If you go to backup infrastructure, will you see there any outdated components?

[jmeisel]

Yes ... under managed Servers there is still an standalone hyperv-Server that no longer exists.
But because it has been discovered by adding our System Center Virtual Machine Manager, it can't be removed from Veeam.
Strange...

[jmeisel]

I just created a case. Case Number is 01746090

I guess we have to remove the orphaned HyperV-Servers (that no longer exist on SCVMM) manually from Veeam Database. Deleting the entry under dbo.hosts won't be enough, I guess.

[veremin]

It seems that there are indeed orphaned references inside the product database that need to be cleaned. Knowledgeable support engineer will be able to assist you with that process. Thanks.

[jmeisel]

FYI: the issue has been resolved by deleting old, orphaned HyperV-Servers from the Veeam-Database.
We received the SQL-Script from Veeam-Support.

In case you have a similar issue: just open a case and you will receive help

[GladstoneRC]

Same issue here. Guess I'll open a ticket.

[jconk711]

Good morning,

I have been working with a Veeam representative on a case I opened (#01825339). I am not 100% certain exactly when this annoyance appeared as I inherited the environment but we recently Upgraded to Veeam 9 update 1 and every time the console is opened the component upgrade window appears but no components appear listed that require an update and you have to cancel out of the window.

In working with Veeam we have attempted the following:
1. Cleaned out extraneous managed servers that are no longer in use.
2. Verified SP1 and hotfix1 were applied.
3. Reviewed the util.clientlauncher.log
4. Reviewed SVC.VeeamBackup.log
5. Rescanned all managed servers to verify no errors
6. Rescanned all WAN accelerators to verify no errors
7. Worked with Veeam support to clean up stale database entries for old managed servers

I have found multiple posts from people who have seen this behavior and wanted to see if anyone has overcome this as nothing has corrected the behavior yet and we are at the point of either living with this or attempting a reinstall which I would like to avoid.

Other articles:
Not solved
vmware-vsphere-f24/remote-console-update-1-t35146.html

Solved by cleaning up the configuration database:
veeam-backup-replication-f2/components- ... 34072.html

Any help is appreciated!

[jbennett]

No condoning digging into the SQL DB without support, but it looks like HostComponent may have an orphaned component. Seemed to by my issue.

This is how I was able to check:

Code: Select all

SELECT *
  FROM [VeeamBackup].[dbo].[HostComponents], [VeeamBackup].dbo.PhysicalHosts
  WHERE HostComponents.physical_host_id = PhysicalHosts.id and HostComponents.is_up_to_date = 0

  Select *
  FROM [VeeamBackup].[dbo].[HostComponents]
  WHERE HostComponents.is_up_to_date = 0

[jconk711]

I was able to find stale entries using Justin's query. As he stated I would not edit without Veeam Support being present or before taking a backup of the database.