{"id":29927,"date":"2019-10-31T21:32:42","date_gmt":"2019-10-31T18:32:42","guid":{"rendered":"https:\/\/prohoster.info\/blog\/bekap-mne-na-lentu-zapili-rasskaz-ot-pervogo-litsa\/"},"modified":"2019-10-31T21:32:42","modified_gmt":"2019-10-31T18:32:42","slug":"bekap-mne-na-lentu-zapili-rasskaz-ot-pervogo-litsa","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/bekap-mne-na-lentu-zapili-rasskaz-ot-pervogo-litsa","title":{"rendered":"\u201eZ\u00e1lohu mi na p\u00e1sku sprav\u201c Pr\u00edbeh z poh\u013eadu prvej osoby","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

V predch\u00e1dzaj\u00facej \u010dl\u00e1nku<\/a><\/noindex> Povedali sme v\u00e1m o nov\u00fdch funkci\u00e1ch v janu\u00e1rovom aktualiz\u00e1cii Update 4 pre Veeam Backup & Replication 9.5 (VBR), kde sme \u00famyselne nespomenuli z\u00e1lohy na magnetick\u00e9 p\u00e1sky. Rozpr\u00e1vanie o tejto oblasti si zasl\u00fa\u017ei samostatn\u00fd \u010dl\u00e1nok, preto\u017ee nov\u00fdch funkci\u00ed bolo naozaj ve\u013ea.<\/p>\n

\u2013 Chlapci z QA, nap\u00ed\u0161ete \u010dl\u00e1nok?
\n\u2013 Pre\u010do nie!<\/p>\n

\"\u201eZ\u00e1lohu
\n
\n<\/a><\/noindex><\/p>\n

P\u00e1skov\u00e9 \u00falo\u017eisk\u00e1 v XXI. storo\u010d\u00ed<\/h1>\n

\nUkladanie d\u00e1t na magnetick\u00e9 p\u00e1sky (kazety, \u201ep\u00e1sky<\/b>\u201c, ako ich naz\u00fdvame v R&D) sa neobmedzuje na minulos\u0165 po\u010d\u00edta\u010da ZX-Spectrum, ktor\u00e9ho hra sa mohla na\u010d\u00edtava\u0165 do opera\u010dnej pam\u00e4te 48 kb z magnetof\u00f3novej kazety<\/a><\/noindex> nieko\u013eko min\u00fat. Za \u0161tvr\u0165 storo\u010dia sa r\u00fdchlosti a kapacity kaziet zv\u00fd\u0161ili o 6-7 poriadkov. To nie je celkom presn\u00e9 porovnanie a pod\u013ea Mooreovho z\u00e1kona<\/a><\/noindex> \u0161tandard LTO<\/a><\/noindex> nest\u00edha. Napriek tomu modern\u00e9 technol\u00f3gie umo\u017e\u0148uj\u00fa zap\u00edsa\u0165 na kilometrov\u00fa p\u00e1sku jednej kazety 12 terabajtov d\u00e1t (a\u017e 30 terabajtov v kompresnom re\u017eime), tak\u017ee \u00falo\u017eisko za 160 dol\u00e1rov predbehne konkurenciu v cene dlhodob\u00e9ho uchov\u00e1vania ve\u013ek\u00e9ho objemu d\u00e1t, aj so zoh\u013eadnen\u00edm invest\u00edci\u00ed do zariaden\u00ed na z\u00e1pis\/\u010d\u00edtanie. D\u00e1tami na tak\u00fdchto kazet\u00e1ch s\u00fa spo\u013eahlivo uchov\u00e1van\u00e9 15-30 rokov.<\/p>\n

Pozrime sa na to z in\u00e9ho poh\u013eadu. V posledn\u00fdch \u010dasoch ransomv\u00e9r<\/a><\/noindex> dosiahol nov\u00fd level. M\u00f4\u017ee \u010daka\u0165 na svoj \u010das v infra\u0161trukt\u00fare ve\u013ekej spolo\u010dnosti t\u00fd\u017edne a mesiace, a s pr\u00edchodom novej zranite\u013enosti nult\u00e9ho d\u0148a - zni\u010di\u0165 (nie bez pomoci \u010dloveka, ve\u010f ide o ve\u013ek\u00e9 peniaze) nielen v\u0161etky d\u00e1ta, ale aj v\u0161etky z\u00e1lohy, ku ktor\u00fdm sa d\u00e1 len dosta\u0165. Tu je \u010derstv\u00fd pr\u00edklad<\/a><\/noindex>, kedy musela spolo\u010dnos\u0165 zaplati\u0165 v\u00fdkupn\u00e9. Takzvan\u00e9 air gap<\/b>, t. j. fyzicky izolovan\u00e9 od infra\u0161trukt\u00fary z\u00e1lohy sa stali v podstate jedin\u00fdm spo\u013eahliv\u00fdm z\u00e1chran\u00e1rom pred tak\u00fdmito situ\u00e1ciami. Magnetick\u00e1 p\u00e1ska je tu jedn\u00fdm z nad\u010dasov\u00fdch rie\u0161en\u00ed.<\/p>\n

\"\u201eZ\u00e1lohu
\n
\nAle jedna \u0161pecifik\u00e1cia a technologick\u00e9 \u017eelez\u00e1 a baryo-ferritov\u00e9 novinky od popredn\u00fdch v\u00fdrobcov (IBM, HPE, Oracle, Dell) nesta\u010dia na spo\u013eahliv\u00fa ochranu d\u00e1t, potrebn\u00fd je dobr\u00fd softv\u00e9r. U n\u00e1s vo Veeam je cel\u00fd t\u00edm, ktor\u00fd sa zaober\u00e1 p\u00e1skov\u00fdmi z\u00e1lohami, pribli\u017ene 10 \u013eud\u00ed denne analyzuje, pl\u00e1nuje, sk\u00fama, vyv\u00edja a testuje. V\u00fdsledky tejto pr\u00e1ce ste mohli vidie\u0165 v predch\u00e1dzaj\u00facich \u010dl\u00e1nkoch (raz<\/a><\/noindex>, dva<\/a><\/noindex>). \u010co sa v\u0161ak urobilo za posledn\u00fd rok?<\/p>\n

Glos\u00e1r<\/h1>\n

\nStoj\u00ed p\u0159ed volbou mezi svobodou ohledn\u011b rodn\u00e9ho jazyka a slo\u017eit\u00fdmi form\u00e1ln\u011b ne\u010ditelnostmi. Preferuji prvn\u00ed mo\u017enost, proto se p\u0159edem omlouv\u00e1m, pokud n\u011bkomu \u017earg\u00f3nov\u00e9 v\u00fdrazy ze seznamu n\u00ed\u017ee budou p\u016fsobit ru\u0161iv\u011b. Zde si tak\u00e9 v kr\u00e1tkosti p\u0159ipomeneme, co znamen\u00e1 ten \u010di onen term\u00edn. <\/p>\n

Kori\u00e9r\u016fm VBR tuto \u010d\u00e1st lze p\u0159esko\u010dit<\/b>Job <\/b>\u2013 job \u2013 \u00faloha z\u00e1lohov\u00e1n\u00ed. Vlastn\u011b, cel\u00fd VBR je postaven na jobech. Krom\u011b z\u00e1lohy a replikace to m\u016f\u017ee b\u00fdt i kop\u00edrov\u00e1n\u00ed na magnetickou p\u00e1sku (backup to tape job, tape job). Upozorn\u00edm, \u017ee obnova ze z\u00e1lohy (restore) je tak\u00e9 job, ale v tomto \u010dl\u00e1nku pod t\u00edmto slovem budeme ch\u00e1pat pr\u00e1v\u011b z\u00e1lohu.<\/p>\n

Storage <\/b>\u2013 storage \u2013 historicky zaveden\u00fd n\u00e1zev. Jsou to soubory v repozit\u00e1ri <\/b>(repository \u2013 \u00falo\u017ei\u0161t\u011b), kter\u00e9 obsahuj\u00ed z\u00e1lohy \u2013 \u00fapln\u00e9 <\/b>a inkrement\u00e1ln\u00ed<\/b>. V jednom storage m\u016f\u017ee b\u00fdt jak jedna, tak i n\u011bkolik virtu\u00e1ln\u00edch stroj\u016f.<\/p>\n

\u0158et\u011bzec <\/b>\u2013 chain \u2013 sekvence propojen\u00fdch storage. Pro obnoven\u00ed dat z n-t\u00e9ho inkrement\u00e1ln\u00edho storage jsou pot\u0159eba v\u0161echny p\u0159edchoz\u00ed od (n-1)-t\u00e9ho a\u017e po 1. a \u00fapln\u00e9 storage, na kter\u00e9 odkazuje prvn\u00ed inkrement\u00e1ln\u00ed.<\/p>\n

Source<\/b>, Target <\/b>\u2013 source, target. Source \u2013 v\u00fdchoz\u00ed entita, kterou zpracov\u00e1v\u00e1 job. V p\u0159\u00edpad\u011b z\u00e1loh\/replik je to obvykle virtu\u00e1ln\u00ed stroj v hypervizoru. V p\u0159\u00edpad\u011b tape job je source samotn\u00e1 z\u00e1lohovac\u00ed \u00faloha (no nebo soubory v p\u0159\u00edpad\u011b file to tape job). Target pro z\u00e1lohovac\u00ed job je repozit\u00e1\u0159, kde se z\u00e1lohy ukl\u00e1daj\u00ed. Pro tape job je to v\u0161ak media pool.<\/p>\n

Media pool<\/b> \u2013 media pool<\/a><\/noindex> \u2013 pool informa\u010dn\u00edch nosi\u010d\u016f, v na\u0161em p\u0159\u00edpad\u011b \u2013 kazet. Logick\u00fd kontejner, vytv\u00e1\u0159en\u00fd u\u017eivateli a obsahuj\u00edc\u00ed kazety jedn\u00e9 nebo n\u011bkolika knihoven. Tak\u017ee tape job v\u017edy m\u00e1 media pool jako target, tedy data nejsou zapisov\u00e1na na n\u011bjakou konkr\u00e9tn\u00ed kazetu a ne na jakoukoli kazetu v knihovn\u011b, ale na ur\u010dit\u00fd jejich soubor. Media pool m\u00e1 nastaven\u00ed doby uchov\u00e1v\u00e1n\u00ed dat, po jej\u00edm\u017e uplynut\u00ed m\u016f\u017ee b\u00fdt kazeta p\u0159eps\u00e1na. U\u017eivatel m\u016f\u017ee vytv\u00e1\u0159et b\u011b\u017en\u00e9 (standard) a GFS pooly<\/a><\/noindex>. Ka\u017ed\u00fd z t\u011bchto typ\u016f m\u016f\u017ee b\u00fdt je\u0161t\u011b WORM a non-WORM, o tom n\u00ed\u017ee.<\/p>\n

Media set<\/b> \u2013 media set<\/a><\/noindex> \u2013 s\u00fabor kaziet v medi\u00e1lnom poole, na ktor\u00e9 s\u00fa nepretr\u017eite zapisovan\u00e9 z\u00e1lohy\/s\u00fabory. Pre GFS pooly medi\u00e1lnych s\u00faborov s\u00fa kazety viazan\u00e9 aj na interval (napr\u00edklad ro\u010dn\u00fd \u2013 yearly), kazety sa rotuj\u00fa iba v r\u00e1mci svojho intervalu.<\/p>\n

Disk<\/b>, meni\u010d<\/b><\/a><\/noindex> \u2013 prvky tape kni\u017enice. Disk \u010d\u00edta a prekr\u00faca kazetu, meni\u010d \u2013 je robot, ktor\u00fd pres\u00fava kazety medzi slotmi na \u00faschovu, slotmi na vykl\u00e1dku a diskom. Existuj\u00fa aj samostatn\u00e9 disky<\/b> (standalone \u2013 samostatn\u00fd), \u00falohu meni\u010da tu pln\u00ed \u010dlovek. Pre disk je nevyhnutn\u00e9 spr\u00e1vne nain\u0161talovan\u00fd ovl\u00e1da\u010d v\u00fdrobcu na stroji so syst\u00e9mom Windows, ku ktor\u00e9mu je pripojen\u00e1 kni\u017enica; s meni\u010dom m\u00f4\u017eeme pracova\u0165 aj bez ovl\u00e1da\u010dov, cez native SCSI.<\/p>\n

<\/p>\n

Naj\u00edmanie na kazetu. Chr\u00e1nen\u00fd poskytovate\u013e \u2013 chr\u00e1nen\u00ed klienti<\/h1>\n

\nIhne\u010f vytiahneme trumfy na st\u00f4l. Najv\u00e4\u010d\u0161ia funkcia na\u0161ej aktualiz\u00e1cie, ur\u010den\u00e1 pre cloudov\u00fdch poskytovate\u013eov<\/a><\/noindex>, ktor\u00ed vo svojej infra\u0161trukt\u00fare vyu\u017e\u00edvaj\u00fa VBR. V\u00fdvoj sa za\u010dal u\u017e pred dvoma rokmi. \u010coskoro sme si uvedomili, \u017ee sa s tak z\u00e1va\u017enou \u00falohou nebudeme schopn\u00ed vyrovna\u0165 do najbli\u017e\u0161ieho vydania, vzali sme si kr\u00e1tku pauzu a nakoniec sme funkciu vydali v aktualiz\u00e1cii 9.5 Update 4.<\/p>\n

Ak to zhrnieme, teraz maj\u00fa poskytovatelia mo\u017enos\u0165 kop\u00edrova\u0165 z\u00e1lohy svojich klientov na kazety pomocou tape job v GFS poole. To poskytovate\u013eom \u2013 a to s\u00fa ve\u013emi d\u00f4le\u017eit\u00e9 a cenn\u00e9 osoby pre na\u0161e srdce a obchodn\u00e9 oddelenie \u2013 d\u00e1va dve mo\u017enosti:<\/p>\n