{"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\/lv\/blog\/administrirovanie\/otkuda-berutsya-logi-veeam-log-diving","title":{"rendered":"K\u0101 rodas \u017eurn\u0101li? Veeam Log Diving","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"K\u0101<\/p>\n

Turpin\u0101m m\u016bsu iepaz\u012b\u0161anos ar aizraujo\u0161o \u017eongl\u0113\u0161anas pasauli... trauc\u0113jummekl\u0113\u0161an\u0101, izmantojot \u017eurn\u0101lus. T\u0101tad, iepriek\u0161\u0113j\u0101 rakst\u0101<\/a><\/noindex> m\u0113s vienoj\u0101mies par pamatterminu noz\u012bmi un iepazin\u0101mies ar Veeam kop\u0113j\u0101s strukt\u016bras visp\u0101r\u012bgo ainu k\u0101 vienota lietojumprogramma. Uzdevums \u0161aj\u0101\u2009\u2014\u2009izprast, k\u0101 veidojas \u017eurn\u0101lfaili, k\u0101da inform\u0101cija tajos atspogu\u013cota un k\u0101p\u0113c tie izskat\u0101s tie\u0161i t\u0101.<\/p>\n

K\u0101 j\u016bs dom\u0101jat, kas visp\u0101r ir \u0161ie \u00ab\u017eurn\u0101li\u00bb? Liel\u0101k\u0101s da\u013cas uzskatos \u017eurn\u0101liem jebkur\u0101 lietojum\u0101 j\u0101b\u016bt visvarenai b\u016btnei, kas liel\u0101ko da\u013cu laika ir kaut kur aizmirsta, bet nepiecie\u0161am moments izn\u0101k no nekurienes sp\u012bdo\u0161os bru\u0146\u0101s un visus gl\u0101bj. Tas ir, tajos j\u0101b\u016bt visam, s\u0101kot no s\u012bk\u0101kaj\u0101m k\u013c\u016bd\u0101m katr\u0101 komponent\u0101 l\u012bdz atsevi\u0161\u0137\u0101m datu b\u0101zes transakcij\u0101m. Un t\u0101, lai p\u0113c k\u013c\u016bdas nekav\u0113joties tiktu pierakst\u012bts k\u0101 v\u0113l to labot. Un visam \u0161im j\u0101iek\u013caujas p\u0101ris megabaitos, ne vair\u0101k. Tas ta\u010du ir tikai teksts! Teksta faili ta\u010du nevar aiz\u0146emt desmitiem gigabaitu, es kaut kur to dzird\u0113ju!<\/p>\n

T\u0101tad, lo\u0123i.<\/h2>\n

Re\u0101laj\u0101 pasaul\u0113 lo\u0123i ir tikai diagnostikas inform\u0101cijas arh\u012bvs. Un ko taj\u0101 uzglab\u0101t, no kurienes \u0146emt inform\u0101ciju uzglab\u0101\u0161anai un cik detaliz\u0113tai tai j\u0101b\u016bt, izl\u0113mj pa\u0161i izstr\u0101d\u0101t\u0101ji. K\u0101ds iet minim\u0101lisma ce\u013cu, uzglab\u0101jot iesl\u0113g\u0161anas\/izsl\u0113g\u0161anas l\u012bme\u0146a ierakstus, bet k\u0101ds cent\u012bgi sakr\u0101jas visam, ko vien var aizsniegt. Tom\u0113r ir ar\u012b starpvariantu ar iesp\u0113ju izv\u0113l\u0113ties t\u0101 saukto Logging Level, kad j\u016bs pats nor\u0101d\u0101t, cik detaliz\u0113tu inform\u0101ciju v\u0113laties uzglab\u0101t un cik daudz lieka vieta jums ir diskos =) VBR ir pat se\u0161i \u0161\u0101di l\u012bme\u0146i, starp citu. Un, ticiet man, j\u016bs nev\u0113laties redz\u0113t, kas notiek, kad logi ir maksim\u0101li detaliz\u0113ti, ar br\u012bvu vietu j\u016bsu disk\u0101.<\/p>\n

Labi. M\u0113s apm\u0113ram saprat\u0101m, ko v\u0113lamies saglab\u0101t, bet rodas likum\u012bgs jaut\u0101jums: no kurienes \u0146emt \u0161o inform\u0101ciju? Da\u013cu notikumu \u017eurn\u0101lfailiem, protams, veidojam m\u0113s pa\u0161i ar m\u016bsu iek\u0161\u0113j\u0101m proced\u016br\u0101m. Bet ko dar\u012bt, kad notiek mijiedarb\u012bba ar \u0101r\u0113jo vidi? Lai nenon\u0101ktu \u0137\u0113d\u0113 no pagarin\u0101jumiem un velosip\u0113diem, Veeam ir tendence neizdom\u0101t jau izgudrotus risin\u0101jumus. Vienm\u0113r, kad ir jau gatavs API, ieb\u016bv\u0113ta sist\u0113mas funkcija, bibliot\u0113ka utt., m\u0113s dodam priek\u0161roku gataviem risin\u0101jumiem, pirms s\u0101kam veidot savas sare\u017e\u0123\u012bt\u0101s idejas. Tom\u0113r t\u0101du nav maz. T\u0101d\u0113\u013c analiz\u0113jot \u017eurn\u0101lus ir svar\u012bgi izprast, ka liel\u0101k\u0101 da\u013ca k\u013c\u016bdu attiecas uz pazi\u0146ojumiem no tre\u0161o pu\u0161u API, sist\u0113mas izsaukumiem un cit\u0101m bibliot\u0113k\u0101m. \u0160aj\u0101 gad\u012bjum\u0101 VBR loma ir \u0161o k\u013c\u016bdu p\u0101rs\u016bt\u012b\u0161ana \u017eurn\u0101lfailos t\u0101d\u0101 veid\u0101, k\u0101 t\u0101s ir. Pamatuzdevums lietot\u0101jam ir iem\u0101c\u012bties saprast, kura rindi\u0146a ir no k\u0101, un par ko atbild \u0161is \u201ck\u0101ds\u201d. T\u0101d\u0113\u013c, ja k\u013c\u016bdas kods no VBR \u017eurn\u0101la j\u016bs noved pie MSDN lapas, tas ir norm\u0101li un pareizi.<\/p>\n

K\u0101 m\u0113s bij\u0101m vienoju\u0161ies iepriek\u0161: Veeam ir t\u0101 saucam\u0101 SQL b\u0101zes lietojumprogramma. Tas noz\u012bm\u0113, ka visas iestat\u012bjumi, visa inform\u0101cija un visp\u0101r viss, kas nepiecie\u0161ams norm\u0101lai darb\u012bbai, tiek uzglab\u0101ts taj\u0101 b\u0101z\u0113. No t\u0101 izriet vienk\u0101r\u0161a paties\u012bba: tas, kas nav \u017eurn\u0101los, visticam\u0101k, ir b\u0101z\u0113. Bet tas nav sudraba lod\u012bte: da\u017eas lietas nav ne lok\u0101lajos Veeam komponentu \u017eurn\u0101los, ne t\u0101s b\u0101z\u0113. T\u0101p\u0113c j\u0101iem\u0101c\u0101s izp\u0113t\u012bt saimniekcomputeru \u017eurn\u0101lus, lok\u0101l\u0101s ma\u0161\u012bnas \u017eurn\u0101lus un visus \u017eurn\u0101lus, kas piedal\u0101s dubl\u0113\u0161anas un atjauno\u0161anas proces\u0101. Gad\u0101s ar\u012b t\u0101, ka nepiecie\u0161am\u0101 inform\u0101cija nav nek\u0101d\u0101 viet\u0101. \u0160\u0101ds ir ce\u013c\u0161. <\/p>\n

Da\u017ei piem\u0113ri \u0161\u0101diem API<\/h4>\n

\u0160is saraksts neizvirza m\u0113r\u0137i b\u016bt iz\u0146\u0113muma piln\u012bbai, t\u0101p\u0113c nevajag taj\u0101 mekl\u0113t p\u0113d\u0113jo instanci. T\u0101 uzdevums — tikai par\u0101d\u012bt visbie\u017e\u0101k izmantot\u0101s tre\u0161o pu\u0161u API un tehnolo\u0123ijas, kas tiek lietotas m\u016bsu produktos.<\/p>\n

S\u0101ksim ar VMware<\/strong>. <\/p>\n

Pirmais sarakst\u0101 b\u016bs vSphere API<\/strong>. Tiek izmantots autentifik\u0101cijai, hierarhijas las\u012b\u0161anai, snapshots veido\u0161anai un dz\u0113\u0161anai, inform\u0101cijas piepras\u012b\u0161anai par ma\u0161\u012bn\u0101m un daudz\u0101m (\u013coti daudz\u0101m) cit\u0101m liet\u0101m. Risin\u0101juma funkcionalit\u0101te ir \u013coti pla\u0161a, t\u0101p\u0113c ikvienam interesentam varu ieteikt  VMware vSphere API Reference attiec\u012bgai versijai. 5.5<\/u><\/a><\/noindex> un 6.0<\/u><\/a><\/noindex>. Jaun\u0101k\u0101s versijas ir viegli samekl\u0113jamas, izmantojot mekl\u0113t\u0101ju.<\/p>\n

VIX API<\/strong>. Melnais burv\u012bba hipervizora, kam ir atsevi\u0161\u0137s k\u013c\u016bdu saraksts<\/u><\/a><\/noindex>. VMware API, lai str\u0101d\u0101tu ar failiem uz mitin\u0101t\u0101ja bez piek\u013cuves tiem t\u012bkl\u0101. Beigu variants, kad j\u0101ievieto fails ma\u0161\u012bn\u0101, kurai nav lab\u0101ka sakaru kan\u0101la. Tas rada s\u0101pes un cie\u0161anas, ja fails ir liels, bet mitin\u0101t\u0101js ir noslogots. Bet \u0161eit darbojas likums, ka pat 56,6 Kb\/s ir lab\u0101k nek\u0101 0 Kb\/s. Hyper-V \u0161\u0101ds risin\u0101jums tiek saukts par PowerShell Direct. Bet tas bija sp\u0113k\u0101 tikai l\u012bdz<\/p>\n

vSphere Web Services API<\/strong> . S\u0101kot ar vSphere 6.0 (apm\u0113ram, jo \u0161is API pirmo reizi tika ieviests versij\u0101 5.5), to izmanto, lai str\u0101d\u0101tu ar viesu ma\u0161\u012bn\u0101m, un tas jau praktiski visur ir nomain\u012bjis VIX. Paties\u012bb\u0101 tas ir v\u0113l viens API vSphere p\u0101rvald\u012bbai. Interesentiem varu ieteikt izp\u0113t\u012bt izcilu<\/u><\/a><\/noindex> rokasgr\u0101matu. <\/p>\n

VDDK<\/strong> \uff08Virtual Disk Development Kit). Bibliot\u0113ka, par kuru da\u013c\u0113ji run\u0101ts \u0161aj\u0101 rakst\u0101<\/u><\/a><\/noindex>. Tiek izmantots virtu\u0101lo disku las\u012b\u0161anai. Tolaik tas bija da\u013ca no VIX, tom\u0113r gadu gait\u0101 tas tika izdal\u012bts k\u0101 atsevi\u0161\u0137s produkts. Bet k\u0101 mantinieks tas izmanto tos pa\u0161us k\u013c\u016bdu kodus, k\u0101 VIX.  Ta\u010du k\u0101da iemesla d\u0113\u013c pa\u0161\u0101 SDK nav nek\u0101da \u0161\u012bs k\u013c\u016bdas apraksta. T\u0101p\u0113c pieredz\u0113ju\u0161i izzin\u0101t\u0101ji ir secin\u0101ju\u0161i, ka VDDK k\u013c\u016bdas ar citiem kodiem — ir tikai bin\u0101r\u0101 koda un desmitisk\u0101 koda tulkojums. Tas sast\u0101v no div\u0101m da\u013c\u0101m \u2013 pirm\u0101 puse ir nedokument\u0113ta inform\u0101cija par kontekstu, bet otr\u0101 da\u013ca ir tradicion\u0101l\u0101s VIX\/VDDK k\u013c\u016bdas. Piem\u0113ram, ja redzam:<\/p>\n

VDDK k\u013c\u016bda: 21036749815809. Nezin\u0101ma k\u013c\u016bda<\/code><\/p>\n

Tad dro\u0161i konvert\u0113jam to hex un ieg\u016bstam 132200000001. Neinformat\u012bvo s\u0101kumu 132200 vienk\u0101r\u0161i izsl\u0113dzam, un atlikums b\u016bs m\u016bsu k\u013c\u016bdas kods (VDDK 1: Nezin\u0101ma k\u013c\u016bda). Par visbie\u017e\u0101k sastopamaj\u0101m VDDK k\u013c\u016bd\u0101m nesen tika rakst\u012bts atsevi\u0161\u0137s raksts<\/u><\/a><\/noindex>.<\/p>\n

Tagad apl\u016bkosim Windows<\/strong>. <\/p>\n

. \u0160eit visu nepiecie\u0161amo un svar\u012bgo var atrast standart\u0101 Event Viewer<\/strong>. Bet ir viena probl\u0113ma: p\u0113c senas trad\u012bcijas Windows re\u0123istr\u0113 ne pilnu k\u013c\u016bdas tekstu, bet tikai t\u0101s numuru. Piem\u0113ram, k\u013c\u016bda 5 — tas ir \u201cPiek\u013cuve noraid\u012bta\u201d, bet 1722 — tas ir \u201cRPC serveris nav pieejams\u201d, un 10060 — tas ir \u201cSavienojuma laiks ir beidzies\u201d. Protams, tas ir lieliski, ja tu atceries viszin\u0101m\u0101k\u0101s, bet k\u0101 b\u016bt ar iepriek\u0161 neredz\u0113t\u0101m? <\/p>\n

Lai dz\u012bve neb\u016btu p\u0101r\u0101k salda, k\u013c\u016bdas tiek saglab\u0101tas ar\u012b se\u0161padsmitniek\u0101 ar prefiksu 0x8007. Piem\u0113ram, 0x8007000e \u2014 tas paties\u012bb\u0101 ir 14, Out of Memory. K\u0101p\u0113c un kam tas tika izdar\u012bts \u2014 paliek nosl\u0113pums. Tom\u0113r pilnu k\u013c\u016bdu sarakstu var bez maksas un bez SMS lejupiel\u0101d\u0113t no att\u012bst\u012bbas centra<\/u><\/a><\/noindex>.<\/p>\n

J\u0101atz\u012bm\u0113, ka da\u017ereiz sastopami ar\u012b citi prefiksi, ne tikai 0x8007. \u0160\u0101d\u0101 skumj\u0101 situ\u0101cij\u0101, lai saprastu HRESULT (\u201cresult handle\u201d), ir j\u0101iedzi\u013cin\u0101s v\u0113l dzi\u013c\u0101k dokumenti<\/u><\/a><\/noindex> izstr\u0101d\u0101t\u0101jiem. Ikdien\u0101 to nevar\u0113tu ieteikt, bet ja nu gad\u012btos st\u0101v\u0113t pie sienas vai vienk\u0101r\u0161i interes\u0113, tagad j\u016bs zin\u0101t, ko dar\u012bt.<\/p>\n

Tom\u0113r Microsoft kol\u0113\u0123i nedaudz sauso\u0161i ieteica mums un par\u0101d\u012bja pasaulei r\u012bku ERR<\/u><\/a><\/noindex>. Tas ir neliels konsoles prieks, kas sp\u0113j p\u0101rv\u0113rst k\u013c\u016bdu kodus cilv\u0113ku valod\u0101, neizmantojot Google. Tas darbojas apm\u0113ram \u0161\u0101di.<\/p>\n

C:UsersrootDesktop>err.exe 0x54f\n# heksadecim\u0101lais 0x54f \/ decim\u0101lais 1359\n  ERROR_INTERNAL_ERROR                                           winerror.h\n# Iek\u0161\u0113ja k\u013c\u016bda notika.\n# k\u0101 HRESULT: Smagums: VEIKSME (0), FACILITY_NULL (0x0), Kods 0x54f\n# heksadecim\u0101lais 0x54f \/ decim\u0101lais 1359\n  ERROR_INTERNAL_ERROR                                           winerror.h\n# Iek\u0161\u0113ja k\u013c\u016bda notika.\n# 2 sakrit\u012bbas atrastas \"0x54f\"<\/code><\/pre>\n
Rod\u0101s pamatots jaut\u0101jums: k\u0101p\u0113c m\u0113s uzreiz neierakst\u0101m lo\u0123os at\u0161ifr\u0113jumu, bet atst\u0101jam \u0161os nosl\u0113pumainos kodus? Atbilde ir tre\u0161\u0101s puses lietojumprogramm\u0101s. Kad j\u016bs pa\u0161i veicat k\u0101du WinAPI izsaukumu, t\u0101 at\u0161ifr\u0113\u0161ana nav gr\u016bta, jo tam ir pat speci\u0101ls WinAPI izsaukums. Bet, k\u0101 jau min\u0113ts, m\u016bsu lo\u0123os non\u0101k viss, kas vien pien\u0101k pie mums atbild\u0113s. Un \u0161eit jau at\u0161ifr\u0113\u0161anai b\u016btu past\u0101v\u012bgi j\u0101mudina \u0161is apzi\u0146as pl\u016bsmas straume, j\u0101izvelk no t\u0101s gabali ar Windows k\u013c\u016bd\u0101m, j\u0101at\u0161ifr\u0113 tos un j\u0101ievieto atpaka\u013c. God\u012bgi sakot, tas nav pats aizraujo\u0161\u0101kais darbs.<\/p>\n
Windows failu p\u0101rvald\u012bbas API <\/strong>vis\u0101di tiek izmantots, str\u0101d\u0101jot ar failiem. Failu izveide, dz\u0113\u0161ana, atv\u0113r\u0161ana rakst\u012b\u0161anai, darbs ar atrib\u016btiem un t\u0101 t\u0101l\u0101k.<\/p>\n
Iepriek\u0161 min\u0113tais PowerShell Direct<\/strong> k\u0101 VIX API analoga Hyper-V pasaul\u0113. Diem\u017e\u0113l ne tik elast\u012bgs: daudzas funkcionalit\u0101tes ierobe\u017eojumi, nedarbojas ar katru hosta versiju un t\u0101lu ne ar visiem viesiem.<\/p>\n
RPC<\/strong> (T\u0101l\u0101 proced\u016bru izsauk\u0161ana) Es uzskatu, ka nav neviena cilv\u0113ka, kur\u0161 b\u016btu str\u0101d\u0101jis ar Windows un neb\u016btu redz\u0113jis k\u013c\u016bdas, kas saist\u012btas ar RPC. Neskatoties uz pla\u0161i izplat\u012bto mald\u012bgo priek\u0161statu, tas nav viens protokols, bet jebkur\u0161 klients-serveris protokols, kas atbilst noteiktiem parametriem. Tom\u0113r, ja m\u016bsu \u017eurn\u0101los ir RPC k\u013c\u016bda, 90% gad\u012bjumu t\u0101 b\u016bs k\u013c\u016bda no Microsoft RPC, kas ir da\u013ca no DCOM (Distrib\u016btu komponentu objektu modelis).  Internet\u0101 ir pieejama milz\u012bga dokument\u0101cija \u0161aj\u0101 jom\u0101, tom\u0113r liela da\u013ca no t\u0101s ir diezgan novecojusi. Bet, ja ir liela v\u0113lme izp\u0113t\u012bt t\u0113mu, varu ieteikt rakstus Kas ir RPC?<\/u><\/a><\/noindex>, K\u0101 RPC darbojas<\/u> <\/a><\/noindex>un gar\u0161 saraksts RPC k\u013c\u016bd\u0101m<\/u><\/a><\/noindex>.<\/p>\n
Galvenie RPC k\u013c\u016bdu c\u0113lo\u0146i m\u016bsu \u017eurn\u0101los ir neveiksm\u012bgi m\u0113\u0123in\u0101jumi sazin\u0101ties starp VBR komponentiem (serveris > proxy, piem\u0113ram) un visbie\u017e\u0101k radu\u0161\u0101s sakaru probl\u0113mu d\u0113\u013c.<\/p>\n
Vado\u0161\u0101 k\u013c\u016bda starp vis\u0101m k\u013c\u016bd\u0101m ir k\u013c\u016bda The RPC server is unavailable (1722). Piem\u0113rojot vienk\u0101r\u0161u valodu, klients nesp\u0113ja izveidot savienojumu ar serveri. K\u0101p\u0113c un k\u0101 \u2014 vienota atbilde nav, ta\u010du parasti tas ir autentifik\u0101cijas vai t\u012bkla piek\u013cuves probl\u0113mas d\u0113\u013c l\u012bdz portam 135. Tas ir \u012bpa\u0161i rakstur\u012bgi infrastrukt\u016br\u0101m ar dinamisku portu pie\u0161\u0137ir\u0161anu. Par \u0161o t\u0113mu ir pat \u012bpa\u0161a KVP.<\/u><\/a><\/noindex>. T\u0101s Microsoft pla\u0161s ce\u013cvedis<\/u><\/a><\/noindex> pa c\u0113lo\u0146u mekl\u0113\u0161anu.<\/p>\n
Otr\u0101 popul\u0101r\u0101k\u0101 k\u013c\u016bda ir: There are no more endpoints available from the endpoint mapper (1753). RPC klients vai serveris nesp\u0113ja pie\u0161\u0137irt sev portu. Parasti tas notiek, kad serveris (m\u016bsu gad\u012bjum\u0101 viesma\u0161\u012bna) ir iestat\u012bts uz dinamisku portu pie\u0161\u0137ir\u0161anu no ierobe\u017eota diapazona, kas ir beidzies. Bet, ja uz to raug\u0101mies no klienta puses (m\u016bsu gad\u012bjum\u0101 VBR servera), tas noz\u012bm\u0113, ka m\u016bsu VeeamVssAgent vai nu nes\u0101ka darboties, vai netika re\u0123istr\u0113ts k\u0101 RPC interfeiss. Par \u0161o t\u0113mu ir ar\u012b \u012bpa\u0161a KVP.<\/u><\/a><\/noindex>.<\/p>\n
Un, lai pabeigtu Top-3 RPC k\u013c\u016bdas, atcer\u0113simies RPC function call failed (1726). \u0160\u012b k\u013c\u016bda par\u0101d\u0101s, ja savienojums tika izveidots, bet RPC piepras\u012bjumi netiek izpild\u012bti. Piem\u0113ram, m\u0113s piepras\u0101m inform\u0101ciju par VSS statusu (ja p\u0113k\u0161\u0146i tur tie\u0161i tagad tiek veidota \u0161edokopija, bet m\u0113s cen\u0161amies piek\u013c\u016bt), bet atbildes nav, tikai klusums un ignor\u0113\u0161ana.<\/p>\n
Windows Tape Backup API <\/strong>ir nepiecie\u0161ams darbam ar lenti\u0146bibliot\u0113k\u0101m vai dzin\u0113jiem. K\u0101 es min\u0113ju s\u0101kum\u0101: rakst\u012bt savus draiverus un p\u0113c tam moc\u012bties ar katra ier\u012bces atbalsta organiz\u0113\u0161anu nav nek\u0101das baudas. T\u0101p\u0113c vima nav savu draiveru. Viss notiek caur standarta API, kura atbalstu \u012bsteno pa\u0161i aparat\u016bras pieg\u0101d\u0101t\u0101ji. T\u0101 ir daudz lo\u0123isk\u0101k, vai ne?<\/p>\n
SMB\/CIFS<\/strong> Visi to raksta blakus, lai gan t\u0101lu ne visi atceras, ka CIFS (Common Internet File System) \u2014 tas ir vienk\u0101r\u0161i priv\u0101ta versija SMB (Server Message Block). T\u0101d\u0113j\u0101di nav nek\u0101 slikta, apkopojot \u0161os j\u0113dzienus. \u0160eit Samba \u2014 jau Linux\/Unix realiz\u0101cija, un tur ir savas \u012bpatn\u012bbas, bet es novirzos no t\u0113mas. Kas ir svar\u012bgi: kad Veeam l\u016bdz ierakst\u012bt kaut ko pa UNC ce\u013cu (serverdirectory), serveris izmanto failu sist\u0113mas draiveru hierarhiju, tostarp mup un mrxsmb, lai ierakst\u012btu krav\u0101. Attiec\u012bgi, k\u013c\u016bdas rad\u012bsies ar\u012b \u0161ie draiveri.<\/p>\n
Nemaz nevar iztikt bez Winsock API<\/strong>. Ja kaut kas j\u0101dara caur t\u012bklu, VBR str\u0101d\u0101 caur Windows Socket API, taut\u0101 paz\u012bstams k\u0101 Winsock. T\u0101p\u0113c, ja log\u0101 redzam IP:Port p\u0101ri, tas ir tas. Ofici\u0101laj\u0101 dokument\u0101cij\u0101 ir labs saraksts ar iesp\u0113jamiem k\u013c\u016bdas<\/u><\/a><\/noindex>.<\/p>\n
Iepriek\u0161 min\u0113tais WMI<\/strong> (Windows Management Instrumentation) \u2014 tas ir visaptvero\u0161s API, lai p\u0101rvald\u012btu visu un visus Windows pasaul\u0113. Piem\u0113ram, str\u0101d\u0101jot ar Hyper-V, gandr\u012bz visi piepras\u012bjumi uz hosta pusi notiek tie\u0161i caur to. Citiem v\u0101rdiem sakot, tas ir piln\u012bgi neaizst\u0101jams un \u013coti jaud\u012bgs sav\u0101s iesp\u0113j\u0101s. M\u0113\u0123inot noskaidrot, kur un kas ir nojucis, \u013coti pal\u012bdz ieb\u016bv\u0113tais r\u012bks WBEMtest.exe.<\/p>\n
Un p\u0113d\u0113jais sarakst\u0101, bet ne maz\u0101k svar\u012bgs \u2014 VSS<\/strong> (Volume Shadow Storage). \u0160is temats ir tik bezgal\u012bgs un nosl\u0113pumains, cik daudz par to ir uzrakst\u012bts dokument\u0101cijas. Shadow Copy visviegl\u0101k ir saprast k\u0101 \u012bpa\u0161u tipa snap\u0161otu, ar ko tas faktiski ir. Pateicoties tam, VMware var veikt lietojumprogrammu saska\u0146otus dubl\u0113jumus, bet Hyper-V visp\u0101r gandr\u012bz visu. Man ir pl\u0101nos izveidot atsevi\u0161\u0137u rakstu ar k\u0101du izvilkumu par VSS, bet pagaid\u0101m varat izm\u0113\u0123in\u0101t izlas\u012bt \u0161o aprakstu<\/u><\/a><\/noindex>. Tikai uzman\u012bgi, jo m\u0113\u0123in\u0101t saprast VSS no pirm\u0101 izskata var izrais\u012bt smadze\u0146u traumas.<\/p>\n
Uz \u0161o, dom\u0101ju, varam apst\u0101ties. Uzdevumu izskaidrot visus pamata aspektus uzskatu par izpild\u012btu, t\u0101p\u0113c n\u0101kamaj\u0101 noda\u013c\u0101 jau skat\u012bsimies uz \u017eurn\u0101liem. Bet, ja ir paliku\u0161i jaut\u0101jumi, tad nekautr\u0113jieties tos izteikt koment\u0101r\u0101.<\/p>\n<\/p>\n
Avots: 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\udd47No kurienes n\u0101k \u017eurn\u0101li? Veeam Log Diving | ProHoster","description":"Turpin\u0101m m\u016bsu iegremd\u0113\u0161anos aizraujo\u0161aj\u0101 burvju pasaul\u0113...","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/otkuda-berutsya-logi-veeam-log-diving","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","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\/lv\/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\/lv\/wp-json\/wp\/v2\/posts\/97729","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=97729"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/97729\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/97730"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=97729"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=97729"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=97729"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}