{"id":96767,"date":"2020-10-14T14:43:02","date_gmt":"2020-10-14T12:43:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/hystax-cloud-migration-skachem-po-oblakam"},"modified":"2020-10-14T14:43:02","modified_gmt":"2020-10-14T12:43:02","slug":"hystax-cloud-migration-skachem-po-oblakam","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/hystax-cloud-migration-skachem-po-oblakam","title":{"rendered":"Hystax Cloud Migration: shkarkojm\u00eb n\u00ebp\u00ebr re","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Nj\u00eb nga lojtar\u00ebt e rinj n\u00eb tregun e zgjidhjeve p\u00ebr Rikuperimin nga Krizat \u00ebsht\u00eb kompania Hystax \u2013 nj\u00eb startup rus i vitit 2016. Duke qen\u00eb se tema e rikuperimit \u00ebsht\u00eb shum\u00eb e popullarizuar dhe n\u00eb treg ka nj\u00eb konkurrenc\u00eb jasht\u00ebzakonisht t\u00eb lart\u00eb, startupi vendosi t\u00eb p\u00ebrqendrohet n\u00eb migrimin midis infrastrukturave t\u00eb ndryshme t\u00eb cloud. Nj\u00eb produkt q\u00eb lejon organizimin e nj\u00eb migrimi t\u00eb thjesht\u00eb dhe t\u00eb shpejt\u00eb n\u00eb cloud do t\u00eb ishte shum\u00eb i dobish\u00ebm edhe p\u00ebr klient\u00ebt e kompanis\u00eb \"Onlanta\" — p\u00ebrdoruesit. Oncloud.ru<\/a><\/noindex>. K\u00ebshtu njoha Hystax dhe fillova t\u00eb testoj mund\u00ebsit\u00eb e tij. \u00c7far\u00eb arrita t\u00eb zbuloj, do ta tregoj n\u00eb k\u00ebt\u00eb artikull.<\/p>\n

\"Hystax<\/a><\/noindex>
\nKarakteristika kryesore e Hystax \u00ebsht\u00eb funksionaliteti i tij i gjer\u00eb p\u00ebr mb\u00ebshtetje t\u00eb platformave t\u00eb ndryshme t\u00eb virtualizimit, sistemeve operative p\u00ebr mysafir\u00eb dhe sh\u00ebrbimeve n\u00eb cloud, duke ofruar mund\u00ebsin\u00eb p\u00ebr t\u00eb transferuar ngarkesat e pun\u00ebs nga \u00e7do vend n\u00eb \u00e7do vend.<\/p>\n

Kjo lejon krijimin jo vet\u00ebm t\u00eb zgjidhjeve DR p\u00ebr rritjen e q\u00ebndrueshm\u00ebris\u00eb s\u00eb sh\u00ebrbimeve, por gjithashtu migrimin fleksib\u00ebl dhe t\u00eb shpejt\u00eb t\u00eb burimeve midis platformave t\u00eb ndryshme dhe hiper-skaluesve p\u00ebr rritjen e kursimeve dhe zgjedhjen e zgjidhjeve m\u00eb t\u00eb mira sipas nevojave specifike t\u00eb sh\u00ebrbimeve n\u00eb \u00e7do moment. P\u00ebrve\u00e7 platformave t\u00eb p\u00ebrmendura n\u00eb imazhin kryesor, kompania gjithashtu bashk\u00ebpunon aktivisht me ofruesit e sh\u00ebrbimeve cloud n\u00eb Rusi: Yandex.Cloud, KROK \u201cSh\u00ebrbimet Cloud\u201d, Mail.ru dhe shum\u00eb t\u00eb tjer\u00eb. Po ashtu, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb theksohet se n\u00eb vitin 2020 kompania krijoi nj\u00eb qend\u00ebr R&D q\u00eb ndodhet n\u00eb Skolkovo.\u00a0<\/p>\n

Zgjedhja e nj\u00eb zgjidhjeje nga nj\u00eb num\u00ebr i madh lojtar\u00ebsh n\u00eb treg tregon nj\u00eb politik\u00eb t\u00eb mir\u00eb \u00e7mimi dhe nj\u00eb aplikueshm\u00ebri t\u00eb lart\u00eb t\u00eb produktit, gj\u00eb q\u00eb ne vendos\u00ebm ta verifikojm\u00eb n\u00eb praktik\u00eb.<\/p>\n

Pra, detyra jon\u00eb e testimit do t\u00eb p\u00ebrfshij\u00eb migrimin nga platforma ime testuese VMware dhe makinat fizike n\u00eb platform\u00ebn e ofruesit, gjithashtu n\u00ebn menaxhimin e VMware. Po, ka shum\u00eb zgjidhje q\u00eb mund t\u00eb realizojn\u00eb nj\u00eb migrim t\u00eb till\u00eb, por ne e shohim Hystax si nj\u00eb mjet universal, dhe t\u00eb testosh migrimin n\u00eb t\u00eb gjitha kombinimet e mundshme \u00ebsht\u00eb nj\u00eb detyr\u00eb e pamundur. Po ashtu, cloud-i Oncloud.ru \u00ebsht\u00eb nd\u00ebrtuar pik\u00ebrisht mbi VMware, k\u00ebshtu q\u00eb kjo platform\u00eb na intereson m\u00eb shum\u00eb si q\u00ebllim. M\u00eb posht\u00eb do t\u00eb p\u00ebrshkruaj parimin kryesor t\u00eb funksionimit, i cili n\u00eb p\u00ebrgjith\u00ebsi nuk varet nga platforma, dhe VMware mund t\u00eb z\u00ebvend\u00ebsohet me platform\u00ebn e ndonj\u00eb ofruesi tjet\u00ebr.\u00a0<\/p>\n

N\u00eb faz\u00ebn e par\u00eb, duhet t\u00eb filloni Hystax Acura, e cila \u00ebsht\u00eb paneli i menaxhimit t\u00eb sistemit.<\/p>\n

\"Hystax<\/a><\/noindex>
\nAjo fillon nga nj\u00eb model. P\u00ebr nj\u00eb arsye, n\u00eb rastin ton\u00eb, modeli ishte jo plot\u00ebsisht korrekt dhe n\u00eb vend t\u00eb 8CPU, 16Gb t\u00eb rekomanduara, u shfaq me burime dyfish m\u00eb t\u00eb ul\u00ebta. Prandaj, mos harroni t'i ndryshoni ato, p\u00ebrndryshe infrastruktura brenda VM, mbi t\u00eb cil\u00ebn \u00ebsht\u00eb nd\u00ebrtuar gjith\u00e7ka, nuk do t\u00eb nis\u00eb dhe portali do t\u00eb jet\u00eb i paarritsh\u00ebm. N\u00eb K\u00ebrkesat e instalimit<\/a><\/noindex> jan\u00eb p\u00ebrshkruar n\u00eb detaje burimet e nevojshme, si dhe portet p\u00ebr t\u00eb gjith\u00eb komponent\u00ebt e sistemit.\u00a0<\/p>\n

Po ashtu, kishim v\u00ebshtir\u00ebsi me caktimin e adres\u00ebs IP p\u00ebrmes modelit, k\u00ebshtu q\u00eb e ndryshuam at\u00eb nga konsola. Pas k\u00ebsaj, mund t\u00eb hyni n\u00eb nd\u00ebrfaqen web t\u00eb administratorit dhe t\u00eb plot\u00ebsoni asistentin fillestar t\u00eb konfigurimit.\u00a0<\/p>\n

\"Hystax<\/a><\/noindex>
\n\"Hystax<\/a><\/noindex>
\nEndpoint \u2013 IP ose FQDN i vCenter ton\u00eb.\u00a0
\nLogin dhe Password \u2013 k\u00ebtu \u00ebsht\u00eb e qart\u00eb.\u00a0
\nTarget ESXi hostname \u2013 nj\u00eb nga hostet e klasit ton\u00eb, n\u00eb t\u00eb cilin do t\u00eb realizohet replikimi.\u00a0
\nTarget datastore \u2013 nj\u00eb nga datastore-t e klasit ton\u00eb, n\u00eb t\u00eb cilin do t\u00eb realizohet replikimi.
\nHystax Acura Control Panel Public IP \u2013 adresa, p\u00ebr t\u00eb cil\u00ebn do t\u00eb jet\u00eb e arritshme paneli i menaxhimit.<\/p>\n

Duhet sqarim i vog\u00ebl p\u00ebr hostin dhe datastore-in. Problemi \u00ebsht\u00eb se replikimi Hystax punon n\u00eb nivelin e hostit dhe datastore-it. M\u00eb von\u00eb do t\u00eb tregoj se si mund t\u00eb ndryshoni hostin dhe datastore-in p\u00ebr tenantin, por problemi \u00ebsht\u00eb tjet\u00ebr. Hystax nuk mb\u00ebshtet pun\u00ebn me grupe burimesh, dmth, replikimi gjithmon\u00eb do t\u00eb ndodh\u00eb n\u00eb rr\u00ebnj\u00ebn e klas\u00ebs (n\u00eb koh\u00ebn e shkruarjes s\u00eb k\u00ebtij materiali, ata n\u00eb Hystax lan\u00e7uam nj\u00eb version t\u00eb p\u00ebrdit\u00ebsuar, ku shpejt zbatuan k\u00ebrkes\u00ebn time p\u00ebr mb\u00ebshtetje p\u00ebr grupet e burimeve). Po ashtu, nuk mb\u00ebshtetet as vCloud Director, dmth, n\u00ebse, si n\u00eb rastin tim, tenanti nuk ka t\u00eb drejta administrative p\u00ebr t\u00ebr\u00eb klasin, vet\u00ebm p\u00ebr nj\u00eb grup specifik burimesh, dhe ne i dham\u00eb akses Hystax, ai do t\u00eb jet\u00eb n\u00eb gjendje t\u00eb b\u00ebj\u00eb replikimin dhe t\u00eb niste k\u00ebto VM, por nuk do t\u00eb mund t'i shihte ato n\u00eb infrastruktur\u00ebn VMware, p\u00ebr t\u00eb cil\u00ebn ka akses dhe, p\u00ebr pasoj\u00eb, t\u00eb menaxhonte m\u00eb tej makinat virtuale. Duhet q\u00eb administrator i klasit t\u00eb zhvendos\u00eb VM n\u00eb grupin e burimeve t\u00eb nevojsh\u00ebm ose t'i importe n\u00eb vCloud Director.<\/p>\n

Pse po e theksoj kaq shum\u00eb k\u00ebt\u00eb \u00e7\u00ebshtje? Sepse, sa e kuptoj un\u00eb konceptin e produktit, klienti duhet t\u00eb ket\u00eb mund\u00ebsin\u00eb t\u00eb realizoj\u00eb \u00e7do mig\u00ebrim ose DR vet\u00eb p\u00ebrmes panelit Acura. Por, deri m\u00eb tani mb\u00ebshtetje p\u00ebr VMware \u00ebsht\u00eb pak m\u00eb e prapambetur krahasuar me mb\u00ebshtetje p\u00ebr OpenStack, ku k\u00ebto mekanizma jan\u00eb tashm\u00eb t\u00eb realizuar.\u00a0<\/p>\n

Por le t\u00eb kthehemi te vendosja. Her\u00ebn e par\u00eb, pas konfigurimit fillestar t\u00eb panelit, na nevojitet t\u00eb krijojm\u00eb qiran\u00eb e par\u00eb n\u00eb sistemin ton\u00eb.<\/p>\n

\"Hystax<\/a><\/noindex>
\nT\u00eb gjitha fushat k\u00ebtu jan\u00eb t\u00eb qarta, do t\u00eb flas vet\u00ebm p\u00ebr fush\u00ebn Cloud. Ne tashm\u00eb kemi nj\u00eb 'cloud' 'default', q\u00eb e krijuam gjat\u00eb konfigurimit fillestar. Por n\u00ebse duam t\u00eb kemi mund\u00ebsin\u00eb t\u00eb vendosim \u00e7do qiramarr\u00ebs n\u00eb nj\u00eb datastor t\u00eb ve\u00e7ant\u00eb dhe n\u00eb nj\u00eb grup burimesh t\u00eb ve\u00e7ant\u00eb, mund t\u00eb realizojm\u00eb k\u00ebt\u00eb p\u00ebrmes krijimit t\u00eb 'cloud'-eve t\u00eb ve\u00e7anta p\u00ebr secilin nga klient\u00ebt tan\u00eb.<\/p>\n

\"Hystax<\/a><\/noindex>
\nN\u00eb form\u00ebn e shtimit t\u00eb nj\u00eb 'cloud'-i t\u00eb ri ne specifikojm\u00eb t\u00eb nj\u00ebjtat parametra q\u00eb p\u00ebrdor\u00ebm gjat\u00eb konfigurimit fillestar (madje mund t\u00eb p\u00ebrdorim t\u00eb nj\u00ebjtin host), specifikojm\u00eb datastorin e nevojsh\u00ebm p\u00ebr klientin e caktuar, dhe tani n\u00eb parametrat shtes\u00eb mund t\u00eb specifikojm\u00eb individualisht grupin e burimeve t\u00eb nevojsh\u00ebm {\"resource_pool\": \"YOUR_POOL_NAME\"}\u00a0<\/p>\n

Si\u00e7 mund ta keni v\u00ebn\u00eb re, n\u00eb form\u00ebn e krijimit t\u00eb qiran\u00ebs nuk ka asgj\u00eb p\u00ebr ndarje burimesh apo kuota - nuk ekziston asgj\u00eb e till\u00eb n\u00eb sistem. Nuk mund t\u00eb kufizojm\u00eb qiran\u00eb nga numri i kopjeve t\u00eb nj\u00ebkohshme, numri i makinave p\u00ebr replikim ose ndonj\u00eb parametr tjet\u00ebr. K\u00ebshtu, ne kemi krijuar qiran\u00eb e par\u00eb. Tani ka nj\u00eb gj\u00eb jo krejt logjike, por t\u00eb domosdoshme - instalimi i agjentit Cloud. Ajo \u00ebsht\u00eb jo logjike, sepse agjenti shkarkohet n\u00eb faqen e klientit t\u00eb ve\u00e7ant\u00eb.<\/p>\n

\"Hystax<\/a><\/noindex>
\nMegjithat\u00eb, ai nuk \u00ebsht\u00eb i lidhur me qiran\u00eb e krijuar dhe p\u00ebrmes tij do t\u00eb punojn\u00eb t\u00eb gjith\u00eb klient\u00ebt tan\u00eb (apo p\u00ebrmes disa, n\u00ebse i kemi vendosur). Nj\u00eb agjent mb\u00ebshtet 10 sesione t\u00eb nj\u00ebkohshme. Nj\u00eb sesi konsiderohet nj\u00eb makin\u00eb. Nuk ka r\u00ebnd\u00ebsi sa disqe ka. Aktualisht, mekanizmi p\u00ebr shtrirjen e agjent\u00ebve n\u00eb vet\u00eb Acura p\u00ebr VMware nuk ekziston. Ka edhe nj\u00eb \u00e7\u00ebshtje tjet\u00ebr t\u00eb pak\u00ebndshme - nuk kemi mund\u00ebsi t\u00eb shohim nga paneli i Acura 'utilizimin' e k\u00ebtij agjenti, p\u00ebr t\u00eb nxjerr\u00eb p\u00ebrfundimin n\u00ebse na nevojitet t\u00eb vendosim akoma nj\u00eb tjet\u00ebr apo \u00ebsht\u00eb e mjaftueshme instalimi aktual. N\u00eb fund, skena duket si n\u00eb vijim:<\/p>\n

\"Hystax<\/a><\/noindex>
\nHapi tjet\u00ebr p\u00ebr t\u00eb pasur akses n\u00eb portalin e klientit ton\u00eb \u00ebsht\u00eb krijimi i nj\u00eb llogarie (dhe paraprakisht, nj\u00eb roli q\u00eb do t\u00eb aplikohet p\u00ebr k\u00ebt\u00eb p\u00ebrdorues).<\/p>\n

\"Hystax<\/a><\/noindex>
\n\"Hystax<\/a><\/noindex>
\nTani klienti yn\u00eb mund t\u00eb p\u00ebrdor\u00eb portalin vet\u00eb. E vetmja gj\u00eb q\u00eb duhet t\u00eb b\u00ebj\u00eb \u00ebsht\u00eb t\u00eb shkarkoj\u00eb agjent\u00ebt nga portali dhe t'i instaloj\u00eb n\u00eb an\u00ebn e tij. Ekzistojn\u00eb tre lloje agjent\u00ebsh: Linux, Windows dhe VMware.<\/p>\n

\"Hystax<\/a><\/noindex>
\nT\u00eb par\u00ebt dy instalohen n\u00eb pajisje fizike ose n\u00eb makina virtuale n\u00eb \u00e7do hipervizor, p\u00ebrve\u00e7 VMware. K\u00ebtu nuk k\u00ebrkohet asgj\u00eb tjet\u00ebr t\u00eb konfigurohet, agjenti shkarkohet dhe tashm\u00eb di ku t\u00eb drejtohet, dhe dosido brenda nj\u00eb minute makina do t\u00eb duket n\u00eb panelin Acura. Situata me agjentin VMware \u00ebsht\u00eb pak m\u00eb e komplikuar. Problemi \u00ebsht\u00eb se agjenti p\u00ebr VMware gjithashtu shkarkohet nga portali, i p\u00ebrgatitur dhe me konfigurimin e nevojsh\u00ebm. Por agjenti VMware p\u00ebrve\u00e7 njohjes s\u00eb portalit ton\u00eb Acura, duhet t\u00eb dij\u00eb gjithashtu p\u00ebr sistemin e virtualizimit n\u00eb t\u00eb cilin do t\u00eb vendoset.<\/p>\n

\"Hystax<\/a><\/noindex>
\nK\u00ebto t\u00eb dh\u00ebna sistemi do t'i k\u00ebrkoj\u00eb t\u00eb shpjegojm\u00eb gjat\u00eb shkarkimit t\u00eb par\u00eb t\u00eb agjentit VMware. Problemi \u00ebsht\u00eb se n\u00eb epok\u00ebn ton\u00eb t\u00eb dashuris\u00eb p\u00ebr sigurin\u00eb, shum\u00eb njer\u00ebz nuk do t\u00eb duan t\u00eb japin fjal\u00ebkalimin e administrat\u00ebs s\u00eb tyre n\u00eb nj\u00eb portal t\u00eb huaj, \u00e7ka \u00ebsht\u00eb krejt e kuptueshme. Nga brenda, pas vendosjes, agjenti nuk mund t\u00eb konfigurohet m\u00eb (mund t\u00eb ndryshoni vet\u00ebm parametrat e rrjetit). K\u00ebtu parashikoj v\u00ebshtir\u00ebsi me klient\u00ebt q\u00eb jan\u00eb t\u00eb shqet\u00ebsuar.\u00a0<\/p>\n

Pra, pas instalimit t\u00eb agjent\u00ebve, ne mund t\u00eb kthehemi n\u00eb panelin Acura dhe t\u00eb shohim t\u00eb gjitha makinat tona.<\/p>\n

\"Hystax<\/a><\/noindex>
\nDuke qen\u00eb se un\u00eb nuk jam dit\u00ebn e par\u00eb q\u00eb punoj me sistemin, kam makina n\u00eb gjendje t\u00eb ndryshme. T\u00eb gjitha jan\u00eb n\u00eb grupin Default, por ka mund\u00ebsi p\u00ebr t\u00eb krijuar grupe t\u00eb ve\u00e7anta dhe p\u00ebr t\u2019i transferuar aty makinat, si\u00e7 ju nevojitet. Kjo nuk ndikon n\u00eb asgj\u00eb - \u00ebsht\u00eb thjesht nj\u00eb p\u00ebrfaq\u00ebsim logjik i t\u00eb dh\u00ebnave dhe grupimi i tyre p\u00ebr nj\u00eb pun\u00eb m\u00eb t\u00eb rehatshme. E para dhe m\u00eb e r\u00ebnd\u00ebsishmja, q\u00eb duhet t\u00eb b\u00ebjm\u00eb pas k\u00ebsaj, \u00ebsht\u00eb t\u00eb fillojm\u00eb procesin e mig\u00ebrimit. Ne mund ta b\u00ebjm\u00eb k\u00ebt\u00eb si me forc\u00eb manualisht, ashtu edhe t\u00eb planifikojm\u00eb, p\u00ebrfshir\u00eb edhe masivisht p\u00ebr t\u00eb gjitha makinat nj\u00ebkoh\u00ebsisht.<\/p>\n

\"Hystax<\/a><\/noindex>
\nDua t\u2019ju rikujtoj se Hystax \u00ebsht\u00eb pozicionuar si nj\u00eb produkt p\u00ebr migrimin. Nuk \u00ebsht\u00eb e \u00e7uditshme q\u00eb p\u00ebr t\u00eb nisur makinat tona t\u00eb replik\u00ebs, na nevojitet t\u00eb krijojm\u00eb nj\u00eb plan DR. Plani mund t\u00eb hartohet p\u00ebr makinat q\u00eb jan\u00eb tashm\u00eb n\u00eb gjendjen Synced. Mund t\u00eb krijojm\u00eb p\u00ebr nj\u00eb VM t\u00eb ve\u00e7ant\u00eb ose p\u00ebr t\u00eb gjitha makinat nj\u00ebher\u00ebsh.<\/p>\n

\"Hystax<\/a><\/noindex>
\nGrupi i parametrave gjat\u00eb gjenerimit t\u00eb planit DR do t\u00eb ndryshoj\u00eb n\u00eb var\u00ebsi t\u00eb infrastruktur\u00ebs n\u00eb t\u00eb cil\u00ebn do t\u00eb migroni. P\u00ebr ambientin VMware \u00ebsht\u00eb n\u00eb dispozicion nj\u00eb grup minimal parametrash. Gjithashtu, Re-IP nuk mb\u00ebshtetet p\u00ebr makinat. N\u00eb k\u00ebt\u00eb plan, na interesojn\u00eb k\u00ebto pika: n\u00eb p\u00ebrshkrimin e VM, parametri \"subnet\": \"VMNetwork\", ku lidhim VM me nj\u00eb rrjet t\u00eb caktuar n\u00eb klaster. Rank \u2013 \u00ebsht\u00eb i r\u00ebnd\u00ebsish\u00ebm kur migroni disa VM, p\u00ebrcakton renditjen e nisjes s\u00eb tyre. Flavor \u2013 p\u00ebrshkruan konfigurimin e VM, n\u00eb k\u00ebt\u00eb rast \u2013 1CPU, 2GB RAM. N\u00eb seksionin subnets p\u00ebrcaktojm\u00eb q\u00eb \"subnet\": \"VMNetwork\" \u00ebsht\u00eb i lidhur me rrjetin \"VM Network\" VMware.\u00a0<\/p>\n

Kur krijoni planin DR, nuk ka mund\u00ebsi t\u00eb \"ndar\u00eb\" disk\u00ebt n\u00eb data store t\u00eb ndryshme. Ata do t\u00eb ndodhen n\u00eb t\u00eb nj\u00ebjtin data store q\u00eb \u00ebsht\u00eb p\u00ebrcaktuar p\u00ebr k\u00ebt\u00eb cloud klienti, dhe n\u00ebse keni disqe t\u00eb klasave t\u00eb ndryshme, kjo mund t\u00eb shkaktoj\u00eb disa v\u00ebshtir\u00ebsi gjat\u00eb nisjes s\u00eb makin\u00ebs, dhe pas nisjes dhe \"\u00e7lirimit\" t\u00eb VM nga Hystax, do t\u00eb k\u00ebrkoj\u00eb gjithashtu nj\u00eb migrim t\u00eb ve\u00e7ant\u00eb t\u00eb disqeve n\u00eb data store t\u00eb nevojshme. M\u00eb pas na mbetet vet\u00ebm t\u00eb nisim planin ton\u00eb DR dhe t\u00eb presim derisa makinat tona t\u00eb ngrihen. Procesi i konvertimit P2V\/V2V gjithashtu merr koh\u00eb. N\u00eb makin\u00ebn time m\u00eb t\u00eb madhe t\u00eb testimit me 100GB dhe tre disqe, kjo zgjati maksimumi 10 minuta.<\/p>\n

\"Hystax<\/a><\/noindex>
\nPas k\u00ebsaj, duhet t\u00eb kontrolloni VM-n\u00eb e nisur, sh\u00ebrbimet mbi t\u00eb, konsistenc\u00ebn e t\u00eb dh\u00ebnave dhe t\u00eb b\u00ebni kontrollime t\u00eb tjera.\u00a0<\/p>\n

M\u00eb pas ne kemi dy mund\u00ebsi:\u00a0<\/p>\n

    \n
  1. Delete \u2013 fshij\u00eb planin DR t\u00eb nisur. Ky veprim do t\u00eb shkat\u00ebrroj\u00eb vet\u00ebm VM-n\u00eb e nisur. Replica e t\u00eb dh\u00ebnave nuk do t\u00eb humbas\u00eb.\u00a0<\/li>\n
  2. Detach \u2013 ndan\u00eb makin\u00ebn e replikuar nga Acura, pra p\u00ebrfundon procesin e migrimit.\u00a0<\/li>\n<\/ol>\n

    \nAvantazhet e zgjidhjes:<\/strong>\u00a0<\/p>\n