{"id":84809,"date":"2020-06-11T01:42:41","date_gmt":"2020-06-10T23:42:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10"},"modified":"2020-06-11T01:42:41","modified_gmt":"2020-06-10T23:42:41","slug":"chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10","title":{"rendered":"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Capacity Tier (ose si\u00e7 e quajm\u00eb ne brenda Veeam \u2014 kaptir) u shfaq q\u00eb n\u00eb koh\u00ebt e Veeam Backup and Replication 9.5 Update 4 me emrin Archive Tier. Ideja e vendosur n\u00eb t\u00eb \u00ebsht\u00eb t\u00eb ofroj\u00eb mund\u00ebsin\u00eb p\u00ebr t\u00eb l\u00ebvizur kopjet rezerv\u00eb, q\u00eb kan\u00eb kaluar nga finesa e njohur si operacioni i rikuperimit, n\u00eb depo objektive. Kjo ndihmonte n\u00eb pastrimin e hap\u00ebsir\u00ebs s\u00eb diskut p\u00ebr ata p\u00ebrdorues q\u00eb kishin pak hap\u00ebsir\u00eb. Kjo opsion quhej Move Mode.<\/p>\n<p>P\u00ebr t\u00eb realizuar k\u00ebt\u00eb veprim t\u00eb thjesht\u00eb (si\u00e7 duket), ishte e nevojshme t\u00eb p\u00ebrmbusheshin dy kushte: t\u00eb gjitha pikat nga kopja rezerv\u00eb e l\u00ebvizshme duhet t\u00eb ishin jasht\u00eb kufijve t\u00eb em\u00ebruar m\u00eb par\u00eb t\u00eb operacionit t\u00eb rikuperimit, i cili p\u00ebrcaktohet qart\u00eb n\u00eb UI. Dhe e dyta: zinxhiri duhet t\u00eb jet\u00eb n\u00eb at\u00eb q\u00eb quhet \u00abzinxhir i vulosur\u00bb (sealed backup chain ose Inactive Backup Chain). Kjo do t\u00eb thot\u00eb q\u00eb me kalimin e koh\u00ebs n\u00eb k\u00ebt\u00eb zinxhir nuk ndodhin ndryshime.<\/p>\n<p>Por n\u00eb VBR v10 koncepti u pasurua me funksione t\u00eb reja \u2014 u shfaq Copy Mode, Sealed Mode dhe nj\u00eb gj\u00eb me emrin e v\u00ebshtir\u00eb Immutability.<\/p>\n<p>M\u00eb k\u00ebto gj\u00ebra emocionuese do t\u00eb flasim sot. Fillimisht p\u00ebr at\u00eb se si funksiononte n\u00eb VBR9.5u4, pastaj p\u00ebr ndryshimet n\u00eb versionin e dhjet\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/954adcc5592fe2a7ea64ec24b06ecc91.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDhe m\u00eb falni mbrojt\u00ebs t\u00eb gjuh\u00ebs s\u00eb past\u00ebr, por ka shum\u00eb terma q\u00eb nuk \u00ebsht\u00eb e mundur t'i p\u00ebrkthesh.<br \/>\nK\u00ebshtu q\u00eb k\u00ebtu do t\u00eb ket\u00eb shum\u00eb anglicizma.<br \/>\nDhe shum\u00eb gif-e. <br \/>\nDhe imazhe.<\/p>\n<ul>\n<li>Pa asnj\u00eb keqardhje. Autori i artikullit.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>Si\u00e7 ishte<\/h1>\n<p>\nPra, le t\u00eb fillojm\u00eb duke analizuar dritaren e rikthimit operacional dhe kopjen e vulosur (ose si quhen n\u00eb dokumentacionin e Inactive Backup Chain). Pa kuptimin e tyre, nuk do t\u00eb mund ta shpjegojm\u00eb m\u00eb tej.<\/p>\n<p>Si\u00e7 e shohim n\u00eb imazh, kemi nj\u00eb zinxhir backup me blloqe t\u00eb dh\u00ebnash, i cili \u00ebsht\u00eb vendosur n\u00eb nivelin Performance t\u00eb repositorit SOBR, t\u00eb cilit i \u00ebsht\u00eb lidhur Capacity Tier. Dritarja jon\u00eb operacionale e backup-it \u00ebsht\u00eb e barabart\u00eb me tre dit\u00eb.<\/p>\n<p>P\u00ebrkat\u00ebsisht, \u03b4\u03b7\u03bc\u03b9\u03bf\u03c5\u03c1\u03b3\u03b7\u03b8\u03ad\u03bd n\u00eb t\u00eb h\u00ebn\u00eb .vbk vulos zinxhirin e m\u00ebparsh\u00ebm, dritarja e t\u00eb cilit \u00ebsht\u00eb vendosur n\u00eb tre dit\u00eb. Dhe, pra, mund t\u00eb fillojm\u00eb qet\u00ebsisht t\u00eb d\u00ebrgojm\u00eb n\u00eb kapacitet tier gjith\u00e7ka q\u00eb \u00ebsht\u00eb m\u00eb e vjet\u00ebr se k\u00ebto tri dit\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/430f31d181bb79c2bd6001011511e3f9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPor \u00e7far\u00eb n\u00ebnkuptohej me zinxhirin e vulosur dhe \u00e7far\u00eb mund t\u00eb d\u00ebrgohej n\u00eb kapacitet tier n\u00eb p\u00ebrdit\u00ebsimin 4?<\/p>\n<p>P\u00ebr Forward Incremental, shenja e vulosjes s\u00eb zinxhirit \u00ebsht\u00eb krijimi i nj\u00eb backup-i t\u00eb ri t\u00eb plot\u00eb. Nuk ka r\u00ebnd\u00ebsi se si arrin t\u00eb krijohet ky backup i plot\u00eb: p\u00ebrfshihen edhe backup-et sintetike t\u00eb plot\u00eb, ashtu si dhe backup-et aktive t\u00eb plota.<\/p>\n<p>N\u00eb rastin e Reverse, k\u00ebto jan\u00eb t\u00eb gjitha skedar\u00ebt q\u00eb nuk bien n\u00ebn dritaren operacionale. <\/p>\n<p>N\u00eb rastin e Forward increment me rollbeke, k\u00ebto jan\u00eb t\u00eb gjitha rollbeket dhe .vbk, n\u00ebse n\u00eb perfoemansin e extentit ka edhe nj\u00eb tjet\u00ebr .vbk.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/4cb6f168862acabadbdab771cc48fe7f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTani le t\u00eb shqyrtojm\u00eb variantin e pun\u00ebs me zinxhir\u00ebt e Kopjimit t\u00eb Backup-it. K\u00ebtu merret parasysh vet\u00ebm ajo q\u00eb p\u00ebrputhet me ruajtjen GFS. Sepse gjith\u00e7ka q\u00eb ndodhet n\u00eb zinxhir\u00ebt m\u00eb t\u00eb rinj t\u00eb kopjimit t\u00eb backup-it mund t\u00eb jet\u00eb n\u00eb nj\u00eb m\u00ebnyr\u00eb ose n\u00eb nj\u00eb tjet\u00ebr e modifikuar.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/4c263058110b7c502501f01940977f1a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTani le t\u00eb hedhim nj\u00eb v\u00ebshtrim n\u00ebn kapak. Aty ndodhet nj\u00eb proces i quajtur dehidrim \u2013 l\u00ebnia e skedar\u00ebve t\u00eb zbraz\u00ebt backup n\u00eb extent dhe zhvendosja e blloqeve nga k\u00ebta skedar\u00eb n\u00eb kapacitetin tir. P\u00ebr optimizimin e k\u00ebtij procesi p\u00ebrdoret nj\u00eb indeks i quajtur dehidrim, i cili lejon t\u00eb mos kopjohen blloqet q\u00eb tashm\u00eb jan\u00eb kopjuar n\u00eb kapacitetin tir. <\/p>\n<p>Le t\u00eb shohim se si duket n\u00eb nj\u00eb rast konkret: le t\u00eb supozojm\u00eb se kemi nj\u00eb .vbk, e cila ka dal\u00eb nga dritarja operative dhe i p\u00ebrket nj\u00eb zinxhiri t\u00eb mbyllur. Kjo do t\u00eb thot\u00eb q\u00eb ne kemi t\u00eb drejt\u00eb t\u00eb transferojm\u00eb at\u00eb n\u00eb kapacitetin e rezonanc\u00ebs. N\u00eb momentin e transferimit krijohet nj\u00eb skedar metadata n\u00eb kapacitetin e rezonanc\u00ebs dhe blloqet e skedarit q\u00eb po transferohet. N\u00eb skedarin e metadata n\u00eb nivel referencash p\u00ebrshkruhet se nga cilat blloqe p\u00ebrb\u00ebhet skedari yn\u00eb. N\u00eb rastin e ilustruar, skedari yn\u00eb i par\u00eb p\u00ebrb\u00ebhet nga blloqet a, b, c dhe n\u00eb metadata jan\u00eb vendosur lidhjet p\u00ebr k\u00ebto blloqe. Kur kemi nj\u00eb skedar t\u00eb dyt\u00eb .vbk, t\u00eb gatsh\u00ebm p\u00ebr transferim dhe q\u00eb p\u00ebrb\u00ebhet nga blloqet a, b, dhe d, ne, duke analizuar indeksin e dehidratimit, kuptojm\u00eb se duhet t\u00eb transferojm\u00eb vet\u00ebm bllokun d. Skedari i tij i metadata do t\u00eb p\u00ebrmbaj\u00eb lidhje p\u00ebr dy blloqet e m\u00ebparshme dhe nj\u00eb t\u00eb re.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/5c502030b8727ecd85c5229df1761c85.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00eb p\u00ebrputhje, procesi i mbushjes s\u00eb k\u00ebtyre vendeve t\u00eb zbraz\u00ebta me t\u00eb dh\u00ebna quhet rigjidhje. K\u00ebtu p\u00ebrdoret indeksi i tij i rigjidhjes, i bazuar n\u00eb skedarin m\u00eb t\u00eb vjet\u00ebr .vbk n\u00eb performanc\u00ebn lokale. Pra, n\u00ebse p\u00ebrdoruesi d\u00ebshiron t\u00eb rikthej\u00eb nj\u00eb skedar nga kapaciteti i tij, ne s\u00eb pari krijojm\u00eb indeksin e bllok\u00ebve t\u00eb backup-it m\u00eb t\u00eb vjet\u00ebr t\u00eb plot\u00eb dhe transferojm\u00eb nga kapaciteti i tij vet\u00ebm bllok\u00ebt e munguar. N\u00eb rastin e paraqitur n\u00eb imazh, p\u00ebr t\u00eb rigjidhur FullBackup1.vbk n\u00eb p\u00ebrputhje me indeksin e rigjidhjes, na mungon vet\u00ebm blloku C, t\u00eb cilin e marrim nga kapaciteti i tij. N\u00ebse kapaciteti i tij \u00ebsht\u00eb nj\u00eb objekt ruajtjeje n\u00eb re, kjo lejon kursimin e shpenzimeve kolosale.<\/p>\n<p>K\u00ebtu mund t\u00eb duket se kjo teknologji \u00ebsht\u00eb identike me at\u00eb q\u00eb p\u00ebrdoret n\u00eb WAN Accelerators, por kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb iluzion. N\u00eb akselerator\u00eb, deduplikimi \u00ebsht\u00eb global, nd\u00ebrsa k\u00ebtu p\u00ebrdoret lokal brenda \u00e7do skedari n\u00eb nj\u00eb offset t\u00eb caktuar. Kjo ndodh p\u00ebr shkak t\u00eb ndryshimeve n\u00eb detyrat q\u00eb zgjidhen: k\u00ebtu na nevojitet t\u00eb kopjojm\u00eb skedar\u00eb t\u00eb m\u00ebdhenj t\u00eb backup-eve t\u00eb plota, dhe sipas hulumtimeve tona, edhe n\u00ebse kalon nj\u00eb periudh\u00eb e madhe kohe midis tyre, nj\u00eb algorit\u00ebm i till\u00eb deduplikimi jep rezultat m\u00eb t\u00eb mir\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/1db1a696e289187ae02bd84d9edd6f66.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPor m\u00eb shum\u00eb indekse p\u00ebr Zotit t\u00eb indekseve! Ka edhe nj\u00eb indeks p\u00ebr rikuperimin e t\u00eb dh\u00ebnave! Kur nisim rikuperimin e nj\u00eb makine, e cila ndodhet n\u00eb kapacitetin e zgjerimit, ne do t\u00eb lexojm\u00eb vet\u00ebm blloqet unike t\u00eb t\u00eb dh\u00ebnave, t\u00eb cilat nuk gjenden n\u00eb performanc\u00ebn e zgjerimit.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/257593c39e63bfb6f7e13d228bcebbae.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h1>Si\u00e7 u b\u00eb<\/h1>\n<p>\nKjo ishte e gjitha p\u00ebr pjes\u00ebn hyr\u00ebse. Ajo \u00ebsht\u00eb mjaft p\u00ebrshkruese, por, si\u00e7 u tha m\u00eb lart, pa k\u00ebto detaje nuk \u00ebsht\u00eb e mundur t\u00eb shpjegohet si funksionojn\u00eb funksionet e reja. Prandaj, pa m\u00eb shum\u00eb hyrje, kalojm\u00eb n\u00eb t\u00eb par\u00ebn.<\/p>\n<h3>Re\u017eimi i kopjimit<\/h3>\n<p>\nShum\u00eb prej saj \u00ebsht\u00eb e bazuar n\u00eb teknologjit\u00eb ekzistuese, megjithat\u00eb sjell logjik\u00eb krejt\u00ebsisht tjet\u00ebr p\u00ebrdorimi.\u00a0<\/p>\n<p>Q\u00ebllimi i k\u00ebtij modeli \u00ebsht\u00eb t\u00eb siguroj\u00eb q\u00eb t\u00eb gjitha t\u00eb dh\u00ebnat q\u00eb ndodhen n\u00eb ekstentin lokal t\u00eb ken\u00eb nj\u00eb kopje n\u00eb kapacitetin e tij.<\/p>\n<p>N\u00ebse e krahasojm\u00eb drejtp\u00ebrdrejt modet Move dhe Copy, do t\u00eb dal\u00eb k\u00ebshtu:<\/p>\n<ul>\n<li>Mund t\u00eb l\u00ebvizni vet\u00ebm nj\u00eb zinxhir t\u00eb vulosur. N\u00eb rastin e modit kopje, merrni gjith\u00e7ka, pavar\u00ebsisht se \u00e7far\u00eb ndodh n\u00eb pun\u00ebn e kopjimit.<\/li>\n<li>L\u00ebvizja aktivizohet kur skedar\u00ebt dalin jasht\u00eb kufijve t\u00eb dritares s\u00eb operacionit t\u00eb kopjimit, nd\u00ebrsa kopjimi aktivizohet menj\u00ebher\u00eb, sapo t\u00eb krijohet nj\u00eb skedar kopje.<\/li>\n<li>P\u00ebr t\u00eb ndjekur t\u00eb dh\u00ebnat e reja p\u00ebr kopjim, operacioni ndodh vazhdimisht, nd\u00ebrsa p\u00ebr l\u00ebvizje ndodhte \u00e7do 4 or\u00eb.<\/li>\n<\/ul>\n<p>\nN\u00eb shqyrtimin e modit t\u00eb ri, sugjeroj t\u00eb fillojm\u00eb me shembuj t\u00eb thjesht\u00eb dhe t\u00eb kalojm\u00eb n\u00eb ata m\u00eb t\u00eb nd\u00ebrlikuar.<\/p>\n<p>N\u00eb rastin m\u00eb t\u00eb thjesht\u00eb kemi thjesht skedar\u00eb t\u00eb rinj me inkrementime q\u00eb na shfaqen, dhe ne thjesht i kopjojm\u00eb ato n\u00eb kapacitetin e tij. Pavar\u00ebsisht nga moda q\u00eb p\u00ebrdoret n\u00eb pun\u00ebn e kopjimit, pavar\u00ebsisht se i p\u00ebrket pjes\u00ebs s\u00eb vulosur t\u00eb zinxhirit apo jo, pavar\u00ebsisht se ka kaluar apo jo dritarja jon\u00eb operative. Thjesht e mor\u00ebm dhe e kopjuam.<\/p>\n<p>Procesi q\u00eb q\u00ebndron pas k\u00ebsaj \u00ebsht\u00eb ende dehidratimi n\u00eb form\u00ebn si\u00e7 \u00ebsht\u00eb p\u00ebrshkruar m\u00eb lart. N\u00eb m\u00ebnyr\u00ebn e kopjimit, ai gjithashtu siguron q\u00eb t\u00eb mos kopjojm\u00eb blloqe q\u00eb tashm\u00eb jan\u00eb n\u00eb depot tona. Dallimi i vet\u00ebm \u00ebsht\u00eb se n\u00eb m\u00ebnyr\u00ebn e l\u00ebvizjes ne z\u00ebvend\u00ebsojm\u00eb skedar\u00ebt real\u00eb me skedar\u00eb t\u00eb zbraz\u00ebt, nd\u00ebrsa k\u00ebtu ne nuk i prekim aspak dhe i l\u00ebm\u00eb gjith\u00e7ka ashtu si \u00ebsht\u00eb. N\u00eb t\u00eb tjerat, kjo \u00ebsht\u00eb nj\u00eb indeks i till\u00eb i dehidratimit, i cili p\u00ebrpiqet me kujdes t\u00eb kursej\u00eb parat\u00eb dhe koh\u00ebn tuaj.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/b3a033f4a0d0cbce8cecee152660c67c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nLindi nj\u00eb pyetje \u2014 n\u00ebse e shikojm\u00eb UI-n\u00eb, ka mund\u00ebsi t\u00eb zgjidhni t\u00eb dy opsionet nj\u00ebkoh\u00ebsisht. Si do t\u00eb funksionoj\u00eb nj\u00eb mod i till\u00eb i kombinuar?<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/12f658765a05e120dc5068920886edb5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nLe t\u00eb hedhim nj\u00eb v\u00ebshtrim.<\/p>\n<p>Fillimi \u00ebsht\u00eb standard: krijohet nj\u00eb skedar backup dhe menj\u00ebher\u00eb kopjohet. I krijohet nj\u00eb increment dhe gjithashtu kopjohet. K\u00ebshtu ndodh deri n\u00eb momentin kur kuptojm\u00eb se skedar\u00ebt kan\u00eb dal\u00eb nga dritarja jon\u00eb operative dhe \u00ebsht\u00eb shfaqur nj\u00eb zinxhir i vulosur. N\u00eb k\u00ebt\u00eb moment kryejm\u00eb operacionin e dehidratimit dhe z\u00ebvend\u00ebsojm\u00eb k\u00ebta skedar\u00eb me skedar\u00eb t\u00eb zbraz\u00ebt. Natyrisht, nuk kopjojm\u00eb asgj\u00eb p\u00ebrs\u00ebri n\u00eb kapacitetin e tij.<\/p>\n<p>E gjith\u00eb kjo logjik\u00eb interesante \u00ebsht\u00eb p\u00ebrgjegj\u00ebsi e nj\u00eb vet\u00ebm checkbox-i n\u00eb nd\u00ebrfaqe: Copy backups to object storage as soon as they are created.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/1a0e27c04428ebd48b13d8927a453d62.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Pse na duhet ky mod Copy? <\/h3>\n<p>\n\u00cbsht\u00eb m\u00eb mir\u00eb ta formuloni pyetjen k\u00ebshtu \u2014 nga cilat rreziqe na mbron ai? Cilin problem na ndihmon ta zgjidhim?<\/p>\n<p>P\u00ebrgjigjja \u00ebsht\u00eb e qart\u00eb: sigurisht, \u00ebsht\u00eb rikuperimi i t\u00eb dh\u00ebnave. N\u00ebse ne kemi nj\u00eb kopje t\u00eb plot\u00eb t\u00eb t\u00eb dh\u00ebnave lokale n\u00eb objektin e ruajtjes, at\u00ebher\u00eb nuk ka r\u00ebnd\u00ebsi \u00e7far\u00eb ndodh me prodhimin ton\u00eb, gjithmon\u00eb mund t\u00eb rikuperojm\u00eb t\u00eb dh\u00ebnat nga skedar\u00ebt e vendosur n\u00eb nj\u00eb Amazon t\u00eb kushtuesh\u00ebm.<\/p>\n<p>Prandaj, le t\u00eb kalojm\u00eb n\u00ebp\u00ebr skenar\u00ebt e mundsh\u00ebm, nga m\u00eb i thjeshti deri tek m\u00eb kompleks.<\/p>\n<p>D\u00ebmi m\u00eb i thjesht\u00eb q\u00eb mund t\u00eb na ndodhi \u00ebsht\u00eb mungesa e nj\u00ebrit prej skedar\u00ebve n\u00eb zinxhirin e kopjeve rezerv\u00eb.<\/p>\n<p>Nj\u00eb histori m\u00eb e trishtuar \u00ebsht\u00eb kur na ka d\u00ebshtuar nj\u00eb nga ekstensat e reservoirit ton\u00eb SOBR.<\/p>\n<p>Gjendja \u00ebsht\u00eb edhe m\u00eb keq kur i gjith\u00eb reservoiri SOBR b\u00ebhet i paakseshem, por kapaciteti funksionon.<br \/>\nDhe gjith\u00e7ka \u00ebsht\u00eb shum\u00eb keq \u2014 \u00ebsht\u00eb kur serveri i kopjeve rezerv\u00eb vdes dhe d\u00ebshira jote e par\u00eb \u00ebsht\u00eb t\u00eb provosh t\u00eb arrish deri n\u00eb kufirin kanadez brenda dhjet\u00eb minutave.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/868d71412901ed362956e1e2157ed895.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTani le t\u00eb analizojm\u00eb \u00e7do situat\u00eb ve\u00e7 e ve\u00e7.<\/p>\n<p>Kur humb\u00ebm nj\u00eb (po, le t\u00eb ndodhin disa) skedar\u00eb rezerv\u00eb, do t\u00eb mjaftonte t\u00eb fillonim procesin e ridiskovrimit t\u00eb repositorit, dhe skedari i humbur do t\u00eb z\u00ebvend\u00ebsohej me nj\u00eb skedar bosh. Me procesin e rigjenerat\u00ebs (p\u00ebr t\u00eb cilin u fol n\u00eb fillim t\u00eb artikullit), p\u00ebrdoruesi mund t\u00eb shkarkoj\u00eb t\u00eb dh\u00ebnat nga kapaciteti n\u00eb ruajtjen lokale.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/5066a21cbd17565569891f8e23cac4fd.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTani situata \u00ebsht\u00eb pak m\u00eb e komplikuar. Supozoni se SOBR yn\u00eb p\u00ebrb\u00ebhet nga dy ekstensione q\u00eb punojn\u00eb n\u00eb modin Performance, do t\u00eb thot\u00eb se .vbk dhe .vib tona jan\u00eb shp\u00ebrndar\u00eb mbi to me nj\u00eb shtres\u00eb mjaft t\u00eb pabarabart\u00eb. Dhe n\u00eb nj\u00eb moment, nj\u00eb nga ekstensat b\u00ebhet i paaccessible, dhe p\u00ebrdoruesi duhet t\u00eb rikuperoj\u00eb menj\u00ebher\u00eb makin\u00ebn, pjesa e t\u00eb dh\u00ebnave t\u00eb s\u00eb cil\u00ebs ndodhet pik\u00ebrisht n\u00eb k\u00ebt\u00eb ekstent. <\/p>\n<p>P\u00ebrdoruesi fillon wizard-in e rikuperimit, zgjedh pik\u00ebn n\u00eb t\u00eb cil\u00ebn d\u00ebshiron t\u00eb rikuperoj\u00eb, dhe wizard-i gjat\u00eb pun\u00ebs arrin n\u00eb p\u00ebrfundimin se t\u00eb gjitha t\u00eb dh\u00ebnat e nevojshme p\u00ebr rikuperim nuk jan\u00eb lokal dhe prandaj duhet t'i shkarkoj\u00eb nga kapaciteti. Nd\u00ebrkoh\u00eb, blloqet q\u00eb kan\u00eb mbetur n\u00eb ruajtjen lokale nuk do t\u00eb shkarkohen nga reja. Fal\u00eb indeksit t\u00eb rikuperimit (po, edhe p\u00ebr t\u00eb \u00ebsht\u00eb folur n\u00eb fillim t\u00eb artikullit).<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/88b38ddf122d20a3e41a0afcba544749.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNj\u00eb n\u00ebnkategori e k\u00ebtij rasti \u00ebsht\u00eb se t\u00eb gjith\u00eb depozitat e SOBR jan\u00eb b\u00ebr\u00eb t\u00eb paarritshme. N\u00eb k\u00ebt\u00eb rast nuk kemi asgj\u00eb p\u00ebr t\u00eb kopjuar nga magazinat lokale, dhe t\u00eb gjitha blloqet shkarkohen nga reja.<\/p>\n<p>Dhe situata m\u00eb interesante \u00ebsht\u00eb se serveri i backup-it ka vdekur. Ka dy mund\u00ebsi: admini \u00ebsht\u00eb shum\u00eb i mir\u00eb dhe ka b\u00ebr\u00eb backup konfiguracioni, ose admini \u00ebsht\u00eb nj\u00eb Burotino i paditur dhe nuk ka b\u00ebr\u00eb backup-in e konfiguracionit.<\/p>\n<p>N\u00eb rastin e par\u00eb, \u00ebsht\u00eb mjaft t\u00eb vendos\u00eb nj\u00eb instalim t\u00eb past\u00ebr t\u00eb VBR diku dhe t\u00eb rivendos\u00eb baz\u00ebn e tij nga backup-i me mjetet e zakonshme. N\u00eb p\u00ebrfundim t\u00eb k\u00ebtij procesi, gjith\u00e7ka do t\u00eb kthehet n\u00eb gjendjen e saj t\u00eb zakonshme. Ose do t\u00eb rikthehet sipas nj\u00eb prej skenar\u00ebve t\u00eb sip\u00ebrp\u00ebrmendur.<\/p>\n<p>Por m\u00eb te qart\u00eb, n\u00ebse administratori \u00ebsht\u00eb armiku i vet, ose n\u00ebse rezervimi i konfiguracionit ka p\u00ebsuar nj\u00eb d\u00ebshtim legjendar, ne nuk do ta l\u00ebm\u00eb at\u00eb n\u00eb fatin e tij. P\u00ebr k\u00ebt\u00eb rast, kemi futur nj\u00eb procedur\u00eb t\u00eb re, t\u00eb quajtur Import Object Storage. Kjo lejon q\u00eb t\u00eb kaloni procesin manual t\u00eb rikrijimit t\u00eb depot SOBR dhe ngjitjes s\u00eb kapacitetit t\u00eb tij me skanimin e m\u00ebpassh\u00ebm, dhe thjesht t\u00eb shtoni objektin e ruajtjes n\u00eb nd\u00ebrfaqen e sistemit dhe t\u00eb filloni procedur\u00ebn e Import Storage Repository. Gj\u00ebja e vetme q\u00eb mund t\u00eb jet\u00eb n\u00eb mes jush dhe rezervimeve tuaja \u00ebsht\u00eb nj\u00eb k\u00ebrkes\u00eb p\u00ebr t\u00eb futur fjal\u00ebkalimin, n\u00ebse rezervimet tuaja jan\u00eb koduar.<\/p>\n<p>K\u00ebtu p\u00ebr Copy Mode, me siguri, \u00ebsht\u00eb e gjitha dhe ne kalojm\u00eb n\u00eb<\/p>\n<h3>Sealed Mode<\/h3>\n<p>\nIdeja kryesore \u00ebsht\u00eb q\u00eb n\u00eb ekstensin e zgjedhur t\u00eb depozit\u00ebs SOBR nuk mund t\u00eb shfaqen rezervime t\u00eb reja. Deri n\u00eb v10, ne kishim vet\u00ebm Maintenance Mode, kur ishin t\u00eb ndaluara \u00e7do aktivitet me depozit\u00ebn. Nj\u00eb m\u00ebnyr\u00eb e ashp\u00ebr p\u00ebr t\u00eb nxjerr\u00eb ruajtjen nga puna, ku ka vet\u00ebm butonin Evacuate, i cili t\u00eb transportonte rezervimet nj\u00eb her\u00eb n\u00eb nj\u00eb ekstens tjet\u00ebr.<\/p>\n<p>Nj\u00eb modalitet i vulosur \u00ebsht\u00eb nj\u00eb version \"m\u00eb t\u00eb but\u00eb\": ne ndalojm\u00eb krijimin e kopjeve rezerv\u00eb t\u00eb reja dhe gradualisht fshijm\u00eb ato t\u00eb vjetra sipas retention q\u00eb \u00ebsht\u00eb zgjedhur, por n\u00eb proces nuk e humbasim mund\u00ebsin\u00eb p\u00ebr tu rikuperuar nga pikat e ruajtura. Nj\u00eb gj\u00eb shum\u00eb e dobishme kur na skadon afati i jet\u00ebs s\u00eb pajisjes dhe duhet ta z\u00ebvend\u00ebsojm\u00eb, ose thjesht duhet ta lirojm\u00eb p\u00ebr di\u00e7ka m\u00eb t\u00eb r\u00ebnd\u00ebsishme, kur s'kemi ku t'i kalojm\u00eb t\u00eb gjitha nj\u00ebher\u00ebsh. Ose s'ka mund\u00ebsi t\u00eb fshijm\u00eb. <\/p>\n<p>P\u00ebrkat\u00ebsisht, parimi i funksionimit \u00ebsht\u00eb mjaft i thjesht\u00eb: duhet t\u00eb ndaloni t\u00eb gjitha operacionet write (shfaqjen e t\u00eb dh\u00ebnave t\u00eb reja), duke l\u00ebn\u00eb read (restor\u00ebt) dhe delete (retention).<\/p>\n<p>T\u00eb dy modalitetet mund t\u00eb p\u00ebrdoren nj\u00ebkoh\u00ebsisht, por duhet t\u00eb kemi parasysh se Maintenance ka p\u00ebrpar\u00ebsi m\u00eb t\u00eb lart\u00eb.<\/p>\n<p>Si nj\u00eb shembull, le t\u00eb shqyrtojm\u00eb SOBR, q\u00eb p\u00ebrb\u00ebhet nga dy ekstenta. Le t\u00eb supozojm\u00eb se kat\u00ebr dit\u00ebt e para krijoheshin kopje rezerv\u00eb n\u00eb modalitetin Forward Forever Incremental, dhe m\u00eb pas ne vulosim ekstentin. Kjo \u00e7on n\u00eb iniciativ\u00ebn p\u00ebr t\u00eb krijuar nj\u00eb Active Full n\u00eb ekstentin e dyt\u00eb t\u00eb disponuesh\u00ebm. N\u00ebse retention yn\u00eb \u00ebsht\u00eb kat\u00ebr, at\u00ebher\u00eb kur e gjith\u00eb zinxhiri, q\u00eb ndodhet n\u00eb ekstentin e vulosur, kalon p\u00ebrtej k\u00ebsaj, ai fshihet pa ndonj\u00eb pendes\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/5476ebcf9b57eeb6c0326499ac42763f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKa jan\u00eb situata kur fshirja ndodh m\u00eb her\u00ebt. P\u00ebr shembull, kjo \u00ebsht\u00eb Forward incremental me fula periodike. N\u00ebse dy dit\u00ebt e para krijuam backup-e t\u00eb plota, dhe n\u00eb t\u00eb enjten vendosim t\u00eb vulosim depozitat, at\u00ebher\u00eb t\u00eb premten, kur krijohet nj\u00eb backup i ri, dosja e t\u00eb h\u00ebn\u00ebs do t\u00eb fshihet sepse deri n\u00eb k\u00ebt\u00eb pik\u00eb nuk ka var\u00ebsi. Dhe vet\u00eb pika nuk varet nga askush. Pas k\u00ebsaj presim q\u00eb t\u00eb krijohen kat\u00ebr pika n\u00eb q\u00ebllimin e aksesuesh\u00ebm dhe fshijm\u00eb tri t\u00eb mbetura, t\u00eb cilat nuk mund t\u00eb fshihen n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur nga nj\u00ebra-tjetra.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/c6cc452f98336803731163dfd794f828.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nGj\u00ebra jan\u00eb m\u00eb t\u00eb thjeshta me Reverse Incremental. N\u00eb t\u00eb, pikat m\u00eb t\u00eb vjetra nuk varen nga asgj\u00eb dhe mund t\u00eb fshihen n\u00eb paqe. Prandaj, sa her\u00eb q\u00eb krijohet nj\u00eb .vbk e re n\u00eb nj\u00eb q\u00ebllim t\u00eb ri, t\u00eb vjetrat .vrb do t\u00eb fshihen nj\u00eb nga nj\u00eb.<\/p>\n<p>P\u00ebr m\u00eb tep\u00ebr, pse \u00e7do her\u00eb krijojm\u00eb nj\u00eb .vbk t\u00eb re: n\u00ebse nuk e krijojm\u00eb dhe vazhdojm\u00eb me zinxhirin e vjet\u00ebr t\u00eb inkrementimeve, e vjetra .vbk do t\u00eb ngec\u00eb p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb n\u00eb \u00e7do mod, duke penguar fshirjen e saj. Prandaj u mor vendimi q\u00eb sa her\u00eb q\u00eb vuloset nj\u00eb q\u00ebllim, krijojm\u00eb nj\u00eb backup t\u00eb plot\u00eb n\u00eb nj\u00eb q\u00ebllim t\u00eb lir\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/3757fae46ad76d64cdddfb941309d557.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nGj\u00ebra jan\u00eb m\u00eb t\u00eb komplikuara me kapacitetin e tirit. <\/p>\n<p>S\u00eb pari le t\u00eb shqyrtojm\u00eb modalitetin copy. Supozoni se kemi krijuar backup p\u00ebr kat\u00ebr dit\u00eb dhe pastaj kapaciteti i tir-it u mbyll. Ne nuk fshijm\u00eb asgj\u00eb, por me durim presim p\u00ebr mbajtjen, pas s\u00eb cil\u00ebs fshijm\u00eb t\u00eb dh\u00ebnat nga kapaciteti i tir-it.<\/p>\n<p>P\u00ebrgjith\u00ebsisht, e nj\u00ebjta gj\u00eb ndodh edhe n\u00eb modalitetin move \u2014 presim p\u00ebr mbajtjen, fshijm\u00eb t\u00eb vjetrin n\u00eb ruajtjen lokale, fshijm\u00eb at\u00eb q\u00eb \u00ebsht\u00eb ruajtur n\u00eb objektin e ruajtjes.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/391d3b231c7de5da1d13e19c31bd6b7c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNj\u00eb shembull interesant me Forever forward incremental. Vendosim mbajtjen n\u00eb tre pika dhe fillojm\u00eb t\u00eb b\u00ebjm\u00eb backup q\u00eb nga e h\u00ebna, t\u00eb cilat kopjohen me korrekt\u00ebsi n\u00eb cloud. Pas mbylljes s\u00eb ruajtjes, backup vazhdon t\u00eb krijohet, duke respektuar tre pik\u00ebt, por t\u00eb dh\u00ebnat e ruajtura n\u00eb kapacitetin e tir-it mbeten t\u00eb varura dhe nuk mund t\u00eb fshihen. Prandaj presim deri t\u00eb enjten, kur .vbk yn\u00eb kalon jasht\u00eb mbajtjes, dhe vet\u00ebm at\u00ebher\u00eb e fshijm\u00eb qet\u00ebsisht t\u00eb gjith\u00eb zinxhirin e ruajtur.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/617a42452060210b58148e1fe942a540.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDhe nj\u00eb sqarim i vog\u00ebl: t\u00eb gjitha shembujt k\u00ebtu jan\u00eb treguar me nj\u00eb makin\u00eb. N\u00ebse keni disa n\u00eb backup, at\u00ebher\u00eb mbajtja e tyre do t\u00eb jet\u00eb ndryshe n\u00eb var\u00ebsi t\u00eb k\u00ebsaj n\u00ebse \u00ebsht\u00eb b\u00ebr\u00eb nj\u00eb Active Full apo jo.<\/p>\n<p>K\u00ebshtu q\u00eb, n\u00eb parim, kjo \u00ebsht\u00eb e gjitha. Tani kalojm\u00eb n\u00eb tipar m\u00eb t\u00eb fort\u00eb \u2014 <\/p>\n<h3>Immutability <\/h3>\n<p>\nSi me dhe pikat e m\u00ebparshme, e para \u00ebsht\u00eb t\u00eb sqarojm\u00eb se \u00e7far\u00eb problemi zgjidh kjo funksion. Sa her\u00eb q\u00eb eksportojm\u00eb kopjet rezerv\u00eb p\u00ebr ruajtje, lind d\u00ebshira p\u00ebr t\u00eb garantuar ruajtjen e tyre, dometh\u00ebn\u00eb p\u00ebr t\u00eb ndaluar fizikisht fshirjen e tyre dhe \u00e7do modifikim p\u00ebr gjat\u00eb periudh\u00ebs s\u00eb caktuar t\u00eb ruajtjes. Kjo p\u00ebrfshin edhe administrator\u00ebt, duke p\u00ebrfshir\u00eb llogarit\u00eb e tyre me privilegje t\u00eb plota. Kjo mund\u00ebson mbrojtjen e tyre nga d\u00ebmtimi aksidental ose t\u00eb q\u00ebllimsh\u00ebm. Ata q\u00eb punojn\u00eb me AWS mund t\u00eb hasin nj\u00eb funksion t\u00eb till\u00eb n\u00ebn emrin Object Lock.<\/p>\n<p>Tani le t\u00eb shqyrtojm\u00eb funksionin n\u00eb terma t\u00eb p\u00ebrgjithsh\u00ebm, dhe pastaj t\u00eb zhytim thell\u00eb n\u00eb detaje. N\u00eb shembullin ton\u00eb, Immutability do t\u00eb aktivizohet p\u00ebr kapacitetin ton\u00eb me nj\u00eb periudh\u00eb ruajtjeje prej kat\u00ebr dit\u00ebsh. Nd\u00ebrsa kopja rezerv\u00eb do t\u00eb p\u00ebrmbaj\u00eb modin Copy.<\/p>\n<p>Immutability nuk nd\u00ebrvepron aspak me periudh\u00ebn e p\u00ebrgjithshme t\u00eb ruajtjes. P\u00ebr shembull, ai nuk shton pik\u00eb t\u00eb tjera ose gj\u00ebra t\u00eb tilla. Thjesht, p\u00ebr gjat\u00eb kat\u00ebr dit\u00ebve, nj\u00eb person nuk mund t\u00eb fshij\u00eb skedar\u00ebt e kopjeve rezerv\u00eb. N\u00ebse b\u00ebhet nj\u00eb kopje rezerv\u00eb t\u00eb h\u00ebn\u00ebn, skedari i saj mund t\u00eb fshihet vet\u00ebm t\u00eb premten.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/131e50058c1a015ec78089ed4d038bfc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nT\u00eb gjitha konceptet e shpjeguara m\u00eb par\u00eb n\u00eb lidhje me dehidrimin, indeksat dhe metadata vazhdojn\u00eb t\u00eb funksionojn\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb nj\u00ebjt\u00eb. Megjithat\u00eb, me nj\u00eb kusht \u2014 blloku vendoset jo vet\u00ebm p\u00ebr t\u00eb dh\u00ebnat, por edhe p\u00ebr metadatat. Kjo \u00ebsht\u00eb b\u00ebr\u00eb p\u00ebr t'i ardhur n\u00eb ndihm\u00eb rastit kur ndonj\u00eb sulmues i keq do t\u00eb p\u00ebrpiqej t\u00eb fshinte baz\u00ebn ton\u00eb t\u00eb metadatat dhe p\u00ebr t\u00eb siguruar q\u00eb blloqet e t\u00eb dh\u00ebnave t\u00eb mos kthehen n\u00eb nj\u00eb p\u00ebrzierje binar\u00ebsh t\u00eb padobish\u00ebm.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/edfe5c04a082594cf5d67f4bafeccb3a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDhe tani ka ardhur momenti fantastic p\u00ebr t\u00eb shpjeguar teknologjin\u00eb ton\u00eb t\u00eb gjenerimit t\u00eb blloqeve. Ose gjenerimi i blloqeve. P\u00ebr k\u00ebt\u00eb, le t\u00eb pranojm\u00eb nj\u00eb situat\u00eb q\u00eb e ka sjell\u00eb n\u00eb jet\u00eb at\u00eb.<\/p>\n<p>T\u00eb marrim nj\u00eb periudh\u00eb kohore prej gjasht\u00eb dit\u00ebsh dhe nga posht\u00eb do t\u00eb sh\u00ebnojm\u00eb koh\u00ebn q\u00eb pritet t\u00eb skadoj\u00eb immutability. Merrni dhe krijoni dit\u00ebn e par\u00eb nj\u00eb skedar, i cili p\u00ebrb\u00ebhet nga nj\u00eb bllok t\u00eb dh\u00ebnash a, dhe metadat\u00ebt e tij. N\u00ebse immutability \u00ebsht\u00eb vendosur n\u00eb tri dit\u00eb, \u00ebsht\u00eb logjike t\u00eb supozojm\u00eb se n\u00eb dit\u00ebn e kat\u00ebrt t\u00eb dh\u00ebnat do t\u00eb shihen dhe fshihen. N\u00eb dit\u00ebn e dyt\u00eb do t\u00eb shtojm\u00eb nj\u00eb skedar t\u00eb ri file2, i cili p\u00ebrb\u00ebhet nga blloku b me t\u00eb nj\u00ebjtat cil\u00ebsime. Blloku a ende duhet t\u00eb fshihet n\u00eb dit\u00ebn e kat\u00ebrt. Por n\u00eb dit\u00ebn e tret\u00eb ndodh nj\u00eb ngjarje e frikshme - krijohet skedari File3, i cili p\u00ebrb\u00ebhet nga nj\u00eb bllok t\u00eb ri d dhe nj\u00eb lidhje me bllokun e vjet\u00ebr a. Kjo do t\u00eb thot\u00eb se p\u00ebr bllokun a flamuri immutability duhet t\u00eb ri-vendoset p\u00ebr nj\u00eb afat t\u00eb ri, i cili shtyhet n\u00eb dit\u00ebn e gjasht\u00eb. Dhe k\u00ebtu lind problemi - n\u00eb backupet reale t\u00eb k\u00ebtyre bllok\u00ebve krijohet nj\u00eb num\u00ebr i madh. Dhe p\u00ebr t\u00eb zgjatur periudh\u00ebn immutability, duhet n\u00eb \u00e7do rast t\u00eb b\u00ebni nj\u00eb num\u00ebr t\u00eb madh k\u00ebrkesash. Dhe n\u00eb fakt, ky do t\u00eb jet\u00eb nj\u00eb proces pothuajse t\u00eb pafund \u00e7do dit\u00eb, pasi me nj\u00eb probabilitet t\u00eb madh gjat\u00eb \u00e7do kopjimi do t\u00eb gjejm\u00eb ambalazhe t\u00eb m\u00ebdha t\u00eb bllok\u00ebve t\u00eb de-duplikuar. Dhe \u00e7far\u00eb do t\u00eb thot\u00eb nj\u00eb num\u00ebr i madh k\u00ebrkesash p\u00ebr ofruesit e object storage? Sakt\u00eb! Nj\u00eb fatur\u00eb enorme n\u00eb fund t\u00eb muajit.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/ce9c5d0da67f99019b00c4a666302fee.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDhe p\u00ebr t\u00eb mos i detyruar klient\u00ebt tan\u00eb t\u00eb dashur t\u00eb paguajn\u00eb shum\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb panevojshme, \u00ebsht\u00eb zbuluar mekanizmi i gjenerimit t\u00eb bllokut. Ky \u00ebsht\u00eb nj\u00eb periudh\u00eb shtes\u00eb q\u00eb ne e Shtojm\u00eb n\u00eb periudh\u00ebn e caktuar t\u00eb pap\u00ebrshkueshm\u00ebris\u00eb. N\u00eb shembullin m\u00eb posht\u00eb, kjo periudh\u00eb \u00ebsht\u00eb dy dit\u00eb. Por kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb shembull. N\u00eb realitet, p\u00ebrdoret nj\u00eb formul\u00eb e ve\u00e7ant\u00eb q\u00eb ofron rreth dhjet\u00eb dit\u00eb shtes\u00eb p\u00ebr \u00e7do bllokim mujor. <\/p>\n<p>T\u00eb nj\u00ebjt\u00ebn situat\u00eb do ta shohim tani, por me gjenerimin e blloqeve. N\u00eb dit\u00ebn e par\u00eb krijojm\u00eb file1 nga blloku a dhe metadatave. Mblidhni periudh\u00ebn e gjenerimeve dhe immutability \u2014 kjo do t\u00eb thot\u00eb se mund\u00ebsia p\u00ebr t\u00eb fshir\u00eb skedarin do t\u00eb jet\u00eb n\u00eb dit\u00ebn e gjasht\u00eb. N\u00ebse n\u00eb dit\u00ebn e dyt\u00eb krijojm\u00eb File2, i cili p\u00ebrb\u00ebhet nga blloku b dhe nj\u00eb link p\u00ebr bllokun a, at\u00ebher\u00eb data e parashikuar p\u00ebr fshirje nuk ndryshon. Ajo vazhdon t\u00eb mbetet n\u00eb dit\u00ebn e gjasht\u00eb. K\u00ebshtu ne mundohemi t\u00eb kursim para n\u00eb numrin e k\u00ebrkesave. Situata e vetme kur afati mund t\u00eb ndryshohet \u00ebsht\u00eb n\u00ebse periudha e gjenerimit ka skaduar. Pra, n\u00ebse n\u00eb dit\u00ebn e tret\u00eb File3 i ri do t\u00eb p\u00ebrmbaj\u00eb nj\u00eb link p\u00ebr bllokun a, at\u00ebher\u00eb do t\u00eb shtohet gjenerimi 2 pasi Gen1 ka skaduar. Dhe data e pritur e fshirjes s\u00eb bllokut a do t\u00eb zgjatet n\u00eb dit\u00ebn e tet\u00eb. Kjo na lejon t\u00eb zvog\u00eblojm\u00eb dramatikisht numrin e k\u00ebrkesave p\u00ebr t\u00eb zgjatur jet\u00ebn e blloqeve t\u00eb deduplikuara, gj\u00eb q\u00eb kursen shum\u00eb para p\u00ebr klient\u00ebt.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10\" src=\"\/wp-content\/uploads\/2020\/06\/2056d0c15e4e7fcdd67a56b11f973119.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u0421\u0430\u043c\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u0430 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c S3 \u0438 S3-\u0441\u043e\u0432\u043c\u0435\u0441\u0442\u0438\u043c\u043e\u0433\u043e \u0436\u0435\u043b\u0435\u0437\u0430, \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u0438 \u043a\u043e\u0442\u043e\u0440\u043e\u0433\u043e \u0433\u0430\u0440\u0430\u043d\u0442\u0438\u0440\u0443\u044e\u0442, \u0447\u0442\u043e \u0438\u0445 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u043d\u0435 \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u043e\u0442 \u0430\u043c\u0430\u0437\u043e\u043d\u043e\u0432\u0441\u043a\u043e\u0439. \u041e\u0442\u0441\u044e\u0434\u0430 \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u0437\u0430\u043a\u043e\u043d\u043d\u044b\u0439 \u0432\u043e\u043f\u0440\u043e\u0441, \u043f\u043e\u0447\u0435\u043c\u0443 \u043d\u0435 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f Azure \u2014 \u0443 \u043d\u0438\u0445 \u0435\u0441\u0442\u044c \u0441\u0445\u043e\u0436\u0430\u044f \u0444\u0438\u0447\u0430, \u043d\u043e \u043e\u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432, \u0430 \u043d\u0435 \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0445 \u043e\u0431\u044a\u0435\u043a\u0442\u043e\u0432. \u041a\u0441\u0442\u0430\u0442\u0438, \u0432 \u0441\u0430\u043c\u043e\u043c \u0430\u043c\u0430\u0437\u043e\u043d\u0435 \u043e\u0431\u0436\u0435\u043a\u0442 \u043b\u043e\u043a \u0435\u0441\u0442\u044c \u0432 \u0434\u0432\u0443\u0445 \u0440\u0435\u0436\u0438\u043c\u0430\u0445: compliance \u0438 governance. \u0412\u043e \u0432\u0442\u043e\u0440\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435 \u043e\u0441\u0442\u0430\u0451\u0442\u0441\u044f \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c, \u0447\u0442\u043e\u0431\u044b \u0441\u0430\u043c\u044b\u0439 \u0432\u0435\u043b\u0438\u043a\u0438\u0439 \u0430\u0434\u043c\u0438\u043d \u043d\u0430\u0434 \u0430\u0434\u043c\u0438\u043d\u0430\u043c\u0438 \u0438 \u0440\u0443\u0442 \u043d\u0430\u0434 \u0440\u0443\u0442\u0430\u043c\u0438, \u043d\u0435\u0441\u043c\u043e\u0442\u0440\u044f \u043d\u0430 \u043e\u0431\u0436\u0435\u043a\u0442 \u043b\u043e\u043a, \u0432\u0441\u0451 \u0436\u0435 \u0443\u0434\u0430\u043b\u0438\u043b \u0434\u0430\u043d\u043d\u044b\u0435. \u0412 \u0441\u043b\u0443\u0447\u0430\u0435 compliance \u0432\u0441\u0451 \u043f\u0440\u0438\u0431\u0438\u0442\u043e \u0433\u0432\u043e\u0437\u0434\u044f\u043c\u0438 \u043d\u0430\u043c\u0435\u0440\u0442\u0432\u043e \u0438 \u0431\u0435\u043a\u0430\u043f\u044b \u043d\u0435 \u0443\u0434\u0430\u043b\u0438\u0442\u044c \u043d\u0438\u043a\u043e\u043c\u0443. \u0414\u0430\u0436\u0435 \u0443 \u0430\u0434\u043c\u0438\u043d\u043e\u0432 \u0430\u043c\u0430\u0437\u043e\u043d\u0430 (\u043f\u043e \u0438\u0445 \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u043c \u0437\u0430\u044f\u0432\u043b\u0435\u043d\u0438\u044f\u043c). \u041c\u044b \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u043c \u0438\u043c\u0435\u043d\u043d\u043e \u044d\u0442\u043e\u0442 \u0440\u0435\u0436\u0438\u043c.<\/p>\n<p>\n\u0418, \u0442\u0440\u0430\u0434\u0438\u0446\u0438\u043e\u043d\u043d\u043e, \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u0445 \u0441\u0441\u044b\u043b\u043e\u043a:<\/p>\n<ul>\n<li>P\u00ebr <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/block_generation.html?ver=100\">Block Generation<\/a><\/noindex> \u0432\u043e \u0432\u0441\u0435\u0445 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u044f\u0445.<\/li>\n<li>\u0412\u0441\u044f \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044f \u043f\u0440\u043e <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/overview.html?ver=100\">Veeam Backup &amp; Replication 10<\/a><\/noindex> \u0432 \u043b\u0443\u0447\u0448\u0435\u043c \u0432\u0438\u0434\u0435<\/li>\n<li>m\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/capacity_tier.html?ver=100\">Capacity Tier<\/a><\/noindex> \u0432 \u0434\u0435\u0442\u0430\u043b\u044f\u0445<\/li>\n<\/ul>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/505818\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>Capacity Tier (\u0438\u043b\u0438 \u043a\u0430\u043a \u043c\u044b \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c \u0435\u0433\u043e \u0443 \u0441\u0435\u0431\u044f \u0432\u043d\u0443\u0442\u0440\u0438 \u0432\u0438\u043c\u0430 \u2014 \u043a\u0430\u043f\u0442\u0438\u0440) \u043f\u043e\u044f\u0432\u0438\u043b\u0441\u044f \u0435\u0449\u0451 \u0432\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0430 Veeam Backup and Replication 9.5 Update 4 \u043f\u043e\u0434 \u0438\u043c\u0435\u043d\u0435\u043c Archive Tier. \u0417\u0430\u043b\u043e\u0436\u0435\u043d\u043d\u0430\u044f \u0432 \u043d\u0435\u0433\u043e \u0438\u0434\u0435\u044f \u2014 \u044d\u0442\u043e \u0434\u0430\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u043f\u0435\u0440\u0435\u043c\u0435\u0449\u0430\u0442\u044c \u0431\u0435\u043a\u0430\u043f\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u044b\u043f\u0430\u043b\u0438 \u0438\u0437 \u0442\u0430\u043a \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c\u043e\u0433\u043e operational restore window, \u043d\u0430 \u043e\u0431\u044a\u0435\u043a\u0442\u043d\u044b\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430. \u042d\u0442\u043e \u043f\u043e\u043c\u043e\u0433\u0430\u043b\u043e \u0440\u0430\u0441\u0447\u0438\u0449\u0430\u0442\u044c \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0435 \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u043e \u0442\u0435\u043c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":84810,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-84809","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"Capacity Tier (\u0438\u043b\u0438 \u043a\u0430\u043a \u043c\u044b \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c \u0435\u0433\u043e \u0443 \u0441\u0435\u0431\u044f \u0432\u043d\u0443\u0442\u0440\u0438 \u0432\u0438\u043c\u0430 \u2014 \u043a\u0430\u043f\u0442\u0438\u0440) \u043f\u043e\u044f\u0432\u0438\u043b\u0441\u044f \u0435\u0449\u0451 \u0432\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0430 Veeam Backup and Replication 9.5 Update 4 \u043f\u043e\u0434 \u0438\u043c\u0435\u043d\u0435\u043c Archive Tier. \u0417\u0430\u043b\u043e\u0436\u0435\u043d\u043d\u0430\u044f \u0432 \u043d\u0435\u0433\u043e \u0438\u0434\u0435\u044f \u2014 \u044d\u0442\u043e \u0434\u0430\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u043f\u0435\u0440\u0435\u043c\u0435\u0449\u0430\u0442\u044c \u0431\u0435\u043a\u0430\u043f\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u044b\u043f\u0430\u043b\u0438 \u0438\u0437 \u0442\u0430\u043a \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c\u043e\u0433\u043e operational restore window, \u043d\u0430 \u043e\u0431\u044a\u0435\u043a\u0442\u043d\u044b\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430. \u042d\u0442\u043e \u043f\u043e\u043c\u043e\u0433\u0430\u043b\u043e \u0440\u0430\u0441\u0447\u0438\u0449\u0430\u0442\u044c \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0435 \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u043e \u0442\u0435\u043c\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0427\u0442\u043e \u0438\u0437\u043c\u0435\u043d\u0438\u043b\u043e\u0441\u044c \u0432 Capacity Tier, \u043a\u043e\u0433\u0434\u0430 Veeam \u0441\u0442\u0430\u043b v10 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"Capacity Tier (\u0438\u043b\u0438 \u043a\u0430\u043a \u043c\u044b \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c \u0435\u0433\u043e \u0443 \u0441\u0435\u0431\u044f \u0432\u043d\u0443\u0442\u0440\u0438 \u0432\u0438\u043c\u0430 \u2014 \u043a\u0430\u043f\u0442\u0438\u0440) \u043f\u043e\u044f\u0432\u0438\u043b\u0441\u044f \u0435\u0449\u0451 \u0432\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0430 Veeam Backup and Replication 9.5 Update 4 \u043f\u043e\u0434 \u0438\u043c\u0435\u043d\u0435\u043c Archive Tier. \u0417\u0430\u043b\u043e\u0436\u0435\u043d\u043d\u0430\u044f \u0432 \u043d\u0435\u0433\u043e \u0438\u0434\u0435\u044f \u2014 \u044d\u0442\u043e \u0434\u0430\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u043f\u0435\u0440\u0435\u043c\u0435\u0449\u0430\u0442\u044c \u0431\u0435\u043a\u0430\u043f\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u044b\u043f\u0430\u043b\u0438 \u0438\u0437 \u0442\u0430\u043a \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c\u043e\u0433\u043e operational restore window, \u043d\u0430 \u043e\u0431\u044a\u0435\u043a\u0442\u043d\u044b\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430. \u042d\u0442\u043e \u043f\u043e\u043c\u043e\u0433\u0430\u043b\u043e \u0440\u0430\u0441\u0447\u0438\u0449\u0430\u0442\u044c \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0435 \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u043e \u0442\u0435\u043c\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-06-10T23:42:41+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-06-10T23:42:41+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47\u00c7far\u00eb ka ndryshuar n\u00eb Capacity Tier, kur Veeam u b\u00eb v10 | ProHoster","description":"Kapaciteti Tier (ose si\u00e7 e quajm\u00eb ne brenda vima \u2014 kaptir) u shfaq p\u00ebr her\u00eb t\u00eb par\u00eb n\u00eb koh\u00ebn e Veeam Backup dhe Replication 9.5 Update 4 me emrin Archive Tier. Ideja e tij \u00ebsht\u00eb t\u00eb ofroj\u00eb mund\u00ebsin\u00eb p\u00ebr t\u00eb zhvendosur backup-et q\u00eb kan\u00eb kaluar nga dritarja e rikthimit operativ, n\u00eb magazinat objektore. Kjo ndihmonte n\u00eb pastrimin e hap\u00ebsir\u00ebs diskore.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0427\u0442\u043e \u0438\u0437\u043c\u0435\u043d\u0438\u043b\u043e\u0441\u044c \u0432 Capacity Tier, \u043a\u043e\u0433\u0434\u0430 Veeam \u0441\u0442\u0430\u043b v10 | ProHoster","og:description":"Capacity Tier (\u0438\u043b\u0438 \u043a\u0430\u043a \u043c\u044b \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c \u0435\u0433\u043e \u0443 \u0441\u0435\u0431\u044f \u0432\u043d\u0443\u0442\u0440\u0438 \u0432\u0438\u043c\u0430 \u2014 \u043a\u0430\u043f\u0442\u0438\u0440) \u043f\u043e\u044f\u0432\u0438\u043b\u0441\u044f \u0435\u0449\u0451 \u0432\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0430 Veeam Backup and Replication 9.5 Update 4 \u043f\u043e\u0434 \u0438\u043c\u0435\u043d\u0435\u043c Archive Tier. \u0417\u0430\u043b\u043e\u0436\u0435\u043d\u043d\u0430\u044f \u0432 \u043d\u0435\u0433\u043e \u0438\u0434\u0435\u044f \u2014 \u044d\u0442\u043e \u0434\u0430\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u043f\u0435\u0440\u0435\u043c\u0435\u0449\u0430\u0442\u044c \u0431\u0435\u043a\u0430\u043f\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u044b\u043f\u0430\u043b\u0438 \u0438\u0437 \u0442\u0430\u043a \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u043c\u043e\u0433\u043e operational restore window, \u043d\u0430 \u043e\u0431\u044a\u0435\u043a\u0442\u043d\u044b\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430. \u042d\u0442\u043e \u043f\u043e\u043c\u043e\u0433\u0430\u043b\u043e \u0440\u0430\u0441\u0447\u0438\u0449\u0430\u0442\u044c \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0435 \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u043e \u0442\u0435\u043c","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-06-10T23:42:41+00:00","article:modified_time":"2020-06-10T23:42:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"84809","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 14:49:54","updated":"2022-09-29 08:38:47"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/84809","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=84809"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/84809\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/84810"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=84809"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=84809"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=84809"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}