Deployment Size options are not available when upgrading or migrating to vCenter Server Appliance 6.5
search cancel

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

book

Article ID: 345495

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
During the migration or upgrade to vCenter Server Appliance 6.5, some deployment sizes are not available for selection.

Environment

VMware vCenter Server 6.7.x
VMware vCenter Server Appliance 6.5.x
VMware vCenter Server 6.5.x

Cause

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.

Resolution

This issue is resolved in vCenter Server Appliance 6.5 Update 1, available at VMware Downloads.

Common areas where disk space can be reclaimed:

Accommodate the smaller deployment size the data that is being moved with the upgrade/migration will need to be reduced. Some common areas where disk space can be reclaimed are:

Inventory Service database

To reduce the size of the Inventory Service database reset the vpx data provider.

Large vCenter Server Database tables

One of the most common causes of large vCenter Server databases is excess event, task, and performance statistic data. To reduce the size of this data see Selective deletion of tasks, events, and historical performance data in vSphere 5.x and 6.x (2110031).
 
The VPX_TEXT_ARRAY table can also consume large amount of space. To check the space on this table, see VPX_TEXT_ARRAY table growing in size causes the vCenter Server database to run out of space (2005333).
 

Core Dumps

Ensure to clean up any dump files for the vCenter Server Appliance. These files will end in .dmp, and the largest core dumps are normally for the vpxd process. These dump can be found in /var/log/vmware/vpxd.
 

Excessive Logging

There are cases where the vCenter Server Appliance may have a large amount of space taken by logging (For example the SSO logs can consume a large amount of space). To remove these logs see /storage/log directory is full in vCenter Server Appliance 6.0 (2143565).
 
Note: To determine the disk space of the partitions on the vCenter Appliance run the following command from the vCenter Server Appliance shell:
 
df -h
 
For example:
 
df -h
 
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 11G 3.9G 6.4G 38% /
udev 4.0G 164K 4.0G 1% /dev
tmpfs 4.0G 40K 4.0G 1% /dev/shm
/dev/sda1 128M 38M 84M 31% /boot
/dev/mapper/core_vg-core 25G 2.7G 21G 12% /storage/core
/dev/mapper/log_vg-log 9.9G 2.5G 7.0G 26% /storage/log
/dev/mapper/db_vg-db 9.9G 214M 9.2G 3% /storage/db
/dev/mapper/dblog_vg-dblog 5.0G 379M 4.3G 8% /storage/dblog
/dev/mapper/seat_vg-seat 9.9G 9.4G 0 100% /storage/seat
/dev/mapper/netdump_vg-netdump 1001M 18M 932M 2% /storage/netdump
/dev/mapper/autodeploy_vg-autodeploy 9.9G 151M 9.2G 2% /storage/autodeploy
/dev/mapper/invsvc_vg-invsvc 5.0G 191M 4.5G 4% /storage/invsvc


Additional Information

The deployment size determines the amount of RAM, CPU, and partition sizes for the vCenter Server Appliance These values can be changed after upgrade, see Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5 (2145603).
VPX_TEXT_ARRAY table growing in size causes the vCenter Server database to run out of space
Selective deletion of tasks, events, and historical performance data in vSphere 5.x and 6.x
Resetting the VMware vCenter Server 6.0 Inventory Service's Individual Data Providers
Purging data from the VMware vCenter Server 5.5 Inventory Service's Individual Data Providers
/storage/log directory is full in vCenter Server Appliance 6.0
Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5

Powered by Wolken Software