Removing old vCenter Server from Veeam not possible

[widmerkarl]

Hello guys

This is my first post here in the Veeam forums. Many times i was glad to find here some advice and tips which helped me alot. Now i hope that someone of you experts can help me with a hint.

A few days ago we changed the VMware infrastructure at a customer. We migrated all VMs to new hosts and storage (HP servers, 3PAR storage, vSphere 6), and also migrated from a vCenter Server based on Windows to a vCenter Server appliance.

All backup and replication jobs were edited and are running fine. The customer runs Veeam Backup & Replication 8 with latest patches.

Now we thought that we clean up in Veeam, checking all the settings we might have missed, remove old hosts and vCenter. When we try to remove the old vCenter Server we recieve an error message:

"Unable to delete host "servername".
VMware vCenter Server "servername" is used by the following jobs:
replication01
replication02
replication02

We checked the replication jobs, added the VMs again just to make sure we had the right source. That did not help so we deleted the replication jobs and created it new from scratch. But the problem was not solved. Everytime we try to remove the old vCenter server, the error message appears.

What can we do or try to get rid of the old vCenter server within Veeam?

Thanks alot for your help.

Kind regards,
Karl

[foggy]

Karl, please contact technical support, they will be able to cleanup your database from the obsolete records. Thanks!

[widmerkarl]

Foggy, thanks for your advice. I've already thought that I have to contact support. I just thought that I may have overlooked a setting or something.

Kind regards

[g2gsr]

I am running into the same issue. The old vCenter server doesn't exist anymore, so this should not be something for which I should need to open a support request. Is there any additional information that can be provided so that this can be handled without having to open a request.

[Vitaliy S.]

Hi John,

If your jobs are running normally after migrating to the new vCenter Server with the same name and job reconfiguration doesn't help, then our support team should be able to fix this pretty quickly for you.

Thanks!