vCenter 7 to 8 Large Disk

[packerprogramme]

I upgraded my vCenter server to 8 and during the installation I could select tiny for the deployment size (i'm 3 hosts and less than 20 VM's). But, I couldn't select default as the disk size. My only options were large and extra large. I didn't think it was a big deal, but when the upgrade completed, my disk was 2TB! That is unreasonably large for my environment. I saw a kb on how to handle it during an upgrade, but mine is complete. 

I thought about adding a new vCenter and moving my hosts over. This is licensed with the new vSphere+ cloud license and when I went to move the first host I got a very unfriendly warning about my license (the new vCenter naturally isn't licensed yet. I haven't seen any good documentation on doing that so I backed up and came here. Any ideas? 

[a_p_]

Unless I misunderstand vSphere+ licensing, you do not need to license vCenter Server separately.
In that case you may simply follow https://docs.vmware.com/en/VMware-vSphere+/services/vsphereplus-getting-started/GUID-450DE67B-1A89-4890-97CD-F116BFD38801.html for the newly deployed vCenter Server.

Out of curiosity, would you mind to share the warning message you got.

André

[packerprogramme]

As I was typing this I realized I should have written down the exact message. It was stating that the host I was adding is licensed via another vsphere and would lose that license when moved. To license vsphere+ you have a cloud gateway that phones home. I originally added the hosts then licensed by connecting my vcenter to the gateway. I’m not sure if I move the hosts to another vcenter and try to license again it it will pull additional cpu licenses. I was hoping there may be another way. I’m thinking now of making a backup of my current vcenter and restoring it to an appropriately sized box. 

[packerprogramme]

 Below are the warnings. I have to choose a license to assign to the host. Since this is vphere+ the license is attached to another vcenter through the subscription. If I choose the current license I the following:

• The license is present in another vCenter Server system. If you assign the license, the licensing configuration will become non-compliant.
• Cannot decode the licensed features on the host. Changing its current license might fail or some features might become unavailable.

If I choose to apply the evaluation license I get:

 

• You are about to change the embedded OEM licenses of some assets and you might be unable to assign back these licenses at a later stage. Contact your hardware vendor for confirmation.
• The license expires in 52 days.

So, I don't know which route to go and if I will be able to easily add this new vcenter to my vsphere+ subscription without messing up my license. 

 

[a_p_]

I would expect that if a host gets removed from the original environment, that the license count will be adjusted accordingly. However, I can't tell you for sure, and suggest that you - unless someone else can answer this question here on VMTN - open a support case with VMware.

All that licensing stuff nowadays somehow reminds me of Asterix and Obelix "The Place That Sends You Mad"

André

[Mark Edwards]

 When selecting the Tiny deployment, the Default Storage option is 579 GB

As this was an upgrade, is it possible your total disk was already larger than 579GB, hence why default wasn't offered?

HTH

 

[packerprogramme]

 it’s a bug that occurs when upgrading. It incorrectly determines size based on datastore. This article explains and gives a solution during upgrade, but not after upgrade. My disk was super small as I only had a couple vms built so far.

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

[packerprogramme]

I wanted to update with my solution. I contacted support and the in article https://kb.vmware.com/s/article/78914 was still the solution.

 

• Powered off VCSA 8
• powered on VCSA 7 (good thing I kept it)
• Ran VCSA INSTALL not upgrade for stage 1
• Select appropriate vm size
• At the end of stage one do not continue. Take snapshot.
• Launch https://fqdn:5480. and select upgrade for stage 2. 
  
  

The process worked with minimal issue. I had one host I had to remove and add back to my HA cluster. This a summary, follow kn for details. 

[virtual-power]

That process works.
Keep in mind that the new VCSA needs to have enough space to accommodate the data imported from the source vCSA . Depending on the deployment sizing the partition size changes. So make sure to check that before following https://kb.vmware.com/s/article/78914.