{"id":97729,"date":"2020-10-21T08:42:22","date_gmt":"2020-10-21T06:42:22","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/otkuda-berutsya-logi-veeam-log-diving"},"modified":"2020-10-21T08:42:22","modified_gmt":"2020-10-21T06:42:22","slug":"otkuda-berutsya-logi-veeam-log-diving","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/otkuda-berutsya-logi-veeam-log-diving","title":{"rendered":"Odkud poch\u00e1zej\u00ed logy? Veeam Log Diving","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Odkud<\/p>\n

Pokra\u010dujeme v na\u0161em pono\u0159en\u00ed do fascinuj\u00edc\u00edho sv\u011bta lad\u011bn\u00ed chyb podle log\u016f. V p\u0159edchoz\u00ed \u010dl\u00e1nku<\/a><\/noindex> domluvili jsme se na v\u00fdznamu z\u00e1kladn\u00edch term\u00edn\u016f a koutkem oka jsme se pod\u00edvali na celkovou strukturu Veeam jako\u017eto jednoho celku. \u00dakolem t\u00e9to \u010d\u00e1sti je pochopit, jak se vytv\u00e1\u0159ej\u00ed logy, jak\u00e9 informace obsahuj\u00ed a pro\u010d vypadaj\u00ed, jak vypadaj\u00ed.<\/p>\n

Co si mysl\u00edte, co vlastn\u011b ty \u201elogy\u201c jsou? Podle v\u011bt\u0161iny by logy jak\u00e9koliv aplikace m\u011bly slou\u017eit jako jak\u00e1si v\u0161emocn\u00e1 entita, kter\u00e1 v\u011bt\u0161inu \u010dasu p\u0159eb\u00fdv\u00e1 n\u011bkde na okraji, ale v prav\u00fd okam\u017eik se objev\u00ed z ni\u010deho nic v z\u00e1\u0159iv\u00fdch zbroj\u00edch a v\u0161echny zachr\u00e1n\u00ed. To znamen\u00e1, \u017ee by m\u011bly obsahovat v\u0161e, po\u010d\u00ednaje drobn\u00fdmi chybami v ka\u017ed\u00e9 komponent\u011b, a\u017e po jednotliv\u00e9 transakce datab\u00e1ze. A aby po chyb\u011b bylo hned naps\u00e1no, jak ji opravit. A m\u011blo by se to v\u0161echno vej\u00edt do p\u00e1r megabajt\u016f, maxim\u00e1ln\u011b. V\u017edy\u0165 je to jen text! Textov\u00e9 soubory nemohou zab\u00edrat des\u00edtky gigabajt\u016f, n\u011bkde jsem to sly\u0161el!<\/p>\n

Tak\u017ee, logy<\/h2>\n

Ve skute\u010dn\u00e9m sv\u011bt\u011b jsou logy jen archivy diagnostick\u00fdch informac\u00ed. A co tam uchov\u00e1vat, odkud br\u00e1t informace pro ukl\u00e1d\u00e1n\u00ed a jak podrobn\u00e9 by m\u011bly b\u00fdt, rozhoduj\u00ed sami v\u00fdvoj\u00e1\u0159i. N\u011bkdo jde cestou minimalismu a uchov\u00e1v\u00e1 z\u00e1znamy o zapnut\u00ed\/vypnut\u00ed, zat\u00edmco jin\u00fd pe\u010dliv\u011b sb\u00edr\u00e1 v\u0161e, co se mu dostane do rukou. Existuje tak\u00e9 st\u0159edn\u00ed cesta s mo\u017enost\u00ed volby takzvan\u00e9 \u00farovn\u011b logov\u00e1n\u00ed, kdy s\u00e1m ur\u010duje\u0161, jak podrobn\u00e9 informace chce\u0161 uchov\u00e1vat a kolik m\u00e1\u0161 voln\u00e9ho m\u00edsta na disc\u00edch =) V VBR je t\u011bchto \u00farovn\u00ed cel\u00fdch \u0161est, mimochodem. A v\u011b\u0159te, \u017ee nechcete vid\u011bt, co se d\u011bje p\u0159i maxim\u00e1ln\u011b podrobn\u00e9m logov\u00e1n\u00ed se voln\u00fdm m\u00edstem na va\u0161em disku.<\/p>\n

Dob\u0159e. P\u0159ibli\u017en\u011b jsme pochopili, co chceme uchov\u00e1vat, ale vyvst\u00e1v\u00e1 opr\u00e1vn\u011bn\u00e1 ot\u00e1zka: odkud br\u00e1t tyto informace? \u010c\u00e1st ud\u00e1lost\u00ed pro logov\u00e1n\u00ed samoz\u0159ejm\u011b generujeme sami na\u0161imi intern\u00edmi procesy. Ale co d\u011blat, kdy\u017e dojde k interakci s vn\u011bj\u0161\u00edm prost\u0159ed\u00edm? Abychom se nezapletli do temn\u00e9ho pekla z obskurn\u00edch \u0159e\u0161en\u00ed, Veeam m\u00e1 tendenci neobjevovat ji\u017e vynalezen\u00e9 vyn\u00e1lezy. Kdykoliv existuje ji\u017e hotov\u00e9 API, integrovan\u00e1 funkce, knihovna atd., d\u00e1v\u00e1me p\u0159ednost t\u011bmto p\u0159ipraven\u00fdm mo\u017enostem, ne\u017e za\u010dneme budovat sv\u00e1 vlastn\u00ed slo\u017eit\u00e1 \u0159e\u0161en\u00ed. A\u010dkoliv t\u011bch posledn\u00edch je tak\u00e9 dost. Proto je p\u0159i anal\u00fdze log\u016f d\u016fle\u017eit\u00e9 pochopit, \u017ee velk\u00e1 \u010d\u00e1st chyb poch\u00e1z\u00ed z  zpr\u00e1v od t\u0159et\u00edch stran API, syst\u00e9mov\u00fdch vol\u00e1n\u00ed a dal\u0161\u00edch knihoven. V tomto p\u0159\u00edpad\u011b spo\u010d\u00edv\u00e1 role VBR ve forwardov\u00e1n\u00ed t\u011bchto chyb do log\u016f tak, jak jsou. A hlavn\u00edm \u00fakolem u\u017eivatele je nau\u010dit se rozum\u011bt, kter\u00e1 \u0159\u00e1dka pat\u0159\u00ed komu a za co ten \u201ekdo\u201c odpov\u00edd\u00e1. Tak\u017ee pokud v\u00e1s k\u00f3d chyby z logu VBR p\u0159esm\u011bruje na str\u00e1nku MSDN, je to norm\u00e1ln\u00ed a spr\u00e1vn\u00e9.<\/p>\n

Jak jsme se d\u0159\u00edve dohodli: Veeam je takzvan\u00e1 aplikace zalo\u017een\u00e1 na SQL. To znamen\u00e1, \u017ee v\u0161echna nastaven\u00ed, v\u0161echny informace a vlastn\u011b v\u0161e, co je pot\u0159eba pro norm\u00e1ln\u00ed fungov\u00e1n\u00ed, je ulo\u017eeno v jeho datab\u00e1zi. Odtud vypl\u00fdv\u00e1 jednoduch\u00e1 pravda: co nen\u00ed v log\u00e1ch, pravd\u011bpodobn\u011b je v datab\u00e1zi. Ale ani to nen\u00ed st\u0159\u00edbrn\u00e1 kulka: n\u011bkter\u00e9 v\u011bci nejsou ani v lok\u00e1ln\u00edch log\u00e1ch komponent Veeam, ani v jeho datab\u00e1zi. Proto se mus\u00edme nau\u010dit studovat logy hostitele, logy m\u00edstn\u00edho po\u010d\u00edta\u010de a logy v\u0161eho, co se pod\u00edl\u00ed na procesu z\u00e1lohov\u00e1n\u00ed a obnoven\u00ed. A n\u011bkdy se tak\u00e9 st\u00e1v\u00e1, \u017ee po\u017eadovan\u00e9 informace nejsou nikde k nalezen\u00ed. Takov\u00e1 je cesta. <\/p>\n

N\u011bkolik p\u0159\u00edklad\u016f takov\u00fdch API<\/h4>\n

Tento seznam si neklade za c\u00edl b\u00fdt v\u00fdjime\u010dn\u011b \u00fapln\u00fd, tak\u017ee v n\u011bm nehledejte pravdu v posledn\u00ed instanci. Jeho \u00fakolem je pouze uk\u00e1zat nej\u010dast\u011bji pou\u017e\u00edvan\u00e1 extern\u00ed API a technologie, kter\u00e9 se pou\u017e\u00edvaj\u00ed v na\u0161ich produktech.<\/p>\n

Za\u010dn\u011bme s VMware<\/strong>. <\/p>\n

Prvn\u00edm na seznamu bude vSphere API<\/strong>. Pou\u017e\u00edv\u00e1 se k autentifikaci, \u010dten\u00ed hierarchie, vytv\u00e1\u0159en\u00ed a maz\u00e1n\u00ed snapshot\u016f, dotazov\u00e1n\u00ed na informace o stroj\u00edch a mnoha (opravdu mnoha) dal\u0161\u00edch funkc\u00edch. Funkcionalita \u0159e\u0161en\u00ed je velmi rozs\u00e1hl\u00e1, proto v\u0161em, kte\u0159\u00ed maj\u00ed z\u00e1jem, mohu doporu\u010dit VMware vSphere API Reference pro verzi 5.5<\/u><\/a><\/noindex> a 6.0<\/u><\/a><\/noindex>. Pro aktu\u00e1ln\u011bj\u0161\u00ed verze je to snadno dostupn\u00e9 pomoc\u00ed vyhled\u00e1va\u010de.<\/p>\n

VIX API<\/strong>. \u010cern\u00e1 magie hypervizoru, pro kterou existuje samostatn\u00fd seznam chyb<\/u><\/a><\/noindex>. VMware API pro pr\u00e1ci se soubory na hostiteli bez p\u0159ipojen\u00ed k nim p\u0159es s\u00ed\u0165. Posledn\u00ed z\u00e1chrana, kdy\u017e je t\u0159eba um\u00edstit soubor do stroje, ke kter\u00e9mu nen\u00ed lep\u0161\u00ed zp\u016fsob komunikace. P\u0159in\u00e1\u0161\u00ed to bolest a tr\u00e1pen\u00ed, pokud je soubor velk\u00fd a hostitel je p\u0159et\u00ed\u017een. Ale zde plat\u00ed pravidlo, \u017ee i 56,6 kB\/s je lep\u0161\u00ed ne\u017e 0 kB\/s. V Hyper-V se podobn\u00e1 funkce naz\u00fdv\u00e1 PowerShell Direct. To v\u0161ak platilo pouze do p\u0159\u00edchodu<\/p>\n

vSphere Web Services API<\/strong> Od verze vSphere 6.0 (zhruba, proto\u017ee toto API bylo poprv\u00e9 p\u0159edstaveno ve verzi 5.5) se pou\u017e\u00edv\u00e1 pro pr\u00e1ci s hostovan\u00fdmi stroji a ji\u017e tak\u0159ka v\u0161ude vytla\u010dilo VIX. V podstat\u011b jde o dal\u0161\u00ed API pro spr\u00e1vu vSphere. Zaj\u00edmav\u00fdm doporu\u010duji prostudovat v\u00fdborn\u00fd<\/u><\/a><\/noindex> manu\u00e1l. <\/p>\n

VDDK<\/strong> (Virtual Disk Development Kit). Knihovna, o kter\u00e9 se \u010d\u00e1ste\u010dn\u011b hovo\u0159ilo v t\u00e9to \u010dl\u00e1nku<\/u><\/a><\/noindex>. Pou\u017e\u00edv\u00e1 se pro \u010dten\u00ed virtu\u00e1ln\u00edch disk\u016f. P\u0159ed d\u00e1vn\u00fdmi \u010dasy byla sou\u010d\u00e1st\u00ed VIX, ale postupem \u010dasu byla vy\u010dlen\u011bna do samostatn\u00e9ho produktu. Na opl\u00e1tku v\u0161ak jako n\u00e1stupce pou\u017e\u00edv\u00e1 stejn\u00e9 chybov\u00e9 k\u00f3dy jako VIX. Av\u0161ak z n\u011bjak\u00e9ho d\u016fvodu nen\u00ed v samotn\u00e9m SDK \u017e\u00e1dn\u00fd popis t\u011bchto chyb. Proto expertn\u00ed cestou bylo zji\u0161t\u011bno, \u017ee chyby VDDK s jin\u00fdmi k\u00f3dy jsou pouze p\u0159evodem z bin\u00e1rn\u00edho na des\u00edtkov\u00fd k\u00f3d. Skl\u00e1d\u00e1 se ze dvou \u010d\u00e1st\u00ed \u2013 prvn\u00ed polovina obsahuje nedokumentovan\u00e9 informace o kontextu, a druh\u00e1 \u010d\u00e1st jsou tradi\u010dn\u00ed chyby VIX\/VDDK. Nap\u0159\u00edklad, pokud vid\u00edme:<\/p>\n

VDDK chyba: 21036749815809.Nejednozna\u010dn\u00e1 chyba<\/code><\/p>\n

Pak to bez v\u00e1h\u00e1n\u00ed p\u0159evedeme na hex a dostaneme 132200000001. Neinformativn\u00ed za\u010d\u00e1tek 132200 prost\u011b vynech\u00e1me, a zbytek bude na\u0161\u00edm chybov\u00fdm k\u00f3dem (VDDK 1: Nezn\u00e1m\u00e1 chyba). O nej\u010dast\u011bj\u0161\u00edch chyb\u00e1ch VDDK se ned\u00e1vno hovo\u0159ilo v samostatn\u00e9m neaktu\u00e1ln\u00ed statistika<\/u><\/a><\/noindex>.<\/p>\n

Nyn\u00ed se pod\u00edvejme na Windows<\/strong>. <\/p>\n

Zde je v\u0161echno pot\u0159ebn\u00e9 a d\u016fle\u017eit\u00e9 pro n\u00e1s nalezen\u00ed ve standardn\u00edm Event Viewer<\/strong>. Ale je tu jeden h\u00e1\u010dek: podle star\u00e9 tradice Windows nezaznamen\u00e1v\u00e1 \u00fapln\u00fd text chyby, ale pouze jej\u00ed \u010d\u00edslo. Nap\u0159\u00edklad, chyba 5 je \u201eP\u0159\u00edstup odep\u0159en\u201d, a 1722 je \u201eRPC server nen\u00ed k dispozici\u201d, a 10060 je \u201eVypr\u0161en\u00ed \u010dasov\u00e9ho limitu p\u0159ipojen\u00ed\u201d. Samoz\u0159ejm\u011b, \u017ee je fajn, kdy\u017e si pamatujete ty nejzn\u00e1m\u011bj\u0161\u00ed, ale co d\u011blat s dosud nev\u00eddan\u00fdmi? <\/p>\n

Aby \u017eivot nebyl jen medem, chyby se tak\u00e9 ukl\u00e1daj\u00ed v hexadecim\u00e1ln\u00edm form\u00e1tu s prefixem 0x8007. Nap\u0159\u00edklad 0x8007000e \u2014 to je ve skute\u010dnosti 14, Out of Memory. Pro\u010d a pro koho to tak bylo ud\u011bl\u00e1no \u2014 z\u016fst\u00e1v\u00e1 z\u00e1hadou. Kompletn\u00ed seznam chyb si m\u016f\u017eete st\u00e1hnout zdarma a bez SMS z devcentra<\/u><\/a><\/noindex>.<\/p>\n

Mimochodem, n\u011bkdy se vyskytuj\u00ed i jin\u00e9 prefixy, nejen 0x8007. V tak smutn\u00e9 situaci je pro porozum\u011bn\u00ed HRESULT ('result handle') pot\u0159eba se je\u0161t\u011b hloub\u011bji pono\u0159it do dokumentaci<\/u><\/a><\/noindex> pro v\u00fdvoj\u00e1\u0159e. V b\u011b\u017en\u00e9m \u017eivot\u011b v\u00e1m to nedoporu\u010duji, ale pokud v\u00e1s na to zatla\u010dilo okol\u00ed nebo jste zv\u011bdav\u00ed, nyn\u00ed v\u00edte, co d\u011blat.<\/p>\n

Ale p\u00e1nov\u00e9 v Microsoftu se nad n\u00e1mi trochu smilovali a p\u0159edstavili sv\u011btu n\u00e1stroj ERR<\/u><\/a><\/noindex>. Je to mal\u00fd kousek konzolov\u00e9ho \u0161t\u011bst\u00ed, kter\u00fd um\u00ed p\u0159ekl\u00e1dat chybov\u00e9 k\u00f3dy do lidsk\u00e9ho jazyka bez pou\u017eit\u00ed Googlu. Funguje to zhruba takto.<\/p>\n

C:UsersrootDesktop>err.exe 0x54f\n# pro hex 0x54f \/ des\u00edtkov\u00fd 1359\n  ERROR_INTERNAL_ERROR                                           winerror.h\n# Do\u0161lo k intern\u00ed chyb\u011b.\n# jako HRESULT: Z\u00e1va\u017enost: \u00daSP\u011aCH (0), ZA\u0158\u00cdZEN\u00cd_NULL (0x0), K\u00f3d 0x54f\n# pro hex 0x54f \/ des\u00edtkov\u00fd 1359\n  ERROR_INTERNAL_ERROR                                           winerror.h\n# Do\u0161lo k intern\u00ed chyb\u011b.\n# 2 shody nalezeny pro \"0x54f\"<\/code><\/pre>\n
Vznik\u00e1 opr\u00e1vn\u011bn\u00e1 ot\u00e1zka: pro\u010d tedy hned do log\u016f nep\u00ed\u0161eme rozlu\u0161t\u011bn\u00ed, ale nech\u00e1v\u00e1me tyto tajemn\u00e9 k\u00f3dy? Odpov\u011b\u010f je v t\u0159et\u00edch stran\u00e1ch aplikac\u00ed. Kdy\u017e s\u00e1m vol\u00e1te n\u011bjak\u00fd WinAPI, nen\u00ed probl\u00e9m jeho odpov\u011b\u010f rozlu\u0161tit, proto\u017ee k tomu existuje speci\u00e1ln\u00ed WinAPI vol\u00e1n\u00ed. Ale jak ji\u017e bylo zm\u00edn\u011bno, do na\u0161ich log\u016f p\u0159ich\u00e1z\u00ed v\u0161echno, co k n\u00e1m p\u0159i odpov\u011bd\u00edch p\u0159ijde. A pro rozlu\u0161t\u011bn\u00ed by bylo nutn\u00e9 neust\u00e1le monitorovat tento tok v\u011bdom\u00ed, vyzved\u00e1vat kusy s chybami Windows, rozlu\u0161tit je a vlo\u017eit zp\u011bt. \u0158ekn\u011bme si na rovinu, nen\u00ed to zrovna nejz\u00e1bavn\u011bj\u0161\u00ed \u010dinnost.<\/p>\n
API pro spr\u00e1vu soubor\u016f Windows <\/strong>se vyu\u017e\u00edv\u00e1 p\u0159i pr\u00e1ci se soubory. Vytv\u00e1\u0159en\u00ed soubor\u016f, maz\u00e1n\u00ed, otev\u00edr\u00e1n\u00ed pro z\u00e1pis, pr\u00e1ce s atributy a tak d\u00e1le.<\/p>\n
V\u00fd\u0161e zm\u00edn\u011bn\u00fd PowerShell Direct<\/strong> jako ekvivalent VIX API ve sv\u011bt\u011b Hyper-V. Bohu\u017eel nen\u00ed tak flexibiln\u00ed: m\u00e1 spoustu omezen\u00ed ve funk\u010dnosti, nefunguje s ka\u017edou verz\u00ed hostitele a ur\u010dit\u011b ne se v\u0161emi hosty.<\/p>\n
RPC<\/strong> (Remote Procedure Call) Mysl\u00edm, \u017ee neexistuje nikdo, kdo by pracoval se syst\u00e9mem Windows a nevid\u011bl by chyby spojen\u00e9 s RPC. Navzdory popul\u00e1rn\u00edmu omylu to nen\u00ed jedin\u00fd protokol, ale jak\u00fdkoli klient-server protokol vyhovuj\u00edc\u00ed \u0159ad\u011b parametr\u016f. Pokud v\u0161ak v na\u0161ich logech najdeme chybu RPC, v 90 % p\u0159\u00edpad\u016f to bude chyba od Microsoft RPC, kter\u00fd je sou\u010d\u00e1st\u00ed DCOM (Distributed Component Object Model). Na internetu je k dispozici obrovsk\u00e9 mno\u017estv\u00ed dokumentace k tomuto t\u00e9matu, ale v\u011bt\u0161ina je zna\u010dn\u011b zastaral\u00e1. Pokud m\u00e1te v\u0161ak silnou touhu se tomu v\u011bnovat, mohu doporu\u010dit \u010dl\u00e1nky Co je RPC?<\/u><\/a><\/noindex>, Jak RPC funguje<\/u> <\/a><\/noindex>a dlouh\u00fd seznam chyb RPC<\/u><\/a><\/noindex>.<\/p>\n
Hlavn\u00ed p\u0159\u00ed\u010diny vzniku RPC chyb v na\u0161ich logech \u2014 to jsou ne\u00fasp\u011b\u0161n\u00e9 pokusy o interakci mezi komponentami VBR (server > proxy, nap\u0159\u00edklad) a v\u011bt\u0161inou kv\u016fli probl\u00e9m\u016fm s konektivitou.<\/p>\n
Nejz\u00e1va\u017en\u011bj\u0161\u00ed ze v\u0161ech z\u00e1va\u017en\u00fdch je chyba The RPC server is unavailable (1722). Jednodu\u0161e \u0159e\u010deno, klient se nemohl spojit se serverem. Pro\u010d a jak \u2014 na tuto ot\u00e1zku neexistuje jednozna\u010dn\u00e1 odpov\u011b\u010f, ale obvykle je to probl\u00e9m s autentizac\u00ed nebo s p\u0159\u00edstupem k portu 135. Posledn\u00ed zm\u00edn\u011bn\u00e9 je charakteristick\u00e9 pro infrastruktury s dynamick\u00fdm p\u0159id\u011blen\u00edm port\u016f. O tomto t\u00e9matu dokonce existuje samostatn\u00e1 KB<\/u><\/a><\/noindex>. A u Microsoftu \u2014 rozs\u00e1hl\u00fd pr\u016fvodce<\/u><\/a><\/noindex> k vyhled\u00e1v\u00e1n\u00ed p\u0159\u00ed\u010din poruchy.<\/p>\n
Druh\u00e1 nej\u010dast\u011bj\u0161\u00ed chyba: There are no more endpoints available from the endpoint mapper (1753). RPC klient nebo server se nedok\u00e1zali p\u0159i\u0159adit port. Obvykle se objevuje, kdy\u017e byl server (v na\u0161em p\u0159\u00edpad\u011b hostitelsk\u00fd stroj) nastaven na dynamick\u00e9 p\u0159i\u0159azov\u00e1n\u00ed port\u016f z \u00fazk\u00e9ho rozsahu, kter\u00fd se vy\u010derpal. A pokud se pod\u00edv\u00e1me ze strany klienta (v na\u0161em p\u0159\u00edpad\u011b VBR serveru), znamen\u00e1 to, \u017ee n\u00e1\u0161 VeeamVssAgent se nespustil nebo nebyl registrov\u00e1n jako RPC rozhran\u00ed. Na toto t\u00e9ma tak\u00e9 existuje samostatn\u00e1 KB<\/u><\/a><\/noindex>.<\/p>\n
No a abychom uzav\u0159eli Top-3 RPC chyb, vzpome\u0148me na RPC function call failed (1726). Tato chyba se objevuje, pokud bylo spojen\u00ed nav\u00e1z\u00e1no, ale RPC po\u017eadavky neprob\u00edhaj\u00ed. Nap\u0159\u00edklad \u017e\u00e1d\u00e1me informace o stavu VSS (co kdyby se zrovna nyn\u00ed prov\u00e1d\u011bla st\u00ednov\u00e1 kopie) a v odpov\u011bdi n\u00e1m p\u0159ich\u00e1z\u00ed ticho a ignorace.<\/p>\n
Windows Tape Backup API <\/strong>je pot\u0159eba pro pr\u00e1ci s p\u00e1sem knihoven nebo pohony. Jak jsem ji\u017e zm\u00ednil na za\u010d\u00e1tku: ps\u00e1t sv\u00e9 ovlada\u010de a pak se tr\u00e1pit s podporou ka\u017ed\u00e9ho za\u0159\u00edzen\u00ed, to n\u00e1s v\u016fbec net\u011b\u0161\u00ed. Proto Veeam nem\u00e1 \u017e\u00e1dn\u00e9 vlastn\u00ed ovlada\u010de. V\u0161echno jde p\u0159es standardn\u00ed API, jeho\u017e podporu implementuj\u00ed sami dodavatel\u00e9 hardwaru. Tak je to mnohem logi\u010dt\u011bj\u0161\u00ed, \u017ee?<\/p>\n
SMB\/CIFS<\/strong> V\u0161ichni je zvykl\u00ed ps\u00e1t vedle sebe, a\u010dkoli ne v\u0161ichni si pamatuj\u00ed, \u017ee CIFS (Common Internet File System) \u2014 to je jen soukrom\u00e1 verze SMB (Server Message Block). Tud\u00ed\u017e ve shrnut\u00ed t\u011bchto pojm\u016f nen\u00ed nic \u0161patn\u00e9ho. Samba \u2014 to je u\u017e realizace pro LinuxUnix, a tam existuj\u00ed sv\u00e9 specifika, ale to jsem se odml\u010del. D\u016fle\u017eit\u00e9 je, \u017ee kdy\u017e Veeam \u017e\u00e1d\u00e1 o z\u00e1pis n\u011b\u010deho prost\u0159ednictv\u00edm UNC cesty (serverdirectory), server pou\u017e\u00edv\u00e1 hierarchii ovlada\u010d\u016f souborov\u00e9ho syst\u00e9mu, v\u010detn\u011b mup a mrxsmb, k z\u00e1pisu na sd\u00edlen\u00ed. Podle toho budou tak\u00e9 tyto ovlada\u010de generovat chyby.<\/p>\n
Ned\u00e1 se obej\u00edt bez Winsock API<\/strong>. Pokud je pot\u0159eba n\u011bco ud\u011blat p\u0159es s\u00ed\u0165, VBR pracuje p\u0159es Windows Socket API, kter\u00e9 je v lidov\u00e9m n\u00e1zvoslov\u00ed zn\u00e1m\u00e9 jako Winsock. Tak\u017ee pokud vid\u00edme v logu p\u00e1r IP:Port, to je ono. V ofici\u00e1ln\u00ed dokumentaci je docela p\u011bkn\u00fd seznam mo\u017en\u00fdch chyb<\/u><\/a><\/noindex>.<\/p>\n
V\u00fd\u0161e zm\u00edn\u011bn\u00fd WMI<\/strong> (Windows Management Instrumentation) \u2014 je to v\u0161emocn\u00e9 API pro spr\u00e1vu v\u0161eho a v\u0161ech ve sv\u011bt\u011b Windows. Nap\u0159\u00edklad p\u0159i pr\u00e1ci s Hyper-V se t\u00e9m\u011b\u0159 v\u0161echny dotazy na hostitele prov\u00e1d\u011bj\u00ed p\u0159es n\u011bj. Jin\u00fdmi slovy, je to naprosto nenahraditeln\u00e9 a velmi mocn\u00e9 ve sv\u00fdch mo\u017enostech. P\u0159i pokusech o pomoc p\u0159i zji\u0161\u0165ov\u00e1n\u00ed, kde a co se pokazilo, velmi pom\u00e1h\u00e1 integrovan\u00fd n\u00e1stroj WBEMtest.exe.<\/p>\n
A posledn\u00ed v seznamu, ale zdaleka ne m\u00e9n\u011b v\u00fdznamn\u00fd \u2014 VSS<\/strong> (Volume Shadow Storage). Tato problematika je natolik nevy\u010derpateln\u00e1 a z\u00e1hadn\u00e1, kolik je o n\u00ed naps\u00e1no dokumentace. Shadow Copy lze nejl\u00e9pe ch\u00e1pat jako zvl\u00e1\u0161tn\u00ed typ snapshotu, kter\u00fdm v z\u00e1sad\u011b je. D\u00edky n\u011bmu lze ve VMware prov\u00e1d\u011bt aplikac\u00ed konzistentn\u00ed z\u00e1lohy, a v Hyper-V t\u00e9m\u011b\u0159 v\u0161echno. M\u00e1m v pl\u00e1nu napsat samostatn\u00fd \u010dl\u00e1nek s jakousi synt\u00e9zou o VSS, ale zat\u00edm si m\u016f\u017eete p\u0159e\u010d\u00edst tento popis<\/u><\/a><\/noindex>. Jen opatrn\u011b, proto\u017ee pokus o pochopen\u00ed VSS hned napoprv\u00e9 m\u016f\u017ee v\u00e9st k \u00faraz\u016fm hlavy.<\/p>\n
Na tom bych asi m\u011bl skon\u010dit. Pova\u017euji \u00fakol vysv\u011btlit nejz\u00e1kladn\u011bj\u0161\u00ed v\u011bci za spln\u011bn\u00fd, tak\u017ee v n\u00e1sleduj\u00edc\u00ed kapitole se u\u017e pod\u00edv\u00e1me na logy. Ale pokud m\u00e1te n\u011bjak\u00e9 dotazy, nev\u00e1hejte je vyj\u00e1d\u0159it v koment\u00e1\u0159\u00edch.<\/p>\n<\/p>\n
Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u0435\u043c \u043d\u0430\u0448\u0435 \u043f\u043e\u0433\u0440\u0443\u0436\u0435\u043d\u0438\u0435 \u0432 \u0443\u0432\u043b\u0435\u043a\u0430\u0442\u0435\u043b\u044c\u043d\u044b\u0439 \u043c\u0438\u0440 \u0433\u0430\u0434\u0430\u043d… \u0442\u0440\u0430\u0431\u043b\u0448\u0443\u0442\u0438\u043d\u0433\u0430 \u043f\u043e \u043b\u043e\u0433\u0430\u043c. \u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043c\u044b \u0434\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438\u0441\u044c \u043e \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0438 \u0431\u0430\u0437\u043e\u0432\u044b\u0445 \u0442\u0435\u0440\u043c\u0438\u043d\u043e\u0432 \u0438 \u043e\u0434\u043d\u0438\u043c \u0433\u043b\u0430\u0437\u043a\u043e\u043c \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043b\u0438 \u043e\u0431\u0449\u0443\u044e \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 Veeam, \u043a\u0430\u043a \u0435\u0434\u0438\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f. \u0417\u0430\u0434\u0430\u0447\u0430 \u043d\u0430 \u044d\u0442\u0443 — \u0440\u0430\u0437\u043e\u0431\u0440\u0430\u0442\u044c\u0441\u044f \u043a\u0430\u043a \u0444\u043e\u0440\u043c\u0438\u0440\u0443\u044e\u0442\u0441\u044f \u043b\u043e\u0433 \u0444\u0430\u0439\u043b\u044b, \u0447\u0442\u043e \u0437\u0430 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044f \u0432 \u043d\u0438\u0445 \u043e\u0442\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u0430 \u0438 \u043f\u043e\u0447\u0435\u043c\u0443 \u043e\u043d\u0438 \u0432\u044b\u0433\u043b\u044f\u0434\u044f\u0442 \u043a\u0430\u043a \u0432\u044b\u0433\u043b\u044f\u0434\u044f\u0442. \u041a\u0430\u043a \u0432\u044b \u0434\u0443\u043c\u0430\u0435\u0442\u0435, \u0447\u0442\u043e \u0432\u043e\u043e\u0431\u0449\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":97730,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-97729","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Odkud se berou logy? Veeam Log Diving | ProHoster","description":"Pokra\u010dujeme v na\u0161em hlubok\u00e9m pono\u0159en\u00ed do fascinuj\u00edc\u00edho sv\u011bta vykl\u00e1d\u00e1n\u00ed...","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/otkuda-berutsya-logi-veeam-log-diving","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\u041e\u0442\u043a\u0443\u0434\u0430 \u0431\u0435\u0440\u0443\u0442\u0441\u044f \u043b\u043e\u0433\u0438? Veeam Log Diving | ProHoster","og:description":"\u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u0435\u043c \u043d\u0430\u0448\u0435 \u043f\u043e\u0433\u0440\u0443\u0436\u0435\u043d\u0438\u0435 \u0432 \u0443\u0432\u043b\u0435\u043a\u0430\u0442\u0435\u043b\u044c\u043d\u044b\u0439 \u043c\u0438\u0440 \u0433\u0430\u0434\u0430\u043d...","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/otkuda-berutsya-logi-veeam-log-diving","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-10-21T06:42:22+00:00","article:modified_time":"2020-10-21T06:42:22+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"97729","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 10:14:39","updated":"2022-09-30 13:30:55","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\/97729","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=97729"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/97729\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/97730"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=97729"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=97729"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=97729"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}