6.5 to 6.7 creates a new appliance

jprovine7 · ‎02-08-2019

Last year I migrated from vcenter 5.5 windows physical server to a 6.5 appliance. I used the migration tool that created the appliance and migrated all the configuration and data to the new server. I have been looking at what it takes to upgrade from 6.5 to 6.7U1 and it looks like the same process that I used to migrate to 6.5 from 5.5, why is it necessary to create a whole new appliance and migrate all the data and configuration again? Is there any other method to do this?

daphnissov · ‎02-08-2019

No, this is how it works. Sometimes underlying OS changes (sometimes slightly; sometimes significantly) and a redeploy guarantees all the dependencies are correct. Why does it matter? The identity will be fully migrated to the new appliance, so it's not as if you have to give up anything or manually make changes after the upgrade occurs.

------------------
How to Ask for Help on Tech Forums
https://neonmirrors.net

View solution in original post

jprovine7 · ‎02-08-2019

Do I still have to create an ephemeral port to make it work , I did the last time

daphnissov · ‎02-08-2019

You should have one to begin with, so if you don't then yes. An ephemeral port group should continue to exist in your environment if you only use a vDS and have your vCSA joined to the vDS it provides.

------------------
How to Ask for Help on Tech Forums
https://neonmirrors.net

jprovine7 · ‎02-08-2019

Yes the one created still exist from my upgrade from 5.5 to 6.5, so I guess it can reuse that for the upgrade

daphnissov · ‎02-08-2019

Then that should work fine.

------------------
How to Ask for Help on Tech Forums
https://neonmirrors.net