The VCSA Installation wizard incorrectly detects the storage deployment size of the source vCenter during migration or upgrade
search cancel

The VCSA Installation wizard incorrectly detects the storage deployment size of the source vCenter during migration or upgrade

book

Article ID: 326287

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • While trying to upgrade from vCenter Server 6.5 to 6.7 or from 6.5/6.7 to 7.0 or 8.0, the upgrade wizard might incorrectly detect the storage deployment size for the source vCenter Server.
  • For example, the source vCenter Server was deployed with a "Normal" storage size, but the installer only offers "Large" or "X-Large" as Storage size options.
  • Or the source vCenter Server was deployed with a "Large" storage size, but in the installer only the "X-Large" storage configuration is available.


Environment

VMware vCenter Server 6.5.x
VMware vCenter Server 7.0.x
VMware vCenter Server 8.0
VMware vCenter Server 6.7.x

Cause

This can happen when:
  1. the source vCenter is deployed on a VSAN datastore with the FTT (failure to tolerate) value set to 1 or higher.
The VCSA Installer uses the Provisioned Space of the VM to configure the Storage size during deployment. On a VSAN Datastore the Provisioned Space of the VM includes the space used by its mirror/raid components and hence would be larger than the VCSA VM's used space.
For example, 173GB used space would be 346GB Provisioned space for a VCSA VM with FTT=1 (Mirror)  VSAN storage policy. If the Provisioned Space is greater than the "Default" storage size for the selected VCSA size, you would only see the next larger storage options in the drop-down.
  1. more than 50 percent of the space available in either of the /storage/seat, /storage/db or /storage/updatemgr partitions is in use in the source vCenter Server appliance

Resolution

This is a known issue and VMware Engineering is working on a fix in a future release.

Workaround:
Note: while there are articles available on the Internet, describing how to shrink the disks of the VCSA after you finished the upgrade, please be aware that none of them are officially supported.

Instead, to work around the issue, you can follow this two-stages approach during upgrade:
 

Stage 1: 

  1. Open the VCSA installation wizard.
  2. Instead of "Upgrade", select the "Install" Option.
  3. In "Select Deployment Option" choose "Small" or "Medium" as the "Deployment size", similar to how the source vCenter Server was deployed. Notice that the "Storage Size" field is set to "Default":image.png
  4. Provide necessary details like the Network configuration etc.
  5. Finish stage 1 by providing other details (Note: Node type (embedded/external psc etc) has to be same as the source VC)
  6. Note down the IP of the appliance and exit the installer.
 

Stage 2:

  1. Open VAMI UI webpage using this URL https://<New_APPLIANCE_IP>:5480
  2. Login using the root credentials used in stage 1.
  3. Select the "Upgrade" option
  4. Provide the source (old) vCenter details.
Note: Use the IP of Source VCenter instead of the FQDN because it may not resolve in the Network and the FQDN will be pointing to the source VCenter.
  1. Provide the information required by the upgrade wizard.
  2. Start the upgrade process.
  3. After the upgrade is complete, connect to the Appliance and confirm all previous settings are in-place.


Additional Information

Note: The same approach can be used to downsize a VCSA during the upgrade.
For example, consider a scenario where the VCSA was originally deployed with XLarge storage size, and the new VCSA should only have a "Large" or "Normal" storage size. However, keep in mind that the new VCSA needs to have enough storage space to accommodate the data imported from the source appliance.

See also: Deployment Size options are not available when upgrading or migrating to vCenter Server Appliance 6.5

Powered by Wolken Software