{"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: komponent\u00ebt dhe glosari","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Veeam
\n
\nNe n\u00eb Veeam i duam log\u00ebt. Dhe pasi shumica e zgjidhjeve tona jan\u00eb modulare, ato shkruajn\u00eb mjaft log\u00eb. Dhe duke qen\u00eb se fusha jon\u00eb e veprimit \u00ebsht\u00eb sigurimi i ruajtjes s\u00eb t\u00eb dh\u00ebnave tuaja (dmth nj\u00eb gjum\u00eb t\u00eb qet\u00eb), log\u00ebt duhet t\u00eb regjistrojn\u00eb jo vet\u00ebm \u00e7do l\u00ebvizje, por ta b\u00ebjn\u00eb k\u00ebt\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb detajuar. Kjo \u00ebsht\u00eb e nevojshme n\u00eb m\u00ebnyr\u00eb q\u00eb, n\u00eb rastin e ndonj\u00eb incidenti, t\u00eb kuptohet si ndodhi ky incident, kush ishte p\u00ebrgjegj\u00ebs dhe \u00e7far\u00eb duhet t\u00eb b\u00ebjm\u00eb m\u00eb pas. K\u00ebtu \u00ebsht\u00eb si n\u00eb kriminalistik\u00eb: kurr\u00eb nuk e di se cila detaj do t\u00eb t\u00eb ndihmoj\u00eb t\u00eb gjesh vras\u00ebsin e Lora Palmer.<\/p>\n

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

Pse seria e artikujve dhe pse jo ta p\u00ebrshkruajm\u00eb gjith\u00e7ka nj\u00ebher\u00eb? <\/h3>\n

\nThjesht t\u00eb p\u00ebrmend\u00ebsh se ku ndodhen log\u00ebt dhe \u00e7far\u00eb p\u00ebrmbajn\u00eb ato \u00ebsht\u00eb nj\u00eb p\u00ebrpjekje mjaft e v\u00ebshtir\u00eb. Dhe mbajtja e k\u00ebtij informacioni t\u00eb fresk\u00ebt \u00ebsht\u00eb e frikshme. Nj\u00eb thjesht listim i t\u00eb gjitha llojeve t\u00eb mundshme t\u00eb log\u00ebve n\u00eb Veeam Backup & Replication \u00ebsht\u00eb nj\u00eb tabel\u00eb q\u00eb merr disa faqe me shkronja t\u00eb vogla. Dhe do t\u00eb jet\u00eb e vlefshme vet\u00ebm n\u00eb momentin e publikimit, pasi me l\u00ebshimin e patch-it t\u00eb ardhsh\u00ebm mund t\u00eb shfaqen log\u00eb t\u00eb reja, logjika e informacionit t\u00eb ruajtur n\u00eb t\u00eb vjetrit mund t\u00eb ndryshoj\u00eb, etj. Prandaj, shum\u00eb m\u00eb e dobishme do t\u00eb jet\u00eb t\u00eb shpjegojm\u00eb struktur\u00ebn e tyre dhe thelbin e informacionit q\u00eb p\u00ebrmbajn\u00eb. Kjo do t\u00eb lejoj\u00eb q\u00eb t\u00eb orientohemi m\u00eb mir\u00eb n\u00eb terren sesa thjesht t\u00eb memorizojm\u00eb emrat.<\/p>\n

Prandaj, p\u00ebr t\u00eb mos u hedhur me kok\u00eb n\u00eb detin e flet\u00ebve t\u00eb gjata tekstuale, le t\u00eb b\u00ebjm\u00eb nj\u00eb pun\u00eb p\u00ebrgatitore n\u00eb k\u00ebt\u00eb artikull. Prandaj, sot nuk do t\u00eb hyjm\u00eb n\u00eb vet\u00eb log\u00ebt, por do t\u00eb dalim nga larg: do t\u00eb hartojm\u00eb nj\u00eb glosar dhe do t\u00eb flasim pak p\u00ebr struktur\u00ebn e Veeam nga k\u00ebndv\u00ebshtrimi i gjenerimit t\u00eb log\u00ebve.<\/p>\n

Glosari dhe termat e argot\u00ebs<\/h3>\n

\nDerihet s\u00eb pari t\u00eb k\u00ebrkoj ndjes\u00eb para mbrojt\u00ebsve t\u00eb past\u00ebrtis\u00eb s\u00eb gjuh\u00ebs shqipe dhe d\u00ebshmitar\u00ebve t\u00eb fjalorit t\u00eb Ozhegov-it. T\u00eb gjith\u00eb ne e duam shum\u00eb gjuh\u00ebn ton\u00eb t\u00eb lindur, por industria e IT-s\u00eb punon n\u00eb anglisht. Ajo nuk \u00ebsht\u00eb idea jon\u00eb, por k\u00ebshtu ka ndodhur historikisht. Nuk \u00ebsht\u00eb faji im, ai vet\u00eb erdhi (c)<\/p>\n

N\u00eb fush\u00ebn ton\u00eb, problemi i anglicizmave (dhe xhargoneve) ka specifik\u00ebn e vet. Kur nga fjal\u00eb t\u00eb pafajshme si \"host\" ose \"guest\" e gjith\u00eb bota kupton gj\u00ebra konkretisht t\u00eb caktuara, n\u00eb \u2159 e tok\u00ebs vazhdon nj\u00eb p\u00ebrplasje heroike dhe l\u00ebvizshm\u00ebria me gisht n\u00eb fjalor\u00eb. Edhe argumenti i detyruesh\u00ebm \"Por tek ne n\u00eb pun\u00eb...\".<\/p>\n

P\u00ebrjashtova terminologjin\u00eb ton\u00eb, e cila \u00ebsht\u00eb specifike p\u00ebr produktet Veeam, edhe pse disa fjal\u00eb dhe shprehje jan\u00eb b\u00ebr\u00eb t\u00eb njohura. Prandaj tani do t\u00eb biem dakord se \u00e7far\u00eb do t\u00eb thot\u00eb \u00e7do term, dhe n\u00eb t\u00eb ardhmen n\u00ebn fjal\u00ebn \"mysafir\" do t\u00eb kem parasysh at\u00eb q\u00eb \u00ebsht\u00eb shkruar n\u00eb k\u00ebt\u00eb kapitull, e jo at\u00eb q\u00eb jeni m\u00ebsuar n\u00eb pun\u00ebn tuaj. Dhe po, kjo nuk \u00ebsht\u00eb vet\u00ebm d\u00ebshira ime, jan\u00eb terma t\u00eb vendosur n\u00eb industri. T\u00eb luftosh me to \u00ebsht\u00eb paksa e pamundur. Megjithat\u00eb, n\u00ebse d\u00ebshiron t\u00eb komentosh, un\u00eb gjithmon\u00eb jam p\u00ebr.<\/p>\n

Fatkeq, numri i terminologjive n\u00eb pun\u00ebn ton\u00eb dhe produkte \u00ebsht\u00eb jasht\u00ebzakonisht i madh, k\u00ebshtu q\u00eb nuk do t\u00eb p\u00ebrpiqem t'i listoj t\u00eb gjitha. Vet\u00ebm ato m\u00eb themelore dhe t\u00eb nevojshme p\u00ebr t\u00eb mbijetuar n\u00eb k\u00ebt\u00eb det informacioni n\u00eb lidhje me backup dhe log. P\u00ebr ata q\u00eb jan\u00eb t\u00eb interesuar, mund t\u00eb ofroj nj\u00eb artikull <\/a><\/noindex>nga koleg\u00ebt mbi rrjetet, ku ai gjithashtu kishte p\u00ebrfshir\u00eb nj\u00eb list\u00eb terminologjish q\u00eb lidhen me at\u00eb pjes\u00eb t\u00eb funksionalitetit.<\/p>\n

Host (Host):<\/strong> N\u00eb bot\u00ebn e virtualizimit, kjo \u00ebsht\u00eb nj\u00eb makin\u00eb me hipervizor. Fizike, virtuale, n\u00eb re \u2014 nuk ka r\u00ebnd\u00ebsi. N\u00ebse mbi di\u00e7ka \u00ebsht\u00eb instaluar nj\u00eb hipervizor (ESXi, Hyper-V, KVM etj.), at\u00ebher\u00eb ky \"di\u00e7ka\" quhet host. Qoft\u00eb nj\u00eb klaster me dhjet\u00eb racks ose laptopi juaj me nj\u00eb laborator p\u00ebr nj\u00ebzet\u00eb virtual\u00eb \u2014 n\u00ebse keni nisur hipervizorin, at\u00ebher\u00eb jeni b\u00ebr\u00eb host. Sepse hipervizori hoston makinat virtuale. Ka madje nj\u00eb histori, q\u00eb VMware n\u00eb nj\u00eb koh\u00eb do t\u00eb p\u00ebrpiqej t\u00eb arrinte nj\u00eb lidhje t\u00eb fort\u00eb t\u00eb fjal\u00ebs host pik\u00ebrisht me ESXi. Por nuk ia doli.<\/p>\n

N\u00eb bot\u00ebn moderne, koncepti i \"host\" \u00ebsht\u00eb praktikisht bashkuar me at\u00eb t\u00eb \"server\", \u00e7ka sjell disa keqkuptime n\u00eb komunikim, sidomos kur b\u00ebhet fjal\u00eb p\u00ebr infrastruktur\u00ebn Windows. Prandaj, \u00e7do makin\u00eb q\u00eb p\u00ebrmban ndonj\u00eb sh\u00ebrbim interesant p\u00ebr ne mund t\u00eb quhet pa m\u00ebdyshje nj\u00eb host. P\u00ebr shembull, n\u00eb logjet e WinSock, fjala host sh\u00ebnon gjith\u00e7ka. Nj\u00eb shembull klasik \u00ebsht\u00eb \"Host not found\". Pra, t\u00eb gjith\u00ebve duhet t\u00eb mbajm\u00eb parasysh kontekstin, por t\u00eb kujtojm\u00eb \u2013 n\u00eb bot\u00ebn e virtualizimit, host \u00ebsht\u00eb ajo q\u00eb hoston mysafir\u00ebt (p\u00ebr k\u00ebt\u00eb do flasim n\u00eb rreshta dy m\u00eb posht\u00eb).<\/p>\n

Nga gjargonet lokale (m\u00eb shum\u00eb se akronime, n\u00eb k\u00ebt\u00eb rast) na vjen nd\u00ebrmend se VMware \u00ebsht\u00eb VI, vSphere \u00ebsht\u00eb VC, dhe Hyper-V \u00ebsht\u00eb HV.<\/p>\n

Guest (Mysafir):<\/strong> Nj\u00eb makin\u00eb virtuale e cila punon n\u00eb host. K\u00ebtu nuk ka asgj\u00eb p\u00ebr t\u00eb shpjeguar, aq logjike dhe e thjesht\u00eb \u00ebsht\u00eb. Sidoqoft\u00eb, shum\u00eb p\u00ebrpiqen t'i japin k\u00ebtu kuptime t\u00eb tjera. <\/p>\n

P\u00ebrse? Nuk e di.
\nGuest OS, p\u00ebrkat\u00ebsisht, \u00ebsht\u00eb sistemi operativ i makin\u00ebs mysafire. Dhe k\u00ebshtu me radh\u00eb.<\/p>\n

Backup\/Replication Job (djobA):<\/strong> Nj\u00eb gjargon krejt\u00ebsisht VMware, q\u00eb p\u00ebrfaq\u00ebson nj\u00eb nga detyrat. Backup job == DjobA e Bekaupit. Si e p\u00ebrkthejm\u00eb k\u00ebt\u00eb n\u00eb shqip \u2014 askush nuk ka arritur ta gjej\u00eb nj\u00eb shprehje t\u00eb bukur, k\u00ebshtu q\u00eb t\u00eb gjith\u00eb thon\u00eb \"djobA\", me theksin n\u00eb sillin e fundit.<\/p>\n

Po, k\u00ebshtu thjesht e marrin dhe thon\u00eb \"job\". Edhe n\u00eb letra k\u00ebshtu shkruajn\u00eb, dhe gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull.
\n\u00c7do lloj punimesh p\u00ebr backup, detyrat e backup-it etj., faleminderit, por nuk \u00ebsht\u00eb nevojshme. Thjesht job, dhe do t'ju kuptojn\u00eb. E r\u00ebnd\u00ebsishmja \u00ebsht\u00eb t\u00eb vendosni theksin n\u00eb sillin e fundit.<\/p>\n

Backup (B\u00ebkap, b\u00ebkap. P\u00ebr t\u00eb v\u00ebrtet\u00ebt e vjet\u00ebr, lejohet bakUp):<\/strong> P\u00ebrve\u00e7 asaj q\u00eb \u00ebsht\u00eb e dukshme (nj\u00eb kopje rezerv\u00eb e dh\u00ebnave diku), do t\u00eb thot\u00eb gjithashtu vet\u00eb job-in (tre rreshta lart, n\u00ebse e keni harruar), si rezultat i s\u00eb cil\u00ebs krijohet ai skedari b\u00ebkap. Me sa duket, zot\u00ebrinj anglishtfol\u00ebs jan\u00eb shum\u00eb t\u00eb len\u00eb p\u00ebr t\u00eb th\u00ebn\u00eb gjithmon\u00eb I ran my backup job, prandaj ata thjesht thon\u00eb I ran my backup, dhe t\u00eb gjith\u00eb kuptojn\u00eb nj\u00ebri-tjetrin shum\u00eb mir\u00eb. Propozoj t\u00eb mb\u00ebshtesim k\u00ebt\u00eb iniciativ\u00eb t\u00eb mrekullueshme.<\/p>\n

Consolidate (Konsolidim): <\/strong>Termi q\u00eb u shfaq n\u00eb ESXi 5.0 Opsioni n\u00eb menun\u00eb e pun\u00ebs me snapshot-et, q\u00eb aktivizon procesin e fshirjes t\u00eb ashtuquajturave snapshot-e orphaned. Pra, snapshot-e t\u00eb cilat fizikisht ekzistojn\u00eb, por kan\u00eb r\u00ebn\u00eb nga struktura logjike e paraqitur. Teorikisht, ky proces nuk duhet t\u00eb preki skedar\u00ebt e paraqitur n\u00eb menaxherin e snapshot-eve, megjithat\u00eb ndodhin edhe raste. Thelbi i procesit t\u00eb konsolidimit \u00ebsht\u00eb q\u00eb t\u00eb dh\u00ebnat nga snapshot-i (disku f\u00ebmij\u00eb) shkruhen n\u00eb diskun kryesor (disku prind). Procesi i bashkimit t\u00eb disqeve quhet m\u00ebrgimi (merge). N\u00ebse \u00ebsht\u00eb dh\u00ebn\u00eb urdhri p\u00ebr konsolidim, at\u00ebher\u00eb informacioni mbi snapshot-in mund t\u00eb fshihet nga baza m\u00eb her\u00ebt sesa snapshot-i t\u00eb m\u00ebrgohet dhe t\u00eb fshihet. Dhe n\u00ebse snapshot-i nuk mund t\u00eb fshihet p\u00ebr ndonj\u00eb arsye, at\u00ebher\u00eb shfaqen k\u00ebto snapshot-e orphaned. P\u00ebr pun\u00ebn me snapshot-et, VMware ka nj\u00eb KB t\u00eb k\u00ebndsh\u00ebm<\/a><\/noindex>. Dhe ne gjithashtu nj\u00eb her\u00eb kemi shkruar p\u00ebr ta n\u00eb Habr\u00eb<\/a><\/noindex>.<\/p>\n

Datastore (Shtes\u00eb ose magazin\u00eb): <\/strong>\u00a0Nj\u00eb koncept shum\u00eb i gjer\u00eb, por n\u00eb bot\u00ebn e virtualizimit n\u00ebnkupton vendin ku ruhen skedar\u00ebt e makinave virtuale. Megjithat\u00eb, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptohet qart\u00eb konteksti dhe n\u00eb rast t\u00eb dyshimeve t\u00eb vogla t\u00eb sqaroni se \u00e7far\u00eb ka dashur t\u00eb thot\u00eb biseduesi juaj.\u00a0<\/p>\n

Proxy (P\u00ebrfaq\u00ebsues): <\/strong>\u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptohet se Veeam Proxy nuk \u00ebsht\u00eb krejt\u00ebsisht e nj\u00ebjt\u00eb me at\u00eb q\u00eb jemi m\u00ebsuar n\u00eb bot\u00ebn e internetit. Brenda produkteve t\u00eb Veeam, kjo \u00ebsht\u00eb nj\u00eb entitet q\u00eb merret me transferimin e t\u00eb dh\u00ebnave nga nj\u00eb vend n\u00eb tjetrin. N\u00ebse nuk hyjm\u00eb n\u00eb detaje, at\u00ebher\u00eb VBR \u00ebsht\u00eb serveri komandon, nd\u00ebrsa proksi \u00ebsht\u00eb puna e tij. Pra, proksi \u00ebsht\u00eb makina p\u00ebrmes s\u00eb cil\u00ebs kalon trafiku dhe p\u00ebr t\u00eb cil\u00ebn jan\u00eb instaluar komponent\u00ebt e VBR, t\u00eb cil\u00ebt ndihmojn\u00eb n\u00eb menaxhimin e k\u00ebtij trafiku. P\u00ebr shembull, transmetimi i t\u00eb dh\u00ebnave nga nj\u00eb kanal n\u00eb tjetrin ose thjesht lidhja e disqeve (HotAdd mode).<\/p>\n

Repository (Repo): <\/strong>\u00a0N\u00eb m\u00ebnyr\u00eb teknike, kjo \u00ebsht\u00eb thjesht nj\u00eb rekord n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VBR q\u00eb tregon vendin ku ruhen kopjet rezerva dhe si t\u00eb lidhemi me k\u00ebt\u00eb vend. N\u00eb fakt, kjo mund t\u00eb jet\u00eb nj\u00eb CIFS share e thjesht\u00eb, nj\u00eb disk i ve\u00e7ant\u00eb, nj\u00eb server ose nj\u00eb bucket n\u00eb re. S\u00ebrish, jemi n\u00eb kontekst, por e kuptojm\u00eb q\u00eb repo \u00ebsht\u00eb thjesht vendi ku jan\u00eb kopjet e rezerva.<\/p>\n

\u00a0Snapshot (Snapshot): <\/strong>Ata q\u00eb preferojn\u00eb gramatik\u00ebn oksfordiane diskutojn\u00eb se si \u00ebsht\u00eb 'snapshot' ose 'snepshot', por shumica analfabet\u00ebve fiton p\u00ebrmes numrit m\u00eb t\u00eb madh. N\u00ebse dikush nuk e di \u2014 kjo \u00ebsht\u00eb nj\u00eb teknologji q\u00eb lejon rikthimin e gjendjes s\u00eb diskut n\u00eb nj\u00eb moment t\u00eb caktuar. Kjo arrihet ose p\u00ebrmes rinisjes s\u00eb operacioneve I\/O drejt nj\u00eb disku tjet\u00ebr \u2014 at\u00ebher\u00eb quhet RoW (Redirect on Write) snapshot \u2014 ose p\u00ebrmes largimit t\u00eb blloqeve t\u00eb rip\u00ebrs\u00ebritura nga disku juaj n\u00eb nj\u00eb tjet\u00ebr \u2014 e cila do t\u00eb quhej CoW (Copy on Write) snapshot. Fal\u00eb mund\u00ebsive t\u00eb gjera t\u00eb p\u00ebrdorimit t\u00eb k\u00ebtyre funksioneve, Veeam mund t\u00eb krijoj\u00eb magjin\u00eb e saj t\u00eb backup-it. N\u00eb t\u00eb v\u00ebrtet\u00eb, jo vet\u00ebm ata, por kjo \u00ebsht\u00eb \u00e7\u00ebshtje e l\u00ebshimeve t\u00eb af\u00ebrta.<\/p>\n

N\u00eb dokumentacionin dhe logjet e ESXi, p\u00ebrreth k\u00ebtij termi ka kaos, dhe n\u00eb kontekstin e p\u00ebrmendjes s\u00eb snapshot-eve mund t\u00eb hasni si snapshot-et, ashtu edhe redo log dhe madje edhe delta disk. N\u00eb dokumentacionin e Veeam nuk ka nj\u00eb kaos t\u00eb till\u00eb, dhe snapshot-i \u00ebsht\u00eb nj\u00eb snapshot, nd\u00ebrsa redo log \u00ebsht\u00eb pik\u00ebrisht skedari REDO, i krijuar nga nj\u00eb disk jo-p\u00ebrs\u00ebrit\u00ebs. Skedar\u00ebt REDO fshihen kur makina virtuale mbyllet, k\u00ebshtu q\u00eb t\u00eb ngat\u00ebrroni ata me snapshot-et \u00ebsht\u00eb nj\u00eb rrug\u00eb p\u00ebr d\u00ebshtim.<\/p>\n

Sintetike (Synthetic):<\/strong> Blegjet sintetike i p\u00ebrkasin bbackup-eve t\u00eb rikthimit incremental dhe p\u00ebrjetsh\u00ebm p\u00ebrpara. N\u00ebse ndonj\u00ebher\u00eb nuk jeni p\u00ebrballur me k\u00ebt\u00eb term, ai \u00ebsht\u00eb thjesht nj\u00eb nga mekanizmat e p\u00ebrdorur p\u00ebr nd\u00ebrtimin e shnd\u00ebrrimeve t\u00eb zinxhirit t\u00eb backup-it. Megjithat\u00eb, n\u00eb log-e gjithashtu mund t\u00eb hasni termin Transform, i cili p\u00ebrdoret n\u00eb kuad\u00ebr t\u00eb krijimit t\u00eb kopjeve t\u00eb plota nga inkrementet (synthtetic full).<\/p>\n

Task (Detyra):<\/strong> Ky \u00ebsht\u00eb procesi i p\u00ebrpunimit t\u00eb \u00e7do makine t\u00eb ve\u00e7ant\u00eb brenda nj\u00eb pune. Pra: n\u00ebse keni nj\u00eb pun\u00eb backup-u, e cila p\u00ebrfshin tri makina. K\u00ebshtu, secila makin\u00eb do t\u00eb p\u00ebrpunoj\u00eb n\u00eb kuad\u00ebr t\u00eb nj\u00eb detyre t\u00eb ve\u00e7ant\u00eb. Pra, do t\u00eb ket\u00eb kat\u00ebr log-e: nj\u00eb kryesor p\u00ebr pun\u00ebn dhe tre p\u00ebr detyrat. Megjithat\u00eb, ka nj\u00eb nuanc\u00eb t\u00eb r\u00ebnd\u00ebsishme: me kalimin e koh\u00ebs fjala \"detyr\u00eb\" \u00ebsht\u00eb b\u00ebr\u00eb tep\u00ebr shum\u00ebznjoh\u00ebse. Kur flasim p\u00ebr log-et e p\u00ebrgjithshme, n\u00ebnkuptojm\u00eb se detyra \u00ebsht\u00eb pik\u00ebrisht VM. Por ka \"detyra\" edhe n\u00eb proxy dhe n\u00eb depo. Aty, kjo mund t\u00eb n\u00ebnkuptoj nj\u00eb disk virtual, nj\u00eb makin\u00eb virtuale, ose t\u00eb gjith\u00eb pun\u00ebn. Pra, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb mos humbasim kontekstin.<\/p>\n

Sh\u00ebrbimi Veeam %name% (Sh\u00ebrbimi)<\/strong>: \u00a0<\/strong>P\u00ebr t\u00eb siguruar backup t\u00eb suksessh\u00ebm punojn\u00eb disa sh\u00ebrbime, lista e t\u00eb cil\u00ebve mund t\u00eb gjendet n\u00eb vegl\u00ebn standarde. Emrat e tyre zakonisht reflektuin qartazi thelbin e tyre, megjithat\u00eb midis t\u00eb barabart\u00ebve ka nj\u00eb m\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm \u2013 Veeam Backup Service, pa t\u00eb cilin t\u00eb tjer\u00ebt nuk do t\u00eb funksiononin.<\/p>\n

VSS: <\/strong>Teknikisht VSS gjithmon\u00eb duhet t\u00eb p\u00ebrfaq\u00ebsoj\u00eb Microsoft Volume Shadow Copy Service. N\u00eb fakt, p\u00ebrdoret nga shum\u00eb si sinonim p\u00ebr Application-Aware Image Processing. \u00c7far\u00eb, sigurisht, \u00ebsht\u00eb kategorikisht e gabuar, megjithat\u00eb kjo \u00ebsht\u00eb nj\u00eb histori nga ai grup i th\u00ebnieve \u2018\u00c7do SUV mund t\u00eb quhet Jeep, dhe do t\u00eb t\u00eb kupton\u00eb\u2019.<\/p>\n

T\u00eb jasht\u00ebzakonshmet log dhe vendet ku ata ndodhen<\/h3>\n

\nDua t\u00eb filloj k\u00ebt\u00eb kapitull duke zbuluar nj\u00eb sekret t\u00eb madh \u2013 \u00e7far\u00eb koha shfaqet n\u00eb log?<\/p>\n

Merrni parasysh:<\/p>\n