{"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\/cs\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10","title":{"rendered":"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Kapacitn\u00ed \u00farove\u0148 (nebo jak ji naz\u00fdv\u00e1me intern\u011b, kaptir) byla p\u0159edstavena ji\u017e v dob\u011b Veeam Backup and Replication 9.5 Update 4 pod n\u00e1zvem Archivn\u00ed \u00farove\u0148. Jej\u00edm c\u00edlem je umo\u017enit p\u0159esun z\u00e1loh, kter\u00e9 p\u0159ekro\u010dily takzvan\u00e9 okno pro obnovu, na objektov\u00e9 \u00falo\u017ei\u0161t\u011b. To pom\u00e1h\u00e1 uvolnit diskov\u00fd prostor u\u017eivatel\u016fm, kte\u0159\u00ed ho maj\u00ed nedostatek. Tato mo\u017enost se naz\u00fdv\u00e1 Move Mode.<\/p>\n<p>K proveden\u00ed t\u00e9to jednoduch\u00e9 (jak se zd\u00e1) akce sta\u010dilo splnit dv\u011b podm\u00ednky: v\u0161echny body z p\u0159esouvan\u00e9 z\u00e1lohy mus\u00ed b\u00fdt za hranicemi v\u00fd\u0161e zm\u00edn\u011bn\u00e9ho okna pro obnovu, kter\u00e9 je v UI explicitn\u011b nastaveno. A druh\u00e9: \u0159et\u011bzec mus\u00ed b\u00fdt v takzvan\u00e9m \u00abzap sealed\u00bb (sealed backup chain nebo Inactive Backup Chain). To znamen\u00e1, \u017ee v tomto \u0159et\u011bzci b\u011bhem \u010dasu nedoch\u00e1z\u00ed k \u017e\u00e1dn\u00fdm zm\u011bn\u00e1m.<\/p>\n<p>Ale ve VBR v10 byla koncepce dopln\u011bna o nov\u00e9 funkce - vznikl Copy Mode, Sealed Mode a mechanismus se slo\u017eit\u00fdm n\u00e1zvem Immutability.<\/p>\n<p>O t\u011bchto fascinuj\u00edc\u00edch v\u011bcech si dnes budeme pov\u00eddat. Nejprve o tom, jak to fungovalo ve VBR9.5u4, a pot\u00e9 o zm\u011bn\u00e1ch v des\u00e1t\u00e9 verzi.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/954adcc5592fe2a7ea64ec24b06ecc91.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA a\u0165 mi prominou zast\u00e1nci \u010dist\u00e9ho jazyka, ale p\u0159\u00edli\u0161 mnoho term\u00edn\u016f nen\u00ed mo\u017en\u00e9 p\u0159elo\u017eit.<br \/>\nTak\u017ee tady bude hromada anglicism\u016f.<br \/>\nA spousta gif\u016f. <br \/>\nA obr\u00e1zk\u016f.<\/p>\n<ul>\n<li>Bez jak\u00fdchkoliv v\u00fd\u010ditek. Autor \u010dl\u00e1nku.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>Jak bylo<\/h1>\n<p>\nTak co, za\u010dneme rozborem okna pro obnovu a sealed backup (nebo jak se v dokumentaci naz\u00fdv\u00e1 Inactive Backup Chain). Bez jejich pochopen\u00ed nelze pokra\u010dovat s dal\u0161\u00edm vysv\u011btlen\u00edm.<\/p>\n<p>Jak vid\u00edme na obr\u00e1zku, m\u00e1me n\u011bjak\u00fd z\u00e1lo\u017en\u00ed \u0159et\u011bzec s datov\u00fdmi bloky, kter\u00fd se nach\u00e1z\u00ed na Performance tier SOBR \u00falo\u017ei\u0161t\u011b, k n\u011bmu\u017e je p\u0159ipojen Kapacitn\u00ed Tier. Na\u0161e okno pro operativn\u00ed z\u00e1lohu \u010din\u00ed t\u0159i dny.<\/p>\n<p>P\u0159\u00edslu\u0161n\u011b, z\u00e1loha vytvo\u0159en\u00e1 v pond\u011bl\u00ed .vbk uzav\u00edr\u00e1 p\u0159edchoz\u00ed \u0159et\u011bzec, jeho\u017e okno je nastaveno na t\u0159i dny. A to znamen\u00e1, \u017ee lze bez obav za\u010d\u00edt p\u0159ev\u00e1\u017eet do kapacitn\u00ed \u00farovn\u011b v\u0161e, co je star\u0161\u00ed ne\u017e tyto t\u0159i dny.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/430f31d181bb79c2bd6001011511e3f9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAle co se p\u0159esn\u011b rozum\u00ed pod sealed \u0159et\u011bzcem a co mohlo b\u00fdt odesl\u00e1no do kapacitn\u00ed \u00farovn\u011b v update 4?<\/p>\n<p>Pro Forward Incremental je znakem uzav\u0159en\u00ed \u0159et\u011bzce vytvo\u0159en\u00ed nov\u00e9 pln\u00e9 z\u00e1lohy. A nez\u00e1le\u017e\u00ed na tom, jak je tato pln\u00e1 z\u00e1loha z\u00edsk\u00e1na: zahrnuj\u00ed se jak syntetick\u00e9 pln\u00e9, tak aktivn\u00ed pln\u00e9 z\u00e1lohy.<\/p>\n<p>V p\u0159\u00edpad\u011b Reverse to jsou v\u0161echny soubory, kter\u00e9 nepat\u0159\u00ed do opera\u010dn\u00edho okna. <\/p>\n<p>V p\u0159\u00edpad\u011b Forward increment s roll-backy se v\u0161echny roll-backy a .vbk, pokud na performance extentu existuje dal\u0161\u00ed .vbk<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/4cb6f168862acabadbdab771cc48fe7f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNyn\u00ed se pod\u00edvejme na variantu pr\u00e1ce se skupinami Backup Copy. Zde se ukl\u00e1dalo pouze to, co spadalo pod GFS retenci. Proto\u017ee v\u0161echno, co je ulo\u017eeno v nov\u011bj\u0161\u00edch skupin\u00e1ch backup copy, m\u016f\u017ee b\u00fdt jak\u00fdmkoliv zp\u016fsobem zm\u011bn\u011bno.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/4c263058110b7c502501f01940977f1a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNyn\u00ed nahl\u00e9dneme pod pokli\u010dku. Prob\u00edh\u00e1 zde proces zvan\u00fd dehydratace \u2014 ponech\u00e1n\u00ed pr\u00e1zdn\u00fdch z\u00e1lo\u017en\u00edch soubor\u016f na extentu a p\u0159esouv\u00e1n\u00ed blok\u016f z t\u011bchto soubor\u016f do kapacitn\u00edho tieru. Pro optimalizaci tohoto procesu se pou\u017e\u00edv\u00e1 takzvan\u00fd index dehydratace, kter\u00fd umo\u017e\u0148uje nekop\u00edrovat bloky, kter\u00e9 ji\u017e byly zkop\u00edrov\u00e1ny do kapacitn\u00edho tieru. <\/p>\n<p>Pod\u00edvejme se, jak to vypad\u00e1 na p\u0159\u00edkladu: p\u0159edpokl\u00e1dejme, \u017ee m\u00e1me .vbk, kter\u00fd vy\u0161el z provozn\u00edho okna a pat\u0159\u00ed uzav\u0159en\u00e9 skupin\u011b. To znamen\u00e1, \u017ee m\u00e1me pln\u00e9 pr\u00e1vo p\u0159esunout ho do kapacitn\u00edho tieru. V okam\u017eiku p\u0159esunu se vytv\u00e1\u0159\u00ed soubor metadat v kapacitn\u00edm tieru a bloky p\u0159ev\u00e1\u017een\u00e9ho souboru. V souboru metadat na \u00farovni odkaz\u016f je pops\u00e1no, z jak\u00fdch blok\u016f se n\u00e1\u0161 soubor skl\u00e1d\u00e1. Na obr\u00e1zku se n\u00e1\u0161 prvn\u00ed soubor skl\u00e1d\u00e1 z blok\u016f a, b, c a v metadatech jsou um\u00edst\u011bny odkazy na tyto bloky. Kdy\u017e m\u00e1me druh\u00fd .vbk soubor, p\u0159ipraven\u00fd k p\u0159esunu a skl\u00e1daj\u00edc\u00ed se z blok\u016f a, b a d, analyzujeme index dehydratace a ch\u00e1peme, \u017ee je pot\u0159eba p\u0159esunout pouze blok d. A jeho soubor metadat bude obsahovat odkazy na dva p\u0159edchoz\u00ed bloky a jeden nov\u00fd.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/5c502030b8727ecd85c5229df1761c85.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nProces zp\u011btn\u00e9ho dopln\u011bn\u00ed t\u011bchto pr\u00e1zdnot daty se naz\u00fdv\u00e1 rehydratace. Zde se u\u017e pou\u017e\u00edv\u00e1 vlastn\u00ed index rehydratace, kter\u00fd se op\u00edr\u00e1 o nejstar\u0161\u00ed .vbk soubor na m\u00edstn\u00edm performance extentu. To znamen\u00e1, \u017ee pokud u\u017eivatel chce vr\u00e1tit soubor z kapacitn\u00edho tieru, nejprve vytvo\u0159\u00edme index blok\u016f nejstar\u0161\u00edho pln\u00e9ho z\u00e1lohy a p\u0159esuneme z kapacitn\u00edho tieru pouze chyb\u011bj\u00edc\u00ed bloky. V p\u0159\u00edpad\u011b zn\u00e1zorn\u011bn\u00e9m na obr\u00e1zku, abychom rehydratovali FullBackup1.vbk podle indexu rehydratace, n\u00e1m chyb\u00ed pouze blok C, kter\u00fd vezmeme z kapacitn\u00edho tieru. Pokud jako kapacitn\u00ed tier slou\u017e\u00ed cloudov\u00e9 objektov\u00e9 \u00falo\u017ei\u0161t\u011b, umo\u017e\u0148uje to u\u0161et\u0159it obrovsk\u00e9 pen\u00edze.<\/p>\n<p>Zde se m\u016f\u017ee zd\u00e1t, \u017ee tato technologie je identick\u00e1 s tou, kter\u00e1 se pou\u017e\u00edv\u00e1 v WAN akceler\u00e1torech, ale to je jen dojem. V akceler\u00e1torech se prov\u00e1d\u00ed glob\u00e1ln\u00ed deduplikace, zat\u00edmco zde se pou\u017e\u00edv\u00e1 lok\u00e1ln\u00ed deduplikace pro ka\u017ed\u00fd soubor na ur\u010dit\u00e9m offsetu. To je zp\u016fsobeno rozd\u00edlnost\u00ed \u00fakol\u016f, kter\u00e9 je t\u0159eba \u0159e\u0161it: zde pot\u0159ebujeme kop\u00edrovat velk\u00e9 soubory pln\u00fdch z\u00e1loh, a podle na\u0161ich v\u00fdzkum\u016f i kdy\u017e mezi nimi uplyne del\u0161\u00ed \u010dasov\u00fd \u00fasek, takov\u00fd deduplika\u010dn\u00ed algoritmus d\u00e1v\u00e1 lep\u0161\u00ed v\u00fdsledek.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/1db1a696e289187ae02bd84d9edd6f66.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAle v\u00edc index\u016f bohu index\u016f! Existuje tak\u00e9 index pro obnovu dat! Kdy\u017e spust\u00edme obnovu stroje um\u00edst\u011bn\u00e9ho v kapacitn\u00edm tieru, \u010dteme pouze jedine\u010dn\u00e9 bloky dat, kter\u00e9 nejsou v performance tieru.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/257593c39e63bfb6f7e13d228bcebbae.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h1>Jak to bylo<\/h1>\n<p>\nNa tomto \u00favodn\u00edm \u010d\u00e1sti je v\u0161e. Je docela podrobn\u00e1, ale jak bylo zm\u00edn\u011bno v\u00fd\u0161e, bez t\u011bchto podrobnost\u00ed nebude mo\u017en\u00e9 vysv\u011btlit, jak nov\u00e9 funkce funguj\u00ed. Proto bez zbyte\u010dn\u00fdch p\u0159edmluv p\u0159ejd\u011bme k prvn\u00edmu.<\/p>\n<h3>Re\u017eim kop\u00edrov\u00e1n\u00ed<\/h3>\n<p>\nZna\u010dn\u011b se zakl\u00e1d\u00e1 na existuj\u00edc\u00edch technologi\u00edch, nicm\u00e9n\u011b nese zcela jinou logiku vyu\u017eit\u00ed.\u00a0<\/p>\n<p>C\u00edlem tohoto re\u017eimu je zajistit, \u017ee v\u0161echna data um\u00edst\u011bn\u00e1 na lok\u00e1ln\u00edm extentu maj\u00ed kopii v kapacitn\u00edm tieru.<\/p>\n<p>Pokud porovn\u00e1me re\u017eimy Move a Copy p\u0159\u00edmo, dopadne to takto:<\/p>\n<ul>\n<li>P\u0159esouvat lze pouze zape\u010det\u011bn\u00fd \u0159et\u011bzec. V p\u0159\u00edpad\u011b re\u017eimu kop\u00edrov\u00e1n\u00ed se d\u00e1vaj\u00ed v\u0161echny, bez ohledu na to, co se d\u011bje v z\u00e1lo\u017en\u00ed \u00faloze.<\/li>\n<li>P\u0159esun se aktivuje, kdy\u017e soubory p\u0159ekro\u010d\u00ed hranice okna provozn\u00ed z\u00e1lohy, zat\u00edmco kop\u00edrov\u00e1n\u00ed se aktivuje ihned, jakmile se objev\u00ed z\u00e1lo\u017en\u00ed soubor.<\/li>\n<li>Sledov\u00e1n\u00ed nov\u00fdch dat pro kop\u00edrov\u00e1n\u00ed prob\u00edh\u00e1 neust\u00e1le, zat\u00edmco pro p\u0159esun se aktivovalo ka\u017ed\u00e9 4 hodiny.<\/li>\n<\/ul>\n<p>\nP\u0159i zva\u017eov\u00e1n\u00ed nov\u00e9ho re\u017eimu navrhuji j\u00edt od jednoduch\u00fdch p\u0159\u00edklad\u016f ke slo\u017eit\u011bj\u0161\u00edm.<\/p>\n<p>V tom nejban\u00e1ln\u011bj\u0161\u00edm p\u0159\u00edpad\u011b se n\u00e1m jednodu\u0161e objevuj\u00ed nov\u00e9 soubory s inkrementy a my je prost\u011b kop\u00edrujeme do kapacitn\u00edho tieru. Bez ohledu na to, jak\u00fd re\u017eim se pou\u017e\u00edv\u00e1 v z\u00e1lo\u017en\u00ed \u00faloze, bez ohledu na to, zda pat\u0159\u00ed k zape\u010det\u011bn\u00e9 \u010d\u00e1sti \u0159et\u011bzce nebo ne, bez ohledu na to, zda uplynulo na\u0161e provozn\u00ed okno. Jednodu\u0161e jsme vzali a zkop\u00edrovali.<\/p>\n<p>Proces za t\u00edmto je st\u00e1le dehydratace ve form\u011b, jak bylo pops\u00e1no v\u00fd\u0161e. V re\u017eimu kop\u00edrov\u00e1n\u00ed tak\u00e9 sleduje, aby nedoch\u00e1zelo ke kop\u00edrov\u00e1n\u00ed blok\u016f, kter\u00e9 ji\u017e existuj\u00ed v na\u0161em objektov\u00e9m \u00falo\u017ei\u0161ti. Jedin\u00fd rozd\u00edl je ten, \u017ee pokud v re\u017eimu p\u0159esunu jsme nahrazovali skute\u010dn\u00e9 soubory pr\u00e1zdn\u00fdmi soubory, zde je ani nijak nezasahujeme a nech\u00e1v\u00e1me v\u0161e tak, jak je. Jinak je to st\u00e1le stejn\u00fd index dehydratace, kter\u00fd pe\u010dliv\u011b usiluje o \u00fasporu va\u0161ich pen\u011bz a \u010dasu.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/b3a033f4a0d0cbce8cecee152660c67c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nObjevuje se ot\u00e1zka \u2013 pokud se pod\u00edv\u00e1me na UI, existuje mo\u017enost vybrat ob\u011b mo\u017enosti najednou. Jak bude fungovat tento kombinovan\u00fd re\u017eim?<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/12f658765a05e120dc5068920886edb5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPoj\u010fme se na to pod\u00edvat.<\/p>\n<p>Za\u010d\u00e1tek je standardn\u00ed: vytvo\u0159\u00ed se z\u00e1lo\u017en\u00ed soubor a okam\u017eit\u011b zkop\u00edruje. K n\u011bmu se vytvo\u0159\u00ed inkrement a tak\u00e9 se zkop\u00edruje. To se d\u011bje a\u017e do okam\u017eiku, kdy pochop\u00edme, \u017ee soubory vypadly z na\u0161eho opera\u010dn\u00edho okna a objevila se zape\u010det\u011bn\u00e1 \u0159et\u011bzov\u00e1 vazba. V tom okam\u017eiku prov\u00e1d\u00edme operaci dehydratace a nahrazujeme tyto soubory pr\u00e1zdn\u00fdmi. Samoz\u0159ejm\u011b, znovu na kapacitn\u00edm \u00falo\u017ei\u0161ti nic nekop\u00edrujeme.<\/p>\n<p>Za celou tuto fascinuj\u00edc\u00ed logiku odpov\u00edd\u00e1 jedin\u00e1 za\u0161krt\u00e1vac\u00ed pol\u00ed\u010dko v rozhran\u00ed: Copy backups to object storage as soon as they are created.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/1a0e27c04428ebd48b13d8927a453d62.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>A pro\u010d pot\u0159ebujeme tento re\u017eim Copy? <\/h3>\n<p>\nLep\u0161\u00ed je p\u0159efrazovat ot\u00e1zku takto \u2013 jak\u00fdch rizik se t\u00edmto chr\u00e1n\u00edme? Jak\u00fd probl\u00e9m n\u00e1m pom\u00e1h\u00e1 \u0159e\u0161it?<\/p>\n<p>Odpov\u011b\u010f je jasn\u00e1: samoz\u0159ejm\u011b, je to obnova dat. Pokud m\u00e1me v objektov\u00e9m \u00falo\u017ei\u0161ti plnou kopii m\u00edstn\u00edch dat, nez\u00e1le\u017e\u00ed na tom, co se stane s na\u0161\u00edm produktem, v\u017edy m\u016f\u017eeme obnovit data ze soubor\u016f ulo\u017een\u00fdch v podm\u00edn\u011bn\u00e9m Amazonu.<\/p>\n<p>Tak\u017ee se poj\u010fme pod\u00edvat na mo\u017en\u00e9 sc\u00e9n\u00e1\u0159e, od nejjednodu\u0161\u0161\u00edho po slo\u017eit\u011bj\u0161\u00ed.<\/p>\n<p>Nejjednodu\u0161\u0161\u00ed pohroma, kter\u00e1 n\u00e1m m\u016f\u017ee spadnout na hlavu \u2013 to je nedostupnost jednoho ze soubor\u016f v z\u00e1lo\u017en\u00edm \u0159et\u011bzci.<\/p>\n<p>Smutn\u011bj\u0161\u00ed p\u0159\u00edb\u011bh \u2013 jeden z extents na\u0161eho SOBR \u00falo\u017ei\u0161t\u011b se n\u00e1m rozbil.<\/p>\n<p>Je\u0161t\u011b h\u016f\u0159e, kdy\u017e je cel\u00e9 SOBR \u00falo\u017ei\u0161t\u011b nedostupn\u00e9, ale kapacitn\u00ed \u00falo\u017ei\u0161t\u011b funguje.<br \/>\nA \u00fapln\u011b \u0161patn\u011b \u2013 to je, kdy\u017e um\u00edr\u00e1 z\u00e1lo\u017en\u00ed server a va\u0161e prvn\u00ed p\u0159\u00e1n\u00ed je zkusit b\u011b\u017eet na kanadskou hranici za deset minut.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/868d71412901ed362956e1e2157ed895.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA nyn\u00ed se pod\u00edvejme na ka\u017edou situaci zvl\u00e1\u0161\u0165.<\/p>\n<p>Kdy\u017e ztrat\u00edme jeden (a\u0165 u\u017e s n\u00edm, i n\u011bkolik) z\u00e1lo\u017en\u00edch soubor\u016f, sta\u010d\u00ed spustit proces znovuskenov\u00e1n\u00ed \u00falo\u017ei\u0161t\u011b a ztracen\u00fd soubor bude nahrazen pr\u00e1zdn\u00fdm souborem. A pomoc\u00ed procesu regenerace (o kter\u00e9m bylo na za\u010d\u00e1tku \u010dl\u00e1nku) si u\u017eivatel m\u016f\u017ee st\u00e1hnout data z kapacity do m\u00edstn\u00edho \u00falo\u017ei\u0161t\u011b.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/5066a21cbd17565569891f8e23cac4fd.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTe\u010f je situace slo\u017eit\u011bj\u0161\u00ed. P\u0159edpokl\u00e1dejme, \u017ee n\u00e1\u0161 SOBR se skl\u00e1d\u00e1 ze dvou extent\u016f, kter\u00e9 pracuj\u00ed v re\u017eimu Performance, co\u017e znamen\u00e1, \u017ee na\u0161e .vbk a .vib jsou rozlo\u017eeny na nich docela nerovnom\u011brn\u011b. A v ur\u010dit\u00e9m okam\u017eiku se jeden z extent\u016f stane nedostupn\u00fdm, a u\u017eivatel pot\u0159ebuje urgentn\u011b obnovit stroj, jeho\u017e \u010d\u00e1st dat le\u017e\u00ed pr\u00e1v\u011b na tomto extentu. <\/p>\n<p>U\u017eivatel spust\u00ed pr\u016fvodce obnovy, vybere bod, na kter\u00fd chce obnovit, a b\u011bhem pr\u00e1ce pr\u016fvodce si uv\u011bdom\u00ed, \u017ee v\u0161echny pot\u0159ebn\u00e9 pro obnovu data nem\u00e1 lok\u00e1ln\u011b a mus\u00ed je st\u00e1hnout z kapacity. P\u0159i\u010dem\u017e bloky, kter\u00e9 zbyly na m\u00edstn\u00edm \u00falo\u017ei\u0161ti, se z cloudu stahovat nebudou. D\u00edky restore indexu (ano, o tom tak\u00e9 bylo na za\u010d\u00e1tku \u010dl\u00e1nku).<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/88b38ddf122d20a3e41a0afcba544749.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPodtyp t\u00e9to situace \u2014 nedostupn\u00fd je cel\u00fd SOBR repozit\u00e1\u0159. V takov\u00e9m p\u0159\u00edpad\u011b nem\u00e1me co kop\u00edrovat z m\u00edstn\u00edch \u00falo\u017ei\u0161\u0165 a v\u0161echny bloky se stahuj\u00ed z cloudu.<\/p>\n<p>A nejzaj\u00edmav\u011bj\u0161\u00ed situace \u2014 selhal z\u00e1lo\u017en\u00ed server. Zde jsou dv\u011b varianty: administr\u00e1tor je \u0161ikovn\u00fd a d\u011bl\u00e1 konfigura\u010dn\u00ed z\u00e1lohy, nebo administr\u00e1tor s\u00e1m sob\u011b zlobn\u00fd Bu\u0159t\u00edk a ned\u011blal konfigura\u010dn\u00ed z\u00e1lohu.<\/p>\n<p>V prvn\u00edm p\u0159\u00edpad\u011b mu bude sta\u010dit jednodu\u0161e n\u011bkde rozbalit \u010distou instalaci VBR a obnovit jeho datab\u00e1zi ze z\u00e1lohy b\u011b\u017en\u00fdmi prost\u0159edky. Na konci tohoto procesu se v\u0161e vr\u00e1t\u00ed na sv\u00e9 m\u00edsto. Nebo bude obnoveno podle jednoho z v\u00fd\u0161e uveden\u00fdch sc\u00e9n\u00e1\u0159\u016f.<\/p>\n<p>Ale pokud je administr\u00e1tor s\u00e1m sob\u011b nep\u0159\u00edtelem nebo z\u00e1loha konfigurace tak\u00e9 potkala historickou ne\u00fasp\u011bch, tak ani tady ho nenech\u00e1me na holi\u010dk\u00e1ch. Pro tento p\u0159\u00edpad jsme zavedli novou proceduru, kter\u00e1 se naz\u00fdv\u00e1 Import Object Storage. Umo\u017e\u0148uje p\u0159esko\u010dit manu\u00e1ln\u00ed proces obnovy SOBR \u00falo\u017ei\u0161t\u011b a jeho p\u0159ipojen\u00ed k kapacitn\u00edm tier\u016fm s n\u00e1sledn\u00fdm rescanem, a jednodu\u0161e p\u0159idat objektov\u00e9 \u00falo\u017ei\u0161t\u011b do rozhran\u00ed Vima a spustit proceduru Import Storage Repository. Jedinou p\u0159ek\u00e1\u017ekou mezi v\u00e1mi a va\u0161imi z\u00e1lohami m\u016f\u017ee b\u00fdt po\u017eadavek na zad\u00e1n\u00ed hesla, pokud byly va\u0161e z\u00e1lohy za\u0161ifrov\u00e1ny.<\/p>\n<p>T\u00edmto kon\u010d\u00edme s Copy Mode, a nyn\u00ed p\u0159ech\u00e1z\u00edme k<\/p>\n<h3>Sealed Mode<\/h3>\n<p>\nHlavn\u00ed my\u0161lenka \u2014 na vybran\u00e9m extentu SOBR \u00falo\u017ei\u0161t\u011b nemohou vznikat nov\u00e9 z\u00e1lohy. A\u017e do verze 10 jsme m\u011bli pouze Maintenance Mode, kdy byla zcela zak\u00e1z\u00e1na jak\u00e1koliv pr\u00e1ce s \u00falo\u017ei\u0161t\u011bm. Takov\u00fd hardcorov\u00fd re\u017eim vy\u0159azen\u00ed \u00falo\u017ei\u0161t\u011b z provozu, kde byla dostupn\u00e1 pouze tla\u010d\u00edtko Evacuate, kter\u00e9 jednor\u00e1zov\u011b p\u0159esouvalo z\u00e1lohy na jin\u00fd extent.<\/p>\n<p>Sealed mode \u2014 to je jak\u00e1si \"m\u011bk\u010d\u00ed\" varianta: zakazujeme vytv\u00e1\u0159en\u00ed nov\u00fdch z\u00e1loh a postupn\u011b odstra\u0148ujeme star\u00e9 podle vybran\u00e9ho reten\u010dn\u00edho obdob\u00ed, ale v pr\u016fb\u011bhu neztr\u00e1c\u00edme mo\u017enost obnovy z ulo\u017een\u00fdch bod\u016f. Velmi u\u017eite\u010dn\u00e1 v\u011bc, kdy\u017e n\u00e1m kon\u010d\u00ed \u017eivotnost hardwaru a je t\u0159eba jej vym\u011bnit, nebo je t\u0159eba uvolnit m\u00edsto pro n\u011bco d\u016fle\u017eit\u011bj\u0161\u00edho, a nen\u00ed kam to v\u0161echno jednor\u00e1zov\u011b p\u0159esunout. Nebo to nelze odstranit. <\/p>\n<p>Princip fungov\u00e1n\u00ed je tedy velmi jednoduch\u00fd: je t\u0159eba zak\u00e1zat v\u0161echny write operace (vznik nov\u00fdch dat), s ponech\u00e1n\u00edm read (obnovy) a delete (reten\u010dn\u00ed).<\/p>\n<p>Oba re\u017eimy lze pou\u017e\u00edvat sou\u010dasn\u011b, jen je t\u0159eba m\u00edt na pam\u011bti, \u017ee Maintenance m\u00e1 vy\u0161\u0161\u00ed prioritu.<\/p>\n<p>Jako p\u0159\u00edklad zva\u017eme SOBR slo\u017een\u00e9 ze dvou extent\u016f. P\u0159edpokl\u00e1dejme, \u017ee prvn\u00ed \u010dty\u0159i dny jsme vytv\u00e1\u0159eli z\u00e1lohy v re\u017eimu Forward Forever Incremental, a pot\u00e9 jsme uzav\u0159eli extent. To vede k tomu, \u017ee iniciujeme vytvo\u0159en\u00ed nov\u00e9ho aktivn\u00edho fullu na druh\u00e9m dostupn\u00e9m extentu. Pokud je na\u0161e reten\u010dn\u00ed obdob\u00ed \u010dty\u0159i, pak kdy\u017e cel\u00e1 \u0159et\u011bzec um\u00edst\u011bn\u00fd na uzav\u0159en\u00e9m extentu p\u0159ekro\u010d\u00ed jeho limit, je s klidn\u00fdm sv\u011bdom\u00edm odstran\u011bn.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/5476ebcf9b57eeb6c0326499ac42763f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nExistuj\u00ed situace, kdy doch\u00e1z\u00ed k odstran\u011bn\u00ed d\u0159\u00edve. Nap\u0159\u00edklad to je Forward incremental s periodick\u00fdmi fully. Pokud jsme za prvn\u00ed dva dny vytvo\u0159ili full z\u00e1lohy, a ve \u010dtvrtek se rozhodneme uzav\u0159\u00edt \u00falo\u017ei\u0161t\u011b, v p\u00e1tek, kdy se vytvo\u0159\u00ed nov\u00fd full, bude soubor ze pond\u011bl\u00ed odstran\u011bn, proto\u017ee k t\u00e9to verzi nejsou \u017e\u00e1dn\u00e9 z\u00e1vislosti. A sama verze na nikom nez\u00e1vis\u00ed. Pot\u00e9 \u010dek\u00e1me, a\u017e budou vytvo\u0159eny \u010dty\u0159i verze na dostupn\u00e9m rozsahu a odstran\u00edme zb\u00fdvaj\u00edc\u00ed t\u0159i, kter\u00e9 nemohou b\u00fdt odstran\u011bny nez\u00e1visle na sob\u011b.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/c6cc452f98336803731163dfd794f828.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nS Reverse Incremental je situace jednodu\u0161\u0161\u00ed. Nejstar\u0161\u00ed verze na ni\u010dem nez\u00e1vis\u00ed a mohou b\u00fdt bez obav odstran\u011bny. Jakmile tedy bude vytvo\u0159en nov\u00fd .vbk na nov\u00e9m rozsahu, star\u00e9 .vrb budou jednotliv\u011b odstra\u0148ov\u00e1ny.<\/p>\n<p>Mimochodem, pro\u010d ka\u017ed\u00fdkr\u00e1t vytv\u00e1\u0159\u00edme nov\u00fd .vbk: pokud bychom ho nevytv\u00e1\u0159eli a pokra\u010dovali ve star\u00e9m \u0159et\u011bzci inkrement\u016f, star\u00fd .vbk by visel nekone\u010dn\u011b dlouho v jak\u00e9mkoli re\u017eimu, co\u017e by br\u00e1nilo jeho odstran\u011bn\u00ed. Proto bylo rozhodnuto, \u017ee jakmile je \u00falo\u017ei\u0161t\u011b uzav\u0159eno, vytvo\u0159\u00edme full z\u00e1lohu na voln\u00e9m rozsahu.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/3757fae46ad76d64cdddfb941309d557.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSituace se komplikuje s kapacity tierem. <\/p>\n<p>Nejprve se pod\u00edvejme na copy mode. P\u0159edpokl\u00e1dejme, \u017ee jsme \u010dty\u0159i dny aktivn\u011b vytv\u00e1\u0159eli z\u00e1lohy a pak byl kapacity tier uzav\u0159en. Nic neodstra\u0148ujeme, ale trp\u011bliv\u011b dodr\u017eujeme reten\u010dn\u00ed politiku, po kter\u00e9 odstran\u00edme data z kapacity tieru.<\/p>\n<p>Podobn\u00e9 se d\u011bje i v move mode \u2014 vy\u010dk\u00e1me na reten\u010dn\u00ed politiku, odstran\u00edme star\u00e9 v lok\u00e1ln\u00edm \u00falo\u017ei\u0161ti a odstran\u00edme to, co je ulo\u017eeno v object storage.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/391d3b231c7de5da1d13e19c31bd6b7c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nZaj\u00edmav\u00fd p\u0159\u00edklad je s Forever forward incremental. Nastav\u00edme reten\u010dn\u00ed politiku na t\u0159i verze a za\u010dneme v pond\u011bl\u00ed vytv\u00e1\u0159et z\u00e1lohy, kter\u00e9 se spolehliv\u011b kop\u00edruj\u00ed do cloudov\u00e9ho \u00falo\u017ei\u0161t\u011b. Po uzav\u0159en\u00ed \u00falo\u017ei\u0161t\u011b z\u00e1lohy pokra\u010duj\u00ed v tvorb\u011b a dodr\u017euj\u00ed t\u0159i verze, ale data ulo\u017een\u00e1 v kapacity tieru z\u016fst\u00e1vaj\u00ed z\u00e1visl\u00e1 a nelze je odstranit. Proto \u010dek\u00e1me a\u017e do \u010dtvrtka, kdy n\u00e1\u0161 .vbk p\u0159ekro\u010d\u00ed reten\u010dn\u00ed politiku, a a\u017e pot\u00e9 bez obav odstran\u00edme cel\u00fd ulo\u017een\u00fd \u0159et\u011bzec.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/617a42452060210b58148e1fe942a540.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA mal\u00e1 pozn\u00e1mka: v\u0161echny p\u0159\u00edklady zde jsou uvedeny s jedn\u00edm strojem. Pokud jich m\u00e1te v z\u00e1loze v\u00edce, bude se jejich reten\u010dn\u00ed politika li\u0161it v z\u00e1vislosti na tom, zda byla provedena Active Full nebo ne.<\/p>\n<p>A t\u00edmto je v podstat\u011b v\u0161e. Tak\u017ee p\u0159ech\u00e1z\u00edme k t\u00e9 nejt\u011b\u017e\u0161\u00ed funkci \u2014 <\/p>\n<h3>Immutability <\/h3>\n<p>\nJak u p\u0159edchoz\u00edch bod\u016f, nejprve si pov\u00edme, jak\u00fd probl\u00e9m tato funkce \u0159e\u0161\u00ed. Jakmile exportujeme na\u0161e z\u00e1lohy na extern\u00ed \u00falo\u017ei\u0161t\u011b, okam\u017eit\u011b vznik\u00e1 touha zaru\u010dit jejich bezpe\u010dnost, tedy fyzicky zak\u00e1zat jejich odstran\u011bn\u00ed a jakoukoliv modifikaci po ur\u010ditou dobu retention. To zahrnuje i administr\u00e1tory, a to i pod jejich root \u00fa\u010dty. To chr\u00e1n\u00ed p\u0159ed n\u00e1hodn\u00fdm nebo z\u00e1m\u011brn\u00fdm po\u0161kozen\u00edm. Ti, kdo pracuj\u00ed s AWS, u\u017e se mohli setkat s podobnou funkc\u00ed pod n\u00e1zvem Object Lock.<\/p>\n<p>Nyn\u00ed se pod\u00edvejme na re\u017eim obecn\u011b, a pak se pono\u0159\u00edme do detail\u016f. V na\u0161em p\u0159\u00edkladu bude Immutability zapnuto pro n\u00e1\u0161 kapacitn\u00ed tier s retenc\u00ed na \u010dty\u0159i dny. A v z\u00e1loze bude zapnut re\u017eim Copy.<\/p>\n<p>Immutability nijak neinteraguje s celkovou retenc\u00ed. Nap\u0159\u00edklad nep\u0159id\u00e1v\u00e1 \u017e\u00e1dn\u00e9 dal\u0161\u00ed body nebo n\u011bco podobn\u00e9ho. Po dobu \u010dty\u0159 dn\u016f nem\u016f\u017ee u\u017eivatel odstranit soubory z\u00e1loh. Pokud se v pond\u011bl\u00ed vytvo\u0159\u00ed z\u00e1loha, bude mo\u017en\u00e9 soubor odstranit a\u017e v p\u00e1tek.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/131e50058c1a015ec78089ed4d038bfc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV\u0161echny d\u0159\u00edve vysv\u011btlen\u00e9 koncepty dehydratace, index\u016f a metadat funguj\u00ed p\u0159esn\u011b tak, jak byly. Ale s jednou podm\u00ednkou \u2014 blok se uplat\u0148uje nejen na data, ale i na metadata. To je ud\u011bl\u00e1no pro p\u0159\u00edpad, \u017ee by zl\u00fd \u00fato\u010dn\u00edk cht\u011bl smazat na\u0161i datab\u00e1zi metadat a aby bloky s daty neztratily svou hodnotu a nestaly se zbyte\u010dnou bin\u00e1rn\u00ed ka\u0161\u00ed.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/edfe5c04a082594cf5d67f4bafeccb3a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA nyn\u00ed nastal skv\u011bl\u00fd okam\u017eik pro vysv\u011btlen\u00ed na\u0161\u00ed technologie generov\u00e1n\u00ed blok\u016f. Nebo block generation. Proto si proberme situaci, kter\u00e1 vedla k jej\u00edmu vzniku.<\/p>\n<p>Vezmeme \u010dasovou osu na \u0161est dn\u00ed a n\u00ed\u017ee budeme vyzna\u010dovat \u010das o\u010dek\u00e1van\u00e9ho vypr\u0161en\u00ed immutability. Vytvo\u0159\u00edme v prvn\u00ed den soubor slo\u017een\u00fd z bloku a a jeho metadata. Pokud je immutability nastavena na t\u0159i dny, je logick\u00e9 p\u0159edpokl\u00e1dat, \u017ee \u010dtvrt\u00fd den budou data odblokov\u00e1na a odstran\u011bna. Druh\u00fd den p\u0159id\u00e1me nov\u00fd file2, slo\u017een\u00fd z bloku b se stejn\u00fdmi nastaven\u00edmi. Blok a by m\u011bl b\u00fdt st\u00e1le odstran\u011bn \u010dtvrt\u00fd den. Ale t\u0159et\u00ed den se stane hrozn\u00e9 \u2014 vytvo\u0159\u00ed se soubor File3, skl\u00e1daj\u00edc\u00ed se z nov\u00e9ho bloku d a odkazu na star\u00fd blok a. To znamen\u00e1, \u017ee pro blok a by m\u011bl b\u00fdt jeho flag immutability nastaven na novou dobu, kter\u00e1 se posune na \u0161est\u00fd den. A tady vznik\u00e1 probl\u00e9m \u2014 v re\u00e1ln\u00fdch z\u00e1loh\u00e1ch t\u011bchto blok\u016f vznik\u00e1 obrovsk\u00e9 mno\u017estv\u00ed. A abychom prodlou\u017eili jejich immutability obdob\u00ed, mus\u00edme poka\u017ed\u00e9 prov\u00e9st obrovsk\u00e9 mno\u017estv\u00ed po\u017eadavk\u016f. A ve skute\u010dnosti to bude t\u00e9m\u011b\u0159 nekone\u010dn\u00fd ka\u017edodenn\u00ed proces, proto\u017ee s velkou pravd\u011bpodobnost\u00ed p\u0159i ka\u017ed\u00e9m kop\u00edrov\u00e1n\u00ed nalezneme obrovsk\u00e9 hromady deduplika\u010dn\u00edch blok\u016f. A co znamen\u00e1 velk\u00e9 mno\u017estv\u00ed po\u017eadavk\u016f u poskytovatel\u016f objektov\u00e9ho \u00falo\u017ei\u0161t\u011b? Spr\u00e1vn\u011b! Obrovsk\u00fd \u00fa\u010det na konci m\u011bs\u00edce.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/ce9c5d0da67f99019b00c4a666302fee.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA aby se v \u017e\u00e1dn\u00e9m p\u0159\u00edpad\u011b neopravdu nezhanobili sv\u00e9 obl\u00edben\u00e9 klienty na slu\u0161n\u00e9 pen\u00edze, byl vynalezen mechanismus generov\u00e1n\u00ed blok\u016f. To je dodate\u010dn\u00e9 obdob\u00ed, kter\u00e9 p\u0159id\u00e1v\u00e1me k nastaven\u00e9mu obdob\u00ed immutability. V n\u00ed\u017ee uveden\u00e9m p\u0159\u00edkladu je toto obdob\u00ed rovno dv\u011bma dn\u016fm. Ale to je pouze pro p\u0159\u00edklad. Ve skute\u010dnosti se tam pou\u017e\u00edv\u00e1 vlastn\u00ed formule, kter\u00e1 d\u00e1v\u00e1 p\u0159ibli\u017en\u011b deset dodate\u010dn\u00fdch dn\u00ed p\u0159i m\u011bs\u00ed\u010dn\u00edm z\u00e1mku. <\/p>\n<p>Pokra\u010dujeme ve zkoum\u00e1n\u00ed t\u00e9\u017ee situace, ale s generov\u00e1n\u00edm blok\u016f. Vytv\u00e1\u0159\u00edme v prvn\u00edm dni file1 z bloku a metadat. Skl\u00e1d\u00e1me obdob\u00ed generov\u00e1n\u00ed a nem\u011bnnost \u2013 to znamen\u00e1, \u017ee mo\u017enost smaz\u00e1n\u00ed souboru bude a\u017e \u0161est\u00fd den. Pokud druh\u00fd den vytvo\u0159\u00edme File2, kter\u00fd se skl\u00e1d\u00e1 z bloku b a odkazu na blok a, o\u010dek\u00e1van\u00fd datum smaz\u00e1n\u00ed se nem\u011bn\u00ed. St\u00e1le z\u016fst\u00e1v\u00e1 na \u0161est\u00fd den. Sna\u017e\u00edme se t\u00edm p\u00e1dem \u0161et\u0159it pen\u00edze na po\u010dtu dotaz\u016f. Jedin\u00e1 situace, kdy se term\u00edn m\u016f\u017ee posunout, je, pokud vypr\u0161elo obdob\u00ed generov\u00e1n\u00ed. To znamen\u00e1, \u017ee pokud t\u0159et\u00ed den nov\u00fd File3 bude obsahovat odkaz na blok a, bude p\u0159id\u00e1n generov\u00e1n\u00ed 2, proto\u017ee Gen1 u\u017e vypr\u0161elo. A o\u010dek\u00e1van\u00e9 datum smaz\u00e1n\u00ed bloku a se posune na osm\u00fd den. To n\u00e1m umo\u017e\u0148uje dramaticky sn\u00ed\u017eit po\u010det dotaz\u016f na prodlou\u017een\u00ed \u017eivotnosti deduplikovan\u00fdch blok\u016f, co\u017e \u0161et\u0159\u00ed spoustu pen\u011bz pro z\u00e1kazn\u00edky.<\/p>\n<p><img decoding=\"async\" alt=\"Co se zm\u011bnilo v Capacity Tier, kdy\u017e se Veeam stal v10\" src=\"\/wp-content\/uploads\/2020\/06\/2056d0c15e4e7fcdd67a56b11f973119.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSamotn\u00e1 technologie je dostupn\u00e1 u\u017eivatel\u016fm S3 a S3-kompatibiln\u00edho hardwaru, jeho\u017e v\u00fdrobci zaru\u010duj\u00ed, \u017ee jejich implementace se neli\u0161\u00ed od t\u00e9 od Amazonu. Odtud odpov\u011b\u010f na legitimn\u00ed ot\u00e1zku, pro\u010d nen\u00ed podporov\u00e1no Azure \u2013 maj\u00ed podobnou funkci, ale ta funguje na \u00farovni kontejner\u016f, nikoli jednotliv\u00fdch objekt\u016f. Mimochodem, v samotn\u00e9m Amazonu existuje Object Lock ve dvou re\u017eimech: compliance a governance. V druh\u00e9m p\u0159\u00edpad\u011b z\u016fst\u00e1v\u00e1 mo\u017enost, \u017ee ten nejv\u011bt\u0161\u00ed admin nad adminy a root nad rooty, navzdory Object Lock, p\u0159esto sma\u017ee data. V p\u0159\u00edpad\u011b compliance je v\u0161echno p\u0159ibito h\u0159eb\u00edky a nikdo nem\u016f\u017ee z\u00e1lohy smazat. Dokonce ani administr\u00e1to\u0159i Amazonu (podle jejich ofici\u00e1ln\u00edch prohl\u00e1\u0161en\u00ed). Podporujeme pr\u00e1v\u011b tento re\u017eim.<\/p>\n<p>\nA tradi\u010dn\u011b, n\u011bkolik u\u017eite\u010dn\u00fdch odkaz\u016f:<\/p>\n<ul>\n<li>O <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/block_generation.html?ver=100\">Generov\u00e1n\u00ed blok\u016f<\/a><\/noindex> ve v\u0161ech podrobnostech.<\/li>\n<li>V\u0161echny informace o <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/overview.html?ver=100\">Veeam Backup &amp; Replication 10<\/a><\/noindex> v nejlep\u0161\u00edm proveden\u00ed<\/li>\n<li>O <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/capacity_tier.html?ver=100\">Kapacitn\u00ed \u00farove\u0148<\/a><\/noindex> v detailech<\/li>\n<\/ul>\n<p>Zdroj: <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.3 - 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\/cs\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"cs_CZ\" \/>\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\/cs\/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\udd47Co se zm\u011bnilo v Kapacitn\u00ed \u00farovni, kdy\u017e Veeam p\u0159e\u0161el na v10 | ProHoster","description":"Kapacitn\u00ed \u00farove\u0148 (nebo jak ji naz\u00fdv\u00e1me uvnit\u0159 vymy \u2014 kaptir) byla zavedena u\u017e v dob\u011b Veeam Backup and Replication 9.5 Update 4 pod n\u00e1zvem Archive Tier.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/chto-izmenilos-v-capacity-tier-kogda-veeam-stal-v10","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/84809","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=84809"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/84809\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/84810"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=84809"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=84809"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=84809"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}