{"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\/sq\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh","title":{"rendered":"Udh\u00ebzuesi p\u00ebr backup-in e bazave t\u00eb t\u00eb dh\u00ebnave","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<blockquote><p>\u2013 O, asnj\u00eb streh\u00eb nuk mund t\u00eb p\u00ebrballoj\u00eb goditjen e nj\u00eb meteori. Por, si gjithkush, ju keni nj\u00eb rezerv\u00eb, k\u00ebshtu q\u00eb mund t\u00eb mos shqet\u00ebsoheni.<\/p>\n<p><i>Stanislav Lem, \u00abDairy Star t\u00eb Ijon Tichit\u00bb<\/i><\/p><\/blockquote>\n<p>\nBackup i referohet ruajtjes s\u00eb nj\u00eb kopjeje t\u00eb t\u00eb dh\u00ebnave diku jasht\u00eb vendit kryesor t\u00eb ruajtjes s\u00eb tyre.<\/p>\n<p><img decoding=\"async\" alt=\"Udh\u00ebzuesi p\u00ebr backup-in e bazave t\u00eb t\u00eb dh\u00ebnave\" src=\"\/wp-content\/uploads\/2020\/08\/c1dba0d8999cab69315560dfc57546e0.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nQ\u00ebllimi kryesor i backup-it \u00ebsht\u00eb rikthimi i t\u00eb dh\u00ebnave pas humbjes s\u00eb tyre. N\u00eb k\u00ebt\u00eb kontekst, shpesh d\u00ebgjohet se n\u00ebse ekziston nj\u00eb replik\u00eb e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave, gjithmon\u00eb mund t\u00eb rikuperoni t\u00eb dh\u00ebnat prej saj, dhe backup-i nuk \u00ebsht\u00eb i nevojsh\u00ebm. N\u00eb t\u00eb v\u00ebrtet\u00eb, backup-i lejon zgjidhjen e t\u00eb pakt\u00ebn tre problemeve q\u00eb nuk mund t\u00eb zgjidhen p\u00ebrmes nj\u00eb replike, dhe gjithashtu nuk \u00ebsht\u00eb e leht\u00eb t\u00eb inicializohet nj\u00eb replik\u00eb pa nj\u00eb kopje rezerv\u00eb.<\/p>\n<p>S\u00eb pari, nj\u00eb kopje rezerv\u00eb lejon rikthimin e t\u00eb dh\u00ebnave pas nj\u00eb gabimi logjik. P\u00ebr shembull, nj\u00eb accountant fshin nj\u00eb grup operacionesh ose nj\u00eb administrator i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave shkat\u00ebrron hap\u00ebsir\u00ebn e tabelave. T\u00eb dyja operacionet jan\u00eb krejt legjitime nga pik\u00ebpamja e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave, dhe procesi i replikimit do t\u00eb i reproduktoj\u00eb ato n\u00eb baz\u00ebn-ruajtes.<\/p>\n<p>S\u00eb dyti, sistemet moderne t\u00eb menaxhimit t\u00eb t\u00eb dh\u00ebnave jan\u00eb komplekse shum\u00eb t\u00eb besueshme, megjithat\u00eb, ndonj\u00ebher\u00eb ndodhin shqet\u00ebsime t\u00eb brendshme n\u00eb strukturat e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave, pas t\u00eb cilave humbet qasja n\u00eb t\u00eb dh\u00ebna. E ve\u00e7anta \u00ebsht\u00eb se kjo ndodhi shpesh ndodhi gjat\u00eb ngarkes\u00ebs s\u00eb lart\u00eb ose gjat\u00eb instalimit t\u00eb ndonj\u00eb azhurnimi. Por ngarkesa e lart\u00eb, ashtu si dhe azhurnimet e rregullta, tregojn\u00eb se baza e t\u00eb dh\u00ebnave nuk \u00ebsht\u00eb thjesht testuese dhe t\u00eb dh\u00ebnat q\u00eb ruhen aty jan\u00eb t\u00eb vlefshme.<\/p>\n<p>S\u00eb fundi, detyra e tret\u00eb q\u00eb k\u00ebrkon nj\u00eb kopje rezerv\u00eb \u00ebsht\u00eb klonimi i baz\u00ebs, p\u00ebr shembull, p\u00ebr q\u00ebllime testi.<\/p>\n<p>Backup-et e bazave t\u00eb t\u00eb dh\u00ebnave jan\u00eb, n\u00eb nj\u00eb apo tjet\u00ebr form\u00eb, t\u00eb bazuara n\u00eb nj\u00eb nga dy parimet:<\/p>\n<ul>\n<li>E nxjerr\u00eb e t\u00eb dh\u00ebnave pasuar nga ruajtja n\u00eb nj\u00eb format t\u00eb rast\u00ebsish\u00ebm;<\/li>\n<li>Nj\u00eb snapshot i gjendjes s\u00eb skedar\u00ebve t\u00eb DB dhe ruajtja e ditar\u00ebve.<\/li>\n<\/ul>\n<p>\nLe t\u00eb shqyrtojm\u00eb k\u00ebto parime dhe mjetet q\u00eb i realizojn\u00eb ato m\u00eb n\u00eb detaje.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Nxjerrja e t\u00eb dh\u00ebnave<\/h3>\n<p>\nN\u00eb koleksionin e mjeteve q\u00eb shoq\u00ebrojn\u00eb \u00e7do DBMS, patjet\u00ebr q\u00eb ekzistojn\u00eb mjete p\u00ebr nxjerrjen dhe ngarkimin e t\u00eb dh\u00ebnave. T\u00eb dh\u00ebnat ruhen ose n\u00eb format tekst, ose n\u00eb format binar, specifik p\u00ebr secilin DBMS. Tabela m\u00eb posht\u00eb tregon nj\u00eb list\u00eb t\u00eb till\u00eb mjete:<\/p>\n<p>Formati binar<br \/>\nFormati tekstual<\/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>MongoDB<br \/>\nmongodump\/mongorestore<br \/>\nmongoexport\/mongoimport<\/p>\n<p>Cassandra<br \/>\nnodetool snapshot\/sstableloader<br \/>\ncqlsh<\/p>\n<p>\nFormati tekstual \u00ebsht\u00eb i mir\u00eb sepse mund t\u00eb redaktohet ose madje t\u00eb krijohet nga programe t\u00eb jashtme, nd\u00ebrsa formati binar \u00ebsht\u00eb i mir\u00eb sepse lejon shp\u00ebrndarjen dhe ngarkimin m\u00eb t\u00eb shpejt\u00eb t\u00eb t\u00eb dh\u00ebnave p\u00ebr shkak t\u00eb kursimit t\u00eb burimeve n\u00eb konvertimin e formateve.<\/p>\n<p>Megjith\u00ebse ideja e nxjerrjes s\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb e thjesht\u00eb dhe e dukshme, ky metod nuk p\u00ebrdoret shpesh p\u00ebr rezervimin e bazave t\u00eb dh\u00ebnash industriale me ngarkes\u00eb. K\u00ebtu jan\u00eb arsyet p\u00ebrse nxjerrja nuk \u00ebsht\u00eb e p\u00ebrshtatshme p\u00ebr nj\u00eb backup t\u00eb plot\u00eb:<\/p>\n<ul>\n<li>procesi i nxjerrjes krijon ngarkes\u00eb t\u00eb konsiderueshme n\u00eb sistemin burim;<\/li>\n<li>nxjerrja merr shum\u00eb koh\u00eb \u2013 deri n\u00eb koh\u00ebn kur p\u00ebrfundon nxjerrja, ajo do t\u00eb b\u00ebhet tashm\u00eb joaktuale;<\/li>\n<li>t\u00eb realizosh nj\u00eb nxjerrje t\u00eb nj\u00ebjt\u00eb t\u00eb gjith\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave gjat\u00eb ngarkes\u00ebs s\u00eb lart\u00eb \u00ebsht\u00eb praktikisht e pamundur, pasi DBMS \u00ebsht\u00eb e detyruar t\u00eb mbaj\u00eb nj\u00eb snapshot t\u00eb gjendjes s\u00eb saj n\u00eb momentin e fillimit t\u00eb nxjerrjes. Sa m\u00eb shum\u00eb transaksione t\u00eb kryhen q\u00eb nga fillimi i nxjerrjes, aq m\u00eb i madh \u00ebsht\u00eb volumi i snapshot-it (kopjet joaktuale t\u00eb t\u00eb dh\u00ebnave n\u00eb PostgreSQL, hap\u00ebsira e anullimit n\u00eb Oracle, tempdb n\u00eb Microsoft SQL Server, etj.);<\/li>\n<li>nxjerrja ruan struktur\u00ebn logjike t\u00eb t\u00eb dh\u00ebnave, por nuk ruan struktur\u00ebn fizike t\u00eb tyre \u2013 parametrat e ruajtjes fizike t\u00eb tabelave, indekset dhe t\u00eb tjera.<\/li>\n<\/ul>\n<p>\nMegjithat\u00eb, nxjerrja ka dhe p\u00ebrfitimet e saj:<\/p>\n<ul>\n<li>zgjedhja e lart\u00eb: mund t\u00eb nxjerrni tabela t\u00eb ve\u00e7anta, fusha t\u00eb ve\u00e7anta dhe madje edhe rreshta t\u00eb ve\u00e7anta;<\/li>\n<li>t\u00eb dh\u00ebnat e nxjerra mund t\u00eb ngarkohen n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash tjet\u00ebr versioni, dhe n\u00ebse nxjerrja b\u00ebhet n\u00eb format tekst, edhe n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash tjet\u00ebr.<\/li>\n<\/ul>\n<p>\nK\u00ebshtu, nxjerrja p\u00ebrdoret kryesisht p\u00ebr detyra t\u00eb tilla si rezervimi i tabelave t\u00eb vogla (p.sh., listave) ose shp\u00ebrndarja e grupeve t\u00eb t\u00eb dh\u00ebnave me aktualizimin e fundit t\u00eb aplikacionit. <\/p>\n<p>Metoda m\u00eb e zakonshme e rezervimit t\u00eb bazave t\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb kopjimi i skedar\u00ebve t\u00eb baz\u00ebs.<\/p>\n<h3>Ruajtja \"e ftoht\u00eb\" e skedar\u00ebve t\u00eb DB<\/h3>\n<p>\nIdeja \u00ebsht\u00eb e qart\u00eb \u2013 ndaloni baz\u00ebn e t\u00eb dh\u00ebnave dhe kopjoni t\u00eb gjith\u00eb skedar\u00ebt e saj. Kjo rezerv\u00eb quhet \"e ftoht\u00eb\". Ky metod \u00ebsht\u00eb jasht\u00ebzakonisht i besuesh\u00ebm dhe i thjesht\u00eb, por ka dy disavantazhe t\u00eb dukshme:<\/p>\n<ul>\n<li>nga nj\u00eb kopje \"e ftoht\u00eb\" rezerv\u00eb mund t\u00eb rikuperohet vet\u00ebm gjendja e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave q\u00eb ishte n\u00eb momentin e ndaljes; transaksionet e kryera pas rinisjes s\u00eb baz\u00ebs nuk do t\u00eb p\u00ebrfshihen n\u00eb kopjen \"e ftoht\u00eb\".<\/li>\n<li>nuk \u00e7do baz\u00eb t\u00eb dh\u00ebnash ka nj\u00eb dritare teknologjike, kur mund t\u00eb ndalet baza.<\/li>\n<\/ul>\n<p>\nN\u00ebse kopjimi \"i ftoht\u00eb\" ju p\u00ebrshtatet, duhet t\u00eb mbani mend se<\/p>\n<ul>\n<li>\"kopja e ftoht\u00eb\" ndonj\u00ebher\u00eb duhet t\u00eb p\u00ebrfshij\u00eb edhe regjistrat. Metodat p\u00ebr p\u00ebrcaktimin e regjistrave q\u00eb duhet t\u00eb jen\u00eb pjes\u00eb e kopjes \"e ftoht\u00eb\" jan\u00eb individuale p\u00ebr \u00e7do DBMS. P\u00ebr shembull, n\u00eb Oracle \u00ebsht\u00eb e nevojshme t\u00eb kopjohen regjistrat online redo, dhe kjo do t\u00eb thot\u00eb se nj\u00eb num\u00ebr i caktuar i skedar\u00ebve regjistrues n\u00eb nj\u00eb katalog t\u00eb ve\u00e7ant\u00eb, madje edhe kur baza ndalhet n\u00eb m\u00ebnyr\u00eb korrekte. N\u00eb PostgreSQL, t\u00eb gjith\u00eb regjistrat duhet t\u00eb ruhet duke filluar nga regjistri q\u00eb p\u00ebrmban pik\u00ebn e fundit t\u00eb kontrollit, informacioni p\u00ebr t\u00eb cilin ndodhet n\u00eb skedarin administrativ.<\/li>\n<li>katalogu i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave mund t\u00eb p\u00ebrmbaj\u00eb skedar\u00eb t\u00eb m\u00ebdhenj t\u00eb hap\u00ebsirave t\u00eb p\u00ebrkohshme t\u00eb tabelave, t\u00eb cilat nuk \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrfshihen n\u00eb kopjen rezerv\u00eb. P\u00ebr mendje, ky v\u00ebrejtje \u00ebsht\u00eb e v\u00ebrtet\u00eb edhe p\u00ebr kopjimin \"e nxeht\u00eb\".<\/li>\n<\/ul>\n<p><\/p>\n<h3>\"Kopjimi i nxeht\u00eb\" i skedar\u00ebve<\/h3>\n<p>\nShumica e kopjeve rezerv\u00eb t\u00eb bazave t\u00eb t\u00eb dh\u00ebnave moderne kryhen duke kopjuar skedar\u00ebt e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave pa ndaluar baz\u00ebn. K\u00ebtu dalin disa probleme:<\/p>\n<ul>\n<li>N\u00eb momentin e fillimit t\u00eb kopjimit, p\u00ebrmbajtja e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave mund t\u00eb mos p\u00ebrputhet me p\u00ebrmbajtjen e skedar\u00ebve, pasi nj\u00eb pjes\u00eb e informacionit ndodhet n\u00eb cache dhe ende nuk \u00ebsht\u00eb shkruar n\u00eb disk.<\/li>\n<li>Gjat\u00eb kopjimit, p\u00ebrmbajtja e baz\u00ebs mund t\u00eb ndryshoj\u00eb. N\u00ebse p\u00ebrdoren struktura t\u00eb dh\u00ebnash t\u00eb ndryshueshme, p\u00ebrmbajtja e skedar\u00ebve ndryshon, nd\u00ebrsa n\u00ebse p\u00ebrdoren struktura t\u00eb pandryshueshme, ndryshon grupi i skedar\u00ebve: skedar\u00eb t\u00eb rinj shfaqen, nd\u00ebrsa t\u00eb vjetrat fshihen.<\/li>\n<li>Duke qen\u00eb se shkrimi i t\u00eb dh\u00ebnave n\u00eb baz\u00eb dhe leximi i skedar\u00ebve t\u00eb DB nuk sinkronizohen n\u00eb asnj\u00eb m\u00ebnyr\u00eb, programi i rezerv\u00ebs mund t\u00eb lexoj\u00eb nj\u00eb faqe t\u00eb pavlefshme, ku nj\u00eb pjes\u00eb do t\u00eb jet\u00eb nga versioni i vjet\u00ebr i faqes, dhe pjesa tjet\u00ebr nga versioni i ri.<\/li>\n<\/ul>\n<p>\nP\u00ebr t\u00eb siguruar q\u00eb kopja rezerv\u00eb t\u00eb jet\u00eb e q\u00ebndrueshme, \u00e7do DBMS ka nj\u00eb komand\u00eb q\u00eb njofton q\u00eb procesi i kopjimit rezerv\u00eb ka filluar. Sintaksikisht, kjo urdh\u00ebr mund t\u00eb duket ndryshe: <\/p>\n<ul>\n<li>n\u00eb Oracle kjo \u00ebsht\u00eb nj\u00eb komand\u00eb e ve\u00e7ant\u00eb ALTER DATABASE\/TABLESPACE BEGIN BACKUP;<\/li>\n<li>n\u00eb PostgreSQL \u2013 funksioni pg_start_backup();<\/li>\n<li>n\u00eb Microsoft SQL Server dhe DB2, p\u00ebrgatitja p\u00ebr kopjimin rezerv\u00eb realizohet n\u00eb m\u00ebnyr\u00eb implicite gjat\u00eb ekzekutimit t\u00eb komand\u00ebs BACKUP DATABASE;<\/li>\n<li>n\u00eb MySQL Enterprise, Cassandra dhe MongoDB, p\u00ebrgatitja realizohet n\u00eb m\u00ebnyr\u00eb implicite nga nj\u00eb mjet t\u00eb jasht\u00ebm \u2013 mysqlbackup, OpsCenter dhe Ops Manager p\u00ebrkat\u00ebsisht.<\/li>\n<\/ul>\n<p>\nMegjith\u00ebse ka dallime sintaksike, procesi i p\u00ebrgatitjes p\u00ebr kopjimin rezerv\u00eb duket nj\u00ebsoj.<\/p>\n<p>Ja si duket p\u00ebrgatitja p\u00ebr kopjimin rezerv\u00eb n\u00eb DBMS me struktura disku t\u00eb ndryshueshme, dmth., n\u00eb t\u00eb gjitha sistemet tradicionale relacional\u00eb t\u00eb diskut:<\/p>\n<ol>\n<li>Ruhet momenti i fillimit t\u00eb kopjimit rezerv\u00eb; kopja rezerv\u00eb do t\u00eb p\u00ebrfshij\u00eb regjistrat e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave q\u00eb fillojn\u00eb nga ky moment.<\/li>\n<li>Kryhet nj\u00eb pik\u00eb kontrolli, dmth. t\u00eb gjitha ndryshimet q\u00eb ndodhin n\u00eb faqet e t\u00eb dh\u00ebnave deri n\u00eb momentin e mbajtur, shkruhen n\u00eb disk. Kjo garanton q\u00eb regjistrat deri n\u00eb momentin e fillimit t\u00eb kopjimit rezerv\u00eb nuk do t\u00eb nevojiten gjat\u00eb rikuperimit.<\/li>\n<li>Aktivizohet nj\u00eb mod p\u00ebr regjistrim t\u00eb ve\u00e7ant\u00eb: n\u00ebse nj\u00eb faqe t\u00eb dh\u00ebnash \u00ebsht\u00eb ndryshuar p\u00ebr her\u00eb t\u00eb par\u00eb pas ngarkimit nga disku, at\u00ebher\u00eb n\u00eb vend q\u00eb t\u00eb regjistrohet n\u00eb regjist\u00ebr ndryshimi i faqes, baza do t\u00eb regjistroj\u00eb faqen e plot\u00eb. Gjat\u00eb procedur\u00ebs p\u00ebrgatit\u00ebse, t\u00eb gjitha faqet shkruhen n\u00eb disk, dhe k\u00ebshtu, me ndryshimin e par\u00eb, blloku gjithmon\u00eb do t\u00eb regjistrohet n\u00eb regjist\u00ebr t\u00ebr\u00ebsisht. Por, n\u00ebse gjat\u00eb procesit t\u00eb kopjimit, faqja p\u00ebrs\u00ebri do t\u00eb shkruhet n\u00eb disk, at\u00ebher\u00eb ndryshimi i saj t\u00eb ardhsh\u00ebm gjithashtu do t\u00eb sjell\u00eb paraqitjen n\u00eb regjist\u00ebr t\u00eb kopjes s\u00eb plot\u00eb t\u00eb faqes. Kjo garanton se n\u00ebse papritmas gjat\u00eb kopjimit t\u00eb skedar\u00ebve me t\u00eb dh\u00ebna faqeja del e pavlefshme, p\u00ebrdorimi i regjistrit do ta b\u00ebj\u00eb at\u00eb t\u00eb vlefshme p\u00ebrs\u00ebri.<\/li>\n<li>Bllokohet ndryshimi i titujve t\u00eb skedar\u00ebve t\u00eb t\u00eb dh\u00ebnave, dmth. pjesa e saj q\u00eb ndryshimet nuk reflektohen n\u00eb regjistra. Kjo garanton q\u00eb titulli do t\u00eb kopjohet n\u00eb m\u00ebnyr\u00eb korrekte, dhe pastaj regjistrat do t\u00eb aplikohen n\u00eb m\u00ebnyr\u00eb korrekte n\u00eb skedarin e t\u00eb dh\u00ebnave.<\/li>\n<\/ol>\n<p>\nPas p\u00ebrfundimit t\u00eb t\u00eb gjitha procedurave t\u00eb lartp\u00ebrmendura, mund t\u00eb kopjoni skedar\u00ebt e t\u00eb dh\u00ebnave me ndihm\u00ebn e sistemit operativ \u2013 cp, rsync dhe t\u00eb tjera. Aktivizimi i modit t\u00eb kopjimit redukton performanc\u00ebn e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave: s\u00eb pari, rritet volumi i regjistrave, dhe s\u00eb dyti, n\u00ebse ndodhin probleme gjat\u00eb modit t\u00eb kopjimit, rikuperimi do t\u00eb jet\u00eb m\u00eb i gjat\u00eb, pasi titujt e skedar\u00ebve t\u00eb t\u00eb dh\u00ebnave nuk p\u00ebrdit\u00ebsohen. Sa m\u00eb shpejt t\u00eb p\u00ebrfundoj\u00eb kopjimi, aq m\u00eb mir\u00eb \u00ebsht\u00eb p\u00ebr baz\u00ebn e t\u00eb dh\u00ebnave, prandaj \u00ebsht\u00eb e p\u00ebrshtatshme t\u00eb p\u00ebrdoren mjete t\u00eb till\u00eb si skedari (snapshot) i sistemit t\u00eb skedar\u00ebve ose ndar\u00ebsja e pasqyr\u00ebs (BCV) n\u00eb grumbullin e diskut. Disa DBMS (Oracle, PostgreSQL) lejojn\u00eb administratorin t\u00eb zgjedh\u00eb m\u00ebnyr\u00ebn e kopjimit, nd\u00ebrsa t\u00eb tjerat (Microsoft SQL Server) ofrojn\u00eb nj\u00eb nd\u00ebrfaqe p\u00ebr integrimin e mjeteve t\u00eb tyre t\u00eb kopjimit me mekanizmat e sistemeve t\u00eb skedar\u00ebve ose t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave.<\/p>\n<p>Pas p\u00ebrfundimit t\u00eb kopjimit, duhet t\u00eb kthehet baza e t\u00eb dh\u00ebnave n\u00eb gjendjen e zakonshme. N\u00eb Oracle, kjo b\u00ebhet me komand\u00ebn ALTER DATABASE\/TABLESPACE END BACKUP, n\u00eb PostgreSQL \u2013 duke thirrur funksionin pg_stop_backup(), dhe n\u00eb bazat e tjera \u2013 me n\u00ebnprograme t\u00eb brendshme t\u00eb komandave p\u00ebrkat\u00ebse ose sh\u00ebrbimeve t\u00eb jashtme.<\/p>\n<p>K\u00ebshtu duket diagrami preliminar i procesit t\u00eb kopjimit:<\/p>\n<p><img decoding=\"async\" alt=\"Udh\u00ebzuesi p\u00ebr backup-in e bazave t\u00eb t\u00eb dh\u00ebnave\" src=\"\/wp-content\/uploads\/2020\/08\/4e74f865e9f35acec083b747da4449cf.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<ul>\n<li>P\u00ebrgatitja p\u00ebr kopjimin (begin backup) merr koh\u00eb, ndonj\u00ebher\u00eb duke qen\u00eb e konsiderueshme. Edhe kur p\u00ebrdoren v\u00ebllime pasqyruese ose sisteme skedar\u00ebsh me mund\u00ebsi p\u00ebr t\u00eb b\u00ebr\u00eb skedare, procesi i kopjimit nuk do t\u00eb jet\u00eb i menj\u00ebhersh\u00ebm.<\/li>\n<li>S\u00eb bashku me skedar\u00ebt e t\u00eb dh\u00ebnave, duhet t\u00eb ruani regjistrat duke filluar nga momenti i p\u00ebrgatitjes p\u00ebr kopjim dhe p\u00ebrfunduar me momentin e kthimit t\u00eb baz\u00ebs n\u00eb gjendjen normale.<\/li>\n<li>Mund t\u00eb rikuperoheni nga ky kopjim <b>n\u00eb momentin e kthimit t\u00eb baz\u00ebs n\u00eb gjendjen normale<\/b>. Rikuperimi n\u00eb nj\u00eb moment m\u00eb t\u00eb hersh\u00ebm nuk \u00ebsht\u00eb i mundur.<\/li>\n<\/ul>\n<p>\nMe bazat e t\u00eb dh\u00ebnave q\u00eb p\u00ebrdorin struktura t\u00eb pandryshueshme t\u00eb t\u00eb dh\u00ebnave (skedare memorie, pem\u00eb LSM) situata \u00ebsht\u00eb m\u00eb e thjesht\u00eb. P\u00ebrgatitja p\u00ebr kopjimin p\u00ebrb\u00ebhet nga hapat e m\u00ebposht\u00ebm:<\/p>\n<ol>\n<li>T\u00eb dh\u00ebnat nga memoria hidhen n\u00eb disk.<\/li>\n<li>Regjistrohet lista e skedar\u00ebve q\u00eb do t\u00eb hyjn\u00eb n\u00eb kopjim. Deri sa procesi i kopjimit t\u00eb p\u00ebrfundoj\u00eb, baza ndalohet t\u00eb fshij\u00eb k\u00ebta skedar\u00eb, madje edhe n\u00ebse ata nuk jan\u00eb m\u00eb t\u00eb nevojsh\u00ebm.<\/li>\n<\/ol>\n<p>\nMe sinjalin q\u00eb kopjimi ka p\u00ebrfunduar, baza me struktura t\u00eb pandryshueshme mund t\u00eb fshij\u00eb p\u00ebrs\u00ebri skedar\u00ebt q\u00eb nuk i nevojiten.<\/p>\n<h3>Rikuperimi n\u00eb pik\u00ebn<\/h3>\n<p>\nKopja e rezerv\u00ebs lejon rikuperimin e gjendjes s\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave n\u00eb momentin kur p\u00ebrfundoi urdhri p\u00ebr kthim nga moda e kopjimit. Megjithat\u00eb, nj\u00eb aksident, pas t\u00eb cilit k\u00ebrkohet rikuperimi, mund t\u00eb ndodh\u00eb n\u00eb \u00e7do moment. Detyra e rikuperimit t\u00eb gjendjes s\u00eb DB n\u00eb nj\u00eb moment t\u00eb caktuar quhet \"rikuperim n\u00eb pik\u00eb\" (point-in-time recovery).<\/p>\n<p>P\u00ebr t\u00eb siguruar k\u00ebt\u00eb mund\u00ebsi, duhet t\u00eb ruani regjistrat e DB duke filluar nga momenti i p\u00ebrfundimit t\u00eb kopjimit, dhe gjat\u00eb rikuperimit t\u00eb vazhdoni t\u00eb aplikoni regjistrat n\u00eb kopjen e rikuperuar. Pas rikuperimit t\u00eb DB nga kopja n\u00eb momentin e p\u00ebrfundimit t\u00eb kopjimit, gjendja e baz\u00ebs (skedar\u00ebve dhe faqeve t\u00eb memorizuara) \u00ebsht\u00eb garantuar t\u00eb jet\u00eb e sakt\u00eb, prandaj nuk nevojitet nj\u00eb mod regjistrimi t\u00eb ve\u00e7ant\u00eb. Duke aplikuar regjistrat deri n\u00eb momentin e nevojsh\u00ebm, mund t\u00eb sigurohet gjendja e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave n\u00eb \u00e7do moment n\u00eb koh\u00eb.<\/p>\n<p>N\u00ebse shpejt\u00ebsia e rikuperimit t\u00eb kopjes \u00ebsht\u00eb e kufizuar vet\u00ebm nga kapaciteti i diskut, at\u00ebher\u00eb shpejt\u00ebsia e aplikimit t\u00eb regjistrave zakonisht kufizohet nga performanca e procesorit. N\u00ebse n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave kryesore ndodhin ndryshime paralelisht, at\u00ebher\u00eb gjat\u00eb rikuperimit t\u00eb gjitha ndryshimet kryhen n\u00eb m\u00ebnyr\u00eb t\u00eb nj\u00ebpasnj\u00ebshme \u2013 n\u00eb rendin e leximit nga regjistri. Si rrjedhoj\u00eb, koha e rikuperimit \u00ebsht\u00eb linearisht e varur nga sa larg \u00ebsht\u00eb pika e rikuperimit nga pika e p\u00ebrfundimit t\u00eb kopjimit. P\u00ebr k\u00ebt\u00eb arsye, detyrohemi t\u00eb b\u00ebjm\u00eb kopje t\u00eb plota mjaft shpesh \u2013 minimum nj\u00eb her\u00eb n\u00eb jav\u00eb p\u00ebr bazat me ngarkes\u00eb t\u00eb vog\u00ebl transaksionesh dhe deri n\u00eb kopjime ditore p\u00ebr bazat me ngarkesa t\u00eb larta.<\/p>\n<h3>Kopjimi inkremental<\/h3>\n<p>\nP\u00ebr t\u00eb p\u00ebrshpejtuar rikuperimin n\u00eb pik\u00ebn, do t\u00eb donim t\u00eb kishim mund\u00ebsin\u00eb t\u00eb realizonim kopjime sa m\u00eb shpesh, por, n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, t\u00eb mos z\u00ebn\u00eb vend t\u00eb tep\u00ebrt n\u00eb disqe dhe t\u00eb mos ngarkojn\u00eb baz\u00ebn me detyra kopjimi.<\/p>\n<p>Zgjidhja e problemit \u00ebsht\u00eb kopjimi inkremental, dometh\u00ebn\u00eb kopjimi vet\u00ebm i faqeve t\u00eb t\u00eb dh\u00ebnave q\u00eb jan\u00eb ndryshuar q\u00eb nga kopjimi i m\u00ebparsh\u00ebm.<br \/>\nKopjimi incremental ka kuptim vet\u00ebm p\u00ebr DB-t\u00eb q\u00eb p\u00ebrdorin struktura t\u00eb dh\u00ebnash t\u00eb ndryshueshme.<\/p>\n<p>Inkrementi mund t\u00eb matet si nga kopja e plot\u00eb rezerv\u00eb (kopja kumulative), ashtu edhe nga \u00e7do kopje t\u00eb m\u00ebparshme (kopja diferenciale). <\/p>\n<p><img decoding=\"async\" alt=\"Udh\u00ebzuesi p\u00ebr backup-in e bazave t\u00eb t\u00eb dh\u00ebnave\" src=\"\/wp-content\/uploads\/2020\/08\/10e3bb87445cb36693c7b5469d62eeaf.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nFatkeq\u00ebsisht, nuk ekziston nj\u00eb terminologji e vetme, dhe prodhues t\u00eb ndrysh\u00ebm p\u00ebrdorin terma t\u00eb ndrysh\u00ebm:<\/p>\n<p>Diferenciale<br \/>\nKumulative<\/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>\nN\u00ebse ekzistojn\u00eb kopje inkrementale, procesi i rikuperimit n\u00eb pik\u00ebn e caktuar duket si vijon:<\/p>\n<ul>\n<li>rikuperohet kopja e fundit e plot\u00eb rezerv\u00eb, e b\u00ebr\u00eb para momentit t\u00eb rikuperimit;<\/li>\n<li>sip\u00ebr kopj\u00ebs s\u00eb plot\u00eb rikuperohen kopjet inkrementale;<\/li>\n<li>ngarkohen ditar\u00ebt nga pika e fillimit t\u00eb kopjimit t\u00eb rezerv\u00ebs deri n\u00eb pik\u00ebn e rikuperimit.<\/li>\n<\/ul>\n<p>\nPrania e nj\u00eb kopje kumulative e p\u00ebrshpejton procesin e rikuperimit. P\u00ebr shembull, p\u00ebr t\u00eb rikuperuar gjendjen e baz\u00ebs n\u00eb nj\u00eb pik\u00eb midis T3 dhe T4 \u00ebsht\u00eb e nevojshme t\u00eb rikuperohen dy kopje inkrementale, nd\u00ebrsa p\u00ebr t\u00eb rikuperuar n\u00eb nj\u00eb pik\u00eb pas T4 \u2013 vet\u00ebm nj\u00eb.<br \/>\nSigurisht, q\u00ebllimi i nj\u00eb kopje kumulative \u00ebsht\u00eb m\u00eb i vog\u00ebl se ai i disa kopjeve diferenciale, pasi disa faqe kan\u00eb ndryshuar disa her\u00eb, dhe \u00e7do kopje inkrementale p\u00ebrmban versionin e saj t\u00eb faqes.<\/p>\n<p>Ka tri m\u00ebnyra p\u00ebr t\u00eb krijuar nj\u00eb kopje inkrementale:<\/p>\n<ol>\n<li>krijimi i nj\u00eb kopje t\u00eb plot\u00eb dhe llogaritja e diferenc\u00ebs me kopjen e fundit t\u00eb plot\u00eb;<\/li>\n<li>analiza e ditar\u00ebve, p\u00ebrgatitja e nj\u00eb liste t\u00eb faqeve t\u00eb ndryshuara dhe rezervimi i faqeve t\u00eb p\u00ebrfshira n\u00eb list\u00eb;<\/li>\n<li>k\u00ebrkesa p\u00ebr faqet e ndryshuara n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave.<\/li>\n<\/ol>\n<p>\nM\u00ebnyra e par\u00eb kursen hap\u00ebsir\u00eb diskun, por nuk zgjidh ngarkes\u00ebn mbi baz\u00ebn e t\u00eb dh\u00ebnave. M\u00eb shum\u00eb, n\u00ebse kemi nj\u00eb kopje t\u00eb plot\u00eb rezerv\u00eb, at\u00ebher\u00eb kthimi n\u00eb nj\u00eb inkrementale \u00ebsht\u00eb pa kuptim, pasi rikuperimi i kopjes s\u00eb plot\u00eb \u00ebsht\u00eb m\u00eb i shpejt\u00eb se rikuperimi i kopj\u00ebs s\u00eb plot\u00eb t\u00eb m\u00ebparshme dhe inkrementaleve. Problemin e kursimit t\u00eb hap\u00ebsir\u00ebs diskun duhet ta delegohet n\u00eb komponent\u00eb t\u00eb ve\u00e7ant\u00eb me mekanizma t\u00eb integruar deduplication. K\u00ebto mund t\u00eb jen\u00eb si sisteme t\u00eb ve\u00e7anta ruajtjeje (EMC DataDomain, HPE StorageWorks VLS, e gjith\u00eb gama NetApp), ashtu edhe produkte softuerike (ZFS, Veritas NetBackup PureFile, Windows Server Data Deduplication).<\/p>\n<p>M\u00ebnyra e dyt\u00eb dhe e tret\u00eb dallohen nga mekanizmi i p\u00ebrcaktimit t\u00eb list\u00ebs s\u00eb faqeve t\u00eb ndryshuara. Analiza e ditar\u00ebve \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00eb p\u00ebr resurset, p\u00ebrve\u00e7 k\u00ebsaj, p\u00ebr ta realizuar \u00ebsht\u00eb e nevojshme t\u00eb njoh\u00ebsh struktur\u00ebn e skedar\u00ebve t\u00eb ditar\u00ebve. T\u00eb pyes\u00ebsh vet\u00eb baz\u00ebn se cilat faqe kan\u00eb ndryshuar \u00ebsht\u00eb m\u00eb e thjesht\u00eb, por p\u00ebr k\u00ebt\u00eb, b\u00ebrthama e DB-s\u00eb duhet t\u00eb ket\u00eb funksionalitetin p\u00ebr t\u00eb ndjekur ndryshimet n\u00eb blloqe (block change tracking).<\/p>\n<p>Funksionaliteti i kopjimit t\u00eb rezervave inkrementale u krijua p\u00ebr her\u00eb t\u00eb par\u00eb n\u00eb softuerin Oracle Recovery Manager (RMAN), i cili u shfaq n\u00eb versionin Oracle 8i. Oracle menj\u00ebher\u00eb zbatoi ndjekjen e blloqeve t\u00eb ndryshuara, prandaj nuk kishte nevoj\u00eb p\u00ebr analiz\u00ebn e ditar\u00ebve.<\/p>\n<p>PostgreSQL nuk ndjek blloqet e ndryshuara, prandaj utilitarja pg_probackup, e zhvilluar nga kompania ruse Postgres Professional, p\u00ebrcakton faqe t\u00eb ndryshuara duke analizuar ditar\u00ebt. Megjithat\u00eb, kompania ofron gjithashtu DB-n\u00eb PostgresPro, e cila p\u00ebrfshin zgjerimin ptrack, q\u00eb ndjek ndryshimet n\u00eb faqe. Kur p\u00ebrdoret pg_probackup me DB-n\u00eb PostgresPro, utilitarja k\u00ebrkon faqet e ndryshuara direkt nga vet\u00eb baza \u2013 ashtu si RMAN.<\/p>\n<p>Microsoft SQL Server ashtu si Oracle, ndjek faqet e ndryshuara, por komand\u00ebs BACKUP i lejon t\u00eb b\u00ebj\u00eb vet\u00ebm kopje t\u00eb plota dhe kumulative.<\/p>\n<p>N\u00eb DB2 ekziston mund\u00ebsia p\u00ebr t\u00eb ndjekur faqet e ndryshuara, por p\u00ebr m\u00eb shum\u00eb \u00ebsht\u00eb e \u00e7aktivizuar nga e drejta. Pas aktivizimit, DB2 do t\u00eb lejoj\u00eb krijimin e kopjeve t\u00eb plota, diferenciale dhe kumulative.<\/p>\n<p>Nj\u00eb dallim i r\u00ebnd\u00ebsish\u00ebm midis mjeteve t\u00eb p\u00ebrshkruara n\u00eb k\u00ebt\u00eb seksion (p\u00ebrve\u00e7 pg_probackup) dhe mjeteve t\u00eb kopjimit t\u00eb skedar\u00ebve \u00ebsht\u00eb se ato k\u00ebrkojn\u00eb imazhet e faqeve nga databaza, jo lexojn\u00eb t\u00eb dh\u00ebnat nga disku vet\u00eb. Mang\u00ebsia e k\u00ebtij qasja \u00ebsht\u00eb ngarkesa e vog\u00ebl shtes\u00eb mbi databaz\u00ebn. Megjithat\u00eb, kjo mang\u00ebsi p\u00ebrmbushet plot\u00ebsisht nga fakti se faqja e lexuar \u00ebsht\u00eb gjithmon\u00eb e sakt\u00eb, prandaj nuk ka nevoj\u00eb p\u00ebr aktivizimin e nj\u00eb regjimi t\u00eb ve\u00e7ant\u00eb n\u00eb koh\u00ebn e kopjimit t\u00eb rezerv\u00ebs.<\/p>\n<p>Kujtoni p\u00ebrs\u00ebri q\u00eb prania e kopjeve inkrementale nuk heq k\u00ebrkesat p\u00ebr pranin\u00eb e ditar\u00ebve p\u00ebr rikuperim n\u00eb nj\u00eb pik\u00eb t\u00eb caktuar n\u00eb koh\u00eb. Prandaj n\u00eb databazat industriale, ditar\u00ebt vazhdimisht shkruhen n\u00eb nj\u00eb mb\u00ebshtetje t\u00eb jashtme, nd\u00ebrsa kopjet rezerv\u00eb, t\u00eb plota dhe\/ose inkrementale, krijohen sipas nj\u00eb orari.<\/p>\n<p>Implementimi m\u00eb i mir\u00eb deri m\u00eb tani i ides\u00eb s\u00eb kopjimit incremental \u00ebsht\u00eb kompleksi softuerik-hardware (n\u00eb terminologjin\u00eb e Oracle \u2013 sistemi i projektuar) Zero Data Loss Recovery Appliance \u2013 nj\u00eb zgjidhje e specializuar e Oracle p\u00ebr kopjimin e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave t\u00eb saj. Kompleksi p\u00ebrb\u00ebhet nga nj\u00eb grup <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sq\/server\/\"   title=\"servera\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1521\">servera<\/a> me nj\u00eb volum t\u00eb madh disqesh, mbi t\u00eb cilat \u00ebsht\u00eb instaluar nj\u00eb version i modifikuar i softuerit Recovery Manager dhe mund t\u00eb punoj\u00eb me komplekse t\u00eb tjera softuerike-hardware t\u00eb Oracle (Database Appliance, Exadata, SPARC Supercluster), si dhe me bazat e t\u00eb dh\u00ebnave Oracle n\u00eb infrastruktur\u00ebn tradicionale. Ndryshe nga RMAN-i 'i zakonsh\u00ebm', n\u00eb ZDLRA \u00ebsht\u00eb realizuar koncepti i 'incremental forever'. Sistemi krijon nj\u00eb kopje t\u00eb plot\u00eb t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave nj\u00eb her\u00eb, dhe pastaj b\u00ebn vet\u00ebm kopje inkrementale. Modul t\u00eb tjera RMAN-i lejojn\u00eb bashkimin e kopjave, duke krijuar kopje t\u00eb reja t\u00eb plota nga ato inkrementale. <\/p>\n<p>P\u00ebr nder t\u00eb zhvilluesve rus\u00eb, duhet t\u00eb theksohet se edhe pg_probackup di t\u00eb bashkoj\u00eb kopjat inkrementale.<\/p>\n<p><img decoding=\"async\" alt=\"Udh\u00ebzuesi p\u00ebr backup-in e bazave t\u00eb t\u00eb dh\u00ebnave\" src=\"\/wp-content\/uploads\/2020\/08\/275b649ce74614c04410618a062dddbd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00eb kund\u00ebrshtim me shum\u00eb pyetje t\u00eb ngjashme, pyetja 'cili \u00ebsht\u00eb metoda m\u00eb e mir\u00eb p\u00ebr kopjimin' ka nj\u00eb p\u00ebrgjigje t\u00eb qart\u00eb \u2013 m\u00eb s\u00eb miri \u00ebsht\u00eb utilitari i lindur p\u00ebr DBMS-n\u00eb e p\u00ebrdorur q\u00eb siguron mund\u00ebsin\u00eb e kopjimit inkrementale.<\/p>\n<p>P\u00ebr administratorin e DB-s\u00eb, pyetjet mbi zgjedhjen e strategjis\u00eb s\u00eb kopjimit dhe integrimin e mjeteve t\u00eb kopjimit t\u00eb bazave t\u00eb dh\u00ebnave n\u00eb infrastruktur\u00ebn korporative jan\u00eb shum\u00eb m\u00eb t\u00eb r\u00ebnd\u00ebsishme. Por k\u00ebto \u00e7\u00ebshtje jan\u00eb jasht\u00eb scope-it t\u00eb k\u00ebtij artikulli.<br \/>\n<br \/>Burimi: <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.0.1 - 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\/sq\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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\/sq\/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\udd47Udh\u00ebzuesi p\u00ebr kopjimin e bazave t\u00eb t\u00eb dh\u00ebnave | ProHoster","description":"\u2013 Oh, no shelter can withstand a meteorite impact.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/putevoditel-po-rezervnomu-kopirovaniyu-baz-dannyh","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/92367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=92367"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/92367\/revisions"}],"predecessor-version":[{"id":158765,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/92367\/revisions\/158765"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/92368"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=92367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=92367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=92367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}