Skip to main content
  • EN

I just stumbled over tho following article and I think this is interesting.

My colleagues who administer our vSphere clusters ran in such a problem some time ago.

https://www.provirtualzone.com/how-to-add-extra-space-to-vcenter-for-the-upgrade/

Thanks for sharing! It is a great resource!

There are also problems with migrations (Windoes → Appliacne) of vCenter. Very often, wizard pre-selects a very large deployment despite it is not necessary. Sometimes it helps to clear some tables:

https://vnote42.net/2019/11/16/bad-deployment-and-storage-size-estimation-in-vcenter-migration-wizard/

Sometimes this can be helpful too:

For migrations and upgrades (these two pre-deploy a new VCSA and import data in second step) this works as well: Start the wizard with installation-option and select the deployment size you want. After first step connect to https://fqdn_of_new_vcsa:5480 and select upgrade or migration. 

Thanks for sharing! It is a great resource!

There are also problems with migrations (Windoes → Appliacne) of vCenter. Very often, wizard pre-selects a very large deployment despite it is not necessary. Sometimes it helps to clear some tables:

https://vnote42.net/2019/11/16/bad-deployment-and-storage-size-estimation-in-vcenter-migration-wizard/

Excellent article!!

Sometimes this can be helpful too:

For migrations and upgrades (these two pre-deploy a new VCSA and import data in second step) this works as well: Start the wizard with installation-option and select the deployment size you want. After first step connect to https://fqdn_of_new_vcsa:5480 and select upgrade or migration. 

LOL.

I guess it’s TNS (totally not supported), but a clever cheat for the wizard.. :grinning:

Sometimes this can be helpful too:

For migrations and upgrades (these two pre-deploy a new VCSA and import data in second step) this works as well: Start the wizard with installation-option and select the deployment size you want. After first step connect to https://fqdn_of_new_vcsa:5480 and select upgrade or migration. 

LOL.

I guess it’s TNS (totally not supported), but a clever cheat for the wizard.. :grinning:

To be honest, I think it is supported! Steps are the same as continuing in wizard. Connecting to port 5480 during installation/migration/upgrade is some kind of failback, when wizard was accidently closed.

Sometimes this can be helpful too:

For migrations and upgrades (these two pre-deploy a new VCSA and import data in second step) this works as well: Start the wizard with installation-option and select the deployment size you want. After first step connect to https://fqdn_of_new_vcsa:5480 and select upgrade or migration. 

LOL.

I guess it’s TNS (totally not supported), but a clever cheat for the wizard.. :grinning:

Update here, @MichaelSchroeder: VMware describes this procedure as a workaround in a similar configuration (with vSAN). So it is definitely a supported way!

https://kb.vmware.com/s/article/78914

Comment


Terms & Conditions