{"id":92367,"date":"2020-08-26T07:42:09","date_gmt":"2020-08-26T05:42:09","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh"},"modified":"2020-08-26T07:42:09","modified_gmt":"2020-08-26T05:42:09","slug":"putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh","title":{"rendered":"Sprievodca z\u00e1lohovan\u00edm datab\u00e1z","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<blockquote><p>\u2013 O, \u017eiadne \u00fato\u010disko nepre\u017eije z\u00e1sah meteoritu. Ale ako ka\u017ed\u00fd, aj vy m\u00e1te rezervu, tak\u017ee sa nemus\u00edte ob\u00e1va\u0165.<\/p>\n<p><i>Stanislav Lem, \u201eHviezdne denn\u00edky Ijona Tich\u00e9ho\u201c<\/i><\/p><\/blockquote>\n<p>\nZ\u00e1lohovanie znamen\u00e1 uchovanie k\u00f3pie \u00fadajov niekde mimo hlavn\u00e9ho miesta ich ulo\u017eenia.<\/p>\n<p><img decoding=\"async\" alt=\"Sprievodca z\u00e1lohovan\u00edm datab\u00e1z\" src=\"\/wp-content\/uploads\/2020\/08\/c1dba0d8999cab69315560dfc57546e0.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nHlavn\u00fdm cie\u013eom z\u00e1lohovania je obnovenie \u00fadajov po ich strate. V s\u00favislosti s t\u00fdm sa \u010dasto po\u010duje, \u017ee pri existencii repliky datab\u00e1zy je mo\u017en\u00e9 v\u017edy obnovi\u0165 \u00fadaje z nej, a z\u00e1lohovanie nie je potrebn\u00e9. V skuto\u010dnosti v\u0161ak z\u00e1lohovanie umo\u017e\u0148uje vyrie\u0161i\u0165 minim\u00e1lne tri \u00falohy, ktor\u00e9 nie je mo\u017en\u00e9 vyrie\u0161i\u0165 pomocou repliky, a replik\u00e1ciu bez z\u00e1lohy nie je mo\u017en\u00e9 inicializova\u0165.<\/p>\n<p>Po prv\u00e9, z\u00e1loh sa m\u00f4\u017ee vyu\u017ei\u0165 na obnovenie \u00fadajov po logickej chybe. Napr\u00edklad, ak \u00fa\u010dtovn\u00edk odstr\u00e1ni skupinu transakci\u00ed, alebo administr\u00e1tor DB zni\u010d\u00ed tabu\u013ekov\u00fd priestor. Obe oper\u00e1cie s\u00fa z poh\u013eadu datab\u00e1zy \u00faplne legit\u00edmne a proces replik\u00e1cie ich reprodukuje v repre datab\u00e1ze.<\/p>\n<p>Po druh\u00e9, modern\u00e9 S\u00daDB s\u00fa ve\u013emi spo\u013eahliv\u00e9 softv\u00e9rov\u00e9 syst\u00e9my, av\u0161ak ob\u010das m\u00f4\u017ee d\u00f4js\u0165 k po\u0161kodeniu vn\u00fatorn\u00fdch \u0161trukt\u00far datab\u00e1zy, po ktorom d\u00f4jde k strate pr\u00edstupu k \u00fadajom. \u010co je obzvl\u00e1\u0161\u0165 z\u00fafal\u00e9, toto poru\u0161enie sa zvy\u010dajne deje pri vysokom za\u0165a\u017een\u00ed alebo pri in\u0161tal\u00e1cii nejak\u00e9ho updatu. Ale ako vysok\u00e9 za\u0165a\u017eenie, tak pravideln\u00e9 aktualiz\u00e1cie nazna\u010duj\u00fa, \u017ee datab\u00e1za rozhodne nie je testovacia a \u00fadaje, ktor\u00e9 s\u00fa v nej ulo\u017een\u00e9, s\u00fa cenn\u00e9.<\/p>\n<p>Napokon, tretia \u00faloha, ktor\u00fa je mo\u017en\u00e9 vyrie\u0161i\u0165 iba so z\u00e1lohou, je klonovanie datab\u00e1zy, napr\u00edklad na \u00fa\u010dely testovania.<\/p>\n<p>Z\u00e1lohovanie datab\u00e1z sa vo svojej podstate zaklad\u00e1 na jednom z dvoch princ\u00edpov:<\/p>\n<ul>\n<li>V\u00fdber \u00fadajov s n\u00e1sledn\u00fdm ukladan\u00edm v \u013eubovo\u013enom form\u00e1te;<\/li>\n<li>Snapshot stavu s\u00faborov DB a uchov\u00e1vanie logov.<\/li>\n<\/ul>\n<p>\nPo\u010fme sa pozrie\u0165 na tieto princ\u00edpy a na n\u00e1stroje, ktor\u00e9 ich realizuj\u00fa, podrobnej\u0161ie.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Export d\u00e1t<\/h3>\n<p>\nV s\u00fabore util\u00edt, ktor\u00e9 s\u00fa prilo\u017een\u00e9 k akejko\u013evek S\u00daDB, musia by\u0165 nevyhnutne n\u00e1stroje na export a import \u00fadajov. \u00dadaje sa ukladaj\u00fa bu\u010f v textovom form\u00e1te, alebo v bin\u00e1rnom form\u00e1te \u0161pecifickom pre konkr\u00e9tnu S\u00daDB. V nasleduj\u00facej tabu\u013eke je uveden\u00fd zoznam t\u00fdchto n\u00e1strojov:<\/p>\n<p>Bin\u00e1rny form\u00e1t<br \/>\nTextov\u00fd form\u00e1t<\/p>\n<p>Oracle<br \/>\nDataPump Export\/DataPump Import<br \/>\nExport\/import<br \/>\nSQL*Plus\/SQL*Loader<\/p>\n<p>PostgreSQL<br \/>\npg_dump, pg_dumpall\/pg_restore<br \/>\npg_dump, pg_dumpall\/psql<\/p>\n<p>Microsoft SQL Server<br \/>\nbcp<br \/>\nbcp<\/p>\n<p>DB2<br \/>\nunload\/load<br \/>\nunload\/load<\/p>\n<p>MySQL<\/p>\n<p>mysqldump, mysqlpump\/mysql, mysqlimport<\/p>\n<p>K\u013e\u00fa\u010d-hodnota, grafov\u00fd*<br \/>\nmongodump\/mongorestore<br \/>\nmongoexport\/mongoimport<\/p>\n<p>Cassandra<br \/>\nnodetool snapshot\/sstableloader<br \/>\ncqlsh<\/p>\n<p>\nTextov\u00fd form\u00e1t je dobr\u00fd t\u00fdm, \u017ee ho mo\u017eno upravova\u0165 alebo dokonca vytv\u00e1ra\u0165 extern\u00fdmi programami, zatia\u013e \u010do bin\u00e1rny form\u00e1t je dobr\u00fd t\u00fdm, \u017ee umo\u017e\u0148uje r\u00fdchlej\u0161ie vyp\u00fa\u0161\u0165a\u0165 a na\u010d\u00edta\u0165 d\u00e1ta z d\u00f4vodu \u00faspory zdrojov na transform\u00e1ciu form\u00e1tov.<\/p>\n<p>Napriek jednoduchosti a zrejmosti my\u0161lienky vyp\u00fa\u0161\u0165ania d\u00e1t sa tento sp\u00f4sob pre z\u00e1lohovanie za\u0165a\u017een\u00fdch priemyseln\u00fdch datab\u00e1z zriedka pou\u017e\u00edva. Tu s\u00fa d\u00f4vody, pre\u010do vyp\u00fa\u0161\u0165anie nie je vhodn\u00e9 pre poriadne z\u00e1lohovanie:<\/p>\n<ul>\n<li>vyp\u00fa\u0161\u0165anie vykon\u00e1va v\u00fdznamn\u00fa z\u00e1\u0165a\u017e na syst\u00e9m zdroja;<\/li>\n<li>vyp\u00fa\u0161\u0165anie trv\u00e1 ve\u013ea \u010dasu \u2013 do konca procesu sa stane u\u017e neaktu\u00e1lnym;<\/li>\n<li>uskuto\u010dni\u0165 konzistentn\u00e9 vyp\u00fa\u0161\u0165anie celej datab\u00e1zy pri vysokej z\u00e1\u0165a\u017ei je prakticky nemo\u017en\u00e9, preto\u017ee DBMS mus\u00ed uchov\u00e1va\u0165 sn\u00edmku svojho stavu v \u010dase za\u010diatku vyp\u00fa\u0161\u0165ania. \u010c\u00edm viac transakci\u00ed sa vykon\u00e1 od okamihu za\u010diatku vyp\u00fa\u0161\u0165ania, t\u00fdm v\u00e4\u010d\u0161\u00ed objem sn\u00edmky (neaktu\u00e1lnych k\u00f3pi\u00ed d\u00e1t v PostgreSQL, undo priestoru v Oracle, tempdb v Microsoft SQL Server, a pod.);<\/li>\n<li>vyp\u00fa\u0161\u0165anie zachov\u00e1va logick\u00fa \u0161trukt\u00faru d\u00e1t, ale nezachov\u00e1va ich fyzick\u00fa \u0161trukt\u00faru \u2013 parametre fyzick\u00e9ho ukladania tabuliek, indexy a pod.<\/li>\n<\/ul>\n<p>\nNapriek tomu m\u00e1 vyp\u00fa\u0161\u0165anie aj v\u00fdhody:<\/p>\n<ul>\n<li>vysok\u00e1 selektivita: mo\u017eno vypusti\u0165 jednotliv\u00e9 tabu\u013eky, jednotliv\u00e9 polia a dokonca jednotliv\u00e9 riadky;<\/li>\n<li>vypusten\u00e9 d\u00e1ta m\u00f4\u017eu by\u0165 na\u010d\u00edtan\u00e9 do datab\u00e1zy inej verzie, a ak je vyp\u00fa\u0161\u0165anie vykonan\u00e9 v textovom form\u00e1te, aj do inej datab\u00e1zy.<\/li>\n<\/ul>\n<p>\nTak\u017ee sa vyp\u00fa\u0161\u0165anie pou\u017e\u00edva najm\u00e4 pre tak\u00e9 \u00falohy ako z\u00e1lohovanie mal\u00fdch tabuliek (napr\u00edklad referen\u010dn\u00fdch) alebo \u0161\u00edrenie s\u00faborov s \u010fal\u0161ou verziou aplik\u00e1cie. <\/p>\n<p>Najbe\u017enej\u0161ou met\u00f3dou z\u00e1lohovania datab\u00e1z je kop\u00edrovanie s\u00faborov datab\u00e1zy.<\/p>\n<h3>\u201eStuden\u00e9\u201c ukladanie s\u00faborov DB<\/h3>\n<p>\nZrejm\u00e1 my\u0161lienka \u2013 zastavi\u0165 datab\u00e1zu a skop\u00edrova\u0165 v\u0161etky jej s\u00fabory. Tak\u00e1to z\u00e1loha sa naz\u00fdva \u201estuden\u00e1\u201c. Tento sp\u00f4sob je extr\u00e9mne spo\u013eahliv\u00fd a jednoduch\u00fd, ale m\u00e1 dva zjavn\u00e9 nedostatky:<\/p>\n<ul>\n<li>Z \"studen\u00fdch\" z\u00e1loh je mo\u017en\u00e9 obnovi\u0165 len tak\u00e9 stavy datab\u00e1zy, ak\u00e9 existovali v momente zastavenia; transakcie vykonan\u00e9 po re\u0161tarte datab\u00e1zy sa do \"studenej\" z\u00e1lohy nedostan\u00fa.<\/li>\n<li>\u010ealeko nie ka\u017ed\u00e1 datab\u00e1za m\u00e1 technologick\u00e9 okno, kedy ju je mo\u017en\u00e9 zastavi\u0165.<\/li>\n<\/ul>\n<p>\nAk v\u00e1m \"studene\" z\u00e1lohovanie vyhovuje, treba pam\u00e4ta\u0165 na to, \u017ee<\/p>\n<ul>\n<li>\"studen\u00e1\" k\u00f3pia by ob\u010das mala obsahova\u0165 aj denn\u00edky. Met\u00f3dy ur\u010dovania, ktor\u00e9 denn\u00edky by mali by\u0165 v \"studen\u00e9\" k\u00f3pii, s\u00fa individu\u00e1lne pre ka\u017ed\u00fa DBMS. Napr\u00edklad v Oracle je potrebn\u00e9 skop\u00edrova\u0165 takzvan\u00e9 online redo, teda fixovan\u00fd po\u010det s\u00faborov denn\u00edka v \u0161peci\u00e1lnom adres\u00e1ri, a to aj vtedy, ke\u010f je datab\u00e1za zastaven\u00e1 spr\u00e1vne. V PostgreSQL je potrebn\u00e9 ulo\u017ei\u0165 v\u0161etky denn\u00edky po\u010dn\u00fac t\u00fdm, ktor\u00fd obsahuje posledn\u00fd bod kontrolu, inform\u00e1cie o ktorom s\u00fa obsiahnut\u00e9 v ovl\u00e1dacom s\u00fabore.<\/li>\n<li>adres\u00e1r datab\u00e1zy m\u00f4\u017ee obsahova\u0165 dos\u0165 ve\u013ek\u00e9 s\u00fabory do\u010dasn\u00fdch tabuliek, ktor\u00e9 nie je nutn\u00e9 zahrn\u00fa\u0165 do z\u00e1lohy. Mimochodom, t\u00e1to pozn\u00e1mka plat\u00ed aj pre \"hor\u00face\" z\u00e1lohovanie.<\/li>\n<\/ul>\n<p><\/p>\n<h3>\"Hor\u00face\" ulo\u017eenie s\u00faborov<\/h3>\n<p>\nV\u00e4\u010d\u0161ina z\u00e1loh modern\u00fdch datab\u00e1z sa vykon\u00e1va kop\u00edrovan\u00edm s\u00faborov datab\u00e1zy bez zastavenia datab\u00e1zy. Tu sa objavuje nieko\u013eko probl\u00e9mov:<\/p>\n<ul>\n<li>V momente za\u010datia kop\u00edrovania obsah datab\u00e1zy nemus\u00ed s\u00fahlasi\u0165 s obsahom s\u00faborov, preto\u017ee \u010das\u0165 inform\u00e1ci\u00ed je v cache a e\u0161te nebola zap\u00edsan\u00e1 na disk.<\/li>\n<li>Po\u010das kop\u00edrovania sa m\u00f4\u017ee obsah datab\u00e1zy meni\u0165. Ak sa pou\u017e\u00edvaj\u00fa modifikovate\u013en\u00e9 \u0161trukt\u00fary d\u00e1t, men\u00ed sa obsah s\u00faborov, a pri pou\u017e\u00edvan\u00ed nemodifikovate\u013en\u00fdch \u0161trukt\u00far sa men\u00ed s\u00faborov\u00fd s\u00fabor: objavuj\u00fa sa nov\u00e9 s\u00fabory a star\u00e9 sa odstra\u0148uj\u00fa.<\/li>\n<li>Ke\u010f\u017ee z\u00e1pis d\u00e1t do datab\u00e1zy a \u010d\u00edtanie s\u00faborov DB nie s\u00fa nijako synchronizovan\u00e9, program na z\u00e1lohovanie m\u00f4\u017ee pre\u010d\u00edta\u0165 nekorektn\u00fa str\u00e1nku, kde polovica bude z starej verzie str\u00e1nky a druh\u00e1 polovica \u2013 z novej.<\/li>\n<\/ul>\n<p>\nAby bola z\u00e1loha koherentn\u00e1, pre ka\u017ed\u00fa DBMS existuje pr\u00edkaz, ktor\u00fd oznamuje, \u017ee bol zah\u00e1jen\u00fd proces z\u00e1lohovania. Syntax tohto pr\u00edkazu sa m\u00f4\u017ee l\u00ed\u0161i\u0165: <\/p>\n<ul>\n<li>v Oracle je to samostatn\u00fd pr\u00edkaz ALTER DATABASE\/TABLESPACE BEGIN BACKUP;<\/li>\n<li>v PostgreSQL \u2013 funkcia pg_start_backup();<\/li>\n<li>Pr\u00edprava na z\u00e1lohovanie v Microsoft SQL Server a DB2 sa vykon\u00e1va implicitne po\u010das vykon\u00e1vania pr\u00edkazu BACKUP DATABASE;<\/li>\n<li>V MySQL Enterprise, Cassandre a MongoDB sa pr\u00edprava vykon\u00e1va implicitne extern\u00fdm n\u00e1strojom \u2013 mysqlbackup, OpsCenter a Ops Manager, resp.<\/li>\n<\/ul>\n<p>\nNapriek syntaktick\u00fdm rozdielom sa proces pr\u00edpravy na z\u00e1lohovanie jav\u00ed ako rovnak\u00fd.<\/p>\n<p>Takto vyzer\u00e1 pr\u00edprava na z\u00e1lohovanie v DBMS s menite\u013en\u00fdmi diskov\u00fdmi \u0161trukt\u00farami, teda vo v\u0161etk\u00fdch tradi\u010dn\u00fdch diskov\u00fdch rela\u010dn\u00fdch syst\u00e9moch:<\/p>\n<ol>\n<li>Ulo\u017een\u00ed okamihu za\u010diatku z\u00e1lohovania; z\u00e1loha by mala obsahova\u0165 z\u00e1znamy datab\u00e1zy od tohto okamihu.<\/li>\n<li>Vykon\u00e1va sa kontroln\u00fd bod, teda v\u0161etky zmeny, ktor\u00e9 nastali na str\u00e1nkach d\u00e1t pred zapam\u00e4tnen\u00fdm okamihom, sa zapisuj\u00fa na disk. To zaru\u010duje, \u017ee z\u00e1znamy pred za\u010diatkom z\u00e1lohovania nebud\u00fa pri obnove potrebn\u00e9.<\/li>\n<li>Zah\u00e1jenie \u0161peci\u00e1lneho re\u017eimu protokolovania: ak sa str\u00e1nka d\u00e1t zmenila prv\u00fdkr\u00e1t po na\u010d\u00edtan\u00ed z disku, namiesto toho, aby zaznamen\u00e1vala zmenu str\u00e1nky do protokolu, datab\u00e1za tam zaznamen\u00e1 cel\u00fa str\u00e1nku. Pri vykon\u00e1van\u00ed pr\u00edpravnej proced\u00fary sa v\u0161etky str\u00e1nky zapisuj\u00fa na disk, a preto pri prvom zmene sa blok v\u017edy zaznamen\u00e1 do protokolu v celosti. Ak v\u0161ak po\u010das z\u00e1lohovania bude str\u00e1nka znovu zap\u00edsan\u00e1 na disk, nasleduj\u00faca zmena op\u00e4\u0165 sp\u00f4sob\u00ed, \u017ee v protokole sa objav\u00ed kompletn\u00e1 k\u00f3pia str\u00e1nky. To zaru\u010duje, \u017ee ak sa n\u00e1hodou pri kop\u00edrovan\u00ed s\u00faboru s d\u00e1tami str\u00e1nka stane neplatnou, aplik\u00e1cia protokolu ju op\u00e4\u0165 urob\u00ed platnou.<\/li>\n<li>Zablokuje sa zmena hlavi\u010diek s\u00faborov d\u00e1t, teda tej \u010dasti, ktorej zmeny nie s\u00fa zaznamenan\u00e9 v protokoloch. To zaru\u010duje, \u017ee hlavi\u010dka bude skop\u00edrovan\u00e1 spr\u00e1vne, a potom k s\u00faboru d\u00e1t spr\u00e1vne bud\u00fa aplikovan\u00e9 protokoly.<\/li>\n<\/ol>\n<p>\nPo vykonan\u00ed v\u0161etk\u00fdch vy\u0161\u0161ie uveden\u00fdch postupov je mo\u017en\u00e9 kop\u00edrova\u0165 s\u00fabory \u00fadajov pomocou opera\u010dn\u00e9ho syst\u00e9mu \u2013 cp, rsync a \u010fal\u0161\u00edch. Aktiv\u00e1cia re\u017eimu z\u00e1lohovania zni\u017euje v\u00fdkon datab\u00e1zy: po prv\u00e9, zvy\u0161uje sa objem protokolov, a po druh\u00e9, ak d\u00f4jde k poruche v re\u017eime z\u00e1lohovania, obnova bude dlh\u0161ia, preto\u017ee hlavi\u010dky s\u00faborov \u00fadajov sa neaktualizuj\u00fa. \u010c\u00edm r\u00fdchlej\u0161ie sa z\u00e1lohovanie dokon\u010d\u00ed, t\u00fdm lep\u0161ie pre datab\u00e1zu, preto je tu vhodn\u00e9 pou\u017ei\u0165 prostriedky ako sn\u00edmok (snapshot) s\u00faborov\u00e9ho syst\u00e9mu alebo oddelenie zrkadla (BCV) v diskovom poli. Niektor\u00e9 DBMS (Oracle, PostgreSQL) poskytuj\u00fa administr\u00e1torovi mo\u017enos\u0165 samostatne si vybra\u0165 sp\u00f4sob kop\u00edrovania, in\u00e9 (Microsoft SQL Server) pon\u00fakaj\u00fa rozhranie na integr\u00e1ciu vlastn\u00fdch z\u00e1lohovac\u00edch util\u00edt s mechanizmami s\u00faborov\u00fdch syst\u00e9mov alebo \u00falo\u017en\u00fdch syst\u00e9mov.<\/p>\n<p>Po dokon\u010den\u00ed z\u00e1lohovania je potrebn\u00e9 prepn\u00fa\u0165 datab\u00e1zu sp\u00e4\u0165 do norm\u00e1lneho stavu. V Oracle sa to rob\u00ed pr\u00edkazom ALTER DATABASE\/TABLESPACE END BACKUP, v PostgreSQL volan\u00edm funkcie pg_stop_backup(), a v in\u00fdch datab\u00e1zach pomocou vn\u00fatorn\u00fdch podprogramov pr\u00edslu\u0161n\u00fdch pr\u00edkazov alebo extern\u00fdch slu\u017eieb.<\/p>\n<p>Takto vyzer\u00e1 \u010dasov\u00e1 sch\u00e9ma procesu z\u00e1lohovania:<\/p>\n<p><img decoding=\"async\" alt=\"Sprievodca z\u00e1lohovan\u00edm datab\u00e1z\" src=\"\/wp-content\/uploads\/2020\/08\/4e74f865e9f35acec083b747da4449cf.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<ul>\n<li>Pr\u00edprava na z\u00e1lohovanie (begin backup) trv\u00e1 \u010das, niekedy zna\u010dn\u00fd. Aj ke\u010f sa pou\u017e\u00edvaj\u00fa zrkadlov\u00e9 zv\u00e4zky alebo s\u00faborov\u00e9 syst\u00e9my s mo\u017enos\u0165ou vytv\u00e1rania sn\u00edmok, proces z\u00e1lohovania nebude okam\u017eit\u00fd.<\/li>\n<li>Spolu so s\u00fabormi \u00fadajov je potrebn\u00e9 uchova\u0165 protokoly od okamihu za\u010datia pr\u00edpravy na z\u00e1lohovanie a\u017e po okamih, ke\u010f sa datab\u00e1za vr\u00e1ti do norm\u00e1lneho stavu.<\/li>\n<li>Z tejto z\u00e1lohy je mo\u017en\u00e9 sa obnovi\u0165 <b>v momente, ke\u010f sa datab\u00e1za vr\u00e1tila do norm\u00e1lneho stavu<\/b>. Obnovenie na sk\u00f4r neexistuje.<\/li>\n<\/ul>\n<p>\nSo z\u00e1lohami datab\u00e1z, ktor\u00e9 pou\u017e\u00edvaj\u00fa nemenn\u00e9 \u0161trukt\u00fary d\u00e1t (sn\u00edmky pam\u00e4te, LSM-stromy), je situ\u00e1cia jednoduch\u0161ia. Pr\u00edprava na z\u00e1lohovanie pozost\u00e1va z nasleduj\u00facich krokov:<\/p>\n<ol>\n<li>\u00dadaje z pam\u00e4te sa pres\u00favaj\u00fa na disk.<\/li>\n<li>Zaznamen\u00e1va sa zoznam s\u00faborov, ktor\u00e9 sa dostan\u00fa do z\u00e1lohy. A\u017e do dokon\u010denia procesu z\u00e1lohovania je datab\u00e1ze zak\u00e1zan\u00e9 odstr\u00e1ni\u0165 tieto s\u00fabory, aj ke\u010f sa stan\u00fa nepotrebn\u00fdmi.<\/li>\n<\/ol>\n<p>\nPo sign\u00e1le o ukon\u010den\u00ed z\u00e1lohovania m\u00f4\u017ee datab\u00e1za s nemenn\u00fdmi \u0161trukt\u00farami op\u00e4\u0165 odstra\u0148ova\u0165 nepotrebn\u00e9 s\u00fabory.<\/p>\n<h3>Obnovenie do bodu<\/h3>\n<p>\nZ\u00e1loha umo\u017e\u0148uje obnovi\u0165 stav datab\u00e1zy v momente, ke\u010f sa ukon\u010dila pr\u00edkaz na n\u00e1vrat z re\u017eimu z\u00e1lohovania. Av\u0161ak hav\u00e1ria, po ktorej bude potrebn\u00e9 obnovenie, m\u00f4\u017ee nasta\u0165 kedyko\u013evek. \u00dalohou obnovenia stavu datab\u00e1zy do \u013eubovo\u013en\u00e9ho okamihu sa naz\u00fdva \u201eobnovenie do bodu\u201c (point-in-time recovery).<\/p>\n<p>Aby bola t\u00e1to mo\u017enos\u0165 zabezpe\u010den\u00e1, je potrebn\u00e9 uchov\u00e1va\u0165 z\u00e1znamy datab\u00e1zy od momentu ukon\u010denia z\u00e1lohovania a v priebehu obnovenia pokra\u010dova\u0165 v aplikovan\u00ed z\u00e1znamov na obnoven\u00fa k\u00f3piu. Po tom, ako bola datab\u00e1za obnoven\u00e1 zo z\u00e1lohy v \u010dase ukon\u010denia kop\u00edrovania, je stav datab\u00e1zy (s\u00faborov a cacheovan\u00fdch str\u00e1nok) zaru\u010dene spr\u00e1vny, tak\u017ee nie je potrebn\u00fd \u017eiadny \u0161peci\u00e1lny re\u017eim zaznamen\u00e1vania. Aplikovan\u00edm z\u00e1znamov do potrebn\u00e9ho momentu m\u00f4\u017eeme z\u00edska\u0165 stav datab\u00e1zy v akomko\u013evek \u010dase.<\/p>\n<p>Ak je r\u00fdchlos\u0165 obnovenia z\u00e1lohy obmedzen\u00e1 iba priepustnos\u0165ou disku, r\u00fdchlos\u0165 aplikovania z\u00e1znamov je zvy\u010dajne obmedzen\u00e1 v\u00fdkonom procesora. Ak sa v hlavnej datab\u00e1ze zmeny dej\u00fa paralelne, pri obnoven\u00ed sa v\u0161etky zmeny vykon\u00e1vaj\u00fa postupne \u2013 v porad\u00ed \u010d\u00edtania zo z\u00e1znamu. T\u00fdm p\u00e1dom je \u010das obnovenia line\u00e1rne z\u00e1visl\u00fd od toho, ako \u010faleko je bod obnovenia od bodu ukon\u010denia z\u00e1lohovania. Z tohto d\u00f4vodu je potrebn\u00e9 pomerne \u010dasto robi\u0165 \u00fapln\u00e9 z\u00e1lohy \u2013 minim\u00e1lne raz za t\u00fd\u017ede\u0148 pre datab\u00e1zy s malou transak\u010dnou z\u00e1\u0165a\u017eou a a\u017e po denn\u00fa z\u00e1lohu pre vysoko za\u0165a\u017een\u00e9 datab\u00e1zy.<\/p>\n<h3>Inkrement\u00e1lne z\u00e1lohovanie<\/h3>\n<p>\nAby sme ur\u00fdchlili obnovenie do bodu, bolo by dobr\u00e9 ma\u0165 mo\u017enos\u0165 vykon\u00e1va\u0165 z\u00e1lohovanie \u010do naj\u010dastej\u0161ie, ale z\u00e1rove\u0148 nezap\u013a\u0148a\u0165 nadbyto\u010dne miesto na diskoch a neza\u0165a\u017eova\u0165 datab\u00e1zu \u00falohami z\u00e1lohovania.<\/p>\n<p>Rie\u0161en\u00edm probl\u00e9mu je inkrement\u00e1lne z\u00e1lohovanie, teda kop\u00edrovanie iba t\u00fdch str\u00e1n d\u00e1t, ktor\u00e9 sa zmenili od posledn\u00e9ho z\u00e1lohovania.<br \/>\nInkrement\u00e1lne z\u00e1lohovanie m\u00e1 zmysel len pre S\u00daDB, ktor\u00e9 pou\u017e\u00edvaj\u00fa menite\u013en\u00e9 \u0161trukt\u00fary \u00fadajov.<\/p>\n<p>Inkrement sa m\u00f4\u017ee od\u010d\u00edta\u0165 bu\u010f od \u00faplnej z\u00e1lohy (kumulat\u00edvna z\u00e1loha), alebo od akejko\u013evek predch\u00e1dzej\u00facej k\u00f3pie (diferenci\u00e1lna k\u00f3pia). <\/p>\n<p><img decoding=\"async\" alt=\"Sprievodca z\u00e1lohovan\u00edm datab\u00e1z\" src=\"\/wp-content\/uploads\/2020\/08\/10e3bb87445cb36693c7b5469d62eeaf.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nBohu\u017eia\u013e, neexistuje jednotn\u00e1 terminol\u00f3gia a r\u00f4zni v\u00fdrobcovia pou\u017e\u00edvaj\u00fa r\u00f4zne term\u00edny:<\/p>\n<p>Diferenci\u00e1lna<br \/>\nKumulat\u00edvna<\/p>\n<p>Oracle<br \/>\nDifferential<br \/>\nCumulative<\/p>\n<p>PostgresPro<br \/>\nIncremental<br \/>\n\u2014<\/p>\n<p>Microsoft SQL Server<br \/>\n\u2014<br \/>\nDifferential<\/p>\n<p>IBM DB2<br \/>\nDelta<br \/>\nIncremental<\/p>\n<p>\nPri existencii inkrement\u00e1lnych k\u00f3pi\u00ed vyzer\u00e1 proces obnovovania do bodu nasledovne:<\/p>\n<ul>\n<li>obnovuje sa posledn\u00e1 \u00fapln\u00e1 z\u00e1loha, vykonan\u00e1 pred momentom obnovy;<\/li>\n<li>na \u00fapln\u00fa k\u00f3piu sa obnovuj\u00fa inkrement\u00e1lne k\u00f3pie;<\/li>\n<li>aplikuj\u00fa sa protokoly od bodu za\u010diatku z\u00e1lohovania do bodu obnovy.<\/li>\n<\/ul>\n<p>\nExistencia kumulat\u00edvnej k\u00f3pie ur\u00fdch\u013euje proces obnovenia. Napr\u00edklad na obnovenie stavu datab\u00e1zy do bodu medzi T3 a T4 je potrebn\u00e9 obnovi\u0165 dve inkrement\u00e1lne k\u00f3pie, a na obnovenie do bodu po T4 \u2013 len jednu.<br \/>\nJe zrejm\u00e9, \u017ee objem jednej kumulat\u00edvnej k\u00f3pie je men\u0161\u00ed ako objem nieko\u013ek\u00fdch diferenci\u00e1lnych k\u00f3pi\u00ed, preto\u017ee niektor\u00e9 str\u00e1nky sa menili nieko\u013ekokr\u00e1t a ka\u017ed\u00e1 inkrement\u00e1lna k\u00f3pia obsahuje svoju verziu str\u00e1nky.<\/p>\n<p>Existuj\u00fa tri sp\u00f4soby vytv\u00e1rania inkrement\u00e1lnej k\u00f3pie:<\/p>\n<ol>\n<li>vytvorenie \u00faplnej k\u00f3pie a v\u00fdpo\u010det rozdielu s predch\u00e1dzaj\u00facou \u00faplnou k\u00f3piou;<\/li>\n<li>anal\u00fdza protokolov, vytvorenie zoznamu zmenen\u00fdch str\u00e1nok a z\u00e1lohovanie str\u00e1nok zahrnut\u00fdch v zozname;<\/li>\n<li>\u017eiada\u0165 o zmenen\u00e9 str\u00e1nky v datab\u00e1ze.<\/li>\n<\/ol>\n<p>\nPrv\u00fd sp\u00f4sob \u0161etr\u00ed diskov\u00fd priestor, ale nerie\u0161i \u00falohu zn\u00ed\u017eenia z\u00e1\u0165a\u017ee na datab\u00e1ze. Navy\u0161e, ak m\u00e1me \u00fapln\u00fa z\u00e1lohu, previes\u0165 ju na inkrement\u00e1lnu je nesmyseln\u00e9, preto\u017ee obnova \u00faplnej k\u00f3pie je r\u00fdchlej\u0161ia ako obnova predch\u00e1dzaj\u00facej \u00faplnej k\u00f3pie a inkrementu. \u00dalohu \u0161etrenia diskov\u00e9ho priestoru pri takomto pr\u00edstupe je lep\u0161ie prenies\u0165 na \u0161peci\u00e1lne komponenty so zabudovan\u00fdmi mechanizmami deduplik\u00e1cie. M\u00f4\u017eu to by\u0165 \u0161peci\u00e1lne \u00falo\u017eisk\u00e1 (EMC DataDomain, HPE StorageWorks VLS, cel\u00e1 l\u00ednia NetApp) alebo softv\u00e9rov\u00e9 produkty (ZFS, Veritas NetBackup PureFile, Deduplik\u00e1cia \u00fadajov Windows Server).<\/p>\n<p>Druh\u00fd a tret\u00ed sp\u00f4sob sa l\u00ed\u0161ia mechanizmom ur\u010dovania zoznamu zmenen\u00fdch str\u00e1nok. Anal\u00fdza protokolov je n\u00e1ro\u010dnej\u0161ia na zdroje a z\u00e1rove\u0148 na jej realiz\u00e1ciu je potrebn\u00e9 pozna\u0165 \u0161trukt\u00faru protokolov\u00fdch s\u00faborov. Najjednoduch\u0161ie je op\u00fdta\u0165 sa samotnej datab\u00e1zy, ktor\u00e9 str\u00e1nky sa zmenili, ale na to mus\u00ed ma\u0165 jadro DBMS funk\u010dnos\u0165 sledovania zmenen\u00fdch blokov (block change tracking).<\/p>\n<p>Funkcionalita inkrement\u00e1lneho z\u00e1lohovania bola prv\u00fdkr\u00e1t vytvoren\u00e1 v softv\u00e9ri Oracle Recovery Manager (RMAN), ktor\u00fd sa objavil v releas Oracle 8i. Oracle ihne\u010f implementoval sledovanie zmenen\u00fdch blokov, tak\u017ee nie je potrebn\u00e9 analyzova\u0165 protokoly.<\/p>\n<p>PostgreSQL nesleduje zmenen\u00e9 bloky, tak\u017ee n\u00e1stroj pg_probackup, vyvinut\u00fd ruskou spolo\u010dnos\u0165ou Postgres Professional, ur\u010duje zmenen\u00e9 str\u00e1nky prostredn\u00edctvom anal\u00fdzy protokolu. Av\u0161ak spolo\u010dnos\u0165 dod\u00e1va aj DBMS PostgresPro, ktor\u00fd zah\u0155\u0148a roz\u0161\u00edrenie ptrack, sleduj\u00face zmeny str\u00e1nok. Pri pou\u017e\u00edvan\u00ed pg_probackup s DBMS PostgresPro n\u00e1stroj \u017eiada o zmenen\u00e9 str\u00e1nky priamo od datab\u00e1zy \u2013 presne tak, ako RMAN.<\/p>\n<p>Microsoft SQL Server, rovnako ako Oracle, sleduje zmenen\u00e9 str\u00e1nky, ale pr\u00edkaz BACKUP umo\u017e\u0148uje vykon\u00e1va\u0165 iba \u00fapln\u00e9 a kumulat\u00edvne z\u00e1lohy.<\/p>\n<p>V DB2 je mo\u017enos\u0165 sledovania zmenen\u00fdch str\u00e1nok, ale predvolene je t\u00e1to funkcia vypnut\u00e1. Po jej zapnut\u00ed bude DB2 umo\u017e\u0148ova\u0165 vykon\u00e1va\u0165 \u00fapln\u00e9, diferencovan\u00e9 a kumulat\u00edvne z\u00e1lohy.<\/p>\n<p>D\u00f4le\u017eit\u00e9 je, \u017ee pop\u00edsan\u00e9 prostriedky (okrem pg_probackup) sa od s\u00faborov\u00fdch prostriedkov z\u00e1lohovania l\u00ed\u0161ia t\u00fdm, \u017ee \u017eiadaj\u00fa obr\u00e1zky str\u00e1nok od datab\u00e1zy, a nie \u010d\u00edtaj\u00fa d\u00e1ta z disku samostatne. Nev\u00fdhodou tohto pr\u00edstupu je mierne dodato\u010dn\u00e9 za\u0165a\u017eenie datab\u00e1zy. Av\u0161ak t\u00fato nev\u00fdhodu viac ne\u017e vyv\u00e1\u017ei fakt, \u017ee pre\u010d\u00edtan\u00e1 str\u00e1nka je v\u017edy spr\u00e1vna, a preto nie je potrebn\u00e9 aktivova\u0165 po\u010das z\u00e1lohovania \u0161peci\u00e1lny re\u017eim zaznamen\u00e1vania.<\/p>\n<p>E\u0161te raz si v\u0161imnite, \u017ee existencia inkrement\u00e1lnych z\u00e1loh neodstr\u00e1\u0148uje po\u017eiadavky na pr\u00edtomnos\u0165 protokolov na obnovenie do \u013eubovo\u013en\u00e9ho bodu v \u010dase. Preto sa v priemyseln\u00fdch datab\u00e1zach protokoly neust\u00e1le prepisuj\u00fa na extern\u00fd nosi\u010d, zatia\u013e \u010do z\u00e1lohy, \u00fapln\u00e9 a\/alebo inkrement\u00e1lne, sa vytv\u00e1raj\u00fa pod\u013ea rozvrhu.<\/p>\n<p>Najlep\u0161ia realiz\u00e1cia my\u0161lienky inkrement\u00e1lneho z\u00e1lohovania je programovo-hardware komplex (v terminol\u00f3gii Oracle \u2013 engineered system) Zero Data Loss Recovery Appliance \u2013 \u0161pecializovan\u00e9 rie\u0161enie Oracle pre z\u00e1lohovanie vlastnej DB. Komplex predstavuje klaster <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sk\/server\/\"   title=\"serverov\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1521\">serverov<\/a> s ve\u013ek\u00fdm objemom diskov, na ktor\u00e9 je nain\u0161talovan\u00e1 modifikovan\u00e1 verzia softv\u00e9ru Recovery Manager a m\u00f4\u017ee pracova\u0165 ako s in\u00fdmi programovo-hardware komplexmi Oracle (Database Appliance, Exadata, SPARC Supercluster), tak aj s datab\u00e1zami Oracle na tradi\u010dnej infra\u0161trukt\u00fare. Na rozdiel od \u201ebe\u017en\u00e9ho\u201c RMAN, v ZDLRA je implementovan\u00e1 koncepcia \u201eve\u010dn\u00e9ho inkrementu\u201c (incremental forever). Syst\u00e9m jednorazovo vytvor\u00ed \u00fapln\u00fa k\u00f3piu datab\u00e1zy a potom rob\u00ed iba inkrement\u00e1lne k\u00f3pie. Dodato\u010dn\u00e9 moduly RMAN umo\u017e\u0148uj\u00fa sp\u00e1ja\u0165 k\u00f3pie a vytv\u00e1ra\u0165 nov\u00e9 \u00fapln\u00e9 k\u00f3pie z inkrement\u00e1lnych. <\/p>\n<p>Na po\u010des\u0165 rusk\u00fdch v\u00fdvoj\u00e1rov treba poznamena\u0165, \u017ee aj pg_probackup dok\u00e1\u017ee sp\u00e1ja\u0165 inkrement\u00e1lne k\u00f3pie.<\/p>\n<p><img decoding=\"async\" alt=\"Sprievodca z\u00e1lohovan\u00edm datab\u00e1z\" src=\"\/wp-content\/uploads\/2020\/08\/275b649ce74614c04410618a062dddbd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNa rozdiel od mnoh\u00fdch podobn\u00fdch ot\u00e1zok, ot\u00e1zka \u201ektor\u00e1 met\u00f3da z\u00e1lohovania je najlep\u0161ia\u201c m\u00e1 jednozna\u010dn\u00fa odpove\u010f \u2013 najlep\u0161ie je nat\u00edvny n\u00e1stroj pre pou\u017eit\u00fd DBMS, ktor\u00fd zabezpe\u010duje mo\u017enos\u0165 inkrement\u00e1lneho z\u00e1lohovania.<\/p>\n<p>Pre administr\u00e1tora DB s\u00fa ove\u013ea d\u00f4le\u017eitej\u0161ie ot\u00e1zky v\u00fdberu strat\u00e9gie z\u00e1lohovania a integr\u00e1cia prostriedkov z\u00e1lohovania datab\u00e1z do firemnej infra\u0161trukt\u00fary. Ale tieto ot\u00e1zky presahuj\u00fa r\u00e1mec tohto \u010dl\u00e1nku.<br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/516428\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u2013 \u041e, \u043d\u0438\u043a\u0430\u043a\u043e\u0435 \u0443\u0431\u0435\u0436\u0438\u0449\u0435 \u043d\u0435 \u0432\u044b\u0434\u0435\u0440\u0436\u0438\u0442 \u043f\u043e\u043f\u0430\u0434\u0430\u043d\u0438\u044f \u043c\u0435\u0442\u0435\u043e\u0440\u0438\u0442\u0430. \u041d\u043e \u0432\u0435\u0434\u044c \u0443 \u0432\u0430\u0441, \u043a\u0430\u043a \u0438 \u0443 \u043a\u0430\u0436\u0434\u043e\u0433\u043e, \u0435\u0441\u0442\u044c \u0440\u0435\u0437\u0435\u0440\u0432, \u0442\u0430\u043a \u0447\u0442\u043e \u043c\u043e\u0436\u0435\u0442\u0435 \u043d\u0435 \u0431\u0435\u0441\u043f\u043e\u043a\u043e\u0438\u0442\u044c\u0441\u044f. \u0421\u0442\u0430\u043d\u0438\u0441\u043b\u0430\u0432 \u041b\u0435\u043c, \u00ab\u0417\u0432\u0451\u0437\u0434\u043d\u044b\u0435 \u0434\u043d\u0435\u0432\u043d\u0438\u043a\u0438 \u0418\u0439\u043e\u043d\u0430 \u0422\u0438\u0445\u043e\u0433\u043e\u00bb \u0420\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435 \u043a\u043e\u043f\u0438\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u0433\u0434\u0435-\u0442\u043e \u0432\u043d\u0435 \u043e\u0441\u043d\u043e\u0432\u043d\u043e\u0433\u043e \u043c\u0435\u0441\u0442\u0430 \u0438\u0445 \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f. \u0413\u043b\u0430\u0432\u043d\u043e\u0435 \u043d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u2013 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0445 \u043f\u043e\u0441\u043b\u0435 \u0438\u0445 \u043f\u043e\u0442\u0435\u0440\u0438. \u0412 \u0441\u0432\u044f\u0437\u0438 \u0441 \u044d\u0442\u0438\u043c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":92368,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-92367","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.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u2013 \u041e, \u043d\u0438\u043a\u0430\u043a\u043e\u0435 \u0443\u0431\u0435\u0436\u0438\u0449\u0435 \u043d\u0435 \u0432\u044b\u0434\u0435\u0440\u0436\u0438\u0442 \u043f\u043e\u043f\u0430\u0434\u0430\u043d\u0438\u044f \u043c\u0435\u0442\u0435\u043e\u0440\u0438\u0442\u0430.\" \/>\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\/sk\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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\u041f\u0443\u0442\u0435\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c \u043f\u043e \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u043c\u0443 \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044e \u0431\u0430\u0437 \u0434\u0430\u043d\u043d\u044b\u0445 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u2013 \u041e, \u043d\u0438\u043a\u0430\u043a\u043e\u0435 \u0443\u0431\u0435\u0436\u0438\u0449\u0435 \u043d\u0435 \u0432\u044b\u0434\u0435\u0440\u0436\u0438\u0442 \u043f\u043e\u043f\u0430\u0434\u0430\u043d\u0438\u044f \u043c\u0435\u0442\u0435\u043e\u0440\u0438\u0442\u0430.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh\" \/>\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-08-26T05:42:09+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-08-26T05:42:09+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\udd47Sprievodca z\u00e1lohovan\u00edm datab\u00e1z | ProHoster","description":"\u2013 O, nijak\u00e9 \u00fato\u010disko nevydr\u017e\u00ed z\u00e1sah meteoritom.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\u041f\u0443\u0442\u0435\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c \u043f\u043e \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u043c\u0443 \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044e \u0431\u0430\u0437 \u0434\u0430\u043d\u043d\u044b\u0445 | ProHoster","og:description":"\u2013 \u041e, \u043d\u0438\u043a\u0430\u043a\u043e\u0435 \u0443\u0431\u0435\u0436\u0438\u0449\u0435 \u043d\u0435 \u0432\u044b\u0434\u0435\u0440\u0436\u0438\u0442 \u043f\u043e\u043f\u0430\u0434\u0430\u043d\u0438\u044f \u043c\u0435\u0442\u0435\u043e\u0440\u0438\u0442\u0430.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh","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-08-26T05:42:09+00:00","article:modified_time":"2020-08-26T05:42:09+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"92367","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 12:09:36","updated":"2026-02-09 16:50:36","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/92367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=92367"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/92367\/revisions"}],"predecessor-version":[{"id":158765,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/92367\/revisions\/158765"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/92368"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=92367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=92367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=92367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}