{"id":53098,"date":"2019-11-23T00:00:00","date_gmt":"2019-11-22T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline"},"modified":"2020-02-18T14:00:57","modified_gmt":"2020-02-18T11:00:57","slug":"operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","title":{"rendered":"Operace \u201eMigrace\u201d: jak prob\u00edh\u00e1 p\u0159esun do cloudu DataLine","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u0159ed asi 7 lety se prvn\u00ed projekty p\u0159esouvaly do na\u0161eho cloudu jednodu\u0161e a bez komplikac\u00ed. Obrazy virtu\u00e1ln\u00edch stroj\u016f se nahr\u00e1valy na FTP server nebo se p\u0159iv\u00e1\u017eely na pevn\u00fdch disc\u00edch. Pot\u00e9 se pomoc\u00ed speci\u00e1ln\u00edho importn\u00edho serveru VM nahr\u00e1valy do cloudu.<\/p>\n

Pokud nen\u00ed pro klienta probl\u00e9m vypnout virtu\u00e1lku na den nebo dva (nebo to nejsou jin\u00e9 mo\u017enosti), lze to ud\u011blat takto. Ale pokud by m\u011bl b\u00fdt prostoje maxim\u00e1ln\u011b hodinu, tento zp\u016fsob se nehod\u00ed. Dnes v\u00e1m pov\u00edm, jak\u00e9 n\u00e1stroje pomohou migraci do cloudu s minim\u00e1ln\u00edm prostoje a jak samotn\u00fd proces migrace u n\u00e1s prob\u00edh\u00e1.<\/p>\n

\"Operace
\n<\/a><\/noindex><\/p>\n

Migrace pomoc\u00ed Veeam Backup and Replication<\/h3>\n

\nVeeam Backup and Replication je zn\u00e1m jako n\u00e1stroj pro vytv\u00e1\u0159en\u00ed z\u00e1loh a replik. Pou\u017e\u00edv\u00e1me ho pro migraci mezi na\u0161imi lokalitami a pro p\u0159evoz klient\u016f z priv\u00e1tn\u00ed virtualizace k n\u00e1m do cloudu. Virtu\u00e1ln\u00ed stroje klienta se replikuj\u00ed na na\u0161em vCenter, pot\u00e9 in\u017een\u00fdr je p\u0159id\u00e1 do vCloud Director. <\/p>\n

Po\u010d\u00e1te\u010dn\u00ed replikace se prov\u00e1d\u00ed na zapnut\u00e9m virtu\u00e1ln\u00edm stroji. V dohodnut\u00e9m \u010dase se stroj na stran\u011b klienta vypne. Replikace se spust\u00ed znovu, aby se p\u0159enesly zm\u011bny, kter\u00e9 nastaly od prvn\u00ed replikace. Pot\u00e9 se virtu\u00e1ln\u00ed stroj spust\u00ed ji\u017e v na\u0161em cloudu. <\/p>\n

\"Operace
\n
\nObvykle od okam\u017eiku vypnut\u00ed stroje na infrastruktu\u0159e klienta do okam\u017eiku zapnut\u00ed v na\u0161em cloudu ub\u011bhne maxim\u00e1ln\u011b p\u016fl hodiny, sp\u00ed\u0161e 15\u201320 minut. <\/p>\n

Na m\u00edst\u011b klienta z\u016fst\u00e1v\u00e1 p\u016fvodn\u00ed virtu\u00e1ln\u00ed stroj. Pokud se n\u011bco pokaz\u00ed, v\u017edy se lze vr\u00e1tit a zapnout ho. Pro klienta je tento zp\u016fsob tak\u00e9 v\u00fdhodn\u00fd, proto\u017ee nevy\u017eaduje p\u0159\u00edtomnost Veeamu.<\/p>\n

P\u0159\u00edpad 1
\nKlient m\u011bl vlastn\u00ed virtu\u00e1ln\u00ed infrastrukturu na b\u00e1zi VMware \u2013 40 VM o velikosti 30 TB. Hardware, na kter\u00e9m byl rozvinut klastr, ji\u017e zastar\u00e1val, a klient se rozhodl nezapojovat se do n\u00e1kupu nov\u00e9ho a p\u0159est\u011bhovat se do ve\u0159ejn\u00e9ho cloudu. Po\u017eadavek na prostoje kritick\u00fdch syst\u00e9m\u016f \u010dinil maxim\u00e1ln\u011b hodinu. Jako n\u00e1stroj byla zvolena Veeam Replication. V\u00fdhodou tak\u00e9 bylo, \u017ee internetov\u00fd poskytovatel klienta byl p\u0159\u00edtomen v na\u0161em datov\u00e9m centru, co\u017e umo\u017enilo zorganizovat dobr\u00fd kan\u00e1l. Migrace trvala zhruba m\u011bs\u00edc, prostoje p\u0159i p\u0159epnut\u00ed \u010dinily a\u017e 30 minut na jednu skupinu virtu\u00e1ln\u00edch stroj\u016f.<\/i><\/p>\n

Migrace pomoc\u00ed Veeam Cloud Connect<\/h3>\n

\nVeeam Cloud Connect \u2013 n\u00e1stroj, kter\u00fd pom\u00e1h\u00e1 nastavovat replikaci virtu\u00e1ln\u00edch stroj\u016f a spou\u0161t\u011bt repliky v cloudu poskytovatele slu\u017eeb. Po aktualizaci v 2019<\/a><\/noindex> roce se objevila mo\u017enost replikovat virtu\u00e1ln\u00ed stroje p\u0159\u00edmo do vCloud Director. Jedinou podm\u00ednkou je, \u017ee na stran\u011b klienta mus\u00ed b\u00fdt nasazen vlastn\u00ed Veeam Backup and Replication verze 9 nebo vy\u0161\u0161\u00ed. Pokud to shrneme (podrobn\u00e1 verze tady<\/a><\/noindex>), cel\u00fd proces vypad\u00e1 n\u00e1sledovn\u011b.<\/p>\n

Ve vCloud Director se vytvo\u0159\u00ed organizace s pot\u0159ebn\u00fdmi zdroji a s\u00edt\u011bmi. V Veeam Cloud Connect vytvo\u0159\u00edme \u00fa\u010det, klient se k n\u011bmu p\u0159ipojuje ze sv\u00e9ho Veeam B&R, vyb\u00edr\u00e1 poskytovatele DataLine a organizaci, nastavuje \u00fakoly pro replikaci. Krom\u011b toho, \u017ee doba odst\u00e1vky p\u0159i takov\u00e9 migraci bude v rozmez\u00ed 15\u201320 minut, klient nen\u00ed z\u00e1visl\u00fd na technick\u00e9 podpo\u0159e poskytovatele a \u0159\u00edd\u00ed cel\u00fd proces s\u00e1m: vytv\u00e1\u0159\u00ed \u00fakoly na replikaci, samotnou replikaci, vyp\u00edn\u00e1 stroje a spou\u0161t\u00ed jejich start na nov\u00e9 platform\u011b. <\/p>\n

\"Operace
\n
\nP\u0159\u00edpad 2
\nInfrastruktura klienta, odkud byla pl\u00e1nov\u00e1na migrace, se nach\u00e1zela v B\u011blorusku. Bylo t\u0159eba p\u0159ev\u00e9st 90 VMs s celkov\u00fdm objemem 27 TB, p\u0159i\u010dem\u017e internetov\u00fd kan\u00e1l byl 100 mbit\/s. Pokud bychom d\u011blali z\u00e1lohu a hned ji nahr\u00e1vali k n\u00e1m do cloudu, n\u011bkter\u00e9 VMs by to trvalo n\u011bkolik dn\u00ed. B\u011bhem t\u00e9to doby by na VMs vznikla velk\u00e1 delta, co\u017e by mohlo negativn\u011b ovlivnit v\u00fdkon stroj\u016f nebo, co\u017e je je\u0161t\u011b hor\u0161\u00ed, by do\u0161lo m\u00edsto na datastoru. Postupovali jsme n\u00e1sledovn\u011b: nejprve klient provedl lok\u00e1ln\u00ed kompletn\u00ed z\u00e1lohu a p\u0159enesl jej\u00ed kopii k n\u00e1m do cloudu pomoc\u00ed Veeam Cloud Connect. Pot\u00e9 vytvo\u0159il a p\u0159enesl do cloudu inkrement\u00e1ln\u00ed z\u00e1lohu. P\u016fvodn\u00ed virtu\u00e1ln\u00ed stroj pokra\u010doval v pr\u00e1ci. Po vypnut\u00ed VMs klient provedl dal\u0161\u00ed inkrement a tak\u00e9 p\u0159enesl do cloudu. Na sv\u00e9 stran\u011b jsme nasadili virtu\u00e1ln\u00ed stroj z kompletn\u00ed z\u00e1lohy a pot\u00e9 doplnili dva inkrementy. Tento postup umo\u017enil nakonec minimalizovat odst\u00e1vku na 2 hodiny p\u0159i p\u0159epnut\u00ed na na\u0161i platformu. <\/i><\/p>\n

Migrace pomoc\u00ed VMware vCloud Availability<\/h3>\n

\nV b\u0159eznu leto\u0161n\u00edho roku spole\u010dnost VMware uvedla vCloud Availability 3.0, kter\u00fd umo\u017e\u0148uje migrovat virtu\u00e1ln\u00ed stroje mezi r\u016fzn\u00fdmi cloudy (vCloud Director \u2013 vCloud Director) a z priv\u00e1tn\u00edch virtualiza\u010dn\u00edch st\u00e1n\u00ed klienta do cloudu (vCenter \u2013 vCloud Director). Hlavn\u00ed v\u00fdhodou je integrace s rozhran\u00edm vCloud Director. To v\u00fdrazn\u011b zjednodu\u0161uje proces spr\u00e1vy replikace a minimalizuje prostoje p\u0159i p\u0159ep\u00edn\u00e1n\u00ed.<\/p>\n

Pomoc\u00ed tohoto n\u00e1stroje jsme migrovali jednoho z klient\u016f z na\u0161eho moskevsk\u00e9ho cloudu do na\u0161eho cloudu v Petrohradu. Bylo t\u0159eba p\u0159en\u00e9st 18 virtu\u00e1ln\u00edch stroj\u016f s celkovou kapacitou 14 TB. Pro klienta byla vytvo\u0159ena organizace v petrohradsk\u00e9m cloudu a byly zorganizov\u00e1ny pot\u0159ebn\u00e9 s\u00edt\u011b. N\u00e1sledn\u011b z rozhran\u00ed vCloud Director klient p\u0159e\u0161el k nastaven\u00edm vCloud Availability, vytvo\u0159il \u00fakoly replikace a ve vhodnou dobu se p\u0159epnul na petrohradskou lokalitu. Prostoje p\u0159i p\u0159ep\u00edn\u00e1n\u00ed \u010dinily 12 minut.<\/p>\n

\"Operace
\nSch\u00e9ma migrace mezi cloudy DataLine v Petrohradu a Moskv\u011b.<\/i><\/p>\n

Ve vCloud Availability existuje mechanismus migrace VM z plochy klienta do na\u0161eho cloudu. K tomu se na vCenter klienta nasazuje speci\u00e1ln\u00ed appliance vCloud Availability. Po jednoduch\u00e9m nastaven\u00ed se provede p\u0159ipojen\u00ed k cloudu a nastavuj\u00ed se \u00fakoly migrace. Klient tak\u00e9 samo\u0159iditeln\u011b \u0159\u00edd\u00ed cel\u00fd proces, a \u010das migrace se minimalizuje.<\/p>\n

\"Operace
\nSch\u00e9ma migrace virtu\u00e1ln\u00edch stroj\u016f z priv\u00e1tn\u00ed instalace do cloudu.<\/i><\/p>\n

VMware vCloud Availability m\u00e1 mnoho dal\u0161\u00edch sc\u00e9n\u00e1\u0159\u016f pou\u017eit\u00ed, brzy o nich podrobn\u011bji uvedeme v samostatn\u00e9m \u010dl\u00e1nku. <\/p>\n

P\u0159\u00edprava na migraci <\/h3>\n

\nAbychom vybrali n\u00e1stroj a mohli se pustit do migrace, je t\u0159eba si ujasnit n\u00e1sleduj\u00edc\u00ed body:<\/p>\n

Odkud migrujeme. <\/b>Pokud migrujete z priv\u00e1tn\u00edho \u0159e\u0161en\u00ed, m\u00e1te \u00faplnou svobodu ve v\u00fdb\u011bru n\u00e1stroj\u016f. Pokud se p\u0159est\u011bhujete od poskytovatele, je to slo\u017eit\u011bj\u0161\u00ed. Pravd\u011bpodobn\u011b nebude mo\u017en\u00e9 propojit infrastruktury dvou poskytovatel\u016f a jednodu\u0161e p\u0159et\u00e1hnout VM z d\u016fvodu bezpe\u010dnostn\u00edch obav. N\u011bkdy poskytovatel, od kter\u00e9ho se klient hodl\u00e1 odpojit, za\u010dne \u0161kodit a zdr\u017eovat. P\u0159est\u011bhov\u00e1n\u00ed od poskytovatele lze prov\u00e9st klasicky: prost\u0159ednictv\u00edm exportu VM na disky a FTP nebo migrac\u00ed na \u00farovni aplikace. N\u00e1zev posledn\u00edho je podm\u00edn\u011bn\u00fd, a vypad\u00e1 to p\u0159ibli\u017en\u011b tak.<\/p>\n

P\u0159\u00edpad 3
\nBylo pot\u0159eba migrovat SAP syst\u00e9m klienta od evropsk\u00e9ho poskytovatele: 34 VM o objemu 54 TB. Klientovi byly p\u0159id\u011bleny zdroje v na\u0161em cloudu. Mezi n\u00e1mi a infrastrukturou evropsk\u00e9ho poskytovatele byla zaji\u0161t\u011bna s\u00ed\u0165ov\u00e1 konektivita. Aplika\u010dn\u00ed servery byly znovu nasazeny s pot\u0159ebn\u00fdmi konfiguracemi. Velk\u00e9 datab\u00e1ze byly migrov\u00e1ny prost\u0159ednictv\u00edm nahr\u00e1n\u00ed z\u00e1loh do na\u0161eho cloudu. N\u00e1sledn\u011b byla nastavena replikace mezi datab\u00e1zemi v na\u0161em a p\u016fvodn\u00edm prost\u0159ed\u00ed. V dohodnut\u00e9m \u010dase jsme p\u0159epnuli na datab\u00e1ze v na\u0161em cloudu.<\/i><\/p>\n

Objem dat a internetov\u00fd kan\u00e1l.<\/b> Obvykle \u017e\u00e1d\u00e1me klienta, aby n\u00e1m poskytl v\u00fdstup podle syst\u00e9m\u016f s parametry pam\u011bti, CPU a disk\u016f. Odhadujeme, zda bude kan\u00e1l dostate\u010dn\u00fd pro p\u0159\u00edm\u00e9 odes\u00edl\u00e1n\u00ed replik nebo z\u00e1loh virtu\u00e1ln\u00edch stroj\u016f. <\/p>\n

P\u0159ijateln\u00fd v\u00fdpadek.<\/b> Pro r\u016fzn\u00e9 syst\u00e9my a odpov\u00eddaj\u00edc\u00ed virtu\u00e1ln\u00ed stroje m\u016f\u017ee b\u00fdt jin\u00fd v z\u00e1vislosti na jejich kriti\u010dnosti pro business. Obvykle klient p\u0159ich\u00e1z\u00ed s p\u0159ipraven\u00fdmi po\u017eadavky na v\u00fdpadek p\u0159i migraci, na jejich\u017e z\u00e1klad\u011b vyb\u00edr\u00e1me vhodn\u00fd n\u00e1stroj a pl\u00e1n migrace. Sna\u017e\u00edme se napl\u00e1novat fin\u00e1ln\u00ed p\u0159epnut\u00ed na no\u010dn\u00ed hodiny nebo v\u00edkendy, aby i nepatrn\u00fd v\u00fdpadek nebyl pro koncov\u00e9 u\u017eivatele klienta znateln\u00fd. <\/p>\n

Na z\u00e1klad\u011b t\u011bchto dat m\u016f\u017eeme vyb\u00edrat n\u00e1stroj a p\u0159istoupit k samotn\u00e9 migraci. Tady je, co se d\u011bje d\u00e1le.<\/p>\n

    \n
  1. Nastaven\u00ed s\u00ed\u0165ov\u00e9 konektivity. <\/b>Organizujeme s\u00ed\u0165ovou konektivitu mezi na\u0161\u00edm cloudem a infrastrukturou klienta. Po t\u00e9to s\u00edti budou kop\u00edrov\u00e1ny virtu\u00e1ln\u00ed stroje. Pokud se pou\u017e\u00edv\u00e1 Veeam Backup and Replication, tak to je vyhrazen\u00fd kan\u00e1l, m\u00e9n\u011b \u010dasto \u2013 VPN kan\u00e1l. Pokud Veeam Cloud Connect, tak v\u0161echno prob\u00edh\u00e1 p\u0159es internet nebo ten stejn\u00fd vyhrazen\u00fd kan\u00e1l.\n

    Pot\u00e9 se nastav\u00ed s\u00ed\u0165 pro VM v cloudu. Stroje obvykle migruj\u00ed skupinov\u011b a ne za jeden den. Jakmile byly VM p\u0159evedeny k n\u00e1m a spu\u0161t\u011bny, mus\u00ed interagovat se stroji, kter\u00e9 je\u0161t\u011b z\u016fst\u00e1vaj\u00ed v p\u016fvodn\u00edm prost\u0159ed\u00ed. <\/li>\n

  2. Pl\u00e1n migrace.<\/b> Kdy\u017e je stroj\u016f hodn\u011b, je rozumn\u00e9 je rozd\u011blit do skupin a p\u0159epravovat po parti\u00edch. Spole\u010dn\u011b s klientem domlouv\u00e1me pl\u00e1n, ve kter\u00e9m specifikujeme, kdy a jak\u00e9 stroje se p\u0159esunou a kdy bude provedena fin\u00e1ln\u00ed replikace a p\u0159epnut\u00ed na nov\u00e9 prost\u0159ed\u00ed. <\/li>\n
  3. Testovac\u00ed migrace.<\/b> Migrace testovac\u00ed virtu\u00e1ln\u00ed stroje a ov\u011b\u0159en\u00ed, zda je v\u0161e spr\u00e1vn\u011b nastaveno: s\u00ed\u0165ov\u00e1 konektivita mezi lokalitami, dostupnost virtu\u00e1ln\u00edho stroje pro stroje na p\u016fvodn\u00ed lokalit\u011b, pr\u00e1va \u00fa\u010dtu a dal\u0161\u00ed. Takov\u00fd test pom\u00e1h\u00e1 vyhnout se zpo\u017ed\u011bn\u00edm b\u011bhem f\u00e1ze v\u00fdrobn\u00ed migrace.<\/li>\n<\/ol>\n

    \nTo je ode m\u011b v\u0161e. V koment\u00e1\u0159\u00edch se ptejte a pod\u011blte se o sv\u00e9 zku\u0161enosti s migrac\u00ed.
    \n
    Zdroj:     habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

    \u041b\u0435\u0442 7 \u043d\u0430\u0437\u0430\u0434 \u0441\u0430\u043c\u044b\u0435 \u043f\u0435\u0440\u0432\u044b\u0435 \u043f\u0440\u043e\u0435\u043a\u0442\u044b \u043f\u0435\u0440\u0435\u0435\u0437\u0436\u0430\u043b\u0438 \u0432 \u043d\u0430\u0448\u0435 \u043e\u0431\u043b\u0430\u043a\u043e \u043f\u0440\u043e\u0441\u0442\u043e \u0438 \u043d\u0435\u0437\u0430\u0442\u0435\u0439\u043b\u0438\u0432\u043e. \u041e\u0431\u0440\u0430\u0437\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u0437\u0430\u0433\u0440\u0443\u0436\u0430\u043b\u0438\u0441\u044c \u043d\u0430 FTP-\u0441\u0435\u0440\u0432\u0435\u0440, \u0438\u043b\u0438 \u0438\u0445 \u043f\u0440\u0438\u0432\u043e\u0437\u0438\u043b\u0438 \u043d\u0430 \u0436\u0435\u0441\u0442\u043a\u0438\u0445 \u0434\u0438\u0441\u043a\u0430\u0445. \u0417\u0430\u0442\u0435\u043c \u0447\u0435\u0440\u0435\u0437 \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 \u0438\u043c\u043f\u043e\u0440\u0442-\u0441\u0435\u0440\u0432\u0435\u0440 \u0412\u041c \u0437\u0430\u0433\u0440\u0443\u0436\u0430\u043b\u0438 \u0432 \u043e\u0431\u043b\u0430\u043a\u043e. \u0415\u0441\u043b\u0438 \u0434\u043b\u044f \u043a\u043b\u0438\u0435\u043d\u0442\u0430 \u043d\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0432\u044b\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u043a\u0443 \u043d\u0430 \u0441\u0443\u0442\u043a\u0438-\u0434\u0432\u043e\u0435 (\u0438\u043b\u0438 \u043d\u0435\u0442 \u0434\u0440\u0443\u0433\u0438\u0445 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u043e\u0432), \u0442\u043e \u043c\u043e\u0436\u043d\u043e \u0438 \u0442\u0430\u043a. \u041d\u043e \u0435\u0441\u043b\u0438 \u043f\u0440\u043e\u0441\u0442\u043e\u0439 \u0434\u043e\u043b\u0436\u0435\u043d \u0431\u044b\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-53098","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Operace \"Migrace\": jak prob\u00edh\u00e1 p\u0159echod do cloudu DataLine | ProHoster","description":"P\u0159ed asi 7 lety se na\u0161e nejstar\u0161\u00ed projekty st\u011bhovaly do na\u0161eho cloudu jednodu\u0161e a bez komplikac\u00ed. Obrazy virtu\u00e1ln\u00edch stroj\u016f byly nahr\u00e1v\u00e1ny na FTP server nebo byly p\u0159ivezeny na pevn\u00fdch disc\u00edch.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041e\u043f\u0435\u0440\u0430\u0446\u0438\u044f \u201c\u041c\u0438\u0433\u0440\u0430\u0446\u0438\u044f\u201d: \u043a\u0430\u043a \u043f\u0440\u043e\u0438\u0441\u0445\u043e\u0434\u0438\u0442 \u043f\u0435\u0440\u0435\u0435\u0437\u0434 \u0432 \u043e\u0431\u043b\u0430\u043a\u043e DataLine | ProHoster","og:description":"\u041b\u0435\u0442 7 \u043d\u0430\u0437\u0430\u0434 \u0441\u0430\u043c\u044b\u0435 \u043f\u0435\u0440\u0432\u044b\u0435 \u043f\u0440\u043e\u0435\u043a\u0442\u044b \u043f\u0435\u0440\u0435\u0435\u0437\u0436\u0430\u043b\u0438 \u0432 \u043d\u0430\u0448\u0435 \u043e\u0431\u043b\u0430\u043a\u043e \u043f\u0440\u043e\u0441\u0442\u043e \u0438 \u043d\u0435\u0437\u0430\u0442\u0435\u0439\u043b\u0438\u0432\u043e. \u041e\u0431\u0440\u0430\u0437\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u0437\u0430\u0433\u0440\u0443\u0436\u0430\u043b\u0438\u0441\u044c \u043d\u0430 FTP-\u0441\u0435\u0440\u0432\u0435\u0440, \u0438\u043b\u0438 \u0438\u0445 \u043f\u0440\u0438\u0432\u043e\u0437\u0438\u043b\u0438 \u043d\u0430 \u0436\u0435\u0441\u0442\u043a\u0438\u0445 \u0434\u0438\u0441\u043a\u0430\u0445.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-11-22T21:00:00+00:00","article:modified_time":"2020-02-18T11:00:57+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"53098","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-24 06:04:31","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 14:29:47","updated":"2026-01-24 06:04:31","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/53098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=53098"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/53098\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=53098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=53098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=53098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}