{"id":33622,"date":"2019-10-31T21:53:47","date_gmt":"2019-10-31T18:53:47","guid":{"rendered":"https:\/\/prohoster.info\/blog\/veeam-backup-replication-poleznye-sovety-po-obespecheniyu-zhiznesposobnosti-bekapov-i-replik\/"},"modified":"2019-10-31T21:53:47","modified_gmt":"2019-10-31T18:53:47","slug":"veeam-backup-replication-poleznye-sovety-po-obespecheniyu-zhiznesposobnosti-bekapov-i-replik","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/veeam-backup-replication-poleznye-sovety-po-obespecheniyu-zhiznesposobnosti-bekapov-i-replik","title":{"rendered":"Veeam Backup & Replication: k\u00ebshilla t\u00eb dobishme p\u00ebr garantimin e q\u00ebndrueshm\u00ebris\u00eb s\u00eb backup-eve dhe replikave","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sot u lutem, sot po prezantoj p\u00ebrs\u00ebri disa k\u00ebshilla t\u00eb dobishme nga kolegu im Evgeny Ivanov, lideri i ekipit t\u00eb mb\u00ebshtetjes teknike t\u00eb Veeam. K\u00ebt\u00eb her\u00eb, Zhenya ndau rekomandime p\u00ebr pun\u00ebn me backup-et dhe replikat. Shpresoj se ato do t'ju ndihmojn\u00eb t\u00eb evitoni gabimet tipike dhe replikat dhe backup-et tuaj kurr\u00eb nuk do t\u00eb jen\u00eb \"n\u00ebpik\u00eb p\u00ebr dob\u00ebsi\" n\u00eb procesin e rikuperimit, n\u00ebse do t\u00eb jet\u00eb e nevojshme. <\/p>\n

Pra, mir\u00ebsevini n\u00ebn k\u00ebt\u00eb postim.<\/p>\n

\"Veeam
\n<\/a><\/noindex>
\nN\u00eb p\u00ebrmas\u00ebn time t\u00eb kaluar artikulli yn\u00eb<\/a><\/noindex> ne u merrem me optimizimin e ngarkes\u00ebs n\u00eb komponent\u00ebt e infrastruktur\u00ebs s\u00eb kopjimit, dhe shqyrtuam gabimet tipike t\u00eb konfigurimit. Tani kalojm\u00eb te nj\u00eb tem\u00eb tjet\u00ebr t\u00eb r\u00ebnd\u00ebsishme \u2013 p\u00ebrgatitja dhe kryerja e rikuperimit. K\u00ebt\u00eb tem\u00eb do ta shqyrtojm\u00eb gjithashtu me shembuj real\u00eb me t\u00eb cil\u00ebt ekipi i mb\u00ebshtetjes teknike ka punuar.<\/p>\n

Backup pa restaurim \u2013 para t\u00eb humbura<\/h1>\n

\nK\u00ebtu shpesh na kontaktojn\u00eb p\u00ebrdoruesit q\u00eb e kan\u00eb gjetur veten n\u00eb situata t\u00eb ngjashme: duhet t\u00eb kryejn\u00eb rikuperimin nga nj\u00eb backup, por gjat\u00eb p\u00ebrpjekjes p\u00ebr ta b\u00ebr\u00eb k\u00ebt\u00eb, ata hasin nj\u00eb problem t\u00eb pazgjidhsh\u00ebm. Dhe ky problem \u2013 nuk \u00ebsht\u00eb aspak mungesa e nj\u00eb kopjeje rezerv\u00eb, veprimet e CryptoLocker ose di\u00e7ka e ngjashme. \u00cbsht\u00eb \"vet\u00ebm\" mungesa e v\u00ebmendjes ndaj verifikimit t\u00eb kopjeve rezerv\u00eb dhe replikave p\u00ebr mund\u00ebsin\u00eb e rikuperimit. Shum\u00eb shpesh p\u00ebrqendrohen vet\u00ebm n\u00eb procesin e krijimit t\u00eb backup-it, duke harruar se thjesht ekzistenca e nj\u00eb kopjeje rezerv\u00eb nuk \u00ebsht\u00eb nj\u00eb panacee p\u00ebr mund\u00ebsit\u00eb e mundshme t\u00eb fatkeq\u00ebsis\u00eb. Duhet t\u00eb kuptojm\u00eb se rikuperimi \u00ebsht\u00eb nj\u00eb proces krejt\u00ebsisht i ndrysh\u00ebm, me ve\u00e7orit\u00eb e tij, dhe q\u00eb patjet\u00ebr duhet t\u00eb kontrollohet dhe testohet para se t\u00eb filloj\u00eb n\u00eb prodhim. Ja disa shembuj t\u00eb duksh\u00ebm:<\/p>\n

    \n
  1. Nj\u00eb p\u00ebrdorues kishte nj\u00eb d\u00ebshtim n\u00eb pun\u00ebn e nj\u00eb makine virtuale kritike me madh\u00ebsi 20 TB. Nd\u00ebrprerjet, natyrisht, jan\u00eb t\u00eb papranueshme, dhe administratorit fillon procesin e rikuperimit t\u00eb menj\u00ebhersh\u00ebm (VM instant recovery) \u2013 pas 5 minutash, makina \u00ebsht\u00eb ngritur. Por ne e kujtojm\u00eb se ky gjendje e makin\u00ebs mund t\u00eb p\u00ebrdoret vet\u00ebm p\u00ebrkoh\u00ebsisht \u2013 ajo patjet\u00ebr duhet t\u00eb migrohet n\u00eb datastorin e prodhimit (datastore). N\u00eb k\u00ebt\u00eb rast, si\u00e7 u zbulua, mund\u00ebsit\u00eb e infrastruktur\u00ebs nuk lejonin kopjimin e 20 TB t\u00eb t\u00eb dh\u00ebnave p\u00ebr nj\u00eb koh\u00eb t\u00eb arsyeshme. N\u00eb cil\u00ebsimet e procesit t\u00eb rikuperimit t\u00eb menj\u00ebhersh\u00ebm, ishte zgjedhur t\u00eb ruaj\u00eb ndryshimet n\u00eb disk Nga:<\/i> Serverat Veeam Backup & Replication (ndryshe nga snapshot-i i vSphere) - si rezultat, natyrisht hap\u00ebsira n\u00eb disk u mbush shpejt. N\u00eb momentin q\u00eb p\u00ebrdoruesi u paraqit n\u00eb suport, VM kishte ndryshime q\u00eb nuk mund t\u00eb injoroheshin. Pra, kemi nj\u00eb situat\u00eb kur nuk \u00ebsht\u00eb e mundur t\u00eb finalizohet shpejt procesi i rikuperimit t\u00eb menj\u00ebhersh\u00ebm t\u00eb makineris\u00eb kritike - si t\u00eb shp\u00ebtojm\u00eb t\u00eb dh\u00ebnat?\n

    T\u00eb them t\u00eb drejt\u00ebn, p\u00ebr shkak t\u00eb kalimit t\u00eb viteve nuk e mbaj mend t\u00eb gjitha detajet e finales, por e mbaj mend se n\u00eb fund nuk arrit\u00ebm t\u00eb shk\u00ebputnim asgj\u00eb geniale. Klient\u00ebt nga ana e tyre, me disa v\u00ebshtir\u00ebsi, e zgjidh\u00ebn k\u00ebt\u00eb problem, duke zgjeruar diskun C: nga rezervat, kopjuan skedar\u00ebt m\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm dhe m\u00eb pas ndaluan VM-n\u00eb dhe k\u00ebshtu migruan. N\u00eb p\u00ebrgjith\u00ebsi, nuk ndodhi asnj\u00eb mrekulli.<\/li>\n

  2. N\u00eb infrastruktur\u00ebn e p\u00ebrdoruesit punonte nj\u00eb kontrollues domeni, dhe t\u00eb gjith\u00eb komponent\u00ebt e Veeam Backup & Replication ishin konfiguratuar duke p\u00ebrdorur DNS. Po, po, pik\u00ebrisht k\u00ebshtu, nuk e ke d\u00ebgjuar gabim. Kishte nj\u00ebqind mund\u00ebsi zhvillimi t\u00eb ngjarjeve, por realiteti ishte ky: njer\u00ebzit kishin planifikuar mir\u00ebmbajtjen dhe vendos\u00ebn t\u00eb kalonin n\u00eb replik\u00ebn e kontrolluesit t\u00eb tyre t\u00eb domainit. Ata p\u00ebrdor\u00ebn kalimin e planifikuar, q\u00eb n\u00eb p\u00ebrgjith\u00ebsi rekomandohet t\u00eb b\u00ebhet n\u00eb situata t\u00eb tilla. N\u00eb faz\u00ebn e par\u00eb gjith\u00e7ka shkoi mir\u00eb, dhe n\u00eb faz\u00ebn e dyt\u00eb VM-n\u00eb e ndal\u00ebn p\u00ebr pak, p\u00ebr t\u00eb transferuar mbetjet e t\u00eb dh\u00ebnave. Natyrisht, detyra e kalimit p\u00ebrfundoi menj\u00ebher\u00eb me nj\u00eb gabim, pasi DNS pushoi s\u00eb punuari.\n

    Fatmir\u00ebsisht, k\u00ebtu arrit\u00ebm t\u00eb menaxhonim situat\u00ebn, duke aktivizuar replik\u00ebn manualisht nga vSphere (n\u00eb t\u00eb v\u00ebrtet\u00eb, kjo operacion nuk rekomandohet t\u00eb b\u00ebhet vet\u00eb, si\u00e7 do t\u00eb shihni n\u00eb shembullin e ardhsh\u00ebm). Por, si\u00e7 e kuptoni, procesi i mir\u00ebmbajtjes u nd\u00ebrpre dhe u shty. P\u00ebr m\u00eb tep\u00ebr, na duhej t\u00eb futnim manualisht emrat e hosteve n\u00eb skedarin C:WindowsSystem32driversetchosts<\/i> n\u00eb serverin Veeam Backup & Replication, p\u00ebr t\u00eb siguruar sakt\u00ebsin\u00eb gjat\u00eb rikthimit t\u00ebr\u00ebsor.<\/li>\n

  3. Nj\u00eb klient tjet\u00ebr kishte nd\u00ebrtuar t\u00eb gjith\u00eb infrastruktur\u00ebn e kopjimit t\u00eb t\u00eb dh\u00ebnave rreth disqeve t\u00eb magnetik\u00ebs, nd\u00ebrsa n\u00eb disk ruheshin vet\u00ebm disa skedar\u00eb t\u00eb shkurt\u00ebr. Kur iu nevojit t\u00eb rikthej\u00eb disa skedar\u00eb nga nj\u00eb server i madh i skedar\u00ebve, doli se asnj\u00eb makin\u00eb nuk mund t\u00eb p\u00ebrdorej si depo ndihm\u00ebse p\u00ebr rikthimin nga banda, pasi asnj\u00ebra prej tyre nuk kishte hap\u00ebsir\u00eb t\u00eb mjaftueshme t\u00eb lir\u00eb. (P\u00ebr rikthimin nga banda direkt dhe duke p\u00ebrdorur nj\u00eb depo ndihm\u00ebse, mund t\u00eb lexoni k\u00ebtu<\/a><\/noindex> (p\u00ebr momentin n\u00eb anglisht)).<\/li>\n<\/ol>\n

    \nMendoj se n\u00eb t\u00eb tre shembujt e p\u00ebrmendur, p\u00ebrdoruesit, si\u00e7 thon\u00eb, ishin n\u00eb nj\u00eb iluzion - ata supozuan se n\u00ebse backup-i kishte kaluar me sukses, at\u00ebher\u00eb nuk do t\u00eb kishin probleme me rikthimin. Por, si\u00e7 e kuptoni, kjo nuk \u00ebsht\u00eb gjithmon\u00eb e till\u00eb, dhe prandaj rikthimi duhet t\u00eb p\u00ebrgatitet po aq seriozisht sa edhe backup-i. Fillimisht, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb studioheni guidi i p\u00ebrdoruesit<\/a><\/noindex>, ku p\u00ebrmban informacione t\u00eb detajuara n\u00eb lidhje me llojet e ndryshme t\u00eb rikthimit. N\u00eb fillim t\u00eb \u00e7do paragrafi renditen k\u00ebrkesat, veprimet p\u00ebrgatitore dhe kufizimet e mundshme. P\u00ebrshkrimi i rikthimit nga disqet magnetike ose nga snapshotet harduerike t\u00eb SAN mund t\u00eb gjendet n\u00eb seksionet e dokumentacionit dhe n\u00eb ne kemi njohur me bazat e DATA VAULT, zgjerimin e DATA VAULT n\u00eb nj\u00eb gjendje m\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr analiz\u00eb dhe krijimin e BUSINESS DATA VAULT. Ka ardhur koha p\u00ebr t\u00eb p\u00ebrfunduar ciklin me artikullin e tret\u00eb.<\/a><\/noindex> n\u00eb Habr\u00e9. P\u00ebr m\u00eb tep\u00ebr, veprimet p\u00ebrgatitore p\u00ebr rikthimin e objekteve t\u00eb aplikacioneve duke p\u00ebrdorur mjetet Veeam Explorers jan\u00eb p\u00ebrshkruar n\u00eb seksionin 'Planifikimi dhe p\u00ebrgatitja' udh\u00ebzimet<\/a><\/noindex> p\u00ebr \u00e7do mjet. Ju rekomandoj t\u00eb familiarizoheni me to \u2014 kjo do t'ju ndihmoj\u00eb t\u00eb p\u00ebrgatitni sistemin p\u00ebr rikthim n\u00eb rast nevoje. N\u00eb gjuh\u00ebn rusisht, udh\u00ebzimet p\u00ebr rikthimin e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave SQL Server jan\u00eb t\u00eb dh\u00ebna k\u00ebtu<\/a><\/noindex>.<\/p>\n

    Pse nuk duhet punuar me replikat nga konsola e vSphere?<\/h1>\n

    \nTeorikisht, replikat e Veeam p\u00ebrfaq\u00ebsojn\u00eb makina t\u00eb zakonshme virtuale, me t\u00eb cilat, n\u00eb dukje, do t\u00eb ishte logjike t\u00eb punonit, duke p\u00ebrdorur mjetet e vSphere, ve\u00e7an\u00ebrisht klientin vSphere. Megjithat\u00eb, ne nuk e rekomandojm\u00eb k\u00ebt\u00eb, dhe ja pse: kalimi n\u00eb replik\u00ebn n\u00eb Veeam Backup & Replication \u00ebsht\u00eb nj\u00eb proces mjaft i nd\u00ebrlikuar, q\u00eb k\u00ebrkon nj\u00eb ekzekutim t\u00eb rrept\u00eb n\u00eb radh\u00eb t\u00eb hapat (n\u00eb m\u00ebnyr\u00eb q\u00eb, n\u00eb rast ndonj\u00eb pengese, t\u00eb mund t\u00eb ktheheni nj\u00eb hap prapa) dhe veprime p\u00ebrfundimtare t\u00eb sakta \u2013 thjesht shihni imazhin q\u00eb ilustron procesin:<\/p>\n

    \"Veeam
    \n
    \nN\u00ebse vendosni t\u00eb aktivizoni replik\u00ebn nga vSphere client, ka shum\u00eb mund\u00ebsi q\u00eb m\u00eb pas t\u00eb p\u00ebrballeni me nj\u00eb s\u00ebr\u00eb problemesh:<\/p>\n

      \n
    1. Mekanizmi i kalimit n\u00eb replik\u00ebn nga Veeam Backup & replication (i paraqitur n\u00eb diagram) nuk do t\u00eb funksionoj\u00eb m\u00eb p\u00ebr k\u00ebt\u00eb makin\u00eb.<\/li>\n
    2. T\u00eb dh\u00ebnat n\u00eb baz\u00ebn e Veeam Backup nuk do t\u00eb p\u00ebrputhen me gjendjen aktuale t\u00eb VM. N\u00eb rastin m\u00eb t\u00eb keq, p\u00ebr t\u00eb riparuar do t\u00eb duhet t\u00eb redaktoni baz\u00ebn.<\/li>\n
    3. Madje mund t\u00eb ndodhi humbja e t\u00eb dh\u00ebnave, si\u00e7 \u00ebsht\u00eb rasti m\u00eb posht\u00eb: p\u00ebrdoruesi aktivizoi manualisht replik\u00ebn n\u00eb vSphere client dhe vendosi t\u00eb vazhdoj\u00eb pun\u00ebn me t\u00eb. Pasi kaloi nj\u00eb koh\u00eb, vuri re se replika ende shfaqej n\u00eb konsol\u00ebn Veeam Backup & Replication, dhe vendosi ta heq\u00eb at\u00eb si t\u00eb padobishme. Klikoi mbi t\u00eb me t\u00eb djatht\u00ebn dhe dha komand\u00ebn \u00abFshij nga disku\u00bb<\/i>. Veeam Backup & Replication menj\u00ebher\u00eb e fshiu nga disku replik\u00ebn, e cila, p\u00ebr t'ju kujtuar, tashm\u00eb ishte duke u p\u00ebrdorur si nj\u00eb VM e zakonshme dhe p\u00ebrmbante t\u00eb dh\u00ebna t\u00eb nevojshme dhe t\u00eb dobishme.<\/li>\n<\/ol>\n

      \nSigurisht, ka situata kur pranohet t\u00eb aktivizohet replik\u00eb nga vSphere client \u2013 zakonisht kjo ndodh kur serveri Veeam \u00ebsht\u00eb fikur dhe replik\u00ebn duhet ta aktivizoni me vones\u00eb. Por n\u00ebse me serverin Veeam \u00ebsht\u00eb gjith\u00e7ka n\u00eb rregull, at\u00ebher\u00eb duhet t\u00eb punoni me replikat pik\u00ebrisht nga konsola e tij.<\/p>\n

      Gjithashtu nuk duhet t\u00eb fshihni replikat duke p\u00ebrdorur vSphere client. Veeam Backup & Replication do t\u00eb mbetet n\u00eb ignorance n\u00eb lidhje me k\u00ebt\u00eb ndryshim, dhe kjo \u00ebsht\u00eb e rrezikshme p\u00ebrgabime dhe t\u00eb dh\u00ebna t\u00eb skaduara. N\u00ebse replika nuk ju nevojitet m\u00eb, fshijeni at\u00eb p\u00ebrmes konsol\u00ebs Veeam, dhe jo si nj\u00eb VM nga vSphere client. K\u00ebshtu do t\u00eb keni gjithmon\u00eb nj\u00eb list\u00eb aktuale t\u00eb replikave. <\/p>\n

      \u00abO\u00bb \u2014 kujdes, p\u00ebrdit\u00ebsime!<\/h1>\n

      \nK\u00ebtu, natyrisht, flasim p\u00ebr p\u00ebrdit\u00ebsimet p\u00ebr hipervizor\u00ebt dhe aplikacione t\u00eb ndryshme q\u00eb b\u00ebjn\u00eb backup me Veeam. N\u00ebse i shohim ato nga pik\u00ebpamja e pun\u00ebs me Veeam Backup & Replication, p\u00ebrdit\u00ebsimet mund t\u00eb ndahen n\u00eb dy kategori: t\u00eb m\u00ebdha, serioze, q\u00eb sjellin shum\u00eb ndryshime \u2013 dhe t\u00eb vogla.<\/p>\n

      Le t'i shqyrtojm\u00eb s\u00eb pari kategorin\u00eb e par\u00eb. <\/p>\n

      P\u00ebrdit\u00ebsimet m\u00eb t\u00eb r\u00ebnd\u00ebsishme jan\u00eb ato q\u00eb jan\u00eb p\u00ebr hypervisorin. Para se t\u00eb instaloni nj\u00eb p\u00ebrdit\u00ebsim t\u00eb till\u00eb, patjet\u00ebr duhet t\u00eb siguroheni q\u00eb ai mb\u00ebshtetet nga Veeam Backup & Replication. T\u00eb tilla p\u00ebrdit\u00ebsime sjellin shum\u00eb ndryshime n\u00eb bibliotekat dhe nd\u00ebrfaqet API q\u00eb p\u00ebrdor Veeam Backup & Replication, prandaj p\u00ebr t\u00eb deklaruar zyrtarisht mb\u00ebshtetje p\u00ebr to, duhet t\u00eb p\u00ebrdit\u00ebsoni kodin e Veeam Backup & Replication dhe t\u00eb kryeni nj\u00eb testim t\u00eb kujdessh\u00ebm. <\/p>\n

      Duhet gjithashtu t\u00eb keni parasysh se, p\u00ebr shembull, VMware nuk ofron qasje t\u00eb p\u00ebrparuar n\u00eb versionet m\u00eb t\u00eb reja t\u00eb vSphere p\u00ebr prodhuesit e softuerit, k\u00ebshtu q\u00eb zhvilluesit dhe tester\u00ebt e Veeam marrin versionin e ri n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb me gjith\u00eb njer\u00ebzimin progresiv \u2013 prandaj ndonj\u00ebher\u00eb kalon nj\u00eb periudh\u00eb e caktuar kohore mes daljes s\u00eb VMware dhe mb\u00ebshtetjes s\u00eb shpallur zyrtarisht. Numri dhe diversiteti i ndryshimeve q\u00eb duhet t\u00eb b\u00ebhen jan\u00eb t\u00eb till\u00eb, sa q\u00eb ka pak shanse q\u00eb ato t\u00eb p\u00ebrfshihen n\u00eb nj\u00eb hotfix t\u00eb thjesht\u00eb \u2013 dhe mb\u00ebshtetje zyrtare zakonisht shpallet bashk\u00eb me daljen e versionit t\u00eb ri t\u00eb Veeam Backup & Replication. <\/p>\n

      N\u00eb fund ndodh ai moment i sikletsh\u00ebm, kur pas daljes s\u00eb nj\u00eb versioni t\u00eb ri t\u00eb vSphere, numri i k\u00ebrkesave n\u00eb ndihm\u00ebn teknike rritet papritur, sepse p\u00ebrdoruesit nisen me ngut p\u00ebr t\u00eb instaluar versionin e ri dhe backup-et e tyre, sigurisht, menj\u00ebher\u00eb fillojn\u00eb t\u00eb mos funksionojn\u00eb. Ne \u2013 ndihma teknike e Veeam \u2013 duhet t'u shpjegojm\u00eb p\u00ebrdoruesve se \u00e7far\u00eb kan\u00eb b\u00ebr\u00eb gabim, t'u k\u00ebrkojm\u00eb t\u00eb kthehen pas (n\u00ebse \u00ebsht\u00eb e mundur) ose t\u00eb imagjinojm\u00eb m\u00ebnyra t\u00eb nd\u00ebrlikuara p\u00ebr t\u00eb dal\u00eb nga kjo situat\u00eb. Prandaj, para se t\u00eb instaloni nj\u00eb p\u00ebrdit\u00ebsim serioz, ju lutem kontrolloni p\u00ebrputhshm\u00ebrin\u00eb e tij me softin q\u00eb po p\u00ebrdorni!<\/b><\/p>\n

      \u00c7do gj\u00eb e th\u00ebn\u00eb m\u00eb sip\u00ebr vlen edhe p\u00ebr aplikacionet q\u00eb po b\u00ebni backup dhe planifikoni t'i riktheni me Veeam. Linja e mjeteve Veeam Explorers gjithashtu ka nj\u00eb list\u00eb t\u00eb versioneve p\u00ebrkat\u00ebse t\u00eb aplikacioneve q\u00eb jan\u00eb mb\u00ebshtetur, e cila plot\u00ebsohet me \u00e7do lirim t\u00eb Veeam Backup & Replication. Prandaj, para se t\u00eb instaloni versionin e ri t\u00eb aplikacionit tuaj \u2013 qoft\u00eb kjo Exchange, Oracle apo SharePoint \u2013 ju lutem lexoni p\u00ebrs\u00ebri seksionin p\u00ebrkat\u00ebs. t\u00eb dokumentacionit t\u00eb Veeam Explorers<\/a><\/noindex>.<\/p>\n

      N\u00eb kategorin\u00eb e dyt\u00eb, dometh\u00ebn\u00eb p\u00ebr p\u00ebrdit\u00ebsime t\u00eb vogla, p\u00ebrfshij ato si versionet e reja t\u00eb VMware Tools, p\u00ebrdit\u00ebsimet kumulative t\u00eb Exchange, p\u00ebrdit\u00ebsimet e siguris\u00eb t\u00eb vSphere, etj. N\u00eb shumic\u00ebn e rasteve, ato nuk sjellin ndonj\u00eb modifikim t\u00eb r\u00ebnd\u00ebsish\u00ebm, dhe n\u00eb shumic\u00ebn e rasteve, Veeam Backup & Replication nuk p\u00ebrballet me probleme p\u00ebr to. (Prandaj, nuk ka njoftime t\u00eb publikuara p\u00ebr mb\u00ebshtetje zyrtare n\u00eb produkt.) Sidoqoft\u00eb, n\u00eb praktikat tona, jan\u00eb shfaqur raste kur edhe k\u00ebto p\u00ebrdit\u00ebsime ndryshonin ndjesh\u00ebm rrjedh\u00ebn e zakonshme t\u00eb pun\u00ebs, duke sjell\u00eb gabime n\u00eb funksionimin e Veeam Backup & Replication. N\u00eb k\u00ebto situata, pas konfirmimit t\u00eb problemit, inxhinier\u00ebt e Veeam p\u00ebrpiqen t\u00eb publikojn\u00eb shpejt nj\u00eb hotfix.<\/p>\n

      P\u00ebr ata q\u00eb zot\u00ebrojn\u00eb anglishten teknike<\/b>N\u00ebse d\u00ebshironi t\u00eb jeni n\u00eb dijeni mbi at\u00eb q\u00eb po punojn\u00eb inxhinier\u00ebt dhe me \u00e7far\u00eb p\u00ebrballen arkitekt\u00ebt e sistemeve dhe specialist\u00ebt e mb\u00ebshtetjes teknike, rekomandoj t\u00eb abonoheni n\u00eb forumet tona<\/a><\/noindex>. \u00c7do jav\u00eb p\u00ebr abonent\u00ebt e saj del nj\u00eb buletin \"Fjala nga Gostev\" i autorit TheRealGostev<\/a><\/noindex>. N\u00eb t\u00eb, Anton Gostev, i cili drejton departamentin e menaxhimit t\u00eb produkteve, flet p\u00ebr problemet e zbuluara s\u00eb fundmi (dhe jo vet\u00ebm n\u00eb an\u00ebn e Veeam), planet p\u00ebr versionet e reja dhe lajmet nga bota e IT. N\u00ebse keni nevoj\u00eb p\u00ebr m\u00eb shum\u00eb informacion, mund t\u00eb shqyrtoni temat e forumit - n\u00ebse ndonj\u00eb klient ka zbuluar nj\u00eb problem me funksionimin e produktit pas ndonj\u00eb p\u00ebrdit\u00ebsimi, ai ka shkruar p\u00ebr k\u00ebt\u00eb n\u00eb forum.<\/p>\n

      Si e kuptoni, patch-et dhe p\u00ebrdit\u00ebsimet mund t\u00eb shkaktojn\u00eb probleme jo vet\u00ebm me backup-et, por edhe me aplikacionet p\u00ebr t\u00eb cilat b\u00ebhen k\u00ebto backup-e. Dhe k\u00ebtu do t'ju ndihmojn\u00eb laborator\u00ebt virtual\u00eb - Veeam DataLabs. Sigurisht q\u00eb keni d\u00ebgjuar p\u00ebr funksionalitetin SureBackup, i cili \u00ebsht\u00eb i dedikuar p\u00ebr v\u00ebrtetimin e kopjeve rezerv\u00eb. Ai bazohet pik\u00ebrisht n\u00eb p\u00ebrdorimin e DataLabs, duke krijuar nj\u00eb mjedis t\u00eb izoluar, n\u00eb t\u00eb cilin mund t\u00eb testoni p\u00ebrdit\u00ebsime para se t'i instaloni ato n\u00eb prodhim. E rekomandoj fort ta b\u00ebni k\u00ebt\u00eb - do t\u00eb kurseni shum\u00eb nerva. Dhe n\u00ebse dikush tjet\u00ebr nuk di p\u00ebr SureBackup, rekomandoj t\u00eb lexoni dokumentacion<\/a><\/noindex>.<\/p>\n

      M\u00eb duket se kjo \u00ebsht\u00eb gjith\u00e7ka p\u00ebr sot, faleminderit p\u00ebr v\u00ebmendjen!<\/p>\n

      \u00c7far\u00eb tjet\u00ebr t\u00eb lexoni<\/h1>\n

      \nArtikuj n\u00eb Habr\u00eb:<\/p>\n