{"id":20189,"date":"2017-03-01T09:00:25","date_gmt":"2017-03-01T08:00:25","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=20189\/"},"modified":"2023-07-16T11:28:13","modified_gmt":"2023-07-16T09:28:13","slug":"vmware-vcsa-6-0-to-6-5-upgrade-data-copy-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-0-to-6-5-upgrade-data-copy-pt-2\/","title":{"rendered":"VMware VCSA 6.0 to 6.5 upgrade: data copy - pt.2"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-20234 size-full\" title=\"vcsa60to65datacopy01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy01.jpg\" alt=\"vcsa60to65datacopy01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Deployed the VCSA 6.5, the upgrade process continues with Stage 2 where <strong>data are copied<\/strong> from source to target vCenter Server Appliance.<\/p>\n<p>With the result of the upgrade procedure, the new vCenter Server will have <strong>same hostname and IP address<\/strong> of the source VCSA avoiding services interruption.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Blog Series<\/h2>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-0-to-6-5-upgrade-deploy-vcsa-pt-1\/\">VMware VCSA 6.0 to 6.5 upgrade: deploy VCSA - pt.<\/a>1<br \/>\nVMware VCSA 6.0 to 6.5 upgrade: data\u00a0copy - pt.2<\/p>\n<p>&nbsp;<\/p>\n<h2>Stage 2\u00a0data copy<\/h2>\n<p>Completed Stage 1, Stage 2 can be finalized in two ways:<\/p>\n<ul>\n<li>using the <strong>vCenter Server Appliance Installer <\/strong><\/li>\n<li>accessing the\u00a0<strong>vCenter Server Appliance Management Interface<\/strong> typing in your preferred\u00a0browser the address<strong> https:\/\/IPAddress_VCSA:5480<\/strong><\/li>\n<\/ul>\n<p>In the example, the\u00a0vCenter Server Appliance Installer is used to proceed\u00a0with Stage 2. Click <strong>Next<\/strong>\u00a0to begin.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20235 size-large\" title=\"vcsa60to65datacopy02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy02-600x359.jpg\" alt=\"vcsa60to65datacopy02\" width=\"600\" height=\"359\" \/><\/p>\n<p>The system performs some <strong>pre-upgrade checks<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20236 size-full\" title=\"vcsa60to65datacopy03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy03.jpg\" alt=\"vcsa60to65datacopy03\" width=\"312\" height=\"158\" \/><\/p>\n<p>A warning reminds you that the cluster where the ESXi host that manages the new VCSA resides has <strong>not to be set as Fully Automated<\/strong>. Check out <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-0-to-6-5-upgrade-deploy-vcsa-pt-1\/\">part 1<\/a>\u00a0of the procedure for additional details. Other extensions installed in the source VCSA (<a href=\"https:\/\/nolabnoparty.com\/en\/pernixdata-fvp-3-5-architect-1-1-released\/\">PernixData FVP<\/a> in the example) should be double checked for compatibility with the new VCSA. Click <strong>Close<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20237 size-large\" title=\"vcsa60to65datacopy04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy04-600x386.jpg\" alt=\"vcsa60to65datacopy04\" width=\"600\" height=\"386\" \/><\/p>\n<p>The window shows the credentials inserted in Stage 1. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20238 size-large\" title=\"vcsa60to65datacopy05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy05-600x359.jpg\" alt=\"vcsa60to65datacopy05\" width=\"600\" height=\"359\" \/><\/p>\n<p>Select what data should be copied to the target VCSA then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20239 size-large\" title=\"vcsa60to65datacopy06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy06-600x359.jpg\" alt=\"vcsa60to65datacopy06\" width=\"600\" height=\"359\" \/><\/p>\n<p>Optionally you can join the <strong>CEIP<\/strong> program. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20240 size-large\" title=\"vcsa60to65datacopy07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy07-600x359.jpg\" alt=\"vcsa60to65datacopy07\" width=\"600\" height=\"359\" \/><\/p>\n<p>Thick <strong>I have backed up the source vCenter Server and all the required data from the database<\/strong>\u00a0option then click <strong>Finish<\/strong> to start the data copy process.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20241 size-large\" title=\"vcsa60to65datacopy08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy08-600x359.jpg\" alt=\"vcsa60to65datacopy08\" width=\"600\" height=\"359\" \/><\/p>\n<p>Click <strong>OK<\/strong> to confirm.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20242 size-full\" title=\"vcsa60to65datacopy09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy09.jpg\" alt=\"vcsa60to65datacopy09\" width=\"498\" height=\"173\" \/><\/p>\n<p>The system starts copying the data from source VCSA.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20243 size-large\" title=\"vcsa60to65datacopy10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy10-600x355.jpg\" alt=\"vcsa60to65datacopy10\" width=\"600\" height=\"355\" \/><\/p>\n<p>Looking at the <strong>Migration Assistant<\/strong>\u00a0installed in the VUM server, the export process is in progress.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20244 size-large\" title=\"vcsa60to65datacopy11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy11-600x322.jpg\" alt=\"vcsa60to65datacopy11\" width=\"600\" height=\"322\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>VMware Identity Manager Service error<\/h4>\n<p>During the copy process you may experience this error related to the\u00a0<strong>vmidentity-firstboot.py<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20245 size-large\" title=\"vcsa60to65datacopy12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy12-600x386.jpg\" alt=\"vcsa60to65datacopy12\" width=\"600\" height=\"386\" \/><\/p>\n<p>The procedure <strong>stops\u00a0at 5% of step 2<\/strong> while the system tries starting the <strong>VMware Identity Manager Service<\/strong>. Clicking on <strong>Retry<\/strong> button,\u00a0the problem is not solved and same error occurs again. Click <strong>Close<\/strong> to exit the wizard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20246 size-large\" title=\"vcsa60to65datacopy13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy13-600x355.jpg\" alt=\"vcsa60to65datacopy13\" width=\"600\" height=\"355\" \/><\/p>\n<p>This error doesn't give any chance to continue the upgrade and you have to\u00a0<strong>start the entire procedure<\/strong> from the beginning.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20247 size-large\" title=\"vcsa60to65datacopy14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy14-600x246.jpg\" alt=\"vcsa60to65datacopy14\" width=\"600\" height=\"246\" \/><\/p>\n<p>To fix this matter, you have to add <strong>localhost.localdom localhost<\/strong> in the <em>\/etc\/hosts<\/em> file of the new VCSA as suggested by the\u00a0<a href=\"https:\/\/kb.vmware.com\/kb\/2147908\" target=\"_blank\" rel=\"noopener\">KB2147908<\/a>\u00a0article <strong>before Stage 2<\/strong> takes place. When <strong>Stage 1 has completed<\/strong>, from the vSphere Web Client of the source VCSA right click the target VCSA and select <strong>Open Console<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20248 size-full\" title=\"vcsa60to65datacopy15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy15.jpg\" alt=\"vcsa60to65datacopy15\" width=\"593\" height=\"442\" \/><\/p>\n<p>Press <strong>Alt+F1<\/strong> and log in with <strong>root credentials<\/strong>.\u00a0Run this command to <strong>enable SSH<\/strong>:<\/p>\n<p><span style=\"color: #0000ff;\"># ssh.set --enabled true<\/span><\/p>\n<p>and this command to <strong>verify SSH<\/strong> is enabled:<\/p>\n<p><span style=\"color: #0000ff;\"># ssh.get<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20249 size-large\" title=\"vcsa60to65datacopy16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy16-600x459.jpg\" alt=\"vcsa60to65datacopy16\" width=\"600\" height=\"459\" \/><\/p>\n<p>Connect to the VCSA\u00a0with an <strong>SSH session<\/strong> and root credentials using the temporary IP Address specified during Stage 1 .<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20250 size-full\" title=\"vcsa60to65datacopy17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy17.jpg\" alt=\"vcsa60to65datacopy17\" width=\"452\" height=\"437\" \/><\/p>\n<p><strong>Enable the shell<\/strong> and run the following command to add <em>localhost.localdom localhost<\/em> to the <em>\/etc\/hosts<\/em> file:<\/p>\n<p><span style=\"color: #0000ff;\">Command&gt; shell<\/span><br \/>\n<span style=\"color: #0000ff;\"># echo \"::1 localhost.localdom localhost\" &gt;&gt; \/etc\/hosts<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20251 size-large\" title=\"vcsa60to65datacopy18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy18-600x379.jpg\" alt=\"vcsa60to65datacopy18\" width=\"600\" height=\"379\" \/><\/p>\n<p>Type the following command to verify if the parameter has been entered.<\/p>\n<p><span style=\"color: #0000ff;\"># cat \/etc\/hosts<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20252 size-large\" title=\"vcsa60to65datacopy19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy19-600x379.jpg\" alt=\"vcsa60to65datacopy19\" width=\"600\" height=\"379\" \/><\/p>\n<p>Continuing with Stage 2 of the deployment, I figure out the <strong>Applying network configuration<\/strong>\u00a0step erased the\u00a0entry\u00a0causing the same error again.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20253 size-large\" title=\"vcsa60to65datacopy20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy20-600x367.jpg\" alt=\"vcsa60to65datacopy20\" width=\"600\" height=\"367\" \/><\/p>\n<p>Adding the\u00a0<em>localhost.localdom localhost<\/em> to the <em>\/etc\/hosts<\/em>\u00a0as soon as Stage 2<strong> starts step 2<\/strong> fixed the issue.<\/p>\n<p><span style=\"color: #0000ff;\"># echo \"::1 localhost.localdom localhost\" &gt;&gt; \/etc\/hosts<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20254 size-large\" title=\"vcsa60to65datacopy21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy21-600x430.jpg\" alt=\"vcsa60to65datacopy21\" width=\"600\" height=\"430\" \/><\/p>\n<h4>Resume the data copy<\/h4>\n<p>After using the suggested fix, the installation continues.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20255 size-large\" title=\"vcsa60to65datacopy22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy22-600x355.jpg\" alt=\"vcsa60to65datacopy22\" width=\"600\" height=\"355\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Importing VMware vSphere Update Manager error<\/h4>\n<p>Another issue you may experience occurs in Stage 2 during the <strong>Importing VMware vSphere Update Manager data<\/strong> step. Also this error requires to <strong>start the overall upgrade procedure<\/strong> from the beginning.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20256 size-large\" title=\"vcsa60to65datacopy23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy23-600x355.jpg\" alt=\"vcsa60to65datacopy23\" width=\"600\" height=\"355\" \/><\/p>\n<p>To fix this problem, make sure the VMware vSphere Update Manager Service in the VUM server\u00a0<strong>runs with a dedicated account<\/strong> and not as <strong>Local System<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20257 size-large\" title=\"vcsa60to65datacopy24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy24-600x166.jpg\" alt=\"vcsa60to65datacopy24\" width=\"600\" height=\"166\" \/><\/p>\n<p>Start the upgrade once again and if no issues occur, after some minutes Stage 2 completes successfully. Click <strong>Close<\/strong> to exit the wizard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20258 size-large\" title=\"vcsa60to65datacopy25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy25-600x355.jpg\" alt=\"vcsa60to65datacopy25\" width=\"600\" height=\"355\" \/><\/p>\n<p>The new VCSA offers two ways to access vSphere:<\/p>\n<ul>\n<li>Using the classic\u00a0<strong>Flash-based<\/strong>\u00a0vSphere Web Client<\/li>\n<li>Using the new <strong>HTML5-based<\/strong> vSphere Web Client but with limited functionality<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20259 size-large\" title=\"vcsa60to65datacopy26\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy26-600x277.jpg\" alt=\"vcsa60to65datacopy26\" width=\"600\" height=\"277\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Access the new VCSA<\/h2>\n<p>Since the upgrade process copies the configuration from source to the target VCSA, the new vCenter Server will have <strong>same hostname and IP address<\/strong> of the source VCSA.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20260 size-large\" title=\"vcsa60to65datacopy27\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy27-600x106.jpg\" alt=\"vcsa60to65datacopy27\" width=\"600\" height=\"106\" \/><\/p>\n<p>To access the classic\u00a0<strong>Flash-based<\/strong>\u00a0vSphere Web Client, from your favorite browser type the address <strong>https:\/\/IPAddress_VCSA\/vsphere-client<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20265 size-large\" title=\"vcsa60to65datacopy28\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy28-600x439.jpg\" alt=\"vcsa60to65datacopy28\" width=\"600\" height=\"439\" \/><\/p>\n<p>To access the <strong>HTML5<\/strong><strong>-based<\/strong>\u00a0vSphere Web Client, type the address <strong>https:\/\/IPAddress_VCSA\/ui<\/strong>. Keep in mind that this client has <strong>limited functionality<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-20266 size-large\" title=\"vcsa60to65datacopy29\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/03\/vcsa60to65datacopy29-600x439.jpg\" alt=\"vcsa60to65datacopy29\" width=\"600\" height=\"439\" \/><\/p>\n<p>The upgrade procedure is now complete. For a <strong>fresh installation<\/strong> of the VCSA, check out <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcsa-6-5-deployment-pt1\/\">this post<\/a>.<\/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>Deployed the VCSA 6.5, the upgrade process continues with Stage 2 where data are copied from source to target vCenter Server Appliance. With the result of the upgrade procedure, the new vCenter Server will have same hostname and IP address of the source VCSA avoiding services interruption.<\/p>\n","protected":false},"author":3,"featured_media":20234,"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-20189","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\/20189","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=20189"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/20189\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/20234"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=20189"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=20189"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=20189"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}