{"id":706,"date":"2019-02-07T20:48:53","date_gmt":"2019-02-07T19:48:53","guid":{"rendered":"https:\/\/virtualguru.cz\/?p=706"},"modified":"2019-02-08T19:39:26","modified_gmt":"2019-02-08T18:39:26","slug":"upgrade-vcenter-server-6-5-na-6-7-a-jak-resit-nedostatek-mista","status":"publish","type":"post","link":"https:\/\/virtualguru.cz\/en\/2019\/02\/07\/upgrade-vcenter-server-6-5-na-6-7-a-jak-resit-nedostatek-mista\/","title":{"rendered":"Upgrade vCenter Server 6.5 na 6.7 a jak \u0159e\u0161it nedostatek m\u00edsta"},"content":{"rendered":"

Ji\u017e v\u00edce ne\u017e p\u016fl roku je na sv\u011bt\u011b nov\u00e1 verze vSphere 6.7 a v\u202fz\u00e1v\u011bru lo\u0148sk\u00e9ho roku se do\u010dkala i sv\u00e9ho prvn\u00edho velk\u00e9ho update U1. Jednou z\u202fnejv\u011bt\u0161\u00edch novinek t\u00e9to verze je u\u017eivatelsk\u00e9 rozhran\u00ed v\u202fHTML5, kter\u00e9 ji\u017e pokr\u00fdv\u00e1 100% funkcionality. V\u00edce o novink\u00e1ch se do\u010dtete v\u202fofici\u00e1ln\u00ed dokumentaci zde<\/a>.<\/p>\n

My si dnes projdeme krok za krokem cel\u00fd proces upgrade vCenter Server Appliance (vCSA) v\u202fGUI a uk\u00e1\u017eeme si, jak vy\u0159e\u0161it probl\u00e9m s\u202fnedostatkem m\u00edsta na zdrojov\u00e9m vCSA.<\/p>\n

Je\u0161t\u011b ne\u017e se samotnou migrac\u00ed za\u010dneme, m\u011bli bychom si ud\u011blat malou p\u0159\u00edpravu.<\/p>\n

    \n
  1. Zkontrolovat, jestli je podporov\u00e1n upgrade z verze, kterou m\u00e1me na verzi, kterou zam\u00fd\u0161l\u00edme, na str\u00e1nk\u00e1ch VMware Product Interoperability Matrices v z\u00e1lo\u017ece Upgrade Path<\/a>.<\/li>\n
  2. Ud\u011blat si p\u0159ehled z\u00e1vislost\u00ed dal\u0161\u00edch komponent, kter\u00e9 pou\u017e\u00edv\u00e1me, p\u0159i upgrade je d\u016fle\u017eit\u00e9 dodr\u017eet spr\u00e1vnou posloupnost upgrade jednotliv\u00fdch komponent, dobr\u00fdm vod\u00edtkem je KB53710<\/a>.<\/li>\n
  3. Ud\u011blat si p\u0159ehled stavu prost\u0159ed\u00ed, v prost\u0159ed\u00ed by nem\u011bly b\u00fdt p\u0159ed zah\u00e1jen\u00ed upgrade ide\u00e1ln\u011b \u017e\u00e1dn\u00e9 chyby. Zkontrolovat error logy, health status v management rozhran\u00ed vCSA, zapomenut\u00e9 snapshoty, atd … Dobr\u00fdm pomocn\u00edkem m\u016f\u017ee b\u00fdt RVTools<\/a>, pokud nem\u00e1te n\u00e1stroje z rodiny vRealize.<\/li>\n<\/ol>\n

    V tuto chv\u00edli budu p\u0159edpokl\u00e1dat, \u017ee m\u00e1te z\u00e1vislosti vy\u0159e\u0161eny a pust\u00edme se do upgrade samotn\u00e9ho vCSA. Postup tak\u00e9 p\u0159edpokl\u00e1d\u00e1 jednoduch\u00e9 nasazen\u00ed s integrovan\u00fdm PSC.<\/p>\n

    1.<\/strong> Spust\u00edme GUI instal\u00e1tor.<\/p>\n

    \"\"<\/a>Vybereme volbu Upgrade.<\/p>\n

    2.<\/strong> Upgrade proces je rozd\u011blen do dvou f\u00e1z\u00ed, prvn\u00ed je instalace samotn\u00e9ho nov\u00e9ho vCSA, ve druh\u00e9m se pak migruj\u00ed data z p\u016fvodn\u00edho vCSA do nov\u00e9ho.<\/p>\n

    \"\"<\/a>Zde je tedy pouze \u00favodn\u00ed obrazovka, na kter\u00e9 d\u00e1me NEXT.<\/p>\n

    3. <\/strong><\/p>\n

    \"\"<\/a>P\u0159e\u010dteme si a odsouhlas\u00edme licen\u010dn\u00ed podm\u00ednky, pak d\u00e1me NEXT.<\/p>\n

    4.<\/strong><\/p>\n

    \"\"<\/a>V tomto kroku vypln\u00edme IP nebo FQDN st\u00e1vaj\u00edc\u00edho vCSA a d\u00e1me CONNECT TO SOURCE.<\/p>\n

    \"\"<\/a>Rozbal\u00ed se n\u00e1m dal\u0161\u00ed pol\u00ed\u010dka, po\u017eadavek na opr\u00e1vn\u011bn\u00ed SSO admina a v doln\u00ed \u010d\u00e1sti po\u017eadavek na opr\u00e1vn\u011bn\u00ed ESXi hosta nebo vCentru, kde b\u011b\u017e\u00ed vCSA, kter\u00fd upgradujeme. Po vypln\u011bn\u00ed v\u0161ech \u00fadaj\u016f d\u00e1me NEXT.<\/p>\n

    5.<\/strong><\/p>\n

    \"\"<\/a>V tomto kroku vypln\u00edme \u00fadaje FQDN nebo IP a opr\u00e1vn\u011bn\u00ed k ESXi hostovi nebo vCentru, kam budeme nov\u00fd vCSA instalovat. Pot\u00e9 d\u00e1me NEXT.<\/p>\n

    6.<\/strong><\/p>\n

    \"\"<\/a>Vybereme slo\u017eku, do kter\u00e9 nov\u00fd vCSA za\u0159ad\u00edme a d\u00e1me NEXT.<\/p>\n

    7.<\/strong><\/p>\n

    \"\"<\/a>Zde vybereme cluster nebo hosta, odkud budou vCSA poskytov\u00e1ny zdroje a d\u00e1me NEXT.<\/p>\n

    8.<\/strong><\/p>\n

    \"\"<\/a>V tomto kroku vypln\u00edme VM n\u00e1zev nov\u00e9ho vCSA a heslo pro u\u017eivatele root samotn\u00e9 appliance. Pot\u00e9 d\u00e1me NEXT.<\/p>\n

    9.<\/strong><\/p>\n

    \"\"<\/a>Nyn\u00ed vybereme velikost vCSA. V pr\u016fvodci je tabulka, kter\u00e1 popisuje, jak\u00e9 zdroje budou t\u00e9 kter\u00e9 variant\u011b p\u0159i\u0159azeny. Pro rozhodnut\u00ed n\u00e1m sta\u010d\u00ed v\u011bd\u011bt, kolik host\u016f a kolik VM bude vCSA spravovat. Vyb\u00edr\u00e1me tak dle posledn\u00edch dvou sloupc\u016f podle vy\u0161\u0161\u00ed hodnoty. Pot\u00e9 d\u00e1me NEXT.<\/p>\n

    10.<\/strong><\/p>\n

    \"\"<\/a>V tomto kroku vybereme storage, kam budeme vCSA instalovat a jestli nov\u011b vytvo\u0159en\u00e9 disky maj\u00ed b\u00fdt v Thin provisioningu. Pot\u00e9 d\u00e1me NEXT.<\/p>\n

    11.<\/strong><\/p>\n

    \"\"<\/a>Dal\u0161\u00edm krokem je nastaven\u00ed do\u010dasn\u00e9 s\u00edt\u011b pro vCSA. Zde bych pouze zd\u016fraznil „Temporary IP address“, je to do\u010dasn\u00e1 IP pouze pro p\u0159enos soubor\u016f z p\u016fvodn\u00ed vCSA do nov\u00e9. Ob\u011b vCSA na sebe s\u00ed\u0165ov\u011b mus\u00ed „vid\u011bt“. Po vypln\u011bn\u00ed v\u0161ech parametr\u016f d\u00e1me NEXT.<\/p>\n

    12.<\/strong><\/p>\n

    \"\"<\/a>Nyn\u00ed vid\u00edme sum\u00e1\u0159 v\u0161ech parametr\u016f, kter\u00e9 jsme zadali a instalace nov\u00e9 vCSA m\u016f\u017ee nyn\u00ed za\u010d\u00edt. D\u00e1me FINISH.<\/p>\n

    \"\"<\/a>O pr\u016fb\u011bhu instalace n\u00e1s instal\u00e1tor informuje nejen procentu\u00e1ln\u00edm dokon\u010den\u00edm, ale i v\u00fdpisem, co pr\u00e1v\u011b d\u011bl\u00e1. Pokud v\u0161e dopadne dob\u0159e a vCSA je \u00fasp\u011b\u0161n\u011b nainstalov\u00e1no, objev\u00ed se dialog:\"\"<\/a>Nyn\u00ed m\u00e1me prvn\u00ed f\u00e1zi hotovou a plynule pokra\u010dujeme do druh\u00e9. D\u00e1me CONTINUE.<\/p>\n

    13.<\/strong><\/p>\n

    \"\"<\/a>Dle \u00fadaj\u016f, kter\u00e9 jsme vyplnili ve f\u00e1zi jedna, je instal\u00e1tor p\u0159ipraven se p\u0159ipojit k p\u016fvodn\u00ed vCSA a zah\u00e1jit migraci. D\u00e1me NEXT. Nyn\u00ed prob\u011bhne p\u0159ipojen\u00ed, kontrola mno\u017estv\u00ed dat pro p\u0159enos a n\u011bkter\u00fdch nastaven\u00ed.<\/p>\n

    14.<\/strong><\/p>\n

    \"\"<\/a>Nyn\u00ed dost\u00e1v\u00e1me na v\u00fdb\u011br, jak\u00e1 data chceme migrovat a informaci o jejich mno\u017estv\u00ed. Bohu\u017eel, na zdrojov\u00e9 vCSA nen\u00ed dostatek m\u00edsta ve v\u00fdchoz\u00edm um\u00edst\u011bn\u00ed pro p\u0159\u00edpravu takov\u00e9ho exportu a jsme vyzv\u00e1ni k zad\u00e1n\u00ed cesty v r\u00e1mci zdrojov\u00e9 vCSA, kam maj\u00ed b\u00fdt data ulo\u017eena. Nyn\u00ed m\u00e1me t\u0159i mo\u017enosti:<\/p>\n