The last days VCSA 6.7.0a gets GA. In this post I want to show the upgrade from VCSA 6.5 U1 to VCSA 6.7.0 (not a). In my other post (Update VCSA 6.7) I’ve made the update from 6.7.0 to 6.7.0a.
First thing to know is, there is no support to upgrade from 6.5 U2 to 6.7.0! So, if you are planning to update your existing VCSA 6.5 to Update 2 you have to wait for the (maybe) VCSA 6.7 Update 1 to migrate to 6.7.
For example there is also no support from Veeam Backup & Replication 9.5 Update 3 for vSphere 6.7 (www.veeam.com) Support will come with the next update.
(26thJun18 Veeam B& R 9.5 Update 3a is availiable)
VMware has made an KB article with important information before upgrade (kb.vmware.com)
Now lets start with the upgrade
In September 3 Flings were updated and none new Fling was released.
The updated Flings are
You will find Changelog and more information in this article.
In my previous posts I wrote about the upgrade of vCSA (vCenter Server Appliance) from version 5.5 to 6.0.
In all my lab testing the upgrade runs without any errors. On our production site I was doing the upgrade and the migration went fine until the new appliance boots for the first time.
The services start all until the vPostgres database starts. Something in the upgrade script gives back an error. Installation abort and I must boot the old vCSA 5.5.
VMware closed my call, because of an unsupported way getting vCenter Server for Windows to the vCSA 5.5. Everything runs in the vCSA 5.5. The upgrade fails and with the migrated database there is no support.
Since my decision to change my blog to english i’ve wrote some articles. But the domain ends with .de and in my opinion this wasn’t nice.
So I move the whole content to a new domain. What I didn’t know was how to preserve the old links to my posts without contact all users and partners.
I’ve wrote my transfer steps down. At the end it was really easy, but i’ve searched a little for some steps.