Currently trying to update one of our vCenters from 6.5 u3 to 7.0 u3, Stage 1 passes fine but it keeps failing on Stage 2 with the same error.
2022-11-18T16:10:51.405Z Upgrade import failed due to error Error while creating constraints: psql.bin:/storage/seat/cis-export-folder/vcdb/create_constr.sql:29: ERROR: could not create unique index "pk_vpx_alarm_runtime"
2022-11-18T16:10:51.405Z Upgrade import step failed
2022-11-18T16:10:51.405Z vPostgres firstboot(action=firstboot) failed.
Any advice as to what this relates to?
Is it worth trying to do a vcdb vacuum cleanup on the source vCenter? Even though I don't suspect space/capacity is an issue here.
You need to check vCenter 6.5u3 Build and vCenter 7.0 Build if they are compatible:
check builds for "Back-in-time release upgrade restriction".
You can also take an intermediate step: vcsa 6.5u3 -> vcsa 6.7u3 -> vcsa 7.0u3 (but always check the build numbers first).
Thanks for your reply.
I did the same upgrade on our other vcenter last week which completed with no issues, both are on the same original version and I'm using the same iso file for both upgrades.
It's only this one I'm having an issue with only difference is a virtual distributed network switch, and an additional 2 physical hosts on the cluster.
From experience I can tell you that each update is a case in itself. Try the step by step procedure: 6.5u3->6.7u3->7.0u3
First you need to upgrade your VDS version
Upgrade a vSphere Distributed Switch to a Later Version: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-330A0689-574A-4...
Before starting, always take a cold SnapShot.