{"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 ndryshoi n\u00eb Capacity Tier kur Veeam u b\u00eb v10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Kapaciteti Tier (ose si\u00e7 e quajm\u00eb brenda vetes - kaptir) u shfaq q\u00eb n\u00eb koh\u00ebn e Veeam Backup dhe Replication 9.5 Update 4 me emrin Archive Tier. Ideja pas k\u00ebtij \u00ebsht\u00eb t\u00eb mund\u00ebsoj\u00eb zhvendosjen e kopjeve rezerv\u00eb q\u00eb kan\u00eb dal\u00eb jasht\u00eb dritares operacionale t\u00eb rikuperimit n\u00eb magazinat objektive. Kjo ndihmonte n\u00eb lirimin e hap\u00ebsir\u00ebs diskore p\u00ebr ata p\u00ebrdorues q\u00eb kishin hap\u00ebsir\u00eb t\u00eb kufizuar. Kjo opsion quhet Move Mode.<\/p>\n<p>P\u00ebr t\u00eb realizuar k\u00ebt\u00eb veprim t\u00eb thjesht\u00eb (si\u00e7 duket) mjaftonte t\u00eb p\u00ebrmbusheshin dy kushte: t\u00eb gjitha pikat nga kopja rezerv\u00eb e zhvendosur duhet t\u00eb ishin jasht\u00eb dritares s\u00eb rikuperimit operacional, e cila \u00ebsht\u00eb e specifikuar qart\u00eb n\u00eb UI. E dyta: zinxhiri duhet t\u00eb jet\u00eb n\u00eb nj\u00eb \"form\u00eb t\u00eb vulosur\" (sealed backup chain ose Inactive Backup Chain). Kjo do t\u00eb thot\u00eb se 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 - u shfaq\u00ebn Copy Mode, Sealed Mode dhe nj\u00eb gj\u00eb me nj\u00eb em\u00ebr t\u00eb v\u00ebshtir\u00eb p\u00ebr tu th\u00ebn\u00eb Immutability.<\/p>\n<p>K\u00ebto gj\u00ebra interesante ne do t\u00eb diskutojm\u00eb sot. Fillimisht p\u00ebr at\u00eb se si funksiononte n\u00eb VBR9.5u4, dhe pastaj p\u00ebr ndryshimet n\u00eb versionin e dhjet\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 le t\u00eb m\u00eb falin ata q\u00eb mbrojn\u00eb gjuh\u00ebn e past\u00ebr, por shum\u00eb terma nuk mund t\u00eb p\u00ebrkthehen.<br \/>\nPra, 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 ishte<\/h1>\n<p>\nPra, le t\u00eb fillojm\u00eb me analiz\u00ebn e dritares operative t\u00eb rikuperimit dhe backup-it t\u00eb vulosur (ose siqu quhen n\u00eb dokumentacion Inactive Backup Chain). Pa kuptuar ato, nuk mund t\u00eb shpjegohet m\u00eb tej.<\/p>\n<p>Si\u00e7 e shohim n\u00eb figur\u00eb, kemi nj\u00eb zinxhir rezerv\u00eb me blloqe t\u00eb dh\u00ebnash, i cili ndodhet n\u00eb Performance tier t\u00eb repositorit SOBR, ku \u00ebsht\u00eb lidhur Kapaciteti Tier. Dritarja jon\u00eb operacionale e rezervimit \u00ebsht\u00eb e barabart\u00eb me tre dit\u00eb.<\/p>\n<p>K\u00ebshtu, nj\u00eb .vbk e krijuar t\u00eb h\u00ebn\u00ebn 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 paq pastrimin n\u00eb kapacitetin tier t\u00eb gjitha ato q\u00eb jan\u00eb m\u00eb t\u00eb vjetra se k\u00ebto tri dit\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 do t\u00eb thoshte pik\u00ebrisht nj\u00eb zinxhir i vulosur dhe \u00e7far\u00eb mund t\u00eb d\u00ebrgohej n\u00eb kapacitetin tier n\u00eb update 4?<\/p>\n<p>P\u00ebr Forward Incremental, treguesi i vulosjes s\u00eb zinxhirit \u00ebsht\u00eb krijimi i nj\u00eb backup-i t\u00eb plot\u00eb t\u00eb ri. Dhe nuk ka r\u00ebnd\u00ebsi se si merret ky backup i plot\u00eb: konsiderohet si backup i plot\u00eb sintetik dhe backup i plot\u00eb aktiv.<\/p>\n<p>N\u00eb rastin e Reverse, k\u00ebto jan\u00eb t\u00eb gjitha skedar\u00ebt q\u00eb nuk bien n\u00eb dritaren operacionale. <\/p>\n<p>N\u00eb rastin e Forward increment me rrotullime, t\u00eb gjitha rrotullimet dhe .vbk, n\u00ebse n\u00eb kapacitetin e performanc\u00ebs ka edhe nj\u00eb tjet\u00ebr .vbk.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 opsionin e pun\u00ebs me zinxhir\u00ebt e Backup Copy. K\u00ebtu \u00ebsht\u00eb ruajtur vet\u00ebm ajo q\u00eb p\u00ebrfshin ruajtjen GFS. Sepse gjith\u00e7ka q\u00eb ndodhet n\u00eb zinxhir\u00ebt m\u00eb t\u00eb rinj t\u00eb backup copy mund t\u00eb jet\u00eb ndonj\u00ebher\u00eb e ndryshuar n\u00eb nj\u00eb m\u00ebnyr\u00eb ose n\u00eb nj\u00eb tjet\u00ebr.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 shohim n\u00ebn kapak. Atje ndodh nj\u00eb proces i quajtur dehidrim - l\u00ebnia e q\u00ebndrushmeve t\u00eb skedar\u00ebve t\u00eb backup n\u00eb kapacitet dhe zhvendosja e blloqeve nga k\u00ebta skedar\u00eb n\u00eb rezervat e kapacitetit. P\u00ebr t\u00eb optimizuar k\u00ebt\u00eb proces, p\u00ebrdoret nj\u00eb indeks i ashtuquajtur dehidrimi, i cili lejon q\u00eb t\u00eb mos kopjohen blloqet q\u00eb jan\u00eb kopjuar tashm\u00eb n\u00eb rezervat e kapacitetit. <\/p>\n<p>Le t\u00eb shohim si duket kjo n\u00eb nj\u00eb shembull: supozoni se kemi nj\u00eb .vbk, q\u00eb ka dal\u00eb nga fush\u00ebpamja operacionale dhe i p\u00ebrket nj\u00eb zinxhiri t\u00eb vulosur. K\u00ebshtu, ne kemi t\u00eb drejt\u00eb ta transferojm\u00eb at\u00eb n\u00eb rezervat e kapacitetit. N\u00eb momentin e zhvendosjes krijohet nj\u00eb skedar metadata n\u00eb rezerv\u00ebn e kapacitetit dhe blloqet e skedarit t\u00eb transferuar. N\u00eb skedarin e metadatas n\u00eb nivelin e lidhjeve p\u00ebrshkruhet nga cilat blloqe p\u00ebrb\u00ebhet skedari yn\u00eb. N\u00eb rastin n\u00eb figur\u00eb, skedari yn\u00eb i par\u00eb p\u00ebrb\u00ebhet nga blloqet a, b, c dhe n\u00eb metadat e vendosura jan\u00eb lidhjet p\u00ebr k\u00ebto blloqe. Kur kemi nj\u00eb skedar t\u00eb dyt\u00eb .vbk, gati p\u00ebr t'u zhvendosur dhe i p\u00ebrb\u00ebr\u00eb nga blloqet a, b dhe d, ne, duke analizuar indeksin e dehidrimit, kuptojm\u00eb se duhet t\u00eb transferojm\u00eb vet\u00ebm bllokun d. Skedari i tij i metadatas do t\u00eb p\u00ebrmbaj\u00eb lidhjet p\u00ebr dy blloqet e m\u00ebparshme dhe nj\u00eb t\u00eb re.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 \/>\nP\u00ebr k\u00ebt\u00eb arsye, procesi i mbushjes s\u00eb k\u00ebtyre q\u00ebndrushmeve me t\u00eb dh\u00ebna quhet rehidrimi. K\u00ebtu p\u00ebrdoret nj\u00eb indeks i vet\u00eb rehidrimit, i mb\u00ebshtetur n\u00eb skedarin m\u00eb t\u00eb vjet\u00ebr .vbk n\u00eb kapacitetin e performanc\u00ebs lokale. K\u00ebshtu, n\u00ebse nj\u00eb p\u00ebrdorues d\u00ebshiron t\u00eb rikthej\u00eb nj\u00eb skedar nga rezervat e kapacitetit, ne fillimisht krijojm\u00eb nj\u00eb indeks blloqesh t\u00eb backup-it m\u00eb t\u00eb plot\u00eb t\u00eb vjet\u00ebr dhe zhvendosim nga rezervat e kapacitetit vet\u00ebm blloqet e munguar. N\u00eb rastin e paraqitur n\u00eb figur\u00eb, p\u00ebr t\u00eb rehidratuar FullBackup1.vbk sipas indeksit t\u00eb rehidrimit na mungon vet\u00ebm blloku C, t\u00eb cilin e marrim nga rezervat e kapacitetit. N\u00ebse si rezerv\u00eb kapaciteti sh\u00ebrben nj\u00eb objekt blerjeje n\u00eb re, kjo lejon kursimin e nj\u00eb shume t\u00eb madhe parash.<\/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 n\u00eb kuad\u00ebr t\u00eb \u00e7do faili n\u00eb nj\u00eb offset t\u00eb caktuar. Kjo ndodh p\u00ebr shkak t\u00eb ndryshimit t\u00eb detyrave q\u00eb zgjidhim: k\u00ebtu na nevojitet t\u00eb kopjojm\u00eb skedar\u00eb t\u00eb m\u00ebdhenj t\u00eb backup-eve t\u00eb plota, dhe sipas k\u00ebrkimeve tona, madje edhe n\u00ebse kalon nj\u00eb periudh\u00eb e madhe kohe mes tyre, nj\u00eb algorit\u00ebm i till\u00eb i deduplikimit ofron rezultatet m\u00eb t\u00eb mira.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 Zotit indekseve! Ka edhe nj\u00eb indeks p\u00ebr rikuperimin e t\u00eb dh\u00ebnave! Kur ne fillojm\u00eb rikuperimin e nj\u00eb makine t\u00eb vendosur n\u00eb kapacitetin e rezervuarit, at\u00ebher\u00eb do t\u00eb lexojm\u00eb vet\u00ebm blloqet unike t\u00eb t\u00eb dh\u00ebnave, t\u00eb cilat nuk gjenden n\u00eb rezervuarin e performanc\u00ebs.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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>\nK\u00ebtu p\u00ebrfundon pjesa hyr\u00ebse. Ajo \u00ebsht\u00eb mjaft e detajuar, por, si\u00e7 u tha m\u00eb par\u00eb, pa k\u00ebto detaje nuk mund t\u00eb shpjegojm\u00eb se si funksionojn\u00eb tiparet e reja. Prandaj, pa asnj\u00eb parath\u00ebnie, kalojm\u00eb n\u00eb t\u00eb par\u00ebn.<\/p>\n<h3>M\u00ebnyra kopjimi<\/h3>\n<p>\nN\u00eb shum\u00eb aspekte bazohet n\u00eb teknologjit\u00eb ekzistuese, megjithat\u00eb sjell nj\u00eb logjik\u00eb krejt\u00ebsisht tjet\u00ebr p\u00ebrdorimi.\u00a0<\/p>\n<p>Q\u00ebllimi i k\u00ebtij mode \u00ebsht\u00eb t\u00eb siguroj\u00eb q\u00eb t\u00eb gjitha t\u00eb dh\u00ebnat e vendosura n\u00eb ekstentin lokal t\u00eb ken\u00eb nj\u00eb kopje n\u00eb kapacitetin e rezervuarit.<\/p>\n<p>N\u00ebse e krahasojm\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb drejtp\u00ebrdrejt\u00eb m\u00ebnyrat Move dhe Copy, do t\u00eb rezultonte k\u00ebshtu:<\/p>\n<ul>\n<li>Mund t\u00eb l\u00ebvizni vet\u00ebm zinxhirin e vulosur. N\u00eb rastin e m\u00ebnyr\u00ebs s\u00eb kopjimit, transportohet krejt\u00ebsisht gjith\u00e7ka, pavar\u00ebsisht nga ajo q\u00eb ndodh n\u00eb pun\u00ebn e backup-it.<\/li>\n<li>L\u00ebvizja aktivizohet kur skedar\u00ebt dalin jasht\u00eb dritares operacionale t\u00eb backup-it, nd\u00ebrsa kopjimi aktivizohet menj\u00ebher\u00eb sapo shfaqet skedari i backup-it.<\/li>\n<li>Ndjekja e t\u00eb dh\u00ebnave t\u00eb reja p\u00ebr kopjim ndodh vazhdimisht, nd\u00ebrsa p\u00ebr l\u00ebvizje aktivizohej nj\u00eb her\u00eb n\u00eb 4 or\u00eb.<\/li>\n<\/ul>\n<p>\nDuke shqyrtuar m\u00ebnyr\u00ebn e re, propozoj t\u00eb shkojm\u00eb nga shembujt e thjesht\u00eb te ata m\u00eb t\u00eb komplikuar.<\/p>\n<p>N\u00eb rastin m\u00eb t\u00eb zakonsh\u00ebm, thjesht shfaqen skedar\u00eb t\u00eb rinj me inkrementet dhe ne thjesht i kopjojm\u00eb ato n\u00eb kapacitetin e rezervuarit. Pa marr\u00eb parasysh se cila m\u00ebnyr\u00eb p\u00ebrdoret n\u00eb pun\u00ebn e backup-it, pa marr\u00eb parasysh n\u00ebse i p\u00ebrket pjes\u00ebs s\u00eb vulosur t\u00eb zinxhirit apo jo, pa marr\u00eb parasysh n\u00ebse ka skaduar dritarja jon\u00eb operative. Thjesht mor\u00ebm dhe kopjuam.<\/p>\n<p>Procesi q\u00eb q\u00ebndron pas k\u00ebsaj \u00ebsht\u00eb ende dehidrimi ashtu si\u00e7 \u00ebsht\u00eb p\u00ebrshkruar m\u00eb sip\u00ebr. N\u00eb modalitetin e kopjimit, ai gjithashtu ndjek q\u00eb t\u00eb mos kopjojm\u00eb blloqet q\u00eb tashm\u00eb jan\u00eb n\u00eb storage-in ton\u00eb. Diferenca e vetme \u00ebsht\u00eb q\u00eb n\u00eb modalitetin e l\u00ebvizjes ne z\u00ebvend\u00ebsonim skedar\u00ebt real\u00eb me skedar\u00eb zbraz\u00ebt, nd\u00ebrsa k\u00ebtu ne nuk i prekim fare dhe e l\u00ebm\u00eb gjith\u00e7ka si\u00e7 \u00ebsht\u00eb. P\u00ebrndryshe, ky \u00ebsht\u00eb nj\u00eb indeks i till\u00eb dehidrimi, 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 ndryshoi 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 \/>\nShqet\u00ebsimi q\u00eb lind \u00ebsht\u00eb \u2014 n\u00ebse shohim n\u00eb UI, aty ka mund\u00ebsin\u00eb p\u00ebr t\u00eb zgjedhur t\u00eb dy opsionet nj\u00ebkoh\u00ebsisht. Si do t\u00eb funksionoj\u00eb nj\u00eb modalitet i till\u00eb i kombinuar?<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 merremi me k\u00ebt\u00eb.<\/p>\n<p>Fillimi \u00ebsht\u00eb standard: krijohet nj\u00eb skedar backup dhe menj\u00ebher\u00eb kopjohet. Shkruhet nj\u00eb inkrement dhe gjithashtu kopjohet. Kjo ndodh deri n\u00eb momentin kur kuptojm\u00eb se skedar\u00ebt kan\u00eb dal\u00eb nga dritarja jon\u00eb operacionale dhe ka nj\u00eb zinxhir t\u00eb vulosur. N\u00eb k\u00ebt\u00eb moment, ne kryejm\u00eb operacionin e dehidrimit dhe z\u00ebvend\u00ebsojm\u00eb k\u00ebta skedar\u00eb me zbraz\u00ebt. Natyrisht, nuk kopjojm\u00eb p\u00ebrs\u00ebri asgj\u00eb n\u00eb kapacitetin e tir.<\/p>\n<p>P\u00ebr gjith\u00eb k\u00ebt\u00eb logjik\u00eb emocionuese p\u00ebrgjigjen vet\u00ebm nj\u00eb shenj\u00eb n\u00eb nd\u00ebrfaqe: Copy backups to object storage as soon as they are created.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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>Por pse na nevojitet ky modalitet Kopjimi? <\/h3>\n<p>\nMadje \u00ebsht\u00eb m\u00eb mir\u00eb ta riformulojm\u00eb pyetjen k\u00ebshtu \u2014 nga cilat rreziqe po na mbrojn\u00eb me ndihm\u00ebn e tij? \u00c7far\u00eb problemi na ndihmon t\u00eb zgjidhim?<\/p>\n<p>P\u00ebrgjigjja \u00ebsht\u00eb e qart\u00eb: sigurisht, \u00ebsht\u00eb rikuperimi i t\u00eb dh\u00ebnave. N\u00ebse n\u00eb object storage kemi nj\u00eb kopje t\u00eb plot\u00eb t\u00eb t\u00eb dh\u00ebnave lokale, nuk ka r\u00ebnd\u00ebsi se \u00e7far\u00eb ndodh me prodhimin ton\u00eb, ne gjithmon\u00eb mund t\u00eb rikuperojm\u00eb t\u00eb dh\u00ebnat nga skedar\u00ebt q\u00eb ndodhen n\u00eb nj\u00eb Amazon t\u00eb kushtuar.<\/p>\n<p>Prandaj, le t\u00eb shqyrtojm\u00eb skenar\u00ebt e mundsh\u00ebm, nga m\u00eb t\u00eb thjesht\u00ebt deri te m\u00eb t\u00eb nd\u00ebrlikuarit.<\/p>\n<p>Shtypja m\u00eb e thjesht\u00eb q\u00eb mund t\u00eb na bjer\u00eb \u00ebsht\u00eb pamund\u00ebsia e nj\u00ebrit nga skedar\u00ebt n\u00eb zinxhirin e backupeve.<\/p>\n<p>Nj\u00eb histori m\u00eb e trishtueshme \u2014 na \u00ebsht\u00eb thyer nj\u00eb nga ekstent\u00ebt e repository-t ton\u00eb SOBR.<\/p>\n<p>Akoma m\u00eb keq b\u00ebhet kur i gjith\u00eb repository SOBR b\u00ebhet i pamundur, por kapaciteti i tir vazhdon t\u00eb funksionoj\u00eb.<br \/>\nDhe gjith\u00e7ka \u00ebsht\u00eb shum\u00eb keq \u2014 \u00ebsht\u00eb kur serveri backup vdes dhe d\u00ebshira juaj e par\u00eb \u00ebsht\u00eb t\u00eb provoni t\u00eb arrini kufirin e Kanadas\u00eb brenda dhjet\u00eb minutash.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 \/>\nDhe tani le t\u00eb shqyrtojm\u00eb \u00e7do situat\u00eb ve\u00e7mas.<\/p>\n<p>Kur ne humb\u00ebm nj\u00eb (po le t\u00eb jet\u00eb, madje disa) skedar\u00eb backup, na mjafton t\u00eb fillojm\u00eb procesin e skanimit t\u00eb magazin\u00ebs, dhe skedari i humbur do t\u00eb z\u00ebvend\u00ebsohet me nj\u00eb skedar t\u00eb zbraz\u00ebt. Dhe me ndihm\u00ebn e procesit t\u00eb rigjenerimit (p\u00ebr t\u00eb cilin u fol n\u00eb fillim t\u00eb artikullit), p\u00ebrdoruesi do t\u00eb jet\u00eb n\u00eb gjendje t\u00eb shkarkoj\u00eb t\u00eb dh\u00ebnat nga kapaciteti i pirgusit n\u00eb magazin\u00ebn lokale.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 m\u00eb e komplikuar. Supozojm\u00eb se SOBR-i yn\u00eb p\u00ebrb\u00ebhet nga dy ekstensione q\u00eb punojn\u00eb n\u00eb modin Performance, dhe k\u00ebshtu, .vbk dhe .vib jan\u00eb shp\u00ebrndar\u00eb mbi to n\u00eb nj\u00eb shtres\u00eb mjaft t\u00eb paekuilibruar. Dhe n\u00eb nj\u00eb moment, nj\u00eb nga ekstensat b\u00ebhet i paaksesuesh\u00ebm, dhe p\u00ebrdoruesit i nevojitet urgjentisht t\u00eb rikthej\u00eb makin\u00ebn, nj\u00eb pjes\u00eb t\u00eb t\u00eb dh\u00ebnave t\u00eb s\u00eb cil\u00ebs q\u00ebndron pik\u00ebrisht n\u00eb k\u00ebt\u00eb ekstens. <\/p>\n<p>P\u00ebrdoruesi fillon wizard-in e rikthimit, zgjedh pik\u00ebn n\u00eb t\u00eb cil\u00ebn d\u00ebshiron t\u00eb rikthej\u00eb, nd\u00ebrsa wizard-i gjat\u00eb procesit arrin n\u00eb p\u00ebrfundimin se nuk ka t\u00eb dh\u00ebna t\u00eb nevojshme p\u00ebr rikthim lokal, dhe prandaj ato duhet shkarkuar nga kapaciteti i pirgusit. N\u00eb k\u00ebt\u00eb rast, blloqet q\u00eb mbeten n\u00eb magazin\u00ebn lokale nuk do t\u00eb shkarkohen nga re. Fal\u00eb indeksit t\u00eb rikthimit (po, p\u00ebr t\u00eb u fol gjithashtu n\u00eb fillim t\u00eb artikullit).<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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\u00ebnvariant i k\u00ebtij rasti \u00ebsht\u00eb q\u00eb e gjith\u00eb magazina SOBR b\u00ebhet e paaksesueshme. N\u00eb k\u00ebt\u00eb rast, nuk kemi \u00e7far\u00eb t\u00eb kopjojm\u00eb nga magazinat lokale, dhe t\u00eb gjith\u00eb blloqet shkarkohen nga re.<\/p>\n<p>Dhe situata m\u00eb interesante \u00ebsht\u00eb kur serveri i backup-it vdes. K\u00ebtu ka dy mund\u00ebsi: admini \u00ebsht\u00eb i shk\u00eblqyer dhe ka b\u00ebr\u00eb backup dhe admini \u00ebsht\u00eb nj\u00eb Pinokio i keq q\u00eb nuk ka b\u00ebr\u00eb nj\u00eb backup t\u00eb konfigurimit.<\/p>\n<p>N\u00eb rastin e par\u00eb, mjafton q\u00eb ai t\u00eb shp\u00ebrndaj\u00eb diku nj\u00eb instalim t\u00eb past\u00ebr t\u00eb VBR dhe t\u00eb rikthej\u00eb baz\u00ebn e tij nga backup-i me mjetet standarde. N\u00eb p\u00ebrfundim t\u00eb k\u00ebtij procesi, gjith\u00e7ka do t\u00eb kthehet n\u00eb normalitet. Ose do t\u00eb rikthehet sipas nj\u00eb nga skenar\u00ebt e m\u00ebsip\u00ebrm.<\/p>\n<p>Por \u00e7far\u00ebdo admini, ose n\u00ebse ai vet\u00eb \u00ebsht\u00eb armiku i tij, ose n\u00ebse backup-i i konfiguracionit p\u00ebrjetoi nj\u00eb d\u00ebshtim legjendar, ne nuk do ta l\u00ebm\u00eb at\u00eb n\u00eb m\u00ebshir\u00ebn e fatit. P\u00ebr k\u00ebt\u00eb rast, ne kemi futur nj\u00eb procedur\u00eb t\u00eb re, e cila quhet Import Object Storage. Kjo lejon t\u00eb anashkalojm\u00eb procesin e rikrijimit manual t\u00eb repozitorit SOBR dhe lidhjen e kapacitetit me nj\u00eb skaner t\u00eb m\u00ebvonsh\u00ebm; thjesht duhet t\u00eb shtojm\u00eb objektin e ruajtjes n\u00eb nd\u00ebrfaqen e vima dhe t\u00eb nisemi me procedur\u00ebn Import Storage Repository. E vetmja gj\u00eb q\u00eb mund t\u00eb q\u00ebndroj\u00eb mes jush dhe backup-it tuaj \u00ebsht\u00eb k\u00ebrkesa p\u00ebr t\u00eb futur nj\u00eb fjal\u00ebkalim, n\u00ebse backup-et tuaja ishin t\u00eb kriptuara.<\/p>\n<p>K\u00ebtu p\u00ebr Copy Mode, mendoj se kemi p\u00ebrfunduar, dhe ne kalojm\u00eb n\u00eb<\/p>\n<h3>Sealed Mode<\/h3>\n<p>\nKoncepci kryesore \u00ebsht\u00eb q\u00eb n\u00eb ekstensin e zgjedhur t\u00eb repozitorit SOBR nuk mund t\u00eb shfaqen backup-e t\u00eb reja. Para versionit v10, ne kishim vet\u00ebm Modalitetin e Mir\u00ebmbajtjes, ku ndalohej plot\u00ebsisht \u00e7do pun\u00eb me repozitorin. Nj\u00eb lloj rrethi ekstrem t\u00eb pun\u00ebs jasht\u00eb p\u00ebrdorimit, ku vet\u00ebm butoni Evacuate ishte i disponuesh\u00ebm, duke t\u00ebrhequr backup-et n\u00eb nj\u00eb ekstens tjet\u00ebr nj\u00eb her\u00eb.<\/p>\n<p>Modaliteti i Pezulluar \u00ebsht\u00eb nj\u00eb version 'm\u00eb t\u00eb but\u00eb': ndalojm\u00eb krijimin e backup-eve t\u00eb reja dhe gradualisht fshijm\u00eb ato t\u00eb vjetra sipas ruajtjes s\u00eb zgjedhur, por n\u00eb proces nuk humbasim mund\u00ebsin\u00eb p\u00ebr t'u rikuperuar nga piketat e ruajtura. Nj\u00eb gj\u00eb shum\u00eb e dobishme kur na duhen ose po i skadon afati i 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, dhe nuk kemi vend p\u00ebr ta transferuar gjith\u00e7ka nj\u00ebher\u00ebsh. Ose nuk \u00ebsht\u00eb e mundur ta fshijm\u00eb. <\/p>\n<p>Prandaj, parimi i funksionimit \u00ebsht\u00eb mjaft i thjesht\u00eb: duhet t\u00eb ndaloni t\u00eb gjitha operacionet shkruese (shfaqjen e t\u00eb dh\u00ebnave t\u00eb reja), duke l\u00ebn\u00eb ato lexuese (rikuperimet) dhe fshir\u00ebse (ruajtjen).<\/p>\n<p>T\u00eb dy modet mund t\u00eb p\u00ebrdoren nj\u00ebkoh\u00ebsisht, por duhet t\u00eb kemi parasysh se Modaliteti i Mir\u00ebmbajtjes ka p\u00ebrpar\u00ebsi m\u00eb t\u00eb lart\u00eb.<\/p>\n<p>Si nj\u00eb shembull, le t\u00eb marrim nj\u00eb SOBR, i p\u00ebrb\u00ebr\u00eb nga dy ekstens. Supozoni se p\u00ebr kat\u00ebr dit\u00ebt e para kemi krijuar backup-e n\u00eb modalitetin Forward Forever Incremental, dhe pastaj ne pezullojm\u00eb ekstensin. Kjo \u00e7on n\u00eb faktin se ne iniciativisht krijojm\u00eb nj\u00eb aktiv t\u00eb plot\u00eb n\u00eb ekstensin e dyt\u00eb t\u00eb disponuesh\u00ebm. N\u00ebse ruajtja jon\u00eb \u00ebsht\u00eb kat\u00ebr, at\u00ebher\u00eb kur e gjith\u00eb zinxhiri, q\u00eb ndodhet n\u00eb ekstensin e pezulluar, kalon p\u00ebrtej kufijve t\u00eb tij, ai fshihet pa ndonj\u00eb ndjenj\u00eb faji.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 ndodh n\u00eb Forward incremental me fulle periodike. N\u00ebse dy dit\u00ebt e para kemi krijuar backup-e t\u00eb plota, dhe t\u00eb enjten vendosim t\u00eb mbyllim repositorin, at\u00ebher\u00eb t\u00eb premten, kur t\u00eb krijohet nj\u00eb backup i ri, file p\u00ebr t\u00eb h\u00ebn\u00ebn do t\u00eb fshihet sepse 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 ekstensin\u00eb e disponueshme dhe fshijm\u00eb tre t\u00eb tjera t\u00eb mbetura, t\u00eb cilat nuk mund t\u00eb fshihen ndaras nga nj\u00ebra-tjetra.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 \/>\n\u00cbsht\u00eb m\u00eb e thjesht\u00eb me Reverse Incremental. N\u00eb t\u00eb, pikat m\u00eb t\u00eb vjetra nuk varen nga asgj\u00eb dhe mund t\u00eb fshihen pa ndonj\u00eb problem. Prandaj, sa her\u00eb q\u00eb krijohet nj\u00eb .vbk e re n\u00eb nj\u00eb ekstension t\u00eb ri, t\u00eb vjetrat .vrb do t\u00eb fshihen nj\u00eb nga nj\u00eb.<\/p>\n<p>Sidoqoft\u00eb, pse ne \u00e7do her\u00eb krijojm\u00eb nj\u00eb .vbk t\u00eb ri: n\u00ebse nuk do ta krijonim at\u00eb dhe do t\u00eb vazhdonim me zinxhirin e vjet\u00ebr t\u00eb inkrement\u00ebve, at\u00ebher\u00eb e vjetra .vbk do t\u00eb ngej n\u00eb m\u00ebnyr\u00eb t\u00eb pafund n\u00eb \u00e7do mod, duke penguar fshirjen e saj. Prandaj, u mor vendimi q\u00eb sa her\u00eb q\u00eb mbyllet ekstensioni, krijojm\u00eb nj\u00eb backup t\u00eb plot\u00eb n\u00eb ekstensionin e lir\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 \/>\n\u00cbsht\u00eb m\u00eb e komplikuar me kapacitetin e tier-it. <\/p>\n<p>Fillimisht, le t\u00eb shqyrtojm\u00eb modin copy. Supozoni se gjat\u00eb kat\u00ebr dit\u00ebve kemi krijuar backup-e aktive, dhe pastaj kapaciteti i tier-it \u00ebsht\u00eb mbyllur. Ne nuk fshijm\u00eb asgj\u00eb, por durim q\u00ebndrojm\u00eb me ruajtjen, dhe pas k\u00ebsaj fshijm\u00eb t\u00eb dh\u00ebnat nga kapaciteti i tier-it.<\/p>\n<p>P\u00ebrgjith\u00ebsisht, e nj\u00ebjta gj\u00eb ndodh edhe me modin move \u2014 presim ruajtjen, fshijm\u00eb t\u00eb vjetrat n\u00eb ruajtjen lokale, dhe fshijm\u00eb ato q\u00eb ruhen n\u00eb object storage.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 \u00ebsht\u00eb me Forever forward incremental. Vendosim ruajtjen n\u00eb tre pika dhe fillojm\u00eb t\u00eb h\u00ebn\u00ebn duke b\u00ebr\u00eb backup-e, t\u00eb cilat kopjohen sakt\u00ebsisht n\u00eb cloud. Pas mbylljes s\u00eb ruajtjes, backup-et vazhdojn\u00eb t\u00eb krijohen, duke mbajtur tre pika, por t\u00eb dh\u00ebnat q\u00eb ruhen n\u00eb kapacitetin e tier-it mbeten t\u00eb vare nga nj\u00ebra-tjetra dhe nuk mund t\u00eb fshihen. Prandaj, presim t\u00eb enjten, kur .vbk jon\u00eb kalon jasht\u00eb kufijve t\u00eb ruajtjes dhe vet\u00ebm at\u00ebher\u00eb fshijm\u00eb t\u00eb gjith\u00eb zinxhirin e ruajtur.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 sh\u00ebnim i vog\u00ebl: t\u00eb gjitha shembujt k\u00ebtu jan\u00eb t\u00eb ilustruar me nj\u00eb makin\u00eb. N\u00ebse keni m\u00eb shum\u00eb makineri n\u00eb backup, ruajtja e tyre do t\u00eb ndryshoj\u00eb n\u00eb var\u00ebsi t\u00eb faktit n\u00ebse \u00ebsht\u00eb b\u00ebr\u00eb Active Full apo jo.<\/p>\n<p>K\u00ebshtu q\u00eb, n\u00eb principe, kjo \u00ebsht\u00eb e gjitha. Prandaj, kalojm\u00eb te karakteristika m\u00eb e fort\u00eb \u2014 <\/p>\n<h3>Immutability <\/h3>\n<p>\nSi me parazgjuar me pikat e m\u00ebparshme, fillimisht flasim p\u00ebr problemin q\u00eb zgjidh kjo funksionalitet. Sapo transferojm\u00eb backupet tona p\u00ebr ruajtje diku, ndjehet nj\u00eb d\u00ebshir\u00eb e madhe p\u00ebr t\u00eb garantuar ruajtjen e tyre, dometh\u00ebn\u00eb p\u00ebr t\u00eb ndaluar fizikisht fshirjen e tyre dhe \u00e7do modifikim gjat\u00eb periudh\u00ebs s\u00eb caktuar t\u00eb ruajtjes. Edhe nga administrator\u00ebt, madje edhe nga llogarit\u00eb e tyre t\u00eb adminit. Kjo ndihmon n\u00eb mbrojtjen e tyre nga d\u00ebmshm\u00ebria e rast\u00ebsishme apo e q\u00ebllimshme. Ata q\u00eb punojn\u00eb me AWS, mund t\u00eb ken\u00eb hasur nj\u00eb funksionalitet t\u00eb till\u00eb n\u00ebn emrin Object Lock.<\/p>\n<p>Tani le t\u00eb shohim modin n\u00eb m\u00ebnyr\u00eb t\u00eb p\u00ebrgjithshme, pastaj do t\u00eb thellohemi 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 backupi p\u00ebrfshin modin Copy.<\/p>\n<p>Immutability nuk nd\u00ebrvepron asnj\u00ebher\u00eb me ruajtjen e p\u00ebrgjithshme. P\u00ebr shembull, nuk shton pika t\u00eb tjera apo di\u00e7ka t\u00eb till\u00eb. Thjesht gjat\u00eb kat\u00ebr dit\u00ebve, personi nuk mund t\u00eb fshij\u00eb skedar\u00ebt e backupit. N\u00ebse b\u00ebhet nj\u00eb backup t\u00eb h\u00ebn\u00ebn, at\u00ebher\u00eb skedari i tij mund t\u00eb fshihet vet\u00ebm t\u00eb premten.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 m\u00ebparshme t\u00eb dehidratimit, indekseve dhe metad\u00ebnave vazhdojn\u00eb t\u00eb funksionojn\u00eb nj\u00ebsoj. Por me nj\u00eb kushtrim \u2014 blloku vendoset jo vet\u00ebm p\u00ebr t\u00eb dh\u00ebnat, por edhe p\u00ebr metad\u00ebnat. Kjo \u00ebsht\u00eb b\u00ebr\u00eb n\u00eb rast se nj\u00eb keqb\u00ebr\u00ebs dinak vendos t\u00eb fshij\u00eb baz\u00ebn ton\u00eb t\u00eb metad\u00ebnave dhe q\u00eb blloqet me t\u00eb dh\u00ebna t\u00eb mos shnd\u00ebrrohen n\u00eb nj\u00eb grumbull binar t\u00eb padobish\u00ebm.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 nj\u00eb moment i shk\u00eblqyer p\u00ebr t\u00eb shpjeguar teknologjin\u00eb ton\u00eb t\u00eb gjenerimit t\u00eb bllok\u00ebve. Ose gjenerimi i bllok\u00ebve. P\u00ebr k\u00ebt\u00eb, le t\u00eb shqyrtojm\u00eb situat\u00ebn q\u00eb \u00e7oi n\u00eb shfaqjen e saj.<\/p>\n<p>Marrim nj\u00eb lini kohore prej gjasht\u00eb dit\u00ebsh dhe nga posht\u00eb do t\u00eb sh\u00ebnojm\u00eb koh\u00ebn e pritur p\u00ebr skadimin e immutability. Marrim dhe krijojm\u00eb n\u00eb dit\u00ebn e par\u00eb nj\u00eb skedar, i p\u00ebrb\u00ebr\u00eb nga blloku a dhe metadatate e tij. N\u00ebse immutability \u00ebsht\u00eb vendosur p\u00ebr tre dit\u00eb, \u00ebsht\u00eb logjike t\u00eb supozojm\u00eb se n\u00eb dit\u00ebn e kat\u00ebrt t\u00eb dh\u00ebnat do t\u00eb \u00e7bllokohen dhe do t\u00eb fshihen. N\u00eb dit\u00ebn e dyt\u00eb do t\u00eb shtojm\u00eb nj\u00eb skedar t\u00eb ri file2, i p\u00ebrb\u00ebr\u00eb nga blloku b me t\u00eb nj\u00ebjtat konfigurime. Blloku a ende duhet t\u00eb fshihet n\u00eb dit\u00ebn e kat\u00ebrt. Por n\u00eb dit\u00ebn e tret\u00eb ndodh di\u00e7ka e frikshme \u2014 krijohet skedari File3, i p\u00ebrb\u00ebr\u00eb nga blloku i ri d dhe nj\u00eb referenc\u00eb n\u00eb bllokun e vjet\u00ebr a. Kjo do t\u00eb thot\u00eb se p\u00ebr bllokun a flamuri i immutability duhet t\u00eb rikonfirmohet p\u00ebr nj\u00eb afat t\u00eb ri, i cili shtyhet p\u00ebr n\u00eb dit\u00ebn e gjasht\u00eb. Dhe k\u00ebtu shfaqet problemi \u2014 n\u00eb backup-et reale t\u00eb k\u00ebtyre bllok\u00ebve krijohet nj\u00eb num\u00ebr i madh. Dhe p\u00ebr t\u00eb zgjatur periudh\u00ebn e immutability, duhet t\u00eb kryhen nj\u00eb sasi e madhe k\u00ebrkesash \u00e7do her\u00eb. Dhe n\u00eb fakt, kjo do t\u00eb jet\u00eb nj\u00eb proces praktikisht i pafund\u00ebm \u00e7do dit\u00eb, sepse me probabilitet t\u00eb lart\u00eb, ne do t\u00eb gjejm\u00eb grumbuj t\u00eb m\u00ebdhenj t\u00eb bllok\u00ebve t\u00eb deduplication n\u00eb \u00e7do kopjim. Dhe \u00e7far\u00eb do t\u00eb thot\u00eb nj\u00eb num\u00ebr i madh k\u00ebrkesh ndaj ofruesve t\u00eb objekteve t\u00eb ruajtjes? Sakrifikim! Nj\u00eb fatur\u00eb e madhe n\u00eb fund t\u00eb muajit.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 r\u00ebnduar klient\u00ebt tan\u00eb t\u00eb dashur me shifra t\u00eb larta p\u00ebr di\u00e7ka q\u00eb ndodh pa arsye, u shpik mekanizmi i gjenerimit t\u00eb bllok\u00ebve. Ky \u00ebsht\u00eb nj\u00eb periudh\u00eb shtes\u00eb q\u00eb ne e shtojm\u00eb n\u00eb periudh\u00ebn e vendosur t\u00eb immutability. N\u00eb shembullin m\u00eb posht\u00eb, kjo periudh\u00eb \u00ebsht\u00eb dy dit\u00eb. Por kjo \u00ebsht\u00eb vet\u00ebm p\u00ebr shembull. N\u00eb realitet, aty p\u00ebrdoret nj\u00eb formul\u00eb e vetme, e cila ofron p\u00ebraf\u00ebrsisht dhjet\u00eb dit\u00eb shtes\u00eb p\u00ebr nj\u00eb bllokim mujor. <\/p>\n<p>Do vazhdojm\u00eb t\u00eb shqyrtojm\u00eb t\u00eb nj\u00ebjt\u00ebn situat\u00eb, por tani me gjenerimin e bllokut. Krijojm\u00eb n\u00eb dit\u00ebn e par\u00eb file1 nga blloku a dhe t\u00eb dh\u00ebnat metadatatike. Kemi grumbulluar periudh\u00ebn e gjenerimit dhe immutability - do t\u00eb thot\u00eb, 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 lidhja me bllokun a, asgj\u00eb nuk ndodh me dat\u00ebn e parashikuar t\u00eb fshirjes. Ajo mbetet e pandryshuar n\u00eb dit\u00ebn e gjasht\u00eb. K\u00ebshtu, ne po p\u00ebrpiqemi t\u00eb kursejm\u00eb para n\u00eb numrin e k\u00ebrkesave. Situata e vetme kur afati mund t\u00eb shtyhet \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 lidhje me bllokun a, do t\u00eb shtohet gjenerimi 2 pasi Gen1 ka skaduar. Dhe data e pritur e fshirjes s\u00eb bllokut a do t\u00eb zhvendoset n\u00eb dit\u00ebn e tet\u00eb. Kjo na lejon t\u00eb reduktojm\u00eb dramatikisht numrin e k\u00ebrkesave p\u00ebr t\u00eb zgjasur jet\u00ebn e blloqeve t\u00eb deduplikuara, q\u00eb kursen shum\u00eb para p\u00ebr klient\u00ebt.<\/p>\n<p><img decoding=\"async\" alt=\"\u00c7far\u00eb ndryshoi 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 \/>\nP\u00ebrgjith\u00ebsisht, teknologjia \u00ebsht\u00eb e disponueshme p\u00ebr p\u00ebrdoruesit e S3 dhe pajisjeve t\u00eb nd\u00ebrlidhura me S3, prodhuesit e t\u00eb cilave garantojn\u00eb q\u00eb implementimi i tyre nuk ndryshon nga ai i Amazon. K\u00ebtu vjen p\u00ebrgjigjja p\u00ebr pyetjen legjitime, pse Azure nuk mb\u00ebshtetet - ata kan\u00eb nj\u00eb ve\u00e7ori t\u00eb ngjashme, por ajo funksionon n\u00eb nivelin e kontejner\u00ebve dhe jo t\u00eb objekteve individuale. P\u00ebr m\u00eb tep\u00ebr, n\u00eb Amazon ka dy m\u00ebnyra p\u00ebr obiekt lok: compliance dhe governance. N\u00eb rastin e dyt\u00eb, ka mund\u00ebsi q\u00eb admini m\u00eb i fuqish\u00ebm mbi admin\u00ebt dhe super admini, pavar\u00ebsisht nga obiekt lok, t\u00eb fshij\u00eb t\u00eb dh\u00ebnat. N\u00eb rastin e compliance, gjith\u00e7ka \u00ebsht\u00eb ngjitur fort dhe askush nuk mund t\u00eb fshij\u00eb backup-et. Madje edhe admin\u00ebt e Amazon (sipas deklaratave t\u00eb tyre zyrtare). Ne mb\u00ebshtesim pik\u00ebrisht k\u00ebt\u00eb m\u00ebnyr\u00eb.<\/p>\n<p>\nDhe, tradicionalisht, disa lidhje t\u00eb dobishme:<\/p>\n<ul>\n<li>P\u00ebr <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/block_generation.html?ver=100\">Generimi i Bllokut<\/a><\/noindex> n\u00eb t\u00eb gjitha detajet.<\/li>\n<li>T\u00eb gjitha informacionet rreth <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/overview.html?ver=100\">Veeam Backup &amp; Replication 10<\/a><\/noindex> n\u00eb form\u00ebn m\u00eb t\u00eb mir\u00eb<\/li>\n<li>Q <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/capacity_tier.html?ver=100\">Capacity Tier<\/a><\/noindex> n\u00eb detaje<\/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 5.0.2 - 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.\" \/>\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) 5.0.2\" \/>\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.\" \/>\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":"Tara e Kapacitetit (ose si\u00e7 e quajm\u00eb ne n\u00eb brend\u00ebsi \u2014 kaptir) u shfaq q\u00eb n\u00eb koh\u00ebn e Veeam Backup and Replication 9.5 Update 4 me emrin Archive Tier.","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.","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","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"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}]}}