Veeam ONE: Impossible to upgrade to version 11 because the upgrade process find unsupported veeam B&R version

Issue

A customer of mine fails to update Veeam ONE from version 10.0.0.750 to the latest version 11. He encounter the following error message "Veeam ONE database has one or more unsupported Veeam Backup & Replication servers. This product supports Veeam Backup & Replication 9.5 Update 4 or later."

Solution

I tried to see if there were any objects or configurations prior to version 9.5 but I didn't find anything.
The problem encountered may occur when the VBR server, added to Veeam ONE was upgraded before the Veeam ONE upgrade, so automatic upgrade is not possible.
Anyway, there is a workaround for this situation, suggested by veeam support. Is a manual product update.
To solve, follow the instructions below:

1. Make a backup of Veeam ONE database: https://www.veeam.com/kb1471 and then uninstall Veeam ONE on the server completely.

2. Install Veeam ONE v11a with the local database (SQL server express will be installed on the server)

3. After the installation, execute the script from the folder: ISO: Addins\SQLScript\VeeamOne.sql. against the existing Veeam ONE database (on the production SQL server: https://www.veeam.com/kb2312 )

4. Once the script is executed, change the database name in Veeam ONE settings and restart the services as described in the following article: https://www.veeam.com/kb1592

Thanks, to the guys at veeam support.

That's it.

Just a cosmetic issue?? No, PortGroup and Uplink disconnected (on UI) not properly re-assigned after upgrade.

Issue

After an upgrade of the ESXi host from version 7.0.1 to 7.0.2 when the host came back on, the network was no longer properly connected to the DVS.
I then re-added the ESXi host to the various DVSs by reassigning the uplinks to the correct vmnic as originally.

Everything seemed to be working fine (ping, VMs were reachable, the host was properly managed by vCenter, vMotion was OK, then the host was able to mount iSCSI storage correctly etc) when I noticed ...

and ...

Solution

To solve the problem I had to re-assign the VMkernel adapters to the corresponding Portgroup even if they were already present.

So, I proceeded as follows ..

• Right click with the mouse on DVS affected (The images below refer to a different DVS from that shown by the images above, however the procedure performed does not change).
  
• Add and Manage Hosts...
  
• Select Manage host networking and click Next
  
• Click on Attached Hosts... select the host affected. Click OK and then Next until you get to session 4 Manage VMkernel adapter.
  
• Select the vmk of the "On this switch" section (in my case, I start with vmk0 and then with the others) and click Assign portgroup.
  
• Select the right portgroup and clik OK.
  
• Do the same for the others vmks.
  
• Click NEXT, NEXT and then FINISH.
  
• As we can see now, from the image below a new "Port ID" has been assigned to the host and the "State" results with the Link Up.
  
• But if I look into the Topology view, there is still something to fix ...
  
  
  the Uplink1 and Uplink2 State for the host are still down ...
  
• Connecting via SSH to the host, I check the status of the nic with the command
  
  # esxcli network nic list
  
  I observe, that unlike the graphical interface, the "Link Status" of vmnic20 and vmnic21 are Up.
  
• I solved it, putting down and up the vmnic20 and vmnic21 ...
  
  # esxcli network nic down -n vmnic20
  # esxcli network nic up -n vmnic20
  
• Looking the UI ...
  
  Now everything is OK.

That's it.