{"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\/ro\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","title":{"rendered":"Opera\u021biunea \u201eMigrarea\u201d: cum are loc mutarea \u00een cloud-ul DataLine","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Acum 7 ani, cele mai vechi proiecte se mutau \u00een cloud-ul nostru simplu \u0219i f\u0103r\u0103 complica\u021bii. Imaginile ma\u0219inilor virtuale erau \u00eenc\u0103rcate pe un server FTP sau erau aduse pe discuri dure. Apoi, printr-un server special de import, ma\u0219inile virtuale erau \u00eenc\u0103rcate \u00een cloud.<\/p>\n

Dac\u0103 pentru client nu este o problem\u0103 s\u0103 opreasc\u0103 ma\u0219ina virtual\u0103 pentru o zi sau dou\u0103 (sau dac\u0103 nu exist\u0103 alte op\u021biuni), se poate face \u0219i a\u0219a. Dar dac\u0103 oprirea trebuie s\u0103 dureze maximum o or\u0103, atunci aceast\u0103 metod\u0103 nu este adecvat\u0103. Ast\u0103zi voi vorbi despre ce instrumente ajut\u0103 la migrarea \u00een cloud cu un timp de nefunc\u021bionare minim \u0219i despre cum func\u021bioneaz\u0103 procesul de migrare la noi.<\/p>\n

\"Opera\u021biunea
\n<\/a><\/noindex><\/p>\n

Migrarea cu ajutorul Veeam Backup and Replication<\/h3>\n

\nToat\u0103 lumea cunoa\u0219te Veeam Backup and Replication ca un instrument pentru crearea de backup-uri \u0219i replici. Noi \u00eel folosim pentru migrarea \u00eentre platformele noastre \u0219i pentru a transfera clien\u021bi de la virtualizarea privat\u0103 la cloud-ul nostru. Ma\u0219inile virtuale ale clientului sunt replicate pe vCenter-ul nostru, dup\u0103 care inginerul le adaug\u0103 \u00een vCloud Director. <\/p>\n

Replicarea ini\u021bial\u0103 se efectueaz\u0103 pe ma\u0219ina virtual\u0103 activ\u0103. La un moment convenit, ma\u0219ina de partea clientului este oprit\u0103. Replicarea este reluat\u0103 pentru a transfera modific\u0103rile ap\u0103rute de la prima replicare. Dup\u0103 aceea, ma\u0219ina virtual\u0103 porne\u0219te deja \u00een cloud-ul nostru. <\/p>\n

\"Opera\u021biunea
\n
\nDe obicei, de la momentul opririi ma\u0219inii \u00een infrastructura clientului \u0219i p\u00e2n\u0103 la momentul activ\u0103rii \u00een cloud-ul nostru nu trec mai mult de o jum\u0103tate de or\u0103, ci mai degrab\u0103 15\u201320 de minute. <\/p>\n

\u00cen acest proces, pe site-ul clientului r\u0103m\u00e2ne ma\u0219ina virtual\u0103 original\u0103. Dac\u0103 se \u00eent\u00e2mpl\u0103 ceva nea\u0219teptat, se poate \u00eentotdeauna reveni \u0219i activa ea. Pentru client, acest mod este convenabil \u0219i pentru c\u0103 nu necesit\u0103 prezen\u021ba Veeam.<\/p>\n

Cazul 1
\nClientul avea propria infrastructur\u0103 virtual\u0103 bazat\u0103 pe VMware \u2013 40 de ma\u0219ini virtuale cu un volum de 30 TB. Echipamentul pe care a fost desf\u0103\u0219urat clusterul era deja \u00eenvechit, iar clientul a decis s\u0103 nu se mai complice cu achizi\u021bia de echipamente noi \u0219i s\u0103 se mute \u00een cloud-ul public. Cerin\u021ba privind timpul de nefunc\u021bionare pentru sistemele critice a fost de maximum o or\u0103. Ca instrument, a fost ales Veeam Replication. Un alt avantaj a fost c\u0103 furnizorul de internet al clientului era prezent \u00een centrul nostru de date, ceea ce a permis organizarea unei bune conexiuni. Migrarea a durat aproximativ o lun\u0103, timpul de nefunc\u021bionare \u00een timpul comut\u0103rii fiind de p\u00e2n\u0103 la 30 de minute pentru un grup de ma\u0219ini virtuale.<\/i><\/p>\n

Migrarea cu ajutorul Veeam Cloud Connect<\/h3>\n

\nVeeam Cloud Connect \u2013 un instrument care ajut\u0103 la configurarea replic\u0103rii ma\u0219inilor virtuale \u0219i la lansarea replicilor \u00een cloud-ul furnizorului de servicii. Dup\u0103 actualizarea din 2019<\/a><\/noindex> anul acesta, a ap\u0103rut posibilitatea de a replica ma\u0219inile virtuale direct \u00een vCloud Director. Singura condi\u021bie este ca de partea clientului s\u0103 existe un Veeam Backup and Replication desf\u0103\u0219urat cu versiunea de 9 sau mai recent\u0103. Pe scurt (versiunea detaliat\u0103 aici<\/a><\/noindex>), procesul arat\u0103 astfel.<\/p>\n

\u00cen vCloud Director se creeaz\u0103 o organiza\u021bie cu resurse \u0219i re\u021bele necesare. \u00cen Veeam Cloud Connect cre\u0103m un cont, clientul se conecteaz\u0103 la acesta din Veeam B&R, alege furnizorul DataLine \u0219i organiza\u021bia, configur\u00e2nd sarcinile pentru replicare. Pe l\u00e2ng\u0103 faptul c\u0103 migrarea dureaz\u0103 \u00eentre 15\u201320 de minute, clientul nu depinde de suportul tehnic al furnizorului \u0219i gestioneaz\u0103 \u00eentregul proces autonom: creeaz\u0103 sarcini de replicare, realizarea replic\u0103rii, opre\u0219te ma\u0219inile \u0219i le porne\u0219te \u00een noua loca\u021bie. <\/p>\n

\"Opera\u021biunea
\n
\nCaz 2
\nInfrastructura clientului, de unde era planificat\u0103 migrarea, se afla \u00een Belarus. Era necesar s\u0103 transport\u0103m 90 de VM cu un volum total de 27 TB, av\u00e2nd \u00een vedere c\u0103 canalul de internet era de 100 Mbit\/s. Dac\u0103 efectu\u0103m backup-ul \u0219i \u00eel transfer\u0103m imediat \u00een cloud-ul nostru, pentru unele VM ar fi durat c\u00e2teva zile. \u00cen acest timp, pe VM ar fi crescut o delta mare, ceea ce ar fi putut afecta negativ performan\u021ba ma\u0219inilor sau, \u0219i mai r\u0103u, s\u0103 r\u0103m\u00e2n\u0103 f\u0103r\u0103 spa\u021biu pe datastore. Am procedat astfel: ini\u021bial, clientul a realizat un backup complet local \u0219i a transferat o copie \u00een cloud-ul nostru prin Veeam Cloud Connect. Apoi a realizat \u0219i a transferat \u00een cloud un incremental. Ma\u0219ina virtual\u0103 original\u0103 continua s\u0103 func\u021bioneze. Dup\u0103 oprirea VM, clientul a realizat \u00eenc\u0103 un incremental \u0219i l-a transferat \u0219i pe acesta \u00een cloud. De partea noastr\u0103, am desf\u0103\u0219urat o ma\u0219in\u0103 virtual\u0103 din backup-ul complet, apoi am aplicat cele dou\u0103 incrementale. Aceast\u0103 schem\u0103 a permis \u00een final s\u0103 minimaliz\u0103m timpul de nefunc\u021bionare la 2 ore c\u00e2nd am trecut pe platforma noastr\u0103. <\/i><\/p>\n

Migrarea prin VMware vCloud Availability<\/h3>\n

\n\u00cen martie a acestui an, VMware a lansat vCloud Availability 3.0, care permite migrarea ma\u0219inilor virtuale \u00eentre diferite clouduri (vCloud Director \u2013 vCloud Director) \u0219i de la standurile private de virtualizare ale clientului \u00een cloud (vCenter \u2013 vCloud Director). Principalul avantaj este integrarea cu interfa\u021ba vCloud Director. Acest lucru simplific\u0103 semnificativ procesul de gestionare a replic\u0103rii \u0219i minimizeaz\u0103 timpii de inactivitate \u00een timpul comut\u0103rii.<\/p>\n

Cu ajutorul acestui instrument, am migrat unul dintre clien\u021bii no\u0219tri din cloudul nostru din Moscova \u00een cloudul nostru din Sankt Petersburg. A fost necesar s\u0103 mut\u0103m 18 ma\u0219ini virtuale cu o capacitate total\u0103 de 14 TB. Pentru client a fost creat\u0103 o organiza\u021bie \u00een cloudul din Sankt Petersburg \u0219i au fost organizate re\u021belele necesare. Apoi, din interfa\u021ba vCloud Director, clientul a trecut la set\u0103rile vCloud Availability, a creat sarcini de replicare \u0219i s-a comutat pe platforma din Sankt Petersburg la un moment convenabil pentru el. Timpul de inactivitate \u00een timpul comut\u0103rii a fost de 12 minute.<\/p>\n

\"Opera\u021biunea
\nSchema de migrare \u00eentre cloudurile DataLine din Sankt Petersburg \u0219i Moscova.<\/i><\/p>\n

\u00cen vCloud Availability exist\u0103 un mecanism de migrare a VM-urilor de la platforma clientului \u00een cloudul nostru. Pentru aceasta, \u00een vCenter-ul clientului se desf\u0103\u0219oar\u0103 un appliance special vCloud Availability. Dup\u0103 o configurare simpl\u0103, se conecteaz\u0103 la cloud \u0219i se configureaz\u0103 sarcinile de migrare. Clientul de asemenea gestioneaz\u0103 \u00eentregul proces, iar timpul de migrare este minimizat.<\/p>\n

\"Opera\u021biunea
\nSchema de migrare a ma\u0219inilor virtuale dintr-o instala\u021bie privat\u0103 \u00een cloud.<\/i><\/p>\n

VMware vCloud Availability are multe alte scenarii de utilizare, \u0219i \u00een cur\u00e2nd v\u0103 vom povesti despre ele \u00eentr-un articol separat. <\/p>\n

Preg\u0103tirea pentru migrare <\/h3>\n

\nPentru a alege instrumentul \u0219i a \u00eencepe efectiv migrarea, trebuie s\u0103 clarific\u0103m urm\u0103toarele aspecte:<\/p>\n

De unde migr\u0103m. <\/b>Dac\u0103 migra\u021bi de la o solu\u021bie privat\u0103, ave\u021bi libertate total\u0103 \u00een alegerea instrumentelor. Dac\u0103 p\u0103r\u0103si\u021bi un furnizor, lucrurile devin mai complicate. Cel mai probabil, legarea infrastructurii a doi furnizori \u0219i pur \u0219i simplu mutarea VM-urilor nu va fi posibil\u0103 din motive de securitate. Uneori, furnizorul de la care clientul inten\u021bioneaz\u0103 s\u0103 plece \u00eencepe chiar s\u0103 fac\u0103 probleme \u0219i c\u00e2\u0219tig\u0103 timp. P\u0103r\u0103sirea furnizorului se poate face \u00een mod tradi\u021bional: prin desc\u0103rcarea VM-urilor pe discuri \u0219i FTP sau migr\u00e2nd la nivel de aplica\u021bie. Numele ultimei metode este condi\u021bional, \u0219i arat\u0103 cam a\u0219a.<\/p>\n

Caz 3
\nA fost necesar\u0103 migrarea sistemului SAP al clientului de la un furnizor european: 34 VM cu un volum de 54 TB. Clientului i-au fost alocate resurse \u00een cloud-ul nostru. \u00centre noi \u0219i infrastructura furnizorului european a fost organizat\u0103 conectivitate de re\u021bea. Serverele de aplica\u021bii au fost redeployment \u0219i configurate corespunz\u0103tor. Baze de date mari au fost migrat prin \u00eenc\u0103rcarea de backup-uri \u00een cloud-ul nostru. Apoi, a fost configurat\u0103 replicarea \u00eentre bazele de date pe site-urile noastre \u0219i cele ini\u021biale. La momentul convenit, am comutat pe bazele de date din cloud-ul nostru.<\/i><\/p>\n

Volumul de date \u0219i canalul de internet.<\/b> De obicei, cerem clientului s\u0103 ne ofere o exportare a sistemelor cu parametrii de memorie, CPU, discuri. Evalu\u0103m dac\u0103 canalul este suficient pentru a trimite direct replicile sau backup-urile ma\u0219inilor virtuale. <\/p>\n

Timpul de nefunc\u021bionare acceptabil.<\/b> Pentru diferite sisteme \u0219i, respectiv, ma\u0219ini virtuale, acesta poate varia \u00een func\u021bie de criticitatea lor pentru afacere. De obicei, clientul vine cu cerin\u021be clare \u00een leg\u0103tur\u0103 cu timpul de nefunc\u021bionare \u00een timpul migra\u021biei, iar pe baza acestora alegem instrumentul \u0219i planul de migrare potrivit. Ne str\u0103duim s\u0103 planific\u0103m comutarea final\u0103 pentru timpul de noapte sau weekenduri, astfel \u00eenc\u00e2t chiar \u0219i un timp de nefunc\u021bionare minor s\u0103 nu fie observat de utilizatorii finali ai clientului. <\/p>\n

Pe baza acestor date, se pot alege instrumentele \u0219i poate \u00eencepe migrarea propriu-zis\u0103. Iat\u0103 ce se \u00eent\u00e2mpl\u0103 mai departe.<\/p>\n

    \n
  1. Configurarea conectivit\u0103\u021bii de re\u021bea. <\/b>Organiz\u0103m conectivitatea de re\u021bea \u00eentre cloud-ul nostru \u0219i infrastructura clientului. Prin aceast\u0103 re\u021bea vor fi copiate ma\u0219inile virtuale. Dac\u0103 se folose\u0219te Veeam Backup and Replication, atunci este un canal dedicat, mai rar \u2013 un canal VPN. Dac\u0103 se folose\u0219te Veeam Cloud Connect, atunci totul trece prin internet sau acela\u0219i canal dedicat.\n

    Apoi se configureaz\u0103 re\u021beaua pentru VM \u00een cloud. Ma\u0219inile se mut\u0103 de obicei \u00een grupuri \u0219i nu \u00eentr-o singur\u0103 zi. Dup\u0103 ce VM-urile au fost transferate la noi \u0219i au fost lansate, acestea trebuie s\u0103 interac\u021bioneze cu ma\u0219inile care r\u0103m\u00e2n \u00eenc\u0103 pe site-ul ini\u021bial. <\/li>\n

  2. Programul de migrare.<\/b> C\u00e2nd sunt multe ma\u0219ini, este rezonabil s\u0103 le \u00eemp\u0103r\u021bim \u00een grupuri \u0219i s\u0103 le transport\u0103m \u00een loturi. \u00cempreun\u0103 cu clientul, stabilim un plan \u00een care definim c\u00e2nd \u0219i ce ma\u0219ini se mut\u0103 \u0219i c\u00e2nd va avea loc replicarea final\u0103 \u0219i comutarea pe noua platform\u0103. <\/li>\n
  3. Migrarea de test.<\/b> Migremos ma\u0219ina virtual\u0103 de test \u0219i verific\u0103m dac\u0103 totul este corect configurat: conectivitatea re\u021belei \u00eentre loca\u021bii, disponibilitatea ma\u0219inii virtuale pentru ma\u0219inile din loca\u021bia ini\u021bial\u0103, drepturile contului \u0219i altele. Un astfel de test ajut\u0103 la evitarea \u00eent\u00e2rzierilor \u00een etapa migra\u021biei \u00een produc\u021bie.<\/li>\n<\/ol>\n

    \nAsta e tot din partea mea. \u00centreba\u021bi \u00een comentarii \u0219i povesti\u021bi despre experien\u021ba voastr\u0103 cu migrarea.
    \n
    Sursa:     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\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\udd47Opera\u021biunea \u201eMigrarea\u201d: cum se desf\u0103\u0219oar\u0103 mutarea \u00een cloud-ul DataLine | ProHoster","description":"Acum aproximativ 7 ani, primele proiecte s-au mutat \u00een cloud-ul nostru \u00eentr-un mod simplu \u0219i f\u0103r\u0103 complica\u021bii. Imaginile ma\u0219inilor virtuale erau \u00eenc\u0103rcate pe serverul FTP sau erau aduse pe discuri dure.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/53098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=53098"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/53098\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=53098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=53098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=53098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}