YYYY-MM-DDTHH:MM:SS info vmware-vum-server[133951] [Originator@6876 sub=BaselineMgr] [baselineMgr 5292] Migrating baseline, id: 361, name: ESXi80U3b-24280767YYYY-MM-DDTHH:MM:SS verbose vmware-vum-server[133951] [Originator@6876 sub=BaselineMgr] [baselineMgr 1255] Got spec for baseline id: 361, name: ESXi80U3b-24280767YYYY-MM-DDTHH:MM:SS info vmware-vum-server[133951] [Originator@6876 sub=BaselineMgr] [baselineMgr 5440] Data migration, update baseline for : 361, name: ESXi80U3b-24280767YYYY-MM-DDTHH:MM:SS error vmware-vum-server[133951] [Originator@6876 sub=BaselineMgr] [baselineMgr 1930] Vcidb ERROR: Element with same name already exists - ESXi80U3b-24280767-->--> Exiting....-->YYYY-MM-DDTHH:MM:SS error vmware-vum-server[133951] [Originator@6876 sub=BaselineMgr] [baselineMgr 1930] [backtrace begin] product: VMware Update Manager, version: 8.0.3, build: build-24091160, tag: vmware-vum-server, cpu: x86_64, os: linux, buildType: release--> backtrace[00] libvmacore.so[0x00530335]--> [backtrace end]YYYY-MM-DDTHH:MM:SS error vmware-vum-server[133951] [Originator@6876 sub=VcIntegrity] [vcIntegrity 765] Error is start vum server :Fault cause: vim.fault.AlreadyExists
Note: Ensure a valid backup of the vCenter Server(s) or a powered off snapshot has been taken before proceeding as the below steps involve modification of the vCenter Server database.
Identify and delete the duplicate baseline entry.
service-control --stop vmware-updatemgrselect id,name from VCI_BASELINES where name='<name of baseline>';
select id,name from VCI_BASELINES where name='ESXi80U3b-24280767';id | name----+--------------------361 | ESXi80U3b-24280767360 | ESXi80U3b-24280767
delete from VCI_BASELINES where id=<id value>;
delete from VCI_BASELINES where id=361;service-control --start vmware-updatemgr