vCenter upgrade from 6.5 U2b to 6.7 -- X-Large is the only size option

[DawitBirhanu]

Hi,

While trying to upgrade VCSA from 6.5 U2b to 6.7, X-Large is the only size option available. But my setup is relatively small as you can see below.

VCSA configured with external PSC

VCSA vCenter

Version: 6.5.0.21000

2 vCPUs

10GB RAM

Storage :

root@vc1 [ / ]# df -h

Filesystem                                Size  Used Avail Use% Mounted on

devtmpfs                                  4.9G     0  4.9G   0% /dev

tmpfs                                     4.9G   24K  4.9G   1% /dev/shm

tmpfs                                     4.9G  708K  4.9G   1% /run

tmpfs                                     4.9G     0  4.9G   0% /sys/fs/cgroup

/dev/sda3                                  11G  5.0G  5.1G  50% /

tmpfs                                     4.9G  1.2M  4.9G   1% /tmp

/dev/mapper/log_vg-log                    9.8G  1.5G  7.8G  16% /storage/log

/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   23M  9.2G   1% /storage/imagebuilder

/dev/mapper/dblog_vg-dblog                 15G  519M   14G   4% /storage/dblog

/dev/mapper/updatemgr_vg-updatemgr         99G  121M   94G   1% /storage/updatemgr

/dev/mapper/core_vg-core                   25G   45M   24G   1% /storage/core

/dev/sda1                                 120M   28M   87M  25% /boot

/dev/mapper/db_vg-db                      9.8G  130M  9.1G   2% /storage/db

/dev/mapper/netdump_vg-netdump            985M  1.3M  932M   1% /storage/netdump

/dev/mapper/autodeploy_vg-autodeploy      9.8G   23M  9.2G   1% /storage/autodeploy

/dev/mapper/seat_vg-seat                  542G  190M  514G   1% /storage/seat

VCSA PSC

========

Version: 6.5.0.21000

2 vCPUs

4GB RAM

Storage:

root@psc1 [ / ]# df -h

Filesystem                                Size  Used Avail Use% Mounted on

devtmpfs                                  2.0G     0  2.0G   0% /dev

tmpfs                                     2.0G  4.0K  2.0G   1% /dev/shm

tmpfs                                     2.0G  684K  2.0G   1% /run

tmpfs                                     2.0G     0  2.0G   0% /sys/fs/cgroup

/dev/sda3                                  11G  3.4G  6.8G  33% /

tmpfs                                     2.0G  680K  2.0G   1% /tmp

/dev/mapper/updatemgr_vg-updatemgr        6.8M   50K  6.3M   1% /storage/updatemgr

/dev/mapper/log_vg-log                    9.8G  944M  8.3G  11% /storage/log

/dev/mapper/netdump_vg-netdump            6.8M   50K  6.3M   1% /storage/netdump

/dev/mapper/core_vg-core                  9.8G   23M  9.2G   1% /storage/core

/dev/mapper/seat_vg-seat                  6.8M   50K  6.3M   1% /storage/seat

/dev/mapper/db_vg-db                      9.8G   31M  9.2G   1% /storage/db

/dev/mapper/autodeploy_vg-autodeploy      6.8M   50K  6.3M   1% /storage/autodeploy

/dev/mapper/dblog_vg-dblog                6.8M   50K  6.3M   1% /storage/dblog

/dev/mapper/imagebuilder_vg-imagebuilder  6.8M   50K  6.3M   1% /storage/imagebuilder

/dev/sda1                                 120M   28M   87M  25% /boot

What do I need to do to get other size choices?

[Vijay2027 · Accepted solution]

/dev/mapper/seat_vg-seat                  542G  190M  514G   1% /storage/seat

/storage/seat mount is 542GB. I think the only option is to go for xLarge.

May be you could use converter to shrink vol size edit the vmx file pointing to the new vmdk..

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

[diegodco31]

Hi

Deployment sizes will not be available if the disk size of any vCenter Server Appliance partition is greater than the threshold for that deployment size.

VMware Knowledge Base

[Levin1]

Hi

In my case on option "Storage size" was only "X-Large" available. It was because of an active snapshot.

As I removed the snap, i was able to choose "large"