{"id":1013,"date":"2021-02-10T15:43:29","date_gmt":"2021-02-10T14:43:29","guid":{"rendered":"https:\/\/vblog.hochsticher.de\/?p=1013"},"modified":"2023-03-31T19:57:01","modified_gmt":"2023-03-31T17:57:01","slug":"vcenter-7-0-u1-upgrade-stumbling-blocks","status":"publish","type":"post","link":"https:\/\/vblog.hochsticher.de\/?p=1013","title":{"rendered":"vCenter 7.0 U1 upgrade stumbling blocks"},"content":{"rendered":"\n

Recently I upgraded my vCenter from Version 6.7 U3 17138064 to Version 7.0 U1. During deployment I hit the first issue.<\/p>\n\n\n\n\n\n\n\n

As you may know, if you upgrade from a VCSA (vCenter Server Appliance) you can’t change the Deployment or Storage size. This may cause in too small Partitions for your new vCenter.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

You see the Upgrade Wizzard in the middle of Stage 1. In Stage 2, after the new deployed vCenter came up, the Wizzard showed me the following Error Message:<\/p>\n\n\n\n

Insufficient space on the target appliance partition to accommodate all the import data for upgrade data option ‘core’.
Do one of the following: — Select an upgrade data option that requires less space than option ‘core’. — Increase the size of the insufficient partitions. — Delete the appliance VM and re-deploy with a larger deployment size.<\/p>\n\n\n\n

In KB https:\/\/kb.vmware.com\/s\/article\/78515<\/a> the Partitions are described. My first thought about the “Core” in the Error Message is to expand the Core Partition which is VMDK #4. But that doesn’t helped me out. VMware Support pointed me to KB https:\/\/kb.vmware.com\/s\/article\/51981<\/a>. This was not the solution, but get me in the right direction. <\/p>\n\n\n\n

I checked the Partition \/storage\/db. This is residing on VMDK #6. I expanded this disk and executed the following command in the new vCenter via SSH Session.<\/p>\n\n\n\n

Command> com.vmware.appliance.system.storage.resize <\/code><\/p>\n\n\n\n

(also described here: https:\/\/kb.vmware.com\/s\/article\/2145603<\/a>)<\/p>\n\n\n\n

After that, I was able to continue the Deployment Wizzard and got to vCenter 7 Update 1 \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"

Recently I upgraded my vCenter from Version 6.7 U3 17138064 to Version 7.0 U1. During deployment I hit the first issue.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[10,7],"tags":[],"class_list":["post-1013","post","type-post","status-publish","format-standard","hentry","category-vcenter","category-vsphere"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=\/wp\/v2\/posts\/1013","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1013"}],"version-history":[{"count":5,"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=\/wp\/v2\/posts\/1013\/revisions"}],"predecessor-version":[{"id":1115,"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=\/wp\/v2\/posts\/1013\/revisions\/1115"}],"wp:attachment":[{"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1013"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1013"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vblog.hochsticher.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1013"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}