Selected database has one or more unsupporte ESXi or vCenter

[pidthepiper]

Hi,

I am getting this error when I try to install Veeam v8 on a new 2012 vm and direct it to use the database used by Veeam v6.5

It database is on an external SQL 2008 R2 VM.

I don't get what the error is referring to exactly?

The database is at SQL 2005 (90) compatibility Level, the error comes just after it says it will upgrade the database if needed.

Cheers,

[foggy]

Bilal, the error refers to the fact that the database contains some of the older VI 3.5 servers (ESX(i) 3.5, vCenter 2.5), which were supported in v6.5, however not unsupported in v8. I think if you remove those from v6.5 installation, the upgrade should go fine.

[pidthepiper]

Let me investigate!

[pidthepiper]

OK there is an ESX 3. host, it has a couple of VMs that I would like to backup, but I get the error "Your Veeam Backup license does not allow the processing of free ESXi."

I have an Enterprise license ? why would this be an issue?

[foggy]

Do you have a paid VMware license covering this ESXi host? Veeam B&R is not allowed to process free ESXi host (the message itself is somewhat confusing).

[pidthepiper]

it has a valid license, either way I have removed it and the setup has started and then failed for some reason

[foggy]

Did it fail with the same or different error?

[pidthepiper]

Well the first time it started installing and then backed out.

After a reboot I got 2 errors while it tried to install the NetApp Plugin and another vendor lugin:
Unable to connect to SQL Server the login failed.

But it finished installing

[foggy]

You can try to repair the installation to see whether the errors persist and contact support i case they do.

[pidthepiper]

Well those plugins dont even matter to me, we run Dell Compellent

Do I have to edit each job and update the credentials ??

Do I have to readd my repositories, as I am unable to find the bit to edit the login details?

[foggy]

Credentials update should not be required in case of upgrade.

[pidthepiper]

Well all the jobs are there and everything, well its a totally new VM pointing to the old 6.5 current database?

[foggy]

Could you clarify your last question, please?

[foggy]

Ah, sorry, in case of remote DB you would need to re-enter credentials, right (since they are encrypted with a machine-specific key).

[pidthepiper]

How do I re enter the username/pass for the backup repositories? I click on their properties and I don't see anything regarding logins?

[foggy]

Credentials are specified while you add server that holds the repository to Veeam B&R console, not in the repository wizard.

[pidthepiper]

dont mind me I was being stupid I have figured it all out and it seems to be running!

[foggy]

No problem, glad I could help. Feel free to ask any further questions, if required.

[MaLa]

Hello everybody,

I have unfortunately the same Error "Selected database has one or more unsupporte ESXi or vCenter" while attempting to Update from Version 8 to 9. Our VCenter was launched with Version 5.5, so there can't be an older Version. Therefore I do not understand this error message ...

Maybe you have an idea what could be the cause? Unfortunately I see no error

Thanks in advance
Regards Mario

[foggy]

Hello Mario, any chance some of the older ESXi servers were previously added to this Veeam B&R installation? Anyway, you need to contact technical support for the database cleanup.

[masonit]

Hi

Trying to upgrade from v8 to v9. But get error about old esx servers. The error is correct. One of many vcenters has 4 esx hosts with version 4.0. Plan is ofcourse to either upgrade or remove these hosts. But is there a way around this? Why can't I even upgrade..? We don't backup any vms on thoose hosts..

/Masonit

[foggy]

Are you sure those hosts are not explicitly added as standalone in Veeam B&R UI? In case only vCenter is added, unsupported hosts under it shouldn't block the upgrade.

[masonit]

Ok then it should not be a problem. I got this error on a test vbr server. After that it started to look up if there was old esx servers connected to our production vbr servers. I haven't actually tried to upgrade production yet.

\Masonit