B&R v9 Install (managed server unsupported) error

[iAmRoot]

I've been attempting to upgrade our B&R v8u3 server to v9 and am getting a "This configuration database contains managed servers with an unsupported OS (Windows 2003 and earlier). You must remove all such servers before upgrading." This doesn't seem to make sense since all VM's that are hosting Veeam components (proxies, etc) are Server 2008 R2. We backup several Server 2003 guests as part of our jobs, but they have nothing to do with any Veeam service or component. Has anyone seen this and know the solution?

[nielsengelen]

If you are 100% sure you don't have any Windows 2003 part of the Veeam infrastructure it should work correct however if the problems is persistent please open a suppot case to have this resolved. Might be an issue related to your database.

[Dima P.]

Hi Andy,

Indeed, please open a support case and post case ID to this thread: we might need to quickly check the upgrade logs to identify the root cause. Thanks in advance.

P.S. From the top of my head, could it be a component that was upgraded from Windows 2003 to 2008 while being added to the VBR v8 console?

[iAmRoot]

I figured it out. Under the Backup Infrastructure there were some 2003 servers non-Veeam application servers of ours that had some transport components installed on them. Not really sure how or why they were there, but I removed them and was able to proceed through the upgrade process. Thank you to everyone for your help!

[Dima P.]

Awesome! Glad you nailed it and thanks for updating the thread.

[tlelache]

I get the same error doing my upgrade from 8 to 9. I went through my managed servers and removed all the proxies on servers on 2003. I rerun the upgrade and I get the same error. When I look at the table dbo.hosts, I can see the backup proxies that I deleted still listed. Do I have to manually delete these records from the table? I'm comfortable doing that but don't want unintended consequences. Thanks for your response in advance.

[Gostev]

Most likely, deleting these records will be sufficient as this is the only table setup checks, as far as I know. But, I can't guarantee that there are no dependencies or some other tables you also need to clean up to keep the database consistent... which is why with all database edits, it is always best to go through support.

[SHSDavid]

Thank you to iAmRoot for posting their fix.

I had a winXP proxy that was giving me this error. Once I removed it, I was able to upgrade to v9 with no further issues