{"id":2482,"date":"2017-06-19T12:56:59","date_gmt":"2017-06-19T10:56:59","guid":{"rendered":"http:\/\/www.ewig-drohendes-versagen.de\/?p=2482"},"modified":"2017-06-19T12:58:35","modified_gmt":"2017-06-19T10:58:35","slug":"upgrade-vcenter-appliance-von-6-0-6-5","status":"publish","type":"post","link":"https:\/\/www.ewig-drohendes-versagen.de\/?p=2482","title":{"rendered":"Upgrade vCenter Appliance von 6.0 -> 6.5"},"content":{"rendered":"\n<!-- google_ad_section_start -->\n<p>Zu Beginn -> Backup \/ Snapshot des &#8222;alten&#8220; vCenters!!<\/p>\n<p>Einen ersten Eindruck des Setups kann man sich hier ansehen:<br \/>\n<a href=\"https:\/\/v-punk.com\/how-to-upgrade-vcsa-6-0-to-vcsa-6-5\/\">https:\/\/v-punk.com\/how-to-upgrade-vcsa-6-0-to-vcsa-6-5\/<\/a><\/p>\n<p>Wenn man die neue 6.5er Appliance mit dem &#8222;alten&#8220; Namen deployen m\u00f6chte &#8211; sollte man die alte VM vorher einfach umbenennen.<br \/>\nDann ist es nat\u00fcrlich auch nicht verkehrt einen anderen Datastore zu nehmen&#8230;<\/p>\n<p>Bevor es wirklich losgeht ->><br \/>\n1. \u00dcberpr\u00fcfen ob das root Password nicht abgelaufen ist<br \/>\n-> A general system error occurred: vix error codes = (1, 4294967293).<br \/>\n&#8211;>> <a href=\"https:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?language=en_US&#038;cmd=displayKC&#038;externalId=2147895\">https:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?language=en_US&#038;cmd=displayKC&#038;externalId=2147895<\/a><\/p>\n<p>2. Den Migrations Assistenten auf dem Server mit dem Update Manager starten<br \/>\n-> There is no MA extension for VUM available on source VC.<br \/>\n&#8211;>> <a href=\"http:\/\/pubs.vmware.com\/vsphere-65\/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-6A39008B-A78C-4632-BC55-0517205198C5.html\">http:\/\/pubs.vmware.com\/vsphere-65\/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-6A39008B-A78C-4632-BC55-0517205198C5.html<\/a><\/p>\n<p>3. Evtl. vorher mal pr\u00fcfen ob die Datenbank Sequenzen den richtigen Owner haben<br \/>\n-> Database in-place upgrade failed. Please see vcdb_inplace.err and vcdb_inplace.out for details.<br \/>\n&#8211;>> <a href=\"https:\/\/communities.vmware.com\/thread\/548057\">https:\/\/communities.vmware.com\/thread\/548057<\/a><\/p>\n<p>4. Fehler bei Schritt 3<br \/>\n-> Error attempting Vcintegrity Export file does not exist or is corrupted, abort import<br \/>\n&#8211;>> <a href=\"https:\/\/communities.vmware.com\/thread\/546958\">https:\/\/communities.vmware.com\/thread\/546958<\/a><br \/>\n&#8212;>>>> Bei mir hat ein Reboot der neuen Appliance zumindest eine 6.5er Appliance zur\u00fcckgelassen auf der alles bis auf den Update Manager migriert war&#8230;<\/p>\n\n<!-- google_ad_section_end -->\n","protected":false},"excerpt":{"rendered":"<p>Zu Beginn -> Backup \/ Snapshot des &#8222;alten&#8220; vCenters!! Einen ersten Eindruck des Setups kann man sich hier ansehen: https:\/\/v-punk.com\/how-to-upgrade-vcsa-6-0-to-vcsa-6-5\/ Wenn man die neue 6.5er Appliance mit dem &#8222;alten&#8220; Namen deployen m\u00f6chte &#8211; sollte man die alte VM vorher einfach umbenennen. Dann ist es nat\u00fcrlich auch nicht verkehrt einen anderen Datastore zu nehmen&#8230; Bevor es [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"enabled":false},"version":2}},"categories":[16,20],"tags":[45,52,46,71],"class_list":["post-2482","post","type-post","status-publish","format-standard","hentry","category-edv-probleme","category-esx","tag-vcenter","tag-vmware","tag-vsphere","tag-work"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/peux2-E2","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=\/wp\/v2\/posts\/2482","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2482"}],"version-history":[{"count":4,"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=\/wp\/v2\/posts\/2482\/revisions"}],"predecessor-version":[{"id":2487,"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=\/wp\/v2\/posts\/2482\/revisions\/2487"}],"wp:attachment":[{"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2482"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2482"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ewig-drohendes-versagen.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2482"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}