VMware Cloud Community
DanielMrkos
Contributor
Contributor
Jump to solution

VCSA 6.5U1 to 6.7U1 upgrade - wrong source VCSA storage size detected

Hi,

I am trying to upgrade from VCSA 6.5U1 to 6.7U1, but I can't select "tiny" deployment size with "default" storage option only large or x-large, because my source VCSA is detected with 470GB storage, which is not true. Source VCSA has only 250GB storage with thick provision lazy zeroed type. I tried restart VCSA and launch upgrade to version 6.7 instead of 6.7U1, but upgrade setup always detects wrong size.

Can someone tell me, how to fix this? Screenshots are in attachment.

Thank you very much.

Reply
0 Kudos
1 Solution

Accepted Solutions
DanielMrkos
Contributor
Contributor
Jump to solution

Problem solved. Old temporary snapshot from Veeam had about 200GB in size. I deleted it and now it is OK.

View solution in original post

Reply
0 Kudos
3 Replies
daphnissov
Immortal
Immortal
Jump to solution

You're probably going to have to purge some data from your source vCSA before attempting the upgrade, because otherwise it won't suggest smaller storage footprints for it. If you search, there are several KBs that can help here. The main offender is the table(s) containing SEAT data.

Reply
0 Kudos
DanielMrkos
Contributor
Contributor
Jump to solution

But my VCSA has lot of free space. So even if I run a cleanup, I won't free a lot.

Space.png

Reply
0 Kudos
DanielMrkos
Contributor
Contributor
Jump to solution

Problem solved. Old temporary snapshot from Veeam had about 200GB in size. I deleted it and now it is OK.

Reply
0 Kudos