{"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 sigurimin e jet\u00ebsis\u00eb s\u00eb backup-eve dhe replikave","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sot kam k\u00ebnaq\u00ebsin\u00eb t'ju prezantoj p\u00ebrs\u00ebri 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-e dhe replika. Shpresoj se ato do t'ju ndihmojn\u00eb t\u00eb evitoni gabimet tipike dhe q\u00eb replikat dhe backup-et tuaja kurr\u00eb nuk do t\u00eb jen\u00eb \"nj\u00eb pik\u00eb e dob\u00ebt\" n\u00eb procesin e rikuperimit, n\u00ebse e till\u00eb nevojitet. <\/p>\n

Pra, mir\u00eb se erdh\u00ebt posht\u00eb.<\/p>\n

\"Veeam
\n<\/a><\/noindex>
\nN\u00eb shkrimin tim t\u00eb m\u00ebparsh\u00ebm artikullin<\/a><\/noindex> ne shqyrtuam se si t\u00eb optimizojm\u00eb ngarkes\u00ebn n\u00eb komponent\u00ebt e infrastruktur\u00ebs s\u00eb backup-it dhe shqyrtuam gabimet tipike t\u00eb konfigurimit. Tani kalojm\u00eb n\u00eb nj\u00eb tem\u00eb tjet\u00ebr t\u00eb r\u00ebnd\u00ebsishme \u2013 p\u00ebrgatitjen e duhur dhe ekzekutimin e rikuperimit. K\u00ebt\u00eb tem\u00eb do ta shqyrtojm\u00eb gjithashtu p\u00ebrmes shembujve real\u00eb, me t\u00eb cil\u00ebt ekipi i mb\u00ebshtetjes teknike ka punuar.<\/p>\n

Backup pa restorant \u2013 para n\u00eb er\u00eb<\/h1>\n

\nP\u00ebrdoruesit na kontaktojn\u00eb rregullisht, duke u p\u00ebrballur me situata t\u00eb ngjashme: duhet t\u00eb kryejn\u00eb rikuperimin nga nj\u00eb kopje rezerv\u00eb, por kur p\u00ebrpiqen t\u00eb b\u00ebjn\u00eb k\u00ebt\u00eb, p\u00ebrballen me nj\u00eb problem t\u00eb pazgjidhsh\u00ebm p\u00ebr ta. Ky problem nuk \u00ebsht\u00eb fare mungesa e nj\u00eb kopjeje rezerv\u00eb, veprimtaria e CryptoLocker ose ndonj\u00eb gj\u00eb e ngjashme. \u00cbsht\u00eb \"thjesht\" mungesa e p\u00ebrkushtimit n\u00eb verifikimin e kopjeve rezerv\u00eb dhe replikave p\u00ebr mund\u00ebsin\u00eb e rikuperimit. Shum\u00eb shpesh p\u00ebrqendrohen ekskluzivisht n\u00eb procesin e krijimit t\u00eb kopjeve rezerv\u00eb, duke harruar se thjesht ekzistenca e nj\u00eb kopjeje rezerv\u00eb nuk \u00ebsht\u00eb nj\u00eb cure ndaj fatkeq\u00ebsive t\u00eb mundshme. Duhet t\u00eb kuptohet se rikuperimi \u00ebsht\u00eb nj\u00eb proces krejt\u00ebsisht tjet\u00ebr, 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 ilustrues:<\/p>\n

    \n
  1. Nj\u00eb p\u00ebrdorues kishte nj\u00eb d\u00ebshtim n\u00eb pun\u00ebn e nj\u00eb maachine kritike virtuale me madh\u00ebsin\u00eb 20 TB. Nd\u00ebrprerjet, natyrisht, jan\u00eb t\u00eb papranueshme, dhe administratori nis procesin e rikuperimit t\u00eb menj\u00ebhersh\u00ebm t\u00eb VM (VM instant recovery) \u2013 pas 5 minutash, makina \u00ebsht\u00eb rikuperuar. Por ne e dim\u00eb se nj\u00eb gjendje e till\u00eb e makin\u00ebs mund t\u00eb p\u00ebrdoret vet\u00ebm p\u00ebrkoh\u00ebsisht \u2013 ajo duhet patjet\u00ebr t\u00eb migrohet n\u00eb datastorin e prodhimit (datastore). Dhe n\u00eb k\u00ebt\u00eb rast, si\u00e7 rezultoi, aft\u00ebsit\u00eb e infrastruktur\u00ebs nuk lejonin q\u00eb t\u00eb eksportoheshin 20 TB t\u00eb dh\u00ebnash brenda nj\u00eb kohe t\u00eb arsyeshme. N\u00eb cil\u00ebsimet e procesit t\u00eb rikuperimit t\u00eb menj\u00ebhersh\u00ebm ishte zgjedhur t\u00eb ruhej ndryshimet n\u00eb disk. Nga:<\/i> server\u00ebt Veeam Backup & Replication (n\u00eb dallim nga snapshot-i i vSphere) \u2013 si rezultat, natyrisht, hap\u00ebsira e lir\u00eb n\u00eb disk u mbush shpejt. N\u00eb momentin q\u00eb p\u00ebrdoruesi k\u00ebrkoi ndihm\u00eb, VM kishte ndryshime q\u00eb nuk mund t\u00eb injoroheshin. Pra, kemi nj\u00eb situat\u00eb ku \u00ebsht\u00eb e pamundur t\u00eb finalizohet shpejt procesi i rikuperimit t\u00eb menj\u00ebhersh\u00ebm t\u00eb nj\u00eb makine kritike \u2013 si mund t\u00eb shp\u00ebtojm\u00eb t\u00eb dh\u00ebnat k\u00ebtu?\n

    T\u00eb pranoj, p\u00ebr shkak t\u00eb koh\u00ebs, nuk e mbaj mend \u00e7do detaj t\u00eb fundit, por e di se n\u00eb fund nuk shpik\u00ebm asgj\u00eb gjeniale. Klient\u00ebt nga ana e tyre pak a shum\u00eb e zgjidh\u00ebn k\u00ebt\u00eb problem, duke zgjeruar diskun C: nga rezervat, kopjuan dosjet m\u00eb t\u00eb r\u00ebnd\u00ebsishme dhe pastaj e shuan VM-n\u00eb dhe k\u00ebshtu e migruan. N\u00eb p\u00ebrgjith\u00ebsi, nuk ndodhi ndonj\u00eb mrekulli.<\/li>\n

  2. N\u00eb infrastruktur\u00ebn e p\u00ebrdoruesit punonte nj\u00eb kontrollues domeni, dhe t\u00eb gjitha komponent\u00ebt e Veeam Backup & Replication ishin konfiguruar duke p\u00ebrdorur DNS. Po, po, e d\u00ebgjuat drejt. Kishte nj\u00ebqind opsione p\u00ebr zhvillim, por realiteti shkoi k\u00ebshtu: njer\u00ebzit planifikuan nj\u00eb mb\u00ebshtetje dhe vendos\u00ebn t\u00eb kalonin n\u00eb replik\u00ebn e kontrolluesit t\u00eb domenit t\u00eb tyre. Ata aktivizuan kalimin e planifikuar, q\u00eb n\u00eb thelb rekomandohet t\u00eb b\u00ebhet n\u00eb situata t\u00eb tilla. N\u00eb faz\u00ebn e par\u00eb gjith\u00e7ka shkoi mir\u00eb, nd\u00ebrsa n\u00eb t\u00eb dyt\u00ebn, VM e origjin\u00ebs u fik p\u00ebr nj\u00eb koh\u00eb t\u00eb shkurt\u00ebr p\u00ebr t\u00eb transferuar mbetjet e t\u00eb dh\u00ebnave. Natyrisht, detyra e kalimit u p\u00ebrfundua menj\u00ebher\u00eb me nj\u00eb gabim, pasi DNS ndaloi s\u00eb funksionuari.\n

    Faleminderit, k\u00ebtu arrit\u00ebm t\u00eb menaxhojm\u00eb situat\u00ebn duke aktivizuar replik\u00ebn manualisht nga vSphere (nuk rekomandohet t\u00eb b\u00ebni k\u00ebt\u00eb operacion vet\u00eb, si\u00e7 do ta shihni nga shembulli n\u00eb vazhdim). 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 shtinim manualisht emrat e hostname-ve n\u00eb skedarin C:WindowsSystem32driversetchosts<\/i> n\u00eb serverin Veeam Backup & Replication, p\u00ebr t\u00eb siguruar sakt\u00ebsin\u00eb gjat\u00eb rikthimit.<\/li>\n

  3. Nj\u00eb tjet\u00ebr klient kishte nd\u00ebrtuar t\u00eb gjith\u00eb infrastruktur\u00ebn e kopjimit rreth pajisjeve t\u00eb band\u00ebs magnetike, nd\u00ebrsa n\u00eb disk ruheshin vet\u00ebm disa skedar\u00eb t\u00eb shkurt\u00ebr. Kur ata kishin nevoj\u00eb t\u00eb rikthenin nj\u00eb s\u00ebr\u00eb skedar\u00ebsh nga nj\u00eb server i madh skedar\u00ebsh, u zbulua se asnj\u00eb makin\u00eb nuk mund t\u00eb p\u00ebrdorej si depo ndihm\u00ebse gjat\u00eb rikthimit nga banda, pasi n\u00eb asnj\u00ebr\u00ebn nuk kishte mjaft hap\u00ebsir\u00eb t\u00eb lir\u00eb. (P\u00ebr rikthimin nga banda magnetike 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 tri rastet p\u00ebrdoruesit ishin, p\u00ebr ndonj\u00eb m\u00ebnyr\u00eb, t\u00eb kapur nga iluzionet \u2013 ata supozuan se n\u00ebse kopjimi kishte kaluar me sukses, do t\u00eb kishte gjithashtu probleme me rikuperimin. Por, si\u00e7 e dini, kjo nuk \u00ebsht\u00eb gjithmon\u00eb e v\u00ebrtet\u00eb, prandaj rikuperimi duhet p\u00ebrgatitur po aq me kujdes sa dhe kopjimi. N\u00eb fillim, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb studioni udh\u00ebzimin e p\u00ebrdoruesit<\/a><\/noindex>, ku p\u00ebrmban informacione mjaft t\u00eb detajuara n\u00eb lidhje me llojet e ndryshme t\u00eb rikuperimit. N\u00eb fillim t\u00eb \u00e7do paragrafi listohen k\u00ebrkesat, veprimet p\u00ebrgatitore dhe kufizimet e mundshme. P\u00ebrshkrimi i rikuperimit nga kasetat magnetike ose nga kopjet harduerike t\u00eb sistemit t\u00eb ruajtjes mund t\u00eb gjendet n\u00eb seksionet e dokumentacionit dhe n\u00eb tonat 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. \u00cbsht\u00eb koha p\u00ebr t\u00eb p\u00ebrfundoj\u00eb serin\u00eb me artikullin e tret\u00eb.<\/a><\/noindex> n\u00eb Habr\u00e9. P\u00ebr m\u00eb tep\u00ebr, veprimet p\u00ebrgatitore p\u00ebr rikuperimin e objekteve t\u00eb aplikacioneve duke p\u00ebrdorur mjetet Veeam Explorers jan\u00eb p\u00ebrshkruar n\u00eb seksionin \u00abPlanifikimi dhe p\u00ebrgatitja\u00bb udh\u00ebzimeve<\/a><\/noindex> p\u00ebr secil\u00ebn nga mjetet. Ju rekomandoj t\u00eb njiheni me to me kujdes \u2013 kjo do t'ju ndihmoj\u00eb t\u00eb p\u00ebrgatitni sistemin sakt\u00ebsisht p\u00ebr rikuperim n\u00eb rast nevoje. N\u00eb gjuh\u00ebn ruse, udh\u00ebzimet p\u00ebr rikuperimin e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave SQL Server jan\u00eb paraqitur k\u00ebtu<\/a><\/noindex>.<\/p>\n

    Pse nuk duhet t\u00eb punoni me replika nga konsola vSphere?<\/h1>\n

    \nTeoria thot\u00eb se replikat Veeam jan\u00eb thjesht makina virtuale, t\u00eb cilat, duket logjik\u00eb t\u00eb punoni me to duke p\u00ebrdorur mjetet e vSphere, ve\u00e7an\u00ebrisht klientin vSphere. Megjithat\u00eb, ne nuk rekomandojm\u00eb ta b\u00ebni k\u00ebt\u00eb, dhe ja pse: kalimi n\u00eb replik\u00eb n\u00eb Veeam Backup & Replication \u2013 \u00ebsht\u00eb nj\u00eb proces mjaft i nd\u00ebrlikuar, q\u00eb k\u00ebrkon nj\u00eb zbatim t\u00eb rrept\u00eb t\u00eb hapave (n\u00eb rast se gj\u00ebrat shkojn\u00eb keq, mund t\u00eb ktheheni pas n\u00eb hapin e m\u00ebparsh\u00ebm) dhe veprime p\u00ebrfundimtare t\u00eb sakta \u2013 shikoni vet\u00ebm imazhin q\u00eb ilustron procesin:<\/p>\n

    \"Veeam
    \n
    \nN\u00ebse vendosni t\u00eb aktivizoni replik\u00ebn nga klienti vSphere, me nj\u00eb probabilitet t\u00eb madh do t\u00eb hasni nj\u00eb s\u00ebr\u00eb problemesh n\u00eb t\u00eb ardhmen:<\/p>\n

      \n
    1. Mekanizmi i kalimit n\u00eb replik\u00eb nga Veeam Backup & replication (i treguar n\u00eb skem\u00eb) 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 reale t\u00eb VM. N\u00eb rastin m\u00eb t\u00eb keq, p\u00ebr ta riparuar do t\u00eb duhet t\u00eb redaktoni baz\u00ebn.<\/li>\n
    3. Mund t\u00eb ndodhi edhe humbja e t\u00eb dh\u00ebnave, si n\u00eb k\u00ebt\u00eb shembull: p\u00ebrdoruesi aktivizoi manualisht replik\u00ebn n\u00eb klientin vSphere dhe vendosi t\u00eb vazhdoj\u00eb pun\u00ebn me t\u00eb. Pasi kaloi pak koh\u00eb, ai vuri re se replika ende shfaqej n\u00eb konsol\u00ebn Veeam Backup & Replication dhe vendosi ta hiqte at\u00eb si t\u00eb panevojshme. Klikoi mbi t\u00eb me t\u00eb djatht\u00ebn dhe dha komand\u00ebn \u00abFshij nga disku\u00bb<\/i>. Veeam Backup & Replication e fshiu menj\u00ebher\u00eb replik\u00ebn nga disku, e cila, p\u00ebr t\u00eb th\u00ebn\u00eb t\u00eb v\u00ebrtet\u00ebn, po p\u00ebrdorej 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 duhet t\u00eb aktivizohet p\u00ebrs\u00ebri replika nga klienti vSphere \u2013 zakonisht n\u00eb rastet kur serveri Veeam \u00ebsht\u00eb fikur dhe replika duhet t\u00eb aktivizohet me vones\u00eb. Por n\u00ebse serveri Veeam \u00ebsht\u00eb n\u00eb rregull, at\u00ebher\u00eb duhet punuar me replikat pik\u00ebrisht nga konsola e tij.<\/p>\n

      Po ashtu, nuk duhet t\u00eb fshini replikat duke p\u00ebrdorur klientin vSphere. Veeam Backup & Replication do t\u00eb mbetet n\u00eb nj\u00eb situat\u00eb t\u00eb panjohur n\u00eb lidhje me k\u00ebt\u00eb ndryshim, gj\u00eb q\u00eb sjell gabime dhe t\u00eb dh\u00ebna t\u00eb vjetra. N\u00ebse replika nuk ju nevojitet m\u00eb, fshijeni at\u00eb p\u00ebrmes konsol\u00ebs Veeam dhe jo si VM nga klienti vSphere. K\u00ebshtu, do t\u00eb keni gjithmon\u00eb nj\u00eb list\u00eb t\u00eb sakt\u00eb t\u00eb replikave. <\/p>\n

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

      \nK\u00ebtu, natyrisht, kemi n\u00eb mendje azhurnimet p\u00ebr hipervizor\u00ebt dhe aplikacione t\u00eb ndryshme q\u00eb b\u00ebjn\u00eb kopje rezerv\u00eb me Veeam. N\u00ebse i shohim ato nga perspektiva e pun\u00ebs me Veeam Backup & Replication, azhurnimet mund t\u00eb ndahen n\u00eb dy kategori: ato t\u00eb m\u00ebdha, serioze, q\u00eb sjellin nj\u00eb s\u00ebr\u00eb ndryshimesh \u2013 dhe ato t\u00eb vogla.<\/p>\n

      Le t\u00eb shqyrtojm\u00eb fillimisht kategorin\u00eb e par\u00eb. <\/p>\n

      Azhurnimet m\u00eb t\u00eb r\u00ebnd\u00ebsishme jan\u00eb ato q\u00eb jan\u00eb t\u00eb destinuara p\u00ebr hipervizorin. Para se t\u00eb instalohet nj\u00eb azhurnim t\u00eb till\u00eb, \u00ebsht\u00eb domosdoshm\u00ebrisht q\u00eb t\u00eb sigurohemi se ai mb\u00ebshtetet nga Veeam Backup & Replication. Ato azhurnime sjellin shum\u00eb ndryshime n\u00eb bibliotekat dhe nd\u00ebrfaqet e API-ve q\u00eb p\u00ebrdor Veeam Backup & Replication, prandaj p\u00ebr t\u00eb deklaruar officialisht mb\u00ebshtetje p\u00ebr to, \u00ebsht\u00eb e nevojshme t\u00eb azhurnohet kodi i Veeam Backup & Replication dhe t\u00eb b\u00ebhet nj\u00eb testim i kujdessh\u00ebm. <\/p>\n

      Duhet gjithashtu t\u00eb merret parasysh se VMware, p\u00ebr shembull, nuk ofron qasje t\u00eb parakohshme n\u00eb versionet m\u00eb t\u00eb fundit t\u00eb vSphere p\u00ebr prodhuesit e softuerit, k\u00ebshtu q\u00eb zhvilluesit dhe testuesit e Veeam marrin versionin e ri n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb me gjith\u00eb njer\u00ebzimin progresiv \u2013 prandaj, zakonisht kalon nj\u00eb koh\u00eb e caktuar midis publikimit t\u00eb VMware dhe mb\u00ebshtetjes zyrtare t\u00eb shpallur. Sasia dhe diversiteti i ndryshimeve t\u00eb nevojshme jan\u00eb t\u00eb till\u00eb, saq\u00eb mund\u00ebsia p\u00ebr t'i p\u00ebrfshir\u00eb ato n\u00eb nj\u00eb hotfix \u00ebsht\u00eb e vog\u00ebl \u2013 dhe mb\u00ebshtetje zyrtare zakonisht shpallet me daljen e versionit publik t\u00eb Veeam Backup & Replication. <\/p>\n

      Si rezultat, ndodh ai moment i \u00e7uditsh\u00ebm, kur pas daljes s\u00eb nj\u00eb versioni t\u00eb ri t\u00eb vSphere numri i k\u00ebrkesave p\u00ebr mb\u00ebshtetje teknike rritet duksh\u00ebm, p\u00ebr shkak se p\u00ebrdoruesit nxitojn\u00eb t\u00eb instalojn\u00eb versionin e ri, dhe backup-et e tyre, sigurisht, ndalojn\u00eb menj\u00ebher\u00eb s\u00eb funksionuari. Ne \u2013 mb\u00ebshtetja teknike e Veeam \u2013 detyrohemi t\u00eb sqarojm\u00eb p\u00ebr p\u00ebrdoruesit se \u00e7far\u00eb sakt\u00ebsisht kan\u00eb b\u00ebr\u00eb gabim, t'i k\u00ebrkojm\u00eb t\u00eb kthehen prapa (n\u00ebse \u00ebsht\u00eb e mundur) ose t\u00eb shpikim rrug\u00eb t\u00eb komplikuara p\u00ebr t\u00eb dal\u00eb nga bllokimi. Prandaj, para se t\u00eb instaloni nj\u00eb p\u00ebrdit\u00ebsim t\u00eb r\u00ebnd\u00ebsish\u00ebm, sigurohuni t\u00eb kontrolloni p\u00ebrputhshm\u00ebrin\u00eb me software-n q\u00eb keni, ju lutem!<\/b><\/p>\n

      E gjith\u00eb e th\u00ebn\u00eb m\u00eb sip\u00ebr vlen edhe p\u00ebr aplikacionet q\u00eb b\u00ebni backup dhe planifikoni t\u00eb riktheni me ndihm\u00ebn e Veeam. Rreshti i mjeteve Veeam Explorers gjithashtu ka nj\u00eb list\u00eb versionsh t\u00eb mb\u00ebshtetur t\u00eb aplikacioneve p\u00ebrkat\u00ebse, e cila plot\u00ebsohet me \u00e7do version t\u00eb ri t\u00eb Veeam Backup & Replication. Prandaj, para se t\u00eb instaloni versionin e ri t\u00eb aplikacionit tuaj \u2013 qofshin ato Exchange, Oracle ose SharePoint \u2013 sigurohuni t\u00eb lexoni seksionin p\u00ebrkat\u00ebs t\u00eb dokumentacionit Veeam Explorers<\/a><\/noindex>.<\/p>\n

      N\u00eb kategorin\u00eb e dyt\u00eb, e cila p\u00ebrfshin p\u00ebrmir\u00ebsime t\u00eb vogla, rendit gjithashtu versione t\u00eb reja t\u00eb VMware Tools, p\u00ebrdit\u00ebsime kumulative t\u00eb Exchange, p\u00ebrdit\u00ebsime t\u00eb siguris\u00eb p\u00ebr vSphere, etj. Si rregull, ato nuk sjellin ndonj\u00eb modifikim t\u00eb r\u00ebnd\u00ebsish\u00ebm dhe n\u00eb shumic\u00ebn e rasteve Veeam Backup & Replication nuk has probleme me to. (Prandaj, p\u00ebr to nuk ka njoftime publike p\u00ebr mb\u00ebshtetje zyrtare n\u00eb produkt.) Megjithat\u00eb, n\u00eb praktik\u00ebn ton\u00eb kemi hasur raste kur edhe k\u00ebto p\u00ebrmir\u00ebsime ndryshonin aq shum\u00eb rendin e zakonsh\u00ebm t\u00eb gj\u00ebrave, sa q\u00eb \u00e7onin n\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 l\u00ebshojn\u00eb sa m\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 t\u00eb asaj q\u00eb inxhinier\u00ebt po punojn\u00eb 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 abonet e tij del nj\u00eb buletin 'Fjala nga Gostev' i autoreve TheRealGostev<\/a><\/noindex>. N\u00eb t\u00eb, Anton Gostev, drejtor i departamentit t\u00eb menaxhimit t\u00eb produkteve, tregon p\u00ebr problemet e zbuluara s\u00eb fundmi (jo vet\u00ebm n\u00eb an\u00ebn e Veeam), planet p\u00ebr versionet e reja dhe lajmet nga bota e IT-s\u00eb. N\u00ebse keni nevoj\u00eb p\u00ebr m\u00eb shum\u00eb informacion, mund t\u00eb shqyrtoni temat e forumit - n\u00ebse ndonj\u00eb klient p\u00ebrballet me nj\u00eb problem me funksionimin e produktit pas nj\u00eb azhurnimi, \u00ebsht\u00eb e sigurt se tashm\u00eb ka shkruar p\u00ebr k\u00ebt\u00eb n\u00eb forum.<\/p>\n

      Si\u00e7 e kuptoni, patch-et dhe azhurnimet mund t\u00eb sjellin 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 ju ndihmojn\u00eb laborator\u00ebt virtual\u00eb - Veeam DataLabs. Me siguri keni d\u00ebgjuar p\u00ebr funksionalitetin SureBackup, i cili \u00ebsht\u00eb i dedikuar p\u00ebr verifikimin e kopjeve rezerv\u00eb. Ai bazohet pik\u00ebrisht n\u00eb p\u00ebrdorimin e DataLabs, me krijimin e nj\u00eb mjedisi t\u00eb izoluar, n\u00eb t\u00eb cilin mund t\u00eb testoni azhurnimet para se t'i instaloni ato n\u00eb prodhim. E rekomandoj shum\u00eb ta b\u00ebni k\u00ebt\u00eb - do t'ju kursej\u00eb nj\u00eb num\u00ebr t\u00eb madh qelizash nervore. Dhe n\u00ebse dikush tjet\u00ebr nuk e di p\u00ebr SureBackup, e rekomandoj t\u00eb lexoni. dokumentacioni<\/a><\/noindex>.<\/p>\n

      Nd\u00ebrkaq, p\u00ebr sot kam mjaft, faleminderit p\u00ebr v\u00ebmendjen!<\/p>\n

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

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