{"id":19916,"date":"2017-02-27T09:00:11","date_gmt":"2017-02-27T08:00:11","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=19916\/"},"modified":"2023-07-16T11:28:13","modified_gmt":"2023-07-16T09:28:13","slug":"vmware-vcsa-6-0-to-6-5-upgrade-deploy-vcsa-pt-1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-0-to-6-5-upgrade-deploy-vcsa-pt-1\/","title":{"rendered":"VMware VCSA 6.0 to 6.5 upgrade: deploy VCSA - pt.1"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-20193 size-full\" title=\"vcsa60to65upgdeployvcsa01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa01.jpg\" alt=\"vcsa60to65upgdeployvcsa01\" width=\"602\" height=\"202\" \/><\/p>\n<p>VMware introduced in vSphere 6.5 the <strong>upgrade tool<\/strong> that allows the upgrade\u00a0of an\u00a0existing VCSA\u00a0to version 6.5 with a simple\u00a0procedure.<\/p>\n<p>The upgrade procedure can be applied to <strong>vCenter Server version 5.5 or 6.0<\/strong> and <strong>Platform Services Controller Appliance 6.0<\/strong>. Two stages are involved during the upgrade process:<\/p>\n<p><!--more--><\/p>\n<ul>\n<li>deployment of the new VCSA<\/li>\n<li>copy of the configuration from source vCenter Server<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20194 size-large\" title=\"vcsa60to65upgdeployvcsa02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa02-600x382.jpg\" alt=\"vcsa60to65upgdeployvcsa02\" width=\"600\" height=\"382\" \/><\/p>\n<p>Keep in mind that the\u00a0<strong>upgrade process doesn't delete<\/strong> the old vCenter Server and its configuration but simply copies data to the new VCSA and then powers the source vCenter off. This allows to quickly restore the old vCenter Server if the upgrade process fails.<\/p>\n<p>&nbsp;<\/p>\n<h2>Blog Series<\/h2>\n<p>VMware VCSA 6.0 to 6.5 upgrade: deploy VCSA - pt.1<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-0-to-6-5-upgrade-data-copy-pt-2\/\">VMware VCSA 6.0 to 6.5 upgrade: data copy - pt.2<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Prepare the environment<\/h2>\n<p>To perform a successful upgrade,\u00a0there are <strong>two main prerequisites<\/strong> that must be met:<\/p>\n<ul>\n<li>The cluster where the source VCSA resides has the <strong>DRS<\/strong> not set to <strong>Fully Automated<\/strong><\/li>\n<li>If the VCSA uses an external <strong>Update Manager<\/strong> you need to run the <strong>Migration Assistant<\/strong><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4><\/h4>\n<h4>Disable Fully Automated DRS<\/h4>\n<p>During the upgrade process, the cluster where the ESXi host that manages the source vCenter Server resides must be configured to have the DRS not set to <strong>Fully Automated<\/strong>.<\/p>\n<p>From the vSphere Web Client, right click the cluster to configure and select <strong>Settings<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20195 size-full\" title=\"vcsa60to65upgdeployvcsa03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa03.jpg\" alt=\"vcsa60to65upgdeployvcsa03\" width=\"532\" height=\"690\" \/><\/p>\n<p>Access the<strong> Manage &gt; Settings<\/strong> tab and select the <strong>vSphere DRS<\/strong> option. Note that in this example the <strong>DRS Automation<\/strong> field is set as <strong>Fully Automated<\/strong>. Click <strong>Edit<\/strong> to change the DRS settings.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20196 size-full\" title=\"vcsa60to65upgdeployvcsa04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa04.jpg\" alt=\"vcsa60to65upgdeployvcsa04\" width=\"566\" height=\"516\" \/><\/p>\n<p>Set the <strong>DRS Automation<\/strong> field as <strong>Manual<\/strong> and click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20197 size-large\" title=\"vcsa60to65upgdeployvcsa05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa05-600x389.jpg\" alt=\"vcsa60to65upgdeployvcsa05\" width=\"600\" height=\"389\" \/><\/p>\n<p>The DRS is now set as <strong>Manual<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20198 size-full\" title=\"vcsa60to65upgdeployvcsa06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa06.jpg\" alt=\"vcsa60to65upgdeployvcsa06\" width=\"566\" height=\"516\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Run the Migration-Assistant<\/h4>\n<p>If the VCSA to migrate\u00a0uses an <strong>external\u00a0Update Manager<\/strong>, the\u00a0Migration Assistant must be running on the <strong>source Update Manager machine<\/strong>.<\/p>\n<p>This tool <strong>facilitates the migration<\/strong> of the Update Manager server and database to the new upgraded VCSA. By default the Migration Assistant uses <strong>port 9123<\/strong> but if the port is already in use by another service, it automatically finds a <strong>different free port<\/strong> to use.<\/p>\n<p>Log in to the source Update Manager machine as an administrator and <strong>copy the migration-assistant<\/strong> directory from the VCSA\u00a0Installer package.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20199 size-full\" title=\"vcsa60to65upgdeployvcsa07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa07.jpg\" alt=\"vcsa60to65upgdeployvcsa07\" width=\"588\" height=\"268\" \/><\/p>\n<p>Double-click <strong>VMware-Migration-Assistant.exe<\/strong>\u00a0to run the tool.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20200 size-large\" title=\"vcsa60to65upgdeployvcsa08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa08-600x423.jpg\" alt=\"vcsa60to65upgdeployvcsa08\" width=\"600\" height=\"423\" \/><\/p>\n<p>Type the vCenter Single Sign-On <strong>administrator password<\/strong>. If no errors are displayed <strong>after the pre-checks<\/strong>, the source Update Manager system is ready for the upgrade.\u00a0Leave the Migration Assistant <strong>window open<\/strong> until the upgrade of the VCSA\u00a0finishes.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20201 size-large\" title=\"vcsa60to65upgdeployvcsa09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa09-600x334.jpg\" alt=\"vcsa60to65upgdeployvcsa09\" width=\"600\" height=\"334\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Migrate the VCSA<\/h2>\n<p>Mount the VCSA\u00a0Installer <strong>ISO file<\/strong> and run the installer.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20202 size-large\" title=\"vcsa60to65upgdeployvcsa10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa10-600x337.jpg\" alt=\"vcsa60to65upgdeployvcsa10\" width=\"600\" height=\"337\" \/><\/p>\n<h4>Stage 1\u00a0deployment<\/h4>\n<p>From the vCenter Server Appliance installer, click <strong>Upgrade<\/strong> option to upgrade an existing\u00a0VCSA.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20203 size-large\" title=\"vcsa60to65upgdeployvcsa11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa11-600x452.jpg\" alt=\"vcsa60to65upgdeployvcsa11\" width=\"600\" height=\"452\" \/><\/p>\n<p>Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20204 size-large\" title=\"vcsa60to65upgdeployvcsa12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa12-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa12\" width=\"600\" height=\"362\" \/><\/p>\n<p>Accept the EULA then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20205 size-large\" title=\"vcsa60to65upgdeployvcsa13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa13-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa13\" width=\"600\" height=\"362\" \/><\/p>\n<p>Specify <strong>Source appliance<\/strong> parameters and the <strong>ESXi host that manages the source appliance<\/strong>. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20206 size-large\" title=\"vcsa60to65upgdeployvcsa14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa14-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa14\" width=\"600\" height=\"362\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to accept the self signed SSL certificate.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20207 size-full\" title=\"vcsa60to65upgdeployvcsa15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa15.jpg\" alt=\"vcsa60to65upgdeployvcsa15\" width=\"450\" height=\"350\" \/><\/p>\n<p>If you receive this error message it means the <strong>Migration Assistant\u00a0is not running<\/strong>\u00a0on the VUM server. Run the tool and try again.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20208 size-large\" title=\"vcsa60to65upgdeployvcsa16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa16-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa16\" width=\"600\" height=\"362\" \/><\/p>\n<p>Specify the target ESXi host to deploy the appliance and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20209 size-large\" title=\"vcsa60to65upgdeployvcsa17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa17-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa17\" width=\"600\" height=\"362\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to accept the host's SSL self signed certificate.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20210 size-full\" title=\"vcsa60to65upgdeployvcsa18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa18.jpg\" alt=\"vcsa60to65upgdeployvcsa18\" width=\"400\" height=\"300\" \/><\/p>\n<p>Type the <strong>VM\u00a0name<\/strong> and specify the <strong>Root password<\/strong>. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20211 size-large\" title=\"vcsa60to65upgdeployvcsa19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa19-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa19\" width=\"600\" height=\"362\" \/><\/p>\n<p>Based on your environment, specify the <strong>Deployment and Storage size<\/strong>\u00a0then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20212 size-large\" title=\"vcsa60to65upgdeployvcsa20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa20-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa20\" width=\"600\" height=\"362\" \/><\/p>\n<p>Select the desired storage to save the VCSA and <strong>Enable Thin Disk Mode<\/strong> option to save space. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20213 size-large\" title=\"vcsa60to65upgdeployvcsa21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa21-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa21\" width=\"600\" height=\"362\" \/><\/p>\n<p>Insert the network parameters and click <strong>Next<\/strong>. The assigned <strong>IP address is temporary<\/strong> and used during the upgrade process only. When the upgrade has completed the new VCSA will have same IP of the source VCSA.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20214 size-large\" title=\"vcsa60to65upgdeployvcsa22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa22-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa22\" width=\"600\" height=\"362\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to start the deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20215 size-large\" title=\"vcsa60to65upgdeployvcsa23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa23-600x362.jpg\" alt=\"vcsa60to65upgdeployvcsa23\" width=\"600\" height=\"362\" \/><\/p>\n<p>The appliance is being deployed to the target host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20216 size-large\" title=\"vcsa60to65upgdeployvcsa24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa24-600x354.jpg\" alt=\"vcsa60to65upgdeployvcsa24\" width=\"600\" height=\"354\" \/><\/p>\n<p>When the process has been completed, click <strong>Continue<\/strong> to proceed with <strong>stage 2<\/strong>.\u00a0You can also close the wizard and continue the installation later on via browser typing the address <strong>https:\/\/IPAddress_appliance:5480<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20217 size-large\" title=\"vcsa60to65upgdeployvcsa25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/02\/vcsa60to65upgdeployvcsa25-600x354.jpg\" alt=\"vcsa60to65upgdeployvcsa25\" width=\"600\" height=\"354\" \/><\/p>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-0-to-6-5-upgrade-data-copy-pt-2\/\">Part 2<\/a> will show stage 2 of the VCSA upgrade procedure.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>VMware introduced in vSphere 6.5 the upgrade tool that allows the upgrade\u00a0of an\u00a0existing VCSA\u00a0to version 6.5 with a simple\u00a0procedure. The upgrade procedure can be applied to vCenter Server version 5.5 or 6.0 and Platform Services Controller Appliance 6.0. Two stages are involved during the upgrade process:<\/p>\n","protected":false},"author":3,"featured_media":20193,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[876,1551,699],"class_list":["post-19916","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-upgrade-en","tag-vcsa","tag-vmware-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/19916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=19916"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/19916\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/20193"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=19916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=19916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=19916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}