{"id":97726,"date":"2020-10-21T08:42:15","date_gmt":"2020-10-21T06:42:15","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/veeam-log-diving-komponenty-i-glossarij"},"modified":"2020-10-21T08:42:15","modified_gmt":"2020-10-21T06:42:15","slug":"veeam-log-diving-komponenty-i-glossarij","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/veeam-log-diving-komponenty-i-glossarij","title":{"rendered":"Veeam Log Diving: komponentet dhe glosari","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Veeam
\n
\nNe jemi n\u00eb Veeam dhe i duam log\u00ebt. Dhe ndonj\u00ebher\u00eb, duke qen\u00eb se shumica e zgjidhjeve t\u00eb nostres jan\u00eb modulare, ato shkruajn\u00eb shum\u00eb log\u00eb. Duke qen\u00eb se fusha jon\u00eb e veprimit \u00ebsht\u00eb ruajtja e t\u00eb dh\u00ebnave tuaja (dmth. p\u00ebr t\u00eb garantuar nj\u00eb gjum\u00eb t\u00eb qet\u00eb), log\u00ebt duhet jo vet\u00ebm t\u00eb regjistrojn\u00eb \u00e7do ngjarje, por edhe ta b\u00ebjn\u00eb k\u00ebt\u00eb n\u00eb detaje. Kjo \u00ebsht\u00eb e nevojshme p\u00ebr t\u00eb qen\u00eb t\u00eb sigurt se n\u00eb rast ndonj\u00eb problemi, do t\u00eb kuptohet se \u00e7far\u00eb ndodhi, kush \u00ebsht\u00eb fajtor dhe \u00e7far\u00eb duhet t\u00eb b\u00ebjm\u00eb m\u00eb pas. K\u00ebtu si n\u00eb kriminalistik\u00eb: kurr\u00eb nuk e di se cila detaj mund t\u00eb ndihmoj\u00eb p\u00ebr t\u00eb zbuluar vras\u00ebsin e Laura Palmer.<\/p>\n

Prandaj, vendosa t\u00eb filloj nj\u00eb seri artikujsh ku do t\u00eb tregoj radhazi se \u00e7far\u00eb shkruajm\u00eb n\u00eb log\u00eb, ku i ruajm\u00eb ato, si t\u00eb mos dalim t\u00eb \u00e7mendur nga struktura e tyre dhe \u00e7far\u00eb duhet t\u00eb k\u00ebrkojm\u00eb brenda tyre.
\n<\/a><\/noindex><\/p>\n

Pse nj\u00eb seri artikujsh dhe pse jo ta p\u00ebrshkruajm\u00eb gjith\u00e7ka nj\u00ebher\u00ebsh? <\/h3>\n

\nThjesht t\u00eb renditosh se cili log ndodhet ku dhe \u00e7far\u00eb p\u00ebrmban ai \u2014 \u00ebsht\u00eb nj\u00eb ide e komplikuar. Dhe p\u00ebr t\u00eb mbajtur k\u00ebt\u00eb informacion t\u00eb azhurnuar, madje, \u00ebsht\u00eb nj\u00eb mendim q\u00eb tremb. Nj\u00eb renditje e t\u00eb gjith\u00eb llojeve t\u00eb mundshme t\u00eb log\u00ebve n\u00eb Veeam Backup & Replication \u2014 \u00ebsht\u00eb nj\u00eb tabel\u00eb q\u00eb z\u00eb disa faqe me shkronja t\u00eb vogla. Dhe ajo do t\u00eb jen\u00eb e vlefshme vet\u00ebm n\u00eb momentin e publikimit, pasi me daljen e patch-it t\u00eb ardhsh\u00ebm mund t\u00eb shfaqen log\u00eb t\u00eb rinj, logjika e t\u00eb dh\u00ebnave n\u00eb ato t\u00eb vjetra mund t\u00eb ndryshoj\u00eb, etj. Prandaj, do t\u00eb ishte shum\u00eb m\u00eb e dobishme t\u00eb shpjegoheshin struktura e tyre dhe thelbi i informacionit brenda tyre. Kjo do t\u00eb ndihmoj\u00eb n\u00eb orientimin m\u00eb t\u00eb mir\u00eb n\u00eb terren, sesa thjesht t\u00eb m\u00ebsosh nga memorizimi emrave.<\/p>\n

Prandaj, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mos hidhemi me kok\u00eb n\u00eb gremin\u00ebn e panum\u00ebrt t\u00eb teksteve, le t\u00eb b\u00ebjm\u00eb nj\u00eb pun\u00eb p\u00ebrgatitore n\u00eb k\u00ebt\u00eb artikull. Prandaj sot nuk do t\u00eb futemi n\u00eb log\u00ebt vet\u00eb, por do t'i afrohemi nga ana tjet\u00ebr: do t\u00eb krijojm\u00eb nj\u00eb glosar dhe pak do t\u00eb diskutojm\u00eb mbi struktur\u00ebn e Veeam nga k\u00ebndv\u00ebshtrimi i krijimit t\u00eb log\u00ebve.<\/p>\n

Glosari dhe gjuh\u00eb argotike<\/h3>\n

\nK\u00ebtu s\u00eb pari duhet t\u00eb k\u00ebrkoj falje para mbrojt\u00ebsve t\u00eb pastrimit t\u00eb gjuh\u00ebs ruse dhe d\u00ebshmitar\u00ebve t\u00eb fjalorit t\u00eb O\u0436\u0435\u0433\u043e\u0432. Ne t\u00eb gjith\u00eb e duam shum\u00eb gjuh\u00ebn ton\u00eb amtare, por industria e mallrave IT funksionon n\u00eb anglisht. Ne nuk e shpik\u00ebm k\u00ebt\u00eb, por k\u00ebshtu e solli historia. Nuk jam fajtore, ai vet\u00eb erdhi (c)<\/p>\n

N\u00eb fush\u00ebn ton\u00eb, problemi i anglicizmit (dhe gjargonit) ka specifik\u00ebn e tij. Kur fjal\u00eb t\u00eb dukshme si \"host\" ose \"guest\" kuptohet prej koh\u00ebsh n\u00eb m\u00ebnyr\u00eb t\u00eb ve\u00e7ant\u00eb n\u00eb \u00e7do pjes\u00eb t\u00eb bot\u00ebs, nj\u00eb gjendje heroike p\u00ebr\u00e7arjeje vazhdon n\u00eb \u2159 e tok\u00ebs me gishtin drejt fjalor\u00ebve. Dhe argumenti i domosdosh\u00ebm \"Por ne n\u00eb pun\u00eb...\".<\/p>\n

P\u00ebrve\u00e7 k\u00ebsaj, kemi terminologjin\u00eb ton\u00eb specifike q\u00eb i p\u00ebrket pik\u00ebrisht produkteve Veeam, edhe pse disa fjal\u00eb dhe fraza kan\u00eb dal\u00eb n\u00eb p\u00ebrdorim t\u00eb gjer\u00eb. Prandaj tani ne do t\u00eb biem dakord se \u00e7far\u00eb do t\u00eb thot\u00eb \u00e7do term, dhe n\u00eb vazhdim, kur them \"guest\", do t\u00eb kem parasysh pik\u00ebrisht at\u00eb q\u00eb \u00ebsht\u00eb shkruar n\u00eb k\u00ebt\u00eb kapitull, dhe jo at\u00eb q\u00eb ju jeni m\u00ebsuar n\u00eb pun\u00ebn tuaj. Dhe po, kjo nuk \u00ebsht\u00eb ndonj\u00eb \u00e7menduri personale e imja, jan\u00eb terma t\u00eb ngulitura n\u00eb industri. T\u00eb luftosh me to \u00ebsht\u00eb disi e kot\u00eb. Megjithat\u00eb, gjithmon\u00eb jam p\u00ebr t\u00eb diskutuar n\u00eb komentet.<\/p>\n

Fatkeq\u00ebsisht, terminologjia n\u00eb pun\u00ebn ton\u00eb dhe p\u00ebr produktet \u00ebsht\u00eb jasht\u00ebzakonisht e madhe, k\u00ebshtu q\u00eb nuk do t\u00eb p\u00ebrpiqem t\u00eb lista t\u00eb gjitha. Vet\u00ebm ato m\u00eb bazike dhe t\u00eb nevojshme p\u00ebr mbijetes\u00eb n\u00eb detin e informacionit mbi backupet dhe log-et. P\u00ebr ata q\u00eb jan\u00eb t\u00eb interesuar, mund t\u00eb propozoj nj\u00eb artikull <\/a><\/noindex>nga koleg\u00ebt q\u00eb p\u00ebrmendin llogarit\u00eb, ku ai gjithashtu ka dh\u00ebn\u00eb nj\u00eb list\u00eb terma q\u00eb lidhen me at\u00eb pjes\u00eb funksionaliteti.<\/p>\n

Host (Host):<\/strong> N\u00eb bot\u00ebn e virtualizimit, kjo \u00ebsht\u00eb makina me hipervizorin. Fizike, virtuale, cloud \u2014 nuk ka r\u00ebnd\u00ebsi. N\u00ebse mbi ndonj\u00eb gj\u00eb \u00ebsht\u00eb instaluar nj\u00eb hipervizor (ESXi, Hyper-V, KVM etj.), at\u00ebher\u00eb kjo \"di\u00e7ka\" quhet host. Qoft\u00eb nj\u00eb klas\u00eb me dhjet\u00eb raftesh apo laptopi juaj me nj\u00eb laboratori me nj\u00eb t\u00eb vet\u00ebm virtual \u2014 n\u00ebse keni aktivizuar hipervizorin, at\u00ebher\u00eb keni b\u00ebr\u00eb host. Sepse hipervizori hoston makina virtuale. Ka madje nj\u00eb legjend\u00eb q\u00eb VMware n\u00eb koh\u00ebn e saj donte t\u00eb arrinte nj\u00eb asociacion t\u00eb fort\u00eb t\u00eb fjal\u00ebs host me ESXi. Por nuk e arriti.<\/p>\n

N\u00eb bot\u00ebn moderne, koncepti i \"host\" praktikisht \u00ebsht\u00eb bashkuar me at\u00eb t\u00eb \"server\", q\u00eb sjell nj\u00eb konfuzion t\u00eb caktuar n\u00eb komunikim, sidomos n\u00ebse flasim p\u00ebr infrastruktur\u00ebn Windows. Pra, \u00e7do makin\u00eb q\u00eb ka ndonj\u00eb sh\u00ebrbim t\u00eb interesit ton\u00eb, mund t\u00eb quhet me siguri host. P\u00ebr shembull, n\u00eb log-et e WinSock, \u00e7do gj\u00eb etiketohet si host. Nj\u00eb shembull klasik \u00ebsht\u00eb \"Host not found\". Pra, le t\u00eb nisemi nga konteksti, por mos harroni \u2014 n\u00eb bot\u00ebn e virtualizimit, host \u00ebsht\u00eb ajo q\u00eb hoston mysafir\u00ebt (p\u00ebr k\u00ebt\u00eb flitet dy rreshta m\u00eb posht\u00eb).<\/p>\n

Nga argot\u00ebt lokal\u00eb (madje akronimet, n\u00eb k\u00ebt\u00eb rast) p\u00ebrmendim se VMware \u00ebsht\u00eb VI, vSphere \u00ebsht\u00eb VC, dhe Hyper-V \u00ebsht\u00eb HV.<\/p>\n

Guest (E Huaj):<\/strong> Nj\u00eb makin\u00eb virtuale q\u00eb punon n\u00eb host. K\u00ebtu madje nuk ka nevoj\u00eb p\u00ebr shpjegim, gjith\u00e7ka \u00ebsht\u00eb kaq logjike dhe e thjesht\u00eb. Megjithat\u00eb, shum\u00eb p\u00ebrpiqen t'i japin k\u00ebtu disa kuptime t\u00eb tjera. <\/p>\n

Pse? Nuk e di.
\nGuest OS, p\u00ebrkat\u00ebsisht, sistema operativ i makin\u00ebs s\u00eb huaj. Dhe k\u00ebshtu me radh\u00eb.<\/p>\n

Backup\/Replication Job (pun\u00eb e rezerv\u00ebs):<\/strong> Nj\u00eb argot i past\u00ebr i VMware, q\u00eb p\u00ebrfaq\u00ebson ndonj\u00eb nga detyrat. Backup job == Puna e Rezerv\u00ebs. Si t\u00eb p\u00ebrkthehet kjo bukur n\u00eb shqip \u2014 askush nuk e ka menduar, prandaj t\u00eb gjith\u00eb thon\u00eb 'pun\u00eb'. Me theksin n\u00eb sill\u00ebn e fundit.<\/p>\n

Po, k\u00ebshtu thjesht e marrin dhe thon\u00eb 'pun\u00eb'. Madje e shkruajn\u00eb edhe n\u00eb letra, dhe gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull.
\nLlojet e pun\u00ebve t\u00eb rezerv\u00ebs, detyrat e rezerv\u00ebs etj., faleminderit, por nuk nevojiten. Thjesht pun\u00eb, dhe do t'ju kuptojn\u00eb. E r\u00ebnd\u00ebsishme \u00ebsht\u00eb t\u00eb vendosni theksin n\u00eb sill\u00ebn e fundit.<\/p>\n

Backup (Rezerva, rezervim. P\u00ebr v\u00ebrtet\u00eb-pleqt\u00eb e v\u00ebrtet\u00eb lejohet edhe rezervim):<\/strong> P\u00ebrve\u00e7 asaj q\u00eb \u00ebsht\u00eb e qart\u00eb (nj\u00eb kopje rezerv\u00eb q\u00eb ndodhet diku), do t\u00eb thot\u00eb gjithashtu edhe vet\u00eb pun\u00ebn (tre rreshta m\u00eb lart, n\u00ebse e keni harruar), p\u00ebr shkak t\u00eb s\u00eb cil\u00ebs krijohet ai skedari rezerv\u00eb. Ka shum\u00eb mund\u00ebsi q\u00eb zot\u00ebrinjt\u00eb mbajt\u00ebs t\u00eb anglishtes jan\u00eb tep\u00ebr t\u00eb len\u00eb p\u00ebr t\u00eb th\u00ebn\u00eb gjithmon\u00eb 'I ran my backup job', prandaj thon\u00eb thjesht 'I ran my backup' dhe t\u00eb gjith\u00eb e kuptojn\u00eb nj\u00ebri-tjetrin. Propozoj t\u00eb mb\u00ebshtesim k\u00ebt\u00eb iniciativ\u00eb t\u00eb shk\u00eblqyer.<\/p>\n

Consolidate (Konsolidimi): <\/strong>Term q\u00eb u shfaq n\u00eb ESXi 5.0 Opsioni n\u00eb menun\u00eb e pun\u00ebs me snapshotet, q\u00eb nis procesin e fshirjes s\u00eb ashtuquajturve snapshot t\u00eb braktisur. Pra, snapshot q\u00eb jan\u00eb fizikisht aty, por kan\u00eb r\u00ebn\u00eb nga struktura logjike e dukshme. Teorikisht, ky proces nuk duhet t\u00eb preki skedar\u00ebt e shfaqur n\u00eb menaxherin e snapshot-eve, megjithat\u00eb ndodhin gj\u00ebra t\u00eb tjera. Q\u00ebllimi i procesit t\u00eb konsolidimit \u00ebsht\u00eb q\u00eb t\u00eb dh\u00ebnat nga snapshoti (disku f\u00ebmij\u00eb) shkruhen n\u00eb diskun kryesor (disku prind). Procesi i bashkimit t\u00eb diskeve quhet m\u00ebrg (merge). N\u00ebse \u00ebsht\u00eb dh\u00ebn\u00eb komanda p\u00ebr konsolidim, regjistrimi i snapshotit mund t\u00eb hiqet nga baza m\u00eb p\u00ebrpara se sa snapshoti t\u00eb m\u00ebrgohet dhe fshihet. Dhe n\u00ebse snapshoti nuk mund t\u00eb fshihet p\u00ebr ndonj\u00eb arsye, at\u00ebher\u00eb shfaqen k\u00ebta snapshot t\u00eb braktisur. P\u00ebr pun\u00ebn me snapshotet, VMware ka<\/a><\/noindex>nj\u00eb KB t\u00eb mir\u00eb. Dhe ne gjithashtu nj\u00eb her\u00eb kemi<\/a><\/noindex>.<\/p>\n

shkruar p\u00ebr to n\u00eb Habr\u00eb (Habr\u00e9). <\/strong>\u00a0Nj\u00eb koncept mjaft i gjer\u00eb, por n\u00eb bot\u00ebn e virtualizimit n\u00ebnkupton vendin ku ruhen skedar\u00ebt e makinave virtuale. Megjithat\u00eb, n\u00eb \u00e7do rast, duhet t\u00eb kuptoni shum\u00eb qart\u00eb kontekstin dhe, n\u00eb rast t\u00eb dyshimeve t\u00eb vogla, t\u00eb sqaroni se \u00e7far\u00eb pati n\u00eb mendje biseduesi juaj.\u00a0<\/p>\n

Proxy (Proksi): <\/strong>\u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptohet menj\u00ebher\u00eb se Veeam Proxy nuk \u00ebsht\u00eb aq e nj\u00ebjt\u00eb sa jemi m\u00ebsuar n\u00eb fush\u00ebn e internetit. Brenda produkteve t\u00eb Veeam, ky \u00ebsht\u00eb nj\u00eb entitet q\u00eb merret me transferimin e t\u00eb dh\u00ebnave nga nj\u00eb vend n\u00eb nj\u00eb tjet\u00ebr. Pa u menduar shum\u00eb n\u00eb detaje, VBR \u00ebsht\u00eb serveri komandues, nd\u00ebrsa proksi \u00ebsht\u00eb \u201ckali\u201d i tij i pun\u00ebs. Pra, proksi \u00ebsht\u00eb makina p\u00ebrmes s\u00eb cil\u00ebs rrjedh trafiku dhe mbi t\u00eb cil\u00ebn jan\u00eb instaluar komponent\u00ebt e VBR q\u00eb ndihmojn\u00eb n\u00eb menaxhimin e k\u00ebtij trafiku. P\u00ebr shembull, t\u00eb transferoni t\u00eb dh\u00ebna nga nj\u00eb kanal n\u00eb nj\u00eb tjet\u00ebr ose thjesht t\u00eb lidhni disqe (re\u017eimi HotAdd).<\/p>\n

Repository (Repozitari): <\/strong>\u00a0Teknikisht, kjo \u00ebsht\u00eb thjesht nj\u00eb regjistrim n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb VBR q\u00eb tregon vendin ku ruhen kopjet rezerv\u00eb dhe si t\u00eb lidhesh me k\u00ebt\u00eb vend. N\u00eb thelb, kjo mund t\u00eb jet\u00eb nj\u00eb ndarje simple CIFS, nj\u00eb disk i ve\u00e7ant\u00eb, nj\u00eb server apo nj\u00eb kov\u00eb n\u00eb re. S\u00ebrish, jemi brenda kontekstit, por kuptojm\u00eb se repo e shkurtuar \u00ebsht\u00eb thjesht vendi ku q\u00ebndrojn\u00eb kopjet rezerv\u00eb t\u00eb tua.<\/p>\n

\u00a0Snapshot (SnapshOt): <\/strong>Adhuruesit e gramatik\u00ebs s\u00eb Oksfordit preferojn\u00eb t\u00eb flasin p\u00ebr snapshot, disa si snEpshot, disa si sNpshot, megjithat\u00eb shumica e paarsimuar fiton p\u00ebrmes mas\u00ebs m\u00eb t\u00eb madhe. N\u00ebse dikush nuk e di - kjo \u00ebsht\u00eb teknologjia q\u00eb lejon rikthimin e gjendjes s\u00eb diskut n\u00eb nj\u00eb moment t\u00eb caktuar. Kjo b\u00ebhet ose p\u00ebrmes ridrejtimit t\u00eb p\u00ebrkohsh\u00ebm t\u00eb operacioneve I\/O nga disku kryesor - at\u00ebher\u00eb do t\u00eb quhet RoW (Redirect on Write) snapshot - ose duke e transferuar bllokun e shkruar nga disku juaj n\u00eb nj\u00eb tjet\u00ebr - kjo do t\u00eb quhet CoW (Copy on Write) snapshot. Fal\u00eb mund\u00ebsive t\u00eb gjera p\u00ebr aplikimin e k\u00ebtyre funksioneve, Veeam mund t\u00eb kryej\u00eb magjin\u00eb e saj t\u00eb backup-it. Sakt\u00ebsisht, jo vet\u00ebm me t\u00eb, por kjo \u00ebsht\u00eb puna e l\u00ebshimeve t\u00eb af\u00ebrta.<\/p>\n

N\u00eb dokumentacionin dhe logjet e ESXi, rreth k\u00ebtij termi ka kaos, dhe n\u00eb kontekstin e p\u00ebrmendjes s\u00eb snapshots, mund t\u00eb hasni si snapshotet, ashtu edhe redo log dhe madje edhe delta disk. N\u00eb dokumentacionin e Veeam nuk ka nj\u00eb p\u00ebr\u00e7arje t\u00eb till\u00eb, dhe snapshot \u00ebsht\u00eb nj\u00eb snapshot, nd\u00ebrsa redo log \u00ebsht\u00eb pik\u00ebrisht skedari REDO, i krijuar nga nj\u00eb disk jo-p\u00ebrhersh\u00ebm. Skedar\u00ebt REDO fshihen kur fikni makinat virtuale, k\u00ebshtu q\u00eb ngat\u00ebrresa e tyre me snapshotet \u00ebsht\u00eb nj\u00eb rrug\u00eb drejt d\u00ebshtimit.<\/p>\n

Sintetik (Synthetic):<\/strong> Backup-et sintetike i p\u00ebrkasin backup-eve reverse incremental dhe forever forward. N\u00ebse ndonj\u00ebher\u00eb nuk keni hasur k\u00ebt\u00eb term, at\u00ebher\u00eb ky \u00ebsht\u00eb thjesht nj\u00eb nga mekanizmat e p\u00ebrdorur p\u00ebr nd\u00ebrtimin e zinxhirit t\u00eb backup-it. Megjithat\u00eb, n\u00eb logje gjithashtu mund t\u00eb hasni konceptin Transform, i cili p\u00ebrdoret p\u00ebr krijimin e kopjeve t\u00eb plota nga incrementet (synthetic full).<\/p>\n

Detyra (Task):<\/strong> Ky \u00ebsht\u00eb procesi i p\u00ebrpunimit t\u00eb \u00e7do makine t\u00eb ve\u00e7ant\u00eb brenda nj\u00eb pun\u00eb. Pra, n\u00ebse keni nj\u00eb pun\u00eb backup q\u00eb p\u00ebrfshin tri makina. K\u00ebshtu, \u00e7do makin\u00eb do t\u00eb p\u00ebrpunohen n\u00eb kuad\u00ebr t\u00eb nj\u00eb detyre t\u00eb ve\u00e7ant\u00eb. Pra, do t\u00eb ket\u00eb kat\u00ebr logje: nj\u00eb kryesore p\u00ebr pun\u00ebn dhe tri p\u00ebr detyrat. Megjithat\u00eb, k\u00ebtu ka nj\u00eb nuanc\u00eb t\u00eb r\u00ebnd\u00ebsishme: me kalimin e koh\u00ebs, fjala \u201cdetyr\u00eb\u201d ka marr\u00eb shum\u00eb kuptime. Kur flasim p\u00ebr logjet e zakonshme, n\u00ebnkuptojm\u00eb se detyra \u00ebsht\u00eb pik\u00ebrisht VM. Por ka \u201cdetyrat\u201d e veta edhe n\u00eb proxy dhe n\u00eb depo. Aty mund t\u00eb n\u00ebnkuptoj\u00eb si nj\u00eb disk virtual, ashtu edhe nj\u00eb makin\u00eb virtuale, ose t\u00eb gjith\u00eb pun\u00ebn. Pra, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb mos humbni kontekstin.<\/p>\n

Sh\u00ebrbimi Veeam %name% (Service)<\/strong>: \u00a0<\/strong>P\u00ebr mir\u00ebqenien e backup-eve t\u00eb suksesshme punojn\u00eb menj\u00ebher\u00eb disa sh\u00ebrbime, lista e t\u00eb cilave mund t\u00eb gjendet n\u00eb vegl\u00ebn standarde. Emrat e tyre mjaft hapur pasqyrojn\u00eb thelbin e tyre, megjithat\u00eb mes t\u00eb barabart\u00ebve ka nj\u00eb m\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm - Sh\u00ebrbimi i Backup-it Veeam, pa t\u00eb cilin t\u00eb tjerat nuk do t\u00eb funksiononin.<\/p>\n

VSS: <\/strong>Teknikisht, VSS gjithmon\u00eb duhet t\u00eb n\u00ebnkuptoj\u00eb Sh\u00ebrbimin p\u00ebr Kopjimin e Hijes s\u00eb Volumit t\u00eb Microsoft. N\u00eb fakt, p\u00ebrdoret nga shum\u00eb si sinonim p\u00ebr Procesimin e Imazheve t\u00eb Nd\u00ebrgjegjsh\u00ebm p\u00ebr Aplikacionin. \u00c7ka, sigurisht, \u00ebsht\u00eb kategorikisht e gabuar, megjithat\u00eb kjo \u00ebsht\u00eb nj\u00eb histori nga ajo lloj q\u00eb thot\u00eb \"\u00c7do SUV mund t\u00eb quhet Jeep, dhe do t\u00eb kuptohet\".<\/p>\n

Logjet fantastike dhe vendet ku ato banojn\u00eb<\/h3>\n

\nDua t\u00eb filloj k\u00ebt\u00eb kapitull me zb\u00ebrthimin e nj\u00eb misteri t\u00eb madh - cilin koh\u00eb shfaqet n\u00eb logje?<\/p>\n

Mbani mend:<\/p>\n